Already using man. Facebook is greenified but not much effect. This crappy app doesn't work well in greenifyWhy don't you skip amplify and use greenify for the apps instead? Ever tried?
Already using man. Facebook is greenified but not much effect. This crappy app doesn't work well in greenifyWhy don't you skip amplify and use greenify for the apps instead? Ever tried?
Greenify will quiet any app if properly configured on a rooted device. That said, the official Facebook is a steaming pile for numerous reasons. Lite alternatives exist which have proven satisfactory to most. Can also use tools like Hermit to improve the experience using the web interface. Your choice.Already using man. Facebook is greenified but not much effect. This crappy app doesn't work well in greenify
Clickbait is a first.I have to admit, the title sounded like click bait at a first glance but after carefully following which services and wakelocks to limit along side the Ultimate Battery Guide on XDA. It really does work.! I left my second phone (Samsung S5) at home before school with around 79% battery, 3G on and everything and came back (after 8 hours) to see the same amount.
Kudos to @Celestial Fury! for making such an awesome guide.
Protip: to anyone who uses this guide, it works super well alongside Greenify + PowerNap.
I think he meant like, how do you send a link with the specific post. I.e. if you click a link it will take you to this thread post 18.Clickbait is a first.However, take note that ADB BBS on non-rooted can also show 0% drain even though BBS records and shows a drop - but that's a bug.
@drbabusaha - click on reply for a particular post to "quote" it unless by share you mean something else.
Hover over the Post number: #3499. The balloon will say: Permalink to Post #3499. Click on it to open a new tab. Copy that URL and paste it in the Insert Link icon in your REPLY message editor.I think he meant like, how do you send a link with the specific post. I.e. if you click a link it will take you to this thread post 18.
Idk how to do that though haha.
There are some other issues too, but the main culprit isHello, can anyone check up my battery stats? I've got 1.8% drain during idle for the past 4 hours . Couldn't leave my phone idle longer as i need it for work
================
Kernel Wakelocks !!! wakeup_sources !!!
================
sensor_ind (): 3 h 32 m Cnt:(c/wc/ec)30/3/0 80.8%
There are some other issues too, but the main culprit is
I have not experienced this problem myself but check https://reddit.com/r/nexus6/comments/2ttg4d/****ing_sensor_ind_wakelock. You should basically either try to enable or disable your ambient display (depending on its current state) and see if there are any changes.
When it triggers it should appear in Amplify. There's also a search function in Amplify. Limit it and you'll likely have problems with WiFi connection.I cant seem to find the WifiConnectivity manager in Amply. Is there like something that i have to type in myself?
Sorry for the dumb question
Notification-related alarms/wakelocks have a red cloud icon in Post #2. You have an active network connection [see network section in your log] from your many active apps leading to a high CPU usage while idle.Hi guys,
please take a look at my BBS.
I have already optimized some alarms and wakelocks according to previous posts.
But i still have 28 alarms / h over night from android
Alarms: 33, Intent: *job.delay*
Alarms: 41, Intent: WriteBufferAlarm
Alarms: 16, Intent: DeviceIdleController.light
Alarms: 37, Intent: NETWORK_LINGER_COMPLETE.200
Alarms: 12, Intent: *job.deadline*
Alarms: 37, Intent: WificondScannerImplPno Monitor
and some high numbers from com.google.android.gms
Alarms: 17, Intent: com.google.android.gms.gcm.HEARTBEAT_ALARM
Alarms: 14, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR
Unfortunately i couldn't find any useful information by googleling those alarms.
Can i limit those alarms without having any issues like missing notifications?
What limit should i choose? 3600 seconds?
Do you see any other potential to optimize my battery drain?
Thanks for your help!
Notification-related alarms/wakelocks have a red cloud icon in Post #2. You have an active network connection [see network section in your log] from your many active apps leading to a high CPU usage while idle.
Seen this movie before. Older device runs fine on Android 6/7 then suffers high idle drain with Oreo with no obvious culprits exposed by BBS and similar tools (as is the case with in your dump). Likely kernel has not been optimized for Android 8.x ROMs and is failing to put one or more hardware components into a power efficient state. Roll back to whatever worked before and profit.Thanks for your feedback but how do i solve this issue?
I added another BBS file from last night with wifi turned off but i lost the same amount of battery over night.
According to my understanding there shouldn't be that much wakelocks and alarms.
On Marshmallow i had a battery drain of 1% in 8h so i don't get whats different now![]()
You can test it systematically by first establishing baselines as in Post #3.Thanks for your feedback but how do i solve this issue?
I added another BBS file from last night with wifi turned off but i lost the same amount of battery over night.
According to my understanding there shouldn't be that much wakelocks and alarms.
On Marshmallow i had a battery drain of 1% in 8h so i don't get whats different now![]()
Not exactly: this regex will restrict all ALARM_WAKEUP with six digits or more.You can also stop them by using
So for example, the regex ALARM_WAKEUP[0-9]{6,} will restrict all ALARM_WAKEUP with six digits