Related
So I'm new to phone hacking, but an experienced software developer with a pretty strong Linux background... Anyway, I was rooting around the filesystem and found /sys/devices/system/cpu/cpu0/cpufreq/
I checked the values in scaling_max_freq and scaling_min_freq and they were both set to 528000. After doing some forum searching I see that some people mention using setCPU to let their CPU throttle down to 245 MHz when the screen is off, but when I tried to do echo 245000 > scaling_min_freq it doesn't ever change from 528000
I'm using Fresh 1.1, do I need to install a different kernel if I want my CPU to scale, and why can't I edit this file manually? I assumed that all setCPU was doing was editing /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and scaling_max_freq and scaling_min_freq
ASULutzy said:
So I'm new to phone hacking, but an experienced software developer with a pretty strong Linux background... Anyway, I was rooting around the filesystem and found /sys/devices/system/cpu/cpu0/cpufreq/
I checked the values in scaling_max_freq and scaling_min_freq and they were both set to 528000. After doing some forum searching I see that some people mention using setCPU to let their CPU throttle down to 245 MHz when the screen is off, but when I tried to do echo 245000 > scaling_min_freq it doesn't ever change from 528000
I'm using Fresh 1.1, do I need to install a different kernel if I want my CPU to scale, and why can't I edit this file manually? I assumed that all setCPU was doing was editing /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and scaling_max_freq and scaling_min_freq
Click to expand...
Click to collapse
I dont know alot about linux or the kernel stuff but I do know that those of us that have been using SetCPU to adjust freqency have been installing a seperate kernel. Its Gumbo Kernel. Ill get you a link.
Gumbo Kernel
http://forum.xda-developers.com/showpost.php?p=5502421
Looks like there's a script in there that fiddles with the memory freer and sets the scaling_governor to performance instead of ondemand or msm7k.
Changes /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144
to 1536,3072,4096,21000,23000,25000 that's interesting.
edit: I'm not sure how useful that really is. Memory that isn't storing anything isn't doing anything, and so while it might make you feel better to say "Look! I have 90 mb free!" that really isn't as great as you'd think. If you run low on memory (ie the active process is needing more), then it's already going to kill and free up empty apps and content providers with no clients attached, so not really sure how useful that particular part really is.
edit2: So returning to my original question. If I want to change how low my CPU will scale down to, I need to install a new kernel?
ASULutzy said:
Looks like there's a script in there that fiddles with the memory freer and sets the scaling_governor to performance instead of ondemand or msm7k.
Changes /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144
to 1536,3072,4096,21000,23000,25000 that's interesting.
edit: I'm not sure how useful that really is. Memory that isn't storing anything isn't doing anything, and so while it might make you feel better to say "Look! I have 90 mb free!" that really isn't as great as you'd think. If you run low on memory (ie the active process is needing more), then it's already going to kill and free up empty apps and content providers with no clients attached, so not really sure how useful that particular part really is.
edit2: So returning to my original question. If I want to change how low my CPU will scale down to, I need to install a new kernel?
Click to expand...
Click to collapse
Yes. Try the gumbo kernel. try scaling it to 160 just for fun. You'll see how slow it is, and it will prove that the cpu scaling works. try it at 528 also.
Is anyone aware of any way to force an app to stay in memory, rather than getting killed when free RAM is running low? I'm aware of how android's memory management works, lowmemkiller and oom_adj and all that, but setting oom_adj isn't persistent... as soon as you open another app it gets reset. Anyone know how to make an oom_adj setting stick? (or achieve the equivalent via some other method)?
Sure wish someone could come up with a solution for this!!
I am on Galaxy S but also very interested in this.
I found some thread where I saw explanation about how to keep default launcher in memory ( also lowering oom ) using terminal.
But I don't know how to apply same thing on any application.
I mostly need it to keep Phone.apk in memory (cached process)...
So if anyone can help that would be great.
Cheers
Hi there XDA,
I've been using the custom rom DjangoManouche for some time now, and it's great! But while installing i'm usually guessing the settings. If someone can clarify it, it would be great!
Note that these settings are asked of you while you install DjangoManouch custom rom.
1. Available Kernels.
When installing the KoB kernel, you can chose between several options. NoOC or OC, with or without RamHack. I know that OC stands for over clocking, but what does the RamHack do (28 / 32 mb)?
2. Dynamic Fsync (active / inactive)
I found this explanation: http://forum.xda-developers.com/showthread.php?p=33381928
If i understand this correctly it means that you have a small lag when ending calls. But when your system crashed you won't lose data.
3. Frandom Optimazations (active / inactive)
I can find no information about this on the internet..
4. Zram (active 96/128mb or inactive)
I found this explanation: http://forum.xda-developers.com/showthread.php?t=2077072
If i understand this correctly it means that ZRAM is handy for devices with not a lot of RAM. But the LG 02x has 1gb of RAM(?). Wich raises the question what good does it do?
5. RAM Management (stock RAM values / Supercharger Free Ram values / SuperCharger Balanced Ram values)
I found this explanation: http://www.technorms.com/10319/boost-performance-android-phone-supercharger
Wich explains that supercharger script boost your phones performance. But doesn't explain what the difference is between 'Free Ram values' and 'Balanced Ram values'.
6. CRT Effect (enabled / disabled)
Is this the awesome animation that shows when you power on / off your phone?
7. Fast Dormancy (enabled / disabled)
I found this explanation: http://androidforums.com/samsung-galaxy-s2-international/674208-fast-dormancy-in-nutshell.html
In short you want to enable it if your provider supports it, correct?
8. Cronjobs (active / inactive)
I can find some javascript related information, but not connected to Android. So i'm in the dark here.
As last i want to add that I'm posting these questions here because flooding the original thread with these questions is just creating noise And i'm sure there are a lot of other people with the same questions.
Thanks in advanced!
Dynamic sync is better disabled.....when enabled and issues of reboot....has a risk of data corruption.
ZRAM....96 is better....makes apps open faster......one correction-O2X has 512 and not 1GB.
Balanced RAM or free RAM.....old timers from GB will know....so maybe Carbs did not feel to state it again
Kernel ....OC is better but for rh....I prefer no ramhack
Frandom....I chose not to activate....did not find a big difference in perf
Fast dormancy.....better disabled for battery
Ramhack....is hacking and in simple words stealing what is normally for the system.....for faster performance.....but can be lagging or missing some features ....higher RH can lead to issues in Camera or other apps....so I prefer the minimum of rh and less RAM consuming background apps
I hope you can read the threads which you have posted but on experience ....I have posted what I have tested and used over quite some time on this device.
Thanks for the understanding
EDIT: forgot the cron job.....this is something Carbs first started in the O2X long back to free RAM periodically......everyday at a specified time,,,,cron script will run and clear.but you need to activate it by giving permissions
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
LilProphet said:
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
Click to expand...
Click to collapse
for the first part....you are absolutely right my friend.
in android.....extra or too much RAM is wasted RAM.....so generally speaking we dont need too much too....like in WIN
but, less RAM can be leading to lags and screen freezes
Ramhack can be leading to some unpleasant things sometimes.....too much of RH can also make a few apps, system apps to FC....so I always prefer to have no RH and use apps like greenify or minfree manager.....I agree with the DEV as the testings and general usage over time will show the correct results......some of us users might not see that....
SREEPRAJAY said:
Dynamic sync is better disabled.....when enabled and issues of reboot....has a risk of data corruption.
ZRAM....96 is better....makes apps open faster......one correction-O2X has 512 and not 1GB.
Balanced RAM or free RAM.....old timers from GB will know....so maybe Carbs did not feel to state it again
Kernel ....OC is better but for rh....I prefer no ramhack
Frandom....I chose not to activate....did not find a big difference in perf
Fast dormancy.....better disabled for battery
Ramhack....is hacking and in simple words stealing what is normally for the system.....for faster performance.....but can be lagging or missing some features ....higher RH can lead to issues in Camera or other apps....so I prefer the minimum of rh and less RAM consuming background apps
I hope you can read the threads which you have posted but on experience ....I have posted what I have tested and used over quite some time on this device.
Thanks for the understanding
EDIT: forgot the cron job.....this is something Carbs first started in the O2X long back to free RAM periodically......everyday at a specified time,,,,cron script will run and clear.but you need to activate it by giving permissions
Click to expand...
Click to collapse
Thanks for your reply!
It seems that cronjobs are actually really useful! But how do i give it permissions? Usually SU ask to give you permissions when the proces starts. (For example when you open Titanium Backup). But i can't manually add permissions.
LilProphet said:
To be exact, Optimus 2x only has 384 Mb of RAM available to use for Android and apps, because 128Mb of that 512 is dedicated to the GPU. This is why many developers embed RAM hacks, because that is not much.
Since I've been using DMX I've experienced that with supercharger off, I'm always suffering from very little free memory, but many people claims (mainly Carburano), that supercharger eats much CPU even when the screen is off, that's why he doesn't suggest to use it.
Click to expand...
Click to collapse
Thanks for your reply! So it means that your device is faster, but also drains your battery faster when screens is of?
SREEPRAJAY said:
for the first part....you are absolutely right my friend.
in android.....extra or too much RAM is wasted RAM.....so generally speaking we dont need too much too....like in WIN
but, less RAM can be leading to lags and screen freezes
Ramhack can be leading to some unpleasant things sometimes.....too much of RH can also make a few apps, system apps to FC....so I always prefer to have no RH and use apps like greenify or minfree manager.....I agree with the DEV as the testings and general usage over time will show the correct results......some of us users might not see that....
Click to expand...
Click to collapse
Thanks for your reply! Let;s see what Greenify can do!
I'm gonna install the new DMX 1.6.1 in a few minutes with these settings:
1. KoB Kernel with no ramhack
2. Dynamic Fsync inactive
3. Frandom Optimazations inactive
4. Zram 96mb
5. Ram Management with Supercharger Free Ram values
6. CRT Effect enabled
7. Fast dormancy disabled (For better battery life)
8. Cronjobs active
Has anyone experienced differences in performance between 'Supercharger Free Ram values' and 'SuperCharger Balanced Ram values'?
len.asdf said:
Has anyone experienced differences in performance between 'Supercharger Free Ram values' and 'SuperCharger Balanced Ram values'?
Click to expand...
Click to collapse
Not much, only the amount of free ram is more, but it doesn't effect the smoothness much imo. I had heavy lags with stock ram values on DM1.6 unfortunately, so I would have suggested you to use supercharger too. I hope you will be pleased with the settings you chose.
Sent from my LG-P990 using xda premium
LilProphet said:
Not much, only the amount of free ram is more, but it doesn't effect the smoothness much imo. I had heavy lags with stock ram values on DM1.6 unfortunately, so I would have suggested you to use supercharger too. I hope you will be pleased with the settings you chose.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Thanks for your reply! And we will find out today how smooth it goes
I've used my phone now for 2 days with these installation settings:
1. KoB Kernel with no ramhack
2. Dynamic Fsync inactive
3. Frandom Optimazations inactive
4. Zram 96mb
5. Ram Management with Supercharger Free Ram values
6. CRT Effect enabled
7. Fast dormancy disabled (For better battery life)
8. Cronjobs active
But it's far from smooth. I'm installing Greenify now to see if it changes anything..
If you Supercharged rom lag should happen. Which version are you using?
Sent from DjangoManouche!
carburano said:
If you Supercharged rom lag should happen. Which version are you using?
Sent from DjangoManouche!
Click to expand...
Click to collapse
Using DjangoManouceX 1.6.1A (the latest i believe).
But most of the lag happens when switching between apps or starting one. When an app is running, it's usually smooth.
len.asdf said:
Using DjangoManouceX 1.6.1A (the latest i believe).
But most of the lag happens when switching between apps or starting one. When an app is running, it's usually smooth.
Click to expand...
Click to collapse
Install 1.6.1 without supercharged and apply script for more free ram.
In my opinion for kernel use 1.7 KoB OC 32MB Ramhack.
mpoumpis said:
Install 1.6.1 without supercharged and apply script for more free ram.
In my opinion for kernel use 1.7 KoB OC 32MB Ramhack.
Click to expand...
Click to collapse
I will try this out on my next install! I prefere to use a install for several days so i can test it out better.
And after installing Greenify things got a lot smoother! That app is just black magic
Hello,
I'm looking for a good ICS ROM with much RAM memory free.
I know there are many good ones like RocketRom, but the RAM is priority for me, as I use a lot off apps and I don't want them to get killed every time I exit them.
The ROM may be stock based (best) or even some other type.
Do You know some You could recommend?
PS. They don't have to be fast as hell.
Admin please don't close this thread.
try bulletproofing them and freezing/removing unwanted apps.
Also try to set autostarts off for apps you only want to run on request as well as proper exiting them to prevent running ram.
granted its android that should optimize ram usage which is why amount of free ram shouldnt impact, but yet it does.
maybe you have set dont keep activities to on development settings if so, disable it. lol.
Other tweaking can be done with minfree and oom levels to lower values, stock however they are pretty low.
last random thing I can come up with is less memory footprint apps. Alternatives for ones you are using. Lol. Goodluck!
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
try bulletproofing them and freezing/removing unwanted apps.
Also try to set autostarts off for apps you only want to run on request as well as proper exiting them to prevent running ram.
granted its android that should optimize ram usage which is why amount of free ram shouldnt impact, but yet it does.
maybe you have set dont keep activities to on development settings if so, disable it. lol.
Other tweaking can be done with minfree and oom levels to lower values, stock however they are pretty low.
last random thing I can come up with is less memory footprint apps. Alternatives for ones you are using. Lol. Goodluck!
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I have used about 170 apps on my SGS2, now I've reduced them to about 120. I have also deleted some system apps, but the problem is android OS.
Killing apps is disabled for 100%, it's just due to 70MB memory free. The launcher is killing almost every time I turn on some other app (build.prop edit didn't stop it from closing).
Android just uses too much RAM. Fresh ROM uses 400+ MB, that's so much.
That's why I'm looking for some ROM that uses max.300MB. Are there any?
I wish I could have ROM from my xpiera x10, which used max 120MB hehe
jakuburban said:
Hello,
I'm looking for a good ICS ROM with much RAM memory free.
I know there are many good ones like RocketRom, but the RAM is priority for me, as I use a lot off apps and I don't want them to get killed every time I exit them.
The ROM may be stock based (best) or even some other type.
Do You know some You could recommend?
PS. They don't have to be fast as hell.
Admin please don't close this thread.
Click to expand...
Click to collapse
These type of threads are not allowed....as the best is up to the individual to figure out, what is best for me, may not be best for you....
All I would like to do is to keep apps maximum is possible in ram. My goal is for my daily use of most common apps like phone, whatsapp, google messenger, gmail, contacts, calendar etc. to keep them in ram so switching between them is smooth and fast without loading on anything. My memory is always more then 50% empty and little apps like calendar or contact are getting killed with no reason. That is really going on my nerves more and more.
I am on Pure Nexus CMTE rom and I have tried playing with Kernel Auditor low memory killer and virtual memory settings. What ever I do there my ram usage is always about 1 - 1.4 GB newer more then that. How I can force system to keep apps in ram until critical point? Like in my case with more then 50% of ram still available there should not be any apps removed from memory even if is app not active for some time. Can anyone please help me with this.
Possibly you see 1.5G free now, but it may have temporarily been a lot less free when the apps were killed (usage varies over time). See attached how high chrome can jump at its peak.
Just a thought..very half baked. I'm sure someone will give suggestions for what you want.
electricpete1 said:
Possibly you see 1.5G free now, but it may have temporarily been a lot less free when the apps were killed (usage varies over time). See attached how high chrome can jump at its peak.
Just a thought..very half baked. I'm sure someone will give suggestions for what you want.
Click to expand...
Click to collapse
Yes, I know but Chrome memory usage is still nothing compare to free memory available. I did some reading and end up creating local.prop file in root/data and add some lines there. How much that will help I will find out in day or two. If anyone is interested to know what I did I can post it here after.
Just wanted to add that in Android N preview the low memory kill settings by default were very light (like lighter than kernel adiutor's "very light" preset) and it resulted in very stuttery performance. Setting them back to marshmallow stock settings made everything smoother. Looking forward to anything you may uncover on this though.
StykerB said:
Just wanted to add that in Android N preview the low memory kill settings by default were very light (like lighter than kernel adiutor's "very light" preset) and it resulted in very stuttery performance. Setting them back to marshmallow stock settings made everything smoother. Looking forward to anything you may uncover on this though.
Click to expand...
Click to collapse
Okay this is what is confusing me the most. In Kernel Auditor "very light" preset means that apps will be removed soon is possible, very light means small amount of memory to be used. Am I correct? Aggressive on other hand will give more memory for apps, more apps in memory and less removing from it.
So if is that correct then is very understandable why "N" with less then "very light" preset made bad performance and soon you give it more memory to play everything is back to normal.
However I did test on that many times but in both cases my apps are getting removed from memory with more then 50% still available memory. That's why I need somehow to stop system from emptying memory until critical point. Maybe some build.prop lines can help but I am not really expert in that area.
Emilius said:
Okay this is what is confusing me the most. In Kernel Auditor "very light" preset means that apps will be removed soon is possible, very light means small amount of memory to be used. Am I correct? Aggressive on other hand will give more memory for apps, more apps in memory and less removing from it.
So if is that correct then is very understandable why "N" with less then "very light" preset made bad performance and soon you give it more memory to play everything is back to normal.
However I did test on that many times but in both cases my apps are getting removed from memory with more then 50% still available memory. That's why I need somehow to stop system from emptying memory until critical point. Maybe some build.prop lines can help but I am not really expert in that area.
Click to expand...
Click to collapse
What is the solution for Pixel 2 rom of LG Nexus 5X? os ur build prop gonna help for me? if yes plz replay.
MHS3511 said:
What is the solution for Pixel 2 rom of LG Nexus 5X? os ur build prop gonna help for me? if yes plz replay.
Click to expand...
Click to collapse
No idea man, I don't have LG Nexus 5 anymore. Today roms have that battery optimizations build in. Go there and make the app you like to be in memory "not optimized" and in Kernel auditor or any other app flashing memory to "very light". That should help. Good lack