Resume hibernated apps - restore last state? - Greenify

first of all - amazing app!!
I have one question, maybe I got it completely wrong ...
If I hibernate an app, and restart it later again, e.g using the recent key, shouldn't the app state also be restored??
e.g. I use root explorer and navigate to a folder, then press the home key. When I get back to the application ( not using greenify) I will see the same folder that I was in before (if LMK did not kill my app of course).
But when the app was hibernated (greenifed), it always starts up "fresh"... Is this intended??
Galaxy s6, android 5.0.2 rooted

The app is stopped so is normal. Btw in Root Explorer is an option to restore your last working folder, check it if you want to go back to your folder.

MihaiSG said:
The app is stopped so is normal. Btw in Root Explorer is an option to restore your last working folder, check it if you want to go back to your folder.
Click to expand...
Click to collapse
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.

GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
That is how the app is designed. You are not supposed to Greenify every app especially those you use frequently. That will consume more battery. This is stated in the OP of the main thread by the Dev himself and repeated many times in many sub-threads.
Makes sense.

tnsmani said:
That is how the app is designed. You are not supposed to Greenify every app especially those you use frequently. That will consume more battery. This is stated in the OP of the main thread by the Dev himself and repeated many times in many sub-threads.
Makes sense.
Click to expand...
Click to collapse
Yes, makes sense.
Thank you for the clarification.

GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
I believe the closest equivalent of the IOS behavior that you are looking for is generated through Doze, a function implemented in Android phones with Marshmallows. For a more aggressive Doze behavior, you can use greenify. And if you don't have marshmallow on your phone, I believe there is a dedicated Doze app on the play store

Surfinette said:
I believe the closest equivalent of the IOS behavior that you are looking for is generated through Doze, a function implemented in Android phones with Marshmallows. For a more aggressive Doze behavior, you can use greenify. And if you don't have marshmallow on your phone, I believe there is a dedicated Doze app on the play store
Click to expand...
Click to collapse
Ok thank you. I assume the app you are taking about is shutApp... The doze app (same developer) just cuts off the network activity using a dead VPN connection. I will try shutApp on my device phone, but for now I am happy with greenify, it works great except for Chrome and YouTube... Thanks for your help..

GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
You may try the new experimental feature - "Shallow Hibernation" if your device is running Android 6.0 and rooted. It preserves the app running context even in hibernation.

oasisfeng said:
You may try the new experimental feature - "Shallow Hibernation" if your device is running Android 6.0 and rooted. It preserves the app running context even in hibernation.
Click to expand...
Click to collapse
I will give it a try, thanks!

Related

[Q] Mutiple Apps Opening On Their Own

When I open some Apps, 10 other Apps open along with it. Is rooting the phone the only way to have access to the means to stop this?
Thanks,
-Adam
Don't pay so much attention. In general, those applications don't use your cpu and battery. Android has its own task manager system.
Yeah dis is even happening to me,the reason is so simple like one app needs the other apps so they are even opening up.
Devil_Dude said:
Yeah dis is even happening to me,the reason is so simple like one app needs the other apps so they are even opening up.
Click to expand...
Click to collapse
what the appl you using which is opening others appl can u name the apps
if you kill apps, they will probably get restarted automatically and left in the background. If the apps are working correctly, this is not a problem, as a well coded app does not use CPU/battery when in the background.
Actually, I just quit using a task manager to kill tasks (I just let Android kill them as necessary) and I have no problems (phone is not slower, power drain is not higher).
Maybe the thing is that after you stop a task in a task manager it does not update immediately and you don't see the task being restarted, and when you go into the task manager after running some app just then you see the apps restarted.
Also, some apps are very generic (maps) and used by other apps, and some apps need to be running all the time (latitude, mail client, widgets, etc.) and killing them would make them not work properly (widgets no longer updating, not getting new emails, etc.).
My advice is to leave the apps running if you are not very sure of what you are doing, because the OS will eventually kill unnecessary apps, and until then they should not use any CPU or battery.
Only thing is to stay away from badly written apps, the ones that use too much CPU even when in the background or when phone is sleeping. You should probably wait for a night after installing a new app to see if you have higher drain. If so, just uninstall and search for an alternative.
shhbz said:
what the appl you using which is opening others appl can u name the apps
Click to expand...
Click to collapse
Like any Google app by searching is opening. Google search and by using voice search its opening voice search app and so on.
Sent from my LG-P500 using XDA App

How to greenify apps?

I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
scandiun said:
I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
Click to expand...
Click to collapse
Look elsewhere. Greenify doesn't "freeze" any app.
tnsmani said:
Look elsewhere. Greenify doesn't "freeze" any app.
Click to expand...
Click to collapse
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
scandiun said:
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
Click to expand...
Click to collapse
My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
tnsmani said:
My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
Click to expand...
Click to collapse
Yes Hibernation Manager and Greenify only work when screen is off. That's enough for me, but do you know if any app that does it also when the screen is on? (App always hibernating unless on foreground)

