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.
Related
Hello everyone, I've got an interesting problem that I want the experts here at XDA to help me troubleshoot. Feel free to ask questions as I know there's probably a million variables at this point with stuff installed, uninstalled, gps, root, task killers, etc.
alrighty with that said, I did the e-wrecked gps fix (changing the operation mode and server location+port). That seems to work great in terms of time to lock on my position as well as improved accuracy. Over the next couple of days I noticed some really choppy and lengthy phone start ups after the fix.
Eventually it got to (and currently is at) a point where it kept rebooting the phone, or at least touchwiz. It would load up, scan media, search for the network, do all the start up stuff, then lock up, and turn the screen off. Hitting the lock button/power button does nothing while it resets itself. Then it resets to the lock screen, the screen lights up and it goes into "searching" for the tmo network while doing the storage preparations, and other boot up stuff. It does not restart from cold (with the vibrant, tmo, and galaxy animations, only the lock screen and OS boot process)
Anyone else got any funky restarts going on, for whatever reason? I basically want to start seeing what would trigger this behavior. I started uninstalling stuff one by one trying to figure out why its doing that but sometimes it boots up fine, sometimes it boots but doesn't ever find tmo's network, and sometimes it just does the above.
Observations:
1. It will always boot up fine if the SIM card is out.
2. The last time it did it was today while I was at work, listening to music while the phone was charging. Im noticing that the phone gets pretty hot while charging and really hot if you're using while its charging (getting apps, surfing the web, playing games, etc)
So any thoughts from the tech gurus here? anyone have similar behavior in the past on other phones? is the heat affecting the sim card negatively? I can (and have) put my simcard back in my treo 680 backup phone with no issues whatsoever.
New observation, it consistently does the reset process as soon as the "Adjust Time and Date" as it registers/syncs with the network.
UPDATE: so, i did some research, ended up at the setCPU thread and saw that when set to OnDemand some people's phones experienced similar tendencies. Problem is, mine was already set to auto-detect and "Conservative". I un-checked start at boot, and tried again. Same problem. I uninstalled setCPU completely and my phone appears to be back to normal.
I'll update again if anything changes.
so one of the things that i removed during my troubleshooting was my corporate exchange account. When i added it back. it did its initial sync fine and gave me my calendar and contacts. I then rebooted and the problem came back.
I removed the account and rebooted. it went through two cycles of the restarts and on the third one, it worked. I left it alone after that.
I then was showing my friend some things (browser differences) and had 3 browsers open. It froze as i went to close Dolphin HD. Rebooted and now its back to the cycle.
Mine did this also. Installed several apps, woke up to find a slow phone. Resets galore. A quick reset to defaults and app restore fixed it, sans setcpu of course.
From XDA App on SGS-Vibrant
my phone resets itself also as described above, but not really doing anything in particular. i dont have a whole lot of apps installed. i even was using google maps the other day and after it started up the screen went black and the device was unresponsive until the screen came back and it said searching and the media scanner was running.
well first off thanks for responding lol. i thought i was by myself out here.
secondly, i found that if i leave it alone and let it go through its cycle, it does eventually boot up ok (this is recently, before, it was endless). i havent restarted my phone (im afraid to lol) since it did it on its own yesterday (showing my friend the browsers).
since yesterday, i've used it for navigation (motonav), serveral installs, downloaded podcasts, rss feeds, etc and its been ok (even while charging and wifi on). again, havent actually restarted it since yesterday because its actually functioning for once.
Lastly, i unchecked the auto update time and date from network in the settings just to see if that makes a difference because based on previous expereience that is the point where it freezes and resets. Thanks for chiming in and let me know if there's any other advice you have
I'd suggest a reset as mentioned above.
Been checking out this site for awhile but this is my first time posting, today my phone started to have this problem and it just bootloops touchwiz if i have a simcard in the phone.
It works fine without a simcard but my problem is it will not let me turn of auto update of time and date, i have tried disabling this setting and it just enables itself again. I have also noticed that if I started messing around with time and date settings even without a sim touchwiz reloads once. I guess im gonna give a reset a go.
martin0641 said:
Mine did this also. Installed several apps, woke up to find a slow phone. Resets galore. A quick reset to defaults and app restore fixed it, sans setcpu of course.
From XDA App on SGS-Vibrant
Click to expand...
Click to collapse
heygrl said:
I'd suggest a reset as mentioned above.
Click to expand...
Click to collapse
sorry, noob question (i came from winmo and a touch pro 2), what does "a quick reset to defaults" mean? is that like a factory wipe i.e. phone will be brand new again, gotta root again and reinstall everything, change settings, etc?
jblade1000 said:
sorry, noob question (i came from winmo and a touch pro 2), what does "a quick reset to defaults" mean? is that like a factory wipe i.e. phone will be brand new again, gotta root again and reinstall everything, change settings, etc?
Click to expand...
Click to collapse
Root will stick but settings and apps/app data will be gone. It briefs you on what is and isn't lost when you do a factory reset.
Smae problem, its setcpu!
SetCPU with any settings will do this.
It needs an update, the auto detect some how loses and
will set the cpu to 19mhz max and min.
This is too slow to process. I rebooted and pressed settings and uninstalled it
while I could. Seems to behave once out of touchwiz.
For me it was another app not setcpu I never used it. After i did a reset i restored all my apps with titanium backup and once i restarted my phone it looped again. So i did another restore and left off all the apps that i installed right before the problem started and so far i think for me at least one of these caused it
Google maps update
google translate
the extra language pack for translate
barnacle wifi tether
hero of sparta
these are apps that I installed right before the problem happened and without these my phone works fine I am going to see if i can find that one that caused my problem.
It's not the maps update because my phone works fine with it.
It was hero of sparta a gameloft game from there web market funny thing is its suppose to work on the vibrant while dungeon hunter which works fine would only give nexus as a check out option. Anyway im going to try to get a refund tomorrow.
I get the same touchwiz reboot but for me it has only ever happened while using google maps. I do not use set cpu, but I have applied the gps fix. It is more than a little annoying. I have done a system wipe but the problem persists.
Sent from my SGH-T959 using XDA App
yes, if you have setcpu, uninstall it - its buggy with the galaxys
- sometimes you can't wake your phone (if you set a screen off profile), forcing you to do a battery pull
- constant launcher restarts
Judgement5 said:
For me it was another app not setcpu I never used it. After i did a reset i restored all my apps with titanium backup and once i restarted my phone it looped again. So i did another restore and left off all the apps that i installed right before the problem started and so far i think for me at least one of these caused it
Google maps update
google translate
the extra language pack for translate
barnacle wifi tether
hero of sparta
these are apps that I installed right before the problem happened and without these my phone works fine I am going to see if i can find that one that caused my problem.
Click to expand...
Click to collapse
and this is why i started the thread, to make sure i wasnt all alone. i have everything you have installed as well, but it was doing it before i picked up hero of sparta (and nova, and asphalt 5, man those guys make some good phone game lol).
anyways i just installed barnacle wifi tether yesterday so thats not it either (at least for me). That leaves the google stuff, out of the apps in your list, all of which were installed when i first got the problem, and are still on there after I've removed setCPU
heygrl said:
Root will stick but settings and apps/app data will be gone. It briefs you on what is and isn't lost when you do a factory reset.
Click to expand...
Click to collapse
ok so, contacts, text messages, etc stay? Meaning if i do a factory reset, root stays, and all app stuff can be taken care of by, say, AppBrain since it has a running list of everything installed and knows where to get it to install it again? I apprecicate the advice, but this would still be a last resort sort of thing. my phone has worked fine for the past few days but I also havent restarted it yet either
just a quick update, my phone still does this if i reboot my phone (which is never now that i got my 32gb sd card), but for the first time ever hero of sparta caused it to happen while the phone is on. I uninstalled it so we'll see.
hey guys, I don't know what happened but about 30 min ago, every time I try to open Google Maps I get the Force close notification.....anybody have any ideas of how I can fix this? I tried restarting the phone and uninstalling and reinstalling updates but nothing has helped
It's happening to me too. Started about an hour ago. It doesn't happen every time, but pretty often. Since we're not alone, it sounds like google has changed something server side that's sending data that kills the client.
oh pheww.....I thought I was alone lol
not to seem like an a-hole and be happy it's happening to you....but just sayin....haha
Thanks... I was a little worried myself, I installed the wifi tethering mod earlier today and thought I might have screwed the phone up.
Weird! Just started happening to me too. Thanks god for this forum and the search button, because I almost just began the nightmare of trying to figure out which new app or kernel I installed was causing this issue. Guess ill wait now since I'm not the only one. It's probably a Google server causing a problem.....
Same here, just started a little bit ago ... I don't think I can leave the house safely if I don't have access to google maps!$%!
edit: Just a possible fix ... I uninstalled and reinstalled and so far so good...
Are you guys using a modified rom?
Sent from my 1 gigahertz quake 3 playing, Quadrant bustin telephone
I uninstalled/reinstalled didn't help, but if I use WiFi it works fine. Weird.
Me too, except worse - my entire phone freezes up and I have to pull the battery. Not an east or safe thing to do while driving. Started happening about a week ago. Anybody know why?
Forgot to say. Stock ROM on my Vibrant.
shrasmyl said:
Forgot to say. Stock ROM on my Vibrant.
Click to expand...
Click to collapse
Stock Rom here too. Just started doing this to me today also, but only when I use it on the wifi on 3g its fine.
uninstall the google maps update and it will work for now. Google broke it and they will fix it.
Elite GunnerX said:
uninstall the google maps update and it will work for now. Google broke it and they will fix it.
Click to expand...
Click to collapse
Yeah thats what I did.
Same here...Stock Rom started doing this a couple hours ago.
Sent from my Samsung Vibrant
RIP my beloved rooted G1
Same is happening to me...rooted with stock rom. I kind of stop using google maps because of gps issue.
Sent from my SGH-T959 using XDA App
Have you guys tried factory data wipe and reset?
*2767*3855#
I got the crash only when WiFi was turned on . I uninstalled all the updates and am not getting it anymore.
Mine not forcing close, but a black screen "force me to shut down and boot the phone manually".
Everytime I opened google map with GPS on, the phone hanged and I needed to long press the power button to boot..
That is an issue I have seen with lag fix installed...i had to odin back to stock install lag fox then install apps...fixed all my fc issues on stock and other roms...anyways food for thought.
Sent from my SGH-T959 using XDA App
Updated today but still black screen when GPS is on...need to restart the phone manually everytime!!
Hi guys,
Not exactly the most positive of first posts but here we go. There's a problem with my phone that I can't find the solution for...
Essentially my phone randomly turns itself off (no power down sequence, almost as though the battery's being taken out if you know what I mean) and then it has difficulty in fully booting again. For some reason it also likes to revert my wallpaper back to the original as stock.
The first thing that I thought of was malware, with the wallpaper - so I tried a couple of anti-malware apps to no avail. As my device was rooted, I then flashed back to stock, locked and unrooted it and checked the behaviour. Again to no avail (then again I've never rooted/unrooted so this may have been done incorrectly). By the looks of it, the worst case scenario is a problem with battery connections/hardware...
So the question is have you guys come across this before? Is there a solution to this or is Google/LG going to have to give me a replacement?
Many Thanks.
Weird, I just had this happen couple hours ago, I was watching a video and close the app. I press the power button to put it to sleep. Just like 20 second later, I press the power to wake it and it don't do anything. I had to hold the power button to turn it on. I check the battery status afterward and it looks like it drop between 5-10 percent in the chart after it turn on. The battery must have failed or something. This also happen to my wife phone couple weeks back, although she had to do a hard reset(power+volume up and down) it have not happen again though.
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
maintains
kyokeun1234 said:
Hello
First of all, welcome to XDA community!
Now, have you done anything with your phone? As in, root it? Flashed custom kernel? Flashed custom ROM? We would love to help, but you need to provide us what we need
Click to expand...
Click to collapse
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Thrice87 said:
Okay, here's what I had done when this all started:
- Rooted and unlocked.
- TWRP custom recovery
- Standard Kernel, no custom ROM.
I've reverted as much of this back to stock as possible through a nexus tool-kit, but it still has the issue. If I'm missing anything out let me know.
Click to expand...
Click to collapse
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
kyokeun1234 said:
Did this happen before you had the phone rooted? Also did this happen one time only or happened multiple times? I also had this problem, but just turning off and not turning back on part. But that was only one time event and I believe it was because of the custom kernel.
Click to expand...
Click to collapse
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Thrice87 said:
This started yesterday, and I rooted it as soon as I got it 2 weeks ago, so I don't think the root has caused any issues. It's now happening rather often, to the point where it's unuseable
Click to expand...
Click to collapse
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
kyokeun1234 said:
That's odd. Did you download any apps recently that might've caused this issue? Maybe root apps?
Click to expand...
Click to collapse
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Thrice87 said:
The only 2 apps that I downloaded the day before were cerberus and titanium backup, both of which are well known. Either way they were the day before the problems started.
Click to expand...
Click to collapse
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
kyokeun1234 said:
Doubt that these will cause any issues, but could you try uninstalling Cerberus just in case? Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, after completely reverting the phone back to its stock version and pretty much everything else, it's still doing it - which surely points to a problem with the chip (or something). So, I've contacted google about a replacement and so far so good - got through in 5 minutes and sorted out the RMA and everything, should be delivered in the next few days.
Thanks for the help anyway. I'm going to avoid rooting this one for the time being to see how it behaves.
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
hfuizo said:
I experienced "random shutdowns" and even posted about it here. Turns out it was my belt holster that was somehow the culprit. I don't know if it was mashing some weird button sequence to turn off the phone, or if the magnet interfered or something else, but as soon as I got it out of that holster I had no more random shutdowns.
I doubt yours is the same problem but I thought I'd post mine.
Click to expand...
Click to collapse
Yeah that's not my problem at all Lol. Glad you've figured it out and I bet that magnet caused the issue IMO
Sent from my Nexus 4 using xda app-developers app
Funny I had the same thing happen to me last night. I was using the phone put it down for a minute or two and then could not wake the phone. What was interesting was when I couldn't get it to turn on I plugged in into the charger and let it sit for a few hours. When I was finally able to restart it using the the power, vol button the battery was at the same level before the incident. In other words whatever happened prevented the battery from being charged. I am stock and rooted and haven't loaded any new apps in over 2 weeks
Sent from my Nexus 4 using xda app-developers app
I have almost the same problem as the op but I do have a shut down sequence. It does randomly shut down itself. The first thing I got the phone I rooted it and it was fine working on modaco for 2 weeks then one day it kept shutting down upon boot until like 10 tries later I successfully got back in but lasted only a few mins and sometimes hours. Im gonna rma this pos and I hope I can get it replaced soon. I try it with stock rom and kernel then modaco with stock kernel then modaco with faux kernel. Same problem.
I had these problems earlier ... I just gave HARD RESET by pressing power key for more than 5 sec.
Then i figured, it was due to Undervolting ! and Processor going to a DEEP SLEEP all together !
So i removed UVing and it was cool since then ! ... Although my signature says the rest !
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
The same happens several times a week with my nexus 4 running latest cyanogenmod. I will revert it to clean stock in a few days to see how it goes. I don't think that is a hardware problem but time will tell.
MildewMan said:
I bought my N4 about 2 weeks ago, and it has turned itself off 3 of the nights I've had it. I don't have any hard evidence, but I have a theory on why it's doing it.
At first I thought it was because I used a Motorola usb cord instead of the stock cord because I read some people's theories on the internet, but it happened again (twice) after using the stock cord.
It seemed like it only shut off if I left WiFi turned on when I went to sleep (even then it was still a random occurrence). I went into my advanced WiFi settings and noticed Wi-Fi Optimization was turned on with the text "Minimize battery usage when Wi-Fi is on". I thought it might be the problem, so I turned it off. I left WiFi on last night, and the phone was still on in the morning. Again, it is still a random occurrence even with WF on, so I'm going to leave WF on at night for a few days/weeks and see if it happens again. I'll post back with results.
If anyone else has already tried this or has figured out a solution, let me know.
Click to expand...
Click to collapse
Don't know if anyone is keeping up or cares, but I wanted to update and say that this did not fix the problem. 4.2.2 also did not fix the problem. I guess I could try getting a new one from Google.
My wife and I are both having this problem. Hers is completely stock, I'm unlocked and rooted. I was hoping it would be fixed with 4.2.2, but if it hasn't then it maybe time to get replacement N4s
I can't imagine this issue is very widespread, since there have only been a few threads about it. Its a big nuisance especially because it usually happens at night when I'm expecting my alarm to go off at night.
I hadn't wanted to send for replacements since it seems like a software issue but I'm getting fed up.
Sent from my Nexus 4 using xda app-developers app
Just had this problem occur with my N4 last night..... Phone is 2 weeks old.
Went to bed, plugged in the phone to charge [it was at about 50% or so, so not exactly low].
Woke up at 8.30 wondering why my alarm didn't go off at 7.30.... looked over and the phone was off.
It also didn't want to turn back on either. Took about a minute of holding in the power button for various amounts of time before it finally kicked to life [at 100% charge too].
This is going to be a real problem if this problem reoccurs. At home I have a clock radio but I travel a lot and rely on my phone to wake me up!
Here's hoping we can start to identify what is causing this issue. All I can add is that it is not low-battery related.
As stated in the sig. Phone is unlocked/rooted with stock rom.
Hi,
The last couple days my battery had been draining quickly. After having it unplugged for 2 hours this morning, and only listening to music for about 30 min, noticed i was at 95% so looked at my wakelocks. The #1 wake lock is "CacheUpdateService" under google services. It has not allowed my phone to go into deep sleep once. See screen shot. Any help would be appreciated. Just 2 days ago battery was amazing.
530farm said:
Hi,
The last couple days my battery had been draining quickly. After having it unplugged for 2 hours this morning, and only listening to music for about 30 min, noticed i was at 95% so looked at my wakelocks. The #1 wake lock is "CacheUpdateService" under google services. It has not allowed my phone to go into deep sleep once. See screen shot. Any help would be appreciated. Just 2 days ago battery was amazing.
Click to expand...
Click to collapse
Me too, I just found your post in a search for the same issue. I'm going to try a few things and I will post if I fix it...
Noellenchris
Really hope you find a solution to this.
I just tried reflashing CleanRom 1.1, but it did not solve the problem. Granted it was a dirty flash. I'll try a clean flash when i get a chance.
530farm said:
Really hope you find a solution to this.
I just tried reflashing CleanRom 1.1, but it did not solve the problem. Granted it was a dirty flash. I'll try a clean flash when i get a chance.
Click to expand...
Click to collapse
Only thing I found was to toggle the "sync" off then on for the google accounts in the notification pull down on samsung phones. I did that and also cleared cache and dalvik. Problem went away. Give it a shot. I have seen in the past when something like gmail or calendar would hang on sync and a setting it to not sync then back on would fix it. If that doesn't work, I've also actually removed my google account and added it back (fixed another issue in the past). Good luck
Noellenchris
noellenchris said:
Only thing I found was to toggle the "sync" off then on for the google accounts in the notification pull down on samsung phones. I did that and also cleared cache and dalvik. Problem went away. Give it a shot. I have seen in the past when something like gmail or calendar would hang on sync and a setting it to not sync then back on would fix it. If that doesn't work, I've also actually removed my google account and added it back (fixed another issue in the past). Good luck
Noellenchris
Click to expand...
Click to collapse
Thanks for the info. I ended up doing a factory reset then reflashing cleanrom. Seems to have solved it. If it coms up again I'll give your tips a try.
I have awesome battery life. I disabled Google now and never looked back. Also disabled wifi location services. My second charge I got 43 hours off charger and 5 hours of on screen time and had 9% left. Check the battery review thread that's somewhere on these G2 forums for tips.
Had this issue on my G2. After much frustration, i ended up uninstalling google play services with titanium backup, then reinstalling them. To reinstall them, I uninstalled a google play app (google play music in my case) and reinstalled it. The play store then had me install google play services from there.
Sleeping like a baby since.
I have the same problem. Tried everything from factory reset to uninstalling Google Play Services, but no luck. Did anyone have any other solutions? My phone doesn't go to deep sleep ever.
I have been so impressed with the battery power during usage so I tried 2 nights in a row to let it sit and see how the battery was over night. Each morning shocked to see 15% gone in 8 hours. Granted I have seen worse in the past with GS3 but still I am listed as it was awake the whole time. And the listing under Gsam is cacheupdateservice. every google app is unchecked in account and my gmail account is set to sync off. My regular email account is set to sync but only on manual. I do have access my location on with wifi and mobile location checked. I'll try unchecked. Any other help is always appreciated. Thanks
I had/have the same issue. The phone will NEVER sleep. I went into task manager and force stopped and cleared cache on almost all apps. Went to manage apps and cleared all data and cache in google play services yesterday after noon. Perfect for a couple hours. No cacheupdate service listed in gsam. checked back a little later and there it was again. Not sure at all what I did to trigger again. I then did the same thing and let it sit over night. Lost only 4 percent in 7 hours. So far have changed wifi and mobile locations on the way to work to work, checked email and surfed the net. So far so good.
Has anybody made any head way on the cause of this. If I clear the cache and data for Google services and force stop I am good for as much as a day sometimes with none of these wakelocks. Then they are back. I have tried a bunch of stuff with no true fix yet. I uninstalled the updates and no wakelocks but I keep getting messages telling we it needs to be updated. Any in sight would be greatly appreciated. Thanks
I don't have a G2, but I have the exact same issue on my Moto X...I tried searching a lot for this issue and no one seems to have a good solution (wipe cache, dalvik etc has not helped me).
Ultimately what I have done is install this app (phone needs to be rooted), then select System Apps ->Google Play Services and disabled CacheUpdateService. I haven't seen any side effects of this yet, but I am not sure if there will be any....Can someone else who is rooted give it a shot too and see if things improve?
App is called Disable Service
https://play.google.com/store/apps/details?id=cn.wq.disableservice
tejaskary said:
I don't have a G2, but I have the exact same issue on my Moto X...I tried searching a lot for this issue and no one seems to have a good solution (wipe cache, dalvik etc has not helped me).
Ultimately what I have done is install this app (phone needs to be rooted), then select System Apps ->Google Play Services and disabled CacheUpdateService. I haven't seen any side effects of this yet, but I am not sure if there will be any....Can someone else who is rooted give it a shot too and see if things improve?
App is called Disable Service
https://play.google.com/store/apps/details?id=cn.wq.disableservice
Click to expand...
Click to collapse
Suffering from this on my Nexus 4, will download this app and give it a shot.
Sent from my Nexus 4 using Tapatalk
On 10/17/16 I took the OTA to take me from the July Security patch to the September security patch, with build number G935TUVU4APIA.
With in the first day of the update I experienced the phone freezing on the home screen, then rebooting. Later on I found it had rebooted while in my pocket (prompted for pin and system up time was minutes). Ever since over past 6 days it has become frozen and rebooted multiple times a day. Anywhere 2 to 5 times a day doing various different things.
I have tried clearing all system and app cache since after the update. Unfortantely that has not helped at all. So what I would like to know is anyone else on this build experiencing these reboots, or was before and fixed it?
I'm trying to determine if its a bug with this build, cause I will be really annoyed if I have to go through the trouble of a factory reset, then find out it didn't help cause its an issue with this specific build. If some other stock people can confirm this build is not rebooting for them I will give factory reset a try.
AndroidPurity said:
On 10/17/16 I took the OTA to take me from the July Security patch to the September security patch, with build number G935TUVU4APIA.
With in the first day of the update I experienced the phone freezing on the home screen, then rebooting. Later on I found it had rebooted while in my pocket (prompted for pin and system up time was minutes). Ever since over past 6 days it has become frozen and rebooted multiple times a day. Anywhere 2 to 5 times a day doing various different things.
I have tried clearing all system and app cache since after the update. Unfortantely that has not helped at all. So what I would like to know is anyone else on this build experiencing these reboots, or was before and fixed it?
I'm trying to determine if its a bug with this build, cause I will be really annoyed if I have to go through the trouble of a factory reset, then find out it didn't help cause its an issue with this specific build. If some other stock people can confirm this build is not rebooting for them I will give factory reset a try.
Click to expand...
Click to collapse
Idon't have this build installed yet but the previous one and had the same issue, turned out to be my alarm clock plus app causing it to reboot on an alarm.
Sent from my SM-G935T using Tapatalk
Shrubby said:
Idon't have this build installed yet but the previous one and had the same issue, turned out to be my alarm clock plus app causing it to reboot on an alarm.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
Dang that sucks, worse time for it to fail when its supposed to wake you up lol! Thanks or the suggestion but I don't think its app related since it happens on home screen, in app drawer, in chrome, and in my pocket with screen off. Unless its an app in the back ground. But I haven't installed any new in past 5 days apps that I would say are uncommon that aren't supported well.
Edit: I just checked. Since the OTA I did install 1 app the day after. The Nexia app for smart thermostat that came with my new furnace. I don't think thats it since I can recall at least 1 reboot after the OTA and before that app. But just in case I will uninstall that app for a couple days just to test. Thanks!
Shrubby said:
Idon't have this build installed yet but the previous one and had the same issue, turned out to be my alarm clock plus app causing it to reboot on an alarm.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
I use I cant wake up alarm clock and experience that too. I am rooted but still keep the alarm clock because it rearms on reboot and still works. so no biggie for me
Sent from my SM-G935T using Tapatalk
I had a serious freeze/lock up last night. I am on the same build and NOT rooted. I even tried holding down the power button and the phone was unresponsive. Cap. keys stayed lit the whole time. After holding down for 45 sec or so it finally relented and rebooted. But this combined with random heat surges/ups really have me pissed.
Had the same issue. On u firmware now cuz i couldnt take it. One thing that seemed to help some was removing the sd card and wiping cache then rebooting. I let it run for a few hours then put in sd card. Seemed to help alot
I'm back to follow up with the results from uninstalling the only app I installed since the update. It actually almost went 24 hours without a freeze and reboot. I was starting to think it actually was the culprit. But then I had 2 freezes and reboot today. ��
So I have switched back to my Nexus 6P for a while. Thanks to those who also reported the same issue! Since other people are reporting the same issue it seems to be a bug in this build unfortunately. So here is to Samsung pushing out a fix soon. Until then I will be using my 6P. If they haven't fixed it in a couple weeks then I will probably flash to the U firmware too. What variant is the U firmware from anyways? The unlocked North America variant?
I installed the update and have been running it for the past four days with no problems to report thus far. If I get a reboot or any freezing I'll let you folks know. Perhaps try a factory reset.
Sent from my SM-G935T using Tapatalk
I get a reboot twice a day. Sometimes the phone will freeze while I'm scrolling through my internet browser or it will reboot if I'm using the SAMSUNG branded car charger and Google Maps at the same time. Other times it'll just randomly reboot out of nowhere.
This is extremely frustrating. T-Mobile recommended that I get an exchange and I did get an exchange and the same day it rebooted on me. I called complaining that it's not a hardware issue and they told me to exchange the phone again. Smh.
This sucks especially since I use GPS a lot. This phone was/is perfect before the update.
Sent from my SM-G935T using XDA-Developers mobile app
OuncE718 said:
I get a reboot twice a day. Sometimes the phone will freeze while I'm scrolling through my internet browser or it will reboot if I'm using the SAMSUNG branded car charger and Google Maps at the same time. Other times it'll just randomly reboot out of nowhere.
This is extremely frustrating. T-Mobile recommended that I get an exchange and I did get an exchange and the same day it rebooted on me. I called complaining that it's not a hardware issue and they told me to exchange the phone again. Smh.
This sucks especially since I use GPS a lot. This phone was/is perfect before the update.
Click to expand...
Click to collapse
Yeah... Carriers need to train their employees to be able to know how to tell the difference between a hardware and software issue. For example if a user reports something didn't happen until a recent update, then that should be an automatic sign to not waste that customers time with a pointless exchange.