Database Develop

Milestone ram management is horrible?

Im on got 2.2 but this happened to me with 2.1 too, is really annoying, multitasking is not executed well, my programs keep closing :/ 70-80% of the times i press the home button while im playing music+using the browser+using trillian or behive launcher pro loads the whole homescreen and widgets :/ , if switch to the browser, it reloads the websites or loads the homepage , am i doing something wrong?
i tought 256 mb wasnt that horrible for a smartphone

i blame android.
i was ok with my phone til the last week. i got an ipod touch 4g. 256mb only on that one and people complained it was a neutered iphone but damn it smokes my milestone in day to day tasks. granted it can't make a call, but im pretty pissed that android still lacks the optimization we need.

Chad_Petree said:
Im on got 2.2 but this happened to me with 2.1 too, is really annoying, multitasking is not executed well, my programs keep closing :/ 70-80% of the times i press the home button while im playing music+using the browser+using trillian or behive launcher pro loads the whole homescreen and widgets :/ , if switch to the browser, it reloads the websites or loads the homepage , am i doing something wrong?
i tought 256 mb wasnt that horrible for a smartphone
Click to expand...
Click to collapse
Same thing happened to me on 2.2 but on 2.1 it runs very smooth... Try "Keep in memory" setting from Launcher Pro --> Preferences

is there any method to optimize the ram usage of android. i thought that a milestone is better then iphone, i still think it is,but if the android system dont get better, iphone will smoke all of us in the pipe.
the first thing i noticed when i holded my milestone in my hands was, damn is it fast and brilliant, better then the iphone, the same day i started modding and overclocking and things like that. i gave him a little too much vsel, .... and since then i think it has gotten slower :/ , maybe some of you had the same expirience

Guys, please consider the fact, that google has to optimize their OS for different smartphone setups from different manufacturers ... the iOS featured in the iPhone and iPod Touch has been completely optimized on their hardware, since iOS isnt featured outside the apple family of handhelds. Because of this, the optimisation and integration is WAY more comfortable, Google has a ****load of work to do to consider the many different phones besides their nexus one.
give it time guys. MIUI handles the memory management already pretty good, runs way more responsive that stock android.

It's problem of the apps and widget you are using, download a app call system pannel, you will find out many apps and widget take up so many ram.
and 2.2 got leak have a problem which make the launcher redraw so often.
for launcher pro, there is an options to keep it in memory.

vladstercr said:
Same thing happened to me on 2.2 but on 2.1 it runs very smooth... Try "Keep in memory" setting from Launcher Pro --> Preferences
Click to expand...
Click to collapse
i just checked that option, it says its experimental tough , theres a couple of exta ptins:
memory usage preset: high,mediu,moderate,low...
homescreen cache type: normal compressed,light
Should i mess with this setings too?

Try4Ce said:
Guys, please consider the fact, that google has to optimize their OS for different smartphone setups from different manufacturers ... the iOS featured in the iPhone and iPod Touch has been completely optimized on their hardware, since iOS isnt featured outside the apple family of handhelds. Because of this, the optimisation and integration is WAY more comfortable, Google has a ****load of work to do to consider the many different phones besides their nexus one.
give it time guys. MIUI handles the memory management already pretty good, runs way more responsive that stock android.
Click to expand...
Click to collapse
piss poor excuse. there's not much rocket science going into optimizing a homescreen smoothness.
The A4 chip the iPhone 4 uses is more similar to a Samsung Hummingbird.
The OMAP chip the 3GS uses is similar to the one we have in the Droid/Milestone.
The old ARM11 chips in the 2G/3G/iPod Touch 1g/2G/3g 8gb is different too.
The fact is Apple has accounted for 3 types of CPUs and while they are all ARM architecture, it's similar to the fact we have Qualcomm, TI, and Samsung CPUs floating around. Even Google's own Nexus One is piss poor smooth on the homescreen.
Granted here at XDA we've already ROMed the hell out of our phones, but the fact that I'm still ashamed when I whip out my Milestone just to show my friends Facebook, and they ALWAYS comment on how choppy it is despite my 1100mhz overclock or whatever. I'll even reboot just before hanging out with them just in case I need to do some stuff. Android is just too freaking slow.

i am using cronos froyo 1.5 and i must say i am suprised, it is a good rom, fast and stabil,and trust me i testes many roms, maybe all?
so is there a way of modifing a rom (maybe cronos) to get rid of all the services that are not needed for a normal user? maybe it would be more ram available this way... aint it?

