Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

Is it an international version nexus? I thought the nexus had a few variants based on location?

Nope, there is only one version of the hardware that works for all locations.

 

EDIT: Oops there are two versions, but they had the same software.

 

Sent from my Nexus 5 using Tapatalk

 

Link to comment
Share on other sites

IIRC, the same software goes for both d820 and d821.

 

Sent from my Nexus 5

 

Nope, there is only one version of the hardware that works for all locations.

 

Sent from my Nexus 5 using Tapatalk

Oh ok. Been used to samsung having different version. Buildprop edit could be it, but the baseband was different than the 4.4.2 update. Mixed feeling then.

Link to comment
Share on other sites

Lucky you got the 16GB model, I guess.

 

Can't confirm any 32GB models that have MEIDs loaded with sprint, sadly.

Whoh, that is not cool. I was just about to order one, I really don't want to order a 16gb from Sprint for the same price..

 

I guess I will ask around on XDA.

 

Sent from my GT-P5210 using Tapatalk

 

 

Link to comment
Share on other sites

Whoh, that is not cool. I was just about to order one, I really don't want to order a 16gb from Sprint for the same price..

 

I guess I will ask around on XDA.

 

Sent from my GT-P5210 using Tapatalk

 

You are looking far back in the posts there buddy.  Go ahead and buy the 32GB one, there is no issue activating it on Sprint now.

  • Like 5
Link to comment
Share on other sites

The only known issue at this point is that N5s bought from T-Mobile (and possibly from other carriers that sell the North American version of the N5, such as the various Canadian carriers that sell it) do not seem to be in Sprint's database; if Google or Sprint sold it to you directly, you should be fine.

  • Like 1
Link to comment
Share on other sites

So I got mine from Sprint. Should I get it from Google and then return this one?

 

If you want the 32gb version. So far the 16gb version is identical to the 16gb version from Google play. Also depends if you used an upgrade or bought it flat out. In a situation where I was able to upgrade, I would buy an Iphone 5s and sell it factory sealed with the discount and then buy a model from Google play. As for out right, I believe the Google play model is a little be cheaper.

 

EDIT. Google play has the 16gb for 349.99 and the 32gb for 399.99. If you bought it full price from Sprint for 399.99 you are better off saving 50 bucks or getting the additional 16gb for about the same price (tax difference and shipping).

Link to comment
Share on other sites

Whoh, that is not cool. I was just about to order one, I really don't want to order a 16gb from Sprint for the same price..

 

I guess I will ask around on XDA.

 

Sent from my GT-P5210 using Tapatalk

 

 

Yeah that was back right when they came out.

 

Sprint was actually on the ball and resolved the issue within 48 hours.  Early adopter pains.

Link to comment
Share on other sites

The only known issue at this point is that N5s bought from T-Mobile (and possibly from other carriers that sell the North American version of the N5, such as the various Canadian carriers that sell it) do not seem to be in Sprint's database; if Google or Sprint sold it to you directly, you should be fine.

 

 

That's actually good to know - I had no idea T-Mobile Nexus 5 IMEIs were not loaded into sprint.

 

Sprint/Google should support all model D820's - less customer confusion.

Link to comment
Share on other sites

That's actually good to know - I had no idea T-Mobile Nexus 5 IMEIs were not loaded into sprint.

 

Sprint/Google should support all model D820's - less customer confusion.

There could be concerns about a tmo phone being stolen or not paid off yet. Don't know if that is one of the reasons for not including the tmo phones ... yet.

 

Jim, Sent from my Photon 4G using Tapatalk 2

 

 

 

  • Like 1
Link to comment
Share on other sites

There could be concerns about a tmo phone being stolen or not paid off yet. Don't know if that is one of the reasons for not including the tmo phones ... yet.

 

Jim, Sent from my Photon 4G using Tapatalk 2

 

That doesn't make much sense, as they're not locked, it could be used on any other GSM company.

That stolen database, does that even work?

Link to comment
Share on other sites

If the imei isn't in the system they won't even authenticate on that providers network. So while they are unlocked T-Mobile not releasing the imei number is kinda fishy.

 

Sent from my Nexus 5 using Tapatalk

 

 

Link to comment
Share on other sites

If the imei isn't in the system they won't even authenticate on that providers network. So while they are unlocked T-Mobile not releasing the imei number is kinda fishy.

 

Sent from my Nexus 5 using Tapatalk

 

They believe in poaching, but only if they're the one doing it.

Link to comment
Share on other sites

Aw geez!  My Nexus 5 should be arriving today via UPS.  I just called Sprint and they said they were 2 months backordered on the SIM cards!  That's nuts!

 

Anyone have a Sprint SIM card lying around???

  • Like 1
Link to comment
Share on other sites

Aw geez! My Nexus 5 should be arriving today via UPS. I just called Sprint and they said they were 2 months backordered on the SIM cards! That's nuts!

 

Anyone have a Sprint SIM card lying around???

That better not be the case, I'm ordering mine in two weeks..... I'll try online chat and my local coperate store.

 

Sent from my EVO using Tapatalk

 

 

Link to comment
Share on other sites

