1st question
Spoiler
Well, first of all, good day/afternoon/night to everyone.
After watching a youtube video I got pissed off and disgusted. I saw a guy running a PS1 emulator in a XPERIA Play. For what I know, our phone is better in every aspect (hardware and software). But, in the video description and in the phone specifications (vid), says that it has 800 MB RAM. And a dude has asked how he got so much RAM. And he simply answered: Virtual RAM.
Resuming. What do I want to know:
::::::: ::::::: ::::::: ::::::: ::::::: :::::::
- What is virtual RAM (How it works);
- Can we use it on our phone? There are any exceptions or anything that could damage it?
- If possible to use, can we feel the difference? Is it notable? Like, in games, multitasking... Etc.
2nd Question:
Spoiler
And the other thing: Background apps.
I use my phone a lot, playing games and sending messages (Facebook, Gmail, SMS, Whatsapp)...
It's been performing quite good until now, but there's one thing that pisses the *uck out of me: WHY CANT IT STORE APPS IN THE BACKGROUND?
I mean, like in this example:
I am playing NFS:MW. And then, I receive a message. What does usually normal people do when receive a message? That's right. READ IT (OR AT LEAST TRY TO). So. I press the home button, go to "Messages" and read it (and maybe answer it). Ok. I try to get back to the game by long pressing home, and clicking into it. And then, suddenly, it goes right away to the *****NG STARTING SCREEN. :banghead:
And this does not happen only with games. This happens with almost every "background" running task. Can I solve this? I mean, what's the point of having a "background" apps list if you cannot actually open them? Now there's something that annoys the F*CK out of me. Thanks.
About background apps closing ... looks like you are running out of RAM.
Game is still in background, for as long as system do not need that RAM used by your game.
When more RAM is needed background apps are being killed to free that RAM to be used by foreground activity (in your case - game is killed so your messenger can run in that RAM)
This is feature not bug, Android acts like that on purpose.
IDK about virtual RAM on android
RafaeLlLoki said:
1st question
Spoiler
Well, first of all, good day/afternoon/night to everyone.
After watching a youtube video I got pissed off and disgusted. I saw a guy running a PS1 emulator in a XPERIA Play. For what I know, our phone is better in every aspect (hardware and software). But, in the video description and in the phone specifications (vid), says that it has 800 MB RAM. And a dude has asked how he got so much RAM. And he simply answered: Virtual RAM.
Resuming. What do I want to know:
::::::: ::::::: ::::::: ::::::: ::::::: :::::::
- What is virtual RAM (How it works);
- Can we use it on our phone? There are any exceptions or anything that could damage it?
- If possible to use, can we feel the difference? Is it notable? Like, in games, multitasking... Etc.
2nd Question:
Spoiler
And the other thing: Background apps.
I use my phone a lot, playing games and sending messages (Facebook, Gmail, SMS, Whatsapp)...
It's been performing quite good until now, but there's one thing that pisses the *uck out of me: WHY CANT IT STORE APPS IN THE BACKGROUND?
I mean, like in this example:
I am playing NFS:MW. And then, I receive a message. What does usually normal people do when receive a message? That's right. READ IT (OR AT LEAST TRY TO). So. I press the home button, go to "Messages" and read it (and maybe answer it). Ok. I try to get back to the game by long pressing home, and clicking into it. And then, suddenly, it goes right away to the *****NG STARTING SCREEN. :banghead:
And this does not happen only with games. This happens with almost every "background" running task. Can I solve this? I mean, what's the point of having a "background" apps list if you cannot actually open them? Now there's something that annoys the F*CK out of me. Thanks.
Click to expand...
Click to collapse
Maybe what you call "Virtual RAM" is actually...Swap feature from Linux, so, how do you do it?.
Go to CWM->advanced-> partition external sdcard (THIS WILL DELETE EVERYTHING FROM IT, make a backup), select swap partition size (whatever you want really, it doesn't have a real use in our device). Sw.....wait for it....ap done!
About the multitasking problem of yours. Do you use scripts? Most of the time this happens only with custom kernels and strict memory kill values. Check if it happens in stock ROM with stock kernel. I doubt it would.
chemicalrage said:
About the multitasking problem of yours. Do you use scripts? Most of the time this happens only with custom kernels and strict memory kill values. Check if it happens in stock ROM with stock kernel. I doubt it would.
Click to expand...
Click to collapse
No. I don't. I use the CoCore. When I used the stock kernel it was the same thing basically. The changes were that I didn't have a custom recovery neither a custom kernel (???).
:::: :::: ::::
And about the "swap". Could it be done with TWRP instead of CWM? And could it also be done with a vold.fstab nodded system?
RafaeLlLoki said:
No. I don't. I use the CoCore. When I used the stock kernel it was the same thing basically. The changes were that I didn't have a custom recovery neither a custom kernel (???).
:::: :::: ::::
And about the "swap". Could it be done with TWRP instead of CWM? And could it also be done with a vold.fstab nodded system?
Click to expand...
Click to collapse
About TWRP, probably no.
Linux kernel (If I understand correctly) searchs swap partition by itself, so, yes, if you have a modded vold.fstab or want to mod the vold.fstab, you can enable Swap without problems.
I've found a method that allows me to easily SWAP my phone.
http://forum.xda-developers.com/showthread.php?t=1659231
This is the link.
Do you guys think it would work for me, considering that I have a 16 GB card/vold.fstab modded ROM/CoCore (custom kernel)/Stock ROM???????
pinEur the
To emulate ps1 is a very easy thing to do, even a galaxy 5 can do it
And you probably are using a lot of social networking (Facebook, Twitter, etc)
Cause I'm using this phone
can hear music, play n64 and then when a music that i don't want to hear comes I can hold the home and go to music player, change my music and resume playing, the same I can do with all my emu
I'm using stock everything (jb) and only rooted phone with io scheduler noop
Related
Can't see why this is the case (but it obviously is) as long as I have lots of free disk space and not many apps running at the same time. Any logic in this?
I've been experiencing the same issue and wondering the same thing...
Sent from my Samsung Galaxy S GT-I9000 using Tapatalk Pro
There seems to be several things causing this, but the two key issues are:
The moviNAND (the internal flash drive/"SSD") firmware seems to have an issue with fsync() taking extremely long. E.g., it slows down whenever a file is written/updated on the internal storage.
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
There are several topics on these issues in the Android Development forum. There are also several "lag fixes" trying their best to overcome these issues. Go check them out
Einride said:
There seems to be several things causing this, but the two key issues are:
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
Click to expand...
Click to collapse
We have no idea if that is ACTUALLY true.. Just because fsck picked some things up on 1 phone, doesn't mean it happens everywhere.. Furthermore, it doesn't mean the problems detected affect operations
that has no truth at all about more apps slowing down the phone, my phone is the prove
Before jpk i didn't noticed slowdowns with aprox 100 apps, now i do on jpk =/
Prolly that all pictures/links/info stays in his workmemory?
probably cause some of them run in the system memory or run at startup
KaliKot said:
probably cause some of them run in the system memory or run at startup
Click to expand...
Click to collapse
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
AllGamer said:
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
Click to expand...
Click to collapse
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Oletros said:
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Click to expand...
Click to collapse
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
bonehooch said:
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
Click to expand...
Click to collapse
Utter ****e? Why?
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
AllGamer said:
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
Click to expand...
Click to collapse
With autokiller the phone is still laggy.
And please, stop thinking I'm stupid or I don't know a **** about smartphones, ROM's changing, firmware or knowing how a phone must run.
AFAIK this topic and its responses are for the OP
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
TMReuffurth said:
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
Click to expand...
Click to collapse
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Autokiller and task killers are not the solution here! Quick lesson on Android, and why having even A SINGLE BAD APP is going to ruin your whole phone!
Android has something called an 'Intent'. In order to start an app, an intent is made by your launcher or a button you press, and the Android system reads this intent and works out what app it needs to start up.
There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it. This means that an app can register to listen to all sorts of events, such as battery level changed, application start, or a tons of other things. Even if the application is closed, if it is registered as a listener, Android will start it right back up so it can deal with the intent. If the intent comes every 5 seconds, Android will run this app every 5 seconds even if you have a taskkiller killing the app.
The only real solution is to not install apps which are bad! Finding bad apps is a real mission, too. Hopefully in the future, utilities will be available to let us track down these terrible apps, but till then, you'll have to work it out yourself.
yiannisthegreek said:
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Click to expand...
Click to collapse
No need for Root to use all features of Autorun Killer. I would disable only the apps you know and which you do not need at startup and running in background, such as (in my case) Paypal, App Center from Androidpit, Daily Briefing, Photoshop Express, Word Press, TweetCaster, etc.
Every of these apps works normal, even when deactivatet on startup.
So unless you do not disable system apps (must be previously set enabled in settings) you are safe.
RyanZA said:
(...)There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it.(...)
Click to expand...
Click to collapse
Is there any possibility/app to show what is registered for which app?
watching the apps
Samga said:
Is there any possibility/app to show what is registered for which app?
Click to expand...
Click to collapse
There is an app called Autostarts at 0.95$.
It shows what is launched au startup, when you enable/disable wifi etc.
It think it gives insight on how apps seems launching out of nowhere.
I also reccomend Watchdog Task Manager Lite, the free version.
It does not kill anything, but notifies and logs the bad apps that consumes over a certain CPU percentage.
You don’t need to change your ROM to get the best from your 2x, just a rooted stock ROM and a couple of apps that will change things dramatically. One thing I’ve noticed on the 2x is its memory management is too lenient and gets consumed quickly by background tasks etc. In no time I was down to 40-30Mb free memory and then my phone would run like a dog resulting in a reboot as the only solution.
Installing task and app killers are not the way, as they’ll only give you a short respite before the apps and background tasks you killed relaunch.
However, there is a solution.
1)Root your phone using SuperOneClick (piece of cake, instruction already on this forum)
2)Install “AutoKiller Memory Optimizer” by AndRS Studio free from the market
Optional
3) Install “Watchdog Task Manager” by Zolmut LLC (There’s a free or Paid version) I paid!
4) Install “Root App Remover” by Best of Best Android app
AutoKiller is not a task killer/manager it reconfigures Androids inbuilt memory manager to kill or suppress memory usage by applications and tasks. I now always have about 140-170MB free RAM at all times regardless of what I’m doing (but I do close my apps with the back button rather than click home)
AutoKiller Memory Optimizer Settings
I’ve used the ‘Extreme’ settings to ensure I have around 150MB free, and this makes a huge difference in everything I do with the phone.
----------Optional things you may want to consider-----------
Watchdog
Yeah, I know this is a task killer but Watchdog is different from other task mangers as it monitors CPU usage rather than free RAM, 3D Gallery for example is a CPU hog on my 2X, so I configured it to be killed if it consumes more than 30% CPU whilst running in the background, you’d be surprised what saps your battery!
Root App Remover
Uninstall the tosh supplied on the ROM, I removed the following, AndroidBackup (I use Titanium Backup), CarHome, F-Secure_Mobile_Security, SNS (If you’re not using the built in Facebook and Twitter app).
I also use LauncherPro with Beautiful Widgets to give my phone an almost HTC Sense look and feel and uninstalled LG Home using Root App Remover afterwards.
Hope it makes a difference for you, it did for me, vote if you like
What do you think having 140-170MB RAM free at all times actually does?
Guess what? Nothing.
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
We want to see some bench marks.
Thanks for sharing! My phone does become much more responsive
Sent from my LG-P990 using XDA App
I tried the app too and i can say that it works, I also did some of the advanced tweaks.
phone seems more responsive now.
Yes, me too. It's more responsive now. Also when I open app manager, the app list is a lot faster.I know it's more related to file read/write but still it's nice to finally able to browse with less waiting time.
Sent from my LG-P990 using XDA App
thx
good one and simple, thx
cann someone please post some benchmarks?
Here are some screenshots, tested with AnTuTu Benchmark
The first one is v10c stock, some apps like f-secure, carapp etc frozen, second one is with using autokiller memory with preset extreme, third one is to compare, this was while using cm7.1 rc
now we'll see if autokiller works stable ^^
edit: realized that with cm7 something seemed to be wrong with the sd-card, so don't forget to compare the single-scores
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'm sure Rusty knows what he is talking about. Thing is, this talk about "the more free ram the better" has been repeated so many times, and at the end of the day, it seems to be more about user preference.
The default LG ROM seems to allow tasks to run in the background until it reaches around 50MB free RAM, then it starts to close tasks one by one. For multi-taskers like me, this is fine, I love how I can switch between facebook, tweetdeck, miren browser, google+, gmail, and messaging without seeing the apps reload.
For some, they'd want to open a task, close it, and move on to another without looking back. I guess that is where the 100MB of RAM is good for.
If you guys will be looking at benchmarks, I can guarantee that you will have higher scores with RAM optimizers. As benchmarks do not test multitasking, they simply check the performance of your phone at that point in time. (Which is also why some modders pump up their CPU freq to insane values before doing their bench then posting it.)
I have nothing against AKMO, and I find it very effective for Froyo builds. But I would recommend that each user try it out themselves. It's not a "1 fix for all" thing.
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
kiljacken said:
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
Click to expand...
Click to collapse
Does O2X already support swap space in EXT? (Or are your referring to VM heap?)
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
akyp said:
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
Click to expand...
Click to collapse
Yeah, FR19 is one of the more stable ROMs out there. Try full wipe then reflash maybe.
I've downloaded to my LG Optimus Black 30 apps til' now, I'm on Zeus V2.1
When I had the stock rom I had 100 apps!!
Does installing many apps necessarily slow down the phone? or It doesn't have to affect on the phone memory and speed?
On the one hand, I know that the phone is a lot faster when It has only few apps, and on the other hand, I have an Android Phone, Why not to have funny apps like lighter and games. What's your opinion?
Short answer: Mostly less is more...
Means: A lot of apps stay in memory and slow down ur phone, as u alread answered to urself, some even keep running in background and can keep the cpu from going to deep sleep mode, if they are not programmed well.
So yes, many apps slow down ur phone
Well, to describe it correctly, i would like you to explain that it's not the "numbers" of applications that matters.... I mean, we have a whole one GB of internal space, so we can easily afford 100+ applications.
So, it's actually the "type" of applications that give you a considerable effect on your device's performance.
# Example : i have installed TorrentFreak reader application. When i open it to read TF articles, it opens... when i exit it, it exits... shuts down completely. Now, i have installed UNO game from glu, which even if i don't open, it brings me advertisement notification.
So, the moral of story is, if i have installed hundreds of applications like TFreader, they won't cost me any RAM or any battery usage if i don't use it. But if i install just 10-15 apps like UNOgame of glu, they will use my data connection, RAM etc. in background even if i hardly use them.
So, always choose the application wisely, that's the point. Check their permissions, see if they add any "services" that may keep consuming your cpu cycles..... and you are good to go.
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
douginoz said:
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
Click to expand...
Click to collapse
Try enabling zram, I haven't tried it personally but its supposed to allow for more multitasking.
Sent from my Nexus One using xda app-developers app
Moved To Q&A
You may of considered it dev based, but its a question so belongs in the Q&A section.
I've tried ZRAM now for a couple of days but makes no difference. I also have the problem on another Android device. I'm convinced its some sort of design limitation of the opsys or something. When I start up Grindr, it takes a long time to load all the images, make connections, etc. Then I start of Gruff, and it does the same. As long as I don't try to go to another app, I can flip between the two of them without them restarting/reloading/reinitialising themselves. That is clearly because their pages didn't get swapped out of memory or flagged for deletion and deleted.
But if I do something else, or even try to use additional functions within either app, its too much and the next time I try to flip to the other app, it has to reload and reestablish connections etc.
Its not just those apps either. The same with a game like Candy Crush. Or many many apps.
So either my devices don't have enough memory of some form to allow many concurrent apps to run without being swapped out, or Android can't handle it and unnecessarily swaps out or deletes a process's memory pages to make room for the next process, >>> even if the device has plenty of memory<<<.
I don't know which type of memory the opsys needs if this is the case. I'd like to know so that i can make sure there's ample available so that this constant restarting doesn't keep happening. It seems stupid to me that Android does this if the device has got "heaps" of available memory (no pun intended). Newer devices will continually have more and more built in memory, so if Android is doing this arbitrarily and not because of space issues then its, well, stupid.
I have to assume its my devices that are the problem. They're both old (Nook Color, Nexus One). But with the NC, I'd assume we can partition some of that 5GB for use as main memory to run lots of processes concurrently, without this annoying swapping/page deletion/forcing re-inits all the time.
I'm also having problems figuring out where in XDA to post this question - its not NC specific, or dev specific, but I need answers from people that know the Android architecture so I can work out if its possible to stop this from happening.
Hello fellow MI5 users,
I received my phone one week ago and I start having some issues with the RAM. In fact, at the start of the phone, it's already at 70% filled up which is too much for me. Indeed I use a lot of RAM and I'm that type of guy who let the apps running in background everytime because I keep opening them everytime. I was wondering if it was possible to have a link to a better ROM because I guess it's the problem and also a link for a tutorial on how to flash it I'm a newbie in this type of manipulation but I'm very interested so I hope you will help me guys. By the way, my MIUI version is the MIUI 8 Global 6.8.18. I honestly don't know what can i give as information but I'll answer ASAP at any questions
Have a good day
This is working as design - Android keeps apps in RAM to reduce I/O on resuming from background - faster & more energy efficient.
You can change the number of background processes via the development settings or you can kill apps on closing.
adwinp said:
This is working as design - Android keeps apps in RAM to reduce I/O on resuming from background - faster & more energy efficient.
You can change the number of background processes via the development settings or you can kill apps on closing.
Click to expand...
Click to collapse
I've seen that indeed but it was set at standard so I'll probably put it at 3 I guess. How should I set the memory optimization? I've read it should be set off, altough I tried middle and I feel comfortable like that?
Is it normal to start at 70% without anything started ?
Unitae said:
I've seen that indeed but it was set at standard so I'll probably put it at 3 I guess. How should I set the memory optimization? I've read it should be set off, altough I tried middle and I feel comfortable like that?
Is it normal to start at 70% without anything started ?
Click to expand...
Click to collapse
For the 3GB version? Pretty much. MIUI is horrible.
After booting I typically had 1.3GB / 3.0GB free but after a while this averaged to around 650MB free.
free ram is useless ram , which cant accelerate anything
ps2lover said:
free ram is useless ram , which cant accelerate anything
Click to expand...
Click to collapse
I know that but I need more because I use multi-task a lot. Is there a way to change the ROM so I have more space to work with? Even if the ROM itself is beautiful.
Indeed it's the 3gb version 32gb. It have lags sometimes and I think it's due to the full RAM. Can I have a link to a custom ROM which works fine on this device?
I'm a little confused, you want as much RAM available but you want as many processes in the background as well? That sounds contradicting to me. Memory optimization maps to ZRAM, if you set it off there will be no memory compression and thus even less processes will be kept in the background. If you set it high, you can have as many processes as possible, but there could be lag due to (de)compression time overhead.
Try different Rom
Try to use a different Rom. On the Stock Rom is a lot of bloatware which is using your RAM too.
First you need to get an Bootloader unlock permission and have to unlock the BL.
It could take up to 10 Days to get the permission from Xiaomi
http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
After that you have to flash a recovery like trwp via ADB. Google it for videos or threads how to do it.
http://forum.xda-developers.com/mi-5/development/recovery-twrp-xiaomi-mi-5-t3412123
After that you can flash a developer Rom.
I use the Resurrection Remix and it works fine. The CM 13 stucks in Bootloop. Maybe because I made a full wipe and had to sideload my rom.
Because you don't have a SD card option you have to have the room installed on your hard drive. But just follow the description below
http://forum.xda-developers.com/mi-5/development/unofficial-resurrection-remix-m-5-6-9-t3395945
It took me just 1 day to get the unlock permit but don't try do do it without it. You brick your phone.
The RR Rom works really fine. Fingerprint and everything. It has no bloatware and you have to get the gaps like in the description. Arm64 nano seems enough.
Good luck and fun with a great phone.
Normally the android system kills the unused apps even in background. But i also experienced lack in multitasking.
leledumbo said:
I'm a little confused, you want as much RAM available but you want as many processes in the background as well? That sounds contradicting to me. Memory optimization maps to ZRAM, if you set it off there will be no memory compression and thus even less processes will be kept in the background. If you set it high, you can have as many processes as possible, but there could be lag due to (de)compression time overhead.
Click to expand...
Click to collapse
I think you misunderstood the OP question, he wanted more free RAM at start in order to have as many as possible apps in the background.
lapocompris said:
I think you misunderstood the OP question, he wanted more free RAM at start in order to have as many as possible app in the background.
Click to expand...
Click to collapse
Yup exactly
Try trwp 3.0.2.0 with 3.0.2.1 people experience bootloop
Omied said:
Try trwp 3.0.2.0 with 3.0.2.1 people experience bootloop
Click to expand...
Click to collapse
In fact, I'm just doing some research before asking because I'm very new. I have found some videos but they are pretty old and not on this phone but I guess it works more or less the same way
lapocompris said:
I think you misunderstood the OP question, he wanted more free RAM at start in order to have as many as possible apps in the background.
Click to expand...
Click to collapse
OK, in that case, just open Security->Permissions->Autostart and disable those which aren't immediately needed upon start. I have 18 autostart items (mostly system monitoring & social media apps) and I usually start with 1.5 GB free RAM.