Help KitKat update

[mobileminx]

I received the kit Kat update for my nexus 4, which I installed a few days ago. I have to say it's the worst update I've installed. My battery is losing its charge alot faster than usual. the minute I take it off a full charge, it loses 8% without doing anything.

My phone is constantly locking up and rebooting itself.

When the battery is running low, as soon as it reaches about 30%, the phone switches off, with no warning.

Really not impressed. Some of my apps are not working properly.

Please advise when this is going to be fixed

Thank you

 

[SiempreTuna]

Haven't had any of those issues. So far, I haven't noticed any real issues or incompatibilities. There are a couple of things I'm not so keen on but plenty more that are actually kinda cute, if not exactly revolutionary.

There have however, been two builds released - the initial one then a bug fix one. The build I have - KRT16S - is the bug fix one: might be worth checking if that's what you have.

 

[John Bean]

Please advise when this is going to be fixed

No point asking here, you need to ask Google that question.

Think yourself lucky; the 4.4 update turned my Nexus 4 into a paperweight. Fortunately it was still under warranty and Google are replacing it, but to say I'm unimpressed is something of an understatement.

 

[mobileminx]

Thank you for replying to my message.
I have checked my build and I do have the build number KRT16S. I'm noticing more and more problems each day.

My back arrow doesn't want to work on things. I can't always get the keyboard up for typing. Getting more and more frustrated with the phone now.

Thank you

 

[lunatic59]

This isn't a symptom of a bad OS or premature release. Everything described here is symptomatic of having remnants of the previous OS interfering with the update.

At the least, I'd recommend booting into recovery and clearing the cache partition. It still might require a few apps to have their caches cleared as well. Optimally, it would be best to backup ALL your data and then perform a factory reset to make sure that you have a fresh copy of 4.4.

 

[2prevail]

I read an article earlier today that stated that people who installed the OTA while on 4.3 would experience A LOT of bugs where people who were already on KitKat (side loaded the first build) who accepted the OTA were experiencing close to none in bugs. Just a heads up

 

[codesplice]

This isn't a symptom of a bad OS or premature release. Everything described here is symptomatic of having remnants of the previous OS interfering with the update.

To be fair, there have been a lot of bugs reported with the OTA - problems that aren't present in the factory image builds, even those that didn't wipe.

At the least, I'd recommend booting into recovery and clearing the cache partition. It still might require a few apps to have their caches cleared as well. Optimally, it would be best to backup ALL your data and then perform a factory reset to make sure that you have a fresh copy of 4.4.

Maybe some of the steps mentioned in http://androidforums.com/nexus-4/799868-nexus-4-kitkat-update-problem.html will be helpful for you.

 

[Crashdamage]

I did the OTA update on both of our Nexus 4 and a Nexus 7. Didn't clear caches or anything. Zero problems. No doubt 99% or more users have the same trouble-free experience.

 

[codesplice]

I did the OTA update on both of our Nexus 4 and a Nexus 7. Didn't clear caches or anything. Zero problems. No doubt 99% or more users have the same trouble-free experience.

I'm glad to hear that there is success to be had.

 

[lunatic59]

I did the OTA update on both of our Nexus 4 and a Nexus 7. Didn't clear caches or anything. Zero problems. No doubt 99% or more users have the same trouble-free experience.

Were you rooted? Custom recovery? Were you on 4.3 JWR66Y? Any warnings or errors? Trying to figure out what's going wrong with the builds.

 

[bjacks12]

My sister just updated her from 4.3 last night via OTA. No problems.

I have one friend with an N4 who I haven't heard from yet, still got to find out if he got his update.

 

[jhonb]

I did the OTA update on both of our Nexus 4 and a Nexus 7. Didn't clear caches or anything. Zero problems. No doubt 99% or more users have the same trouble-free experience.

I am all good here, but just got the Nex4 upgrade last night. I have had the Nex10 upgrade of close to two weeks.

 

[Crashdamage]

Were you rooted? Custom recovery? Were you on 4.3 JWR66Y? Any warnings or errors? Trying to figure out what's going wrong with the builds.

Stock unrooted JWR66Y on all 3 units. No errors, no warnings, no problems.

 

[lunatic59]

Stock unroofed JWR66Y. No errors, no warnings, no problems.

Then I have to think that the issues are related to root.

 

[John Bean]

It's looking that way.

What surprised me was the utter, complete failure to recover; previous failed OTAs (because of rooting and/or modified systems) had tended to be recoverable often by simply rebooting, which is why I had no qualms about accepting this one. If it failed I would fix whatever it was complaining about and retry, just as I did with 4.3. Not this time though.

 

[codesplice]

Wonder if the new SELinux policy may be at fault?

 

[andruoid]

I unlocked and rooted 4.3, installed the stock KRT160 ROM. I had that for a couple of days then did the KRT16S OTA ...no issues with either. To top it off I'm using ART instead of Dalvik and battery life is fantastic and speed in some cases is dramatic. I'm a user though so don't ask for low level details

 

[bjacks12]

Yeah, ART >> Dalvik for sure. I immediately switched to ART upon updating. So i didn't get to compare 4.4 Dalvik to ART. But after my factory reset last night, I now have the chance. Dalvik is noticeably slower and the battery life is worse. I want to switch back....but ......science.

 

[michaelkenward]

Haven't had any of those issues. So far, I haven't noticed any real issues or incompatibilities..

You beat me to it. Given all the tales of woe, I thought it worth pointing out to people that this update can be painless.

For people who do have problems, it might be worth investigating what it is on the Nexus 4 that could cause their issues. There have already been various suggestions here, but what about apps? Could they upscrew an installation and create these symptoms?

If that is a possibility, it would also help if those who don't have problems could post a list of installed apps, but I would not know how to create one.

 

[ooberandy]

How do you choose to use ART instead of dalvik?

 

[bjacks12]

How do you choose to use ART instead of dalvik?

Go to Settings -> About Phone. At the bottom where it says Build, tap that repeatedly until it says you are now a developer. IIRC it's 7 times. Then go back out to the Settings menu, and right above About Phone, you will see Developer Options. Go into that menu and somewhere near the top it will say Select Runtime. Press that and switch to ART. This will require a reboot of the phone which will take quite a while depending on how many apps you have. It's recompiling them so that it has them ready whenever you use them.

 

[ooberandy]

Brilliant, thanks. Rebooting as I type

 

[jhonb]

My battery app does not work any more. The developer says that Android had decided to lock people out of the battery state. I have to root my phone to get it to work again.

 

[codesplice]

My battery app does not work any more. The developer says that Android had decided to lock people out of the battery state. I have to root my phone to get it to work again.

Yep.

 

[jhonb]

My battery app does not work any more. The developer says that Android had decided to lock people out of the battery state. I have to root my phone to get it to work again.

The Bastards.... Did Steve Job's get resurrected as a Google exec? Looks like that is the direction they are headed in.