Does Greenify really work ?

On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
mermaidkiller said:
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
Click to expand...
Click to collapse
Of course it does. The size/activity in this forum plus frequent mentions in respected publications over many years should offer some clues to its integrity. Whether it is working on your device is a different matter.
Greenify does best on rooted devices as unharnessed ROMs can both undo actions and/or misrepresent status. It's quite possible an app placed in hibernation was later woken via internal trigger that Greenify can not suppress on an unrooted device. In the case of Opera (my preferred browser) there is regular syncing of tabs and downloading of *cough* 'news' if you have those features enabled.
I also question info coming out of the "Android Assistant" app. On my device it claimed all apps had zero CPU...including itself. Also did not display system partitions correctly nor properly detect the sensor suite. Granted I only spent a few minutes poking around. Maybe some switches needed to be thrown.
Finally, you probably don't need Greenify on Oreo as Doze does a find job with power management.
planetera said:
Don't I really need Greenify on oreo? Is Doze on Oreo really that good? Can you confirm please? I've been always using Greenify but if I don't need it on Oreo, I'll remove it
Click to expand...
Click to collapse
Well don't take my word for it. Simply remove all apps from Greenify's hibernation list (hopefully there are not many there), observe device behavior over the next few days then make your own decision.
planetera said:
Well, thanks for information. Just made a quick research and everyone says Greenify is trash on Oreo. So I just uninstalled it. Thanks for heads up. Glad I've seen your comment
Click to expand...
Click to collapse
Trash? Err-no. I have it installed on every one of my devices for valid reasons. Needed for generic power management on Doze capable ROMs? Probably not (and as such serving no purpose). Enjoy your device.
planetera said:
ok, but, when Greenify hibernates an app, you don't get notificaton froms this app, but when Android itself hibernates the app, you still get notifications, how does these two compare?
Click to expand...
Click to collapse
It varies by app, developer approach and user settings. Many apps will experience delayed notifications with Doze while other punch right through. Greenify can be configured to permit notifications but only if the app utilizes GCM (Firebase). Aggressive doze, light hibernation, Xposed framework availability and several other variables contribute to notification behavior. If your head is spinning it should! End users should not need to know the contents of the underwear drawer. Best practice is to simply let Android do its thing without 3rd party tools unless one understands their behavior and application. At one time such tools were needed to achieve acceptable app/device performance and battery life. Not so today. Is such a simplistic solution 'optimal' form an enthusiasts point-of-view? Probably not. It is acceptable/reasonable from an end-user perspective? In most cases 'yes' yielding a good balance of performance and battery life with minimal interaction for those who simply want to enjoy their device vs. manage it. Good luck with whatever direction you choose.
Agree one hundred percent!
Greenify on Oreo is an appendage that is best left out in my opinion, since for most, Oreo itself manages the drain admirably. Though I have it installed, it is more by way of habit than necessity. I have experienced Oreo without Greenify and have no complaints.
Greenify is STILL works.
But its benefit on recent Android versions is not as prominent as on earlier versions.
Coz we already have Doze starting from Marshmallow.
It works for me. I have a samsung tab a 9.7 sm-t550 with an aicp 8.1 rom (lineageos based). Therefore it doesn't have the built-in samsung app device maintenance. I've also discovered a little trick to using greenify that I want to share. I use greenify with another app called shutapp. Shutapp is an app that helps you force stop apps running in the background. Except I don't do that. I use it solely for the purpose of having an accurate number of apps running in the background. Then I open the app to see which ones are running. Next I open greenify and hibernate them. I use this method, because I found that when you force stop the apps they will open back up again. Also, I use the widget from shutapp and not the floating bubble which requires extra permissions granted. The widget does the same thing without the extra permissions. This method I discovered has improved my ram and battery life drastically. I can tell because I use status bar mini pro to monitor my ram speed constantly. And finally I do have Xposed with the donation package of greenify, didn't want to leave that out. Not sure if it makes a difference or not, but wanted to be accurate. That's it, hope that works for somebody else, take care.
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
tnsmani said:
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
Click to expand...
Click to collapse
Greenify works just fine on recent Android builds. It is a tool that can be very beneficial when properly used to produce a specific outcome. That said, it is rarely needed on Android 6+ as doze handles most of the heavy lifting. Enjoy using your device vs trying to fix problems you haven't identified.

apps start afresh instead of resuming from where they hibernated

