Hi,
First of all, this is a task killer question, and I know it has been preached again and again that task killers should not be used, which I do agree but need more clarification. I've googled and still can't find the answer to my question.
Current Phone : Huawei P9 Lite
Current Protected Apps Setting : Nova Launcher, Whatsapp, Inbox, Amplify, Greenify
So Huawei phones has this Phone Manager which is essentially a Task Killer and Memory Cleanup Utility to me.
To ensure that an app doesn't got killed after screen off, I need to add that app to be "Protected"
We all know that killing an app and have it restart/reload when being opened is bad(extra battery drain)
Hence my question:
Does killing an app, for example Chrome or Facebook, stops all it's background process after screen off? and thus stops battery use from that app? Previously before using Greenify, I have had incidences whereby Chrome kept my phone awake for the night if I didn't kill it.
Does this incident happens to you? As in, you trust android to manage memory, but having those app behind in background would simply just gives it a chance to run and keep your phone awake, such as Google Now, Maps(This! is notorious.....)
Looking to have 0.5% battery drain overnight if that is possible..
Hey all,
I have an L04 running B360 Nougat with EMUI 5. I updated using Charles method. I noticed the Facebook drain issue pretty much right away after upgrading. So I did a factory reset afterwards, which helped at first. But later in the day, the app started draining again...
With the Facebook app installed, I notice ridiculous background CPU usage on Facebook, using about 20% of battery with over 1 hour of background CPU usage in one day. I tried blacklisting Facebook so it gets closed in the background after screen is locked, but I notice the process just starts itself again without me even opening the app....
I have notifications off on Facebook and a bunch of other things, but it still drained like crazy. My OP3 does not have this issue despite running also on Nougat. I have no idea why it drains so much, when it should be doing absolutely nothing in the background. Seems to keep the phone awake too.
Has anyone else had this issue? Currently the app is uninstalled so that I can get decent battery life.
I noticed increased battery drain in general with Nougat/B360, not sure exactly why. I recommend installing "Swipe for Facebook" in the meantime, as it isn't as battery intensive and is a great replacement for the normal FB app.
The Facebook app had a bug that had an issue with battery drain. Did you installed the latest version?
Try to download the latest Facebook and Messanger app from apkmirror and try again.
Thanks for the quick reply guys. I am going to check out swype in the meantime.
Potato997 said:
The Facebook app had a bug that had an issue with battery drain. Did you installed the latest version?
Try to download the latest Facebook and Messanger app from apkmirror and try again.
Click to expand...
Click to collapse
Yes they are the newest version that's on Google play store. Messenger itself seems fine, it's Facebook itself that's killing me...
aeozyalcin said:
Thanks for the quick reply guys. I am going to check out swype in the meantime.
Yes they are the newest version that's on Google play store. Messenger itself seems fine, it's Facebook itself that's killing me...
Click to expand...
Click to collapse
I also recommend FB Messenger Lite if you don't really need the calling features of the regular Messenger app; I'm not a fan of all the Snapchat-like features that they've been adding to the main application lately.
I confirm that the Facebook app, no matter what version you have, is a huge battery drainer. It doesn't respect the EMUI settings or anything. It drained the phone over night even on flight mode.
After uninstalling it, the battery performance on EMUI 5 is very good.
If you're on L09C432 please refer to this thread to get the system fix released by Honor/Huawei
morpheus302 said:
If you're on L09C432 please refer to this thread to get the system fix released by Honor/Huawei
Click to expand...
Click to collapse
Yeah I saw that on the forum yesterday. But I'm thinking I can't put that update on my L04. Swipe for Facebook seems to be pretty awesome, I have been using that. I also installed the regular Facebook app again to try once more, and it has already consumed 3 times the energy Swipe has consumed, and I used Swipe mostly..
aeozyalcin said:
Seems to keep the phone awake too.
Click to expand...
Click to collapse
If you go the application info and click on battery, you can find an option to disable the system wakeup (refer to the screenshot).
Overall, I did notice that the battery life decreased after the nougat update. I personally have problems with Instagram, I constantly have the power-intensive prompt notification, and just like you said, the lockscreen-app-kill doesn't work like it's suppposed to.
takichiman said:
If you go the application info and click on battery, you can find an option to disable the system wakeup (refer to the screenshot).
Overall, I did notice that the battery life decreased after the nougat update. I personally have problems with Instagram, I constantly have the power-intensive prompt notification, and just like you said, the lockscreen-app-kill doesn't work like it's suppposed to.
Click to expand...
Click to collapse
Huh, interesting... I only have close after screen lock and power intensive prompt as the two options on that screen.... No option for system awake. Are you on L04 on EMUI5?
aeozyalcin said:
Huh, interesting... I only have close after screen lock and power intensive prompt as the two options on that screen.... No option for system awake. Are you on L04 on EMUI5?
Click to expand...
Click to collapse
Yes, I have L04 on Nougat/EMUI5.
This option is not available for all apps, but I'm sure I've had it for Facebook with EMUI4.1
aeozyalcin said:
Hey all,
I have an L04 running B360 Nougat with EMUI 5. I updated using Charles method. I noticed the Facebook drain issue pretty much right away after upgrading. So I did a factory reset afterwards, which helped at first. But later in the day, the app started draining again...
With the Facebook app installed, I notice ridiculous background CPU usage on Facebook, using about 20% of battery with over 1 hour of background CPU usage in one day. I tried blacklisting Facebook so it gets closed in the background after screen is locked, but I notice the process just starts itself again without me even opening the app....
I have notifications off on Facebook and a bunch of other things, but it still drained like crazy. My OP3 does not have this issue despite running also on Nougat. I have no idea why it drains so much, when it should be doing absolutely nothing in the background. Seems to keep the phone awake too.
Has anyone else had this issue? Currently the app is uninstalled so that I can get decent battery life.
Click to expand...
Click to collapse
Its not problem of new emui 5 , Mine is running old version emui 4.1 and still drain battery for better battery performance use facebook via google might be way better then apps through playstore.
I use Facebook Lite and Messenger Lite, you can grab either from APKMirror.
So system wakeup toggle now magically shows up for Facebook. I switched it off, and it has been good on power now. However the funny thing is, when I go to "Apps that use power in background" screen, Facebook is listed there as an application that frequently wakes up the device. It's bizarre.
I'm monitoring power consumption of Facebook closely to see how it behaves.
Facebook is one of the apps that the company behind it has the mentality of "I'm going to run on the background of your phone no matter what". It's absurd. Three apps on my phone, Facebook, Messenger and Instagram (but surprisingly not WhatsApp) wake up at the same time. If one of them is allowed to wake up, wakes up the rest - it's insane. I've tried everything possible on a non-rooted, non-xposed phone. It just starts on the background, and you can see on Greenify wakeup tracker that the trio (fb, messenger, instagram) starts exactly at the same time.
Of course, this is not the first time they are being user-hostile: https://www.macstories.net/linked/the-background-data-and-battery-usage-of-facebooks-ios-app/
The only thing I found that kind-of mitigates the problem is using AppOps by Quixingchen ( https://play.google.com/store/apps/details?id=rikka.appops ) which, in EMUI 5, allows to remove the permission to run in the background from certain apps. It doesn't require root, but requires to do some tricks with adb and usb debugging. Removing it on the trio of appls forces them to use the GCM push method, which is much battery friendly but may delay some notifications - that is ok for me.
I hope this post helps people with battery drain issues - me personally don't have any issues with EMUI 4.1/5 and facebook, but I was already aggressively trying to make fb stop running in the background, so I don't know what would happen if I didn't.
I have disabled background activity on my pixel 2 running 8.1 for some apps, namely facebook and despite that it always shows that its working for some time "while in background". Should it still be working like this or is it a bug in reporting?
Of123 said:
I have disabled background activity on my pixel 2 running 8.1 for some apps, namely facebook and despite that it always shows that its working for some time "while in background". Should it still be working like this or is it a bug in reporting?
Click to expand...
Click to collapse
facebook will just about always be running in the background, this is normal. If you want it to not run, you can use a tool like greenify if you are rooted and hibernate the app when you're not using it. Keep in mind that doing so will interfere with things like facebook notifications.
Restricting background activity prevents some things from running in the background -- if an app is using GCM, it will still have some background activity no matter what.
On stock and android 11 unrooted phone.
Coming from rooted android 10 the battery drain is way higher on android 11
Done all the usual stuff to stop drain and debloated few things but what else can anyone recommend for battery saving
Thanks
Things that help me are:
DEBLOAT
Debloat Oneplus account
Debloat Oneplus cloud
Debloat Oneplus wireless emergency alerts.
Debloat Google Pictures
Debloat Google Movies
Debloat Google Music
Debloat Google Gmail
SETTINGS
WIFI Scanning settings: Turn OFF
Bluethooth/Printing : Turn OFF
NFC: OFF, never use it.
Adaptive brightness : OFF ( Always adjusting consumes battery)
Use a dark Wallpaper & Screen time out is 30s
Notification, only allow the apps you want. Or switch off, every notification wakes the phone from Doze mode.
Location: OFF
Battery : Optimise every user app, including Google Play store & Google Play Services (Battery HOGS)
Accounts: Switch Sync data off
Hope this helps you.
@soka said:
Things that help me are:
DEBLOAT
Debloat Oneplus account
Debloat Oneplus cloud
Debloat Oneplus wireless emergency alerts.
Debloat Google Pictures
Debloat Google Movies
Debloat Google Music
Debloat Google Gmail
SETTINGS
WIFI Scanning settings: Turn OFF
Bluethooth/Printing : Turn OFF
NFC: OFF, never use it.
Adaptive brightness : OFF ( Always adjusting consumes battery)
Use a dark Wallpaper & Screen time out is 30s
Notification, only allow the apps you want. Or switch off, every notification wakes the phone from Doze mode.
Location: OFF
Battery : Optimise every user app, including Google Play store & Google Play Services (Battery HOGS)
Accounts: Switch Sync data off
Hope this helps you.
Click to expand...
Click to collapse
Thanks for the above
Optimise the battery on most apps and not getting some notifications ie Gmail so take it this is one of the side affects
Yep, stuff that runs in the background always eat battery. Especially Google apps.
@soka said:
Yep, stuff that runs in the background always eat battery. Especially Google apps.
Click to expand...
Click to collapse
Goggle play Services, Playstore, Google backup Transport and Framework are prime offenders.
The former two I kept disabled unless I need them. The latter two are package blocked.
Sync is turned off. Gmaps is kept firewall blocked unless needed otherwise it constantly is running in the background.
@soka said:
funkyirishman said:
Thanks for the above
Optimise the battery on most apps and not getting some notifications ie Gmail so take it this is one of the side affects
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Optimization can eat battery and cause erratic behavior. Developer options>Standby apps, all buckets should show as active. Otherwise power management is active and it will cause trouble.
Dependencies... disabling some apps can cause seemingly unpredictable consequences and higher battery consumption. Goggle play Services has lots of dependencies but killing it saves battery. Turning off location helps too.
Turn off all carrier, manufacturer and app feedback.
Disable OTA updates; only update if proven to be worthwhile. Most updates harm the usability and provide little improvement. If the phone is running fast, stable and fulfilling its mission leave it be. Most carrier Android phones need to be optimized or they will run like pigs. Updates generally just complicate the optimization process.
Each Android and user are unique requiring different solutions. Play with it.
With Google you're not the customer, you're the product... the less Gookill, the better.
blackhawk said:
Goggle play Services, Playstore, Google backup Transport and Framework are prime offenders.
The former two I kept disabled unless I need them. The latter two are package blocked.
Sync is turned off. Gmaps is kept firewall blocked unless needed otherwise it constantly is running in the background.
Optimization can eat battery and cause erratic behavior. Developer options>Standby apps, all buckets should show as active. Otherwise power management is active and it will cause trouble.
Click to expand...
Click to collapse
Was looking at this but what do you mean by 'all buckets'?
Some of the apps are on WORKIng_SET /ACTIVE or RARE and a few on FREQUENT
Anything to do on these to save battery
Also I have Dont Keep Activities ticked but even when I close the apps its still running and press clear all
funkyirishman said:
Was looking at this but what do you mean by 'all buckets'?
Some of the apps are on WORKIng_SET /ACTIVE or RARE and a few on FREQUENT*
Anything to do on these to save battery
Also I have Dont Keep Activities ticked but even when I close the apps its still running and press clear all
Click to expand...
Click to collapse
*These are the buckets. Google terminology not mine. More Google bloatware.
If you can't change their run state there then power management is disable... as is best.
Simple close apps when done with them.
If they continue to cause trouble try limiting background battery and/or data usage.
Ditch the really bad actors if can't get them to behave.
Power management apps will cause nothing but trouble and eat battery. Android manages its self well without this junk with well written apps.
Hi
I'm on a stock Samsung Note 10+ 5G. I normally disable unused apps with Tasker and only load them as I need them, my primary aim to reduce battery drain. I wanted to see how good Android 12 was at controlling apps battery usage so I've enable all my apps, and put them into the following states:
Mobile Data - I've turned "Allow background data usage" to OFF
Under the battery section, each app is Restricted
I've removed from "Optimise battery usage" section, so they are being battery optimised
Under Developer Options, Standby Apps, I have put each app into Restricted mode
Most apps are behaving fine, but I'm getting quite a few apps over time using battery. When I check under GSAM, all of them have the same wakelock which is Google_C2DM. The apps typically are not active (i.e. when I check in the app manager, "Force Stop" is greyed out) and they are listed as "Manually Disabled". I've tried killing the apps, clearing cache on the apps and the phone, restarting etc but cannot get them to entirely stop battery usage. Is there a solution for this and any idea why its the same Google_C2DM wakelock?
thanks
I myself am investigating YouTube app battery usage and that component is also listed at the top in GSAM.