In my experience, the shorter the time can result higher awake percentage. As an example, Suppose that during 1 hour if you listen to mp3 for 10 minutes, then awake percentage becomes 10/60*100 = 16%
[APP][2.2+] [v.1.5+] Wakelock Detector- What keeps your phone awake when it sleeps?
- Thread starter ahikmat
- Start date
In my experience, the shorter the time can result higher awake percentage. As an example, Suppose that during 1 hour if you listen to mp3 for 10 minutes, then awake percentage becomes 10/60*100 = 16%
Well actually I also bought the full version on Play Store, to show you some much deserved love!
The only small issue I have with this version is that it always displays the kernel wakelocks on open and I have to switch each time to CPU wakelocks.
Oh and the kernel wakelock
durations look a bit odd: I'm getting 2 days of wakelocks, but this is neither since last unplugged (10h max), nor since the last reboot (5-6 days). What duration do these kernel wakelocks take into account? Thanks!
Trimis de pe Nexus 4 cu Tapatalk
hey there
awesome tool but since a few days i always get "wakelock detector has stopped" error when i try to open it :what:
edit :
i just found out that this error occurs while i have "swipeback" on
(this is a xposed framework modul) -
if i turn it off wakelock detector works again ...
Sent from my JY-G4 using XDA Premium 4 mobile app
awesome tool but since a few days i always get "wakelock detector has stopped" error when i try to open it :what:
edit :
i just found out that this error occurs while i have "swipeback" on
(this is a xposed framework modul) -
if i turn it off wakelock detector works again ...
Sent from my JY-G4 using XDA Premium 4 mobile app
Attachments
Last edited:
Well actually I also bought the full version on Play Store, to show you some much deserved love!
The only small issue I have with this version is that it always displays the kernel wakelocks on open and I have to switch each time to CPU wakelocks.
Oh and the kernel wakelockView attachment 2656823 durations look a bit odd: I'm getting 2 days of wakelocks, but this is neither since last unplugged (10h max), nor since the last reboot (5-6 days). What duration do these kernel wakelocks take into account?
Thanks!
Trimis de pe Nexus 4 cu Tapatalk
I realized the reason of this issue,
for non-rooted kitkat phone i made kernel wakelock as default.
it will be fixed and updated
Thank you for sharing this issue
some advice?
i wanna recommend this to my friend who uses S4. he's always complaining about horrible battery life (and as an iphone convert that paints a poor picture of android for him) so i think this app will be useful for him. however S4 just received 4.4 update recently and sadly that means wakelock detector now requires root. my friend's a non power user (iphone convert, remember?) so i wouldn't immediately recommend him to root. so thank goodness for pc version:good: what i wanna ask is, for the pc version, all he has to do is plug in his phone and run the .exe? does he have to enable debugging and/or adb or other developer options (sorry, i myself although rooted, ain't too familiar with all the dev options)?
thanks in advance:laugh:
i wanna recommend this to my friend who uses S4. he's always complaining about horrible battery life (and as an iphone convert that paints a poor picture of android for him) so i think this app will be useful for him. however S4 just received 4.4 update recently and sadly that means wakelock detector now requires root. my friend's a non power user (iphone convert, remember?) so i wouldn't immediately recommend him to root. so thank goodness for pc version:good: what i wanna ask is, for the pc version, all he has to do is plug in his phone and run the .exe? does he have to enable debugging and/or adb or other developer options (sorry, i myself although rooted, ain't too familiar with all the dev options)?
thanks in advance:laugh:
Hi,
for PC version, the USB debugging should be on, and S4 drivers must be installed on PC side (for adb connection)
I am not sure if your friend can do it,
If you have seen these slides:
http://goo.gl/Yqdh2F
Your friend should follow slides: 2 ,3 ,4 , 6
All the best!
Nice app. Thx.
Disturbing that it shows Google svcs are the primary batt killer. Just for kicks, I downloaded FB and Instagram, and have had Plume up and running, yet the apps waking the phone are from google. Maybe that's because I can set FB, etc to update manually only; didn't find a way to do that with Google.
Eh, I'd suspected google anyway, but it's nice to know for sure, though.
General Q: so Greenify seems like the sort of app where, after you figure out what's killing your batt, and you find a replacement that is better behaved (or go without that service), then go ahead and remove Greenify, right? (Or freeze Greenify until you next need it when trying out new apps.) —Unless you opt to keep an app that needs to be put down, but I haven't found one yet that I couldn't replace or adjust in settings somehow. The worst behaved were ones I'd WANT to wake the phone (SMS or phone); I found I didn't need Greenify when I could successfully replace other apps.
Btw, WTF is MotoCare? Anyone know? I mean, it's gone now, but that little bugger was nearly as bad as google location and backup, and I don't even know what it did, ...I suppose it cared. (A LOT, since it was HUGE!)
Disturbing that it shows Google svcs are the primary batt killer. Just for kicks, I downloaded FB and Instagram, and have had Plume up and running, yet the apps waking the phone are from google. Maybe that's because I can set FB, etc to update manually only; didn't find a way to do that with Google.
Eh, I'd suspected google anyway, but it's nice to know for sure, though.
General Q: so Greenify seems like the sort of app where, after you figure out what's killing your batt, and you find a replacement that is better behaved (or go without that service), then go ahead and remove Greenify, right? (Or freeze Greenify until you next need it when trying out new apps.) —Unless you opt to keep an app that needs to be put down, but I haven't found one yet that I couldn't replace or adjust in settings somehow. The worst behaved were ones I'd WANT to wake the phone (SMS or phone); I found I didn't need Greenify when I could successfully replace other apps.
Btw, WTF is MotoCare? Anyone know? I mean, it's gone now, but that little bugger was nearly as bad as google location and backup, and I don't even know what it did, ...I suppose it cared. (A LOT, since it was HUGE!)
Wakelock detector has been updated
Wakelock detector 1.6.1 Update Information
- "SwipeBack" related bug has been fixed
- Internet permission is back again, for only KitKat workaround purpose (no outer traffic is consumed)
- Widget related bug has been fixed(for Free version)
- Minor optimization
Feel free to test and give feedback!
Wakelock detector 1.6.1 Update Information
- "SwipeBack" related bug has been fixed
- Internet permission is back again, for only KitKat workaround purpose (no outer traffic is consumed)
- Widget related bug has been fixed(for Free version)
- Minor optimization
Feel free to test and give feedback!
Thanks for the Windows version to use on non-rooted phones.
I've had a terrible battery drain for at least two weeks, and the best I can see with this app is "com.google.android.backuptransport" on my Droid Maxx. Not really sure where to go from here, this is the first wakelock issue on any phone that's had me stumped...but this is also the first phone I've not rooted (and can't root).
I've had a terrible battery drain for at least two weeks, and the best I can see with this app is "com.google.android.backuptransport" on my Droid Maxx. Not really sure where to go from here, this is the first wakelock issue on any phone that's had me stumped...but this is also the first phone I've not rooted (and can't root).
Could you check if under "Settings" -> "Backup & Restore" -> "Save my data" is activated? (It should be called something like this, I'm using the german loalization and don't own a Droid Maxx).
It's the option that allows google to store app data / wifi passwords at the google server.
Perhaps deleting and readding your google account could also help.
I think it's a problem between your phone and the google servers to sync some kind of data.
Yes, it is. I actually went there before posting and unchecked it, but hit cancel when it warned of a removing all backups off the server. I just went ahead it did it now. I also went to recovery and cleared the cache (about all you can do unrooted on this phone).
I'll monitor and post back after a day or two.
This phone used to last 40+ hours with legitimate heavy-moderate usage and lots of screen time, it's down to maybe half that lately.
Hi,
Thanks for the windows version, really awesome to check wakelocks without root. I've been having a problem with my Note Pro 12.2. Android system keeps the tab awake 95% of the time. I tried wiping but that only helped for a few days and the problem returned. Last night WLD showed that com.sec.android.app.bluetoothtest is keeping awake. Any ideas how to fix this?
Bluetooth is switched off and never used. I've tried reloading the firmware via Kies without wiping but that not helped.
Thanks.
Sent from my SM-P905 using XDA Premium 4 mobile app
Thanks for the windows version, really awesome to check wakelocks without root. I've been having a problem with my Note Pro 12.2. Android system keeps the tab awake 95% of the time. I tried wiping but that only helped for a few days and the problem returned. Last night WLD showed that com.sec.android.app.bluetoothtest is keeping awake. Any ideas how to fix this?
Bluetooth is switched off and never used. I've tried reloading the firmware via Kies without wiping but that not helped.
Thanks.
Sent from my SM-P905 using XDA Premium 4 mobile app
Attachments
Any chance that some simple Linux scripts could be released that would allow for similar functionality to the PC/Windows version? Unfortunately my Moto X doesn't have adb on the device. It wouldn't have to have a fancy graphical display, just a text dump of the info would be great.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
354Wakelock Detector 1.5.*
Ever wondered why your smartphone screen doesn’t turn off automatically when it should have, the screen wakes up all of a sudden or you find your phone battery drained even when you exited apps and turned off the screen? This might be due to wakelock holding apps.”Wakelock Detector” helps you to detect battery consuming applications in your Android device by checking wakelock usage history. Now you can find out which applications drain your battery in a simple way by using this app!
"Wakelock detector" is our goal to simplify detecting wakelock issues for an ordinary user.
As you know, wakelocks have enormous impact on battery life.
Available in GoogelPlay: Download from GooglePlay
Please feel free to comment and give us your feedback
Thank you!
Presentation about "Wakelock Detector" (recommended) Wakelock PRESENTATION
User Guide (Manual) for Wakelock Detector : http://www.slideshare.net/ahikmat1/manual-for-wakelock-detector
Changelog:
https://docs.google.com/document/d/1eatTvA_mSaN2Nljq7i_Qy-5gfDtkOi5QiYY5QHUga84/edit?usp=sharing
[PC version]
For KitKat non rooted users PC version has been developed.
PC version retrieves stats via adb.
[Reviews]
XDA Review
XDA Video Review
LifeHacker
HowToGeek
DotTech
Temefy
Facebook page32testing for kitkat
Wakelock detector 1.5.7, supports KitKat (rooted, also for non-rooted phones with few steps)
New permission added:
[INTERNET] - WLD does not consume any traffic, this permission is needed for adb self connection purpose
([BOOT] - this permission will be added for calculating screen on time for non-rooted kitkat phones)
Starting from kitkat we retrieve wakelock stats from "dumpsys", that is why your phone either needs to be ROOTED or you need to have adb access to your phone itself.
KitKat owners with ROOTED phones
Run WLD, allow ROOT at first run. It is preferred to check "remember it" option
KitKat owners with NON-ROOTED phones
This option takes few steps to accomplish, but this is the only way to see wakelock stats for non-rooted kitkat phones.
In android phones, by default adbd listens to USB port, we need to change it to listen tcpip for establishing adb connection.
for that we need to run "adb tcpip 5555" from PC. For Windows OS, usb drivers need to be installed. http://developer.android.com/sdk/win-usb.html
Install one of these light adb on your PC:
Windows: http://xdaforums.com/showthread.php?p=42407269
Mac/Linux: https://code.google.com/p/adb-fastboot-install/
Enable "developer option" on your phone (it is in settings window , if you don't see it click "Build version" 7 times on "About" section)
Run "adb tcpip 5555" from command line.
Then install "Terminal emulator" on your phone and run "adb kill-server" , "adb devices" and confirm self-connection.
You can follow these slides for details: https://docs.google.com/presentation/d/1r3VlhZIZVSufZlAeICJet6QBtyAF7z06_ysl1kUKME4/edit?usp=sharing
We are working to make single-click PC app.
If you could have better idea to optimize these steps, share it with us! Thank you!
[updated apk]
Big thanks to Sordna for helping to improve WLD and RootTools performance!29After the recent Google's update for KitKat 4.4, I am discouraged and disappointed with Google's actions against developers.
I think "wakelock" info must be available for all Android users, because it is their property. They should be able to know what is happening to their phone while they are not using it.
Until KitKat the apps like BBS, Gsam and WLD gave users all these detail statistics from Google's hidden battery statistics repositories.
But starting from KitKat, they completely restricted it. Only the ROOTed users might be able to see the wakelock statistics for now. They might even disable it also in the future.
I wrote email to the person who did this. But no effect.
...
I have some idea about organizing a public Online(or maybe offline) demonstration against the Google's restricting developers and users from their freedom of knowing the detail battery statistics.
Maybe it sounds dumb, but we could join all together and do something against Google's change.
There are millions of users who resolved wakelock issues and doubled their battery life, who saved their phone from resetting or doing all costly things.
We can use famous social networks like a facebook page, or Google Plus page then
post our demands until we reach Google.
What do you think ? How much are you eager to support this idea.12I got a reply from "Dianne Hackborn" who commited the change
Hi Uzum,
This was never available to third party applications anyway -- the only APIs to access the information protected by it are all hidden, and change across platform versions. Any applications using these private APIs are going to break sooner or later, and we would rather it was sooner.
So I send her reply again, if it does not work, then we will try to catch public attention
Dear Dianne Hackborn,
Thanks for your reply.
We thought over about your reply,
However,
Could you consider discussing about reverting BATTERY_STATS permission's protection level from "androidrotectionLevel="signature|system" to "androidrotectionLevel="dangerous"
We could not find any solution for this issue, Our app can not access wakelock statistics without ROOT, and we don't want to force our users to ROOT their devices.
As users are aware that third-party app is going to access battery statistics,in our opinion this permission can not hurt the user . It just only gives access to power consumption information. We do not see any danger in this.
We are aware that this battery statistics API was hidden, we used reflection to access this info as that was the only choice.
Standard android battery app is good enough, however many users with "no-sleep" issues could not solve their battery draining issues with standard app. Because android's standard battery app does not give detail information.
Fortunately, they found "BBS" or "Wakelock detector" or "GSam battery monitor" and easily found out which rogue apps kept their phone awake from deep-sleep that were causing drastic battery drain.
They need this "wake lock" statistics. That is why there was a big demand for such apps.
In other words, Google is taking away the right from users to see their detail battery statistics.
For understanding how much serious problem is "no-sleep" issue, please take a look below links:
https://www.google.com/search?q=android+no+sleep+issue&oq=android+no+sleep+issue
http://software.intel.com/en-us/articles/wakelocks-detect-no-sleep-issues-in-android-applications
According to research paper, almost 50% of apps had this "no-sleep" bugs in 2012.
Hopefully, that number dropped by 2013, but still there are apps which mis-use "wake lock" feature and cause drastic battery drain.
Please check out the user feedbacks in "Wakelock detector" for more details.
Since 2013.03.01 We were happy to serve Android users by helping them to resolve their wakelock issues.
They doubled their battery life without going to A/S or Resetting their phones.
Right now, We need your help to help our users which are your users in turn.
Please Help!
Regards UzumApps
