Unfortunately [everything] has stopped.

[chinoco02]

Do let us know if the 4.4 kitkat upgrade solves/removes this annoying issue!

I've had this exact same problem. It occurs a couple of times per week. This could be coincidence, but for me the first thing that seems to crash is Swiftkey. After that, everything else I attempt to open crashes and eventually the UI will crash as well. A reboot is the only cure. I don't use wireless charging so that doesn't appear to be the culprit for me. I just installed Kitkat tonight. Hopefully that rectifies the issue.

 

[PlusJack]

Haven't wirelessly charged for two days and the problem has been nonexistent. Can someone with KitKat confirm/deny if it's fixed?

 

[chinoco02]

Sigh, negative ghostrider, the auto date/time zone trick didn't work. Opened up messenging and it force closed on me. Clearing out my recent apps seems to have rectified the problem the for now. Guess I'll have to plug my N4 the old way. Even that has charging issues.

Good stuff scoutzdad. I tried checking off the automatic time zone and date as well as the daylight savings time. I then checked it back on.

We'll see what happens tomorrow morning. I put my N4 on the wireless orb as well. Anyone want to place bets to see what happens? ;-)

 

[BadHead1970]

Just a suggestion, but wipe tit phone - including the cache and the dalvik cache (This can sometimes be done from Recovery. Depending on your recovery version and make.) Then re-flash your ROM and keep it stock. Do not add any Apps at all. Maybe even don't set jon your Google account or wi-fi and just leave it for a few night. If its OK, do one thing and leave it again for a couple of nights...etc etc.

Carry on like this until (or if) something goes wrong. That way you will have a better idea of the culprit.

Hope this advice helps.

Sent from my Nexus 4 with Tapatalk

 

[BadHead1970]

It may Aldo be worth just clearing your Dalvik cache now, without going anything else. A lot of info on the internet suggests that this could be a cause of a number of problems when changing ROMs.

Also, if you do manage to get your phone up and running again, it would be worth doing this on a regular basis. I use an apply called 'Root Cleaner' to do this. Your phone will most likely need to he rooted for this yo work though.

Sent from my Nexus 4 with Tapatalk

 

[sanchitgrover]

Y dont you guys try changing your rom ? May be that can help?

 

[scoutzdad]

Wired charging worked again last nite for me. Anyone update to KitKat yet with this problem that can confirm it solved the issue?

 

[jbevers77]

I changed my ROM. That didn't seem to help. I thought I was free of the problem this morning after returning the phone to stock but no luck with that either. I'm going to wire charge again tonight and see if the issue persists. I was sent a replacement phone and will put that on the charger for a couple nights to see if its phone specific as well just in case.

Posted via Android Central App

 

[TdotLee]

I don't believe this problem has anything to do with battery savers, third party apps, wireless chargers, roms, rooted, non-rooted, locked, unlocked, 4.4, 4.3, time zone, daylight savings, the time of day, or what color eyes you have! I believe this is a Google issue they need to figure out.

I've been having this problem for awhile now with my Mlive apps and my wife started having the problem with her Google Keep app. I get this message whenever updating my apps even though I'm not running or updating either of my Mlive apps (though I can open either app no problem). The message will popup when I'm in the My Apps section of the Play store. My wife gets the message whenever she attempts to open her Keep app.

Sent from my Nexus 4 using AC Forums mobile app

 

[PlusJack]

I'd like to get a couple things straight

1. Factory reset doesn't work. I've tried.
2. It's not an app problem. Even with only stock apps installed, it still happens.
3. It only happens after wireless charging for a few hours. Using wired charging fixes this.
4. Different ROMs do nothing. I installed CyanogenMod to no avail.

 

[whitenight21]

I'd like to get a couple things straight

1. Factory reset doesn't work. I've tried.
2. It's not an app problem. Even with only stock apps installed, it still happens.
3. It only happens after wireless charging for a few hours. Using wired charging fixes this.
4. Different ROMs do nothing. I installed CyanogenMod to no avail.

PlusJack is right. same thoughts here.

Posted via Android Central App

 

[treggs]

