[APP][2.2+] [v.1.5+] Wakelock Detector- What keeps your phone awake when it sleeps?
- Thread starter ahikmat
- Start date
Check the attachment,
If you have Greenify v1.97 and above, then the button "Greenify" appears on the expanded view.
Attachments
After 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.
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.
Good idea. I'd call the campaign something like "Google Being Evil' and explain in the first line that, at the very least, they are being callous.
I 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
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 "android
rotectionLevel="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
Last edited:
And how do you do on devices without known flaws to get root? Root should be left to power users, having a device that doesn't die after 5 hours shouldn't be reserved to power users though.
Regards
however, the procedure of using WLD is going to change:
1) Run WLD on your phone
2) Connect your phone to your PC (for Windows users; make sure you have USB drivers installed)
3) Run "WLD_Helper" app on your pc (this app is under development)
4) Unplug from USB, and enjoy wakelock statistics
After that you can use WLD like before,
however, if you restart your phone you got to repeat the above procedure (phone settings resets at reboot)
What do you think?
Would you just ROOT your device ?
or would you follow this procedure to solve your wakelock problem?
Last edited:
I think most users of wld have rooted their phone (me too) so I don't bother to have root as a requirement to avoid this (annoying) procedure.
As far as I understand wld is a (the) utility to check for wake locks but next step is eliminate the unwanted wakelock(s) and that's more difficult if you don't want to simply uninstall an app (which is ultima ratio but often not desired or not possible because you need the apps features/aims). In detail the countermeasure often/maybe needs root (in case you must disable certain services or permissions producing wakelocks, ie with System Tuner or Disable Service or similar apps which all need root).
So finally with wld you will get information but with root you will be able to 'kill' the explored wakelock with countermeasures.
As far as I understand wld is a (the) utility to check for wake locks but next step is eliminate the unwanted wakelock(s) and that's more difficult if you don't want to simply uninstall an app (which is ultima ratio but often not desired or not possible because you need the apps features/aims). In detail the countermeasure often/maybe needs root (in case you must disable certain services or permissions producing wakelocks, ie with System Tuner or Disable Service or similar apps which all need root).
So finally with wld you will get information but with root you will be able to 'kill' the explored wakelock with countermeasures.
Last edited:
I you would like to look into implementing as a system app to regain battery_stats perms for rooted users (and avoid parsing dumpsys output and expensive su operations) I have a running and tested implementation for BBS. The repo is up-to-date
Hi guys, before asking I want to thanks the creators of this app because I think it is wounderful!
So I tell you my problem: I am the owner of an Ascend P1 Huawei and I am running a stock firmware not officially released from the constructor but it is a stable version.
It never goes in deepsleep except when it is on plane mode so I started to search some solution and I founded your app.
It gives me a result of about x1200 wake call from AlarmManager and Android OS with the most percentual of battery drain.
After that I've tryed to access the AlarmManager.txt o AlarmDump.txt but probably the indications that I found on the differents threads on this forum doesn't work with my phone.
So anybody can help me to access this file? I need it to understand wich application of the system is keeping awake my phone.
P.S.: When I got these results I had a factory resetted phone so I had no app and I didn't make calls or data connection.
Thank you so much for the help!
EDIT: I've got the files I was looking for, someone can help me to understand where is the problem
So I tell you my problem: I am the owner of an Ascend P1 Huawei and I am running a stock firmware not officially released from the constructor but it is a stable version.
It never goes in deepsleep except when it is on plane mode so I started to search some solution and I founded your app.
It gives me a result of about x1200 wake call from AlarmManager and Android OS with the most percentual of battery drain.
After that I've tryed to access the AlarmManager.txt o AlarmDump.txt but probably the indications that I found on the differents threads on this forum doesn't work with my phone.
So anybody can help me to access this file? I need it to understand wich application of the system is keeping awake my phone.
P.S.: When I got these results I had a factory resetted phone so I had no app and I didn't make calls or data connection.
Thank you so much for the help!
EDIT: I've got the files I was looking for, someone can help me to understand where is the problem
Last edited:
Aside from the dirty fix to get this app working on 4.4 is there a more permanent fix? When I open the app I get a message saying 'failed to perform this task, try again later'
Tried clean install, wiped data etc but nothing works.
Thanks
Sent from my Desire HD using Tapatalk
Tried clean install, wiped data etc but nothing works.
Thanks
Sent from my Desire HD using Tapatalk
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