I think that 256 mb ram are enough. Try eclair mod v0.3b. It is very fast and i get about 110mb free ram. I use Advanced task killer and Estrong task manager. I have them both on my homescreen and when i tap them both I get 110mb ram free.

ram
the task killer is an option i dont want to use, because android should manage that him self, but maybe tere are some services that are not needed, so we can delete them, and make a slim rom. do someone know what services are not needed, and how we can wipe them?

Granted here at XDA we've already ROMed the hell out of our phones, but the fact that I'm still ashamed when I whip out my Milestone just to show my friends Facebook, and they ALWAYS comment on how choppy it is despite my 1100mhz overclock or whatever. I'll even reboot just before hanging out with them just in case I need to do some stuff. Android is just too freaking slow.
Click to expand...
Click to collapse
Ha ha I have to do that exact same thing, so embarrassing as it always happens just after I've sung praises for Android!

Yriel40k said:
I think that 256 mb ram are enough. Try eclair mod v0.3b. It is very fast and i get about 110mb free ram. I use Advanced task killer and Estrong task manager. I have them both on my homescreen and when i tap them both I get 110mb ram free.
Click to expand...
Click to collapse
On milestone? Don't believe it. Pleas post some screenshots so I can be amazed

As Milestone has really terrible hardware spec (cpu, ram, flash) I am still hoping someone would start to build ultra-lite version of the android without any non-essential services running, applications on flash, launchers, wallpapers, etc.
Regarding the multitasking - yes when I try to open second app I am holding my breath whether the first one will get killed or will survive

IMO it was depend on which rom u were used.

Try live home for launcher its pretty fast and handles multitasking
Sent from my Milestone using XDA App

Do you use any weather and clock widgets-if yes there is a option called refresh when home is pressed you disable it and your screen would come alive much faster.
Sent from my Milestone using XDA App

I have never be success on milestone, always restarting

I would say it probably more have to do with Motorola for not taking the effort to optimize Android's software for the Milestone, my friend X8 is smoother than mine despite having only 168MB(!) of RAM and he used live wallpapers too. 2.2 also for some reason seems to be very sluggish as compared to 2.1/2.3
Anyway I also believe that because of our higher resolution screen (854 x 480), more RAM is needed as more resource is needed for greater resolution and phones usually reserved more RAM (slightly) for connectivity purposes (cell tower) which lead to a "shortage" of free RAM on our milestone.
Though no doubt, I would say iOS have a slightly better memory management than Android but Android is not that bad given that the Nexus One prior to 2.2/2.3, the amount of RAM available for them is 40mb less than Milestone due to a bug but it still flies. Shows alot that effort to optimize by the OEMs matter more rather than Android itself.

[Q] Nexus one flash partition layout, lowest 63MB...

I've been trying to recover some space on my Nexus one and have been largely successful in doing so with a combination of tricks, but while looking at my partitions and tallying up the numbers something didn't seem to be adding up right; the unit is supposed to have 512MB flash, but I was coming up about 60MB short.
I found this thread which discusses the partition layout of the N1; the sizes they show all seem to match up well with what my device shows. Now, the hex address of the end of the last partion (user data) ends just a couple MB short of 512MB; the start of the first partion (misc) however seems to start over 60MB into the memory space... is there a reason for this, and if so what's occupying those lowest 63.75MB of flash space?

Baseband, AKA "radio", is what you're looking for. Unless you want your Nexus not to boot anymore, it's not advisable to try and repartition baseband space.
Instead of working hard and uselessly wasting effort, use A2SD or any other kind of linking to SD-mounted EXT partition. No matter what you try, Nexus doesn't have nearly enough internal space for any common use.

That answers my question, thank you.
As I mentioned in my original message, I was successful in freeing enough space on my device; a combination of moving apps and libraries (copy to system/lib and symlink back to original location) into the system partition and clearing out bulky or unnecessary apps has left me with over 60MB of free data space without even having to resort to fancy A2SD business (just normal android move to SD card). I was simply curious about what was filling in the remaining space on the flash chip and the radio pretty much fits the bill.

As someone with pretty average amount of user apps (a bit less than 100) and 700 MB user space taken, I can't see the point in doing what you mentioned for anything but pure fun. But if that suits you - I won't argue.

