Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

After a few days of driving around the Springs, I am having little to no issue with the .13 radio. Granted, both B25 and B26 signals are a bit weaker (no B41 around here to test) but based on my highly unscientific observations, it seems that when it falls back to 3G, it's for a valid reason - the LTE signal is poor enough that it's no faster (or even slower) than 3G.

 

I haven't experienced any fallbacks to 3G when the LTE signal is strong though which seems to be one of the primary complaints I'm reading from most of you. So based on my experience, I'm going to side with Robert's assessment of a network side issue and that the Springs is a mature enough LTE market that there are no fixes necessary in this area. Hopefully Sprint is aware of and actively working towards whatever network-based changes are necessary to fix the issues most of you are experiencing.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

I am still waiting for the OTA. I am unlocked but stock everything. I have been checking every hour. Ironically my wife is completely stock and could not care less about the update. She got it yesterday. Figures.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

I am still waiting for the OTA. I am unlocked but stock everything. I have been checking every hour. Ironically my wife is completely stock and could not care less about the update. She got it yesterday. Figures.

Save your thumb and don't bother hitting the update button all day.. Google distributes the OTAs randomly, and checking for updates multiple times per day does not change your place in line. You have to be patient or sideload it yourself.

 

-Mike

  • Like 1
Link to comment
Share on other sites

I am still waiting for the OTA. I am unlocked but stock everything. I have been checking every hour. Ironically my wife is completely stock and could not care less about the update. She got it yesterday. Figures.

 

Sent from my Nexus 5 using Tapatalk

This sums up life in general.  : o )

Link to comment
Share on other sites

After a few days of driving around the Springs, I am having little to no issue with the .13 radio. Granted, both B25 and B26 signals are a bit weaker (no B41 around here to test) but based on my highly unscientific observations, it seems that when it falls back to 3G, it's for a valid reason - the LTE signal is poor enough that it's no faster (or even slower) than 3G.

 

I haven't experienced any fallbacks to 3G when the LTE signal is strong though which seems to be one of the primary complaints I'm reading from most of you. So based on my experience, I'm going to side with Robert's assessment of a network side issue and that the Springs is a mature enough LTE market that there are no fixes necessary in this area. Hopefully Sprint is aware of and actively working towards whatever network-based changes are necessary to fix the issues most of you are experiencing.

 

Sent from my Nexus 5 using Tapatalk

In my experience, this applying to all carriers and not just Sprint, there are too many people that are focused on what network indicator they are getting on the phone and too few that focus on the actual network throughput and performance.

 

My kingdom for people who just focus on user experience. I must admit, my kingdom isn't a lot. ;)

  • Like 3
Link to comment
Share on other sites

In my experience, this applying to all carriers and not just Sprint, there are too many people that are focused on what network indicator they are getting on the phone and too few that focus on the actual network throughput and performance.

 

My kingdom for people who just focus on user experience. I must admit, my kingdom isn't a lot. ;)

 

I agree...well, to a point.  I've speed tested and just generally browsed on the .13 radio, and at no point did the 3G it wants to constantly sit in hold a candle to even a weak LTE signal in the same spot.  I know you aren't singling out any particular person, but my user experience is exactly lining up with which network/dBm I'm getting at current.

Link to comment
Share on other sites

I agree...well, to a point. I've speed tested and just generally browsed on the .13 radio, and at no point did the 3G it wants to constantly sit in hold a candle to even a weak LTE signal in the same spot. I know you aren't singling out any particular person, but my user experience is exactly lining up with which network/dBm I'm getting at current.

I concur with this. On .17 I get 14mb LTE on .13 I get .4-.5mb 3g.

 

Sent from my Nexus 5 using Tapatalk

  • Like 2
Link to comment
Share on other sites

I am waiting on the OTA.

 

Can anyone with the update tell me if the update fixes the problem where the phone does not ring on incoming calls?

 

Just yesterday my N5 showed I had 2 bars and was displaying LTE. I dial myself, LTE turns into "R" and the phone does not ring. Missed 2 calls yesterday because of this bug.

Link to comment
Share on other sites

I am waiting on the OTA.

 

Can anyone with the update tell me if the update fixes the problem where the phone does not ring on incoming calls?

 

