[APP][2.2+] [v.1.5+] Wakelock Detector- What keeps your phone awake when it sleeps?

Search This thread

TerrorApple

Senior Member
Aug 26, 2012
416
173
To used WLD with Magisk, you need to use the Terminal App Systemizer module to make it a system app.
Wow, this actually worked! Thanks so much. Seems like systemizing with TB doesn't work correctly. Anyway, WLD ist up und running :)

Edit: nevermind. Rebooting broke it again. "Failed to perform this task at the moment, try again later". I'll be switching to BBS for now, WLD just doesn't seem ready for Oreo.
 
Last edited:

200mpx

Senior Member
Sep 23, 2005
761
89
Moscow
Wakelock Detector 1.5.*

For another day I can not grant permissions to app through adb (without root) - I follow the manual from here: https://docs.google.com/presentatio...F7z06_ysl1kUKME4/edit#slide=id.g25a03f28e_026 and it returns to me with the following: Bad argument: java.lang.IllegalArgumentException: Unknown package: com.uzumapps.wakelockdetector.noroot
usage

Updated: I managed to get permissions, it seems to me, that my adb was old (but still working for all my needs except the case with this app), changed to recommended Minimal ADB and Fastboot and the extention worked like a charm
 
Last edited:

Nheo12

Member
May 28, 2016
18
2
Hi. Why not collect battery statistic my WLD in the CPU wakelock menu?
629296_screenshot_wakelock_detector_free_20180227-095931.png
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,731
16,043
IDK
Yeah unfortunately Wakelock Detector isn't performing consistently on Stock Unrooted Samsung Galaxy S8+ running Oreo 8.0 - It's temperamental as to when it provides a measurement - More often than not it returned "failed to perform this task at the moment" - It seems to be related to the a few things - The percentage of the Battery - How long since Full Charge - How long since Boot.
It's working perfectly on my Rooted devices - But quite unreliable when using adb commands - It's a shame because it's a pretty terrific app!
Maybe there's going to be some additional Development for Unrooted devices?
?
 

ChadGW

New member
May 29, 2016
1
0
For another day I can not grant permissions to app through adb (without root) - I follow the manual from here: (URL BLOCKED) and it returns to me with the following: Bad argument: java.lang.IllegalArgumentException: Unknown package: com.uzumapps.wakelockdetector.noroot
usage

Updated: I managed to get permissions, it seems to me, that my adb was old (but still working for all my needs except the case with this app), changed to recommended Minimal ADB and Fastboot and the extention worked like a charm

What version of ADB Minimal did you install? I tried the latest 1.43, in addition to several older ones and I still get the same Unknown package error when I try running
adb shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS

I'm stuck and could really use help to get this working on my unrooted Samsung S9.
 

k_o_t_s

Senior Member
Nov 27, 2007
68
2
Help

Could someone help please? I am doing everything correctly in order to make this app work without root access but I always get the error message:

Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.

(screenshot attached)

Device: Xiaomi Redmi 4 Prime
ROM: Stock 6.0.1 with MIUI

Edit: This is what solved it:

Turn on the following option:

USB debugging -Debug mode when USB is connected

Install via USB -Allow installing apps via USB

USB debugging (Security Settings)- Allow granting permissions and simulating input via USB debugging
 
Last edited:
  • Like
Reactions: babelus

IanHodgson

Senior Member
May 1, 2016
332
44
I'm running WLD with root on a redmi note 4 running Pixel Experience, but even after an overnight, when there has been definite CPU activity going on (I can tell because of battery drain and percentage awake), WLD still tells me I need to leave the phone longer to be able to get some stats. Is this maybe an Oreo bug or should I leave the phone longer than 10 hours?

Thanks.

Ian

Edit: I think I found the answer: I just had to enable advanced features in settings.

Edit 2: So it still doesn't show any stats for CPU, that is after 'show processes used by Android OS' is on. I left it overnight, making sure WiFi was turned on and leaving it on before letting the phone go to deep sleep by itself. Still no stats. It says in the 'how to' to leave phone idling for at least 2-3 hours. Either I'm missing something or there is an Oreo bug. Anyone with similar experience? The only thing I haven't tried is installing as system.
 
Last edited:

Tagtag123

Senior Member
Sep 26, 2010
407
136
I'm running WLD with root on a redmi note 4 running Pixel Experience, but even after an overnight, when there has been definite CPU activity going on (I can tell because of battery drain and percentage awake), WLD still tells me I need to leave the phone longer to be able to get some stats. Is this maybe an Oreo bug or should I leave the phone longer than 10 hours?

Thanks.

Ian

Edit: I think I found the answer: I just had to enable advanced features in settings.

Edit 2: So it still doesn't show any stats for CPU, that is after 'show processes used by Android OS' is on. I left it overnight, making sure WiFi was turned on and leaving it on before letting the phone go to deep sleep by itself. Still no stats. It says in the 'how to' to leave phone idling for at least 2-3 hours. Either I'm missing something or there is an Oreo bug. Anyone with similar experience? The only thing I haven't tried is installing as system.

Exact same problem, OnePlus 3T running the latest stable rooted with magisk.
I have no sleep want to find out what's causing the trouble.
I came to the stable OOS by a clean flash from BETA where I had the exact same problem.
 

IanHodgson

Senior Member
May 1, 2016
332
44
Exact same problem, OnePlus 3T running the latest stable rooted with magisk.
I have no sleep want to find out what's causing the trouble.
I came to the stable OOS by a clean flash from BETA where I had the exact same problem.
Better Battery Stats worked for me. Download APK from XDA thread. Follow instructions in OP for settings. My lack of deep sleep was down to Windscribe VPN not being in battery saver mode, ie. always on.
 

