So I was out running today, and I had My Tracks running, as well as listening to music with Apollo, and after three miles I had to battery pull because my phone had gone into a deep sleep. I've never run into this before, and the only thing different is My Tracks--fired it up for the first time today. Has anyone run into something similar? Running CM10 7/31 build.
Related
I am running Caulkins Rom 1.1 with Clemsyns kernel version 5. I was continually having problems with the tablet not waking from sleep. I have searched and read till I was blue in the face.
I decided to try the long tedious method to troubleshoot this. I did a complete wipe and reinstall without installing any other apps and lo and behold no problems with sleep. I then began installing my 30 or 40 apps one at a time to see if any of them would affect the wake from sleep as I had read on other threads.
The very first app I installed was Fancy Widget. I put the tablet to sleep waited about 10 minutes and it would not wake up without a reboot. So I uninstalled Fancy Widget and sure enough no problems.
Next I tried an app called Gizmo for streaming music from my home PC. It would play one or two songs and then stop and sure enough not wake from sleep. I then tried changing the setting to keep the wifi on at all times in settings. This did not help. I am now trying Wifi Keep Alive but that just quit also and had to reboot.
It appears with just the first two apps that I tried that the tablet is actually locking up when an app tries to access the wifi during sleep. It is not actually shutting down but rather just freezing as it continues to use battery and you have to do a long press on the power button to force a reboot.
Without these apps the sleep function works great. The streaming apps are kind of a pisser though since I would really like to listen to music.
Is there a way to disable sleep completely? Can anyone test out Fancy Widgets and see if it causes them the same problem?
Todd
I can second this wifi sleep theory. I haven't had any sleep of death issues since I changed the wifi sleep policy to "never". I honestly didn't connect it since I did so after flashing a new rom. But now that you say that, I'm remembering if I had Pandora playing when the screen shut off, I couldn't wake the screen up unless I reset it, but the music would continue playing until I rebooted. Maybe some other folks would be willing to set their wifi sleep to never and report back? I'm on Calkulins ROM btw.
EDIT: In case you aren't sure how to change this. Settings>wireless and networks>wifi settings>advanced settings>wifi sleep policy
After further testing here is what I have come up with.
Fancy Widget definitely causes a freeze.
Streaming music seems to only freeze when I am streaming to my bluetooth speaker. I have had Gizmo running for almost an hour now playing just through the Gtab speakers and it is fine. I even tried streaming to the bluetooth speaker with the screen set to never shut off and it completely froze the Gtab. I had to hard reboot with the power button.
So I am back to trying to troubleshoot bluetooth problems which I have had no success in doing. I have posted bluetooth questions a couple of times and gotten no responses.
Any bluetooth gurus out there?
Vegan 5.1.1 + Clemsyn's kernel v7 here. No sleep of death or anything. The gtab now runs incredibly fast.
goodintentions said:
Vegan 5.1.1 + Clemsyn's kernel v7 here. No sleep of death or anything. The gtab now runs incredibly fast.
Click to expand...
Click to collapse
TNT Lite 4.4.0 just got Clem's v7 - so far, so good.
roebeet said:
TNT Lite 4.4.0 just got Clem's v7 - so far, so good.
Click to expand...
Click to collapse
Wooter here.
Clem's 7 fixed the sleep issue on my new gtab. Oh yeah, using you're (roebeet) TnT 4.3 mod (thanks), when did you release 4.4?
I have no sleep issues now except for the above mentioned. My battery life is awesome now as well.
I solved my streaming problem by buying a 6 foot 1/8 to 1/8 cord and plugging in my speaker. Kind of defeats the purpose of buying a wireless speaker but it works
Interesting. Not positive but I think my sleep issues started after I installed Fancy Widget. I'll uninstall and report back.
No Fancy Widget and so far so good.
Anytime I'm listening to music my battery dies extremely fast. I also notice that the back of my phone gets hot too... Next time this happens ill upload a screenshot of the battery usage
Sent from my Desire HD using XDA App
Happens to me too. Its the app though. When running music for example the newest release of Google Music player. You can check the partial wake status of apps through the Spare Parts app. This shows what apps are awake while you phone is in sleep mode. When listening to music for 2 hours or so, it will show that the music player has been in partial wake. So its just like leaving your phone on for 2 hours straight. And on top of what ever else is running. You can try finding other music apps to see if the issue still exists.
As for you phone getting hot. Could be a battery issue. Could be an overclock issue or undervolt issue.
Hopefully that helps you determine what is causing these issues.
Draining
This happens to me too. When I use GPS alot and Music. Each rom seems to have a different effect with the draining, so I would suggest getting feedback from the DEV.
Hey guys,
I experienced very weird battery behavior tonight.
Before I went to sleep I listend to an audiobook for a bit, played some towerdefense and the battery went down to 88% before I set it to Airplane mode, activated my alarm for the morning and put it on my nightstand.
Usually the battery will drop by less than 5% until morning, which would be expected.
But today when I woke up, battery stats read 35%.
You can imagine that I was quite surprised.
Images are attached.
One thing I also changed (I just remembered) before I went to sleep:
I got rid of the Poweramp widget and put the regular HTC Music widget on my screen, listened to 2 songs to see if it sounded alright, then stopped playback and put it down.
So the only thing that I can imagine right now is the regular Music widget keeping the phone active although no music is playing.
ROM is ARHD 6.2.1 - is this ROM specific?
Help appreciated.
I could be wrong but it looks like something is preventing your phone from sleeping. Go to terminal and type the following 2 lines. You can also run it from adb shell too. Toward the bottom will show some wakelock lines.
su
dumpsys power
Here is a sample from my phone when it had a wakelock issue.
PARTIAL_WAKE_LOCK 'MediaScannerService' activated (minState=0, uid=10014, pid=4932)
Code:
Power Manager State:
mIsPowered=true mPowerState=0 mScreenOffTime=263861 ms
mPartialCount=0
mWakeLockState=
mUserState=
mPowerState=
mLocks.gather=
mNextTimeout=294581118 now=294852985 -271s from now
mDimScreen=true mStayOnConditions=0 mPreparingForScreenOn=false mSkippedScreen
On=false
mScreenOffReason=3 mUserState=0
mBroadcastQueue={-1,-1,-1}
mBroadcastWhy={0,0,0}
mPokey=0 mPokeAwakeonSet=false
mKeyboardVisible=false mUserActivityAllowed=false
mKeylightDelay=6000 mDimDelay=32000 mScreenOffDelay=7000
mPreventScreenOn=false mScreenBrightnessOverride=-1 mButtonBrightnessOverrid
e=-1
mScreenOffTimeoutSetting=45000 mMaximumScreenOffTimeout=2147483647
mLastScreenOnTime=0
mBroadcastWakeLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mStayOnWhilePluggedInScreenDimLock=UnsynchronizedWakeLock(mFlags=0x6 mCount=0
mHeld=false)
mStayOnWhilePluggedInPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mH
eld=false)
mPreventScreenOnPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=f
alse)
mProximityPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mProximityWakeLockCount=0
mProximitySensorEnabled=false
mProximitySensorActive=false
mProximityPendingValue=-1
mLastProximityEventTime=143525904
mLightSensorEnabled=false
mLightSensorValue=-1.0 mLightSensorPendingValue=320.0
mLightSensorPendingDecrease=false mLightSensorPendingIncrease=false
mLightSensorScreenBrightness=142 mLightSensorButtonBrightness=0 mLightSensorKe
yboardBrightness=0
mUseSoftwareAutoBrightness=true
mAutoBrightessEnabled=false
mScreenBrightness: animating=false targetValue=-1 curValue=104.0 delta=0.0
mLocks.size=0:
mPokeLocks.size=0:
That's what the shell command gives me.
The important line is toward the bottom. mlocks.size = 0 just means there is no current process that has a wakelock state. What this means is a process was running at some point, enabled a wakelock, and the process exited without removing the lock. Figuring out which process is a problem since there isn't much to go on. The only thing I might try is run the command below in terminal and monitor the wake_count column. The output is a little messy but excel formats everything into nice columns.
cat /proc/wakelocks
Since the only thing that I've done differently than well... ever, was using the original HTC Music player.
I guess there's a bug with the ARHD ROM and the stock player that keeps it active even though nothing is playing.
I'll just stay away from it and use Poweramp instead.
sorry, ive been looking around and I see in the Liquid Rom thread that it has a SOD problem. I looked around for a bit and i couldn't manage to find what it stands for. I think i might have it because sometimes when i turn my screen on, the touch response doesn't respond. I have to turn off my screen and turn it on again to make it work. I'm unsure if its a aosp problem cause i don't remember getting this problem in Sense
It stands for sleep of death, so it is a deep sleep problem.
Its not an AOSP problem, Ive never had it on Dark Jelly CM10 at least.
SOD stands for Sleep Of Death like the above poster said, and can result in a number of things.
The TF101 was plauged by SOD, and on that device sometimes the screen wouldnt turn on after a deep sleep. It also did random reboots during deep sleep and hanged at the boot sequence - draining the battery in no time at all. That was very frustrating.
A workaround for the TF was to use an app that woke the device up every now and then, so it didnt deep sleep for long periods of time. It drained the battery a bit faster, but it was quite ok.
Personally I worked around it by never letting wifi turn off - even during deep sleep, then set up some task that used wifi such as weather updates every 30min, msn, rss feeds etc.
Basically, SOD is commonly used when you wake a device up and it doesnt act as it should and forces you to reboot/remove battery/wait for battery to drain/etc
I have a Droid 4 running the Unofficial CM11 ROM. I've been using this ROM for a few months now, mainly without issue. Only recently, for some reason, I am getting these uncontrollable wakelocks that cannot be plugged.
http://imgur.com/a/9wSYW
Using BBS, I see that I am having issues with GCM_CONN and GCM_CONN_ALARM. They will not allow my phone to sleep. I am using Amplify and Wakelock Terminator, both set to block these guys, but it's not enough to let the phone go into Deep Sleep.
I also heard about Deep Sleep Battery Saver, and I've downloaded that in an attempt to force the phone into Deep Sleep, but that hasn't worked at all as you can see.
Has anyone had any experience quelling wakelocks of this magnitude before? I cannot seem to figure out what is preventing the phone from going into a normal sleep rhythm.