Just yesterday my N5 showed I had 2 bars and was displaying LTE. I dial myself, LTE turns into "R" and the phone does not ring. Missed 2 calls yesterday because of this bug.

No, mine doesn't ring in certain areas of town when on LTE. I've had my phone replaced and it still does it.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

If I disable b26 and b41 completely .13 connects fine to b25 even if I have b25 as top priority it tries to force me to b26 and dies.

 

Sent from my Nexus 5 using Tapatalk

 

We have ecsfb issues here in the MO market still with B26 so .13 is doing it job for you.

Link to comment
Share on other sites

If I disable b26 and b41 completely .13 connects fine to b25 even if I have b25 as top priority it tries to force me to b26 and dies.

 

Sent from my Nexus 5 using Tapatalk

 

That seems to be my problem. I am on Band 25, and have been for quite a while. Then, I see my phone trying to connect to Band 26, then Band 41 in rapid succession, and then disconnect and connect to 3G, and sit there for hours. This only happens on a few towers downtown. This does appear to be a ecsfb issue.

Link to comment
Share on other sites

The .13 modem is better than expected. Today I had to run errands all around the local Court house. Lots of elevators and basements. Not only did my N5 hold a call going down an elevator into the basement, I never went below 3g in the basement. A speed test ran at 1/1mb. Before .13 I could not get 3G in that basement. Today I did not lose it.

Edited by goodfellaslxa
  • Like 3
Link to comment
Share on other sites

Download Google voice and set it up to use for voicemail (you don't need a gv #). Then there a check box within gv that says "view and display voice mails from the phone call log". Now you can get VM notifications and listen to your VM without ever opening up gv.

 

Sent from my Nexus 5 using Tapatalk

Works like a champ

Link to comment
Share on other sites

After watching my phone's behavior on .13, I think I have a theory as to what is going on with the radio, and it has to do with ecfsb and Band 26 (and possibly Band 41). I believe what is happening is that our phones connect fine to Band 25, which doesn't have a csfb problem.  However, in scanning other bands and measuring capacity, it switches over to Band 26, either after a few minutes, or 30 minutes. When trying to connect to Band 26, it encounters the csfb problem with that particular band, and goes to 3G and stays there, which is consistent with what I've seen with csfb issues on Band 25.

 

This would explain why we don't see the "3g camping" on .15, the radio that is much more tolerant of csfb issues. This would also explain why we didn't see the issue on .23, which never could connect to Band 26. 

 

This would further explain why the "3g camping" is sporadic and not that predictable, because it only occurs when the phone attempts to connect to Band 26 after measuring capacity.

 

EDIT: this would also explain why some folks who used to have the problem, are not having the problem any more, because Sprint has fixed the csfb issue.

 

Am I way off base?

 

Also, and perhaps this is a question for the csfb thread, but does Sprint have a way of detecting csfb problems other than manually testing every tower? Or do I need to alert Sprint to my problems? (of course a low level CSR will have no idea what the problem is).

  • Like 2
Link to comment
Share on other sites

After watching my phone's behavior on .13, I think I have a theory as to what is going on with the radio, and it has to do with ecfsb and Band 26 (and possibly Band 41). I believe what is happening is that our phones connect fine to Band 25, which doesn't have a csfb problem. However, in scanning other bands and measuring capacity, it switches over to Band 26, either after a few minutes, or 30 minutes. When trying to connect to Band 26, it encounters the csfb problem with that particular band, and goes to 3G and stays there, which is consistent with what I've seen with csfb issues on Band 25.

 

This would explain why we don't see the "3g camping" on .15, the radio that is much more tolerant of csfb issues. This would also explain why we didn't see the issue on .23, which never could connect to Band 26.

 

This would further explain why the "3g camping" is sporadic and not that predictable, because it only occurs when the phone attempts to connect to Band 26 after measuring capacity.

That might make sense but I'm having all the same radio connectivity issues others are reporting and Syracuse has no band 26 broadcasting at all.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

That might make sense but I'm having all the same radio connectivity issues others are reporting and Syracuse has no band 26 broadcasting at all.

 

Sent from my Nexus 5 using Tapatalk

 

Any Band 41?

Link to comment
Share on other sites

Just got hit on my N5 and my N10 5 minutes later. And as soon as it was done I popped my B41 cherry in my house. And it stayed parked there ever since.

 

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...