Hi guys
My phone's clock seemed to loose 3 hours in the night. I woke up this morning and the clock was saying 3:50am when actually it was 6:50am, I was nearly late for work. I checked the clock and alarm before I went to bed and it was correct. Any idea what could cause this? I have SPB Time installed, but it's been working fine for over a week.
Just a bit wary of trusting it as my alarm clock now!
Cheers
The same problem with mine, any help?
clock loses -5 hour a day
Have the same problem!
Any suggestions?
Kallisto
And i thought only my phone was going nuts.. I had this problem some time ago, did a hard reset and clock is working fine now...
Hi!
I have noticed that my Diamond wakes up after some time while being stand-by (sleeping). The screen comes to full brightness and then after 30 sec turns back to sleep. And this is every time I put my phone to sleep / or itself goes sleep.
Has anyone had same problem ? Any suggestions? Fixes?
I havent running any applications, only some today screen plugins like Today Launcher, Wifi/Bluetooth/Phone toggler, Key Lock.
I have no idea what is causing this problem. I am afraid that this causes my battery to tray a lot faster.
Also the screen doesn't self-wake-up right away, but after some time ~ 20 - 30 sec
Have you found a solution? I have similar problem, but mine wakes up not so often. I've noticed that it wakes up several times during the day and night. Sometimes when it wakes up it is only once, but sometimes it keeps doing this every minute. Besides the fact it drains the battery too quickly, this drives me crazy.
ROM version is: 2.03.401.3 WWE
Radio version: 1.09.25.23
Protocol version: 52.51.25.26H
Any ideas?
Hello deer XDA friends
My phone suddenly shut down by it self every 3-4 days sometimes when the battery above 50% , when i try to booted up it wont until i remove the battery then it start normally .
what do you think is the problem here?
sorry my English is very bad
Eltoro2010 said:
Hello deer XDA friends
My phone suddenly shut down by it self every 3-4 days sometimes when the battery above 50% , when i try to booted up it wont until i remove the battery then it start normally .
what do you think is the problem here?
sorry my English is very bad
Click to expand...
Click to collapse
You might have some rogue apps running that overheat the cpu. Look in taskmanager which apps are using much power. Download cpu spy free from the market to see if the cpu comes in deep sleep or not.
Good luck
I also have it occasionally. POWER+HOME button to reset. One time need to remove battery. Actually I felt like phone is still open but screen cannot come back. Next time I will call my phone when it happens.
I've had this happen twice. Both times a battery pull fixed it. At first I thought the phone was going dead, completely black and the power button would do nothing, but the second time I hit the volume button several times and it started beeping, so even though it looked completely dead, it was still turned on. I don't know what the problem is, but probably something software.
Which ROM/kernel are you using?
Any special CPU profiles?
How's the temperature?
Sent from my GT-N7000 using XDA App
happened a few times too. So, last time when I found it "dead" I did some test.
1. used my bluetooth headset (MW600) tried to play music, surprisingly music started playing but screen cannot turn on by any keys.
2. I called myself using another phone, Caller can hear ring normally and the call NOT dropped to voice mail, however my Note doesn't ring at all, screen still cannot turn on by any keys.
So it doesn't look like it's auto switched off by overheating, seems like unable to completely wake up after deep sleep.
Phone using Stock Rom(rooted with CWM), with System Power Saving mode turned on. I suspecting it's related to the power saving mode.
I'm also stock 2.3.5 rooted, with CWM, but do not have system power saving turned on. I haven't noticed any heat, but haven't monitored temperatures.
Do you also have the stock kernel?
Are you using setCPU?
Try using cpuspy, from market.
Sent from my GT-N7000 using XDA App
Dead
I also had this case yesterday for the first time. I bought it the 30th november.
Did not want to wakeup, darkscreen. Only way to recover was to remove battery. I am on 2.3.6 french.
I do not use Setcpu.
Mine is unroot. In other words, stock ROM and kernel.
I think it is software problem. And I think it is either Samsung software or Android system. Someone need to run logcat though.
For your information.
When you sure it's sleep dead(not shutdown cause by no battery)
Disconnect any charger/USB connected. Press and hold the power switch for around 10-15 sec,
that will restart the phone, no need remove that inconvenient back cover for battery pull.
alexchan.ccs said:
For your information.
When you sure it's sleep dead(not shutdown cause by no battery)
Disconnect any charger/USB connected. Press and hold the power switch for around 10-15 sec,
that will restart the phone, no need remove that inconvenient back cover for battery pull.
Click to expand...
Click to collapse
The first time it happened to me I tried holding the power button but it didn't work, so I did the battery pull. I haven't tried again since then.
Sudden Shutdown
Mine too i've experience it 3 times, this happen when im opening some applications sudden black screen and restarted cannot access back button, haven't tried the power button. It just restarted thats it!!! Im at stock kernel unrooted 2.3.6 so what do you think guys should i root or just wait for Ice Scream Sandwich upgrade?
maxh said:
The first time it happened to me I tried holding the power button but it didn't work, so I did the battery pull. I haven't tried again since then.
Click to expand...
Click to collapse
See if you hold the button long enough for over 10 seconds, before I would release and think power button not work after 7-8 seconds.
I have experienced "sleep of death" many times on different firmware versions. I has never happened since I flashed KL3. I'm on AbyssNote 2.1 kernel.
update:
since I replaced the stock launcher & locker, no more sleep dead issues. I suspect the problem source is stock locker or some stock widgets. Also, battery last longer too.
now using: widget locker + awd launcher ex + multi-picture live wall paper.
For those wonder why phone can't wake up for some reason, a user at the green power app forum had got the solid evidence.
http://greenpower.pouzerate.com/ind...-s2-freeze--black-screen?limit=6&start=48#465
"And if then it looks like the touchwiz launcher has crashed and changed pid when restarting without telling the InputManagerService about it, so it can't wake up the screen for that reason."
So the culprit is the stock launcher. And this matched with my experience even after I uninstalled green power free, my phone still have "not waking up" problem . But since switched to use 3rd party lock and launcher for a month, the "not waking up" never happens again.
This happened to me for the first time yesterday, when I eventually got it restarted by removing the battery, it was at 88% so don't think it was overheating, otherwise it would be much lower. Also I had Go launcher Ex running so touch wiz unlikely to be the culprit. Maybe some widget, I have loads!
alexchan.ccs said:
For those wonder why phone can't wake up for some reason, a user at the green power app forum had got the solid evidence.
http://greenpower.pouzerate.com/ind...-s2-freeze--black-screen?limit=6&start=48#465
"And if then it looks like the touchwiz launcher has crashed and changed pid when restarting without telling the InputManagerService about it, so it can't wake up the screen for that reason."
So the culprit is the stock launcher. And this matched with my experience even after I uninstalled green power free, my phone still have "not waking up" problem . But since switched to use 3rd party lock and launcher for a month, the "not waking up" never happens again.
Click to expand...
Click to collapse
This actually fits well with my experience. Touchwiz crashes on me occasionally and just last night I was experiencing the sleep of death thing. This time I thought it might have been the battery, so plugged in the charger and that somehow woke the screen back up to show touchwiz in the process of starting up, caught red handed!
This has happened to me as well 3 times, and every time it has been related to using a highres picture on the stock locker. It would lag out on unlock, black screen of death, which i would have to batt pull to fix. Didn't realize i had to hold down the power button for 15 secs to achieve the same thing. Have since switched to a low res pic on lock screen and haven't experienced the issue since. Will try the alternative locker solution if it happens again.
So here's the deal. Wasn't getting great idle drain but figured I'd give it a while to see if it worked itself out. It hasn't. Took my phone off the charger and slept for less than 8 ours and loss almost 16% about 2% per hour.
I had wifi on. Blue tooth off. gps off. i have greenify stopping my voicemail and facebook app. I have about 60 something apps frozen. Android OS took up most of my battery life as you can see in pictures. Went to partial wakelocks and saw email at 30seconds but there are only like 45 secs of partial wakelocks so not that big of a deal. Noticed that better battery stats said my phone was awake for almost an hour (I was on it for 10 minutes looking at stuff which is why the screen on pic saus about 10 minutes, the screen wasn't on at all from unplug to me waking up). Noticed under kernal lock that something was keeping stuff on for almost an hour.
So why on earth was my phone on for almost an hour of the 8 hours i was asleep? Further, why does my battery drain look like it was pretty consistent over that time even though the phone was on for an hour. It makes me think that it continuously must be turning itself back on. I know that wifi is the problem for some people but I figured that I would be able to see that in partial wakelocks yet it isn't there. I can try changing wifi stuff if some sees something showing that it is wifi issues.
Otherwise, maybe i should return the phone???
So , I would say that the main issue is your mail service process. It woke up 184 times, every time it wakes its going to keep the phone awake for a little before the phone completely goes back to sleep. it is work related i assume?
anotherfiz said:
So , I would say that the main issue is your mail service process. It woke up 184 times, every time it wakes its going to keep the phone awake for a little before the phone completely goes back to sleep. it is work related i assume?
Click to expand...
Click to collapse
yes that mail account is work and there is an account for my school. It is the email apk that bypasses security that plenty of other people are running. Do you think that it is an account issue or the Email.apk? So the 180 wake ups only totaled for 30 something seconds of partial wakelock. Is it not showing upas a partial wakelock and that is why the phone says that it was on for so long?
also, I read that something having to do with wifi and the qcom_rx_wakelock cause severe battery drain. Know anything about that.
So, yes, the app only worked for 33 seconds because each wakelock probably required only a few milliseconds to do what it needed to do.. but the phone does not go to sleep instantly after each wakelock. so for each of the 184 times that app woke your phone up, it was "awake" for 5-15 seconds or however long it takes the phone to decide its time to go to sleep again. Awake time for me is almost always a function of screen time, like 1.5x - 2x my screen time.
anotherfiz said:
So, yes, the app only worked for 33 seconds because each wakelock probably required only a few milliseconds to do what it needed to do.. but the phone does not go to sleep instantly after each wakelock. so for each of the 184 times that app woke your phone up, it was "awake" for 5-15 seconds or however long it takes the phone to decide its time to go to sleep again. Awake time for me is almost always a function of screen time, like 1.5x - 2x my screen time.
Click to expand...
Click to collapse
so any idea on a solution besides setting up for my email to only check every half hour. It is set to push right now. Given I don't need it at night really and i can set something up to change when it is allowed to check for emails. But sometimes I am up at 2 because I get an email that requires me to do work. Also, the qcom_rx_wakelock that kept m phone on for 32 minutes or something doesn't seem to have to do with the email. But maybe when the email tries to access the internet that wakelock runs to try to get wifi...
edit: I did more research on the qcom_rx_wakelock. I still don't understand it all but it is some issue that the 4.2.2 update came with. It causes major battery drain on some wifi networks and not on some others. It has to do with the wifi connection continuously having to talk to the router and waking the phone up which is also tied to some apps that are syncing. People on nexus's have created patches that fix the issue, but I don't think I'm going to be doing anything like that. I PMd a member to try and get more information.
For now I have two routers at my house and will be switching to using the other router for my wifi connection on my phone to see if it creates the same battery draining issues while in sleep. If I get any more information I will update again. I also think this could explain a lot of the reason that some people are experiencing sub-par battery life while others are getting great battery life. Depending on what router (work, school, home, public place) you are on might make the phone constantly turn itself on and off trying to reconnect or do something with that wifi network. I know many people have had 15 to 20% battery drain overnight then turned wifi off and just stayed on 3g/4g connection and battery drain went to 4 to 5% over night. FYI
I just got the Moto X and have a few things installed. My question is, in the battery mete graph you have screen on and awake. Is the awake always supposed to be on? I'm guessing it is since it has the touchless controls always listening.
Figured why it won't go to sleep. Has anyone ever had it where the phone app gets stuck and stays awake? Only way to get rid of it for me is to reboot.
Stock MM, rooted/Xposed/TWRP.
If I leave my phone sitting face up on my desk, sometimes the screen will come on for about 1-2 seconds for no apparent reason. It's not a full wakeup, because the screen times out really quickly.
It seems to be random, it only seems to happen a couple times a day.. honestly it's usually in my pocket so I wouldn't see it, so I'm not really sure how often it happens. So far it's happened twice in the 4 hours or so I've been sitting here.
I have all that "wave-over" stuff turned off.
I seem to remember it happening with LP too.