Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

I have not seen one person with a Nexus 5 in South Dakota yet, other than in my family. People ask me all the time what I'm using. I caused a near riot in the AT&T store. (OK, that's an exaggeration)

 

Judging by the way AT&T CS has treated you, I would think that, the moment you walked through the door at the AT&T store, lights would flash and alarms would sound.  "Intruder alert!  Unsupported handset!  Unsupported handset!"

 

AJ

  • Like 6
Link to comment
Share on other sites

Well, the Spark update is finally downloading on my Nexus 5. Guess it's time to get my phone turned back on so I can try to find Spark in Visalia.

 

 

Sent from Josh's iPhone 5S using Tapatalk 2

  • Like 1
Link to comment
Share on other sites

Has anyone had this happen? This usually happens on LTE when I connect to a site with ecsfb issues but this happened on 3g.

Woah! Is that an eHRPD connection without a 1x connection!? Or is it just not reporting the radio state properly?

Link to comment
Share on other sites

hepygejy.jpg

 

Has anyone had this happen? This usually happens on LTE when I connect to a site with ecsfb issues but this happened on 3g.

Its happened to me in at least double digit amount of times. Usually when coming from a NV area to a non NV area. Or when transitioning from very faint LTE (where SCP chimes but you never actually see it connect) back down to 3g multiple times in a brief period(like 5ish times in 10-15 seconds).

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Turned my Nexus 5 back on. So far, the LTE isn't that much weaker for me. Later today I'll look for band 41 LTE. Not sure if I'll find it in Visalia or not though.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Are they doing the update by market???

no update for me as of yet

The updates come from Google at random. They are not issued by Sprint, or by market.

 

Robert via Samsung Note 8.0 using Tapatalk Pro

  • Like 1
Link to comment
Share on other sites

Are they doing the update by market???

no update for me as of yet

It's completely random and, I think, based solely on the serial number of your device. Geographical location means nothing.

Link to comment
Share on other sites

I have not seen one person with a Nexus 5 in South Dakota yet, other than in my family. People ask me all the time what I'm using. I caused a near riot in the AT&T store. (OK, that's an exaggeration)

 

Robert via Samsung Note 8.0 using Tapatalk Pro

 

I have not seen anyone else in my lifetime with another N5.  I love this phone and hope that Sprint will include the N6 if it is to exist.   

Link to comment
Share on other sites

Experienced the LTE scan issue today. The phone connected to B25 fine with working eCSFB, then it found B26 and almost immediately dropped to 3G due to lack of eCSFB on 26.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I have not seen anyone else in my lifetime with another N5.

 

That is an odd generalization to make about a handset released only seven months ago.

 

AJ

  • Like 2
Link to comment
Share on other sites

I have not seen anyone else in my lifetime with another N5.

 

And you may find yourself living in a shotgun shack.  And you may find yourself using a Nexus 5...

 

 

AJ

  • Like 2
Link to comment
Share on other sites

That is an odd generalization to make about a handset released only seven months ago.

AJ

Just saying nobody around here (Iowa City) has one that I know. All Samsung phones.

Link to comment
Share on other sites

After spending another day with the update, I'm experiencing the same problems as many others. Most of the time I sit camped on 3G, resetting connection I will hit band 25 LTE and be dropped back to 3G a few minutes later. It feels like Syracuse was 6-8 months ago before they had more than a few towers broadcasting LTE, and definitely not like a launched city. So far it's looking like I'll be going back to one of the older modems but I'll give it to the end of the week.

 

Have you flashed another ROM or are you running stock?

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites

Just saying nobody around here (Iowa City) has one that I know. All Samsung phones.

Here it is samsung, and Apple. I rarely See HTC or LG. Id say 90% of the contract phones are Samsung, or Apple

  • Like 1
Link to comment
Share on other sites

Completely stock for the last few days.

 

Sent from my SM-T217S using Tapatalk

 

Hmm that's a bummer. I'm guessing that whatever issues people are having is related to their market. I've only seen my phone stay on 3g or 1x for at most 10 minutes before switching to LTE and the phone predictably will be on band 25 or 41 at the same locations every time.

 

 

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites

Question: when in a location with known b26 connectivity (but stuck on a nearly unusable 3g connection)...why does doing a PRL update instantly connect me to b26 LTE? Of note.. I have yet to receive the spark update though I know it will come to me in very short order.

Link to comment
Share on other sites

Question: when in a location with known b26 connectivity (but stuck on a nearly unusable 3g connection)...why does doing a PRL update instantly connect me to b26 LTE? Of note.. I have yet to receive the spark update though I know it will come to me in very short order.

PRL update forces a rescan of all channels.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

The new radio is garbage. I can't believe sprint and Google had us wait this long only to release this crap. I was constantly camping on 3g in areas I get good LTE... forced to go back to .15 because of this. Not happy about this update for us. Seems sprint users always get the shaft.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

The new radio is garbage. I can't believe sprint and Google had us wait this long only to release this crap. I was constantly camping on 3g in areas I get good LTE... forced to go back to .15 because of this. Not happy about this update for us. Seems sprint users always get the shaft.

 

Sent from my Nexus 5 using Tapatalk

It's not the radio, it's a bug within the sprint network. My post on the previous page explains what is happening. Also a few pages back someone posted that sprint confirmed this was the case and that network engineers are looking for a solution.

 

I'll reiterate here. This is not the fault of the radio. This is the fault of poor deployment of b26/41 alongside existing b25 with working eCSFB. Here is what I believe happens. The phone scans for LTE and connects to LTE on band 26/41 with broken eCSFB. Since eCSFB is broken/not added, the device falls back to 3G because the network tells it to. The radio is built with completed network upgrades in mind, where all bands have eCSFB. The phone behaves correctly for a properly deployed network. Because of the half-upgraded state of the network, Sprint has to tweak the network side to tell the phone to connect to the band with working eCSFB in the case that it finds a band without it.

 

It also looks like the G2 users are experiencing this http://www.reddit.com/r/Sprint/comments/27kejy/what_is_going_on/

 

More G2 evidence: http://s4gru.com/index.php?/topic/4886-lg-g2-users-thread/page-245&do=findComment&comment=317751

 

Sprint forum thread where the issue is confirmed: https://community.sprint.com/baw/mobile/mobile-access.jspa#jive-discussion?content=https%3A%2F%2Fcommunity.sprint.com%2Fbaw%2Fapi%2Fcore%2Fv2%2Fdiscussions%2F162466

 

Now can we please stop the b****ing about this radio until the network is fixed? I have found that this radio is on par with .15 when the incorrect reporting of signal levels on .15 is taken into account. Throughput on the new radio also seems to be improved across all bands. Once the network side is fixed up I think people will be making a 180 on their thoughts about this radio.

 

Sent from my Nexus 7 using Tapatalk

  • Like 8
Link to comment
Share on other sites

PRL update forces a rescan of all channels.

Sent from my Nexus 5 using Tapatalk

Right but I guess my real question is why the f do I have to do this in order to connect to a perfectly strong and sound b26 signal to begin with? And I think that question may be answered by outstanding ecsfb issues on b26 per several other posts.
Link to comment
Share on other sites

Right but I guess my real question is why the f do I have to do this in order to connect to a perfectly strong and sound b26 signal to begin with? And I think that question may be answered by outstanding ecsfb issues on b26 per several other posts.

Yep that's right, you have to wait for eCSFB on B26 to be fixed, or use the .15 radio and miss calls and texts.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
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

    • 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!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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