Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

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

I have had the B26 CSFB issue on my home site for 1 month now on 4.4.2 / .23 radio. So for about 1 month I have been on 3G 99.8% of the time when at home.

I do not have any problems with B25/B26 on 3 other sites.

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.

 

Interesting theory.. certainly seems plausible to me, and would explain why some of us are experiencing more of a problem than others. If you are correct, then I would expect the problem to disappear when disabling Band 26. I just did that to see if it changes anything.. I'll keep an eye on it.

 

-Mike

  • Like 1
Link to comment
Share on other sites

It's not a theory that what's kinda happening. I been had b26 enabled on my phone way before this update so I been seeing it. Some newly activated b26 sites don't get the ecsfb patch so if you connect to it the radio throws you off it because your phone won't be able to make calls while connected to that tower. It's completely random why some towers get the patch and some don't. That's all up to the vendors reasoning which is pretty unknown.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Interesting theory.. certainly seems plausible to me, and would explain why some of us are experiencing more of a problem than others. If you are correct, then I would expect the problem to disappear when disabling Band 26. I just did that to see if it changes anything.. I'll keep an eye on it.

 

-Mike

I believe someone in the Tampa thread had the same assertion and disabling B26 worked wonders for him.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

My m8 picks up 4 band 41 sites on the way to work, this new radio on the n5 picked up 0. :/

 

Sent from my Nexus 5 using Tapatalk

The stock scan priority is 25-26-41. You can change that if you want.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

The stock scan priority is 25-26-41. You can change that if you want.

 

Sent from my Nexus 5 using Tapatalk

Of course I changed it. That shouldn't matter, though. Band 41 is a network top priority, and should automatically switch you over no matter what your initial scan priority is.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

My m8 picks up 4 band 41 sites on the way to work, this new radio on the n5 picked up 0. :/

 

Sent from my Nexus 5 using Tapatalk

Were you camped on 25/26 LTE or 3G?

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites

Were you camped on 25/26 LTE or 3G?

 

Sent from my Nexus 7 using Tapatalk

25 and 3g. I've noticed that 3g drop you all have been speaking of. Meh.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

25 and 3g. I've noticed that 3g drop you all have been speaking of. Meh.

 

Sent from my Nexus 5 using Tapatalk

It could have just been the scan times not lining up. When on 3G the phone only scans for LTE every so often, so when it scanned for b41 you may have not been in range. I bet if you toggled airplane mode near the towers you know are B41 you would get it.

 

Sent from my Nexus 7 using Tapatalk

Link to comment
Share on other sites

Interesting theory.. certainly seems plausible to me, and would explain why some of us are experiencing more of a problem than others. If you are correct, then I would expect the problem to disappear when disabling Band 26. I just did that to see if it changes anything.. I'll keep an eye on it.

 

-Mike

 

Oh, good idea. Trying that now...

Link to comment
Share on other sites

Anybody else have bad priority looking like this on 4.4.3? I have priority set to 25 - 0, 26 - 1 and 41 - 0. I swear when I set priority on 4.4.2 I had 1- 3.

ybuje4ug.jpg

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Did you run a profile update? It changes if you do it. Also if you just view isn't of edit I think it shows 1-3.

 

Sent from my Nexus 5 using Tapatalk

I did a profile update before but to make sure I did it again and my priority doesn't change.  When I was on 1.13 briefly yesterday and again today I noticed that the priority did show 1-3.  Can anyone else confirm priority 0-2 for .15?

Link to comment
Share on other sites

Got the update around 4:30 this afternoon. To beat from work to bother going to the nearest location with LTE to test it, but 3G and 1x numbers look about the same...

Link to comment
Share on other sites

I changed global to lte and now this phone grabs 41 the same or better than my g2 or m8. I guess I'm happy. Don't know what changed but I back tracked the route when I didn't get 41, did a profile update and changed to LTE. Fixed. We'll see how b26 works

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Update arrived this afternoon from stock 4.4.2(bb.23) to 4.4.3(bb.13) it seems largely invisible to me. No obvious change in RF performance on B25. Still no luck connecting to B41, toggled in and out of airplane mode and rebooted within 1/4mile of B41 site. B26 is not here yet so i can't comment.  

Link to comment
Share on other sites

So I know it is crazy but has anyone seen a mod for a multi-window like experience. I do wish I could keep 2 apps going like I did on my s4.

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