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

Search This thread
By:
Advanced…
B

bpaulien

Senior Member
Jan 10, 2013
381
72
Columbus
Anrikus said:
According to this:

This partial wakelock will occur when your phone seeks reception for example.
I personally have no idea if you can stopp this process and I highly doubt, that stopping this is a good thing (at least if you want to make calls with your phone).
Click to expand...
Click to collapse

Yeah, I was wondering about the RILJ one too. Does it get worse when you don't have good reception? Or is it always there?

I read somewhere that it can be reduced by turning off location services. You might want to try that.

Sent from my nook HD+ running cm10.1 on emmc from Tapatalk HD
 
A

Anrikus

Senior Member
May 14, 2012
214
210
bpaulien said:
Yeah, I was wondering about the RILJ one too. Does it get worse when you don't have good reception? Or is it always there?

I read somewhere that it can be reduced by turning off location services. You might want to try that.

Sent from my nook HD+ running cm10.1 on emmc from Tapatalk HD
Click to expand...
Click to collapse

Well this is only something I observed.
I had a workplace with nearly zero reception and I had a ton of wakelocks (and battery drain)
It also seems if you move a lot (like driving to work) you get more wakelocks than if the phone is in a steady position (like forgot the phone at home)

Still I have no numbers to proof this, it's just a feeling.
Even with turned off location settings I get some RILJ wakelocks, so I guess it's always there.

With my samsung Galaxy S the wakelocks varied with the modem, but this is afaik only something that can only occur with samsung devices.
 
  • Like
Reactions: ahikmat
P

Publiuss

Senior Member
Jun 29, 2012
948
171
Hi

Perhaps I'm saying a stupid sentence, but, could this be related to fast dormancy?

I freezed fast dormancy app long time ago due to wakelocks (not RILJ but by fast dormancy itself) and do not have such wakelocks.

You could try.
 
  • Like
Reactions: ahikmat
I

ishyboy15

Senior Member
May 22, 2007
132
9
Samsung Galaxy S22 Ultra
Just used this app as instructed. Maps is at 380 and exchange services is ar 40 . The only solution i can think of is turn off access to my location from location services and everything will be fine now? Any other ideas? Its just weird. Ive had the omega rom for a week now and this is the first time ive seen maps consume batt while in deep sleep

Sent from my GT-I9505 using xda app-developers app
 
  • Like
Reactions: ahikmat
A

ahikmat

Senior Member
Aug 5, 2010
224
682
Seoul
Upcoming changes in newer version:

- Kernel Wakelocks (finally)
- Light theme color fixes
- Knowledge base for Kernel wakelocks

You are welcome to give feedbacks! ;)
 

Attachments

  • Screenshot_2013-07-11-13-34-17.jpg
    Screenshot_2013-07-11-13-34-17.jpg
    32.8 KB · Views: 303
  • Like
Reactions: rraaka, Anrikus, scottjb and 6 others
whitedragonz83

whitedragonz83

Senior Member
Aug 9, 2012
617
186
ishyboy15 said:
Just used this app as instructed. Maps is at 380 and exchange services is ar 40 . The only solution i can think of is turn off access to my location from location services and everything will be fine now? Any other ideas? Its just weird. Ive had the omega rom for a week now and this is the first time ive seen maps consume batt while in deep sleep

Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse

The newest maps app eliminates all wakelocks regardless of your settings. Baked everything into android processes I think.

Sent from my Galaxy Nexus using Tapatalk 4 Beta
 
  • Like
Reactions: ahikmat
T

timmyd463229

Senior Member
Dec 16, 2010
685
50
Is this a normal amount of wakelocks from android system in about a 3 day period

Sent From My JellyBeans/Zerolemon Note 2
 

Attachments

  • uploadfromtaptalk1375835912951.jpg
    uploadfromtaptalk1375835912951.jpg
    96.5 KB · Views: 796
A

ahikmat

Senior Member
Aug 5, 2010
224
682
Seoul
Wakelock detector 1.5.5 [New updates]

Today "Wakelock detector" has been updated to new version 1.5.5

There are many improvements have been done, and new features had been added.

New features

# Kernel wakelocks for "Advacned mode"

# Show active held wakelocks ( if wakelock acquired time changes on Refresh then it turns red)

# Popup menu(Google it/Copy/Tip) when user long-presses the wakelock tag

# Browsing Knowledge base items after purchase

# UI improvements
 
  • Like
Reactions: XDAMaxe, Soyuz 3, volk9029 and 7 others
Codrea

Codrea

Senior Member
May 22, 2012
287
29
gey guys how to read this wakelock detector

I have this wakelock apps

lux brightness 5 s x 3300 times

borwser 1 minute 47 s x 13 times

which one between two apps have a bigger wakelock drain?

thx
 
A

ahikmat

Senior Member
Aug 5, 2010
224
682
Seoul
Codrea said:
gey guys how to read this wakelock detector

I have this wakelock apps

lux brightness 5 s x 3300 times

borwser 1 minute 47 s x 13 times

which one between two apps have a bigger wakelock drain?

thx
Click to expand...
Click to collapse

Lux Brightness has high wakelock counts(3300),

what is the accumulation time of statistics?

can you put some screenshots?
 
B

bpaulien

Senior Member
Jan 10, 2013
381
72
Columbus
I have for the most part reduced my wakelocks to a reasonable level, but there's still a couple things taking up more than I'd like. Specifically something called *wifi* (asterisks included) and the dialer (RILJ). It's possible that the dialer is just from actually talking on the phone, but I'm pretty sure that the Wifi increase while the phone is supposed to be sleeping. Can you provide any information based on the following screen shots?

Thank you. This Is based on about 28 hours since last charged.

Sent from my LG-LS855 using xda app-developers app
 

Attachments

  • uploadfromtaptalk1377786412857.jpg
    uploadfromtaptalk1377786412857.jpg
    61 KB · Views: 608
  • uploadfromtaptalk1377786424807.jpg
    uploadfromtaptalk1377786424807.jpg
    60.5 KB · Views: 584
  • uploadfromtaptalk1377786436217.jpg
    uploadfromtaptalk1377786436217.jpg
    60.5 KB · Views: 582
  • Like
Reactions: ahikmat
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