I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
devsk said:
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
Click to expand...
Click to collapse
Did you try the shallow hibernation or normal hibernation?
devsk said:
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
Click to expand...
Click to collapse
Yes, Greenify is working on many (tens of) thousands of devices. Likely YOUR device, rom or kernel is aggressively clearing memory due to limited resources. What are you using?
tnsmani said:
Did you try the shallow hibernation or normal hibernation?
Click to expand...
Click to collapse
I tried both but app restarts instead of resuming.
Yes, Greenify is working on many (tens of) thousands of devices.
Click to expand...
Click to collapse
What's your definition of working? It runs and does something or works as in if an app is hibernated and started, it resumes. If its the latter, its clearly not working...
devsk said:
I tried both but app restarts instead of resuming.
What's your definition of working? It runs and does something or works as in if an app is hibernated and started, it resumes. If its the latter, its clearly not working...
Click to expand...
Click to collapse
Not going to engage on this level. Greenify stands on its own merrits.
If not happy with the results nor willing to share device/rom/config info that might help with 'problem' determination then it probably ain't the right tool.
Davey126 said:
Not going to engage on this level. Greenify stands on its own merrits.
If not happy with the results nor willing to share device/rom/config info that might help with 'problem' determination then it probably ain't the right tool.
Click to expand...
Click to collapse
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
devsk said:
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
Click to expand...
Click to collapse
Just for interest, I'd downloaded and installed Andoku. Greenified Andoku. Played a few minutes and stopped within the game. Closed Andoku. Ensured Andoku was hibernated. Opened Andoku and was able to resume my game exactly at the point where I'd closed Andoku.
Just for completeness although most likely unimportant in this matter: Andoku had no internet access granted in AFWall+.
Personal conclusion: Greenify (currently on v4.6.3) works exactly and perfectly as advertised!
Personal remark: I concur with @Davey126. Unless you provide sufficient information about device, ROM, kernel and "configuration" (e.g. Magisk, Xposed, XprivacyLua, tools that restrict permissions, services, broadcast receiver etc.) most likely nobody is able to support you.
devsk said:
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
Click to expand...
Click to collapse
Android hibernation is not the same as Windows hibernation. Resumability is not assured - especially on a resource constrained or highly 'tuned' ROM. You should probably read up on how it works and the primary objective of Greenify which is to suspend unwanted background activity. In that respect it shares many characteristics with doze.
Oswald Boelcke said:
Just for interest, I'd downloaded and installed Andoku. Greenified Andoku. Played a few minutes and stopped within the game. Closed Andoku. Ensured Andoku was hibernated. Opened Andoku and was able to resume my game exactly at the point where I'd closed Andoku.
Click to expand...
Click to collapse
Did you use the pause/resume feature of the Andoku game or did you just click the game to start it again, and it resumed where you left off? Typically, if you resume using the game's feature, you have to click through 3 times to resume your game. If the app is resuming from where it left off, its 1 click just to start the game.
If you resumed the app as if you switched to it using app switcher, then something definitely is broken on my end.
Just for completeness although most likely unimportant in this matter: Andoku had no internet access granted in AFWall+.
Click to expand...
Click to collapse
I do the same.
Oswald Boelcke said:
Unless you provide sufficient information about device, ROM, kernel and "configuration" (e.g. Magisk, Xposed, XprivacyLua, tools that restrict permissions, services, broadcast receiver etc.) most likely nobody is able to support you.
Click to expand...
Click to collapse
I am stock Pixel 3 XL with Magisk 18.1 root. Nothing else. I have given all perms needed by greenify.
Android hibernation is not the same as Windows hibernation.
Click to expand...
Click to collapse
I think this is where likely the disconnect is. I started using greenify several years ago (I have been here on these forums for a while, I keep that dated forum reference in my signature for remembering how far android and this community has come). If I recall correctly, I used to be able to resume apps, just by clicking or switching to them. Now, I notice a different behaviour: the app restarts from scratch. That's all. Obviously, I preferred the app to not start but resume like I was just switching to it.
I don't know if this is relevant in this case, but doesn't Greenify in non-root mode just force stop apps? I believe this to be the case because I can see it happening; i.e., when hibernation is triggered, for each app hibernated the app info screen briefly appears and the warning dialog about force stopping an app flashes on screen momentarily.
olliebean said:
I don't know if this is relevant in this case, but doesn't Greenify in non-root mode just force stop apps? I believe this to be the case because I can see it happening; i.e., when hibernation is triggered, for each app hibernated the app info screen briefly appears and the warning dialog about force stopping an app flashes on screen momentarily.
Click to expand...
Click to collapse
Correct. The equivalent happens on rooted devices just in a more efficient and largely transparent manner. If the ROM later opts to recover some/all of the resources consumed by the 'hibernated' app standard Android memory mgmt rules apply. In most cases that means only critical pointers are retained which may or may not contain sufficient information to resume from the point the app was in when last in the foreground.
Davey126 said:
Correct. The equivalent happens on rooted devices just in a more efficient and largely transparent manner. If the ROM later opts to recover some/all of the resources consumed by the 'hibernated' app standard Android memory mgmt rules apply. In most cases that means only critical pointers are retained which may or may not contain sufficient information to resume from the point the app was in when last in the foreground.
Click to expand...
Click to collapse
But AIUI, force stopping an app is essentially killing the app process. So for the app to start afresh when next launched, rather than resuming from where it was left, would be expected behaviour.
Is Greenifying an app functionally better than disabling Background Activity from the app's Battery Usage page (a new setting in Oreo)? IWHT the latter achieves the same result but without killing the app.
I am running root mode. So, let's not talk about non-root mode.
If a hibernated app is going to restart from scratch instead of resume, I might as well just clear all apps (that I fed to Greenify) on screen off with 5 min delay using tasker/automate. Why bother with anything else?
The point of Greenify was to be able to resume the app after hibernate as if you just switched to it. This used to work, I have tested it in the past. Not anymore though.
olliebean said:
But AIUI, force stopping an app is essentially killing the app process. So for the app to start afresh when next launched, rather than resuming from where it was left, would be expected behaviour.
Is Greenifying an app functionally better than disabling Background Activity from the app's Battery Usage page (a new setting in Oreo)? IWHT the latter achieves the same result but without killing the app.
Click to expand...
Click to collapse
Well, no ... but this is not the place for that discussion. Not going to get into Android 101 or validating speculation around various actions.
---------- Post added at 05:18 PM ---------- Previous post was at 04:52 PM ----------
devsk said:
I am running root mode. So, let's not talk about non-root mode.
If a hibernated app is going to restart from scratch instead of resume, I might as well just clear all apps (that I fed to Greenify) on screen off with 5 min delay using tasker/automate. Why bother with anything else?
The point of Greenify was to be able to resume the app after hibernate as if you just switched to it. This used to work, I have tested it in the past. Not anymore though.
Click to expand...
Click to collapse
Sorry it is not working with your device/kernel/ROM/root solution. Could be an adverse interaction with the doze mechanisms in Android 9, aggressive memory management settings (eg: VM, LMK), resource mapping of the app(s) you are trying to hibernate, etc. I have not see a lot of feedback from Pie users as doze generally addresses rogue background activity and corresponding power drain. So the behavior may be different on that platform. I use Greenify on a variety of devices for other reasons for which it continues to work well. Just another tool in shop; appropriate selection is the key to success. Good luck.

