Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

My device out of the blue just lit up and did a profile update followed by a prl update. Never seen a profile update get initiated by the network like that before. Is it normal and I have just never seen it happen?

The exact same thing just happened to me. Force updated PRL and profile. We'll see if this changes anything.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

It messed with my band priorities.

25-0

26-3

41-1

They were previously at 41-1 25-2 26-5.

And it put me in Global LTE/GSM/CDMA instead of LTE Reccomended LTE/CDMA.

Link to comment
Share on other sites

Add me to the list. Maybe they fixed LTE scanning from 26 -> 3G instead of checking 25?

 

My band priorities are still the same at 25 -> 26 -> 41

 

Ooo very interesting it threw me to LTE/GSM/CDMA (auto).

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Add me to the list. Maybe they fixed LTE scanning from 26 -> 3G instead of checking 25?

 

My band priorities are still the same at 25 -> 26 -> 41

 

Sent from my Nexus 5 using Tapatalk

If they did, that would be huge.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Add me to the list. Maybe they fixed LTE scanning from 26 -> 3G instead of checking 25?

 

My band priorities are still the same at 25 -> 26 -> 41

 

Ooo very interesting it threw me to LTE/GSM/CDMA (auto).

Sent from my Nexus 5 using Tapatalk

 

Would any of those parameters be within the profile and not so much the radio software?

Link to comment
Share on other sites

I think it was sent to everyone. Changed my priorities.

 

I did have:

B25: 0

B26: 1

B41: 1

Now they're all listed as 1 (under edit)

 

Under view its

B25: 0, B26:2, B41:1

 

Sent from my Nexus 5

 

That is the default values that came with the new .13 radio so i dont think any of that changed.

Link to comment
Share on other sites

That is the default values that came with the new .13 radio so i dont think any of that changed.

My .13 radio has 25 at 1, 26 at 2 and 41 at 3. Under edit, every band is set to 1.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

My .13 radio has 25 at 1, 26 at 2 and 41 at 3. Under edit, every band is set to 1.

 

Sent from my Nexus 5 using Tapatalk

 

Sorry, thats what i meant as the default values for .13.  The only radio that I saw that had a 0 for a value when viewing priority is the .15 radio.  That one used 0 1 2 versus 1 2 3 like the others.

Link to comment
Share on other sites

That is the default values that came with the new .13 radio so i dont think any of that changed.

Sorry, thats what i meant as the default values for .13. The only radio that I saw that had a 0 for a value when viewing priority is the .15 radio. That one used 0 1 2 versus 1 2 3 like the others.

I'm still on the .15 radio. The values did change for be. I had B25 set at 0, now its set to 1 under the edit menu.

 

Sent from my Nexus 5

Link to comment
Share on other sites

They change my priorities on my LTE scan back to default too. I changed them back, needless to say.

 

 

Sent from Josh's iPhone 5S using Tapatalk 2

Link to comment
Share on other sites

My device out of the blue just lit up and did a profile update followed by a prl update.  Never seen a profile update get initiated by the network like that before.  Is it normal and I have just never seen it happen?

 

Yep, I can corroborate that.  I was in the car and thought that I had initiated an update with some sort of accidental touchscreen mash.  But I caught it and hit cancel.

 

AJ

Link to comment
Share on other sites

Add me to the list of folks who got the force-update. Looks like my phone isn't camping on B26 quite as much, though I did go in and re-prioritize LTE bands just now so that 26 is at the bottom where it should be...since the 4.4.3 upgrade I've been on B26 more often than not.

Link to comment
Share on other sites

My .13 radio has 25 at 1, 26 at 2 and 41 at 3. Under edit, every band is set to 1.

 

Sent from my Nexus 5 using Tapatalk

I also got the update and was on the gold old .15 radio.  I decided to put the new .13 radio back on to see if anything has changed as I will test it out by driving around later.  My band settings are the same as oldblue910 and it appears that my dBm reading are almost in par with the .15 radio, where before they were reading a lot higher.  It might be because I was adjusting my CPU setting with the Franco kernel at the same time, but I will have to go out and test this and see if it fixes where I would drop to 3G and stay there.  I am just hopeful that maybe this push was Sprint engineers saying they have fixed the issues we have been seeing with this new radio and their towers.

  • Like 1
Link to comment
Share on other sites

I canceled the update too. I can thank being on fringe 3g for giving me enough time to catch it. I'm going to wait for more observations/information before I initiate manually.

 

Sent from my Nexus 5 using Tapatalk

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