Greetings,
Did anyone find the present issues with ONE UI 4.0 update in Galaxy S20 Ultra?
Well for me, After updating to android 12, my device has started to lag, mostly while switching windows, i mean apps and while pulling down the task bar for notifications and quick settings. Even there is a visible decrease in the overall performance.
Fixes that i have tried are, changing between different settings, such as toggling 120Hz back 60Hz and then back to 120Hz, changing color temprature to vivid then back to normal and then back to vivid plus switching off the blur in task bar by going into Accessibility settings > Visibility Enhancements > Reduce transparency and blur but nothing has worked so far. As a last resort to fix this problem, i have also reset it to factory, little improvement though but unsatisfactory.
What could be the possible issue and What could fix this?
You did a factory reset... 12 is a dud.
Not going to candy coat it as many have wanted to roll back from it. You can either do that, wait for a patch or play with it and try to find a work arounds. Try disabling all animations, etc in Developer options.
On my N10+'s one is 9, the other 10 and there they will stay.
Well, i think it is a good idea to play with it while gathering tips and tricks from other users.
I don't have these kinds of issues on OneUI 4.0, this update actually fixed most of the issues I had with this phone to be honest.
PROGamer_199 said:
I don't have these kinds of issues on OneUI 4.0, this update actually fixed most of the issues I had with this phone to be honest.
Click to expand...
Click to collapse
What is your security patch date?
I have the very same issues after updating my S20 5G to One UI 4.0 Android 12. Tried everything without improvement. Rebooting te phone helps a bit for at most 24 hours, after which the phone is too laggy and stuttering again to work with...
maxi65 said:
What is your security patch date?
Click to expand...
Click to collapse
1st of december 2021.
If reboot can fix it for 24 hours then i won't bother rebooting it every 24 hours.
maxi65 said:
If reboot can fix it for 24 hours then i won't bother rebooting it every 24 hours.
Click to expand...
Click to collapse
Tried it but nothing has changed.
Goldenrooster said:
I have the very same issues after updating my S20 5G to One UI 4.0 Android 12. Tried everything without improvement. Rebooting te phone helps a bit for at most 24 hours, after which the phone is too laggy and stuttering again to work with...
Click to expand...
Click to collapse
Is it a memory leak? What's ram usage look like when it acts up? What apks or services are running? How much memory are they using? What's using a lot a battery and/or bandwidth?
Play with it... Adroids wuv attention.
I can go for many days without a reboot on my N10+'s, most of the times I reboot as an afterthought rather than a necessity. The Android OS should be very stable... not running like bloody Vista
blackhawk said:
Is it a memory leak? What's ram usage look like when it acts up? What apks or services are running? How much memory are they using? What's using a lot a battery and/or bandwidth?
Play with it... Adroids wuv attention.
I can go for many days without a reboot on my N10+'s, most of the times I reboot as an afterthought rather than a necessity. The Android OS should be very stable... not running like bloody Vista
Click to expand...
Click to collapse
The reason is still unknown.
maxi65 said:
The reason is still unknown.
Click to expand...
Click to collapse
You need to start looking for clues.
They are there in Device Care and Developer options showing what's cached, running and stats on memory usage. Seeing what's accessing the internet and how often is another tool to use. I also use 3rd party apps like Package Disabler to troubleshoot.
That's how I find almost everything that misbehaves on an Android.
I never upgrade an OS if it is fast, stable and fulfilling its mission. As I have already spent a lot of time to optimize it and find work arounds. Moreover I know how it should behave making malware easier to spot at the get go. I spend very little time on maintenance as such.
The current load on this phone will be 2 yo in June. That's the kind of stability the Android OS platform is capable of. If you're constantly mucking with the firmware and software you'll never realize this potential. Forget the Google update hype and go with what works... and always redundantly backup critical data.
Only thing that I can find is that RAM usage of Android System right after reboot is 14 MB, but after everything starts to lag and stutter (usually after 24 hrs) RAM usage is around 500 MB... Can't find any other strange behavior..
Goldenrooster said:
Only thing that I can find is that RAM usage of Android System right after reboot is 14 MB, but after everything starts to lag and stutter (usually after 24 hrs) RAM usage is around 500 MB... Can't find any other strange behavior..
Click to expand...
Click to collapse
I think usage of 500Mb can't effect the performance because it has 12 GB of RAM.
blackhawk said:
You need to start looking for clues.
They are there in Device Care and Developer options showing what's cached, running and stats on memory usage. Seeing what's accessing the internet and how often is another tool to use. I also use 3rd party apps like Package Disabler to troubleshoot.
That's how I find almost everything that misbehaves on an Android.
I never upgrade an OS if it is fast, stable and fulfilling its mission. As I have already spent a lot of time to optimize it and find work arounds. Moreover I know how it should behave making malware easier to spot at the get go. I spend very little time on maintenance as such.
The current load on this phone will be 2 yo in June. That's the kind of stability the Android OS platform is capable of. If you're constantly mucking with the firmware and software you'll never realize this potential. Forget the Google update hype and go with what works... and always redundantly backup critical data.
Click to expand...
Click to collapse
Ahan we went after the new features so updated.
maxi65 said:
I think usage of 500Mb can't effect the performance because it has 12 GB of RAM.
Click to expand...
Click to collapse
I found it in Developer Options under Active Services "RAM-Status¨ . All my other Android devices (phones and tablets) consistently indicate around 15 MB... Average Ram usage for Android OS (3 hours) indicates 1,8 GB...
Goldenrooster said:
I found it in Developer Options under Active Services "RAM-Status¨ . All my other Android devices (phones and tablets) consistently indicate around 15 MB... Average Ram usage for Android OS (3 hours) indicates 1,8 GB...
Click to expand...
Click to collapse
Looking at this screenshot, Very similar results.
maxi65 said:
Looking at this screenshot, Very similar results.
Click to expand...
Click to collapse
Try going to Running Services instead.
.5 gb of ram usage? That's way too low.
Here it is.
blackhawk said:
Try going to Running Services instead.
.5 gb of ram usage? That's way too low.
View attachment 5516403View attachment 5516409
Click to expand...
Click to collapse
blackhawk said:
Try going to Running Services instead.
.5 gb of ram usage? That's way too low.
View attachment 5516403View attachment 5516409
Click to expand...
Click to collapse
Running services voor app Android System (after reboot) is 15 MB, but when the phone starts to stutter it is 500 MB....
Related
Hello Android Gurus
I have bought Galaxy S (My first Android phone) 2 weeks ago and i have been experimenting with it since. I have noticed one thing regarding how android manages memory and its quite alarming.
When i start my phone I typically have around 160 Mb of RAM. As i load an application that requires 10 MB for example, the available RAM evidently drops to 150 MB but when I kill the application the RAM goes up but not to the previous level (e.g. goes up to 157).
little RAM is always lost as applications are opened and closed. This means that after a couple of hours of using the phone, the RAM goes down to 40 MB and the phone becomes REALLY laggy and you have to restart
The above behavior is typical of windows mobile, and that is exactly why i shifted to Android thinking it is better.
My questions to the android experts out there are the following:
1- Why is memory leaking like this. Such a behavior results in a phone with very bad user experience
2- Is this typical behavior of Android, if yes then i'd better sell my Galaxy S and look for an alternative OS
3- Is this due to TouchWiz by Samsung, if yes then i will wait for subsequent updates to see if this problem could be resolved by Samsung
4- Will the 2.2 Froyo update resolve this issue ?
I used to have an iphone 3gs before this one, and no matter how much you open or close applications, the UI is always smooth and responsive. The thing that made me really hate Apple and its products is their "Closed OS" that does not enable you to do much with your phone. That is why i moved to Galaxy S thinking it would give me a better experience
Thanks for your thoughts.
FREE RAM IS A WASTED RAM, golden rule of android.
Some time ago I did even a video so you can check what i'm talking about... http://www.youtube.com/watch?v=Ewxuy12KuUA
Dexter666 said:
FREE RAM IS A WASTED RAM, golden rule of android.
Some time ago I did even a video so you can check what i'm talking about...
Click to expand...
Click to collapse
That's an awesome video! I never knew the games looked so nice. I'm on a download spree because of that video now
Strange
Dexter666 said:
FREE RAM IS A WASTED RAM, golden rule of android.
Some time ago I did even a video so you can check what i'm talking about... http://www.youtube.com/watch?v=Ewxuy12KuUA
Click to expand...
Click to collapse
This is quite strange, the less RAM you have the more non-responsive the phone is and laggy.
Enough RAM has to be maintained to guarantee a smooth user experience.
If the phone requires 100Mb of RAM to run smoothly, then this much has to be maintained.
from my experience with the Galaxy S, there has to be atleaset 80 to 100 MB to maintain a somewhat smmoth interface.
Edit:
I also understand from your input that this is a Samsung problem, not an android problem, and that no matter how low the RAM is, the interface will always be smooth ??????
Mate, just one word - google.
There are about a billion articles online on android memory management, how to impoove it etc.
Dexter666 said:
FREE RAM IS A WASTED RAM, golden rule of android.
Some time ago I did even a video so you can check what i'm talking about... http://www.youtube.com/watch?v=Ewxuy12KuUA
Click to expand...
Click to collapse
i dont understand how this shows anything? You are manually exiting each one of the games, forcing it to quit anyways. A better test is just to hit the home button, and continually load up the next game.
andy2na said:
i dont understand how this shows anything? You are manually exiting each one of the games, forcing it to quit anyways. A better test is just to hit the home button, and continually load up the next game.
Click to expand...
Click to collapse
This means that after a couple of hours of using the phone, the RAM goes down to 40 MB
Click to expand...
Click to collapse
+red baloon on vid which says phone was used for >day, so "free" ram was <50MB, becouse browser etc. reserve some MBs for quick comming back.
And still was no problem to run anything I choose.
Dont quite understand..care to explain more? I'm getting puzzled abt this shortage of ram thingy. Some suggest to use task killer to free up rams while you say dont. But looking at your videos its fast..please explain. Thanks
Sent from my GT-I9000
Android handles the memory management itself. The moment it runs below certain amount of free memory it will start the kill apps. There is no need to run an app killer. Altho the default settings are not enough to provide a smooth experience. Check out the freememmanager app in the market to change the settings. As long as min 45 mb is free everything will run smooth.
Sent from my GT-I9000 using XDA App
RADLOUNI said:
2- Is this typical behavior of Android, if yes then i'd better sell my Galaxy S and look for an alternative OS.
Click to expand...
Click to collapse
This is typical Android behavior. See ya later.
Really though, if you're killing tasks, then you're already taking horrible advice from people who haven't an inkling of an idea on how Android manages memory.
Keep in mind that your phone is only using 256MB of its total 512MB of memory. Once a newer kernel is released with himem the phone will use all 512MB.
Android's garbage collection can be set to be more aggressive which would sort of fix your issue by killing more background applications. However, you might as well wait for the newer kernel which will fix your problem anyway.
Though it was more 320 out of 512
Sent from my GT-I9000 using XDA App
RADLOUNI said:
The above behavior is typical of windows mobile, and that is exactly why i shifted to Android thinking it is better.
My questions to the android experts out there are the following:
1- Why is memory leaking like this. Such a behavior results in a phone with very bad user experience
2- Is this typical behavior of Android, if yes then i'd better sell my Galaxy S and look for an alternative OS
3- Is this due to TouchWiz by Samsung, if yes then i will wait for subsequent updates to see if this problem could be resolved by Samsung
4- Will the 2.2 Froyo update resolve this issue ?
Thanks for your thoughts.
Click to expand...
Click to collapse
This has to do a lot with Android's garbage collector. The reason task-killers are not the best way to go, is because when you kill tasks a lot of the memory is not recovered (garbage collector does not work as it should). Android by default won't start killing apps until you get between 20-30MB of memory. For some reason, in the SGS, as you said, when ram drops below 70MB, the phone starts to feel pretty laggy; the best way to remedy this is to use applications like autokiller or minfreemanager, which require you to be rooted.
For a more in-depth explanation of how android kills processes see this http://andrs.w3pla.net/autokiller/details (from the developer of Autokiller).
I would like to know why the phone feels so laggy when ram drops below 70MB, from what I understand, this shouldn't be the case...
2- Is this typical behavior of Android, if yes then i'd better sell my Galaxy S and look for an alternative OS
--> No, this is not typical behavior of Android, i use my HTC Magic before Galaxy S, no lagging problem even the memory is lower than 15MB.
The galaxy S defaults are too low for when it starts removing apps from RAM, you need to root it and then install minfree manager or autokiller (which is not a task killer don't be deceived by the name)
Brantyr said:
The galaxy S defaults are too low for when it starts removing apps from RAM, you need to root it and then install minfree manager or autokiller (which is not a task killer don't be deceived by the name)
Click to expand...
Click to collapse
doesn't solve the mystery because this is a non-issue on other android phones.
why do i need to keep 50-70mb free to get a smooth running phone where others can handle 30mb free without problems.
Goshh..thanks for simplified. Now ive removed the task killer..and stand firm by the android golden rules...cheers..
Sent from my GT-I9000
I noticed this same low ram behavior on my galaxy s. After boot the phone shows like 180 mb of ram free after a couple days the phone will drop down to 30 mb of ram all the while I'm killing apps running in the background with task killer.
The phone slows down significantly even after I kill everything.i thought android was supposed to circumvent these kind of low ram Issues.
inurb said:
I noticed this same low ram behavior on my galaxy s. After boot the phone shows like 180 mb of ram free after a couple days the phone will drop down to 30 mb of ram all the while I'm killing apps running in the background with task killer.
The phone slows down significantly even after I kill everything.i thought android was supposed to circumvent these kind of low ram Issues.
Click to expand...
Click to collapse
It is.
And you're supposed to not be messing with how Android manages things cuz taskkilling screws it up.
reuthermonkey said:
It is.
And you're supposed to not be messing with how Android manages things cuz taskkilling screws it up.
Click to expand...
Click to collapse
So you suggest that I not force close any apps using taskkiller and just let android 2.1 do it's thing with memory management?
When I had the phone for the first week without taskkiller installed, the device ran very slow after the first couple days of use. Your saying that the slowness will go away as android dishes out memory effectively?
I'll uninstall taskkiller and let the device run longer than a week and see if it ever speeds up. thanks
Hey,
So I've been using my Nexus 5x with much pleasure but lately it's getting impossible to switch tasks fast, because they're all closing because of memory shortage. Looking in my settings it shows me that Android OS (780mb), play services (150mb) and Android system (140mb) and System UI (90mb) together take up almost 1,2GB of the 1,8gb memory. I don;t know if this is related to me being in the preview program (and having a lot of preview images updates over the last year) or it's just that the newer Android takes up more memory.
I'm pondering stepping out of the bèta program and reflashing the stock rom, but I was wondering if any of you can shed some light if this will actually help.
Thanks!
eldinnie said:
Hey,
So I've been using my Nexus 5x with much pleasure but lately it's getting impossible to switch tasks fast, because they're all closing because of memory shortage. Looking in my settings it shows me that Android OS (780mb), play services (150mb) and Android system (140mb) and System UI (90mb) together take up almost 1,2GB of the 1,8gb memory. I don;t know if this is related to me being in the preview program (and having a lot of preview images updates over the last year) or it's just that the newer Android takes up more memory.
I'm pondering stepping out of the bèta program and reflashing the stock rom, but I was wondering if any of you can shed some light if this will actually help.
Thanks!
Click to expand...
Click to collapse
It's part of the new method for ram management. It's normal. You'll notice those take up tons of ram even on a fresh install. Over time the more apps you install the more processes they auto start. This is what will cause those things to happen. For me I noticed for example first when the HDR processing of taking a picture would push hangouts out of memory even when I was actively talking voice, it just wasn't in the front running. Android does much like windows now in claiming lots of memory to better manage and allocate it as needed
Sent from my Nexus 5X using Tapatalk
On a fresh boot, my phone takes up 1.2GB of RAM, and quickly rises to ~1.4-1.5GB. It usually says there, as I don't use a lot of apps, so I'm not multitasking a lot. It's pretty odd compared to my other devices that use anywhere from 500-700MB of RAM for the OS, but it seems to do it's job just fine nonetheless.
Side note, since I don't have a lot of Apps, and I'm not concerned about RAM usage, I've disabled zram and ksm. Haven't noticed any difference, TBH.
crazyates said:
On a fresh boot, my phone takes up 1.2GB of RAM, and quickly rises to ~1.4-1.5GB. It usually says there, as I don't use a lot of apps, so I'm not multitasking a lot. It's pretty odd compared to my other devices that use anywhere from 500-700MB of RAM for the OS, but it seems to do it's job just fine nonetheless.
Side note, since I don't have a lot of Apps, and I'm not concerned about RAM usage, I've disabled zram and ksm. Haven't noticed any difference, TBH.
Click to expand...
Click to collapse
On a fresh boot it loads every apps auto start process. So that doesn't change anything at all. I am not talking about apps using ram from being run. I'm talking about all the processes they have that are triggered and restart when things occur.
Sent from my Nexus 5X using Tapatalk
Hello.
I got a Mi A2 Lite a few days ago, is my first Android One. My model have 3Gb of RAM.
I'm facing the following problem:
Let's say I'm playing Lords Mobile (the only game I play). Then, I receive a message on WhatsApp. I go there and reply. I then go to Facebook and/or Chrome to check something, and want to go back to Lords Mobile. The game was pulled out from memory, and need to reload again from zero. Same with Chrome, it shows all my tabs I had opened, but is surelly reloading again from zero. Is like the "clear all" of 'recent apps' on some other phones.
I think 3Gb of RAM is enough to handle these apps, don't? I don't have too much apps installed, and the memory use is about 2Gb. I don't know if this behavior is native, by the way. Another example: if I go to sleep just after play, when I go to game again in the morning, the game reload from zero.
Is this normal? Any way to make this model handle the memory in a better way, if is the case?
My device is on Pie, July security patch. No root.
Thanks in advice
It gets better over time. There is "AI" that figures out what to keep in memory.
But in general, pie seems to be worse than previous releases at keeping things in memory, even when memory is not full.
a1291762 said:
It gets better over time. There is "AI" that figures out what to keep in memory.
But in general, pie seems to be worse than previous releases at keeping things in memory, even when memory is not full.
Click to expand...
Click to collapse
Thanks.
Is there a way to get rid of AI, or set an app to be excluded from this?
romulocarlos said:
Is there a way to get rid of AI, or set an app to be excluded from this?
Click to expand...
Click to collapse
Not that anyone seems to know. Maybe custom ROMs help?
I just used my phone like normal and noticed that it got better at not unloading apps that I came back to regularly.
You can try to force Android Go mode, since it's designed for really small RAM use but I tried it and didn't like it (changes some things).
a1291762 said:
Not that anyone seems to know. Maybe custom ROMs help?
I just used my phone like normal and noticed that it got better at not unloading apps that I came back to regularly.
You can try to force Android Go mode, since it's designed for really small RAM use but I tried it and didn't like it (changes some things).
Click to expand...
Click to collapse
Thank you. I don't go for Android Go, seems worse. lol
Any other suggestions will be welcome.
It's not AI, it's the Kernel's scheduler profile, and Xiaomi is famous for tuning it with an aggressive policy towards keeping as much RAM available as possible. The only way to improve it is by installing a custom kernel.
slimshady76 said:
It's not AI, it's the Kernel's scheduler profile, and Xiaomi is famous for tuning it with an aggressive policy towards keeping as much RAM available as possible. The only way to improve it is by installing a custom kernel.
Click to expand...
Click to collapse
Well, custom kernel and ROMs means unlocking bootloader... I can't do this for now. But, anyway, thanks!
3 gigs of ram is barely enough for pie. On the 4 gig version I have barely 1 gig free at idle. But mostly, the app kill is done by a crappy A.I. system that does some battery optimization.
TheoXSD said:
3 gigs of ram is barely enough for pie. On the 4 gig version I have barely 1 gig free at idle. But mostly, the app kill is done by a crappy A.I. system that does some battery optimization.
Click to expand...
Click to collapse
Well, taking in note what @slimshady76 wrote above, maybe the "Butterfly for daisy" will be a good deal. But I can't do it now.
I just made a test on last 2 days.
I uninstalled any optional app on phone I downloaded, and disabled a lot of system apps. Lords Mobile won't unload from memory when switching and/or when I sleep and back to game at morning.
So, is a lack of memory, but I still thinking 3Gb is enough to handle it. When 10.0.12.0 comes available to download, I'll try Butterfly kernel.
Installed it about an hour ago (UK) and in general the phone seems a noticeably zippier for browsing and opening apps etc.
I am not a tech head, and the update is small, only 13 ish megabytes, but feels like the sluggishness I had been experiencing the last six months has gone somewhat. I had really set my mind and wallet on getting a Pixel 4a, but may stick with this a bit longer if the sluggishness has improved.
Wonder if others are finding the same ?
DonkeyKonk said:
Installed it about an hour ago (UK) and in general the phone seems a noticeably zippier for browsing and opening apps etc.
Click to expand...
Click to collapse
You rebooted to install it and that is known to temporarily solve the "ram issues" that android 10 has on this phone.
It's not the update.
a1291762 said:
You rebooted to install it and that is known to temporarily solve the "ram issues" that android 10 has on this phone.
It's not the update.
Click to expand...
Click to collapse
Ohh, it is the update. This one really made the phone feel snappier, and visibly improved performance. Usually it slugs down to a crawl while I'm testing to see if it's still usable after the update, and even after 24hrs after the update it still works just fine, no hogs, no slow downs, minimal stuttering while heavy multi-tasking.
For example, on 11.0.7, go to Chrome, access fast.com (internet speed test) - it downloads and uploads a test file, so intensive i/o memory usage, and try closing the tab and chrome while still downloading... it's slow, it stutters a lot, it occasionally freezes the device, that doesn't happen anymore in august update. Also the speed limitation I was talking about in my review of 11.0.9 is now gone.
TeoXSD said:
Ohh, it is the update. This one really made the phone feel snappier, and visibly improved performance. Usually it slugs down to a crawl while I'm testing to see if it's still usable after the update, and even after 24hrs after the update it still works just fine, no hogs, no slow downs, minimal stuttering while heavy multi-tasking.
For example, on 11.0.7, go to Chrome, access fast.com (internet speed test) - it downloads and uploads a test file, so intensive i/o memory usage, and try closing the tab and chrome while still downloading... it's slow, it stutters a lot, it occasionally freezes the device, that doesn't happen anymore in august update. Also the speed limitation I was talking about in my review of 11.0.9 is now gone.
Click to expand...
Click to collapse
Well I think these ss weren't automated replies after all.
TeoXSD said:
even after 24hrs after the update it still works just fine
Click to expand...
Click to collapse
Apparently I rebooted this morning so I only have 16 hours of uptime. But I have been rebooting weekly so I feel it is still a bit early to be celebrating.
That said, I did just have XDA stay in memory while I downloaded podcasts, updated apps and opened some pages in both Firefox beta and Firefox (opening pages to copy urls over without sync).
Maybe it was a build.prop tweak. That would be small...
a1291762 said:
Apparently I rebooted this morning so I only have 16 hours of uptime. But I have been rebooting weekly so I feel it is still a bit early to be celebrating.
That said, I did just have XDA stay in memory while I downloaded podcasts, updated apps and opened some pages in both Firefox beta and Firefox (opening pages to copy urls over without sync).
Maybe it was a build.prop tweak. That would be small...
Click to expand...
Click to collapse
Actually what I want to say is I am using l speed and I have changed the RAM management profile to multitasking and that fixes my issue and basically it is it editing the build prop my question is if Xiaomi did the same thing and fix the issue isn't it good I mean I can do it with root but all they did was changed this thing which they could have done a long time ago but do keep in mind whenever I use this profile my battery drains a bit faster not like a lot faster only a little bit faster.
Aadil Gillani said:
I am using l speed and I have changed the RAM management profile to multitasking and that fixes my issue and basically it is it editing the build prop my question is if Xiaomi did the same thing and fix the issue isn't it good
Click to expand...
Click to collapse
I found lspeed and friends to extend the time I could run before reboot, not fix the problem.
But now I'm curious so I'm gonna diff the partitions to find out what they changed.
a1291762 said:
I found lspeed and friends to extend the time I could run before reboot, not fix the problem.
But now I'm curious so I'm gonna diff the partitions to find out what they changed.
Click to expand...
Click to collapse
Please do tell what they changed
I'm ... not seeing anything obvious
build.prop changed, but it's just timestamps and versions (ie. normal "make a release" stuff)
only boot, system and vendor were modified
I've attached the diff report (not changes, just modified files), minus a large number of .odex files.
Looks like some media lib bugs got fixed.
I dunno... also, I tried to run the diff on my phone and killed it so my uptime was reset again (finished the comparison on my computer, after converting and mounting the images).
TeoXSD said:
Ohh, it is the update. This one really made the phone feel snappier, and visibly improved performance. Usually it slugs down to a crawl while I'm testing to see if it's still usable after the update, and even after 24hrs after the update it still works just fine, no hogs, no slow downs, minimal stuttering while heavy multi-tasking.
For example, on 11.0.7, go to Chrome, access fast.com (internet speed test) - it downloads and uploads a test file, so intensive i/o memory usage, and try closing the tab and chrome while still downloading... it's slow, it stutters a lot, it occasionally freezes the device, that doesn't happen anymore in august update. Also the speed limitation I was talking about in my review of 11.0.9 is now gone.
Click to expand...
Click to collapse
I have downgraded to android 8.1 version 9.6.11.0
Tried that thing with fast.com no stutter nothing! I would suggest everybody who is tired with xiaomi updates on this phone to downgrade to android 8.1 like i did and it will remind the reason why you purchased this phone in the first place! Its super fast, super responsive, the statusbar icons dont take to much space, everything is working and games will be in ram even if you minimize at morning and reopen at midnight! I thought i would change my phone because it was useless and now it is faster than i ever remembered!
Nearly 4 days of uptime and my phone is once again killing apps as soon as I leave them.
Well nearly been a week now since the update, and definitely feels to me.that things have improved at lot in general use.
Not as good as it was brand new, but nowhere near as bad as it was getting the previous few months, and very usable.
Battery life seems to have gotten back to where it was before too.
Can anyone tell me a fix for this android 10 ram management fix? The phone can't keep hold of more than two apps in the background. Need everyday Restart and Performance in not quite good...
NiKabir said:
Can anyone tell me a fix for this android 10 ram management fix? The phone can't keep hold of more than two apps in the background. Need everyday Restart and Performance in not quite good...
Click to expand...
Click to collapse
Not sure if you're open to flashing a custom ROM, but I had this same issue and switched to HavocOS. My phone has an uptime of 450+ hours at this moment and performance is quite good. Battery life is comparable to stock.
More info on HavocOS
Can anyone tell me a fix for this android 10 ram management fix? The phone can't keep hold of more than two apps in the background. Need everyday Restart and Performance in not quite good...
Click to expand...
Click to collapse
Could be also affect by corresponding "Developer options ON">APPS>Background process limit>choose. Check it.
I had never this problem with stock android 10/One/Q.