Well, by my app drawer I'm sitting at ~125 (44 purely in data, 34 moved to SD with standard android method, rest either native system or moved there) apps, and if my "puny" N1 can have 60MB free and not even need ext-style A2SD I'm not quite sure how the N1 doesn't have "nearly enough internal space for any common use". Seems to me the point (not "pure fun" as you dismissively imply) of doing what I've done is to able to keep using a pretty decent phone that still has more than enough storage space if you make the least bit of effort to manage it.
But hey, who am I to judge if you prefer to buy whatever latest phone the carriers tell you you should want every 12 months just so they can cram more bloated apps on it?
I appreciate the answer to my initial question about what's using the lowest block of flash storage (I was simply curious about what was using it - I couldn't find information if it was flash overprovisioning or some other low-level portion of the OS using it), but I don't really appreciate the unnecessary negative attitude and commentary for what was just a simple question. Thanks anyways.

I guess you didn't understand my point(s). I'll elaborate:
First and foremost, my point is this: N1 is a crap of a phone. Having it for over 1 year, and trying to adapt it to my wife for 3 or 4 months later on before giving up on it, taught me that this phone can't be dealt with by anyone who doesn't want to accept its touchscreen limitations. It was so refreshing having the phone (MT4G in my case) just react without fuss and not expecting it to crap out at any given time - not even mentioning the huge speed-up. The price of "upgrade" (selling the N1 and buying any previous-generation phone, like DHD/MT4G/DS/DZ) can be brought down to as low as $50, and the benefits are huge, I already wrote it a couple of times on the forum.
To the storage point (actually, several points):
N1's NAND is painfully slow, compared to anything, even to regular Class 2 SD card. You can try copying any large file from NAND to EXT and back, from NAND to NAND and from EXT to EXT and see what takes more time. You're likely to discover that A2SD actually adds performance instead of hurting it.
My app data (/data/data/*) alone takes roughly the same space as your whole internal /data storage has, so I guess the amount of apps alone isn't that meaningful of a measurement. I still call it a perfectly normal and average data usage - I don't have anything special installed, no heavy games that save 200+ MB of data on internal memory, just apps like Goggles, Flash, iGO and a couple of other big apps that aren't movable by normal means (and tend to crap the system out when they're forced to move). The problem in your approach is not even the one-time amount of work you had to invest to make that space, but the amount of work you'll have to invest to keep the phone running - moving system updates to /system upon every update, clearing browser cache, etc - generally, keeping things in constant check. Free time is something you learn to appreciate when you don't have enough, and more hassle-free setup is always preferred IMHO.
But again, different people have different needs, so while I can post my point of view - I don't argue with yours.

Thank you for elaborating, actually; it clarifies much that was not apparent in your earlier posts. This thread isn't really about the pros and cons of the N1 so all I'll say is that the advantages of the N1 (small size, OLED, build quality, tricolor trackball LED, etc..) still outweigh its manageable downsides for me, even compared to very modern handsets - so I'll stick with it until I can find a suitable upgrade that I'm happy with (is it so hard for HTC to make a <=4" qHD AMOLED? Seriously...).
Your point about the NAND being slow is interesting; this is something I hadn't heard and will have to benchmark; if it pans out it would be a point in favor of A2SD, but not really in favor of replacing the device over it
The upkeep I don't find that bad; Titanium backup makes integrating updated system apps a single touch for the batch, and I've only got a couple libraries symlinked into system that are unlikely to be frequently updated. With the space I've freed I shouldn't need to clear browser caches nearly as often - so it actually saves me time and frustration regularly for the one-time effort.
Thanks again for taking the time to reply and to clarify your points

If a2sd+ doesn't work for you you could do custom mtd partitions like I did using fireats custom mtd if u google it u will find it basically you can shrink ur system partition down to almost half because it is being wasted I mean whatever size u want to define it as. I'm using miui and my system partition that i defined is 120 mb (4 mbs are free just in case) and my cache partition is 15 mb. Now that leaves 301 mbs free for user data. I have 107 user apps installed about 10 games or so and I still have 120 mb free for user data for me that's more than enough. This way ur phone won't be buggy because u will only use the system partition for ur rom again I would suggest miui since it takes minimal space and is very smooth and stable with amazing battery life (I use tiamat kernel). Hope this helped
---------- Post added at 06:57 PM ---------- Previous post was at 06:52 PM ----------
Oh if u use a2sd in conjunction with custom mtd then u can have close to 750 mb of space available for user data given that ur sd ext partition is 512 mb (which was stable for me using 8gb card) that's basically rivaling new phone memory so don't just call the nexus one off just yet it can surprise anyone that knows how to play with it or stuck with it for 2years like me lol.

I've already been using root access with shell and titanium backup to move apps and libraries into the system partition without resizing it, so I'm already using the available space there. The only major difference is you've dramatically shrunk your cache partition from the default of (IIRC) 100MB down to 15MB; this seems like a pretty huge reduction, and I feel this would have performance implications, especially when running larger apps...
Other than that, if I find my current space as set up proves to be inadequate in the future (it seems just fine for now) then a2sd appears to be the best option for those who need even more additional space on a nexus one.

15 mb is more than enough for cache partition unless u plan to download huge 3d games and as we all know gaming isn't the reason that we have held on to nexus one for so long I haven't seen any app large enough to not install due to my partition size. I messed around with that too first I had it set at 5 mb but that made market force close every time then I set it at 10 was stable but large apps couldn't download and then I tried 15 and hasn't given me a single problem. Otherwise all that space is wasted so why not dedicate it to user data? With 20 mb partition u can download almost all games that can function on nexus one but since I'm not a big mobile gamer I stuck with 15 mb cache.

Most normal programs don't use /cache.
To fix your cache market issue:
Code:
su
busybox mv /cache/download /sd-ext/download
ln -s /sd-ext/download /cache/download
If you don't have a sd-ext you could use /sdcard/download instead. The directory will already exist if you've downloaded anything from the browser, so I just remove /cache/download before linking. I used to get package file invalid errors from this setup though...
Ti backup will also let you move stuff to /system and re-odex your rom instead of shrinking /system. Sure, everytime system stuff updates you need to click a few times, but unless space is real tight, it works fine. The re-odex-ed rom seems to boot faster for me than with external dalvik-cache, too, but that could just be me pretending. I've never busted out the stop-watch.
I like to keep apks on a2sd and put dalvik-cache on internal memory. It's kinda like raiding the two interfaces together to get the sum of the bandwidths of both when launching a program.
siberx: I'm sticking with the N1 until I find a decent phone that has been designed to fit in my pocket instead of sitting in a purse or on the bar too... I considered the glacier for a while, but, near as I can tell, the only benefits of going there are better touch screen and gpu.

I used firerat's mtd patch to rejigger my girlfriend's desire paritions to something more sensible (something like a 230mb system partition stock? ridiculous!) and that worked smashingly; the same trick against my N1 didn't go so well though. Seems like my Nexus with CM6.1 on it is still using the cache partition for dalvik at least partially, and I think shrinking it down to 20mb made it too small to boot right. Not a big deal anyways; I've got enough space to work with as is
I tried to do some benchmarks on my internal flash for comparsion, but the only decent benchmark I could find (without getting manual about it on command line) was Passmark's mobile benchmark; problem is they wan't 90MB free to run the internal memory benchmark, so my 60MB isn't cutting it for that
Anybody know of a decent benchmark that will bench both internal and SD read/write speeds that doesn't need such a huge chunk of free space?
ezdi: I considered for awhile buying a G2 for the faster CPU/GPU and improved touchscreen, but ultimately decided against it due to the extra weight and thickness (combined with the nexus' other advantages like OLED and tricolour LED). Eventually some manufacturer will figure out there's a still a market for compact high-end phones...

ezdi said:
siberx: I'm sticking with the N1 until I find a decent phone that has been designed to fit in my pocket instead of sitting in a purse or on the bar too... I considered the glacier for a while, but, near as I can tell, the only benefits of going there are better touch screen and gpu.
Click to expand...
Click to collapse
Better touch screen is a reason enough by itself.
GPU, much faster and bigger internal memory (both system and data), much faster and bigger RAM, and most of all - 90% HW-compatibility to one of the most popular devices in the world (DHD) - means staying updated and speedy with ROMs that fly where they crawl on Nexus (if they exist at all). Plus - all ROMs besides ICS are 100% functional, CM, MIUI, Sense 3/3.5, you name it. And if it's not enough, 20% hassle-free overclock is standard.
From quite satisfied Glacier owner.

[Q] app storage limitation data

UPDATE:
If you want to fix your low space problem on the captivate, LOOK here:
http://forum.xda-developers.com/showthread.php?t=1541942
Previous Text:
Is there an ics rom that allows all 2 gb of /data to be used for apps? It seems most of them I've tried have the same limit from recent cm7 night lies about 350 mb, before google framework starts crashing (gummy) or I get a low space warning (nostalgia).

I believe this is just something we will have to live with on ICS with our phones.

prbassplayer said:
I believe this is just something we will have to live with on ICS with our phones.
Click to expand...
Click to collapse
So here is something interesting I'm currently running AOKP m28, with ~487 Mb of apps installed.
No low space warning and no framework crashes.

scythekain said:
So here is something interesting I'm currently running AOKP m28, with ~487 Mb of apps installed.
No low space warning and no framework crashes.
Click to expand...
Click to collapse
I'm running AOKP Build 28, I have ~529mb of apps installed and I am getting the warning.
However, I haven't had any framework crashes. Also, I was able to successful restart my phone.

Hangampalli said:
I'm running AOKP Build 28, I have ~529mb of apps installed and I am getting the warning.
However, I haven't had any framework crashes. Also, I was able to successful restart my phone.
Click to expand...
Click to collapse
Yeah, I started to get the low space warning when hitting the ~ 500 MB line as well.
Here's what I've found, two types of AOSP/CyanogenMod based Roms for Cappy:
1) Gives low space warning (and as long as you don't cross that threshold) does not produce framework crashes.
2) Does not give low space warning, but produces massive framework crashes.
The problem (as I've learned from CyanogenMod forums) is the datadata partition. CM7.1 used the datadata partition for apps, and did not have the low space warning. This meant whenever you approached the 172 MB limit of datadata you ran into spectacular framework crashes.
However around nightly 11162011 they changed that, and introduced the "low space warning". This allowed about ~300 MB of apps to be installed, before datadata complained.
I bet if you look at your datadata* (I looked at mine just now) it's pretty close to full. Mine currently only has 17 MB free. I notice when I'm browsing the web with Maxthon with about 5 tabs open I get the low space warning.
I'm wondering now though if this is a relic of linking left in my system folder. Next flash I'm going to format my /system before flash and see if this behavior changes.
*To check your datadata size open a terminal (I like Android Terminal Emulator) and type "df".

You can remove the symlink betwen /datadata and /data (I think) but it will most likely make your phone anywhere from a tad slower to unusable slow. Like I said its just a limitation from our phones, at least for now.

prbassplayer said:
You can remove the symlink betwen /datadata and /data (I think) but it will most likely make your phone anywhere from a tad slower to unusable slow. Like I said its just a limitation from our phones, at least for now.
Click to expand...
Click to collapse
I figured this was what is happening. Has someone tried this and confirmed the performance hit?

I did way back when on ICSSGS 2.x and 3.x Made my phone almost unable, which means my nand isn't in good shape. But the result varies a lot so no way on telling.
I know they had a zip but doubt it will work on any other rom.
Sent from my ICS powered Captivate using Tapatalk

So last night I was performing some benchmarks after formatting system. What I found was interesting to say the least. CNA was no longer laggy. Aokp isn't as fast as it felt.
Anyways, I stuck with dark knight and currently have 560 mb installed with no low space warnings and no framework crashes.
Update:
So after installing >500 mb of apps I'm still getting low space warnings with dark knight. I ran df in my terminal and have determined that it happened when the datadata partition is at oR below 15 megs free. Wierd thing though, I was at 28 mb free, reboot come back up with 6 mb free? Moved 70 mb of apps to USB storage, and it moved up to 26 mb free on datadata.

scythekain said:
So last night I was performing some benchmarks after formatting system. What I found was interesting to say the least. CNA was no longer laggy. Aokp isn't as fast as it felt.
Anyways, I stuck with dark knight and currently have 560 mb installed with no low space warnings and no framework crashes.
Update:
So after installing >500 mb of apps I'm still getting low space warnings with dark knight. I ran df in my terminal and have determined that it happened when the datadata partition is at oR below 15 megs free. Wierd thing though, I was at 28 mb free, reboot come back up with 6 mb free? Moved 70 mb of apps to USB storage, and it moved up to 26 mb free on datadata.
Click to expand...
Click to collapse
I think right now, moving apps to SD card is the only real solution. I think the limit is near ~375ish?
So far, I've only moved games and a video player. Hopefully, they'll still work fine.
I've had this for about 2 days now, and it seems to be working. I did start having framework crashes at the end of monday, but the phone surprisingly restarted. I'm not sure how that happened (maybe the AKOP rom is stronger than I thought). I did try and move some of the bigger app's to the SD card while the phone was crashing....I thought it didn't go through, but maybe it did.
So in summary, move apps to SD card when warning pops up. And if phone starts crashing, still try to move apps to SD card, restart and hope it works?
PS...Is anyone running the nostalgia ROM? I don't think that ROM has this problem. The developer said he had something like 250 apps installed. I'm not using it currently b/c I didn't like some of the theme-ing such as that in the people app. However, the developer recently told me that I could modify the zip package with an unskinned people app. If this AKOP rom fails me, I'll go to that and update results.

Fix for low space problem on Galaxy S (Fascinate/Captivate/Vibrant)
Hangampalli said:
I think right now, moving apps to SD card is the only real solution. I think the limit is near ~375ish?
So far, I've only moved games and a video player. Hopefully, they'll still work fine.
I've had this for about 2 days now, and it seems to be working. I did start having framework crashes at the end of monday, but the phone surprisingly restarted. I'm not sure how that happened (maybe the AKOP rom is stronger than I thought). I did try and move some of the bigger app's to the SD card while the phone was crashing....I thought it didn't go through, but maybe it did.
So in summary, move apps to SD card when warning pops up. And if phone starts crashing, still try to move apps to SD card, restart and hope it works?
PS...Is anyone running the nostalgia ROM? I don't think that ROM has this problem. The developer said he had something like 250 apps installed. I'm not using it currently b/c I didn't like some of the theme-ing such as that in the people app. However, the developer recently told me that I could modify the zip package with an unskinned people app. If this AKOP rom fails me, I'll go to that and update results.
Click to expand...
Click to collapse
I've run Nostalgia as well, it's just more Samsung Bloat (From Doc's) on top of the AOKP core.
So it will give you the low space warning when datadata fills up, but largely like AOKP as long as you deal with it (Dark Knight as well) the system is rock solid.
HOWEVER there is good news for us:
http://forum.xda-developers.com/showthread.php?t=1541942
The script above SHOULD help us use more of our app storage space, while still providing the awesome speed that custom roms are known for.

scythekain said:
I've run Nostalgia as well, it's just more Samsung Bloat (From Doc's) on top of the AOKP core.
So it will give you the low space warning when datadata fills up, but largely like AOKP as long as you deal with it (Dark Knight as well) the system is rock solid.
HOWEVER there is good news for us:
http://forum.xda-developers.com/showthread.php?t=1541942
The script above SHOULD help us use more of our app storage space, while still providing the awesome speed that custom roms are known for.
Click to expand...
Click to collapse
So after a month of running the "datadata" fix:
I have about 700 MB of apps installed with no framework crashes, no low space warnings (AOKP B32 / Glitch).
Datadata consistently has about 80 MB available. at it's current rate of increase when installing new apps, it's possible this configuration would allow the complete 2 GB usage of the data partition.

6Gb RAM utilization option

Just a thought about memory utilization....
So Oneplus 3 is the first mainstream (not the first overall) android phone with 6Gb. Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones. There is really no point in wasted RAM. Having a lot of open apps in memory is truly great and could be the best use for it, but it also can present some issues. Background apps on android are not always suspended in the best way and can waste resources (CPU, battery). Of course if app and system are optimized correctly this shouldn't happen, but unfortunately it is not always the case. While google optimizes the system with dose features etc, I'm wondering about a simpler option until the better one is built into the system.
RAM is 10 times faster than storage, so why not use a portion of it as a RAMDISK, like in old days (MS DOS times). For those who don't know, RAMDISK is a portion of RAM that is used as a temporary storage (like flash memory), that will be 10 times faster than permanent flash storage.
Basically out of 6Gb RAM that phone has (Oneplus 3), 3Gb would be used as regular RAM and 3GB would be used as a RAMDISK. RAMDISK completely looses all the data after reboot, but the good thing is that phones don't really need to be restarted often. So RAMDISK would be almost permanent. Lets say you have 100 apps on your phone. Out of those you use 30 all the time. It is a bit inconvenient when app that you use often (for example Facebook) is kicked out from the memory and has to reload from flash storage (slow). Instead you could have those 30 apps to be loaded/copied/synchronized to the RAMDISK during initial boot. If app is kicked from regular RAM and needs to be restarted/resumed it would load 10 times faster from the RAMDISK. During regular intervals and before reboot data/cache from RAMDISK can be permanently saved (synchronized) back to the flash storage. If you have your favorite app that keeps misbehaving in the background (uses too much CPU, doesn't let phone to go into deep sleep and kills battery) you can just have it removed from background processes (swipe away, greenify, kill it etc), but then it will be almost instantly reloaded from RAMDISK when you need it later. So in the end you would have all your favorite apps loading super fast, even if it is not currently running in the background. You would sacrifice some RAM for faster app loading, possibly also minimizing battery loss due to some bad apps.
My knowledge of Android system is very limited and I might be very mistaken regarding this option, it's implementation and benefits. I would love to hear what people with better knowledge can say on this topic.

Droff said:
Just a thought about memory utilization....
So Oneplus 3 is the first mainstream (not the first overall) android phone with 6Gb. Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones. There is really no point in wasted RAM. Having a lot of open apps in memory is truly great and could be the best use for it, but it also can present some issues. Background apps on android are not always suspended in the best way and can waste resources (CPU, battery). Of course if app and system are optimized correctly this shouldn't happen, but unfortunately it is not always the case. While google optimizes the system with dose features etc, I'm wondering about a simpler option until the better one is built into the system.
RAM is 10 times faster than storage, so why not use a portion of it as a RAMDISK, like in old days (MS DOS times). For those who don't know, RAMDISK is a portion of RAM that is used as a temporary storage (like flash memory), that will be 10 times faster than permanent flash storage.
Basically out of 6Gb RAM that phone has (Oneplus 3), 3Gb would be used as regular RAM and 3GB would be used as a RAMDISK. RAMDISK completely looses all the data after reboot, but the good thing is that phones don't really need to be restarted often. So RAMDISK would be almost permanent. Lets say you have 100 apps on your phone. Out of those you use 30 all the time. It is a bit inconvenient when app that you use often (for example Facebook) is kicked out from the memory and has to reload from flash storage (slow). Instead you could have those 30 apps to be loaded/copied/synchronized to the RAMDISK during initial boot. If app is kicked from regular RAM and needs to be restarted/resumed it would load 10 times faster from the RAMDISK. During regular intervals and before reboot data/cache from RAMDISK can be permanently saved (synchronized) back to the flash storage. If you have your favorite app that keeps misbehaving in the background (uses too much CPU, doesn't let phone to go into deep sleep and kills battery) you can just have it removed from background processes (swipe away, greenify, kill it etc), but then it will be almost instantly reloaded from RAMDISK when you need it later. So in the end you would have all your favorite apps loading super fast, even if it is not currently running in the background. You would sacrifice some RAM for faster app loading, possibly also minimizing battery loss due to some bad apps.
My knowledge of Android system is very limited and I might be very mistaken regarding this option, it's implementation and benefits. I would love to hear what people with better knowledge can say on this topic.
Click to expand...
Click to collapse
Never mind, wrong post.

gee2012 said:
Did you read this http://www.xda-developers.com/how-t...-management-almost-double-the-apps-in-memory/.
Click to expand...
Click to collapse
It is not about fixing the number of apps that can be held in memory, it is about different use for the RAM. When you have 40 apps in the background some of them can kill the battery. That is probably why Oneplus limited the number of apps. RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.

Droff said:
Did you read the post? It is not about fixing the number of apps that can be held in memory, it is about different use for the RAM. When you have 40 apps in the background some of them can kill the battery. That is probably why Oneplus limited the number of apps. RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.
Click to expand...
Click to collapse
I corrected my post didn`t i?

gee2012 said:
I corrected my post didn`t i?
Click to expand...
Click to collapse
I wrote reply while you did the correction. I think it is good to leave my reply there anyways, in case if someone else misreads the topic. Let me know if you think otherwise.

Droff said:
I wrote reply while you did the correction. I think it is good to leave my reply there anyways, in case if someone else misreads the topic. Let me know if you think otherwise.
Click to expand...
Click to collapse
Its cool

Droff said:
Apparently all that memory is not currently utilized. Most likely it is not fully utilized even on 4Gb phones.
Click to expand...
Click to collapse
Could you explain further why you think it is not being utilised ?

Droff said:
RAMDISK could potentiality minimize the battery wasted by background apps (if they are not suspended correctly) by removing them from active memory and still allow fast restart when needed.
Click to expand...
Click to collapse
Android can not address any RAMDISK, it just makes no sense here.

One Twelve said:
Could you explain further why you think it is not being utilised ?
Click to expand...
Click to collapse
Look at the amount of free RAM in average use. There will be plenty that is unused. Keeping lots of apps cached is the best use for the free ram, but in some cases those background apps need to be removed from the active memory to prevent app from keeping device awake (and killing battery as a result). For example RAMDISK would allow to greenify all the bad written apps, stopping them from draining the battery, but then reloading them back to the active RAM almost instantly (much faster than from flash storage), when user wants to access the app again.
This situation (RAM "waste") can sure change with advances in android system itself, but as of now I just think RAMDISK is not a bad option for new devices with a lot of RAM onboard. Apparently we will see android phones with 8Gb Ram pretty soon.
dragon-tmd said:
Android can not address any RAMDISK, it just makes no sense here.
Click to expand...
Click to collapse
There is no such thing currently, but it doesn't mean that it cannot be created (at least in my understanding) and implemented via kernel or just an application (background service).
Here is info from WiKi
https://en.wikipedia.org/wiki/RAM_drive
Here are the examples of programs/apps for PC:
http://www.radeonramdisk.com/software_downloads.php
http://memory.dataram.com/products-and-services/software/ramdisk
Here some more info:
http://www.pcworld.com/article/260918/how_to_supercharge_your_pc_with_a_ram_disk.html
Plenty more can be found online.

I remember we used to do that on the HD2 - it was pretty cool!

blackalice said:
I remember we used to do that on the HD2 - it was pretty cool!
Click to expand...
Click to collapse
Pity it was just Windows Mobile OS.

Droff said:
Look at the amount of free RAM in average use. There will be plenty that is unused.
Click to expand...
Click to collapse
The impression i got that was not all that ram was not available and was reserved for the system. To the point one questioned that 6GB was available, felt like less.
How much RAM does the OP3 mention as free after a restart ?

One Twelve said:
The impression i got that was not all that ram was not available and was reserved for the system. To the point one questioned that 6GB was available, felt like less.
How much RAM does the OP3 mention as free after a restart ?
Click to expand...
Click to collapse
It shows about 4.5Gb free. I'm yet to fully test OP3 and see my average memory usage, but I doubt that I will have less than 2Gb free

Droff said:
It shows about 4.5Gb free. I'm yet to fully test OP3 and see my average memory usage, but I doubt that I will have less than 2Gb free
Click to expand...
Click to collapse
4.5GB free implies its working as stated.
You're saying in use that memory gets reserved and drops, that is more than it should.

Do u have any ideas how can that be done?
Sent from my HTC 10 using Tapatalk
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
That would be really cool
Sent from my HTC 10 using Tapatalk

Xperia U Lover said:
Do u have any ideas how can that be done?
Sent from my HTC 10 using Tapatalk
---------- Post added at 01:55 PM ---------- Previous post was at 01:55 PM ----------
That would be really cool
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
As far as I know, there is no RAMDISK app for android at this time. I would love try it out myself. Unfortunately I don't have much coding experience to create this app (or kernel).
On a side note, after more time with a 6Gb phone I can see that this RAM can get utilized quite a bit. After editing the build.prop to magical number 42 and running bunch of apps (regular operation, nothing really extreme), the free cache reported by OS (developer options) is 1.2GB - 1.3GB. at the same time in RUNNING SERVICES it shows 2.8GB free. SYSTEM got bloated to 2.0GB
From what I can see, the apps that I use didn't misbehave so far and even with such heavy load on RAM, my battery didn't take a hit. As a matter of fact I'm very surprised by battery performance so far, but I'm only 1/4 way through.
That being said, I would still love to create 2Gb RAMDISK from that 6GB and play with it more.

Man your battery life is really good!
Sent from my HTC 10 using Tapatalk

Actually, my RAM is well used and i am grateful for having 6 GB in the phone, that is, because i am using two profiles and on 4GB phones they were always operating at the limit. with the oneplus 3 finally this is over.
Praise the lord.

RAM always at 70% on MI5

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.