Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

Also got a forced PRL update overnight. Woke up to find the screen just sitting on, which is somewhat annoying; who knows how long ago it happened.

 

What is the deal with these forced updates?

Link to comment
Share on other sites

Just had another forced prl/profile update.

Also got a forced PRL update overnight. Woke up to find the screen just sitting on, which is somewhat annoying; who knows how long ago it happened.

 

What is the deal with these forced updates?

Same here keeps changing my scan priorities.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Just had another forced prl/profile update.

since 4.4.4. My phone barely gets on ehrpd just 1x or unstable lte.

I had the phone camp on 3g too until I went back to the 0.15 radio.

 

I also got another prl update today.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Forced prl update overnight for me as well.

 

Sent from my Nexus 5 using Tapatalk

 

Same here...  Second time in about a week.  They sure don't want me to keep the custom 513 PRL. 

 

Oh well, I have it backed up in my EFS backup in TWRP.  :D

  • Like 1
Link to comment
Share on other sites

Mine force updated but didn't change..

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Same here... Second time in about a week. They sure don't want me to keep the custom 513 PRL.

 

Oh well, I have it backed up in my EFS backup in TWRP. :D

So once I've reinstalled the 513, if I backup the EFS , then if (and when?) it automatically updates, all I have to do is restore my EFS backup and the PRL will come along for the ride? No ADB on the computer to restore the goodness that is 513?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

So once I've reinstalled the 513, if I backup the EFS , then if (and when?) it automatically updates, all I have to do is restore my EFS backup and the PRL will come along for the ride? No ADB on the computer to restore the goodness that is 513?

 

Sent from my Nexus 5 using Tapatalk

 

Yeah, just restore the EFS backup in TWRP or whatever recovery you use.  I've done it numerous times.  Really nice to not have to go through the whole process for the PRLs on the N5.

  • Like 1
Link to comment
Share on other sites

Mine force updated but didn't change..

 

Sent from my Nexus 5 using Tapatalk

Yes!  I awoke this morning and saw the message saying my PRL had changed, but it's still the same number as before (55019).  However, on my way to work this morning, my phone bounced from Band 26 to eHRPD, but then bounced straight back to Band 41 down the street from my office!  Maybe Sprint is working out some network issues; I'm still loving my expanded LTE coverage since 4.4.3 came out, and I've never flashed any different radios (running .16 like a BOSS!!).

 

J.

Link to comment
Share on other sites

Yes! I awoke this morning and saw the message saying my PRL had changed, but it's still the same number as before (55019). However, on my way to work this morning, my phone bounced from Band 26 to eHRPD, but then bounced straight back to Band 41 down the street from my office! Maybe Sprint is working out some network issues; I'm still loving my expanded LTE coverage since 4.4.3 came out, and I've never flashed any different radios (running .16 like a BOSS!!).

 

J.

Well I'm back to .15, I was on the new radio then my phone decided to lose signal and had an option in settings for chose your carrier (dafaq is that?) and wouldn't pick up sprint signal again until I flashed between 2.16 and .15 twice (ending up on .15). The funny thing is that when my phone did pick up a signal it was a -82dbm ehrphd signal. So its not like it was a super fringe signal or anything..

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

I'd be sure do a proper backup before flashing the new image.  Just in case you need to return to 4.4.4 because of bugs.

 

Yeah, I took care of that yesterday.  Waiting for initial reviews on XDA before going too far.  I'll probably start with the radio and see how that holds up in the meantime.

  • Like 1
Link to comment
Share on other sites

how will the L preview release be updated from now to OTA/RTM? new images? 

 

If they do release updates to Android L between now and official release it will most likely (almost definitely) be in the form of new images.

Link to comment
Share on other sites

don't forget to backup your userdata if you flash the pre-release images, it is very unlikely you will be able to simply flash the system back to 4.4.4 without having a backup of 4.4.4 data (or resetting data).

Link to comment
Share on other sites

Do I have to be rooted to fash to a different radio?

 

No.

 

You must be bootloader unlocked (which deletes all data when you unlock it if you have not already).

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

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their BRS/EBS licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well.  — — — — — Edit: Turns out this is a spectrum swap where T-Mobile is basically giving them DoD spectrum in a bunch of markets in exchange for all of SoniqWave's BRS/EBS. SoniqWave will likely turn around and sell the DoD spectrum to AT&T whenever the FCC removes the 40MHz cap.
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

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