Hi,
I have discovered that building a boot.img with a standard Image (instead of zImage) works out of the box. Booting time is (apparently, I didn't notice) a little slower since copying the full image to RAM is slower than decompressing the gzipped original.
Reference: http://free-electrons.com/blog/uncompressed-linux-kernel-on-arm/
Next task is modifying the kernel boot code to directly access the kernel rather than copying it to RAM, or something similar. I was thinking (rather, wishing) that using uncompressed Image would automagically give us a few extra MB of RAM capacity since it doesn't need to allocate any memory for both the compressed image and uncompressed Image.
Though I'm stuck on trying to find the code in the arm kernel (boot process) that I can play with. I've been reading this as a reference - ARM Linux Boot Sequence
Any help/ideas? Cheers!
P.S. I run an Xperia Play that is 512MB but only 362MB available in userspace, hence why I'm so determined to experiment with this. Getting an extra few MB would really help
To be executed the kernel must reside in RAM. Uncompressed or compressed the final size is the same as it will end up uncompressed in RAM.
Sent from my GT-I9100 running CM10
MemoryController said:
Uncompressed or compressed the final size is the same as it will end up uncompressed in RAM.
Click to expand...
Click to collapse
Yes but the zImage must be copied to RAM, then the zImage is decompressed to another RAM block. The ARM boot sequence says nothing about deleting/freeing the original zImage copied to RAM once decompressed. That's my main question, where do I check in code for this kernel decompression process.
Of course it gets deleted
Sent from my GT-I9100 running CM10
MemoryController said:
Of course it gets deleted
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
How do you know that? It's not always the case. And why must it only be executed from RAM? How can I find how much dynamic RAM the kernel allocates using a compressed vs uncompressed image? Is it possible to use XIP and DRIP in Android like other ARM Linux?
Nevermind, I've found everything I need right here - http://elinux.org/Kernel_Size_Tuning_Guide
EDIT and here - http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html
CosmicDan said:
How do you know that? It's not always the case. And why must it only be executed from RAM? How can I find how much dynamic RAM the kernel allocates using a compressed vs uncompressed image? Is it possible to use XIP and DRIP in Android like other ARM Linux?
Nevermind, I've found everything I need right here - http://elinux.org/Kernel_Size_Tuning_Guide
EDIT and here - http://www.simtec.co.uk/products/SWLINUX/files/booting_article.html
Click to expand...
Click to collapse
Well xip/drip would require nor flash and I don't think any phone has nor flash. Good thinking though
Sent from my GT-I9100 running CM10
MemoryController said:
Well xip/drip would require nor flash and I don't think any phone has nor flash. Good thinking though
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Yeah after reading more about it it's probably a dead end lol.... but I'm keen to squeeze out a tiny bit more RAM and will explore other options in compiling the kernel. The Xperia Play only has 344MB available to the user disabling 720p recording pushes that up to 362MB but I'm looking for more things to try.
CosmicDan said:
Yeah after reading more about it it's probably a dead end lol.... but I'm keen to squeeze out a tiny bit more RAM and will explore other options in compiling the kernel. The Xperia Play only has 344MB available to the user disabling 720p recording pushes that up to 362MB but I'm looking for more things to try.
Click to expand...
Click to collapse
Have you considered compcache? It won't actually increase RAM size but it will give you some ultra fast swap
Sent from my GT-I9100 running CM10
MemoryController said:
Have you considered compcache? It won't actually increase RAM size but it will give you some ultra fast swap
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Yeah I've got a ZRAM script in there using 10%, considering the Xperia Play can do 1.5GHz stable I have considered experimenting with higher percentages and swappiness values and doing benchmarks/real use tests. But that takes a lot of time, I'll fine tune that another time.
EDIT: I wonder if it's possible to use 100% zram with swappiness at 100.... lol....
CosmicDan said:
Yeah I've got a ZRAM script in there using 10%, considering the Xperia Play can do 1.5GHz stable I have considered experimenting with higher percentages and swappiness values and doing benchmarks/real use tests. But that takes a lot of time, I'll fine tune that another time.
EDIT: I wonder if it's possible to use 100% zram with swappiness at 100.... lol....
Click to expand...
Click to collapse
Lol I don't think so, you must leave enough ram for the kernel at least so that it can actually handle the page faults
Sent from my GT-I9100 running CM10
MemoryController said:
Lol I don't think so, you must leave enough ram for the kernel at least so that it can actually handle the page faults
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Haha. Well ive also been reading about new size optimizations in linaro toolchain too so im going to try building with that too, maybe hack-out some more things like bluetooth headsets and reduce pmem allocations. Gonna experiment with a lot of stuff.
Thanks for the tips and chat
Sent from Xperia Play (R800a) with Tapatalk
CosmicDan said:
Haha. Well ive also been reading about new size optimizations in linaro toolchain too so im going to try building with that too, maybe hack-out some more things like bluetooth headsets and reduce pmem allocations. Gonna experiment with a lot of stuff.
Thanks for the tips and chat
Sent from Xperia Play (R800a) with Tapatalk
Click to expand...
Click to collapse
No problem, hope you work it out.
Sent from my GT-I9100 running CM10
Related
It looks like KJ3 ROM on captivate uses more RAM that KH3. To confirm this can I reuest guys to post their RAM usage for KH, KI and all KJ versions. Please use TaskManager to clear memory and note the base RAM......it may not be accurate but will give an idea. In my experience KH3 runs around 170 MB and KJ3 is at 230 MB.
Thanks for any input
im on a kj3 rom using about 230 myself.
RAM in android is SUPPOSED to be used... free RAM is wasted RAM.
studacris said:
RAM in android is SUPPOSED to be used... free RAM is wasted RAM.
Click to expand...
Click to collapse
only true if the ram is taken by cache not some unknow process/bloatware.
erbsmokah said:
im on a kj3 rom using about 230 myself.
Click to expand...
Click to collapse
Thanks, erbsmokah for your input.
studacris said:
RAM in android is SUPPOSED to be used... free RAM is wasted RAM.
Click to expand...
Click to collapse
Yes, but if you follow peoples comments on KJ3, like I am doing, KJ3 is using a much larger RAM amount, AND when further customized by adding apps, live wallpapers etc, is actually SLOWING the phone considerably. This making the phone real sluggish........which is new for a android ROM......??
EDIT: would you mind sharing your ROM and RAM?
arda99 said:
only true if the ram is taken by cache not some unknow process/bloatware.
Click to expand...
Click to collapse
I agree with this especially on the KJ3......Something is different in what is running in the background, and I hope I can investigate if this turns out to be true for other people.
I agree and went back to fatsy ki rom and it stays faster longer without lag.
I also monitor free ram and once it gets below 40, it lags badly, over 50 it flies.
I think this phone really needed 1 gig like the gs2
Sent from my SAMSUNG-SGH-I897 using xda premium
electroau said:
I think this phone really needed 1 gig like the gs2
Click to expand...
Click to collapse
+1, if the captivate had more ram, I'd still be using it.
Simba501 said:
+1, if the captivate had more ram, I'd still be using it.
Click to expand...
Click to collapse
+1 I myself am willing to agree..........if this RAM usage is a consensus on KJ3 then maybe the cappy is reaching its last usable ROM update? This is important to know......
EDIT: Of course, since this a leak release, then ATT/Samsung are fooling around with this build........., and maybe come back to normal on next leak ?? As a captivate owner, I would like to know what life my phone has as a "advanced" device........
chappatti said:
Yes, but if you follow peoples comments on KJ3, like I am doing, KJ3 is using a much larger RAM amount, AND when further customized by adding apps, live wallpapers etc, is actually SLOWING the phone considerably. This making the phone real sluggish........which is new for a android ROM......??
EDIT: would you mind sharing your ROM and RAM?
Click to expand...
Click to collapse
Fusion x beta kj3 267mb Ram used ATM. But no lag whatsoever.
If you find that the ram does get bogged down just on this firmware version then perhaps the lmk settings in the kernel aren't as aggressive, which would be easily fixed by SOURCE CODE.
studacris said:
Fusion x beta kj3 267mb Ram used ATM. But no lag whatsoever.
If you find that the ram does get bogged down just on this firmware version then perhaps the lmk settings in the kernel aren't as aggressive, which would be easily fixed by SOURCE CODE.
Click to expand...
Click to collapse
Point well taken........
But due you expect LMK to let ~100 MB slip by? It seems a little too much, since the limit on cappy is about 370 (usable). I would think we so much consumption LMK would kick in earlier?????
My KJ3 is using 227 MB. Free memory is ~50 MB. It lags significantly at times. However, I used Auto Memory Manager and set the Android internal task killer to "aggressive" and it keeps ~100 MB free an there is not lag at all now. I haven't noticed (yet) that apps get killed prematurely, which could be an issue with this setting. I'm using the Samurai 1.2 kernel overclocked to 1.252 GHz (no Voodoo lag fix). Other than the occasional black screen on the Gallery, my Captivate has been running pretty fast and seems to have as good a battery life as I remember ever having.
Edit #1: I don't think Auto Memory Manager is needed with Samurai 1.2. This kernel is tweaked already. I set Auto Memory Manager back to default settings, uninstalled it, then re-installed the kernel.
Here's another tip, move all of your apps from the internal SD card to phone memory. Having them on the SD card cause significant lag, crashing, and rebooting for me.
Edit #2: I switched to Pinnacle 1.3 with the latest Boog's kernel, and my KH3 is using 329 MB (the same as KJ3 I was using before (I must have made a typo above when I claimed 227 MB on KJ3 (I verified this before I switched to KH3/Pinnacle)). What governs how much RAM is used? Does it really make any difference? Free memory makes a huge difference in lag, however.
On latest MIUI and i have ~200 MBs of free memory!
Sent from my I897 using xda premium
Surely not that much... M on miui too n the lowest I get is 80,otherwise I am up there at 130ish... But then I have a crapload of services in the background. But yes, I do get 200 when I clear memory.
Sent from my cell phone. DUH
Are there any other existing kernels for sgs4g besides the ones on the first page?
Reason I ask is because I'm trying to use a swap partition, but it seems these kernels are not swap enabled.
Why has nobody bothered to compile any custom kernels for the sgs4g? I am trying myself, but no luck so far.
Any ideas?
Thanks,
S
sconsylman said:
Are there any other existing kernels for sgs4g besides the ones on the first page?
Reason I ask is because I'm trying to use a swap partition, but it seems these kernels are not swap enabled.
Why has nobody bothered to compile any custom kernels for the sgs4g? I am trying myself, but no luck so far.
Any ideas?
Thanks,
S
Click to expand...
Click to collapse
I'm not sure I can answer the whole question as to why we don't use swap, but I can say that we just got the GB kernel source, and people are still working on it and haven't posted anything.... yet. Patients...
But, I noticed that the Bali 3.3 kernel (KD1) also did not have swap. Maybe drhonk and Krylon360 tried it and swap didn't help or improve performance.
The rest of the kernels you'll find are either stock leaks, or modified stock leaks. Samsung doesn't like swap I guess. Or swapping on SD/MMC sucks hard.
I know in newer kernels (3.0 and greater), there is a new driver for mtd-swap, but it is still very new and I doubt anyone will use it in production for quite some time.
Using swap on Android is not such a great idea, it goes a little bit against native Android memory management. Then benefit can be that more programs will stay in memory and won't need to reload, but the phone will become a lot slower, even with small partitions like 32MB. With 128MB or higher it will become almost unusable. Ask me how I know
I think the need for swap was gone once phones started coming with 512mb+ ram. I used swap all the time (also required for GB) on my MT3G, since it only had like 192mb ram. It never made the phone work faster at all, in fact it usually slowed down over time running, it really just made it so stuff didn't force close due to running out of memory. This shouldn't be needed on this or any new phone.
So Bali 3.3 is a GingerBread build? Didn't know that. Kinda figures I guess. Thought I had already tried it though and couldn't bootload. I'll give it another whack. His stuff is awesome of course. I'm not demanding it, mind you, just trying to see why it would not be included. Kind of like not having a /proc/config.gz file in some Android builds, don't really know the reason why they're not included (results in not able to mount ubuntu builds, anybody have these let me know .
This appears to be the only source of kernels for our phones, no swap support enabled though. http://forum.xda-developers.com/showthread.php?t=1194032
(Thanks dr.honk!)
As for the swap partition not making sense, I have a hard time understanding why it wouldn't just provide a static and beneficial extended memory source. I am familiar with the memory management features of Android, and actually don't use any additional task killers as I've found them to be conflicting often.
But Android is built off the Linux system/kernel, so why does dedicated swap work with a large OS but not the smaller but similar Android OS/kernel?
Thanks!
sconsylman said:
As for the swap partition not making sense, I have a hard time understanding why it wouldn't just provide a static and beneficial extended memory source. I am familiar with the memory management features of Android, and actually don't use any additional task killers as I've found them to be conflicting often.
But Android is built off the Linux system/kernel, so why does dedicated swap work with a large OS but not the smaller but similar Android OS/kernel?
Click to expand...
Click to collapse
In short, the phone will become annoyingly slow.
Swap works on kernel level. Android will see this as additional virtual memory, so it will keep more programs alive and won't unload them. For example a browser will hog a lot of memory causing other programs' memory pages to be swapped. Kernel doesn't differentiate between programs, so, for example, the launcher memory pages will be swapped. Or even the active program you are currently working with can have part of its memory in the swap. Next time you try to do something (like scrolling), the memory pages will have to be brought back. Flash memory is not particularly fast (in fact for swap it is very slow), so you can we waiting for some noticeable time for many actions to complete. You'll have a lot of jerky movements, delays, temporary freezes, forget any smoothness. It is just annoying, trust me, I've tried
Ah, ok so the swapping is noticeably slower than the ram on the phone (512mb). I would not figure that it would be too much of a factor, especially on class 6+ sd cards. So there is absolutely no way of coding the system apps to be ram based, and everything else to be swappable? I'm surprised that this has not been done, but I assume that the reason is the expanding active ram capacities on new phones.
So were you experimenting on the sgs4g, or was it another model? And if so, what were you using? Froyo swap enabled kernel?
The HTC Thunderbolt has some similar specs.
http://forum.xda-developers.com/showthread.php?t=1106420
More ram 768mb vs 512mb, more internal storage 4g vs 1000mb, but uses a 1g single core scorpion processor instead of our 1g single core hummingbird. Some are having good luck with this device and swapping (taking all "facts" with a grain of salt). There is more like this too, with a number of market apps to support swapping: Swapper2, Swap for Root, Diaper swappers forum (oops, that one doesn't work for some reason).
sconsylman said:
So Bali 3.3 is a GingerBread build? Didn't know that. Kinda figures I guess.
Click to expand...
Click to collapse
No, Bali 3.3 is Froyo.
I did try it on this phone few months ago when I was still on Froyo with Bali kernel. Don't try to load in on GB, wait until DrHonk makes a new one, he actually may soon.
I personally can't imagine how anybody could use swap on Android and like it, but everybody's mileage varies. The benefit of using swap wouldn't be speed but rather less program reloads. For example you browse the web when a call comes. You answer the call, maybe go to address book, or take some notes, or send some pictures, etc. Everything will be a little slow and jerky, but with swap enabled you have better chance that when returning to the browser it will still be on the same page without reloading from the server.
Just checking again to see if anyone knows of any KJ6 kernels with swap enabled, as I'm currently getting memory warnings from running Backtrack 5 non-gnome. It works pretty well otherwise (besides the lack of space, thanks obsolete fat32).
??
sconsylman said:
Just checking again to see if anyone knows of any KJ6 kernels with swap enabled, as I'm currently getting memory warnings from running Backtrack 5 non-gnome. It works pretty well otherwise (besides the lack of space, thanks obsolete fat32).
??
Click to expand...
Click to collapse
No swap. what version of the kernel are you running?
bhundven said:
No swap. what version of the kernel are you running?
Click to expand...
Click to collapse
Sent from my SGH-T959V using xda premium
2.6.35.7 KJ6-CL694138
It has [email protected]#9 signature on it. I know we had spoken briefly about swap. What linux are you running?
I know that the Debdroid program is successfully running swap with good results, but it won't mount right with the specific scripts (our phones working mount scripts are different, I linked them in my linux post). I can take some coding from that programs scripts but of course it won't work without the kernel having swap built in.
Sent from my SGH-T959V using xda premium
I'm curious about how much free ram everyone has on average after their rom has finished booting and stabilized! Post it here!!!
jookdakang23 said:
I'm curious about how much free ram everyone has on average after their rom has finished booting and stabilized! Post it here!!!
Click to expand...
Click to collapse
Say like fresh boot let it sit for 5 minutes??? Post what rom and kernels you are using as well, as some of us are on the mobile app.
EB build 3 ICS, built in kernel.
Sent from my LG-P999 using xda premium
mt3g said:
Say like fresh boot let it sit for 5 minutes??? Post what rom and kernels you are using as well, as some of us are on the mobile app.
EB build 3 ICS, built in kernel.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
you must have nothin running lol
jookdakang23 said:
you must have nothin running lol
Click to expand...
Click to collapse
it was a fresh boot, I didn't open anything just let it sit for a cigarettes length and then looked at it. Now that I have used the phone I'm at 191MB.
mt3g said:
it was a fresh boot, I didn't open anything just let it sit for a cigarettes length and then looked at it. Now that I have used the phone I'm at 191MB.
Click to expand...
Click to collapse
o ok, ics does manage ram better than gb anyway. im using weapon g2x
Just did a fresh boot on stock 2.3.3 (unrooted) and let it sit for five minutes. I have 1weather running in addition to a couple game push notification services. I have 238 mb free ram right now.
UCFJake said:
Just did a fresh boot on stock 2.3.3 (unrooted) and let it sit for five minutes. I have 1weather running in addition to a couple game push notification services. I have 238 mb free ram right now.
Click to expand...
Click to collapse
how about a screenshot? that's pretty good!
Here it is. It bumped down to 237mb by the time I thought to screenshot it.
i run about 40-80mb free on average just the way i want it.
Android uses ram differently than other operating systems like windows or linux,
it fills your ram with things that you have run already in hopes that youll run them again and it will be alot faster the second time. if it needs that ram for something else, it just kills a program and removes it from ram (this takes VERY little time)
so the more ram used the better
Klathmon said:
i run about 40-80mb free on average just the way i want it.
Android uses ram differently than other operating systems like windows or linux,
it fills your ram with things that you have run already in hopes that youll run them again and it will be alot faster the second time. if it needs that ram for something else, it just kills a program and removes it from ram (this takes VERY little time)
so the more ram used the better
Click to expand...
Click to collapse
I understand what you are saying but in some cases like mine, I only have about 5-8 apps that I use.
mt3g said:
I understand what you are saying but in some cases like mine, I only have about 5-8 apps that I use.
Click to expand...
Click to collapse
thats about all it holds. the VM heap settings are what causes this (in part) each app gets its own virtual machine to run in, this has a limited heap (ram) size of whatever is set in there.
so if your VM heap size is set to 48mb... 48 * 5 = 240mb and 48 * 8 = 384mb
add in whats needed for Android system, kernel, and various background processes that you need... its all gone
Klathmon said:
thats about all it holds. the VM heap settings are what causes this (in part) each app gets its own virtual machine to run in, this has a limited heap (ram) size of whatever is set in there.
so if your VM heap size is set to 48mb... 48 * 5 = 240mb and 48 * 8 = 384mb
add in whats needed for Android system, kernel, and various background processes that you need... its all gone
Click to expand...
Click to collapse
fair enough, never thought of that.
mt3g said:
fair enough, never thought of that.
Click to expand...
Click to collapse
it honestly was not that long ago that i was using a task killer, killing every freakin app running because i was mad it was using up all my ram... then i wanted to start developing stuff for android, and i quickly learned the error of my ways
so u dont agree with auto task killers and you saying the system runs better with lower ram?
that's what he is saying, that's been known since eclair was introduced to android though... I just never thought of the more ram being used the better.
This is what I have left! Running latest euroskank cm7. Was 130 right before screen shot
Sent from my LG-P999
jookdakang23 said:
so u dont agree with auto task killers and you saying the system runs better with lower ram?
Click to expand...
Click to collapse
that's what I'm sayin! if the OS already has the program your trying to launch in memory, it wont need to load it, saving time and power.
and if you kill programs forcefully, android (kinda) treats it like it crashed, and reloads it into memory soon after...
Klathmon said:
that's what I'm sayin! if the OS already has the program your trying to launch in memory, it wont need to load it, saving time and power.
and if you kill programs forcefully, android (kinda) treats it like it crashed, and reloads it into memory soon after...
Click to expand...
Click to collapse
ok so memory can go below 100mb without a problem because i always try to free memory around 150mb
jookdakang23 said:
ok so memory can go below 100mb without a problem because i always try to free memory around 150mb
Click to expand...
Click to collapse
it all depends on what your min-free settings are.
the apps that fall into each category are slightly different for each ROM, but whatever the highest setting is at is what your free memory should sit around, and it can and will fluctuate alot for seemingly no reason.
and before you all go out and change them as high as you can, just know that free memory is wasted memory, it takes NO power to keep things in memory, but it does take power to put things in memory every time you open it!
This explains it a bit better than i can.
Klathmon said:
it all depends on what your min-free settings are.
the apps that fall into each category are slightly different for each ROM, but whatever the highest setting is at is what your free memory should sit around, and it can and will fluctuate alot for seemingly no reason.
and before you all go out and change them as high as you can, just know that free memory is wasted memory, it takes NO power to keep things in memory, but it does take power to put things in memory every time you open it!
This explains it a bit better than i can.
Click to expand...
Click to collapse
makes sense, so basically task killers do the complete opposite? lol i will let services and apps stay in memory without a task killer and see how things go
i just change i9001 Dalvin.VM.Heapside from 64 to 357 mb and the phone is faster.., aps are launching faster .and i have.minimun lag ...i am using stock GB rom no other tweks are made , i only cange the GPU drivers from i8150
freemanandrei87 said:
i just change i9001 Dalvin.VM.Heapside from 64 to 357 mb and the phone is faster.., aps are launching faster .and i have.minimun lag ...i am using stock GB rom no other tweks are made , i only cange the GPU drivers from i8150
Click to expand...
Click to collapse
and have bad multitasking
murad777 said:
and have bad multitasking
Click to expand...
Click to collapse
i didn nothis ani problem..only when i had cange it to 1024 i didn boot and when it was at 256 it was laging .. i got in antutu 3803 and quadrant 1357 .......i am runing aps like usual facebook messenger ..muzic player ...and gta 3 is better playbel now
freemanandrei87 said:
i didn nothis ani problem..only when i had cange it to 1024 i didn boot and when it was at 256 it was laging .. i got in antutu 3803 and quadrant 1357 .......i am runing aps like usual facebook messenger ..muzic player ...and gta 3 is better playbel now
Click to expand...
Click to collapse
how did u do it?Did u use rom toolbox
And this belongs in the development section why?
My recommendation to you is to lower that back. The way it works is that it allows an application to store a maximum of that much memory. Setting it high would force it to garbage collect much later which means more CPU cycles for the app. Bad thing is low RAM and bad multitasking as said by murad. Setting it low would cause it to garbage collect much sooner so better multitasking but worse performance. Overall this doesn't really affect performance that much unless making an app use up the whole of the phone like OP did which is an obviously bad thing.
64 is good and don't change it unless you are just testing.
Xistance said:
And this belongs in the development section why?
My recommendation to you is to lower that back. The way it works is that it allows an application to store a maximum of that much memory. Setting it high would force it to garbage collect much later which means more CPU cycles for the app. Bad thing is low RAM and bad multitasking as said by murad. Setting it low would cause it to garbage collect much sooner so better multitasking but worse performance. Overall this doesn't really affect performance that much unless making an app use up the whole of the phone like OP did which is an obviously bad thing.
64 is good and don't change it unless you are just testing.
Click to expand...
Click to collapse
i dont understand its running better and it was never that fast and i have no more wake uo lag and everythin is loding realy fast ...i chage it from build.prop whit root browser.....and i just try to run 3 smol games in the same time and lissen muzic ...and i didn get lag when i run ups in task manager the ram is use 315 mb.....
Very bad idea to take all the system ram and put it in dalvik heap.. way to much.. 64mb is default, if you take all ram for heap then everything will be preloaded by default. this may result in some faster loading times but the memory is constantly unnecessarily filled. when you have 315mb in use your almost at the limit.. think about it, any app that suddenly requires more ram will lack the ability to get it. And I'm not even mentioning LMK that is also active (so you force your memory to be full and lmk keeps killing apps since its full). This is how i think about it.
edit: just read that you don't use any specific lmk, so i guess that's lmk 20mb or so. still your idea just doesn't work out
Dude...way to big...usually the modders only use 140m max..but still not quite supported for multitasking...anyway not wrong to experiment it....cheers...
Sent from my GT-I9001 using xda premium
gjoy77 said:
Dude...way to big...usually the modders only use 140m max..but still not quite supported for multitasking...anyway not wrong to experiment it....cheers...
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I set it back to 64Mb ....i nothis that aps when are open usual use ram betwen 50 to 100 and more .
freemanandrei87 said:
I set it back to 64Mb ....i nothis that aps when are open usual use ram betwen 50 to 100 and more .
Click to expand...
Click to collapse
Try 96m....i think that should be good enough to try...
Sent from my GT-I9001 using xda premium
gjoy77 said:
Try 96m....i think that should be good enough to try...
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
is runing normal know i just change it so i can run better gta 3 at hie seting
Hello,everyone!
I have a Nexus 5 whose ram size is about 2GB. Now, I want to change the ram size to 1G or anything else below 2.
Do you have any idea? If so, please share with us now. I'll appreciate that very much!
Someone told me that I might try the bootloader, but I havn't figured that out yet. Please help me out! Thanks again!
Hi,
But... Why do you want to reduce your RAM size????
RAM is allocated to user apps, system, GPU, etc... it's possible (for some devices) to re allocate the RAM for the GPU (a little more) for example at kernel level, but here you want to re allocate 1 Gb of RAM, seriously? Why? Even if it was possible, here what do you expect?
For other devices with an unlock bootloader it's the system partition size (I don't remember the exact name) you re allocate to be used for the user (apps), maybe it will be possible in the future for the N5?
But here, honestly, I don't uderstand why you want that
viking37 said:
Hi,
But... Why do you want to reduce your RAM size????
RAM is allocated to user apps, system, GPU, etc... it's possible (for some devices) to re allocate the RAM for the GPU (a little more) for example at kernel level, but here you want to re allocate 1 Gb of RAM, seriously? Why? Even if it was possible, here what do you expect?
For other devices with an unlock bootloader it's the system partition size (I don't remember the exact name) you re allocate to be used for the user (apps), maybe it will be possible in the future for the N5?
But here, honestly, I don't uderstand why you want that
Click to expand...
Click to collapse
Firstly, thanks for your response!
Now I'm doing a series of experiments on swap partition. For the ram size of N5 is a little too large to make use of the swap area I created.
So I want to make the ram size small enough so that the device could run out of memory and would swap things out to emmc(swap area).
Have I made it clear to you? Looking forward to your reply!:fingers-crossed:
Hi,
Yes it's a little clearer, maybe, but why do you want that? What kind of experimentation are you doing? It's totaly counter productive...
Some apps like Ram Manager for example (Play Store) can create a swap file, there is also some kernel like Faux123 with, grrr don't remember exactly the name, something like Zramswap or... not sure...
But you don't reduce the RAM size, on 2Gb, you have about 1,8 Gb free for the system, apps and that's all, you can't reduce this part. At the end with a clean and light system booted you have about 1,6 Gb free. What you want will virtualy increase the RAM size (with the swap file).
In any case with the app above, use it to create and use your swap file, open one or two "big" apps, a game and you will see that it is used...
Tweak also the OOM settings to run Out Of Memory earlier, see Google.
You want reduce the amount of free RAM not reduce the RAM size. For me it's not the same thing.
Or I don't understand again, and I'm sorry. But I don't see the point...
Sent from my LG-D802 using xda premium
viking37 said:
Hi,
Yes it's a little clearer, maybe, but why do you want that? What kind of experimentation are you doing? It's totaly counter productive...
Some apps like Ram Manager for example (Play Store) can create a swap file, there is also some kernel like Faux123 with, grrr don't remember exactly the name, something like Zramswap or... not sure...
But you don't reduce the RAM size, on 2Gb, you have about 1,8 Gb free for the system, apps and that's all, you can't reduce this part. At the end with a clean and light system booted you have about 1,6 Gb free. What you want will virtualy increase the RAM size (with the swap file).
In any case with the app above, use it to create and use your swap file, open one or two "big" apps, a game and you will see that it is used...
Tweak also the OOM settings to run Out Of Memory earlier, see Google.
You want reduce the amount of free RAM not reduce the RAM size. For me it's not the same thing.
Or I don't understand again, and I'm sorry. But I don't see the point...
Sent from my LG-D802 using xda premium
Click to expand...
Click to collapse
Well, actually it's quite simple. The Nexus 5's RAM size is too large(ok, it's about 1.8Gb free or less). Even After I have run a lot of apps, there are still serval hundred Mb RAM free(Maybe I can run more apps, but it doesn't worth. Or I should choose another device with smaller RAM size. But that's out of my budget). Yes, as you said I want to reduce the amount of free RAM. But reducing the RAM size can also work for me.
All in all, I want to see the benefit of swap area through the experimnt?
Ok, my friend, you have got that right? It's ok, if you still feel confused. I'm glad to tall with you!
Cant you increase swappiness?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Cant you increase swappiness?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
What do you mean?
Just now, I found a way out! Make large enough ramdisk in RAM. In that way, the RAM decresed!
Thank you all the same!
zxcoolid said:
What do you mean?
Just now, I found a way out! Make large enough ramdisk in RAM. In that way, the RAM decresed!
Thank you all the same!
Click to expand...
Click to collapse
For future info.
http://en.wikipedia.org/wiki/Swappiness
Just use scavenger pro and slight of hand pro. Then you never run out of memory and you can swap apps really fast!!!!
Sent from my SGH-M919 using xda app-developers app
rootSU said:
For future info.
http://en.wikipedia.org/wiki/Swappiness
Click to expand...
Click to collapse
Thanks for your message!