Verizon Marshmallow Incoming Today 2/16

I don't have the G4 but I have the G3. I'm just totally PO'd that Miracast no longer works after upgrading. My Blu-Ray sees the device, and vice-versa, but the connection is never made. Total F-up with this upgrade.....the proverbial "if it ain't broke, don't fix it!!"
 
OK, having had MM for a bit now, and even after a factory data reset and recovery mode cache clear, the battery life is still worse. Not significantly so, but noticeable.
 
Went back to LP using LGUP and stopped future OTA update using the debloater tool. The screen not turning on was too much for me.

Posted via the Android Central App
 
Did anyone's phone get renamed after the update? Mine showed as "Optimus".

I had to get at the Windows app to update my phone to Marshmallow, I wonder if that is the reason it was renamed.

Also, I no longer have the ability to double-tap on the home or lockscreen to turn the display on or off.
 
Welp I went to the Verizon store, only to confirm that my phone was bricked by the update. So they are sending me a replacement. The takeaway is that unfortunately, once again upgrade at risk to your phone malfunctioning.
 
Welp I went to the Verizon store, only to confirm that my phone was bricked by the update. So they are sending me a replacement. The takeaway is that unfortunately, once again upgrade at risk to your phone malfunctioning.

It's possible that the increased heat of the update process (my G4 got pretty warm and I assume most got warmer than normal) accelerated the bootloop hardware failure. Since heat expanding the defective solders is apparently the issue causing the bootloops.

Point being, it may be a hardware failure and not the software update, given the major known issue and your description of your own G4.
 
It's possible that the increased heat of the update process (my G4 got pretty warm and I assume most got warmer than normal) accelerated the bootloop hardware failure. Since heat expanding the defective solders is apparently the issue causing the bootloops.

Point being, it may be a hardware failure and not the software update, given the major known issue and your description of your own G4.

Is there a way to avoid the update on a Verizon LG G4?
 
I know this has been discussed before, but can't find the thread. Does anyone recall which network mode setting is best for battery life? My Verizon G4 with MM is set to "Global". Am I better off with "LTE/CDMA" from a battery savings perspective? Thanks
 
If you haven't already done so, do not do this update. The update causes a failure in the phone and renders it a nice looking paper weight.

Verizon is shipping me a replacement phone over night.
 
I know this has been discussed before, but can't find the thread. Does anyone recall which network mode setting is best for battery life? My Verizon G4 with MM is set to "Global". Am I better off with "LTE/CDMA" from a battery savings perspective? Thanks

I'm the US the LTE/cdma setting
 
If you haven't already done so, do not do this update. The update causes a failure in the phone and renders it a nice looking paper weight.

Verizon is shipping me a replacement phone over night.

It's not the update, it's a hardware defect causing the phones to boot loop. There's no warning, it just suddenly starts rebooting over and over.
 
So, I installed Marshmallow and cleared my cache. That pesky little 4G icon is still lit up but seems to be making no difference with power or data. Doze is excellent. If my phone sits for a little while, the battery graph will flatline and battery life goes way up; I've not seen that before on my G3 or this G4. Everything is working well; no complaints so far.

I finally broke down and installed MM this morning. While poking about the settings for changes, I noticed an option in the developer settings to keep mobile data active while on Wi-Fi. Mine is unchecked, but maybe yours is on? I haven't been on Wi-Fi yet since finding this, so not sure if it's what you need to look for.
 

Attachments

  • 1456269100400.jpg
    1456269100400.jpg
    69.3 KB · Views: 39
It's possible that the increased heat of the update process (my G4 got pretty warm and I assume most got warmer than normal) accelerated the bootloop hardware failure. Since heat expanding the defective solders is apparently the issue causing the bootloops.

Point being, it may be a hardware failure and not the software update, given the major known issue and your description of your own G4.

Unfortunately I didn't see anything about this boot-loop iissue until after I did the update. Either way, it was the software update that caused the hardware failure. Verizon overnighted a new G4 to me, so I'll see how that goes.
 
I finally broke down and installed MM this morning. While poking about the settings for changes, I noticed an option in the developer settings to keep mobile data active while on Wi-Fi. Mine is unchecked, but maybe yours is on? I haven't been on Wi-Fi yet since finding this, so not sure if it's what you need to look for.

Checked that setting on mine, it's not checked either. Strange. Oh well.
 
Unfortunately I didn't see anything about this boot-loop iissue until after I did the update. Either way, it was the software update that caused the hardware failure. Verizon overnighted a new G4 to me, so I'll see how that goes.

I think you may be missing my larger point. Yes, the update may be what triggered things, but the increased heat (which doesn't require a software update) may well be what caused the hardware issue to kick in. My point being, if that's the case, it was only a matter of time, even if you had never taken the MM update.

Given the known issue with the G4, people shouldn't assume that the software is what is "causing" a bootloop or inability to boot issue. That's the zebra in this looking-for-horses-instead-of-zebras situation.