I've experienced the extreme battery drain others here are reporting. I read about the Facebook 1.3 diagnosis, but removing this app did not resolve the issue for me. After some investigating and testing, I've found that the LED Light widget (not the new app that came with the phone, but a widget actually called "LED Light" by picolyl) also causes a partial wake lock. Your screen will go off but your phone does not sleep. To alleviate this simply remove the widget from the home screen it is located on, no need to uninstall. Hopefully the dev will be able to fix this issue; I have sent him an email via the market to notify him.
ccicchitelli said:
I've experienced the extreme battery drain others here are reporting. I read about the Facebook 1.3 diagnosis, but removing this app did not resolve the issue for me. After some investigating and testing, I've found that the LED Light widget (not the new app that came with the phone, but a widget actually called "LED Light" by picolyl) also causes a partial wake lock. Your screen will go off but your phone does not sleep. To alleviate this simply remove the widget from the home screen it is located on, no need to uninstall. Hopefully the dev will be able to fix this issue; I have sent him an email via the market to notify him.
Click to expand...
Click to collapse
Would this, perhaps, apply to the SwitchPro Widget LED light as well?
I uninstalled the facebook update and was still getting some pretty ****ty battery life, I JUST pulled the switchpro LED light from it's bar and am praying that fixes my battery. I can't find anything in Spare Parts or SystemPanel on what the culprit is though, everything looks "ok"
Are you referring to this widget ?
I have used that app since the phone came out and don't have problems with battery because of it... but I did have a huge battery problem after updating.. FACTORY RESET will fix you problem
Sent from my PC36100 using XDA App
opie2l said:
I have used that app since the phone came out and don't have problems with battery because of it... but I did have a huge battery problem after updating.. FACTORY RESET will fix you problem
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Unless you're on a custom ROM, in which case wouldn't a factory reset totally hose you?
I'm not sure which LED light (with widget) I had, but I can also confirm I had terrible battery life with it. I started removing the most recent apps I installed, and that was the one.
Even if you're not on a Custom rom, factory reset did nothing for my battery life. It was fine until Froyo. Now it's dying and NOTHING is on. I can't see where my battery is going. I've checked all the running apps, and force stopped non essential ones. My battery is still dying very quickly. I was doing factory resets last night because Sprint was saying that if I did it would remove 2.2. I don't know who is dumber, him for telling me or me for actually doing it and believing it might.
jaypeezee said:
Are you referring to this widget ?
Click to expand...
Click to collapse
It's the original version of that widget, yes
opie2l said:
I have used that app since the phone came out and don't have problems with battery because of it... but I did have a huge battery problem after updating.. FACTORY RESET will fix you problem
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
First and foremost, don't factory reset! That causes gremlins to come out. If you want to wipe your data, boot into recovery, wipe the cache, dalvik cache, and the user data option there.
mrfoxhound said:
Even if you're not on a Custom rom, factory reset did nothing for my battery life. It was fine until Froyo. Now it's dying and NOTHING is on. I can't see where my battery is going. I've checked all the running apps, and force stopped non essential ones. My battery is still dying very quickly. I was doing factory resets last night because Sprint was saying that if I did it would remove 2.2. I don't know who is dumber, him for telling me or me for actually doing it and believing it might.
Click to expand...
Click to collapse
Check your Up time vs Awake time in Battery under about phone in settings. If they match or are very close, you have an app causing a wake lock. Typically, you should see a big gap, like this: Up time 20:34:56, Awake time 3:30:24
I posted a topic about this too when the leaked update came out and can confirm it causes a drain. There is no need to wipe or reset anything. Just uninstall it until the dev updates it for froyo.
Related
Has anyone else experienced this?
Sometimes (5-6 times in the last 24 hours) when the phone is sleeping, it will not wake when I hit power/unlock. I have tried installing no lock, hoping it was a glitch in the lock screen, but it still happens. The only way to fix it is to pull the battery.
Any advice?
Web sites are over-rated, when you have apps like these
bryon13 said:
Has anyone else experienced this?
Sometimes (5-6 times in the last 24 hours) when the phone is sleeping, it will not wake when I hit power/unlock. I have tried installing no lock, hoping it was a glitch in the lock screen, but it still happens. The only way to fix it is to pull the battery.
Any advice?
Web sites are over-rated, when you have apps like these
Click to expand...
Click to collapse
Are you running setcpu? Mine was doing this when I would lower the speed with a screen off profile. I just uninstalled setcpu for now. I don't think the kernel supports it anyway.
Sent from my SGH-T959 using XDA App
No, I had it, but since I can't overclock yet, there was no need to keep it installed. I did a factory reset, so we'll see if this fixes things.
Sent from my SGH-T959 using XDA App
bryon13 said:
No, I had it, but since I can't overclock yet, there was no need to keep it installed. I did a factory reset, so we'll see if this fixes things.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
let us know how it goes... If you experienced any unable to wakes after the reset...
Seems to be working fine. I'm not sure what the problem WAS, but the reset seems to have fixed it.
Root and busybox were still intact. Had to re-do the lag fix. (Method 1)
I'll update if I get the issue again.
My phone is just so...VIBRANT
Samething happened to me yesterday morning. Woke up found my phone wouldn't go back up. I thought it was dead, until I pulled the battery. I haven't Root hack it or installed SetCPU.
Sorry to throw this issue in this topic, but anyone have any problem with the phone rotating sideway for WEB and Messaging? I thought when I first got it, it worked.. now it doesnt..
There is probably a common app here or something causing this because I don't ever recall hearing this type of issue with the Vibrant before this thread.
I had the same thing happen to me and found after much trial and error that when I pulled my SD card out I was then able to wake the phone up. Apparently there was some problem with my SD (I was using it with my previous phone..MT3G) that was causing the Media scanning process to get stuck.
I ended up backing up what I needed from the SD and reformatting it. Since then I haven't had any issues. We may or amy not have the same root cause but hopefully this does help.
I'm thinking the problem HAS to be software related. After the reset, I've reinstalled everything I had before, and it's working like a charm! I've even used Titanium Backup to remove a lot of the bloatware, and still ruining great!
I just wish we could get a logcat, but when it happens, the phone is dead until you pull the battery.
My phone is just so...VIBRANT
bryon13 said:
I'm thinking the problem HAS to be software related. After the reset, I've reinstalled everything I had before, and it's working like a charm! I've even used Titanium Backup to remove a lot of the bloatware, and still ruining great!
I just wish we could get a logcat, but when it happens, the phone is dead until you pull the battery.
My phone is just so...VIBRANT
Click to expand...
Click to collapse
I am almost 100% SETCPU is the problem..
My phone would not come out of sleep.. I had to pull the battery and when I turned it on it would say "auto update of time and date".. That made me think the phone lost its internal battery and the phone was bad..
It started doing it right after I configured SETCPU... I installed the program last Thursday but never clicked on it.. I set it for on demand and that is when it started not coming out of sleep..
So I removed SETCPU and it still would not come out of sleep..
So I did a wipe all user data and it started working fine.. I installed SETCPU and it was still working fine.. I setup SETCPU for performance and it started messing up again and not coming out of sleep..
So, I wiped all user data again last night and it has been working perfectly since.. So I do not plan on reinstalling SETCPU...
Most of us here love our Nexus S phones. We love Android 2.3's speed and the neat little TV effect when we lock our screens. Since Friday morning, (Feb. 11th) my Nexus S seems to be having another TV effect: nightly "sign offs."
It does not matter if I was charging the phone or not, the phone would just stop working. The strip of touch buttons along the bottom of the phone could be lit or unlit, but the screen would just turn off and no button presses would wake the phone. If I plugged it in to a computer, you could hear a "device connect" noise and see the Android hard drive appear under the Device Manager in Windows.
All of this means that the Nexus S was powered, but not responding. It would not reboot itself, and yes, I have experienced the reboot issue. This seems to be a separate issue. This only seems to happen after midnight.
The only solution is to pull out the battery and reboot it manually.
If my Nexus S is still on when this silent crash occurs overnight, my battery could be completely drained by the time I wake up, making me plug it in AND requiring a battery pull.
Has anyone else had this issue occur? According to the Android Market, I've only updated a few programs recently, one of them being Twitter.
Some Recently Updated Programs: (most recent first)
T-Mobile My Account (to 5.0.15)
Google Authenticator (installed, 0.54)
Google Goggles (to 1.3.1)
Twitter (to 2.0.0)
Amazon MP3 (to 1.8.30)
Google Books (to 1.1.4)
System Info:
Stock, unrooted Nexus S
Launch day unit
T-Mobile USA
Android 2.3.2
Baseband I9020XXJK8
Kernel 2.6.35.7-g7f1638a [email protected] #1
Build GRH78C
When I woke up on Friday, I called Samsung and they did note the issue under my phone number. I will call them again Monday and let them know I'm still having issues.
Any help/suggestions from the XDA community would be appreciated.
Thank you!
Just checked this morning, (Monday) and I had to pop out the battery to turn the phone back on. Before I went to sleep, my battery was at 100%. When I woke up and booted the phone up, it was around 30%. A 70% drop in 8 hours. Time to call Samsung again.
No one else is having this issue?
Sent from my Nexus S using XDA App
Sounds like either a defective unit, or messed up software.
Try doing a factory reset and use don't install many apps and see if that resolves for problems for a day or 2.
Well I had a strange issue that I had never seen before... at around midnight last night both my NS and my gf's went into bootloop at the same time, it was freaky. We're both on CM7 but hers is an older build and mine has netarchy's but it's never happened before... pulling the battery and powering back on fixed both phones but it's still very weird.
I have never actually called the manufacturer before about any issues with a device. Do they do anything for you? Or help you in any way?
Sent from my Nexus S using XDA App
Samsung suggested that I do a factory reset and then if that does not fix the issue, then I'll have to send the phone into them. The tech I got on Friday was more knowledgeable than the one I got today. I'm going to backup my data and then do a factory reset, making sure not to "pull" my data from Google's servers.
Man, not doing that is going to suck.
I am also using Google Voice for my voicemail. Just wanted to throw that out there in case any running services or something is causing all of this. I'm thinking that the new version of Twitter is causing this, as it's baked into Android now and there was an update recently. Thoughts?
Here's a small update on my issue: it seems to be software-related. My Nexus S crashes during the day as well, requiring a battery pull as described above. Disabling sync does not solve the issue, so it doesn't seem like it's coming from that area. What would you guys suggest my next place to look be?
Thanks!
Well, have been having almost the same issue for the past two days. Go to bed with 57 & 63%. Get up in the morning and the phone is dead. Not sure of the exact time it.passes away, but yeah.
Can't understand why the phone has to drink while I sleep.
Sent from my Nexus S using XDA App
Same prob, only intermitant though. Im using rc1 now, with no custom kernel.
Sent from my Nexus S using XDA App
I've been having the same issue since the 13th of Feb. At first it would freeze only overnight. Now, since the 14th it freezes while asleep 4-5 times a day, and the only way to get it working is to do a battery pull. I've tried to remove recently installed apps and widgets, but that has made no difference. I really don't want to have to do a factory reset, especially after I've been reading on google forums about other users not noticing a difference after a factory reset. This is getting ridiculous.
Unrooted Nexus S
Android 2.3.2
Baseband I9020XXJK8
Kernel 2.6.35.7-g7f1638a [email protected] #1
Build GRH78C
T-Mobile US
Agreed. Mine started to freeze during the day as well, requiring a battery pull. Do you have the new Twitter installed? Do you use Google Voice for voicemail? I'm trying to pull together some common threads. It's definitely software related.
Edit: OK, now this is just stupid. It seems like I'm freezing up every half an hour by now. I pull the phone from my pocket to check on something and I push the power button. The lockscreen shows, but the screen and touch buttons don't respond. Battery pull is the only option.
Yes, I do have the new Twitter installed, and yes, I do use Google Voice.
It seems to be happening more often now for me as well. Sometimes it takes two to three times for it to fully restart and get to the home screen, or the lock screen, and sometimes it will wake and then freeze on my pattern lock which also requires a battery pull.
I've starred a few forums on this same issue on the Google support forums, I hope others do the same to show support for a quick fix.
Last night I had the battery at 90. Switched of Wifi, Data and Sync.
Got up this morning and ... no probs The battery dropped to just 88!
BTW. I have got a stock unrooted phone with no Google Voice or twitter so, could not really be a problem related to that.
I use the app addin timer to run stuff at particular times. Other apps that I downloaded are calcbuddy, barcode scanner (which I think is pointless and going to remove), pure messenger, calwidget, appbrain (again, did not like the new updated one), aTakephone, Flip4Silence, CoPilot, Fast Reboot, Docs to Go, Skype, Remote Desktop, StockIndia, Tunein Radio and Widgetsoid.
Thanks for letting me know the apps you have installed. The only common ones between us are:
Barcode Scanner
Skype
Barcode scanner is actually useful. (QR Codes, etc.) Skype may have something to do with it as it does integrate itself with data sync. Thoughts?
In order for this theory to hold water, your phone must:
Crash and require a battery pull to be responsive
Have Skype installed
Edit: My phone was crashing so much that the "first time/welcome" wizard was coming up. Swype, Facebook and GMail were crashing left and right. Time for another Factory Reset....
Edit 2: The phone has SOMEHOW survived a Factory Reset from the normal phone menu AND the Recovery menu! WHAT?!
My Nexus S is going back to Samsung for repair. *sigh* I wonder what they'll say caused the issues?
Sent from my Nexus One using XDA App
Now, today, the phone doesn't get passed the initial "Google" screen. No matter how many times I pull the battery, plug it into a charger or usb port, it does not go past the first google screen. Very disappointing.
Can you get into the bootloader menu? (Volume Up + Power)
Yes, that allowed me to get to the bootloader menu, but I couldn't do a factory reset, it just sat at the screen with the android and an exclamation point inside a triangle. I then did a battery pull, tried a normal restart and got to my home screen.
Glad to hear that you got in. By the way, once you get to the exclamation point screen, you can push Power while holding the Volume Up button to bring up a menu.
Cool, thanks for the help!!
My phone will randomly stop sleeping, this has happened pretty much since i've gotten it.
I will launch spare parts, running near 100%. Check partial wake lock, nope nothing. And nothing under any of the other menus in spare parts that would indicate it not sleeping. This will occur after a couple of days even after installing no apps, restarting does not fix, neither does pulling battery. It will just start happening and only way to fix is data reset / factory wipe until it happens again, but when it does start happening I might've not even be using it at the time.
Okay, i did actually finally fix it after months without factory reset, it appeared to be when 3g and Data-always enabled was ticked.
ryronz said:
Okay, i did actually finally fix it after months without factory reset, it appeared to be when 3g and Data-always enabled was ticked.
Click to expand...
Click to collapse
If this fixes my no sleep problem, I will name my first child after you.
I've been detailing the steps I've taken to resolve my no sleep issue on another forum, with the last action I took being a flash to factory ROM from huaweidevice.com, changing absolutely nothing on the phone for 24 hours, rebooting, and waiting another 24 hours. Without a reboot between charge/taking off charge, it would be 100% running. If I took it off charge and immediately rebooted, running would be more like 30% (ie: 'normal').
I'll give 'data-always' a go
the red krawler said:
If this fixes my no sleep problem, I will name my first child after you.
I've been detailing the steps I've taken to resolve my no sleep issue on another forum, with the last action I took being a flash to factory ROM from huaweidevice.com, changing absolutely nothing on the phone for 24 hours, rebooting, and waiting another 24 hours. Without a reboot between charge/taking off charge, it would be 100% running. If I took it off charge and immediately rebooted, running would be more like 30% (ie: 'normal').
I'll give 'data-always' a go
Click to expand...
Click to collapse
Wooh, nah for example my running time is 8.7% and screen on is 6.1% so that is pretty good, thats over the course of about an hour
the red krawler said:
If this fixes my no sleep problem, I will name my first child after you.
I've been detailing the steps I've taken to resolve my no sleep issue on another forum, with the last action I took being a flash to factory ROM from huaweidevice.com, changing absolutely nothing on the phone for 24 hours, rebooting, and waiting another 24 hours. Without a reboot between charge/taking off charge, it would be 100% running. If I took it off charge and immediately rebooted, running would be more like 30% (ie: 'normal').
I'll give 'data-always' a go
Click to expand...
Click to collapse
Okay im unsure now, was all fine yesterday, woke up at 7 to alarm, lost 2% overnight. then just put it under my bed but now that i've woken up i've lost 18% because it just stopped sleeping again. I didn't do anything except turn it on check battery, and turn it off. So back to being confused again
Still having this problem, for example. It was sleeping fine when I went to bed then at some point during the night just stopped.
Running 64.6% 10h
Screen on 10ish% 45 minutes
Highest item with partial wake lock in spare parts is like 5 minutes, no other indicators.
This is happening no matter which ROM i try.
Considering a stock ROM with exactly 0 changes still has sleep issues, its clearly a firmware "thing".
For me, it happens after being taken off charge.
For e.g. Last thing before bed I check my running time, and its somewhere around 35-40%. Plug into charger. Take off in the morning, goto work etc, check my run time and its 100% even without the phone being touched.
For the moment I just downloaded one of the "root only" reboot widgets from the Market. Its just part of my morning "get ready for work" routine to hit the reboot widget and reboot my phone.
Its a bit of a PITA but until new firmware is released I cant see a way around it.
the red krawler said:
Considering a stock ROM with exactly 0 changes still has sleep issues, its clearly a firmware "thing".
For me, it happens after being taken off charge.
For e.g. Last thing before bed I check my running time, and its somewhere around 35-40%. Plug into charger. Take off in the morning, goto work etc, check my run time and its 100% even without the phone being touched.
For the moment I just downloaded one of the "root only" reboot widgets from the Market. Its just part of my morning "get ready for work" routine to hit the reboot widget and reboot my phone.
Its a bit of a PITA but until new firmware is released I cant see a way around it.
Click to expand...
Click to collapse
Hey don't know if you've tested it further than that. But its much appreciated, that rebooting after charging does seem to work . But just wondering, if you know... does it only do it when charging via usb (computer) or AC or does it not matter?
I have exactly the same problem.
I also noticed that reboot helps, but only for a while. If i want my phone to go to sleep mode when the screen is off, i would have to reboot it few times a day... Turning WiFi/GPS/Auto-sync on/off does not have any affect on this.
ryronz said:
Hey don't know if you've tested it further than that.
Click to expand...
Click to collapse
As per your suggestion via email, I tried the Malaysian firmware.... It seemed that 'running' time was down alot, but battery life was still pretty average. That was doing nothing more than installing the Malaysian firmware and entering my Google account - no root, no launcher changes, etc.
The lack of Swype was a bit of a downer too
I gave it a whirl from 6:30am to around 5:00pm and 'running' was right down in the 10% range, but battery was still down to ~45% over that time in 'pure' stock form. DAMMIT!
Ah well. It was a good thought and hopefully it worked for you I'm back on roadhound + the OTA update as of about two hours ago.
I'm going to scour the SGS forums and see if anything there can be applied to the U8800 RE: battery life improvements.
the red krawler said:
As per your suggestion via email, I tried the Malaysian firmware.... It seemed that 'running' time was down alot, but battery life was still pretty average. That was doing nothing more than installing the Malaysian firmware and entering my Google account - no root, no launcher changes, etc.
The lack of Swype was a bit of a downer too
I gave it a whirl from 6:30am to around 5:00pm and 'running' was right down in the 10% range, but battery was still down to ~45% over that time in 'pure' stock form. DAMMIT!
Ah well. It was a good thought and hopefully it worked for you I'm back on roadhound + the OTA update as of about two hours ago.
I'm going to scour the SGS forums and see if anything there can be applied to the U8800 RE: battery life improvements.
Click to expand...
Click to collapse
Oh yeah sorry, try using something like juice defender to disable 3g when screen is off or something. 3g radio keeps it running, but it doesn't appear to be, this will stop the battery drains.
EDIT: That does work but its not ideal, turns out the u8800 and the u8800h use the exact same radio so im not sure now, don't know if there is any possible way to figure it out.
ryronz said:
3g radio keeps it running, but it doesn't appear to be, this will stop the battery drains.
Click to expand...
Click to collapse
Sometimes i have 3g data connection running, but phone goes into the sleep mode when screen if turned off. So this is not the cause.
knevski said:
Sometimes i have 3g data connection running, but phone goes into the sleep mode when screen if turned off. So this is not the cause.
Click to expand...
Click to collapse
Oh no, this is just the case for the U8800H malaysian firmware seems normal for all U8800 firmware.
I'm not using u8800H firmware and i have this bug.
Hey guys.
This may not really be the thing you need but I was having similar problems and running 100% on without sleeping etc and came accross another forum where this was an issue (cant remember where)and as trivial as it sounds the solution for me was to go into settings/ applications/ manage applications and running applications and go down to media storage and clear the data. I do this now and then when I have this problem and it seems to help.... Maybe worth a try? It seems to be an issue with a particular media file. I also try to reboot my phone after every charge. Note that my phone is totally stock
astewart said:
Hey guys.
This may not really be the thing you need but I was having similar problems and running 100% on without sleeping etc and came accross another forum where this was an issue (cant remember where)and as trivial as it sounds the solution for me was to go into settings/ applications/ manage applications and running applications and go down to media storage and clear the data. I do this now and then when I have this problem and it seems to help.... Maybe worth a try? It seems to be an issue with a particular media file. I also try to reboot my phone after every charge. Note that my phone is totally stock
Click to expand...
Click to collapse
Thanks for advice, but unfortunately this didn't help either. For some unknown reason, my running time is again 100% although the screen is off most of the time. In Partial wake usage, Android System is in the top of the list.
Oh, Android System partial wake lock seems to be a different issue, but maybe someone can help you out. Whats happening here is running = 100% yet there is no partial wake lock held. Quite unusual
ryronz said:
Oh, Android System partial wake lock seems to be a different issue, but maybe someone can help you out. Whats happening here is running = 100% yet there is no partial wake lock held. Quite unusual
Click to expand...
Click to collapse
Yes, it is confusing also because i have tried different ROM's with same result. I would have thought that all u8800 owners have the same problem.
same problem here...
I've had a SII for a couple of weeks now (new user to android) and I have flashed it to Lightning Rom 1.5. But even before doing this and also afterwards the phone seems to crash/lockup at 5am on about 5-6 occasions.
Is there any program/app I can install to monitor what is kicking in at this time so that I can disable/uninstall it?
Thanks
What do you mean by crash exactly ? Reboot ? Freeze ?
What you could do is plug your phone to your computer before it crashes, and start adb logcat, wait for the crash, and then look at the log to see what caused the crash.
It is completely frozen. I get up at 6:15am and the phone has a blank screen, but I can press a button to activate the screen and the clock is stopped at 5:01am and you cannot do anything else except turn the phone off and back on.
Maybe its the rom? Have you checked its thread? Try flashing bacm to stock. See if problem occurs.
Sent from my GT-I9100 using XDA Premium App
I checked the thread but doesn't appear to be anyone else with same issue. I might try the stock ROM to see if the problem persists. Although I sure it happened once on the firmware that came on the phone (KE2 I think it was).
scheduled backup?
I couldn't find any backups scheduled. So I wiped the phone last night and applied the Lightning 1.5 ROM again and it seems to have been fine this morning..no lockups.
Thanks for the advice.
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
OccasionalDroid said:
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
Click to expand...
Click to collapse
I'll keep that in mind if it happens again..cheers. Been OK this morning so shall see how it goes.
Its done it a few more times since I did a factory reset, always at 5:01am. After rebooting the phone and checking the battery stats it appears that 'Cell Standby' has used 52% of all battery consumption and the battery drained from 100% to 9% over 8 hours. The problem also occurs even if the phone is on charge over night.
So maybe it is a buggy radio? Gonna take it back to the store tomorrow to be looked at.
Edit: Seems this is a more widespread problem, looks like the consensus is that is has to do with Daylight Savings Time change & the wireless charging Orb. Some others with similar problem:
https://productforums.google.com/forum/#!msg/nexus/qkzrUEA-UbM/7IeU2q5uXDIJ
http://www.reddit.com/r/nexus4/comments/1pyk0t/all_apps_crash_in_the_morning_after_taking_my_n4/
https://code.google.com/p/android/i...=ID Type Status Owner Summary Stars&id=61868
----------------------------------------------------------------------------------------------------------------
(Original Post)
Hey guys. I have a 16GB Nexus 4 that is rooted (SuperSU 1.65), running CWM (6.0.3.6), stock radio, stock kernel, stock 4.3.
I installed the pre-released hangouts v2 that was extracted from the AOSP 4.4. It immediately started causing random apps to crash so I uninstalled it and reinstalled the original version of hangouts. Ever since then though, every morning when I take my phone off the charger (orb) whenever I try to open any google apps (gmail, settings, camera, etc) it will force close that app. Once I reboot the phone everything seems to be working fine until the next morning.
I have tried clearing the cache & dalvik but to no avail.
My last nandroid is from a few months ago so Id really like to have to reload that only as a last resort. Any suggestions?
Thanks.
burnski said:
Hey guys. I have a 16GB Nexus 4 that is rooted (SuperSU 1.65), running CWM (6.0.3.6), stock radio, stock kernel, stock 4.3.
I installed the pre-released hangouts v2 that was extracted from the AOSP 4.4. It immediately started causing random apps to crash so I uninstalled it and reinstalled the original version of hangouts. Ever since then though, every morning when I take my phone off the charger (orb) whenever I try to open any google apps (gmail, settings, camera, etc) it will force close that app. Once I reboot the phone everything seems to be working fine until the next morning.
I have tried clearing the cache & dalvik but to no avail.
My last nandroid is from a few months ago so Id really like to have to reload that only as a last resort. Any suggestions?
Thanks.
Click to expand...
Click to collapse
Try clearing the data of Google Services Framework. If that doesn't work, reflash your Gapps package.
thanks, I will give that a shot.
Mine started doing this but not rooted and didn't install any pre-release apks. The clock even crashes while on the charger when it tries to sound the morning alarm.
A reboot clears it for the day but its back every morning. I reset the phone but no change.
crashes every morning
I think it has something to do with the time change???
crashes every morning.
stock rooted
whole bunch of other people too over at reddit
http://www.reddit.com/r/nexus4/comments/1pyk0t/all_apps_crash_in_the_morning_after_taking_my_n4/
Anyone with any fix for instant Karma?
seems to be fixed. thanks.
burnski said:
seems to be fixed. thanks.
Click to expand...
Click to collapse
which fix worked for you?
burnski said:
seems to be fixed. thanks.
Click to expand...
Click to collapse
I got the same problem, i click on clear cache of Google Service Framework but nothing happens!
Can you reproduce your steps?
whelp, i was wrong. When I woke up this morning, checked my email and it crashed. So I tried to go into settings to clear the framework and the settings crashed too. So I rebooted and its fine again. Any other ideas?
Same problem
I was the one that started that thread on Reddit. I've done a factory reset from the settings menu, cleared the cache data and factory reset via fastboot menu and the issue is still occurring. Phone is completely bone stock, no root or anything.
For me it started Saturday 11/2. I have been using the charging orb just as everyone else. I tried using my wall charger last night and I didn't have an issue. Not sure why out of the blue this could be the cause. I will be trying my orb again tonight to see if it reoccurs.
Mine did not crash this morning, after clearing the google service framework yesterday.... now it might crash tomorrow.
here is my thought into the process... Are we all using the google alarm clock? and after the time change?
4.4 can't get here fast enough
Bobvark said:
Mine did not crash this morning, after clearing the google service framework yesterday.... now it might crash tomorrow.
here is my thought into the process... Are we all using the google alarm clock? and after the time change?
4.4 can't get here fast enough
Click to expand...
Click to collapse
The first time it happens to me i was using the timely app as alarm clock. And it occurred the same day i got the time change. After that i uninstall timely and start using de default clock app.
The same day i got the time change the chrome app was not working either, i had to change my time zone to fix it.
I dont use my phone as an alarm clock, I dont use daydream or anything like that.
Do we all use the orb to charge though? Is that something we all seem to have in common?
Bobvark said:
I think it has something to do with the time change???
crashes every morning.
stock rooted
whole bunch of other people too over at reddit
http://www.reddit.com/r/nexus4/comments/1pyk0t/all_apps_crash_in_the_morning_after_taking_my_n4/
Anyone with any fix for instant Karma?
Click to expand...
Click to collapse
Wow, just went through the reddit thread. seems to be a much bigger issue that originally though.
I also edited the title to reflect the orb being the newly suspected cause of the problem - not hangouts as originally thought.
I also found a link to a google group through the reddit thread, so I posted in that to complete the triangle. LOL. Hopefully someone comes up with a solution.
https://productforums.google.com/forum/#!msg/nexus/qkzrUEA-UbM/7IeU2q5uXDIJ
Should also mention on here that my wifes charges her Nexus 4 wirelessly with an LG WCP-300. I charge with the Nexus orb. She does not have the problems.
burnski said:
I also edited the title to reflect the orb being the newly suspected cause of the problem - not hangouts as originally thought.
I also found a link to a google group through the reddit thread, so I posted in that to complete the triangle. LOL. Hopefully someone comes up with a solution.
https://productforums.google.com/forum/#!msg/nexus/qkzrUEA-UbM/7IeU2q5uXDIJ
Click to expand...
Click to collapse
It's not the orb charger. I've been getting the same issue, but I use the N4 cable charger. Timely alarm clock still goes off, but there's a FC message when I go to my phone. Reset fixes it for the day. UK based, CM10.2 M1 + latest goo.im gapps. Also, I have a weird issue where the screen keeps turning back on when I lock it. Just keeps the lock screen permanently on when I'm charging in the morning.
burnski said:
I also edited the title to reflect the orb being the newly suspected cause of the problem - not hangouts as originally thought.
Click to expand...
Click to collapse
I dont think the problem is related to the orb or wireless charger. Two people just post about the problem and they are using wired charging.
Everybody had to change the time before the problem start (summer time, DTS, whatever)? i'm suspicious that android is not handling this changes.
Anybody knows if android has a log with the errors? Maybe we can found some tip.
has anyone had the problem and NOT charged overnight?
Its possible that this occus overnight because the DST change usually occurs at 2am so if the glitch happens at 2am most of us dont see it until we get up.
Im going to disable the automatic network time & automatic time zone settings tonight - see what happens tomorrow morning.
burnski said:
Im going to disable the automatic network time & automatic time zone settings tonight - see what happens tomorrow morning.
Click to expand...
Click to collapse
I like this idea, but for me, the issue started the morning before the daylight savings rollback.
I used my wired charger last night and didn't have the issue this AM, but will be trying my orb again tonight.