Fix weak LTE connection in ZVD firmware

I haven't tracked the results in detail, but compared to pre-ZVD update, I'm not staying on LTE as consistently as I used to. Maybe I'm the exception. :'(
 
This seems to have worked for me, I just did it a couple hrs ago but haven't bounced off LTE and I've been in an area I know normally kicks me to 3g

Posted via the Android Central App
 
I am wondering about doing this procedure to help my LTE connection, has anyone had any unintended consequences or problems after doing this?

Thank you,
Ken
 
Rocket321,

This sounds good. I got on Chat (after many tries--Sprint's chat is usually not available) and was given a six-digit number when I asked for my MSL.

When I entered ##xxxxxx## I got a menu that says:

Service Program
View
View MDN, MSID

Edit

Done

No sign of LTE. This is a Sprint LG G2. Am I misunderstanding the instructions?

Also, how do I know whether I have the ZVD update? I assume I do, because I've checked and downloaded all updates, but is there a way to check?
 
Rocket321,

This sounds good. I got on Chat (after many tries--Sprint's chat is usually not available) and was given a six-digit number when I asked for my MSL.

When I entered ##xxxxxx## I got a menu that says:

Service Program
View
View MDN, MSID

Edit

Done

No sign of LTE. This is a Sprint LG G2. Am I misunderstanding the instructions?

Also, how do I know whether I have the ZVD update? I assume I do, because I've checked and downloaded all updates, but is there a way to check?
Wrong code. The dialer code for LTE is ##data# (3282)

Then click LTE > edit > enter msl and you're good


As far as your question about checking your current version.

Settings > about phone > software information
 
Doh to both. Thanks. I took "data" to mean the MSL, not the literal "data"!

And yes, "Software version" says LS980ZVD.

Happy Monday, now to see whether it helps.

Interesting: when I went to change BSRTimer, it showed 3000 but when I selected it, 3 was entered as the value, i.e., as if that was the current setting. I cancelled out to be sure, and it did indeed say 3000, then 3 again when I selected it. I saved it as 3, rebooted, and now it shows 3 in both places. Makes ya wonder--does something think it *should* be 3 (besides the posts here!)? Of course I'll never know, now that I've set it to 3. Kind of reminds me of the chronic Windows bug (which, hmm, I haven't seen in a while, but saw repeatedly for at least a decade) where some dialog setting shows one value, but behavior suggests it's another, and the fix is to set it to the other and back to the alleged current setting.

Anyway, thanks to y'all's info, I have set it and can now reset it if I think that was Bad (not expecting that, of course, but it's always good to know how to get back where you were).
 
Well, I guess I'll never know: I got that update the day after I made the change, so while it *seems* somewhat better, I can't tell which change fixed it! I suppose I could change BSRTimer back, but that seems counterproductive.
 
Some hardware has ack timings hardcoded into the architecture, it allows you to change settings but only within allowed parameters, if it gets a request outside those parameters it just defaults to its own settings.