[APP][2.2+] [v.1.5+] Wakelock Detector- What keeps your phone awake when it sleeps?
- Thread starter ahikmat
- Start date
alarm manager problem
hi,
been using this wld for awhile, awesome. i have a problem that my phone constantly awake. screenshot below.
how to control the "Alarm Manager" & "zerowakelag" ? i am using SGNote 2. many thanks in advance.
hi,
been using this wld for awhile, awesome. i have a problem that my phone constantly awake. screenshot below.
how to control the "Alarm Manager" & "zerowakelag" ? i am using SGNote 2. many thanks in advance.
Looks as if zerowakelag is there to prevent deep sleep. Maybe you can disable it.
You can start here for information: http://xdaforums.com/showthread.php?t=2208267
not sure about "zerowakelag", it would be nice if someone could give more info on it,
You can reduce "Alarm Manager" wakelock by checking "Wakeup triggers"
Try to reduce wakeup counts for the app listed on the top.
Apps usually have settings for notifications alarms etc..try to reduce the frequency of them..
can not wait to publish new upcoming update of Wakelock Detector
New disc widget, which shows: Awake, Screen On, Deep sleep percentages (Red,Blue,Green accordingly)
More:
- directly greenify from WLD
- improved widgets
- knowledge base updated
- displaying more batt, statistics
New disc widget, which shows: Awake, Screen On, Deep sleep percentages (Red,Blue,Green accordingly)
More:
- directly greenify from WLD
- improved widgets
- knowledge base updated
- displaying more batt, statistics
Attachments
can not wait to publish new upcoming update of Wakelock Detector
New disc widget, which shows: Awake, Screen On, Deep sleep percentages (Red,Blue,Green accordingly)
More:
- directly greenify from WLD
- improved widgets
- knowledge base updated
- displaying more batt, statistics
anyone knows what these wakelocks are?
my Partial Wakelocks are only like 18ms
(PowerManagerService.WakeLocks)
but the following add up to almost an hour
bam_dmux_wakelock 28m 25s
ssp_sensorhub_wake_lock 12m 20s
ssp_wake_lock 9m 47s
on a rooted Galaxy Note 3 with Greenify
Can anyone help me? I got 100% awake even without partial wakelock. I'm desperate from BBS as no one helped me there. :crying:
Attachments
hmm... are you using the phone the whole time..? 27m is too short to decide on anything..
I used it for 1 min. It will be the same even if I left my phone for hours. However, I will give you the screenshot of longer idle time.
While it's hard to tell from those screen shots, one of the best things you can do for your battery is remove Facebook.
Here again with more idle time.
I also added BBS dump, in case you want more details.
PS. I don't think Facebook is the culprit. At least it should not cause 100% awake or it should be shown in stats which is obviously not in this case.
I also added BBS dump, in case you want more details.
PS. I don't think Facebook is the culprit. At least it should not cause 100% awake or it should be shown in stats which is obviously not in this case.
Attachments
Trust him, Facebook is a known battery hog. There is always the web interface, besides life is better without Facebook. Well at least give it a try for a couple of weeks.
You've got "NlpWakelock", you can eliminate it by turning off "Location reporting" in Location Settings of your phone.
The sum of NlpCollectorWakeLock and NlpWakelock is just about 3 minutes. My phone was on for more than 3 hours yet 100% awake.
They can't be the culprit?
How fast your battery drains?
is it draining too fast?
the awake time from android battery service might be wrong too..
could you post the screenshot of default Android battery usage statistics ?
It drained about 1.6%/hour (idle), according to BBS report.
I checked the battery stat and Android OS stayed awake the entire time.
This is my another log with BBS dump. Same scenario. 100% awake, no partial wakelocks that equate to total awake time.
The highest partial wakelock is NlpCollectorWakeLock (Google Services) which only took 2 minutes while my phone stayed awake for more than 10 hours.
Attachments
Last edited:
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
New posts
-
[ROM] [UNOFFICIAL] [13.0] LineageOS 20- Latest: Huntersucksatroms
-
-