So, I guess this makes sense but I noticed some odd behavior (to me) of my Nexus 5 recently.  A new LTE B25 site went live in my area / commute home.  It is providing very fringe / high dB service in the 115's to 120s.  The tower has incredible range and the area is conveniently flat in that area.  What I've noticed is that I'll be on a cell phone call and experience a dropped call.  As soon as the call drops, I'll get LTE service (albeit very high dB) for a little while before it switches back / moves to the next tower.  The reason I bring this up is because without this tower being live I wouldn't have any problem using my phone during the drive.  With what I've learned from this site, it makes sense that my phone is dropping and have issues with NV and legacy (Samsung / Moto market), but is it normal that my phone is actively hunting LTE while I'm on a phone call?  Especially with a triband device.  I apologize if it is an ignorant question, just trying to get a better understanding of how this "system" all works.  I suppose the engineer in me...

 

Thank you in advance. 

Link to comment
Share on other sites

Nothing to see here. The current build is KOT49H. KOT49N is just another build done on the same day.

 

Sent from my Nexus 5 using Tapatalk

 

 

Pretty sure Jan 10 was not the same day as kot49h...

 

Sent from my Nexus 5

The KOT49N indicates that the ROM is built on the same day as KOT49H, but it's the kernel version that was built on Jan 10th. I've seen this before on my GS3 where Samsung released a firmware called MD4 (April 4th, 2013), but the kernel version they released was something along the lines of April 14th.

 

If the picture is true, though, I'm surprised Google wouldn't bump the Android version to 4.4.3, unless this really is just KOT49H with a Sprint Spark update and nothing more to see. Still, even Spark should be a big enough update to warrant a 0.0.1 bump in version number in my opinion, as Sprint Customer Service can point to that version number when an unknowing customer comes in asking why their Nexus 5 isn't getting Spark speeds.

Link to comment
Share on other sites

It is providing very fringe / high dB service in the 115's to 120s.

 

For sake of clarity, that is very low signal because those are negative numbers.  The high/low dBm issue causes considerable confusion.

 

AJ

  • Like 1
Link to comment
Share on other sites

For sake of clarity, that is very low signal because those are negative numbers.  The high/low dBm issue causes considerable confusion.

 

AJ

I appreciate the quick response.  I understand the dB, I'm more confused with how or why the phone is looking for LTE service when I'm ON a phone call.  It certainly makes sense when I'm using data, but why is the phone searching / connecting to an LTE tower when I'm on voice.  I would have thought the preference would be to other 1X towers...?  I hope that helps clarify my original question.  Thanks again.

Link to comment
Share on other sites

For sake of clarity, that is very low signal because those are negative numbers.  The high/low dBm issue causes considerable confusion.

 

AJ

Exactly. Had it actually been 115 dBm, he probably wouldn't have lived to write that post! ;)

Link to comment
Share on other sites

I appreciate the quick response.  I understand the dB, I'm more confused with how or why the phone is looking for LTE service when I'm ON a phone call.  It certainly makes sense when I'm using data, but why is the phone searching / connecting to an LTE tower when I'm on voice.

 

If you are actively using CDMA1X, an e/CSFB single RF path handset cannot search for LTE.  That is not possible.  So, some other reason is the cause for the dropped calls.

 

AJ

Link to comment
Share on other sites

If you are actively using CDMA1X, an e/CSFB single RF path handset cannot search for LTE. That is not possible. So, some other reason is the cause for the dropped calls.

 

AJ

Thanks, that is exactly what I was looking for. I'll look into why / if I can replicate it.

Link to comment
Share on other sites

Exactly. Had it actually been 115 dBm, he probably wouldn't have lived to write that post! ;)

 

If someone wants to calculate the solar constant across one square foot -- roughly the footprint of a human being -- I propose that challenge.  I am curious to know what is the infrared/visible/ultraviolet "signal" strength in dBm.

 

AJ

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Similar Content

  • Posts

    • Two s24 ultras, both say fully up to date. One has T-Mobile and Verizon network, Service provider software version 17, carrier config version 2, and few apps [google play system March 1], other with T-Mobile, Dish Rainbow Sim, Verizon Network (inactive), Service provider software version 19, no carrier config, and many apps [Google play system April 1]
    • Since T-Mobile is testing the fiber waters for a time when FWA needs to be paired back, here is an article comparing the two costs (performance differences not mentioned): https://www.fierce-network.com/broadband/nextlink-ceo-compares-fixed-wireless-fiber. 
    • Checked and found a 2.7mb Google Play System 'security' update pending.   Post install the update date still showing April 1st however.
    • The May security update is out.
    • A new SignalCheck Pro update is now available on Google Play! Notable changes: Improved duplicate LTE GCI cleanup function. Duplicates with the greater number of recorded connection 'hits' will now be kept. Duplicate entries appear for a variety of reasons but can cause neighbor cell notes to display improperly. Strongly recommend running this cleanup function occasionally. Improved site note logging functionality. Better matching of co-located cells and prior Sprint sites. Overhauled display functions to fully re-sync all information when reopening app or with swipe-down gesture. The swipe-down gesture now essentially restarts the core functions of the app. Other changes: Added 5G-NR band to notification pulldown title. Added accent colors for additional wireless providers. Added option to disable street address geocoding when editing a site note; coordinates will populate instead. Code optimizations and enhancements. Improved identification of unregistered 5G-NR cells. Improved LTE PLMN identification on some devices. Resolved issue with log import proceeding when log backup fails. Resolved issue with some 5G-NR connections displaying improper band. Resolved issue with some 5G-NR neighbor cells displaying improper band. Updated internal libraries. As always, I appreciate everyone's support. Dual SIM bugs are *still* being ironed out but it is a priority to resolve. Thanks!
  • Recently Browsing

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