ericdabbs

I presume you were able to connect to this tower on LTE before? The Spark update only allows you to connect to B26 and B41 on the device side but if the NV sites in your area are still affected by the eCSFB issue then the Spark update alone is not enough.

Yeah i got that and I responded to your PM.

Mike...do you need any more data points? I finally got the Spark update on my device and connected to 2 known B41 LTE sites. I got information where Signalcheck displays 310120 and the LTE engineering menus for the PLMN display 311490 at both B41 LTE sites I was connected to. I am in the Los Angeles area so I am not sure if these MCC-MNC numbers are region specific.

Finally upgraded to Spark update last night after having to flash back to stock ZV8. I set the Band priority to 41>25>26. It works nice so far and I am able to connect to B41 with ease. Still not sure what the LTE scan timer is for the device since the option is not there but it doesn't seem like a 5 minute or interval as assumed like in Samsung and HTC devices. It seemed to connect to quicker at least to B41 LTE sites but I am not sure if this is because the B41 priority is set to highest.

Yes I am rooted. Sorry I misread the dilemma.

What do you mean you don't have a /cache/fota folder? Do you have root explorer or a file manager. I see the /cache/fota folder.

OMG...LG still hasn't fixed the spelling of "priority". Priority has been mispelled since ZV7 firmware.

Dem Spark icons!!!!

For those that are curious, root access has been fixed on the ZVA firmware. Please see this thread if you are interested. You need to be using ioroot v21. http://forum.xda-developers.com/showthread.php?t=2522346

I thought the idea was that those with the Spark update post screenshots to show that it was displaying the correct LTE MCC-MNC on SignalCheck.

Agreed. For the time being, I am holding off. However the ZVA modem file is available for people to flash in TWRP. I will give that a shot.

PSA: If you care about rooting or flashing custom ROMS, do not take the ZVA firmware OTA at the moment. Root is currently broken and you are not able to flash a custom recovery like TWRP. LG has added a new aboot file and it is affecting the loki exploit. The devs are trying to work on a workaround this issue. EDIT: Root has been restored with ioroot v21. You can find ioroot v21 here http://forum.xda-developers.com/showthread.php?t=2522346

Yeah it is no longer available because Dropbox only allows "X" number of downloads. What people should be uploading it to is through Mediafire or some other 3rd party hosting site.

I use supersu and can do full unroot on my phone. So I assume that you did a full unroot on your phone and then use twrp to sideload the ZVA update?

Can you confirm if the ioroot v20 root method is working assuming your root your phone.

I don't know about BSR timer but a LTE scan timer setting would be nice to be able to change.

If you are stock unrooted why is this a benefit? Is it because you don't have to wait for the servers to prompt you so that you can finally download the Spark update? I am more curious of finding a way to sideload the Spark update while maintain root access.

Any time you mess with LTE bands or priorities, you need to restart your phone. I am surprised when it did the Spanky....errr Spark update that it didn't prompt you to restart your phone. Even when we were able to manually enable B26 or B41 with the ZV7/ZV8 firmware it automatically needed to reboot the phone. Thank goodness its working You scared me a bit there.

Anyone notice any LTE reception improvements with the Spark update and baseband version? Also I assume with the new Spark update that B41 is easily accessible now?

Yes unfortunately Sprint didn't meet their goals.

You would think that Sprint would be trying to encourage folks to join the Framily plan if you are current customers instead of being hard nosed about these things. I don't get that.

I see. Well I think the lesson learned is to always inspect your device fully during the 14 day evaluation period despite if you have other ways that can do the job. The way I look at it is that unless I have phone insurance this will be my device for the next 2 years so I would sacrifice using any other devices I was relying on temporarily and be damn sure this device is not faulty. I sure as heck am not waiting a month later to test out whether my GPS, Bluetooth, Wifi, 3G/4G data, NFC, phone calling, voice/data reception, etc are working or not. Like the GPS issue, I understand you car has a built navigation system but you could have verified it by maybe launching the Google Maps/Navigation app and letting it route you to work or whereever you were going in the background just to test out the GPS functionality. I can't comment on the RF issues you were having but I feel the GPS issue could have been easily discovered and should have been resolved during your 14 day period.

Why haven't you tried to get LG to replace the device or even exchange your device within your first 14 days? Having a faulty device and comparing it to another device is not an apples to apples comparison.

Has anyone try to manually update their phone yet to see if the Spark update is available?

First of all, the G2 got released later than normal not because it had issues with LTE. It was Sprint's own stupid reason to time everything to make Nov 8 some crazy significant date to announce the release of several Spark devices. This was confirmed by a LG representative that said that LG wanted Sprint to sell the G2 sooner but it was Sprint who was purposely holding back the release. About the G2 radios, who gives a crap what the N5 and G2 use. They are both different devices and even if they use the same radios and what not the shape and design of the phone can have some impact on RF performance. I think instead of asking a million questions about why the G2 is what it is currently with LTE reception, lets just wait for the Spark update to see if any of these issues get resolved. We already know that there is a new baseband version in the Spark update based on the latest leak of the ZVA firmware. Lets just be patient and see what happens. I am sure LG and Sprint are aware of the situation. When the audio issue was prominent in ZV7 firmware, Sprint fixed the audio issue in ZV8 firmware so I know Sprint listens.