mrrogers1

Damn.... ok, bout to try and get the crappy PRL. FOR SCIENCE!

That is good news! My buddy tried a couple times and it stayed. I'll tell him to try a few more times. Thanks! **Has anyone got Digibur the PRL yet?? Sent from my LG-LS980 using Tapatalk

Was on 55016 before update, phone has Z8 software (it may not matter but can't hurt to supply info). I should add, the phone is no more than 300 yards from the nearest 3G/800/4G accepted tower that it typically connects to 800 and 4G and on this PRL, cannot connected to 4G at all and the 3G connection is pretty ugly AND can't get it to connect to the 800 coming off of the tower either.

60657 was the *latest PRL released. I was on 55016 two days ago, updated early yesterday to 55017 and unable to get to 60657 BUT updated my buddy from 55016 straight to 60657. UPDATE: My buddy is telling me he can't even connect to data.... I'm going to try and work with him to verify *exactly what his data situation is. It sure he's technical enough to pull the PRL but will try my best. Sent from my LG-LS980 using Tapatalk

Oh noez... I don't have access to the phone that got it but I'll check with my buddy and see if he has been able to connect to LTE this morning. I noticed that he didn't connect back to the LTE tower we were on immediately after the update but he and I parted ways right after. I wonder what is going on here.... Maybe I'll keep trying to update here, take one for the team if I can get it to update. Sent from my LG-LS980 using Tapatalk

Are you on updated or original software and are you saying it "no longer" holds on to signals that long after PRL update? Are you on updated or original software? Sent from my LG-LS980 using Tapatalk

Current (from what I have seen today) is 55017. You saying you got that 60657 today? I got 55017 today. EDIT! Just updated my buddies phone, who has the software update on his G2 and yes, I see, PRL just went from 55016 to 60657. Interestingly enough, I do not have the software update yet and no amounts of PRL updates will bump me up past 55017. Sent from my LG-LS980 using Tapatalk

Um.... yeah, the EVO LTE is a dog of dogs when it comes to RF performance... the worst name for a device that had such troubles with LTE. Lol I did have EVO LTE and my wife currently uses a EVO LTE and side by side, my HTC One and the LTE, One was much better than the EVO LTE and my G2 is even better (in my comparisons) than the One. I don't know why or what device people came from (maybe they had Note 2's or something) that the G2 isn't performing up to standards but real world, the G2 has been great and definitely a HUGE step up from the EVO LTE.

I don't think we'll ever see the PRL and Profile Update working BUT I could be wrong... Maybe it's just HTC devices (as I have been on them for the last 6yr or so) but CM has never supported that functionality. Would be awfully nice to see it working but not getting hopes up here, unless LG may handle it totally different.

You aren't the only one with wife and multiple kids round here. If and when you want to learn, it's at your own pace, just look around and you will find it.

Eh.... then there is adb devices, adb reboot bootloader, adb reboot recovery, toss in a little fastboot flash recovery recovery.img. It's the internet man, head over to XDA, what you want to know and learn can be found and followed. Since you have Sprint LG G2, start here and go from there >>>>>>>> http://forum.xda-developers.com/lg-g2/sprint

The modems in the thread I posted are flashable through recovery.

I don't know for sure BUT it most likely has to do with your root situation, all stock or not. (*Is your Recovery stock also??) I'd just say install one of the 2 options posted today and profit.

Are you rooted or anything?

I can't say if there is anything else in there worth getting but I know recovery and some other things are in there. Subscribe to that modem thread though, seems to be kept updated pretty well. I think the Dev section for us on XDA is going to be the most useful since the general is general for all (which sucks). We have more pertinent information in here so at least you're in the right place.

http://forum.xda-developers.com/showthread.php?t=2451426

Doubtful that it'll was anything with Spark BUT we know, they don't usually tell use "everything" that is updated so i'm sure it's more than sound and security.

Screen shot of system info please and thank you.

I think root permissions may be required to do this on API 17+

I can tell you, for a fact, the internal memo for Sprint Management (in Corp stores) went out about an hour after the release date was plastered everywhere the morning of Halloween. The distribution of said materials/training is obviously up to the stores BUT everything they have speaks to the 8th being launch day. It also talks about the Play Store devices and supporting hardware being sent. Stores didn't even get Advocate devices yet, this WAS closely guarded. Not to mention, this is a MUCH different type of device and launch with options that are foreign to many veteran Sprint employees. Sent from my d3rpONE using Tapatalk 4

I think it's about that time... @nexgencpu should do the honors.

Just want to mention that while the Google Play device is "Sprint Compatible" it is not, technically a "Sprint phone". The device you get from Sprint is certainly a "Sprint Phone" and I would bet money that someone who gets a pre-ordered device "from Sprint" early doesn't have MEID issues as it's actually a "Sprint" device and not just one that will undoubtedly work on the network (eg. LG G2). They were wrong (but lets be honest, more misinformed as part of the cascading of information has not made it to all channels for the unreleased device) Folks need to just be patient, this is VERY new waters for Sprint and people freaking out on Agents of the Sprint "Machine" about SIM's and id's not in the system before the device has even launched is NOT helping. Owell, it'll all work itself out, for sure, in due time...

Update is what has been communicated officially but who knows...

THEY ARE DUMB AND WRONG.

Just to keep this visible...