• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Beware of Lollipop with Nexus4

LarryM2

LarryM2

Lurker
Yesterday I made the mistake of accepting the OTA update to Lollipop. Now my trusty Nexus4 has no WiFi capability. WiFi will only stay on less than a minute and finds NO networks available. In my geeky neighborhood there are a minimum of 15 WiFi networks at any given time. From the Google Forums, this has been a known issue for at least two weeks, yet Google still rolled out yesterday's OTA update. The Google reps are giving useless advice, e.g., "Forget a network and re-add it". Perhaps that might work if any networks were detected at all. "Toggle in and out of Airplane mode." Again, useless. I'm a bit stunned in that Google has in the past been much more responsible with these updates. Save yourself the headache of a factory reset by avoiding this update.
 
I think it's got something to do with what's been cached and the switch to ART from Dalvik. If you've got a custom recovery installed, try wiping the Davlik cache. Or you may have to factory reset to clear it. I never had any luck with OTA's so I flashed my N4 with the factory image of lollipop. No problems with wifi at all.
 
Unfortunately that does kind of seem to be the pattern. Some who installed the OTA have problems, while those who installed via the factory image do not. I'm in that second category. I installed the factory Lollipop image after doing a full wipe and my N4 hasn't had any issues.

I hate to say it, but you'll probably need to do a factory reset to get things running smoothly again.
 
I just downloaded and installed the OTA (LRX21T) on my Nexus 4, with no difficulty at all.

It sees my WiFi, and one neighbor's as well.
 
RCG said:
I just downloaded and installed the OTA (LRX21T) on my Nexus 4, with no difficulty at all.

It sees my WiFi, and one neighbor's as well.
Click to expand...
were you rooted with a custom recovery? It might be there are fewer issues with stock.
 
RCG said:
Completely stock, I have learned the hard way, over the years, to keep my fingers out of things.
Click to expand...

Yeah. My guess is that the OTA wants to use stock recovery and when it finds something else it tries rather unsuccessfully to use that and ends up with issues or moves to bootloopland.
 
lunatic59 said:
Yeah. My guess is that the OTA wants to use stock recovery and when it finds something else it tries rather unsuccessfully to use that and ends up with issues or moves to bootloopland.
Click to expand...

I had that problem...had to remove SuperSU & Xposed then go back to stock recovery, boot screen, radio...radio gave me the bootloop. Had to flash the Lollipop image with Wugs.
 
You must log in or register to reply here.
Back
Top Bottom