Can't seem to run multiple apps in the background (not a dual window issue)

So when I have multiple apps open, like for example. Youtube, Notes and Firefox then every time I switch app, the apps left in the background refreshes and lose whatever progress I'm doing in them. It's like they have trouble running in the background. didn't have this problem back in LGV20 so this is odd. I made sure to exclude these apps in the battery optimization and it does not seem to help
noddledizzy said:
So when I have multiple apps open, like for example. Youtube, Notes and Firefox then every time I switch app, the apps left in the background refreshes and lose whatever progress I'm doing in them. It's like they have trouble running in the background. didn't have this problem back in LGV20 so this is odd. I made sure to exclude these apps in the battery optimization and it does not seem to help
Click to expand...
Click to collapse
Are you on stock firmware or custom ROM? What version of either?
Do you have some task killer app installed?
ChazzMatt said:
Are you on stock firmware or custom ROM? What version of either?
Do you have some task killer app installed?
Click to expand...
Click to collapse
I have tested this on both stock oreo(US998) and AOSP PIE rom(H918) and the problem persists on both.
No, I do not have any task killers of some sort.
noddledizzy said:
I have tested this on both stock oreo(US998) and AOSP PIE rom(H918) and the problem persists on both.
No, I do not have any task killers of some sort.
Click to expand...
Click to collapse
No cleaners, optimizers, etc?
I'm just asking because I had installed paid CC cleaner app upon a good review on technical website. But after running for a few days I noticed it was killing tasks in the background, like Waze when I would look at an incoming email. Waze was running just fine until it temporarily became a background task. Then it got killed, even though I was still using it!
Also my phone started running hot and had become sluggish in spite of the fact this app was supposed to be "optimizing" my phone. So I uninstalled it.
I'm just curious if there's some app you've have for a while that you forgotten about, that is doing something like that... That would also explain why you see it on stock as well as custom ROMs, because it would be an app you installed yourself.
Least likely is you have the nuclear setting in Developer Options to limit how many apps can run at one time. Most people don't even know about that.
Otherwise I have no other answers.
Thanks for the insight. But the thing is, 90% of apps I have in both my US998 and H918 are open-source from F-droid. None of them really messes up with my battery. The only proprietary apps I have are first party apps from Google like Youtube, Google maps and Play services and some stock LG apps. Yeah, I never touch the app background limit in the developer options. Anyway, I appreciate you trying to help me and you already helped me a lot before.

Categories

Resources