Jump to content

Google Nexus 5 by LG Preview (LG D820)


MacinJosh

Recommended Posts

So do we expect to see a Nexus 5 available on all carriers this time around?  It was kinda sad to see the Nexus 4 only available to Tmobile last year.

 

I'm expecting it based on what I see in this thread. Its down between the Nexus 5 and Note 3 for me now!

 

Edit: I do hope if they bring a nexus back to CDMA carriers, that they work out some kind of deal to get the devices fully supported in AOSP, and updates pushed by Google would be nice...

Link to comment
Share on other sites

Serious question: given the hedging on the meaning of the band certifications (quoted below), what are the odds this will be a Sprint device? Are any of these bands unique to Sprint and unlikely to be in a non-Sprint phone? Is this device intended to work across all carriers?

 

Interpretation from the more knowledgeable is appreciated!

 

The FCC authorization docs show tests run for CDMA2000 band class 10 and LTE band class 41.  Those are practically unique to Sprint, especially in combination.

 

Additionally, LTE bands 4, 5, and 17 are included, covering AT&T and T-Mobile.  The outlier in the tests is LTE band class 13.  It is currently unique to VZW and was not included.

 

So, if this a new Nexus 5, maybe Google is getting back at VZW for screwing over previous Nexus handsets.

 

AJ

  • Like 9
Link to comment
Share on other sites

The FCC authorization docs show tests run for CDMA2000 band class 10 and LTE band class 41.  Those are practically unique to Sprint, especially in combination.

 

Additionally, LTE bands 4, 5, and 17 are included, covering AT&T and T-Mobile.  The outlier in the tests is LTE band class 13.  It is currently unique to VZW and was not included.

 

So, if this a new Nexus 5, maybe Google is getting back at VZW for screwing over previous Nexus handsets.

 

AJ

 

It is kind of strange they didn't just bump it up to hexaband for a nationwide nexus model. Unless there was simply no room? Or maybe Sprint agreed to terms that Verizon wouldn't agree to?  Like perhaps being sold only through the play store? 

Link to comment
Share on other sites

It is kind of strange they didn't just bump it up to hexaband for a nationwide nexus model. (Unless there was simply no room?)

 

It could be a political decision, retribution for VZW.  Or it could be a technical reason, since band class 13 is the only one of the bunch that has an inverted FDD downlink/uplink.

 

AJ

Link to comment
Share on other sites

Only Sprint uses SMR 800 LTE, PCS LTE, & EBS/BRS 2500-2600mhz LTE so it's damn sure going to be on  Sprint to have those specific bands. 

 

Pretty close.  But band 2/25 LTE is part of the AT&T UE regime now.

 

AJ

Link to comment
Share on other sites

write the article before every other Android blog gets wind of this.

 

Of course.  Our FCC OET articles just write themselves in a matter of minutes.

 

;)

 

AJ

  • Like 10
Link to comment
Share on other sites

write the article before every other Android blog gets wind of this.

 

Sent from my SPH-L710 using Tapatalk 4

 

Considering 80% of the people reading this article are guests, I'm assuming they already know.  :lol:

  • Like 1
Link to comment
Share on other sites

  • Like 13
Link to comment
Share on other sites

And just to head off the question posse, no, this mystery handset does not support SVDO nor SVLTE.

 

AJ

 

I just read this lol. Well, at least the possibility of LTE roaming takes the edge off.

Link to comment
Share on other sites

That WOULD be awesome if this device opened up a new era of cross-country roaming on and between ALL carriers of some sort. (but that would be way too good to be true, I am sure).

  • Like 1
Link to comment
Share on other sites

The FCC authorization docs show tests run for CDMA2000 band class 10 and LTE band class 41.  Those are practically unique to Sprint, especially in combination.

 

Additionally, LTE bands 4, 5, and 17 are included, covering AT&T and T-Mobile.  The outlier in the tests is LTE band class 13.  It is currently unique to VZW and was not included.

 

So, if this a new Nexus 5, maybe Google is getting back at VZW for screwing over previous Nexus handsets.

 

AJ

 

What did Verizon do in the past that rubbed Google in the wrong way?

Link to comment
Share on other sites

Galaxy Nexus updates.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

 

What do you mean by that?  Verizon held up speedier Nexus updates on the Galaxy Nexus and ruined part of the image of a Nexus device?

Link to comment
Share on other sites

What do you mean by that? Verizon held up speedier Nexus updates on the Galaxy Nexus and ruined part of the image of a Nexus device?

Verizon insisted on bloating the device up with Verizon specific apps instead of letting it be pure Google so having a nexus on Verizon kind of killed the pure Google experience.
  • Like 2
Link to comment
Share on other sites

Verizon insisted on bloating the device up with Verizon specific apps instead of letting it be pure Google so having a nexus on Verizon kind of killed the pure Google experience.

 

Wow.  Well in that case, I hope Google screws over Verizon and not offer the Nexus 5 to them and make them beg for mercy.

Link to comment
Share on other sites

Wow.  Well in that case, I hope Google screws over Verizon and not offer the Nexus 5 to them and make them beg for mercy.

They won't beg for mercy, from what I understand Nexus devices don't sell that well.

Link to comment
Share on other sites

I posted this article in another thread, but it kinda makes sense here to. Its an article on google's strategy on updating android devices regardless of what the carrier does. So even if the CDMA chip used to be an issue updating the CDMA nexus is the past, this goes a long way into alleviating customers need to update. So maybe Google doesn't mind getting into bed with Sprint again. (not sure why they are leaving Verizon out though)

 

http://arstechnica.com/gadgets/2013/09/balky-carriers-and-slow-oems-step-aside-google-is-defragging-android/

Link to comment
Share on other sites

That is fine.  Google should just have it available for Tmobile, Sprint and ATT.

Oh I absolutely agree, I just know that Verizon won't be crying over not getting the whatever the call the next Nexus.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • I use wireless charging whenever possible so as to minimize issues like this.
    • AT&T Is Not Happy About T-Mobile Sticking Their Nose Into The First Responder Business
    • A month later and this site is finally live. Not getting gig+ download speeds yet but uploads on this site are insane. 
    • DirecTV clinches long-elusive deal to combine with Dish https://www.cnbc.com/2024/09/30/att-sells-70percent-stake-in-directv-to-tpg-for-7point6-billion.html?__source=androidappshare Not certain how far roughly $500 million will last with their current burn rate.  The bond holders asked to take a slight haircut could also demand it. The debt reduction will make the "forth" carrier far more attractive to deeper pockets.
    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...