Related
HI ALL,
I will root my device , but I want to know how to increase its performance and speed and reduce RAM usage?
and what is the best browser for Android for fast browsing and low memory usage?
Most of the speed increasing and RAM decreasing can be done without root. Replacing Touchwiz with Apex or Nova Launcher is the first step that makes the most difference. Disable most of the bloatware and turn down animations in developer options.
This post probably belongs in the Q&A section, not the software one.
Reduction in RAM usage doesn't necessarily equate to performance boost. Android memory management does a good job of keeping things running smoothly so the goal of debloating should not be to free up RAM. To maximize performance with regards to memory usage with Android what you'll want to do is debloat your device to the point that applications that you'll never use are no longer loading into memory automatically (either as active applications or cached) which will allow other frequently used applications a chance to load into RAM/cache for quick response times. Running memory management software is also counter productive as it will battle against Android's own memory management and kill background applications that you may want cached for quicker response when needed.
Personally I WANT RAM to fill up because if I'm jumping from application to application I don't want to wait for things to load from storage into RAM. I also refrain from cache cleaning frequently because I have a particular routine when I use my device (frequenting particular websites and using particular applications daily) so clearing cache frequently will only force my device to have to re-cache things unnecessarily.
Getting down to the nitty gritty of how to debloat, the approach I took for my device is to work with a few applications; SystemPanelLite Task Manager, Greenify, Boot Manager and Titanium Backup. I would clean boot my device and let it sit for a while (several minutes) to cache applications as it saw fit. I'd then pop into the system panel lite application and look at what was loaded into both active processes and cached. I'd evaluate each entry to determine for myself whether or not I wanted that application to load automatically or not OR NEVER. If the answer was never then I'd use Titanium Backup to freeze the application (of course for each app I'd do my research to see if it was serving an important function). If the answer was that I needed the application but not all of the time then I'd look into Greenifying it and also considered disabling it from starting at boot using boot manager.
I'd do the above iteratively until all I saw in RAM or cached were applications and services that I felt were important. Never during this process did I care how low memory usage was since the goal is to preload as much of the important stuff as possible.
In the end I ended up freezing a ton of Samsung apps, especially after uninstalling applications that relied on their own app store like Hancom.
Of course a quicker way to reduce bloat is to go to a ROM that someone else has debloated and start there as a base. I began my own debloating process early last year though so starting again on a ROM even if it already is debloated to a certain extent doesn't seem worth it for me at this time (but if a lollipop update rolls out and a ROM developer updates to that then I'll surely try it).
Sent from my SM-P900 using Tapatalk
ShadowLea said:
Most of the speed increasing and RAM decreasing can be done without root. Replacing Touchwiz with Apex or Nova Launcher is the first step that makes the most difference. Disable most of the bloatware and turn down animations in developer options.
Click to expand...
Click to collapse
thanks a lot man , I used nove launcher and its v nice , I guess need to root so I can freeze more apps as not all can be disabled using offical rom
muzzy996 said:
This post probably belongs in the Q&A section, not the software one.
Reduction in RAM usage doesn't necessarily equate to performance boost. Android memory management does a good job of keeping things running smoothly so the goal of debloating should not be to free up RAM. To maximize performance with regards to memory usage with Android what you'll want to do is debloat your device to the point that applications that you'll never use are no longer loading into memory automatically (either as active applications or cached) which will allow other frequently used applications a chance to load into RAM/cache for quick response times. Running memory management software is also counter productive as it will battle against Android's own memory management and kill background applications that you may want cached for quicker response when needed.
Personally I WANT RAM to fill up because if I'm jumping from application to application I don't want to wait for things to load from storage into RAM. I also refrain from cache cleaning frequently because I have a particular routine when I use my device (frequenting particular websites and using particular applications daily) so clearing cache frequently will only force my device to have to re-cache things unnecessarily.
Getting down to the nitty gritty of how to debloat, the approach I took for my device is to work with a few applications; SystemPanelLite Task Manager, Greenify, Boot Manager and Titanium Backup. I would clean boot my device and let it sit for a while (several minutes) to cache applications as it saw fit. I'd then pop into the system panel lite application and look at what was loaded into both active processes and cached. I'd evaluate each entry to determine for myself whether or not I wanted that application to load automatically or not OR NEVER. If the answer was never then I'd use Titanium Backup to freeze the application (of course for each app I'd do my research to see if it was serving an important function). If the answer was that I needed the application but not all of the time then I'd look into Greenifying it and also considered disabling it from starting at boot using boot manager.
I'd do the above iteratively until all I saw in RAM or cached were applications and services that I felt were important. Never during this process did I care how low memory usage was since the goal is to preload as much of the important stuff as possible.
In the end I ended up freezing a ton of Samsung apps, especially after uninstalling applications that relied on their own app store like Hancom.
Of course a quicker way to reduce bloat is to go to a ROM that someone else has debloated and start there as a base. I began my own debloating process early last year though so starting again on a ROM even if it already is debloated to a certain extent doesn't seem worth it for me at this time (but if a lollipop update rolls out and a ROM developer updates to that then I'll surely try it).
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Really helpfull man thanks a lot for all the information u shared, am ok with but guess will need to do more research for greenify cuz I didnt use it at all, secondly what office u used after uniinstalling hancom?
I'm currently using Microsoft's Word/Excel Preview apps and have an Office 365 account to enable editing. I've just started (1 month trial) so I haven't really gotten a lot of use out of the software yet.
I can't speak for anyone else but myself but my reason for dropping Hancom was twofold; 1) it did not support the review/commenting features that I needed in Word files and 2) it often required updates at inopportune times. My needs are quite specific, my tablet is a reference and note taking device for meetings and is never used for production type work. As such, I need the ability to take email attachments, open them for review and comment and then send the comments back out as email attachments. The limitations of Hancom when it comes to track changes were a deal breaker for me since I could not see the history of development of reports/documents.
Microsoft's mobile version of Word implements the best support of track changes/comments that I've found to date, so I'm forced to pay the premium of a 365 subscription on this device to get what I need.
muzzy996 said:
I'm currently using Microsoft's Word/Excel Preview apps and have an Office 365 account to enable editing. I've just started (1 month trial) so I haven't really gotten a lot of use out of the software yet.
I can't speak for anyone else but myself but my reason for dropping Hancom was twofold; 1) it did not support the review/commenting features that I needed in Word files and 2) it often required updates at inopportune times. My needs are quite specific, my tablet is a reference and note taking device for meetings and is never used for production type work. As such, I need the ability to take email attachments, open them for review and comment and then send the comments back out as email attachments. The limitations of Hancom when it comes to track changes were a deal breaker for me since I could not see the history of development of reports/documents.
Microsoft's mobile version of Word implements the best support of track changes/comments that I've found to date, so I'm forced to pay the premium of a 365 subscription on this device to get what I need.
Click to expand...
Click to collapse
thanks for reply and sorry for late , hoping the android 5 be great
Install cm12 lollipop ROM. Drastic improvement in browser performance and gaming. For example, Asphalt 8 is extremely slow on stock, even overclocked. On cm12 it runs perfectly with max graphics settings. Unfortunately you lose all the cool touchwiz features like multi window. For me, the performance improvement is enough that it's worth the lost features. I'm anxiously waiting for the official lollipop update.
I can live with the Nexus 5X' relative sluggishness when compared to the Nexus 5, but what really stops me from doing my work is the phone killing apps when I switch between them.
Example: I may be filling out a form on a website in Firefox for Android. I need to look up a word in the dictionary, so I switch over to the dictionary and look up the word. When I switch back to Firefox, the application has obviously been killed, as it reloads the page.
Example2: I'm listening to the Audio version of the Economist via the Economist app. The speaker mentions a certain placename and I open the Google Maps app in order too find where it is on the map. Suddenly the audio will stop playing - the app has been killed.
The above gets considerably worse when switching between more than two apps and is really hindering my work and productivity.
Now this almost never happened on the Nexus 5, which also only had 2 GB of RAM. So is it the power saving feature of the Nexus 5X kicking in? Is there a way to stop it from happening?
Marshmallow simply has very bad RAM management from what I've seen. I used to have the Nexus 5 too and as you said, multitasking was a very good experience on it (especially on Kitkat). Google's OS takes more of the phone's resources after each update (with no major new features or improvements). Marshmallow looks exactly the same as Lollipop, except for the tiny feature of apps permissions, and the Now on tap that I barely use (same for Android pay which I'm sure most of Nexus 5x owners won't even be able to use it outside the US). So I still don't understand why they had to jump so fast to a new version of Android while Lollipop still had a ****load of bugs that need fixing, they could've worked more on Lollipop to perfect it first then give us Marshmallow after 2 years maybe, we're not in a hurry.. I just hope they don't stop again at Marshmallow 6.1/6.2 or something and introduce Android N *sigh*
Sounds like you have more user installed apps with constantly running background services installed that the phone can comfortably handle with 2GB memory.
Check the memory stats in Settings - if the average over all the time options is 1.6GB or above used then your phone is going to struggle and cached apps are going to be getting cleared out when switching regularly. Look down the list particulary for apps running close to 100% of the time with a big RAM fingerprint. Also check running services in developer settings to get an idea of what is running a service all of the time.
Once you've identified the worst offenders make that difficult decision - is the apps utility worth it for the impact on performance. Consider reporting the memory use to the developer, particularly if it's much lower after a reboot and increases over time. Plenty of playstore apps ship with clear memory leak issues.
Other than that the other option is reasonably regular reboots to keep the system fresh and clear out any memory leaks.
thanks for the suggestion. Well here's the top 5:
Android operating system 524 MB
Wechat 156 MB
Firefox 117 MB
System UI 105 MB
Android system 99 MB
Clearly it's mostly the system using all resources. Firefox and Wechat, sure, I find them rather essential to my life, but together they don't even use as much as the OS.
Thing is, I can't remember this happening on the Nexus 5.
Sounds like you may have some apps using up a lot of your memory. I haven't been seeing any redraws with my apps, even 24+ hours of sitting in the background. The other day I was switching between gaming, streaming a live sporting even, and text messaging and the phone didn't drop a beat despite the game alone using 600MB of RAM.
Are those the average RAM or peak?
that's what shows up when I get the details of the RAM usage through settings
still this never happened on the Nexus 5, at least I can't remember
Yeah, I have a hard time believing it's the apps. I never had this issue come up in my Moto X 2013 (also 2 GB of RAM) using the same apps. We're seriously talking about one app open, switching to another app. No reason switching back to the first app should have everything reload.
Unless by "some apps," you mean that they have somehow not been optimized for Marshmallow in some way or other. But the apps simply running a process? A smartly-made OS (Lollipop, KitKat) will know "Hey, we have to kill something to free up RAM? Why don't we kill an app that hasn't been used in a while?" and a less-smartly-made OS (perhaps Marshmallow...?) will think "Hey, we have to kill something to free up RAM... why don't we kill the app the user just used?"
And there are two figures there - average and peak - which are those?
If there are the averages rather than peak then both Firefox and Wechat have got a problem.
---------- Post added at 06:42 AM ---------- Previous post was at 06:34 AM ----------
Marshmallow and Lollipop low RAM behaviour is pretty much identical and quite aggressive (the OS tries to preserve quite a chunk of free memory which is uses on the sly as a display buffer), KitKat was less aggressive.
I don't have any problem multitasking on my Nexus5x, but then again for the apps I've got when I check the memory tab I'm normally averaging 1.2-1.4GB used and 400-600MB average memory free so there is plenty of space for the OS to gracefully cache and uncache processes. If the phone is normally running at 1.5GB-1.6GB used and 200-300MB then the LMK is going to be kicking in frequently. It kicks in at around 250MB free on a Nexus5x.
It was the default setting, i.e. average. HM ok good to know. It's happening quite often when listening to the Economist too. Which is really bull****, it should treat it as audio playing. Why would Android kill your music.
I agree music players don't get the priority they should, although that particular 'bug' at least gives a clear symptom that lack of free RAM is an issue, if not the cause of the issue e.g. the OS, to many running services from user apps, or a particular user app with memory leak issues.
I came to the Nexus5x from a 1GB Moto G where it was almost impossible to keep background music running in combination with navigation after Lollipop without uninstalling pretty much everything else user installed and have got used to monitoring the RAM footprint and behaviour of apps as a result.
I've suffered the problem once since I've had the Nexus5x and that was due to the music player (Soundcloud) being a memory hog (120MB+) with it's background music player service coupled with a memory leak in the driving app I was testing at the time - Automate - it was peaking at 460MB use.
I'm not so precious about what is installed now but anything that wants to run a constant service either has to be tiny when running that service or absolutely fundamental to my use of the device.
I find this to be the worst problem .We want to kill our apps like we are use to.Switching between email and chrome is horrible especially when you have to start your application all-over again (submission request) Hopefully some XDA member will figure out how to solve this issue. For now I am testing DEVELOPER OPTIONS allow running
apps in background ? Anyone know what the default value is??
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
For me, Pie has actually been the smoothest compared to DP2 though DP5. There's a similar thread already here:
https://forum.xda-developers.com/pixel-2-xl/how-to/phone-sluggish-time-t3826729
harryfornasier said:
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
I've been getting stutters too. Occasionally it will just catch up and lag.
Haven't noticed any stuttering, just seems smooth for my usage...
harryfornasier said:
Has anyone else noticed some slowdowns on their pixel 2 XL? I had noticed slow animations on Android Oreo, I thought that maybe they would be fixed in the Pie update, but i am still noticing slow downs every so often.
Click to expand...
Click to collapse
There's micro stutters here and there but they're insignificant, I wouldn't call them slowdowns. Google really needs to up their ram for the next phone, the 4gb is starting to show it's limitations. Compared to the iPhone , the pixel doesn't seem very smooth with it's animations.
Actually my test shows after couple hours usage, the free RAM of Android P will drop around 600MB.
At this stage, you will start getting stutter or even no response from apps due to system try to release free RAM.
Right after boot up, Andrpod P will have around 1300MB free RAM, however after couple hours use (depends on how heavy you use your phone), the free RAM will go down to around 500MB and you will notice stutter if you launch some App which requires RAM.
You can verify this by launch Google Map, Google Photo and Street View together... or you could launch Camera App then take some panorama after a day's use. When fresh out of reboot, Pixel 2 XL has no trouble running those App together or handling multiple Panoramas but will run into stutter or even kill your Launcher for free RAM after couple hours useage...
I checked the OOM setting on "empty app" and it's defaulted at 318MB. I suggest raise it to 512MB to get better, longer stutter free operation (YMMV). With default OOM setting when I launch camera app, sometimes Nova Launcher will be killed for free RAM. However after modifing the empty app OOM limit to 512MB I seldom got any kill rampage when launching camera app.
For me, Android P is smooth when free RAM is over 900MB and you will definitely get into stutter when free RAM under 600MB. And it's unavoidable to went to this low ram stage after some use...
If you don't have above issue then lucky you, or you just didn't use your phone heavy enough as Google think you should... I don't want to argue how good Android can manage RAM since for me, kill my Launcher to make RAM for Camera is not a solution... Which happened to me quite often. I use Greenify to block most background app and do check what runs behind the scene quite regularly and kill those unwanted... Still, Android P will go to 600MB free RAM unless I modify OOM... (It's now aound 800MB when Nova Launcher is foreground App)
You can use this app for monitoring your free RAM.
https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicatorPro
lssong99 said:
Actually my test shows after couple hours usage, the free RAM of Android P will drop around 600MB.
At this stage, you will start getting stutter or even no response from apps due to system try to release free RAM.
Right after boot up, Andrpod P will have around 1300MB free RAM, however after couple hours use (depends on how heavy you use your phone), the free RAM will go down to around 500MB and you will notice stutter if you launch some App which requires RAM.
You can verify this by launch Google Map, Google Photo and Street View together... or you could launch Camera App then take some panorama after a day's use. When fresh out of reboot, Pixel 2 XL has no trouble running those App together or handling multiple Panoramas but will run into stutter or even kill your Launcher for free RAM after couple hours useage...
I checked the OOM setting on "empty app" and it's defaulted at 318MB. I suggest raise it to 512MB to get better, longer stutter free operation (YMMV). With default OOM setting when I launch camera app, sometimes Nova Launcher will be killed for free RAM. However after modifing the empty app OOM limit to 512MB I seldom got any kill rampage when launching camera app.
For me, Android P is smooth when free RAM is over 900MB and you will definitely get into stutter when free RAM under 600MB. And it's unavoidable to went to this low ram stage after some use...
If you don't have above issue then lucky you, or you just didn't use your phone heavy enough as Google think you should... I don't want to argue how good Android can manage RAM since for me, kill my Launcher to make RAM for Camera is not a solution... Which happened to me quite often. I use Greenify to block most background app and do check what runs behind the scene quite regularly and kill those unwanted... Still, Android P will go to 600MB free RAM unless I modify OOM... (It's now aound 800MB when Nova Launcher is foreground App)
You can use this app for monitoring your free RAM.
https://play.google.com/store/apps/details?id=info.kfsoft.android.MemoryIndicatorPro
Click to expand...
Click to collapse
This is only valid for people who buy the phones direct from Google and are able to root. For those from Verizon, you are out of luck, as there's no way to mess with memory settings.
This post is one reason in won't buy from Verizon.
Sent from my [device_name] using XDA-Developers Legacy app
Does any body have Advance experience of debloating Apps in A705F/Ds! Any one can point me to help !
Cause'
I do not much see any different in 1 week after Enable /Disable system/user apps in my device(8/128) gb operating with CCSWE App Manager Pro.
Still High 3gb Ram Usage per system vs apps in system start up!
I've just daily usage as (Fb, Messenger,What' App, Chrome, IDM, PUBg,Asphalt-9). Hell_No. !!
#No_Root #Smoothness_Ui_Experience #
RAM is there to be used! No need to free it, what's the point of it? The more apps are loaded in RAM, the faster they start. You have 6 GB of RAM, and only 3 GB in use, that is good
This is an interesting article about how memory works on Android: https://www.androidtipsandhacks.com...ndroid-and-why-you-shouldnt-most-of-the-time/
Bloatware or unwanted software can be removed, disabled or, when rooted, removed. But that has little to do with RAM. Disabling apps won't appear in app drawer, and removing them will free (a little) storage space.
Yeah,As a result of Disabling total 156/336 apps is almost same result as while it' not . Still got laggy in while scolling in Fb, Asphalt 9 . For 8gb Ram devices ' is it alittle way too much?Nothing Different !
CCSWE App manager is too strong but it can't help me out in no root state.
Nexus Axe said:
Yeah,As a result of Disabling total 156/336 apps is almost same result as while it' not . Still got laggy in while scolling in Fb, Asphalt 9 . For 8gb Ram devices ' is it alittle way too much?Nothing Different !
CCSWE App manager is too strong but it can't help me out in no root state.
Click to expand...
Click to collapse
Disable animations in developers settings.
Reduce motion in settings
Install greenify and use it in non root mode.
We have sd675 and it will have its limits.
As for Facebook lag, disable video autoplay and clear cache
I followed the Galaxy S10/9 guides on disabling via ADB to get rid of things like Bixby and other Samsung bloatware. Never had an issue with RAM but I like the idea of fewer icons in the app drawer, fewer notifications and fewer apps with potential to run in the background or eat up my data allowance for no reason. I have to say that this method along with using AdGuard DNS has pretty much done away with my usual desire to root.
Hi,
i guess Stock Pie has a Memory Leak and Garbage collector doesnt work.
I background restricted some apps in Settings but all of them still works on background. I cant see them on the Task Manager but i can see the Ram usage on AIDA64 app.
What i did:
- i set background restriction to these apps. (64 app restricted)
- i select app restrict behavior to Frequent. (for all of them)
- Task manager is empty.
- Cant see these leaked apps even on Android 9's built in Ram usage feature.
- i tryed kill apps when leave feature on the developer options. (These apps garbage still stays on the Ram)
- i even set background app limit 4 (Somehow developer options closed it self and everything i set reverted back to stock when i restart my phone)
But apps still eats the Ram from the background. I know because i can see Ram details on the AIDA64 app.
Phone starts with ~1600'ish mb available Ram. Available Ram decreases when i open-close these background restricted apps. (Hey! I am restricting apps because i dont want them working on the background. Like a Google Translator, Mi Remote, Hd Wallpapers app etc. i restricted all but these apps still works.) If my phone's Ram decrease everything starts slowing down. I am seeing it and i can feel it. After 5 or 10 minute later Ram usage jumps ~2000 mb. Some pieces of background restricted apps still stays in the Ram and i cant avoid from it on Stock Pie and these pieces slowing down my phone's performance. I am not using 26 apps!! Maybe 4 or 5 apps i am frequently using. I dont want unused apps garbage on Ram.
Huawei's EMUI has a built-in feature to avoid auto-start apps. Some custom roms has a Wake-Lock blocker. But i dont have anything on Stock Pie.
I just dont want these apps garbage on my phone's Ram. Because of these reasons i can clearly say Mi A2 Lite's Stock Pie rom has bad garbage collector. Dont know Xiaomi modified it or not. Probably thats why Stock Pie roms consumes more battery than Stock Oreo.
I am not the man who believe 'unused Ram is a waste'.
I just want most important system apps on the Ram and other almost everything shouldnt occupy a space on the Ram. This motto is the key reason of performance for Budget phones on my perspective.
Rom details:
Locked - Stock Android 9 - v10.16.0 (November 2019)
What i am asking is:
- Which Roms has built-in feature to avoid from this?
- Which Roms has a best Garbage collector?
- Which Rom fits to my requirements?
Thanks.
perfect_ said:
I background restricted some apps in Settings but all of them still works on background. I cant see them on the Task Manager but i can see the Ram usage on AIDA64 app.
Click to expand...
Click to collapse
You are fundamentally misunderstaning how task management works.
Restricting stops apps from using the CPU (and thus, the battery).
Android will leave unused apps in RAM for faster launching later. Some "AI" decides which of these to keep when more RAM is needed.
If it offends you to see these apps in a low-level task manager you can kill them. Heaps of task manager apps can do this automatically. You need something like greenify if you want them to stay dead.
a1291762 said:
You are fundamentally misunderstaning how task management works.
Restricting stops apps from using the CPU (and thus, the battery).
Android will leave unused apps in RAM for faster launching later. Some "AI" decides which of these to keep when more RAM is needed.
If it offends you to see these apps in a low-level task manager you can kill them. Heaps of task manager apps can do this automatically. You need something like greenify if you want them to stay dead.
Click to expand...
Click to collapse
I did not misunderstand anything. You didnt understand what i mean exactly.
Why Hd Backgrounds app or Mi Remote app should stay on the Ram even i dont use them? I am using them once a week or so. Thats why i dont need faster launch. Because i am not using them? Clear?Youre talking about app restart power consumption. Thats the point. I am not using them and i am not starting them in a single charge. Even if i want to restart these (as i said this thing happens once a week) apps restart power consumption consumes incomparably less energy than phone restart power consumption. I dont want to use my phone’s Ram with junks.
Do you prefer trashy Ram with bunch of junks? I dont prefer it. I cant clean these apps Ram garbage until restart my phone. The restart consumes a lot of energy and when my phones Ram become trashy i should restart all system to clean them.
Restart has benefits;
- More performance
- Clean Ram
- Better Battery life until Ram become trashy
What i am saying is why i cant use these benefits without restart. Think about all these power consumption when we restart our phone.
Its all about garbage collection and this thing doesnt work on Android Pie. I tryed Greenify gived it all what app wants still nothing changed. Ram still gets trashy and this causes; slowdowns, hiccups, more battery consumption,.. etc. Even my phone’s processor and battery doesnt like garbage on Ram.
I hope Huawei’s HarmonyOS will work better than Google’s trashy Ram management.
perfect_ said:
Why Hd Backgrounds app or Mi Remote app should stay on the Ram even i dont use them?
Click to expand...
Click to collapse
Because there is no benefit to removing them from your RAM.
perfect_ said:
I dont want to use my phone’s Ram with junks.
Click to expand...
Click to collapse
It's not junk. If you want tasks killed, get a task killer. If you want to prevent apps from starting, get a hibernation app.
perfect_ said:
I hope Huawei’s HarmonyOS will work better than Google’s trashy Ram management.
Click to expand...
Click to collapse
The Chinese OEMS are notorious for evicting programs from RAM and preventing them from running in the background, fundamentally breaking the android API contract in the process. If you think that's better then by all means, go use one of those ROMs.
I for one got the A2 Lite instead of the Redmi 6 Pro precisely to avoid MIUI and its task management policies.
a1291762 said:
Because there is no benefit to removing them from your RAM.
It's not junk. If you want tasks killed, get a task killer. If you want to prevent apps from starting, get a hibernation app.
The Chinese OEMS are notorious for evicting programs from RAM and preventing them from running in the background, fundamentally breaking the android API contract in the process. If you think that's better then by all means, go use one of those ROMs.
I for one got the A2 Lite instead of the Redmi 6 Pro precisely to avoid MIUI and its task management policies.
Click to expand...
Click to collapse
There is no point to talk with you. You dont even know what junk it is. Do not write to my threads!