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

Search This thread
By:
Advanced…
L

lihof

New member
Jan 23, 2017
4
2
shaggyskunk said:
You didn't use the Windows Unlocker?

Sent from my SM-G975W using XDA Labs
Click to expand...
Click to collapse

Do you mean Chrome unlocker plugin? I am not aware of other "windows tool".
I stumbled over the Chrome plugin by accident which does not work for full version, only for lite. Finally, Plugin is doing same as you can do via adb by yourself. So I found out correct package name and voila. ADB must be installed anyhow for Plugin or the manual way.
 
Last edited:
shaggyskunk

shaggyskunk

Recognized Contributor
Nov 22, 2011
19,731
16,044
IDK
lihof said:
Do you mean Chrome unlocker plugin? I am not aware of other "windows tool".
I stumbled over the Chrome plugin by accident which does not work for full version, only for lite. Finally, Plugin is doing same as you can do via adb by yourself. So I found out correct package name and voila. ADB must be installed anyhow for Plugin or the manual way.
Click to expand...
Click to collapse

Of course the Unlocker plugin works for the Full version - You can see it right there on the computer screen ?

Sent from my SM-G975W using XDA Labs
 

Attachments

  • 20190817_182755.jpg
    20190817_182755.jpg
    253.1 KB · Views: 346
I

ivar418

Senior Member
Jun 28, 2017
134
12
amsterdam
OnePlus 7 Pro
Hi,

(First of all I might have missed a solution please don't burn me)

I am using the full version. I have magisk root. Most current version. I tried with just root permission. It tells me to install as system. Then I install as system with app systemized via magisk module because the build in install as system app never works. But then it tells me failed to perform this task etc. I have tried the non paid root version as well. That didn't work either. What should I try next?

I am using a onepus 3 with latest rr remix(but I don't work on havoc, aosp extended either)
 
P

pete101

Senior Member
Feb 21, 2014
158
2
Does anyone know how to get rid of the whatsapp wakelock:

com.whatsapp.gcm.IntentLaunch:Service

?

It causes a drain on my battery

S6 edge plus no root 7.0 using wakelock detector lite

When i google the wakelock i get no information
 
P

pete101

Senior Member
Feb 21, 2014
158
2
Does any one know what i can do without rooting and freezing whatsapp in island?

I have this annoying wakelock which i cant shake.

Im on s6 edge plus BTU 7.0 no root with island with encrypted phone enabled.

It is a great app for freezing facebook and messenger but i cant freeze whatsapp as i need the instant notificstions.

I never had this problem on marshmallow.

com.whatsapp.gcm.RegistrationIntentServiceLaunch:service wakelock.

Does anyone have a solution for this please for this wakelock?
 
H

hulyahulya

Senior Member
Feb 19, 2019
197
17
im on android 10 with rooted device . i have this error . "There are no available battery statistics yet, give it some time!" . anyone tried on android 10 ?
 
B

Brotbackmeister

New member
Nov 16, 2019
3
0
ivar418 said:
I wasn't aware that you needed to reboot after setting se permissive. Il try
Click to expand...
Click to collapse

ivar418 said:
Hi,

(First of all I might have missed a solution please don't burn me)

I am using the full version. I have magisk root. Most current version. I tried with just root permission. It tells me to install as system. Then I install as system with app systemized via magisk module because the build in install as system app never works. But then it tells me failed to perform this task etc. I have tried the non paid root version as well. That didn't work either. What should I try next?

I am using a onepus 3 with latest rr remix(but I don't work on havoc, aosp extended either)
Click to expand...
Click to collapse

Anyone found a solution for that? I'm using an AOSP Pie Rom, granted root with magisk and still receiving the message "failed to perform the task".
 
_jis_

_jis_

Senior Member
Feb 5, 2012
1,469
530
Last edited:
crazy4jack

crazy4jack

Senior Member
Apr 12, 2019
114
10
47
T

Tomek0000

Senior Member
Jun 14, 2015
526
143
This application sometimes works correct, sometimes is not able to read data and asks to try agin next time (in android 8 and 9). I had 2 devices with LOS16 with this problem. Mi pad 4 never worked with WLD, mi 9 lite stopped after update to newer update. The both WLDs were converted to system using App2SD application.

I repeated this what was suggested in this thread; I run this command in PC console when device was connected by usbc:

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

After this command WLD (root version) started to work.
I suppouse this is universal solution and should work ever.

Do we have any application, which is able to grand permission to BATTERY_STATS without connecting PC and use adb?
Yes we have.
Run 2 commands in the terminal app:
su
pm grant com.uzumapps.wakelockdetector android.permission.BATTERY_STATS

but it has to be repeated every restart.

If you want ot convert this application to system app, the best is to use magisk's module : systemizer . Use it in terminal :
su
systemize
It works in android 10 too.
 
Last edited:
  • Like
Reactions: asdf2002, Piereligio and casouzaj
You must log in or register to reply here.

Similar threads

C
  • Locked
[APP]SuperOneClick v2.3.3 - Motorola Exploit Added!
Replies
7K
Views
16M
vanessaem
vanessaem
HootanParsa
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
Replies
44K
Views
7M
Ultramanoid
Ultramanoid
R
  • Locked
[APP] z4root
Replies
3K
Views
7M
TRusselo
TRusselo
S
[APP][2.2+][ROOT][WiFi] Reaver-GUI for Android
Replies
2K
Views
2M
D
deverstator
PerfectSlayer
[APP][ROOT/NONROOT][OFFICIAL] AdAway v6.1.1
Replies
18K
Views
7M
S
Sgtmack

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 354
    A
    ahikmat
    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
    View
    32
    A
    ahikmat
    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!
    View
    29
    A
    ahikmat
    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.
    View
    17
    A
    ahikmat
    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.
    View
    12
    A
    ahikmat
    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
    View

New posts