Hello there! I have a S7E rooted and I have the following wake locks that are bugging me (can't find any info on them).
13960000.decon_f
ssp_wake_lock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
andrepcg said:
Hello there! I have a S7E rooted and I have the following wake locks that are bugging me (can't find any info on them).
13960000.decon_f
ssp_wake_lock
Click to expand...
Click to collapse
Your sensors and screen on time.
You know Google, right? They actually made your OS, but they have this big search engine which can give thousands of answers.
Faspaiso said:
Your sensors and screen on time.
You know Google, right? They actually made your OS, but they have this big search engine which can give thousands of answers.
Click to expand...
Click to collapse
I searched but every forum I went nobody had an answer, or I couldn't find it. I always search before asking
andrepcg said:
I searched but every forum I went nobody had an answer, or I couldn't find it. I always search before asking
Click to expand...
Click to collapse
Well there you have your answer. I confirmed both with a Google search though.
You can't change kernel wakelocks without a custom kernel, but yours are normal. Disable some things you use, that use sensors if the battery life annoys you. But really, it don't drain much.
Partial Wakelock and Alarms are the things you have the ability to change.
I just really wanted to know what they are that 13960000.decon_f name was pretty weird and I decided to investigate.
Thanks guys!
Faspaiso said:
Well there you have your answer. I confirmed both with a Google search though.
You can't change kernel wakelocks without a custom kernel, but yours are normal. Disable some things you use, that use sensors if the battery life annoys you. But really, it don't drain much.
Partial Wakelock and Alarms are the things you have the ability to change.
Click to expand...
Click to collapse
I am also having the same issue. But i am having custom kernel on my s7e. So what I have to do? Please explain step by step.
Sent from my SM-G935F using XDA-Developers mobile app
nimalen87 said:
I am also having the same issue. But i am having custom kernel on my s7e. So what I have to do? Please explain step by step.
Click to expand...
Click to collapse
Which kernel do you use? You need a kernel that have synapse. AEL and Superkernel have Synapse support which can disable kernel wakelocks. Don't know about other kernels.
decon_f
should match your screen on time
"It's a wakelock that is taken when you turn your screen on. The count is how many times you turned your screen on and the time is your screen on duration. It has zero effect on battery consumption." [email protected]
ssp
advanced sensor hardware
https://github.com/gokulnatha/GT-I9505/blob/master/drivers/sensorhub/Kconfig
I had the 13960000.decon_f when I had the xposed module Fingerprint enabler enabled. After turning that off it vanished. Now, its returned again. Is there any way to detect what was causing the wake lock
sohojmanush said:
I had the 13960000.decon_f when I had the xposed module Fingerprint enabler enabled. After turning that off it vanished. Now, its returned again. Is there any way to detect what was causing the wake lock
Click to expand...
Click to collapse
I just told you what it is one post above yours. That wakelock has NO effect on battery. Ignore it.
Just chipping in here, as I see some people's answers are on the hostile end of the spectrum.
I also have the 13960000.decon_f wakelock on my s7 flat that I'm trying to figure out. The amount of time for this wakelock is about an hour, but my screen on time so far is 3 hours. So there doesn't seem to be a direct link between the 2 so far
However, I also have a PowerManagerService.Display wakelock that is identical to that of the decon_f wakelock
theo5388 said:
Just chipping in here, as I see some people's answers are on the hostile end of the spectrum.
I also have the 13960000.decon_f wakelock on my s7 flat that I'm trying to figure out. The amount of time for this wakelock is about an hour, but my screen on time so far is 3 hours. So there doesn't seem to be a direct link between the 2 so far
However, I also have a PowerManagerService.Display wakelock that is identical to that of the decon_f wakelock
Click to expand...
Click to collapse
The 13960000.decon_f wakelock seems to match up with SOT for me—not exactly, but with about a small difference that seems to get larger as the day goes by, which I presume means the wakelock takes a second or something after turning the screen off to actually unlock. So what dynospectrum said seems to check out for me, but it's very interesting that it doesn't match up for others. I wonder if there could be something that causes it to hold the wakelock longer after the screen is turned off, resulting in the longer time. @dynospectrum, do you happen to have a link back to the source where @AndreiLux wrote that quote you posted?
It doesn't for me definitely. decon_f wakelock around 12h 31min, while my SoT is only 30 minutes.
Related
I'm sure almost everyone has now experienced the freeze that happens sometimes when the device comes out of deep sleep, usually for a couple seconds.
I (personally) think its the only thing from making this ROM pretty near perfect. I have been trying to get to the bottom of this freezing issue for a few days and I'm sure a lot of other people have been trying too!
I have disable a whole bunch of things, and since it seems it could be related to WiFi (as many are reporting) I started disabling and uninstalling apps in different stages. Iv ended up with the following (see screenshots) disabled/uninstalled and have been repeatedly locking and unlocking the device (letting it enter deep sleep first of course) and have yet to experience the bug again.
Maybe it doesn't work for you, but perhaps someone can pick up from here and we can all get to the bottom of the problem! It might be impossible at this stage and may simply require a newer leak/release of JB for the i9100.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 1513810
View attachment 1513811
Hopefully this helps, if not I apologize, but think the problem needs any insight available
I have not freezed, deleted all the extra functionalities and stuff, but the problem is still there, even worst on wifi. I gave u a thank for make a step up to try to solve the problem
I have removed almost every single samsung app from syatem. Using apex instead of TW. Always have wifi turned off. Because i use my data plan. As its unlimited. I have this problem all the time. Is there anything i can do to help? Logcat or anything.
Sent from my GT-I9100 using Tapatalk 2
I think its a touch panel driver problem but better to do a logcat if you have time for this. I also have experienced the problem when trying to end a call.
gszabi said:
I think its a touch panel driver problem but better to do a logcat if you have time for this. I also have experienced the problem when trying to end a call.
Click to expand...
Click to collapse
Yes, last night I was using logcat and when the screen came on and froze the logcat contained data such as waiting for input, loading mali driver for touch recognition. I laso thought it could be related to motion control, as if its waiting for acceleration from it so as to use the camera motion shortcut etc but alas disabling motion didnt help either
Will upload a logcat or two later after college today!
It also happened to me too when trying to end a call after the screen came back on after taking the phone away from my eat. Ive also noticed that when the screen comes on and touch is unresponsive. The menu and back keys at the bottom are not lit. And after 4/5 seconds they light up and then it is working. Will post a logcat when i next experience it.
Sent from my GT-I9100 using Tapatalk 2
Tried many lock screen apps including the stock one, random freezing with all of them with wifi on. Have been using Holo Locker for a couple of days, seems to fix the problem.
darkloop said:
Tried many lock screen apps including the stock one, random freezing with all of them with wifi on. Have been using Holo Locker for a couple of days, seems to fix the problem.
Click to expand...
Click to collapse
I get around it like another user suggested,
I have a tasker that turns my wifi off when the screen goes off.
I also have phenomenal battery life this way. It is definitely a wifi issue.
I'm switched over to the latest OmniROM nightly (Currently 20140125) for my Find5 but discovered a bad wakelock I never experienced before. It keeps the phone in a wake state like 95% of all the time.
sns_periodic_wakelock
Google and Forum search for it showed up several possiblitys, I tried to eliminate them all. Today I completely wiped my phone and installed the latest Omni nightly on a blank device with TWRP + Core Google Apps without installing any other additional app to it.
And still the sns_periodic_wakelock was there. So it must be caused by something related to google core apps or omnirom itself.
Did anybody discovered something similar with Omni Rom on find5? I never had this before on non kitkat roms.
And it's not just a display fail, the battery is really draining fast with omnirom. Unsubale in my case. Charging to 100% and 3hrs later just letting my phone "sleep" the batery is already down at 20% with only 5min display time.
Any suggestions would be awesome!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had this too ...think it was right after i switched to omni. For me the next nightly or the one after it fixed it for me. That's all I can say.
Sent from my Find 5 using XDA Premium 4 mobile app
Last time I saw an "SNS_XXXXXXXXX" wakelock...was when I had a stockish ROM, and the big hint as to what it was-was the FaceBook icon for the wakelock.
I suspect a social networking app is the culprit. "SNS" standing for "social networking service".
Today I totaly whiped the phone again and installed the latest omni again. Seems to work because now the SNS Wakelock is still present but below 5%. Strange...
I keep an eye on that.
solarizde said:
Today I totaly whiped the phone again and installed the latest omni again. Seems to work because now the SNS Wakelock is still present but below 5%. Strange...
I keep an eye on that.
Click to expand...
Click to collapse
My guess is that it's in gapps somewhere... Or maybe it's in the blobs... I should look through the blobs directory for that string.
While it's listed as a kernel wakelock, it is not actually present in the kernel as far as I can tell. It also doesn't appear in any of the frameworks.
(While most Android wakelocks go through the PowerManagerService and all get lumped under a single wakelock at the kernel level, it IS possible for any userspace application to grab a kernel wakelock of any name.)
Skripka said:
Last time I saw an "SNS_XXXXXXXXX" wakelock...was when I had a stockish ROM, and the big hint as to what it was-was the FaceBook icon for the wakelock.
I suspect a social networking app is the culprit. "SNS" standing for "social networking service".
Click to expand...
Click to collapse
not at all
sns are sensor wakelocks
@Entropy512 you will find this in the sensors.qcom binary
sns_async_ev_wakelock
sns_periodic_wakelock
maxwen said:
not at all
sns are sensor wakelocks
@Entropy512 you will find this in the sensors.qcom binary
sns_async_ev_wakelock
sns_periodic_wakelock
Click to expand...
Click to collapse
Sounds to me like some app is asking for sensor data and causing the wakelock then.
Hello everyone,
I have this weird wakelock that shows up under Kernel wakelock. It usually with or below display wakelock and i'm not sure what it is. I searched Google but no answer.
The wake lock is
13800000.decon_fb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the help
If I remember correctly, I read it somewhere that wakelock ia related to. Screen display
Sent from my SM-N910C using Tapatalk
iznee said:
If I remember correctly, I read it somewhere that wakelock ia related to. Screen display
Sent from my SM-N910C using Tapatalk
Click to expand...
Click to collapse
I heard that too, but haven't seen any confirmation of this.
It's always at or near the top of my wakelocks.
Sent from my SM-N910U
Its really annoying
In the code on the following page 13800000.dexon_fb is mentioned 75 times. Does any body know what the code is for? Maybe it will tell some info regarding this wakelock
http://pastebin.com/PPC1sqmv
Yathani said:
Hello everyone,
I have this weird wakelock that shows up under Kernel wakelock. It usually with or below display wakelock and i'm not sure what it is. I searched Google but no answer.
The wake lock is
13800000.decon_fb
Thanks for the help
Click to expand...
Click to collapse
hi ,
Long shot...... "Facebook " app ?
.I have read ( quite a few threads in past) that Facebook app, can cause wakelocks and battery drain etc etc .
But then again i stated.."long shot "
good luck
I uninstalled Facebook completely, however the wakelock is still there. As seen from the code that I referred to above, it is not connect with 3rd parts apps. It looks like that it is connected with Samsung staff. Can anyone tell what that code is for?
Just ignore it.
It's a wakelock that is taken when you turn your screen on. The count is how many times you turned your screen on and the time is your screen on duration. It has zero effect on battery consumption.
AndreiLux said:
Just ignore it.
It's a wakelock that is taken when you turn your screen on. The count is how many times you turned your screen on and the time is your screen on duration. It has zero effect on battery consumption.
Click to expand...
Click to collapse
Thanks a lot, only after reading your post I noticed that the time of this wakelock is the same as screen on time.
AndreiLux said:
Just ignore it.
It's a wakelock that is taken when you turn your screen on. The count is how many times you turned your screen on and the time is your screen on duration. It has zero effect on battery consumption.
Click to expand...
Click to collapse
Thanks AndreiLux. I have my doubt about this wakelock 13800000.decon_fb as well. After a few googlings, it brought me here and I have the answer.
T
Facebook AppManager wakelock faulty
I just googled 13930000.decon.fb on Note5 abnormal wakelock and came here, now I know it's equal to SOT (thx to AndreiLux) but for those about to complain about abnormal battery drain :
Facebook consumes battery heavily, "and specially" when it is installed as system App with com.facebook.appmanager beside of it.
Uninstall/freeze com.facebook.appmanager or debloat Facebook totally, reboot and install it again from any market (Google Play is preferred).
It will still be draining but way much better than before
I don't think it has anything to do with screen... i get 1 hour and 30 minutes kernel wake with this on a 5 hours standby time during the night... and FB in hibernation mode by Greenify module. for now it's a mystery to me but just to satisfy my curiosity I'll see what can be done.
I will provide some method to save battery life to an extent
This method is suitable for most of device running Android 4.0.3 or above
Basic Requirements
Xposed Framework
Amplify
Ad Away
Root.Click to read how to rooo your zenfone 2 http://forum.xda-developers.com/general/general/root-zenfone-2-t3142597/post61523207#post61523207
Greenify
Basic things you must notice before starting
Display
Brightness of your phone is a major factor for the draining of tje battery. The more the Display Brightness is the more the battery used. So i suggest you to switch from auto brightness to manual.
Wifi
Even though the wifi is not in use, your phone searches for available wifi networks available.
You can Switch of this feature by going to Wifi>Options(on the top right corner of your phone)>Advanced>Scanning always available(off).
Location
Turn off the Location Service when not in use.You can also set the location to 'Device Only" in settings.
Thses are the basic things for battery saving.
GREENIFY
For using this you need Xposed .
Download:- http://forum.xda-developers.com/showthread.php?t=3034811
Once you have the donation package of greenify with you ,you need to activate the Greenify Xposed Module in Xposed. Then enable boost mode and experimental Features.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some of the apps that i greenified are
[*]Browser
[*]Google+
[*]Messenger
[*]Music
[*]XDA
[*]Album
[*]Calender
[*]Camera
[*]File Commander
[*]MX Player
[*]Maps
:good::good:
Do not Greenify Dialer or Messaging apps
B]AMPLIFY[/B]
It is one of the most useful toll in saving battery.You'll need a donation package to block wakelocks and alarms.
After installing this app you must LIMIT THE FOLLOWING
Alarms(Allow every 600 seconds)
com.android.internal.telephony.data-stall
Alarms(Allow every 7200 seconds)
android.content.syncmanager.SYNC_ALARM
android.net.ConnectivityService.action.PKT_CNT_SAM PLE_INTERVAL_ELAPSED
com.oasisfeng.greenify.CLEAN_NOW
com.facebook.push.mqtt.keepalive.KeepaliveManager. ACTION_INEXACT_ALARM.com.facebook.katana
com.facebook.common.executors.WakingExecutorServic e.ACTION.ALARM.com.facebook.katana
Wakeful StateMachine: GeofencerStateMachine(Updated)
NfcService:mRoutingWakeLock(Updated)
Alarms[LOCATION](Allow every 40000 seconds)
ALARM_WAKEUP_LOCATOR(com.google.android.gms.nlp.AL ARM_WAKEUP_LOCATOR)
ALARM_WAKEUP_CACHE_UPDATER
ALARM_WAKEUP_BURST_COLLECTOR(com.google.android.gm s.nlp.ALARM_WAKEUP_BURST_COLLECTOR)
com.google.android.gms.location.fused.GPS_ALARM_BA LANCED_ACCURACY
ALARM_WAKEUP_ACTIVE_COLLECTOR
ALARM_WAKEUP_PASSIVE_COLLECTOR
ALARM_WAKEUP_BURST_COLLECTION_TRIGGER
Alarm(Allow every 84000 seconds)
android.app.backup.intent.RUN
com.google.android.gms/.checkin.EventLogService$Receiver
com.google.android.gms/.checkinCheckinService%Receiver
Wakelocks(Allow every 800 seconds)
WakefulIntentService[GCoreUlr-LocationReportingService]
RILJ(Updated)
Wakelocks(Allow every 7200 seconds)
[*]*net_scheduler*
[*]GCoreFlp
[*]Icing
Wakelocks(Allow every 40000 seconds)
[*]NlpWakeLock
[*]NlpCollectorWakeLock
[*]LocationManagerService
[*]Config Service Fetch
Services(Block/Deny)
com.google.android.gms/com.google.android.location.internal.AnalyticsSamp lerService
com.google.android.gms/com.google.android.location.internal.AnalyticsSamp lerService
And last but not the least:-
Ad Away
Most of you may face a problem while using internets..ads.. Ads are one of the main factor for the loss of battery. By installing AdAway,you can save battery to an extent.
IF THIS HELPED YOU, PLEASE LIKE MY POST, AND YOU ARE FREE TO ASK ANY QUESTIONS ABOUT THE SAME:good::good::good: :fingers-crossed:
Special thanks to vaisakh7..His original thread is seen here.
Cool specs
This smartphone is so cool. Specs are also great.
anchal joshi said:
This smartphone is so cool. Specs are also great.
Click to expand...
Click to collapse
Yeah,it is a good phone. But many useless apps are running which causes battery loss. I only made this post for helping how to stop such applications
Did you just copy this from another thread ? So you gain lots of like just my opinion peace
Nice post but currently I am using the free version of Amplify and quite satisfied with it.
Sent from my ASUS_Z008D using Tapatalk
pato2015 said:
Did you just copy this from another thread ? So you gain lots of like just my opinion peace
Click to expand...
Click to collapse
Not at all ... I juast tried so many apps and found these. Amplify and greenify are some common apps. But only thing i contributed here is the ways for using amplify. Other steps are some common ones
Thanks for the effort!
I can't seem to find some of the Amplify items.
I'm guessing that they're app-specific though (ie. the .facebook alarms are only because you have the Facebook app installed)?
And I can't find any of the services in order to disable them, do you know what app they're affiliated with?
azthemansays said:
Thanks for the effort!
I can't seem to find some of the Amplify items.
I'm guessing that they're app-specific though (ie. the .facebook alarms are only because you have the Facebook app installed)?
And I can't find any of the services in order to disable them, do you know what app they're affiliated with?
Click to expand...
Click to collapse
Dont worry about all the paths. Id u r unable to find these paths just ignore those. Its based on some apps u download like facebook etc.. only look for what you have
Please dont use light green or blue on white background... but I appreciate the work
Hi, I did not use my phone for the last few hours and it was in Airplane mode.
My battery still decreased and BetterBatteryStats says, that the phone was nearly always awake with screen off. Deep Sleep was only used 2% of the time?
Does anyone have an idea why?
no... but you are not the only one with this issue..
if you clear cache ou you recovery you will get this issue fixed for a day or two. but them it comes back again
To have an idea, we'd need to know about your setup (or have your phone) since a lot of us don't have that problem. It sounds like a rogue app that you could nail down by enabling true battery stats and wakelocks on GSAM. (Sorry I know little about BBS). Check out a thread I started here that worked for most to enable full battery stats without root: https://forum.xda-developers.com/honor-8/how-to/gsam-nougat-how-to-grant-permissions-to-t3528453
Then check battery usage after a few hours and upload a snap of it here. Also check kernel wakelocks and do the same from GSAM. (If you feel like going this path, of course).
I'm seeing the same on OP5/4.5.5;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this shows the GSAM "app sucker", which indicates that after 1.5hours of light use, the Kernel keeps it awake for 59 minutes.
A while before that, I took a screenshot using BBS (xda edition) which shows lots of "awake, but screen off" activity
It all looks like this in the regular battery graph which clearly shows too much "Awake"
Picture 1 suggests this is the kernel so I'm having a hard time troubleshooting. I did clear cache from recovery, but that didn't help
I had the same problem as well, but uninstalling Facebook and Messenger made a huge different in the awake time when the screen was off.
I understand facebook is powerhungry, but this is more than just that. This is something gone rogue. The fact that the kernel consumes it makes it harder to track. Otherwise, "facebook" would be listed on top.
asc366 said:
I'm seeing the same on OP5/4.5.5;
this shows the GSAM "app sucker", which indicates that after 1.5hours of light use, the Kernel keeps it awake for 59 minutes.
A while before that, I took a screenshot using BBS (xda edition) which shows lots of "awake, but screen off" activity
It all looks like this in the regular battery graph which clearly shows too much "Awake"
Picture 1 suggests this is the kernel so I'm having a hard time troubleshooting. I did clear cache from recovery, but that didn't help
Click to expand...
Click to collapse
From your first (GSAM) screen, could you show from the pulldown there "Kernel Wake Locks"? Thanks either way.
Almost all userspace apps cause the kernel to spin (since it's what does much of the work), so it'd be nice to figure out which wakelocks are being spun out. Sometimes wakelocks are called for and never picked up as well.
Here's the shots I'm asking for from mine (keep in mine that mine is currently at 21+ hours of usage so my held awake times are OK):
hachamacha said:
From your first (GSAM) screen, could you show from the pulldown there "Kernel Wake Locks"?
Click to expand...
Click to collapse
See attached
asc366 said:
See attached
Click to expand...
Click to collapse
Seems pretty clear that it's an app out of control wakelock wise. I don't think GSAM allows you to break the combined non kernel app wakelocks down further, but BBS..
BBS should let you break those down and give you a better idea which app is causing it. If not, you could try force-closing whatsapp and whatever else is usually running on your phone, resetting the statistics and and seeing what accumulates.
I too face the same issue. Hibernated all apps, turned on battery saver, turned on airplan mode but still battery is draining like hell. I saw it got drained to 6-7% when i woke up in morning.
PrakashGD said:
I too face the same issue. Hibernated all apps, turned on battery saver, turned on airplan mode but still battery is draining like hell. I saw it got drained to 6-7% when i woke up in morning.
Click to expand...
Click to collapse
How'd you hibernate all apps without having root? Just curious. That sounds like something you could only do from TB with root in Nougat.
Anyway: If you're certain you've got every app frozen, then only drastic measures are left like "reset". If you've already tried that, then only more drastic measures remain as in reinstalling all basic firmware.
hachamacha said:
bbs break those down and give you a better idea which app is causing it. If not, you could try force-closing whatsapp and whatever else is usually running on your phone, resetting the statistics and and seeing what accumulates.
Click to expand...
Click to collapse
Im nonrooted but use adb to give bbs more data. Can i still do what you suggest?
Btw. For what is the Standby Mode in Dev options?
asc366 said:
Im nonrooted but use adb to give bbs more data. Can i still do what you suggest?
Click to expand...
Click to collapse
I suppose if you can manage to give BBS more permissions then it's "possible". I don't use BBS so don't know if that's a doable thing. I would give it a try. I just googled how to break down the wakelocks using BBS and there's several pieces about it but they all involve root. I just think it's possible since I found the GSAM way to do root-type stats without being rooted.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
Kallmeidroppe said:
Btw. For what is the Standby Mode in Dev options?
Click to expand...
Click to collapse
I see no "standby mode" in my dev options in 4.5.5. Which OS version and type?
Im in 4.5.5 oos. ITS one under the newstart Option. In German its" erweiterter Neustart"
http://www.directupload.net/file/d/4786/3zv2bnbx_png.htm
Kallmeidroppe said:
Im in 4.5.5 oos. ITS one under the newstart Option. In German its" erweiterter Neustart"
http://www.directupload.net/file/d/4786/3zv2bnbx_png.htm
Click to expand...
Click to collapse
It's Doze toggle.
Kallmeidroppe said:
Im in 4.5.5 oos. ITS one under the newstart Option. In German its" erweiterter Neustart"
http://www.directupload.net/file/d/4786/3zv2bnbx_png.htm
Click to expand...
Click to collapse
I still don't have it unless it's the reboot "extended/advanced" one where it allows a multi-tier reboot (recovery, bootloader or system).
From Battery History present in OnePlusLogKit (Developer Options -> Get logs -> other log info)
I see:
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:52:qcom,glink-smem-native-xprt-dsps: 59m 0s 57ms (9404 times) realtime
Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 23m 20s 583ms (752 times) realtime
In a 4 hour period.
asc366 said:
I understand facebook is powerhungry, but this is more than just that. This is something gone rogue. The fact that the kernel consumes it makes it harder to track. Otherwise, "facebook" would be listed on top.
Click to expand...
Click to collapse
Not necessarily, since a lot of processes facebook uses are tied into system processes. It's worth a shot, I mean I replaced it with a third party app and my awake time went down significantly.
hachamacha said:
How'd you hibernate all apps without having root? Just curious. That sounds like something you could only do from TB with root in Nougat.
Anyway: If you're certain you've got every app frozen, then only drastic measures are left like "reset". If you've already tried that, then only more drastic measures remain as in reinstalling all basic firmware.
Click to expand...
Click to collapse
Greenify also works without root..