Related
Hi all
I very much doubt this post belongs here, but since i am a new member , have no chice but to put it here.
I have recently accidentally purchased a nexus7 (grouper) and decided to try some of the custom roms available, in the end i tried most of them.
Here are my comparison results.
As with all things putting an "order" on the roms is subjective, the "best" rom is the one that works for the individual,with that individuals particular needs and wants.
As an embedded design engineer i am obsessed with speed and efficiency, memory usage, putting as much data on the screen as possible, then finally compatibility and lack of bugs ( in that order ), my results are biased by that order.
Disclaimer........
1) Ok i know that android is not exactly ideal if looking for an efficient well written os ( who the F came up with the idea of running everything in a VM!!! a minimal linux system will run in 85 mb ram with a full xserver, android STARTS at 400mb+, sitting there doing nothing !!!, thats near my cut down windows7 running on an i7 ) but before a decent linux distro is ported to full touch am stuck with it
2) For the N7 the requirement to change the DPI is essential, it is VERY stupid that the os does not check and change this automatically, otherwise its like having your 1920x1080 monitor stuck on 1200x600 permanently, very stupid !!! So am assuming the roms without this facility will function at 160dpi correctly, i have not been able to check this for every rom
All roms were flashed by TWR ( latest ), wipe of cache, dcache, factory reset, system
Memory was checked by settings>apps>running , immediately after first boot, then after a clean reboot, then after a cache,dcache wipe and clean reboot
IMPORTANT NOTE.....
Google apps ( gapps)...... in terms of memory usage gapps is the worst peice of #%%#%%$#$% sh$%^%$%t bloatware i have ever encountered in my os experience ( and given that i spend most of my time in windows, that saying something ).
On any of the roms i have tried flashing gapps adds at LEAST 150mb of unneeded memory usage, and depending on the rom that can go up to 250mb. Even using a minimal gapps with only phonesky,framework,login and setup, still produces a significant 50+mb hit, unfortunately in many cases some of gapps is essential, and some os functions are broken without at least the framework.
This situation seems unacceptable to me, all the roms should function correctly without gapps, and without the bloat, if some dev does not address the situation i will.
1) Prime Grouper D03-06
Tablet ui...... yes
DPI changer ...yes
Size custom nav bar ....yes
Speed....... good
Response ... good
This is first on the list for 1 good reason, memory usage!!!
Before flashing any kind of gapps
First reboot 360mb
Second reboot 320mb
Cache wipe reboot 270mb
Subsequent reboots 266mb ( stable )
Obviously team Vanier know their sh**t, their os is running in nearly HALF the memory space of other roms , and on the whole with few bugs, but whats really impressive is the memory usage is incredibly stable for a android os, zero memory leaks, leave the device at 302 mb ( say you opened an app and it was cached etc ) for 24 hours check again and lo and behold its still roughly 320mb ( obviously internal processes are moving this number a little but only by <>5mb ), this is not the case with stock rom or many other custom roms.
Everything is not all roses though, using prime without flashing gapps at all, exposes quite a few bugs, notification panel does not work at all, clock settings is broken, a few apps fail ( mx player fails for a start ) and others.
Flashing a super minimal gapps, fixes most of the issues, notifications are back, a lock screen turns up, all the settings appear fixed, BUT it also knocks out vanires keybord and totally ruins the memory handling
After flashing "micro" gapps ( and going through setup, adding valid account etc )
First reboot 430mb
Second reboot 360mb
Cache wipe reboot 320mb
Subsequent reboots 360mb ( NOT STABLE, can vary up to 400mb+ with time )
Obviously would love to see PRIME fix the outstanding bugs, and produce a custom set of gapps apk's that dont screw this fine rom.
2) Smooth ROM v5
Tablet ui...... yes
DPI changer ...no
Size custom nav bar ....yes
Speed....... good
Response ... excellent ( the best )
Gapps are included
First reboot 470mb
Second reboot 4200mb
Cache wipe reboot 400mb
Subsiquent reboots 440mb ( NOT STABLE can go 500mb+ )
This rom is second due to a totall lack of bugs, after much mucking around i can not find a single setting or feature that does not work correctly, plus the UI is very very responsive, the best of all i have tried. It would be top but for the lack of a DPI change option and the fact that memory usage is nearly double that of PRIME.
will post the other 20 odd results later
What's more interesting is that identical apps on the galaxy S3 take up 2-3 times more memory. 1GB is fine on the N7 but you have to do a lot of fiddling to get the S3 running with 1GB. Must be down to the Tegra architecture. Smooth 5 runs great on the N7 (especially with greenify app)
Sent from my Nexus 7 using XDA Premium HD app
3) Cookies_Cream-1.3.1
Tablet ui...... yes ( built in as standard )
DPI changer ...yes ( 160 dpi native )
Size custom nav bar ....yes
Speed....... ok
Response ... ok
Before Gapps
First reboot 560mb
Second reboot 560mb
Cache wipe reboot 560mb
Subsequent reboots 560mb ( stable )
Although a memory hungry beast this rom is optimised for the n7 resolution AS STANDARD, you get full true tablet ui, AND with the PARANOID ANDROID framework, it is ultimately compatible with any app at any resolution, and best of all it all works!! no bugs that i can see, although memory use is very high at least it is quite stable before gapps.
If you want the full tablet experience out of the box then consider this.
I have not tried a memory test after gapps, 560 was too high for me without gapps let alone with
4) BeatMod_CrystalClear_v2.3.zip
Tablet ui...... yes
DPI changer ...no
Size custom nav bar ....yes
Speed....... good
Response ... good
Gapps are included
First reboot 480mb
Second reboot 4100mb
Cache wipe reboot 400mb
Subsequent reboots 440mb ( NOT STABLE can go 500mb+ )
being pure CM10 this one is very different in style to the AOKP based roms, but is almost identical to smooth rom in terms of memory usage, although less responsive, on the up side is packed full os sound enhancing mods and an upgraded bravia engine for video
the rest are in no particular order
gsw5700 said:
What's more interesting is that identical apps on the galaxy S3 take up 2-3 times more memory. 1GB is fine on the N7 but you have to do a lot of fiddling to get the S3 running with 1GB. Must be down to the Tegra architecture. Smooth 5 runs great on the N7 (especially with greenify app)
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
jesus am wandering how 512k devices ever ran !!!, android MUST have gotten a lot more bloaty since the 2.x days, otherwise nothing would have worked !!!
jubei_mitsuyoshi said:
jesus am wandering how 512k devices ever ran !!!, android MUST have gotten a lot more bloaty since the 2.x days, otherwise nothing would have worked !!!
Click to expand...
Click to collapse
You got it! There's a huge difference between the gingerbread days and now, i remember when my droid eris would use 200 megs of ram for the OS, now.....its a lot more. Why do you think new devices are getting 2gigs of ram, I'm guessing key lime pie will only use more and more memory to give us a better experience
Sent from my Nexus 7 using xda app-developers app
Triscuit said:
You got it! There's a huge difference between the gingerbread days and now, i remember when my droid eris would use 200 megs of ram for the OS, now.....its a lot more. Why do you think new devices are getting 2gigs of ram, I'm guessing key lime pie will only use more and more memory to give us a better experience
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hmm have to take your word on better experience having just come to android.
PRIME runs at 266mb without gapps, thats a bloody good number for android, just needs the bugs fixed and a minimal/mico ( just playstore functionality, without the paid service ) gapps integrated so all the settings etc function, then we are talking as good as it gets with android.
Generally if you want something doing do it yourself but in this case am in the middle of becoming proficient in c/c++ ( again , its amazing when buried in hardware, pcb design, spice sims, matlab etc etc that one can just forget how to code, i always thought it would be like riding a bike WRONG! ) so learning java from scratch is out for at least 6 months, am very much in hope that PRIME does it for me ,
Before you go any further you should define exactly what you mean by "memory usage".
I challenge you to correlate your "memory usage" statistic to anything you can find in /proc/meminfo.
Go ahead, give it a try.
In any modern OS - including Android - 100% of DRAM is in use. The only thing which remains is some quibbling about whether you should give up file cache space for process memory space or kernel private memory, and the answer to those questions always depend on the nature of the workload.
The whole of dalvik is built on top of native shared libraries that are substantially smaller than the totality of shared libraries present in (let's say) a recent Linux distro. They can be memory mapped in copy-on-write or read-only fashion to a large number of process spaces, and so in fact it is a strategy of the "system_server" process to preload most of them. That way new activities spring to life quickly, rather than being required to demand-load and link everything from scratch.
Bottom line: it is an intentional strategy of android to "use up memory" right from the get-go. Most of that "used memory" is shared libraries that are mapped into activities as they come and go.
So, would I want to run engineering applications that require 800 MB of heap space on an android OS tablet with 1 GB of RAM? The answer is clearly "no" in that case, but mostly because Android devices are not targeted for that kind of work.
For comparison, BTW, my Win 7 x64 box that is nearly bare of applications (I only use it as a VM host) needs 1 GB of committed page space to sit there and do nothing. Android isn't doing so badly in comparison.
cheers
bftb0 said:
Before you go any further you should define exactly what you mean by "memory usage".
I challenge you to correlate your "memory usage" statistic to anything you can find in /proc/meminfo.
Go ahead, give it a try.
In any modern OS - including Android - 100% of DRAM is in use. The only thing which remains is some quibbling about whether you should give up file cache space for process memory space or kernel private memory, and the answer to those questions always depend on the nature of the workload.
The whole of dalvik is built on top of native shared libraries that are substantially smaller than the totality of shared libraries present in (let's say) a recent Linux distro. They can be memory mapped in copy-on-write or read-only fashion to a large number of process spaces, and so in fact it is a strategy of the "system_server" process to preload most of them. That way new activities spring to life quickly, rather than being required to demand-load and link everything from scratch.
Bottom line: it is an intentional strategy of android to "use up memory" right from the get-go. Most of that "used memory" is shared libraries that are mapped into activities as they come and go.
So, would I want to run engineering applications that require 800 MB of heap space on an android OS tablet with 1 GB of RAM? The answer is clearly "no" in that case, but mostly because Android devices are not targeted for that kind of work.
For comparison, BTW, my Win 7 x64 box that is nearly bare of applications (I only use it as a VM host) needs 1 GB of committed page space to sit there and do nothing. Android isn't doing so badly in comparison.
cheers
Click to expand...
Click to collapse
Hmmm
Well lets start with the last first, i run a heavily customized ( rt7 lite, wintoolkit, buclean ) windows 7 ( EE edition which i mastered ) on a asus g15w i7 8 gb geforce 470 , with all drivers in, on full aero , <>560mb mem usage for the system, can go down to 500 if you disable the nvidia startups and services but you lose the nvidia controll panel.
I totally take the point that memory usage in modern multi-core systems is friggin complex, obviously these memory stats are not supposed to be definitive in any way, but given all the tests are run on the same hardware with the same inbuilt prog they can be used as COMPARATIVE results, ie you can say rom x is more efficient than rom y given they do the same thing but with different memory results.
By definition any code abstraction away from 1's and zeros makes that code less efficient, an entire graphical os can fit into 1.8mb if written in x86 ASM, same code becomes <>20mb in C, 25mb in C++, 80mb+ in vm bytecode, the same pattern can be found in mem usage.
Any virtual machine no matter how clever ( and dalvik is bloody clever ) is a glorified interpreter, hence slower ( by a few factors ) than c/c++, which is itself slower by a few factors than ASM.
My opinion on caching is DONT, unless someone comes up with a really psychic piece of code that can for real predict the chaotic needs of the average human, all caching algorithms are just guessing, and do i trust the system to free up all that memory in time when something ( as you say ) calls up a massive heap or worst maloc's it direct, errrr no.
But thats just an opinion, am totally willing to recant if i see evidence and accurate benchmarks to the contrary ( and you seem to know your stuff, so if im way of the mark please enlighten me ! )
Hi ,
I have andorid right now , and looking forward to buy an windows phone 8.
i have android having 512 mb ram. im looking forward to buy Nokia lumia 520. also have 512 ram.
i want to know how much the windows phone allow to use ram. will all apps will work on it like on android. doesnt matter , i only want some apps like viber , whats app and fb to work in background.
Should i buy ram 512 mb phone ?
shanalikhan said:
Hi ,
I have andorid right now , and looking forward to buy an windows phone 8.
i have android having 512 mb ram. im looking forward to buy Nokia lumia 520. also have 512 ram.
i want to know how much the windows phone allow to use ram. will all apps will work on it like on android. doesnt matter , i only want some apps like viber , whats app and fb to work in background.
Should i buy ram 512 mb phone ?
Click to expand...
Click to collapse
if "to work in background" means you want to get push notificiations then: yes and no. windows phone 8's push service is a mess, even if your phone had 512GB of RAM, facebook won't push anything.
Eh? The WP7 version of Facebook did push just fine with 512MB. Not sure about the WP8 version but it *could* work.
Facebook and Twitter and so on will do their integration thing just fine without apps or push notifications anyhow.
With that said, there are definitely apps that won't run on 512MB WP8 devices, but not many, and they're mostly the really big fancy graphically intensive games that the Lumia 520's CPU/GPU would probably struggle with anyhow (not sure if you're aware, but it's basically the entry-level WP8 device).
GoodDayToDie said:
Eh? The WP7 version of Facebook did push just fine with 512MB. Not sure about the WP8 version but it *could* work.
Click to expand...
Click to collapse
The push service of the facebook app was (and still is) a horrible mess. It generally worked, with the exception of message notifications. I never received any message notifications at all, only if someone liked my status, posted in a group etc. Those worked reliable, though.
i heard the in Wp8 , developers are more attracted to set 1GB rams for ther applications. later on they set to 512mb.
so should i buy wp8 with 512mb ? will it run about 85-90% apps ?
512ram on WP8 is like 1gb ram on android its not like android when you run apps just press back until it gets to homescreen and it close all process and it didnt get slow!
how many apps in market is able to run on wp8 , can you estimate , 60% , 70% or 90%
I have htc explorer right now and its working fine on 512mb
Probably well over 90% of apps will run on 512MB phones. The 1GB restriction is mostly only present for high-end games.
There were a few instances of regular Apps not being able to work on 512 MB devices but those got fixed in an update quickly and mostly affected Apps just updated from WP7 to an optimized WP8 version and that had opted out of 256 MB devices on WP7 (so I suppose they forgot to take the limit entry out - it meant "no 256 MB devices" in WP7 but in a WP8-App the same entry limits it to 1 GB devices). Aside from that as has already been said it mostly affected games and quite a lot have been updated to work on 512 MB as well (Asphalt 7 and Temple Run are 2 notable examples).
As for background processing. 180 MB is the maximum a WP8 App may use on 512 MB devices (it was limited to 90 MB max on WP7). There is a set amount of background tasks that can be configured to run that is dependent on the device but regularly scales with the amount of memory available. Apps that are not in the foreground are dormant and are removed from memory if a more recently used App requires the memory. Many Apps like WhatsApp do employ the push service which does not require the actual App to run in the background so those aren't affected by the limitations outlined above.
Phone 8
WP 8 handles less RAM better than Android. This correspondes to the better optimation of the OS.
our moto g 2 has 851MB of usable ram (1GB fisical, about 150 MB is occupied by the OS...right?), and i have about 280-320 MB of free Ram with a normal use, sometimes there are only 220 MB so the phone go laggy
opening "advanced task manager" i see that in backgrund there are Nova Launcher (41 MB), Whatsapp (55), Google Search (23), Google Keyboard (33 MB), Play store (15) and other 5 apps that occupy in total 20 MB...so all the apps named now occupy in total about 220MB
I've also a nexus 7 2012, that has at least 480 free MB, but sometime over 550
why these devices are so different? the nexus 7 doesn't have the phone function but the difference is too high!
my friend has a cubot with 1GB of ram, normally 450-500 free...
has my phone something wrong?
PS:sorry for my english, i'm italian and I don't speek/write it very well
PPS:it's the first message of this account but i've another account but i forgot the password of it and also the password of his email :/
In my moto g 1st gen i always have 400 plus ram now in 2nd gen my free never go above of 250 even I disable all Motorola app which run in background.btw same app installed in both phone.I have to say multitasking is poor then 1st gen.
maybe with the next updates they will fix this issue...or maybe with a cyano
I am on 21.11.23 thuis is screenshot from memory
Sent from my XT1068 using XDA Free mobile app
i opened another thread about the ram, because i found a strange bug about the ram
you find it there
when you open the camera it occupy 80MB, but when you close it the 80MB remains in the ram so you have less free memory until you restart the device.
Have you guys checked how much Motorola bloatware are in the RAM?
1. Motorola notification
2. Audio Effects
3. MotoCare
4. Emergency Alerts
It all takes up precious RAM.
CANADOS said:
Have you guys checked how much Motorola bloatware are in the RAM?
1. Motorola notification
2. Audio Effects
3. MotoCare
4. Emergency Alerts
It all takes up precious RAM.
Click to expand...
Click to collapse
Any idea, what does Motorola Notification do?
check how much ram the camera take, simply boot the phone, check how much free ram do you have, next open the camera, close it and check how much ram do you have....it takes about 80MB even if it is closed.
impressive....
Lets hope they will fix it with Lollipop... or flashing a custom rom like cm 11
with normal usage free ram is 320-330 MB
With Greenify root and closing all I have between 300-400 MB of free RAM
Im using:
ROM: Andro X
Kernel: Furnace-1.1.0
Mod: Nitro X 4.1
I had the Honor 7, it couldn't keep background apps open at all. I returned the phone quicker than you can say memory management.
How's the P9 about that? My current LG can keep background apps open for more than a day.
First to say it is depending on your usage. If you frequent a lot of apps during the day it is likely and also necessary that some will be killed on every phone! For me the P9 seems to be a little more aggressive than my old Z3 with the sony concept rom, but still ok. It uses about 2 GB of RAM on average, whereas the Z3 used 1.5 GB. I think this is due to EMUI whereas the Z3 was nearly Stock Android.
it's not ram management issue , it's a software feature . you can choose which application to keep running from battery settings , protected application
EMUI is way better than MIUI in terms of memory management. Plus, you can always lock important applications that you don't want the OS to kill.
Howdy people-who-already-have the Mi 9 Lite. I don't want to bore you with the details, so I'll try to keep it short. I bought a Xiaomi Mi 9 Lite for my wife and, in the meantime, managed to bork my OnePlus One. Now, I, too, I'm in the market for a new phone.
From the little I played with her new phone, I love the device, and I'm thinking of picking one up too, as a replacement for my OnePlus One. I have two problems, though:
1. Everything on the screen is too small for my failing eyesight. I enabled the developer settings and tried increasing the DPI, but that ended up screwing how some of her apps look. Is there any other way, apart from the provided one in the "official" settings, to increase the text size? By "official settings" I mean "not the developer options", but the setting for text size somewhere in the Display group of options, that offers three possible steps for the text size. All of them too small for me. And by all of this, I mean only the text size since the DPI option in the developer settings affects everything.
2. Since I am "a more demanding user" (compared to my wife), I am torn between this and the Poco F1. Although the Mi 9 Lite is a newer device, the Poco F1 seems to have a vastly better processor, GPU, as well as lots of love and support over here. I don't really care if the screen is somewhat worse, nor use the camera too much, so I was ready to buy this instead of the Mi 9 lite. Mere minutes before taking the plunge, I saw a video by Linus Tech Tips, where he was talking about how you can install gCam, root it, etc. And he suggested "using the nano version of open Google apps". This started ringing alarm bells: the reason for upgrading my wife's phone was its restricted internal storage. We had reached a point where I was removing system apps to be able to update Gmail and Facebook from the Play Store. Is this also a problem in newer phones like the Poco F1 and the Mi 9 lite? I mean, if you already have to use the nano version of open Google apps in a one-year-old smartphone, then what will we be using one or two years from now, when android itself will have grown a lot bigger?
I am sorry if those questions have already been answered, I did a quick search but I didn't run into anything relevant.
You can find display size option in settings/additional settings/accessibility
Sent from my MI 9 Lite using Tapatalk
The problem with space for app updates is in devices with 8gb of flash. The cheapest mi 9 lite has it 8 times more. Do you believe , it will be not enough during next 10 years? Remember about card slot. You can keep all pictures and recordings on external memory.
Tomek0000 said:
The problem with space for app updates is in devices with 8gb of flash. The cheapest mi 9 lite has it 8 times more. Do you believe , it will be not enough during next 10 years? Remember about card slot. You can keep all pictures and recordings on external memory.
Click to expand...
Click to collapse
I believe what's relevant to the OP is the system partition and not the user storage. When using stock GApps, you need to have a large enough partition for the apps installed on that partition to update correctly. Before the Mi 9 Lite I owned a OnePlus X which had 16gb of total storage. I had no problems installing stock GApps over LOS 15, but after around a year of updates I started to get the "low storage" error even though I had more than 6 gb available (which was fixed with a reboot after every system app update, presumably due to the cache being cleared). I doubt that the Mi 9 Lite would have the same problem any time soon though, as the system partition is probably much larger than that of the OPX.
I used galaxy tab 4 with 8GB of flash with 1.7GB of free flash and 80GB of applications installed on second partition. There was not problem to have hundreds applications installed in device with 8GB flash. The only to do was take care to not let start not needed apps on boot and let them to be in ram. I replaced it with mi pad 4 because of a7 core in galaxy.
If you have 64 or 128 GB build in , you are able to install thousands applications. The only limitation will be card size.
Tomek0000 said:
I used galaxy tab 4 with 8GB of flash with 1.7GB of free flash and 80GB of applications installed on second partition. There was not problem to have hundreds applications installed in device with 8GB flash. The only to do was take care to not let start not needed apps on boot and let them to be in ram. I replaced it with mi pad 4 because of a7 core in galaxy.
If you have 64 or 128 GB build in , you are able to install thousands applications. The only limitation will be card size.
Click to expand...
Click to collapse
You're conflating the system partition (where the android framework resides, including the system apps such as GApps) and userdata partition (where apps are installed after the fact, like from the Play Store). You could theoretically have, say, a 512gb device with a 1 TB sdcard installed in which you can install all the apps you'd ever want but the system partition will always be limited to just a few GB.
There are ways to increase the storage allocated to the system partition (this is Android after all), but it requires a bit of tinkering.
In short, yes, a device with 8gb of storage is enough to download plenty of apps, but will not be enough to hold Android 10 (~1.5gb for the OS + ~700mb for stock OpenGapps + storage reserved for any updates) if the system partition on that device is 2 gb.
SpaceDye said:
In short, yes, a device with 8gb of storage is enough to download plenty of apps, but will not be enough to hold Android 10 (~1.5gb for the OS + ~700mb for stock OpenGapps + storage reserved for any updates) if the system partition on that device is 2 gb.
Click to expand...
Click to collapse
Theoretical yes. I thought about it with galaxy and decrease system partition for make data partition larger. It was not possible because of not existing custom kernel for galaxy. Do we have custom kernel for mi 9 ? If yes, resizing partition will be possible. But I do not think we need it anytime. Custom rom creator is able to modify partitions in flashing time or use other partitions size for own needs. The gapps will never be problem. Much better is to install nano or pico and add needed other google apps from play store to data partition.