any reason that latest version giving long list just 0.0s x0 data?
and I have seen negative value
and I have seen negative value
[APP][2.2+] [v.1.5+] Wakelock Detector- What keeps your phone awake when it sleeps?
- Thread starter ahikmat
- Start date
So I'm not rooted and can't be at the moment (although historically I have been so I understand the basics) and I'm trying to get this to work for non-root. I'm trying to follow the tutorial. I already had the ADB drivers installed, but reinstalled them anyway. I tried the ones from this forum and then the universal ones.
I already had USB debugging allowed. I installed the Chrome extension, restarted Chrome, launched the extension and it can't find any devices... Not sure what else I should be trying. Might anyone have any ideas? I'm on a Galaxy S6 running Android 6. Thanks!
I already had USB debugging allowed. I installed the Chrome extension, restarted Chrome, launched the extension and it can't find any devices... Not sure what else I should be trying. Might anyone have any ideas? I'm on a Galaxy S6 running Android 6. Thanks!
+1 The same problem!
Have tried to Use "App systemizer" module in magisk - without any success.
It's very strange because a couple days ago WakeLock Detector worked fine (I used it to see a battery drain)
So it used to work, but suddenly stop working...
==
Xiaomi Mi5 3/64 Gb, MIUI 9.1 by xiaomi.eu 7.12.7 (Android 7.0)
+1 exactly same problem
Magisk, app systemizer module. Apps instaled as a system correct as i cannot uninstall by conventional method
Work ok randomised. And when not working got error 'fail to perform the task, plz try again later'
Anyone find the solution.
Try unistall it, wipes cache, dalvik... Install, give root permission, app systemizer permitions.... works sometimes, but most of the times doesn't.
On mi5 miui 9 epic room android 7.1 [emoji115]
On mi4 miui 9 oficial room android 6.0 works fine anytime
Sent from my LG-V500 using Tapatalk
Last edited:
Surprisingly WLD began to work on my device.
I've read one thread on XDA about Magisk modules and found one idea 'to manually disable SU privilegies'....
I've tried this with WLD and ...
WLD is working )))
So, you need to
- disable root for WLD in MagiskSU
- grant a BATTERY_STATS permission
Hope it helps )))
I guess it's a magiskSU bug.
Last edited:
Thanks you vitna for reply,
I undestand it must be a problem with magisk in androod 7, because in android 6 its working fine.
So you said,
Disable root for WLD ON MAGISKSU..... No root permison then
Grant a battery stats permission....... How?
Is it a permission in magisksu
Another thing i dont undestand is that in the phone mi4 that works fine i dont need to use app systemazer.
Could you link me the xda thread if you have it handy
Sent from my LG-V500 using Tapatalk
Tutorial for non-root workaround:
http://goo.gl/Yqdh2F
'app systemazer' is not nessessary for non-root
(+ you need to choose in WLD Mode: BATTERY_STATS granted)
Last edited:
Hey guys,
Thanks for keeping this thread alive!
I am very glad to see people using WLD.
These days I am working full time and it is being hard to find extra time to support Wakelock detector.
That is why I am considering making WLD open-source.
But I am not sure if there will be volunteer contributors.
Please let me know if you are interested to work on it.
Then, I will put all source code in "github" and I would opt to receive donations instead.
Thanks!
Thanks for keeping this thread alive!
I am very glad to see people using WLD.
These days I am working full time and it is being hard to find extra time to support Wakelock detector.
That is why I am considering making WLD open-source.
But I am not sure if there will be volunteer contributors.
Please let me know if you are interested to work on it.
Then, I will put all source code in "github" and I would opt to receive donations instead.
Thanks!
Thank you.
I did try this method before i went root. It didnt work for me.
Dont think i will try it again.
I have to flash my room clean for something else.
Will see if it does help will the root method, as same device and room of friends it works
Many thanks for your help
Updated : now its working with magisk. I disable in magisk options hide magisk. Then again before sometimes did work and stop
Sent from my LG-V500 using Tapatalk
Last edited:
You're wellcome )))
But it's too early to thank me because WLD on my device lives it's own life (((
Yesterday evening it didn't start with the mentioned error.
Today it's working (just checked).
I don't understand what is triggering WLD to stop working (nothing have been changed on my device except battery level)
Very strange.
Perhaps it's need to check without Magisk...
I just discovered that WLD works fine if you charge the phone to 100%. If the option in settings statistics since unplug is selected.
If you charge the phone under 100%, like I do most of the times up to 80%, for WLD to works you need NOT to select the option statistics since unplug.
Its not ideal as like to check my stats since i unplug the phone, but its a progress.
Sent from my LG-V500 using Tapatalk
Last edited:
Wakelock Detector version 2.04 from April 2nd 2017 is working for me on Oreo 8.1
From Down the Rabbit Hole by:
My SM-G930W8 ??
Little feedback after a bit of a fight on the issue. I have not tested the App systemizer method, and therefore have nothing to do with the Chrome extension to make the [Lite] or [Full] version work. As I was learning to drop the case, I installed the version [Root] and presto, it works perfectly. To see on the duration now.
P.S .: I am on Omnirom 8.1 with an OP3
[edit] for the [Full] version of WLD, the "App systemizer" method works perfectly.
P.S .: I am on Omnirom 8.1 with an OP3
[edit] for the [Full] version of WLD, the "App systemizer" method works perfectly.
Last edited:
Where did you get this update? On the Play store, it's still listed as v. 2.01.
Thanks!
Where i can download that version? Directly from play store or where?
Also, which version do you recommend for android 8.1? I use NitrogenOS with latest magisk version
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
-
Fire TV Stick 4K Firmware and apps. Official Cloud Front direct links- Latest: AFTVnews.com
