Try going into Settings > Developer options > and click on Revoke USB debugging authorization & try connecting the phone to the PC again. You're supposed to get a popup authorization request.
Sent from my SM-G935P using Tapatalk
[APP][2.2+] [v.1.5+] Wakelock Detector- What keeps your phone awake when it sleeps?
- Thread starter ahikmat
- Start date
Try going into Settings > Developer options > and click on Revoke USB debugging authorization & try connecting the phone to the PC again. You're supposed to get a popup authorization request.
Sent from my SM-G935P using Tapatalk
Thanks. Tried that too on both phones but still nothing.
---------- Post added at 11:41 PM ---------- Previous post was at 11:19 PM ----------
When i turn usb debugging on/off Samsung ADB device appears/disappears from device manger, as you would expect. But still no request to authorise computer
You get the prompt after connecting phone to PC, starting adb, and typing in an adb command, such as: adb devices
Still nothing?
Sent from my SM-G935P using Tapatalk
Hi.
Thanks for developing this app for non-rooted devices. I was using it a lot, when I was rooted, so it's one of the most missing apps for me since I don't root mhy phone anymore.
I'm using Oneplus One with latest MM official build Cyaonogen OS 13 (MMB29X) Android 6.0.1.
Unfortunately I can't get Wakelock Detector to work on my device.
That's what I'm doing:
download WLD beta form play store (wakelock detector free 2.0.2) - this one https://play.google.com/store/apps/...r.noroot&ah=kZn_zph5vEm3q2ImTFgQAZT0SUE&hl=pl
reboot the phone
enable usb debugging
revoke adb authorization
connect phone to PC
run WLD Unlock for Chrome extension
confirm RSA on phone (always trust)
click on grant battery stats - icon changes to "thumb up"
disconnect usb
open wakelock detector
confirm RSA (always remember)
WLD is loading, but unable to show anything
What am I doing wrong?
I tried 2nd method - enabling network ADB and then adb tcpip 5555 - but still nothing.
HALP
Thanks for developing this app for non-rooted devices. I was using it a lot, when I was rooted, so it's one of the most missing apps for me since I don't root mhy phone anymore.
I'm using Oneplus One with latest MM official build Cyaonogen OS 13 (MMB29X) Android 6.0.1.
Unfortunately I can't get Wakelock Detector to work on my device.
That's what I'm doing:
download WLD beta form play store (wakelock detector free 2.0.2) - this one https://play.google.com/store/apps/...r.noroot&ah=kZn_zph5vEm3q2ImTFgQAZT0SUE&hl=pl
reboot the phone
enable usb debugging
revoke adb authorization
connect phone to PC
run WLD Unlock for Chrome extension
confirm RSA on phone (always trust)
click on grant battery stats - icon changes to "thumb up"
disconnect usb
open wakelock detector
confirm RSA (always remember)
WLD is loading, but unable to show anything
What am I doing wrong?
I tried 2nd method - enabling network ADB and then adb tcpip 5555 - but still nothing.
HALP
Last edited:
yay! I did it. Ran minimal ADB and fastboot, then command ADB devices then plugged phone in then got authorization message! Thanks
Hi.
Thanks for developing this app for non-rooted devices. I was using it a lot, when I was rooted, so it's one of the most missing apps for me since I don't root mhy phone anymore.
I'm using Oneplus One with latest MM official build Cyaonogen OS 13 (MMB29X) Android 6.0.1.
Unfortunately I can't get Wakelock Detector to work on my device.
That's what I'm doing:
download WLD beta form play store (wakelock detector free 2.0.2) - this one https://play.google.com/store/apps/...r.noroot&ah=kZn_zph5vEm3q2ImTFgQAZT0SUE&hl=pl
reboot the phone
enable usb debugging
revoke adb authorization
connect phone to PC
run WLD Unlock for Chrome extension
confirm RSA on phone (always trust)
click on grant battery stats - icon changes to "thumb up"
disconnect usb
open wakelock detector
confirm RSA (always remember)
WLD is loading, but unable to show anything
What am I doing wrong?
I tried 2nd method - enabling network ADB and then adb tcpip 5555 - but still nothing.
HALP
You did everything right except for one thing - you have to install Wakeup Detector Lite.
Sent from my SM-G935P using Tapatalk
have you tried both options?Hi.
Thanks for developing this app for non-rooted devices. I was using it a lot, when I was rooted, so it's one of the most missing apps for me since I don't root mhy phone anymore.
I'm using Oneplus One with latest MM official build Cyaonogen OS 13 (MMB29X) Android 6.0.1.
Unfortunately I can't get Wakelock Detector to work on my device.
That's what I'm doing:
download WLD beta form play store (wakelock detector free 2.0.2) - this one https://play.google.com/store/apps/...r.noroot&ah=kZn_zph5vEm3q2ImTFgQAZT0SUE&hl=pl
reboot the phone
enable usb debugging
revoke adb authorization
connect phone to PC
run WLD Unlock for Chrome extension
confirm RSA on phone (always trust)
click on grant battery stats - icon changes to "thumb up"
disconnect usb
open wakelock detector
confirm RSA (always remember)
WLD is loading, but unable to show anything
What am I doing wrong?
I tried 2nd method - enabling network ADB and then adb tcpip 5555 - but still nothing.
HALP
1. change usb to tcpip mode
2. grant battery stats
i am going to add some logging, then i will upload it here
Sent from my Nexus 5 using XDA-Developers mobile app
I have same problemHi.
Thanks for developing this app for non-rooted devices. I was using it a lot, when I was rooted, so it's one of the most missing apps for me since I don't root mhy phone anymore.
I'm using Oneplus One with latest MM official build Cyaonogen OS 13 (MMB29X) Android 6.0.1.
Unfortunately I can't get Wakelock Detector to work on my device.
That's what I'm doing:
download WLD beta form play store (wakelock detector free 2.0.2) - this one https://play.google.com/store/apps/...r.noroot&ah=kZn_zph5vEm3q2ImTFgQAZT0SUE&hl=pl
reboot the phone
enable usb debugging
revoke adb authorization
connect phone to PC
run WLD Unlock for Chrome extension
confirm RSA on phone (always trust)
click on grant battery stats - icon changes to "thumb up"
disconnect usb
open wakelock detector
confirm RSA (always remember)
WLD is loading, but unable to show anything
What am I doing wrong?
I tried 2nd method - enabling network ADB and then adb tcpip 5555 - but still nothing.
HALP
edit: Looked for term "google maps" within this thread and got some decent information.
I'm gonna disable Maps since I prefer Waze anyway
---
Two questions:
- Can anyone tell me whether they have the same Google Maps behaviour?
- Those that have Cerberus: do you see the same as below: Cerberus being on the top?
I'm gonna disable Maps since I prefer Waze anyway
---
Two questions:
- Can anyone tell me whether they have the same Google Maps behaviour?
- Those that have Cerberus: do you see the same as below: Cerberus being on the top?
Last edited:
I am currently running MM 6.0.1, no-root, Wakelock Detector light and have a wakelock 'diagnostics.client.wakelock' that is causing the phone not to go into deepsleep.
Could this be a wakelock created by running Wakelock Detector Light?
Has anyone know anything about this wakelock? I found a few old posts about that said this was related to CarrierIQ.... but that was several versions ago..
Could this be a wakelock created by running Wakelock Detector Light?
Has anyone know anything about this wakelock? I found a few old posts about that said this was related to CarrierIQ.... but that was several versions ago..
Hi. Someone can say me what wakelock is
13960000.decon_f
Enviado desde mi SM-G930F mediante Tapatalk
I also have this. Don't know what it is though
I, i have same problems as you with my Note 4 MM: when i connect my phone to PC, i can see adb in devices list, i can see folders in explorer but nothing happen: it doesn't appear any authorization request; i can't understand the meaning of this procedure: "yay! I did it. Ran minimal ADB and fastboot, then command ADB devices then plugged phone in then got authorization message" can you explain me in deep details what you do? What is minimal adb and fastboot? What i have to do to "Run minimal ADB"? I'm using a W10 laptop.
EDIT: solved, i had to start ADB server on my PC in order to connect to my Note 4 (i have installed “UniversalAdbDriver” by koush).
I have already discovered the cause of a bad wakelock: google backup, since i have updated my phone to MM, when i plug my phone to a charger cause a wakelock that last until i reboot.
Last edited:
I have 2 very annoying wakelocks with no helpful information as to find the source of them (BBD-SEL and Keyevents) (inside kernel wakelock detector)
BBD-SEL (70k+ instances in less than 2 hours)
Event poll (6800)
Net link. (6700)
Keyevents (57k instances)
Also android system (cpu wakelock)
Events
Shows me 2 others
Diagnostic.client.wakelock. (230 instances)
*alarm* (70 instances )
Does anybody have an idea of what the hell could be chewing up my battery so bad ?
Rooted G928A ... (flashed modified kernel)
BBD-SEL (70k+ instances in less than 2 hours)
Event poll (6800)
Net link. (6700)
Keyevents (57k instances)
Also android system (cpu wakelock)
Events
Shows me 2 others
Diagnostic.client.wakelock. (230 instances)
*alarm* (70 instances )
Does anybody have an idea of what the hell could be chewing up my battery so bad ?
Rooted G928A ... (flashed modified kernel)
Last edited:
Thanks optimummind using Minimal ADB and Fastboot and then the command 'adb devices' was the only way to bring up a authorization message on a S5 mini. It then allowed the chrome extension to work.
Which is strange as on a Nexus 7 it brings the authorization message up every time just having debugging turned on and attaching the usb to the computer.
Its great to have Wakelock Detector working without root.
Which is strange as on a Nexus 7 it brings the authorization message up every time just having debugging turned on and attaching the usb to the computer.
Its great to have Wakelock Detector working without root.
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