crittarr

Member
Nov 19, 2014
21
0
Hi
Is there by chance a way to use the adb command line?

I have downloaded the universal drivers, deactivated tiny firewall, restarted chrome, reconected the phone (doogee s60 lite) with usb debugging on, phone correctly recognised by the chrome addon, licked on the grant battery stats - no response..

The system is android 7.0, unrooted. I have better battery stats already.
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,731
16,043
IDK
Hi
Is there by chance a way to use the adb command line?

I have downloaded the universal drivers, deactivated tiny firewall, restarted chrome, reconected the phone (doogee s60 lite) with usb debugging on, phone correctly recognised by the chrome addon, licked on the grant battery stats - no response..

The system is android 7.0, unrooted. I have better battery stats already.

Do you have your phone set to "Always Allow" connection to your computer? When I first used the Chrome add on it wasn't working & the reason was "Always Allow" wasn't granted ?

Here's the adb commands - Which SHOULD work for you.

"adb -d shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS"

Sent from my Galaxy S9+ using XDA Labs
 

yochananmarqos

Inactive Recognized Contributor
Feb 15, 2013
3,375
2,525
github.com
Google Pixel 3
Google Pixel 8
Hi
Is there by chance a way to use the adb command line?

I have downloaded the universal drivers, deactivated tiny firewall, restarted chrome, reconected the phone (doogee s60 lite) with usb debugging on, phone correctly recognised by the chrome addon, licked on the grant battery stats - no response..

The system is android 7.0, unrooted. I have better battery stats already.

Yes, this is what the Chrome extension does:
Code:
adb -d shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS
Change the package name if you're not using WLD Lite.

Sent from my Pixel using XDA Labs
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,731
16,043
IDK
Yes, this is what the Chrome extension does:
Code:
adb -d shell pm grant com.uzumapps.wakelockdetector.noroot android.permission.BATTERY_STATS
Change the package name if you're not using WLD Lite.

Sent from my Pixel using XDA Labs
Looks like changing "wakelockdetector" to "wakelockdetectorfull" may work for Wakelock Detector Full - At least the adb command didn't get rejected...? ?

Sent from my SM-G965W ??
 
Last edited:

crittarr

Member
Nov 19, 2014
21
0
Thank you. Must usb debugging be on for the app to work?

If stolen, can the system with usb debugging be broken into or can the system just be re-flashed for a 'new user'?

Thanks a lot

---------- Post added at 02:20 PM ---------- Previous post was at 02:20 PM ----------

Thank you. Must usb debugging be on for the app to work?

If stolen, can the system with usb debugging be broken into or can the system just be re-flashed for a 'new user'?

Thanks a lot
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,731
16,043
IDK
Thank you. Must usb debugging be on for the app to work?

If stolen, can the system with usb debugging be broken into or can the system just be re-flashed for a 'new user'?

Thanks a lot

---------- Post added at 02:20 PM ---------- Previous post was at 02:20 PM ----------

Thank you. Must usb debugging be on for the app to work?

If stolen, can the system with usb debugging be broken into or can the system just be re-flashed for a 'new user'?

Thanks a lot
No - USB Debugging doesn't need to be enabled for Wakelock Detector to work (after you granted adb commands or Chrome Wakelock extension).
Yes leaving USB Debugging enabled can present a security risk if your device falls into the wrong hands - or if it was connected to a public computer etc via the USB cable ?

Sent from my SM-G965W ??
 

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,731
16,043
IDK
It's com.uzumapps.wakelockdetector.full


com.uzumapps.wakelockdetector.full.NOROOT?
or just
com.uzumapps.wakelockdetector.full android.permission........?

In either case once the battery drops to a certain level - I get "failed to perform this task at the moment"...

Sent from my Galaxy S9+ using XDA Labs
 
Last edited:

yochananmarqos

Inactive Recognized Contributor
Feb 15, 2013
3,375
2,525
github.com
Google Pixel 3
Google Pixel 8
com.uzumapps.wakelockdetector.full.NOROOT?
or just
com.uzumapps.wakelockdetector.full android.permission........?
WLD Lite = com.uzumapps.wakelockdetector.noroot
WLD Full = com.uzumapps.wakelockdetector.full

In either case once the battery drops to a certain level - I get "failed to perform this task at the moment"...
There's nothing to do about that. I believe the developer said he didn't have much time for this project anymore, unfortunately.

Sent from my Pixel using XDA Labs
 
Last edited:

DeKiesel

Senior Member
Feb 7, 2012
492
77
WLD Lite = com.uzumapps.wakelockdetector.noroot
WLD Full = com.uzumapps.wakelockdetector.full


There's nothing to do about that. I believe the developer said he didn't have much time for this project anymore, unfortunately.

Sent from my Pixel using XDA Labs
Any chance that the dev will open source the code so that somebody else can update the project? Would be a shame if it went to waste.

Is there another tool out there like wakelock Detector that works on oreo?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 354
    Wakelock 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 page
    32
    testing 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!
    29
    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.
    17
    I am back and working on this lollipop issue

    Thank you everyone for supporting WLD,
    Sorry for being off for sometime.
    it is great to know that many of you using it in Lollipop with your own fix.(SeLinux)

    I am getting lollipop now,
    hopefully i will fix this very soon.
    12
    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 "android:protectionLevel="signature|system" to "android:protectionLevel="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