My wife and I both have stock (rooted) Nexus 4's that had this problem charging on the Nexus orb. Updating to KK seems to have solved it. I suspect Google updated something in preparation for KitKat that broke JellyBean and now we have KK it's all good again.

 

[f1drivr]

Had same problem started about a week ago. I use the Nexus charging orb every night. Almost missed a critical meeting cause alarm didn't go off. Usually Gmail doesn't respond, can't send error report. Now SwiftKey doesn't respond, I couldn't type a response here till killing apps. I will try wired charging now.

Posted via Android Central App

 

[f1drivr]

Update. Day two after my post. Did not charge overnight. Did not use wireless charging orb. In fact I charged in the evening and then placed the phone on the nightstand. First thing in the morning I used it with no problems. Chrome, Gmail all work. Next time I will charge overnight with wired charger.

Posted via Android Central App

 

[ChromeJob]

As per the Google issue page, I left my Nexus 4 (4.3) off the Nexus charger for two nights in a row, and the alarm app worked fine. Later the first day, at work, the phone was on the Nexus wireless charger for a couple of hours, when suddenly keyboards and other apps were stopping, requiring a reboot (actually the phone rebooted itself, another grievous problem with this bug).

This strongly indicates to me that the fault is something to do with wireless charging. Sure hope it's resolved, I bought the N4 to get away from an HTC Amaze that would turn off spontaneously if you rubbed the screen. (And now its replacement is refusing to turn on. Never. Buying. HTC. Again!)

Now that an updated factory build for 4.4 (Nexus 4) is out, and the OTAs are rolling out, an update is imminent.

 

[N4Newbie]

As per the Google issue page, I left my Nexus 4 (4.3) off the Nexus charger for two nights in a row, and the alarm app worked fine. Later the first day, at work, the phone was on the Nexus wireless charger for a couple of hours, when suddenly keyboards and other apps were stopping, requiring a reboot (actually the phone rebooted itself, another grievous problem with this bug).

This strongly indicates to me that the fault is something to do with wireless charging. Sure hope it's resolved, I bought the N4 to get away from an HTC Amaze that would turn off spontaneously if you rubbed the screen. (And now its replacement is refusing to turn on. Never. Buying. HTC. Again!)

Now that an updated factory build for 4.4 (Nexus 4) is out, and the OTAs are rolling out, an update is imminent.

Perhaps, more specifically, the Nexus wireless charging orb? Wife and I both have N4's (though I recently upgraded to an N5) and have used a Qi charger (this one Energizer Qi Enabled 3 Position Inductive Charger | eBay ) every night for most of the last 12 months without any issues.

All three phones are stock and un-rooted.

 

[ChromeJob]

Perhaps, more specifically, the Nexus wireless charging orb? Wife and I both have N4's (though I recently upgraded to an N5) and have used a Qi charger (this one Energizer Qi Enabled 3 Position Inductive Charger | eBay ) every night for most of the last 12 months without any issues.

All three phones are stock and un-rooted.

This just started in the last 2-3 weeks, since the N5 has been out. If you've been using an N5, on 4.4, then you wouldn't have seen it over the last 12 months.

I flashed KRT16S to my N4 last night, put on the charger, and alarm went off normally. As per the Google complaint thread, 4.4 seems to have fixed this. With OTAs going out ... this problem is doubtlessly going away for most.

 

[chinoco02]

Just want to chime in as well. Sideloaded KitKat yesterday and charged my N4 overnight via wireless orb. Everything works so far, no annoying force closes - even from the notification shade. Seems 4.4 was the cure.

 

[PlusJack]

Just want to chime in as well. Sideloaded KitKat yesterday and charged my N4 overnight via wireless orb. Everything works so far, no annoying force closes - even from the notification shade. Seems 4.4 was the cure.

Can't wait until I get 4.4 then, if only for this. I have to wait for CM 11 for that, though.

 

[whitenight21]

true that.. KitKat 4.4 also fixed the problem for me.. once again, happily wirelessly charging all the time, with no problems whatsoever... case closed. thread complete. thanks yall

Posted via Android Central App