On every rom based on lineage I have had pretty much constant awake time even thru the overnight hours and with greenify aggressive doze. I've tried just about all I can think of, I'll lose about 7 or 8 percent overnight where on stock it's around 3 percent
Is anyone else experiencing this? Is it common? Also the only thing to come up on wake lock detector is a Google service on wake up triggers
Any insight would be appreciated.
I don't know if it applies to all ROMs, but make sure you delete the systemapp for NFC. It's likely trying to communicate with your nonexistent NFC chip. I noticed my phone would never enter deep sleep, deleted it, and now it enters deep sleep seconds after shutting the screen off.
username8611 said:
I don't know if it applies to all ROMs, but make sure you delete the systemapp for NFC. It's likely trying to communicate with your nonexistent NFC chip. I noticed my phone would never enter deep sleep, deleted it, and now it enters deep sleep seconds after shutting the screen off.
Click to expand...
Click to collapse
I'm trying to locate it, found the around nfc app but it doesn't come up in titanium
I used Link2sd to unistall it. It's called NfcNci.apk. once i unistalled it, the phone went to sleep.
isTos said:
I used Link2sd to unistall it. It's called NfcNci.apk. once i unistalled it, the phone went to sleep.
Click to expand...
Click to collapse
Worked like a charm. Thanks!
This def fixed my deep sleep issues. Thanks!
Here's a flashable zip you can use to remove NFC. I made it for use with ROMs that have a built in updater with a flash after update feature. This way ROM updates won't re-enable NFC. Tested it on AospExtended but should work on other ROMs as its designed to just remove the NFC apk from system.
Flash from recovery:
https://drive.google.com/file/d/0B3WSJXjA-ygYUjNoZ3F3c0VIWDg/view?usp=sharing
I did not create this zip but edited one that I found from here:
https://forums.oneplus.net/threads/flashable-zip-to-remove-apps.419810/
Related
My phone is not sleeping itself down after the time elapses.anyone else noticing this, its making me think its draining my battery.
Just tested this myself, and on a one minute sleep timer, my phone did properly go to sleep.
Mine sleeps fine too.
mine sleeps fine as well. Do you have any particular app running? For example, if you have AT&T Navigator running it will not sleep. There are a few other apps that provide the ability to prevent it from sleeping. So, are you on the main screen or in an app when it doesn't sleep?
Cannot say I've had this problem. Worked at its default of 1 min, and still works after I changed to 3.
I am trying to id the app if any that is causing it but with no task manager its impossible.
I do notice an issue with the camera app. If the camera button gets pressed then the phone will stay on and not sleep, for me at least.
It goes off on it's own mostly...thanks for the reports as I work through this. I may need a hard reset anyway, hey why not Ill add a microSD at that time.
Hey guys,
i am on latest CM9 quarx build..but my phone is not going into deep sleep atall
it says 0% deep sleep in CPUspy...tat has become a headache..i was on epi CM(..there also it had come problem..then installed latest quarx build..then it was going into deep sleep unto few hrs ago..now it says 0% deep sleep.
I cant few detailed battery drinking info on ICS unlike GB..
Any help would be appreciated name of the app..or advice..or any kind of help will do..
Thank you
Try editing your build.prop and adding
Code:
ro.ril.disable.power.collapse=1
Don't know if this will help , but in the event that it doesn't , try ending processes before locking the phone , or use some system analyzer to see what app is stopping deep sleep
Herpderp Adreno + Tegra.
thanks but i did a full data wipe and reinstalled everything from scratch..later restored apps with the help of titanium backup
its pain in the ass to do everything from scratch...anyways if still i face this problem then will report back..anyways could anyone suggest me some apps which can findout which app or process is the culprit?
Try this one:
http://forum.xda-developers.com/showthread.php?t=1179809
I had the same problem on CM7 120126.2206, and it turned out that Google Maps was the culprit. However, I discovered that Google Maps doesn't prevent the phone from going into deep sleep when the GPS is disabled. Try disabling GPS whenever you're not using it, and see if that helps.
Edit: after further testing, it seems that Google Maps may not have been the culprit after all, or I may have more than one problem with deep sleep. Occasionally the phone gets locked out of deep sleep even when GPS is turned off; yesterday it failed to enter deep sleep even while the phone was untouched for 4 hours. The "BetterBatteryStats" app indicated listed "wifi_wake" under Kernel Wakelocks as the primary culprit. Disabling then re-enabling wifi solved the problem, at least temporarily.
I had my phone on today and after about 13 hours of being on with less than 15 mins of screen time, I noticed it was awake for all 13 hours. Also, I don't know why, but even being rooted I am unable to view Alarms in BetterBatteryStats.
If anyone could look at my log and offer any insight on the problem, it would be highly appreciated.
jsilvermist said:
I had my phone on today and after about 13 hours of being on with less than 15 mins of screen time, I noticed it was awake for all 13 hours. Also, I don't know why, but even being rooted I am unable to view Alarms in BetterBatteryStats.
If anyone could look at my log and offer any insight on the problem, it would be highly appreciated.
Click to expand...
Click to collapse
Some service is holding a wakelock while accessing the modem. Either that service crashed/hung without releasing the wakelock, the modem didn't respond, or there's simply a bug in the code. I would reboot and see if it happens again. If so, think about which apps you installed directly before this started happening. If you're running a custom ROM/kernel, this could be the root of the problem. With the BetterBatteryStats log alone, there if no way of telling this
XDA_Bam said:
Some service is holding a wakelock while accessing the modem. Either that service crashed/hung without releasing the wakelock, the modem didn't respond, or there's simply a bug in the code. I would reboot and see if it happens again. If so, think about which apps you installed directly before this started happening. If you're running a custom ROM/kernel, this could be the root of the problem. With the BetterBatteryStats log alone, there if no way of telling this
Click to expand...
Click to collapse
Thank you for the response, as far as I can tell it was caused by an edit to the hosts file, since reverting the hosts file back to default (only localhost) seems to have fixed the problem.
Like the title says, my phone stops going into deep sleep about 3 days after a reboot. I need to reboot the phone for it to go to deep sleep again. Would anyone know what might be causing this?
Japultra said:
Like the title says, my phone stops going into deep sleep about 3 days after a reboot. I need to reboot the phone for it to go to deep sleep again. Would anyone know what might be causing this?
Click to expand...
Click to collapse
In my opinion, that's not a bad thing. It's better to restart any device with an OS on it at least once a day or two maximum.
A computer device that stays on for days is similar to a human not getting sleep. Things slow down and become fragmented. VRAM, Page File, etc start getting cluttered.
I'm not surprised your phone won't enter deep sleep after three days of being on. After that much use, you'd have used various apps and services causing wakelocks.
That's what I experience, at least.
FiddleGoose said:
In my opinion, that's not a bad thing. It's better to restart any device with an OS on it at least once a day or two maximum.
A computer device that stays on for days is similar to a human not getting sleep. Things slow down and become fragmented. VRAM, Page File, etc start getting cluttered.
I'm not surprised your phone won't enter deep sleep after three days of being on. After that much use, you'd have used various apps and services causing wakelocks.
That's what I experience, at least.
Click to expand...
Click to collapse
My S6 didn't do this though. I could go for a couple weeks without restarting it and it would still enter deep sleep.
I had a similar problem. For me it wasn't every three days, but usually 24-36 hours. But same issue, suddenly wouldn't go into deep sleep and a restart would fix it.
I found my issue to be gas buddy app and it trying to poll locations via bluetooth. Google it, there are lots of threads on it, but basically due to bad programming it would just jam on.
I figured this out as i could get my phone to go into deep sleep by turning off bluetooth, so that might be a quick easy test for you.
Also remember my in case (and unfortunately for a lot of other people) it was the gas buddy app. but others have reported the same issue with other apps.
i don't know if android's implementation on bluetooth location is busted, or the way the apps are using it.
So, here's my issue: I started to notice that bluetooth audio, which was usually good, started to suddenly cut in and out. At the same time, my battery life went to pot, and the top battery sucker was the Bluetooth share. I also noticed that the phone got really hot and very slow when charging when all of this was happening (usually I don't have to worry about the phone getting super hot when charging and using bluetooth).
I installed BBS and GSAM, and they both basically told me that the phone was not going to sleep because the bluetooth share was keeping it away. I even tried installing Naptime, and the phone still refuses to go into deep sleep, and the bluetooth share keeps sucking battery.
So here's what I've done so far...
- Uninstalled recent apps, no change
- Clear Bluetooth share, restart phone, no change
- Unpair all bluetooth devices, no change
- Restart phone (several times), no change
- Start the phone in safe mode, phone behaves normally....
In the course of trying to figure out what's going on, I basically uninstalled every app and the bluetooth share was still keeping my phone awake.
The only way I've found that fixes this issue is to completely format the phone and reinstall stock firmware. And I don't mean just to fastboot flash system system.img, I mean I have to fastboot erase system and then flash the system in order for bluetooth to behave. After I do this, and reinstall all my usual apps (I allow Google to download them, then I use titanium backup to restore the data on apps that don't sync their own data), the phone works brilliantly for about a week and a half, then the ordeal starts all over again.
The only thing I haven't tried is going bone stock... when I reinstall my phone I root and put Frankenclar on it. I used to use Xposed, but I tried going without to see if that made a difference... and, nope. Even without Xposed the bluetooth share keeps the phone awake.
I've started going through the steps to contact Moto, but they may balk because I've unlocked my phone (even though the warranty says valid).
Any ideas??
Oh, I'm on Verizon, so my choice of roms are limited... and I really like the wake on approach, twist for camera, chop for flashlight, and being able to call to my phone when the screen is off and it's not charging.
Thanks for your time!
Okay, so for anyone else who may be having an issue like this... here was my problem:
After doing a lot of searching online, I discovered that the CVS app was causing the issue. Apparently CVS uses bluetooth beacons to discover your location and push "deals" to your phone. Only, this causes the phone to never go to sleep and causes the bluetooth to stay active and scanning.
So I uninstalled the CVS app, restarted the phone, and have been happy ever since. The app was handy, and some people have said that disabling the location ability in the app permissions may fix it, so I might try that later.
In addition, the Gasbuddy app has also caused similar issues, so if you have random battery drain and have either Gasbuddy or CVS installed, try uninstalling those and see if it helps.