Anyone notice problems with the NY Times app recently? I noticed some high network activity out of my Note Pro over the last few days, and dug into it last night. Turned out, my tablet never went to deep sleep, and looking at battery usage, the NY Times app was behind only the OS and System.
I can't uninstall the NY Times, but I can revert to the factory image, and that seems to have put a halt to the network activity, and also the tablet is now going into deep sleep again. So it looks like it was an app update, somewhere along the way?
What's deep sleep as opposed to sleep as opposed to going into airplane mode?? Your posting about the ny times and sleep is difficult to understand.
ericbergan said:
Anyone notice problems with the NY Times app recently? I noticed some high network activity out of my Note Pro over the last few days, and dug into it last night. Turned out, my tablet never went to deep sleep, and looking at battery usage, the NY Times app was behind only the OS and System.
I can't uninstall the NY Times, but I can revert to the factory image, and that seems to have put a halt to the network activity, and also the tablet is now going into deep sleep again. So it looks like it was an app update, somewhere along the way?
Click to expand...
Click to collapse
nychotxxx said:
What's deep sleep as opposed to sleep as opposed to going into airplane mode?? Your posting about the ny times and sleep is difficult to understand.
Click to expand...
Click to collapse
Not difficult to understand at all, this is apparently a wake lock issue with the application.
Tapping the power button to turn off the screen puts the device in sleep mode but CPU speed still varies as background activity continues. Application processes can place wake locks on the CPU to keep it from going into deep sleep which is the lowest power consumption setting. A device that never goes into deep sleep will experience higher battery drain with the screen off for extended periods than one that does go into deep sleep. Sleep has nothing to do with airplane mode, which turns off all radios and has no direct impact on CPU.
First thing I would try with the NY Times app is turn off all notifications for it. Personally I don't use it and have it frozen so I can't verify the wake lock issue on my device.
Sent from my SM-P900 using Tapatalk
muzzy996 said:
First thing I would try with the NY Times app is turn off all notifications for it. Personally I don't use it and have it frozen so I can't verify the wake lock issue on my device.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Much better explanation than I could have given, thanks! So wish I could root my tablet (a Verizon...), feel like I'm trying to debug things with both hands tied behind my back!
So far, the NYT problem hasn't come back - can't freeze or uninstall it without root, but have removed it from Magazine UI and basically backed out all updates by restoring it to its factory image and clearing its data. BTW, it was set to only get updates every 4 hours. Obviously it had a different idea.
Yeah I hate it when apps get like that.
It's times like that where I'll use Greenify sparingly to push the misbehaving app into hibernation. Otherwise I'll just let android do it's thing.
A few days ago, I noticed the NY Times app only it's you view 10 articles for free every month. I was going to say, why not trash that garbage? It requires root, though, since it's actually a system app. That is just profoundly stupid.
At least Samsung didn't pick CNN as it's news app, amirite?
Related
I've been constantly battling sleep issues. I am on PRI/NV 1.77 and latest radio. I tried downgrading to 1.77 just recently to see if it would fix it and it hasn't, but I'm staying put.
Running latest MIUI and Savage 1.6 kernel.
Spare parts had been showing on average 50% running time even though my screen on time would be something like 5%. I had read that ideally these ratios should match, since it means your phone is properly sleeping.
Spare parts shows paltry wake locks of just a few seconds or minutes for Android System as the top app. I've killed all my widgets and even tried airplane mode and don't notice too much of a drop. After getting rid of all updating widgets (minimal text and the MIUI cal widget) and stopping google calendar sync I'm currently at 30% running vs 5% screen on. I've basically got everything that would run in the BG disabled -- set cpu, system monitor, etc. Is this a "good ratio"? Any other ideas on debugging what seems to be an obvious wake lock? I've looked at logcat and don't see a thing that looks interesting, hardly any activity. Am I just being crazy or does it seem like I still have a wake lock?
Thanks for reading
If you've constantly been battling sleep issues, I would start looking at rogue apps that may be causing Android System processes to act up.
For instance:
I was battling a sleep issue with before knowing about PRI 1.90 causing it. Went so far as to reinstall my ROM wipe wipe and wipe some more before finally figuring it out.
In another instance I was battling sleep issues because of HTC's Facebook for HTC Sense. It was causing constant sync and I didn't notice because the sync icon would eventually go away, even if it took around half an hour.
One more instance, constantly changing governors with SetCPU was causing Android System process to use up a lot of CPU and my phone would become sluggish, and only after opening SetCPU and closing it again would my phone return to normal.
I would definitely start out by figuring out what apps you may have running at all times that aren't native to Android, then go from there. It sucks but once you figure it out, good times!
freeza said:
If you've constantly been battling sleep issues, I would start looking at rogue apps that may be causing Android System processes to act up.
For instance:
I was battling a sleep issue with before knowing about PRI 1.90 causing it. Went so far as to reinstall my ROM wipe wipe and wipe some more before finally figuring it out.
In another instance I was battling sleep issues because of HTC's Facebook for HTC Sense. It was causing constant sync and I didn't notice because the sync icon would eventually go away, even if it took around half an hour.
One more instance, constantly changing governors with SetCPU was causing Android System process to use up a lot of CPU and my phone would become sluggish, and only after opening SetCPU and closing it again would my phone return to normal.
I would definitely start out by figuring out what apps you may have running at all times that aren't native to Android, then go from there. It sucks but once you figure it out, good times!
Click to expand...
Click to collapse
Thanks for the reply.
So, this is a bad ratio then, i'm not nuts?
I kill EVERYTHING then sleep and i'm still seeing the issues. Is there some more fool proof way I can guarantee nothing is running before sleeping? My guess would be something syncing more than it should have. Should I try toggling everything app's sync off and then sleeping?
Ok, turned off sync, slept and the top UID was 10018, which on my phone linked back to Google Service Framework. I'm clearing data, turning off sync and watching again to see if it has issues.
lil-dice said:
Ok, turned off sync, slept and the top UID was 10018, which on my phone linked back to Google Service Framework. I'm clearing data, turning off sync and watching again to see if it has issues.
Click to expand...
Click to collapse
Interesting, I had that UID 10018 problem before and I never figured it out. It maybe Google Talk, Gmail, or even the Calendar. You may have to try clearing caches of one or all three to really see.
Cleared data, sleeping didn't improve. I slept with sync off after clearing data...i'm at a loss. I have next to nothing starting up. The only thing I can think is that Spare parts is reporting wrong information. You'd think it would be fairly easy to determine why the phone is not sleeping. If i don't even have sync turned on and it's still not sleeping as much as I feel it should be, I'm at a bit of a loss :/
lil-dice said:
Cleared data, sleeping didn't improve. I slept with sync off after clearing data...i'm at a loss. I have next to nothing starting up. The only thing I can think is that Spare parts is reporting wrong information. You'd think it would be fairly easy to determine why the phone is not sleeping. If i don't even have sync turned on and it's still not sleeping as much as I feel it should be, I'm at a bit of a loss :/
Click to expand...
Click to collapse
Under battery........what are your Up Time and Awake Time looking like?
Identical? minutes apart? seconds?
freeza said:
Under battery........what are your Up Time and Awake Time looking like?
Identical? minutes apart? seconds?
Click to expand...
Click to collapse
I'm not sure how to get to that in MIUI, in battery settings i jut see my minutes since unplugged. No Awake time.
What's a good ratio for awake/screen on? I really wouldn't want my awake time to be more than %120 of the screen on time. This can change if you regularly use the phone while the screen is off (music playing, wifi stuff, etc). At least, I'm pretty sure having the wifi on will increase your awake time.
Saturn2K said:
What's a good ratio for awake/screen on? I really wouldn't want my awake time to be more than %120 of the screen on time. This can change if you regularly use the phone while the screen is off (music playing, wifi stuff, etc). At least, I'm pretty sure having the wifi on will increase your awake time.
Click to expand...
Click to collapse
hmm ding ding ding.
Turned off wifi, did a quick 15 minute test and now my awake/screen are right in line....so what gives? Why does wifi prevent my phone from sleeping? Since i'm running MIUI i have to have wifi set to never sleep otherwise you get random reboots...feel like i'm between a rock and a hard place now :/
lil-dice said:
hmm ding ding ding.
Turned off wifi, did a quick 15 minute test and now my awake/screen are right in line....so what gives? Why does wifi prevent my phone from sleeping? Since i'm running MIUI i have to have wifi set to never sleep otherwise you get random reboots...feel like i'm between a rock and a hard place now :/
Click to expand...
Click to collapse
That's just how it is for all AOSP kernel using roms. Their wifi sleep mode is absolutely terrible. On the plus side, it seems as though it doesn't use an absurd amount of battery to keep the wifi on.
I think my phone is suffering from the Android OS keep awake bug. I just charged my phone to 100%, rebooted, opened and closed the camera app and left it alone for about an hour and a half. I am down to 92% batter life remaining. This seems excessive. The Android OS app shows a keep awake time of exactly 93 minutes which is also exactly the same as the up time.
I don't quite understand BetterBatteryStats just yet, but BetterBatteryStats shows "gps-lock" as 1h27m4s under Kernel Wakelocks since charged. Nothing else comes close. The highest Partial Wakelock is ActivityManager-Launch with 12s. Under Other Awake is 93 minutes and Screen on is 2 minutes. BetterBatteryStats is the first item under Process the surfaceflinger and com.android.phone.
Before rebooting I had set my GPS settings to (and they remained this way after reboot)
-Google's Location Service : Unchecked
-GPS satellites : Checked
-Location & Google search : Unchecked
Other stats:
-Verizon LTE
-bigxie IML74K Build 2
-franco.Kernel #12 (hotplug enabled, 350k low, 120k high)
-No widgets
-No other apps were opened
-Gmail is set to sync. I haven't run or configured Google+ (don't use it). Gmail/Calendar/Contacts should be the only things syncing, no facebook sync.
I had similar issues before flashing the kernel and rom.
How can I get this thing to go to sleep? I don't think this should be consuming so much battery life while idle.
you have a "bad app" that is preventing the phone from deep sleeping.
get cpu spy from the market to verify how long your phone is staying in each state
do you have any notifications in the notification bar?
No notifications were received in the last 90 minutes (forever alone yes). I just installed CPUSpy. This says 00:01:25 was spent in 1200Mhz, 01:39:52 in 350mhz and 0:00:0 in Deep Sleep.
How can I find what app is preventing deep sleep? The only apps listed in the battery app are Android OS, Screen, Phone Idle, Cell standby and Android System.
Wouldn't this bad app show up in BetterBatteryStats under Process?
lethologica said:
No notifications were received in the last 90 minutes (forever alone yes). I just installed CPUSpy. This says 00:01:25 was spent in 1200Mhz, 01:39:52 in 350mhz and 0:00:0 in Deep Sleep.
How can I find what app is preventing deep sleep? The only apps listed in the battery app are Android OS, Screen, Phone Idle, Cell standby and Android System.
Wouldn't this bad app show up in BetterBatteryStats under Process?
Click to expand...
Click to collapse
I don't use BetterBatteryStats so I wouldn't know.
I personally set my CPU speeds from 700-1200MHz (as indicated by Franco and others... setting it to ~300 is bad because it makes the phone use more power to catch up)
How many apps do you have? can you use AppBrain or something to provide me a list of what apps you use?
I just took a list at my CPU Spy...
0:09:51 1200Mhz
920 MHz... 0:01:35
700MHz: 0:09:49
Deep Sleep: 3:21:43
82%... 3h 50m 35s on battery
Android OS 28%
Screen 24%
Google Voice 14%
Phone idle 14%
Android system 7%
Cell standby 3%
Nova Launcher 3%
Wi-Fi 2%
Beautiful Widgets 2%
Market 2%
700-1200MHz. Conservative Governor. Hotplug off
I did try 700 with earlier versions (I think 8 & 9) and was also getting poor battery performance during idle. I wish there was an easier way to determine what app is preventing deep sleep, however it would almost certainly have to be a system app as I did not run any app when I started this test.
lethologica said:
I did try 700 with earlier versions (I think 8 & 9) and was also getting poor battery performance during idle. I wish there was an easier way to determine what app is preventing deep sleep, however it would almost certainly have to be a system app as I did not run any app when I started this test.
Click to expand...
Click to collapse
It doesn't have to be a system app. A app can be started as the moment as Android OS is started.
Not all apps are listed in that battery monitor. I can tell you that for sure. Definitely something is wrong with your phone setup.
The best way to debug it (in my opinion) would be to backup all of your apps and reflash the ROM from scratch. Flash bigxie's ROM (or try another ROM if you choose to) and Franco's Kernel.... install CPU Spy and leave the phone off for like 5-10 minutes. See if it deep sleeps.
Edit: Try this https://market.android.com/details?...251bGwsMSwxLDEsIm5leHRhcHAuc3lzdGVtcGFuZWwiXQ this should help you figure out what app it is.
Thanks for the tip. I am going to recharge and test again with all GPS settings disabled to rule the GPS out. Seeing the gps-lock as the top process in Kernel Waitlocks makes me wonder. I will give SystemPanelLite a try after this test.
lethologica said:
Thanks for the tip. I am going to recharge and test again with all GPS settings disabled to rule the GPS out. Seeing the gps-lock as the top process in Kernel Waitlocks makes me wonder. I will give SystemPanelLite a try after this test.
Click to expand...
Click to collapse
You did update to the latest Google Maps right? it contained fixes for the battery. Maps is a huge drain if it runs in the background. I always leave my GPS deactivated even though it's activated ondemand. I just don't trust it.
Ahh hah! It has only been 20 minutes, but the GPS is the culprit. I did the same charge, reboot, camera cycle. Then I walked away. Checked CPUSpy and sure enough there was 18 minutes of deep sleep time out of a 20 minutes up time. Google Maps is up to date by the way.
Now the funny thing is, the GPS isn't all that great even when it was keeping my phone awake. Last night I checked the GPS after I got out of the subway (public transit, not sandwiches), for a second it still thought I was in the location prior to taking the subway. It took close to ten seconds to get within 500 meters of my location, and after that it was unable to pinpoint my exact location. The phone has been able to pinpoint my exact location in the past though.
So now, how can I determine if this is a software bug or a hardware bug? If it is software then no big deal, I can hold out. If it is hardware then I need to revert to factory, unroot, etc.
lethologica said:
Ahh hah! It has only been 20 minutes, but the GPS is the culprit. I did the same charge, reboot, camera cycle. Then I walked away. Checked CPUSpy and sure enough there was 18 minutes of deep sleep time out of a 20 minutes up time. Google Maps is up to date by the way.
Now the funny thing is, the GPS isn't all that great even when it was keeping my phone awake. Last night I checked the GPS after I got out of the subway (public transit, not sandwiches), for a second it still thought I was in the location prior to taking the subway. It took close to ten seconds to get within 500 meters of my location, and after that it was unable to pinpoint my exact location. The phone has been able to pinpoint my exact location in the past though.
So now, how can I determine if this is a software bug or a hardware bug? If it is software then no big deal, I can hold out. If it is hardware then I need to revert to factory, unroot, etc.
Click to expand...
Click to collapse
It's probably software. Something is keeping the GPS on. Either by a app or ROM. Most likely app.
If you're not using gps with google location services, it will take a while to lock.
Also, you have an app that is requesting GPS constantly while the phone is sleeping.. That is all.
joshnichols189 said:
Also, you have an app that is requesting GPS constantly while the phone is sleeping.. That is all.
Click to expand...
Click to collapse
Any idea on how to figure out what that app is?
I'm not sure how to find an app that is constantly requesting GPS, but I know the app Watchdog will help find an app that is running in the background consuming processor cycles.. you might want to try that but I have no idea if it will work.
holy ****! thank you! I've been trying to figure out what was causing my phone to not deep sleep for a week! I uninstalled google maps and it worked! now I'd like to figure out how to have both deep sleep and google maps installed...
did you tuck your phone in?
I had that problem with a Rom and turning on and off the Bluetooth would fix the problem.
Sent from my GalaxyNexus using Tapatalk
imail724 said:
holy ****! thank you! I've been trying to figure out what was causing my phone to not deep sleep for a week! I uninstalled google maps and it worked! now I'd like to figure out how to have both deep sleep and google maps installed...
Click to expand...
Click to collapse
Try disabling GPS when you're not using it. Worked for me.
i tried to freeze the google maps, but still getting the GPS wakelock.
from the other thread, some one mentioned about facebook.
i freeze facebook in titanium backup. looks like the GPS time is not increasing.
are you guys having this issue installed facebook app?
the other thread:
http://forum.xda-developers.com/showthread.php?t=1419087&page=3
I charged my Nexus LTE(unrooted,4 days old) till it was 100% before I went to bed. As soon as I set my alarm I unplugged it to test to idle. Well I just woke up 6 hours later and it was completly dead. I have it on the charger now, I hope i can see the spycpu cause that was main purpose for leaving it off. I do not sleep surf either.
Is this a defective phone?
Wow that's nuts. I definitely never get that sort of battery drain. Are you rooted? Using a custom rom or just stock?
jd1001 said:
Wow that's nuts. I definitely never get that sort of battery drain. Are you rooted? Using a custom rom or just stock?
Click to expand...
Click to collapse
unrooted.
I have to leave for work now with out a phone, I will try to check up via computer (feeling like a dinosaur).
Ha ha I know I feel so bad when I don't have my phone. Maybe see if it happens again tonight. If it does I would get on to the carrier. Have a good day at work!
jd1001 said:
Ha ha I know I feel so bad when I don't have my phone. Maybe see if it happens again tonight. If it does I would get on to the carrier. Have a good day at work!
Click to expand...
Click to collapse
Ill try both.
It has been documented the Verizon has battery issues but not sure if they were meant to be fixed in the 4.0.2 update
davewinkwink said:
I charged my Nexus LTE(unrooted,4 days old) till it was 100% before I went to bed. As soon as I set my alarm I unplugged it to test to idle. Well I just woke up 6 hours later and it was completly dead. I have it on the charger now, I hope i can see the spycpu cause that was main purpose for leaving it off. I do not sleep surf either.
Is this a defective phone?
Click to expand...
Click to collapse
Are you sure it was dead or you just had a sleep of death? If it truly was dead you definitely have something draining your battery during idle. I highly recommend you turn off your LTE antenna if you haven't already unless your using data intensive apps and you need it, such as surfing or netflix or something. Also, change your sync times to less often, I do every 15min. Sign out of google talk, use wifi when you can, adjust screen brightness, disable bluetooth. White backgrounds will eat your battery faster as well. What else am i forgetting.... Root will help if you can manage to, its incredibly easy especially with the new rootkit out, because you can load francos newest build which has increased my battery 2x, with 25% drain in the last 8.5 hours even with a 1/2 hr of whale tail last night. Also make sure your not running something stupid in your background thats eating your battery like a task killer or battery spy or something, those just rape your battery
If you turn on Google+ instant upload and it has thousands of pictures to upload that will kill your battery in a few hours. If your phone is staying awake because of Android OS then try turning off your GPS.
Sent from my Transformer Prime TF201 using xda premium
As noted in a lot threads on a lot of forums, there are some phones that have a problem with the Android OS and the "Keep Awake" time. There seems to be an issue with some phones not truly going to sleep when the power button is used to turn off the screen as opposed to letting the screen turn off automatically when the screen times out. This results in a very high time in the Settings/Battery/Android OS/Keep Awake menu.
In stock form and with every rom that I have installed, my "Keep Awake" time was always about 50-60% of my total battery time. If the phone had been off charger for 8 hours, I'd have 4-6 hours of Andorid OS "Keep Awake" time. This was true even if the phone had been in my pocket unused and seems to be exacerbated by my habit of turning the screen off manually with the power button every single time. I used to never let the screen timeout.
There seems to be two "fixes" according to Franco (of kernel fame). One concerns the camera. Seems the camera is started and then turned off during startup. But in so doing, it leaves a sensor active and this prevents the phone from actually going to sleep. So he recommends starting and using the back button to go back to the home screen. The other is DRM Protected Content. He recommends this be disabled or frozen. A third, that I don't believe I recall seeing him recommend but that I have seen on his thread at XDA (down for blackout right now) is to disable Maps.
I have done all three of those and my Keep Awake time has gone from 40-50% of my total battery time down to a few percentage points. I mean if I don't use my phone it will now show less than a minute of Keep Awake time per hour.
Good luck
My VZW nexus can idle with moderate use on constant LTE and get 15 hours with out issue. Hell I have even gotten more so check google+ as suggested. If it went dead on idle with nothing running constantly to cause it than I would say your phone and/or battery is defective
Geezer Squid said:
As noted in a lot threads on a lot of forums, there are some phones that have a problem with the Android OS and the "Keep Awake" time. There seems to be an issue with some phones not truly going to sleep when the power button is used to turn off the screen as opposed to letting the screen turn off automatically when the screen times out. This results in a very high time in the Settings/Battery/Android OS/Keep Awake menu.
In stock form and with every rom that I have installed, my "Keep Awake" time was always about 50-60% of my total battery time. If the phone had been off charger for 8 hours, I'd have 4-6 hours of Andorid OS "Keep Awake" time. This was true even if the phone had been in my pocket unused and seems to be exacerbated by my habit of turning the screen off manually with the power button every single time. I used to never let the screen timeout.
There seems to be two "fixes" according to Franco (of kernel fame). One concerns the camera. Seems the camera is started and then turned off during startup. But in so doing, it leaves a sensor active and this prevents the phone from actually going to sleep. So he recommends starting and using the back button to go back to the home screen. The other is DRM Protected Content. He recommends this be disabled or frozen. A third, that I don't believe I recall seeing him recommend but that I have seen on his thread at XDA (down for blackout right now) is to disable Maps.
I have done all three of those and my Keep Awake time has gone from 40-50% of my total battery time down to a few percentage points. I mean if I don't use my phone it will now show less than a minute of Keep Awake time per hour.
Good luck
Click to expand...
Click to collapse
Ive been getting good battery life, despite my awake time being around 6-8 hours at the end of a charge. I tried the camera close but that never helped, I've just disabled DRM though. Also, GPS locator has been associated with this, which is probably what you meant by "maps". I just turn off my location unless i need it for navigation in location settings
how do you disable drm? and what exactly is it?
Peesashiz said:
how do you disable drm? and what exactly is it?
Click to expand...
Click to collapse
It has to do with digitally protected files, music, etc. One time I went home screen/menu/settings/apps/all/drm/disable. The last time I did it from Titanium and pressed the freeze button for that app.
Good luck.
BTW, both actions can be reversed.
This has been bugging me for a while and im not sure if its a universal issue or just me,
When they updated the HOX from 4.0.3 to 4.1.1 they introduced the power saving mode, which one of the features involves shutting down the 3G radio when the screen is off and turning it on periodically to for email/whatsapp/facebook/whatever...
So all push notification only work periodically every X minutes instead of being almost instantaneous.
No problem, we turn off power saving mode and its suppose to be disable leaving the 3G radio operational at all times, no ?
Well... no. apparently its a problem im encountering in all sense roms, they all have the same issue, the 3G power saving is still on even if i turn off power saving mode,
Anyone else experiences this ?
If I remember correctly, basically our phones have 3 states: awake/active (your using it), a sort of light sleep, and after some time of not using sleep. I believe that when it goes to sleep the phone will not reconnect to data to update unless the app tells the phones to come out of the 3rd stage, sleep. So really it all depends on how often you have your apps set to update. If you believe you're apps are set correctly and your phone should be waking to update, you can get an app from the play store like gsam and you will want to look for anything that says wake locks. An app that wake locks is an app that is bringing your phone out of sleep to update and so forth. I would start with those things to see if your apps are behaving as they should.
For some reason my M9 doesn't want to go into deep sleep much. Out of the 1 hour I have it off the charger, only 2 minutes were in deep sleep. I haven't used the phone at all in that 1 hour, so I'm not sure why it wouldn't be sleeping.
Does anyone have this problem or know how to fix it? Thanks
https://play.google.com/store/apps/details?id=nextapp.systempanel.r1
Buy, install, do proper settings, put it into monitoring mode.. then switch of screen and go sleep - in the morning see the activities what were happening during the night monitored..
jauhien said:
https://play.google.com/store/apps/details?id=nextapp.systempanel.r1
Buy, install, do proper settings, put it into monitoring mode.. then switch of screen and go sleep - in the morning see the activities what were happening during the night monitored..
Click to expand...
Click to collapse
I've used a very similar app. There are no wake locks. All it says is "Android OS" is using 100% of the screen off battery. Even in the normal HTC battery settings, android OS is using 100%. Thanks for the help though.
System Panel is neither similar nor showing you those funny wakelocks..
It thoroughly informs you about CPU usage last night..
jauhien said:
System Panel is neither similar nor showing you those funny wakelocks..
It thoroughly informs you about CPU usage last night..
Click to expand...
Click to collapse
Thanks, but all those apps are the same. They can only get a certain amount of info from the core system. There are apps that do the exact same thing for free, which is what I use.
As an update to my problem, rebooting the phone and clearing cache seemed to have solved the issue for now.
aooga said:
Thanks, but all those apps are the same. They can only get a certain amount of info from the core system. There are apps that do the exact same thing for free, which is what I use.
As an update to my problem, rebooting the phone and clearing cache seemed to have solved the issue for now.
Click to expand...
Click to collapse
If you run out of ideas on how to fix this, I'd say get root, get Xposed, and get Power Nap. Pretty much blocks all wakelocks at night and I see like 1% drain the next morning.
Cryosx said:
If you run out of ideas on how to fix this, I'd say get root, get Xposed, and get Power Nap. Pretty much blocks all wakelocks at night and I see like 1% drain the next morning.
Click to expand...
Click to collapse
Wait...xposed works on 64bit phones? Wow I've been missing out for nothing lol.
Yes, but make sure you use the xposed arm64 file.
This thread has the stuff
Here's the zip you want xposed-sdk21-arm64.zip
And you also need the alpha installer.