The following are benchmarks where the only variable is the change in VM heap size. These were done by me, Hungry Man. I may try to take more averages to make more accurate conclusions later.
Phone: HTC Eris
ROM: Cyanogenmod 6 (Port from Hero)
Speed: 768Mhz
Use Compcache: Yes
Enable surface dithering: Yes
------------------------------------------------------------------------
12m: 409, 426, 440
avg: 425
------------------------------------------------------------------------
16m: 410, 371, 440, 435
(my phone seemed laggy for the second benchmark... I'll put a fourth result for 16m)
avg: 414
note: if you remove 371 and take the average for the other 3 you get an average of : 428.333...
------------------------------------------------------------------------
24m: 431, 412, 443
avg: 428.666...
------------------------------------------------------------------------
32m: 420, 417, 433
avg: 423.33333
Done!
Conclusions seem clear. 24m had the highest overall average as well as a peak score of 443! Others may experience different results depending on background apps (I minimized background apps and benchmarks were done directly after a reboot.)
I thought this might be useful for people who don't really know which one to pick. It may seem to some that picking the highest would be the best but from what I saw in the benchmark the 32m will actually cause you to suffer performance-wise.
Hungry Man said:
I thought this might be useful for people who don't really know which one to pick. It may seem to some that picking the highest would be the best but from what I saw in the benchmark the 32m will actually cause you to suffer performance-wise.
Click to expand...
Click to collapse
Thank you! All the JIT users should take this into account if they're modifying build.prop to make JIT more stable.
No problem =p took like an hour and a half lol I'd like to add more to it to get the average really lined up. I know when benchmarking computers you always want way more than 3.
Just gonna shamelessly bump this. Anyone using 2.2 should really have a look >_>
Where do you change heap size?
Depends on the ROM. If you have a 2.1 ROM you go to your build.prop and enter:
dalvik.vm.execution-mode=int:jit
dalvik.vm.heapsize=38m or 24m or any number.
If you're on a 2.2 ROM with cyanogenmod settings you can simply choose it under "performance settings"
GREAT INFO
you the "hungry" man
Really good idea Hungry Man.
Here are my results on CM6 test 4 v3:
12m 449 454 459 460
16m 457 467 472 469
24m 456 454 459 464
32m 449 458 466 457
Averages:
12m 455.5
16m 466.25
24m 458.25
32m 457.5
After trying to figure out what I was changing, I decided to set mine to 32m and see how it goes. Here is some information about heap sizes and linpack scores:
http://ryanolson.wordpress.com/2010...ory-per-vm-heap-can-effect-your-rom-cyanogen/
I assume you're at either 787 or 806mhz? I wonder if there's a correlary between mhz and stability of heap size. Perhaps with higher mhz you can do more with a smaller amount or something.
I'd like to try doing more than 3 tests per heapsize as well to get more accuracy. I'll do this when I get my new phone as right now it's incredibly laggy from trackball issues.
Hungry Man said:
Depends on the ROM. If you have a 2.1 ROM you go to your build.prop and enter:
dalvik.vm.execution-mode=int:jit
dalvik.vm.heapsize=38m or 24m or any number.
If you're on a 2.2 ROM with cyanogenmod settings you can simply choose it under "performance settings"
Click to expand...
Click to collapse
Can you explain the 2.1 instructions more fully? How does one go to their build.prop? is it from adb shell? That and then how to edit. I'm a linux noob.
Thanks for the info!
Full instructions for editing build prop for windows (and maybe linux I dono >_>):
Open your adb command prompt:
adb remount
ADB pull /system/build.prop build.prop
Your build.prop is now in your tools folder. Open it with wordpad or notepad or something. At the bottom add:
dalvik.vm.execution-mode=int:jit
dalvik.vm.heapsize=38m or 24m or any number.
Save it and close it. Then in ADB put in:
adb push build.prop /system/
Reboot.
For this to work JIT must already be activated on your phone. To activate JIT:
http://forum.xda-developers.com/showthread.php?t=679329&highlight=universal+jit&page=4
The Nestor (on page four) gives very helpful instructions.
Thank you!!!
Sure thing.
Tonight I'll be rebenchmarking. I'm going to use a CM6 ROM with no added applications, completely stock and I'll be using some other benchmarks so we can see where it has the largest effect.
edit: This is gonna take multiple nights lol
Related
hi, i have jit on my stock generic world 2.1 firmware. After jit enabiling my build.prop on 32 vm heapsize, i changed after reading some in an motorola milestone forum , it to 36 vm heapsize with rootexplorer. I can not explain why, but i have the feeling that most of my apps go smother when i launch they. I think my phone is smother. Im newbie, but i have the feeling after change it, try the xda app, for example,find it is faster loading.
sry for bad english, and please make a backup before change it
Do you get more points in Linpack and Quadrant now?
Tried, and all it does is brick your phone
When you restart it ofc! Haha
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Flo95 said:
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Click to expand...
Click to collapse
The more cache heapsize, the faster big apps (like huge games) are running. But small and medium size apps run slower.
The less cache heapsize is, the faster small apps run, but this can be cause of FC of huge apps.
for example, with 12 MB heapsize, small apps will fly on your phone instanly, but medium-size and huge apps will crash everytime.
If u are not playing games and use huge apps, u can set cache heapsize to 24 MB, else the 32 MB is good solution for all in my opinion
Flo95 said:
I didn't brick my X10. Mine is smoother now.
In Quadrant I get almost on every run more than 750 points now and in Linpack almost on every run more than 17.35 points. New record for me in Linpack are 17.52 points.
I'm still trying to get more than 777 points in Quadrant...
Click to expand...
Click to collapse
Hm how did that work?
I'm on 2.1 JIT enabled, global FW... I'm restoring it to the J+Z W 2.1 anyways haha!
I might try it again though, if I can be bothered, I'll post results I'll do it more carefully next time
changed to 36m on mine now. SE-Shipped-Lite ROM
hmmmm...seems smoother
Well, guys... same here) Changed to 36, and have everything smoother. Even if everybody recommends changing between 12-32 only, 36 fits perfect our x10s.
hi, thanks for feedback
i have played with my phone these day, and have no problems
linpack now 17.186 before believe at 16, but not over 17
when somebody have problems, you can go back to 32 or 24 vm heapsize
Alakasam said:
Hm how did that work?
I'm on 2.1 JIT enabled, global FW... I'm restoring it to the J+Z W 2.1 anyways haha!
I might try it again though, if I can be bothered, I'll post results I'll do it more carefully next time
Click to expand...
Click to collapse
I changed 32 to 36 with Root Explorer, saved it and rebooted my device. That's it.
Sent from my X10
Placebo effect.
I made that change and did not notice anything different or more smother, Linpack and Quadrant give lower values
Flo95 said:
I changed 32 to 36 with Root Explorer, saved it and rebooted my device. That's it.
Sent from my X10
Click to expand...
Click to collapse
I think I missed out the 36(m <--) bit XD silly me T_T
Will changing it make running 3D gameloft game smoother? Is the build file under /system folder
tiggerbcn said:
Placebo effect.
I made that change and did not notice anything different or more smother, Linpack and Quadrant give lower values
Click to expand...
Click to collapse
Right. Little apps are slower than before.
I changed it back to 32.
Has someone found a value, that makes the X10 faster? With better benchmarks etc
has anyone tested 18 or 24?
hi you can test it and report it
think it's just a feeling, maybe a bit of fine-cut not for the dramatic performance gains
Flo95 said:
Right. Little apps are slower than before.
I changed it back to 32.
Has someone found a value, that makes the X10 faster? With better benchmarks etc
Click to expand...
Click to collapse
It does say that a smaller vm will make smaller apps faster and larger apps slower. I tend to use news readers and browsers rather than games and the like, so I would if I could be bothered, take it down to 24
Edit: just changed it to 24 and it does feel faster. I was able to use it sooner after boot and my custom animations were lovely and smooth. Thanks for the tip op
Sent from my X10i using XDA App
If you are not a gamer and are an average user with the average apps, then 24 is good. I changed down to 24.
IMO the default value 24 is the best fit for our X10i. Never have a problem and can't feel any different when changing it to 32. Even when I'm in 32, I have to relaunch several apps twice before it works correctly.
So I think I'll stick with 24. ^^
The original heap size of the X10 are 24?
And JIT changes it to 32?
I think 32 is better, because the benchmarks are much better.
Hey there,
Just have a few questions about the V6 Supercharger script by zeppelinrox.
1. Is it worth it on the Atrix? I know that he says it's great for all devices as you can set your own values as well as have it rearrange the memory groupings but I was wondering if I would see any performance improvements?
2. Can it be applied to the Atrix? With our locked bootloader and all, I have very limited knowledge about this and how scripts work but it talks a lot about init.d and I was wondering would anything need to be changed so that it works with our phones/2nd-Init?
3. If it works and is worth it, what do you suggest I put for values?
- If you want a tutorial that, in my eyes, seems easier to understand then you can find it here. -
Thanks in advance
- DarkRyoushii
would rather bump than make a new thread.. I'm really eager to apply this as it rearranges memory groupings so that it's better for multitasking..
"You must be root of course!"...Check
"Using CyanogenMod 7.x.x!".....FAIL
That is just for the simplified guide. Check the first link or the original thread for it, it says it works on standard Rom
Sent from my MB860
As long as your rooted it will work.
But I'm curious about a few things...
With 1 gigabyte of ram is there ever any lag?
If the phone gets laggy, how much free ram do you have when this happens?
What are the default minfree values?
I was surprised initially that some V6 presets improved droid X2 and evo4g performance but V8 will include megamemory settings, with 512mb devices in mind, of 6, 12, 75, 125, 150, 175 mb
Hey,
How would I go about finding out the default minifree values?
For me I see quite a bit of lag when the ram hits near 200mb however I am also plagued with horrendous lag when using live wallpapers so I'm willing to try everything haha
DarkRyoushii
Sent from my MB860
zeppelinrox said:
With 1 gigabyte of ram is there ever any lag?
Click to expand...
Click to collapse
No, Ive never experienced any lag on the Atrix. Its fast! Some peeps complain about lwp lag, but I dont have a prob with that either. If anybodys Atrix is lagging its because they are doing something wrong.
DarkRyoushii said:
Hey,
How would I go about finding out the default minifree values?
For me I see quite a bit of lag when the ram hits near 200mb however I am also plagued with horrendous lag when using live wallpapers so I'm willing to try everything haha
DarkRyoushii
Sent from my MB860
Click to expand...
Click to collapse
Run the script.
It will tell you your current minfrees right when you open it under the list of options.
edit: Test this set 6, 12, 150, 200, 250, 300 mb
If it's the ones listed as system default in autokiller memory optimizer then they are:
6, 8, 16, 20, 22, 24
Sent from my MB860
Are you FKM?
lol
Freaking stock telus froyo minfree values are more aggressive at 8, 12, 24, 28, 32, 32
Google's GB values are 8, 12, 16, 24, 28, 32 which are still slightly more aggressive...
Unbelievable.
wow just applied "this set 6, 12, 150, 200, 250, 300 mb" and on reboot my phone is sitting on ~600MB free RAM instead of ~300MB!
DarkRyoushii said:
wow just applied "this set 6, 12, 150, 200, 250, 300 mb" and on reboot my phone is sitting on ~600MB free RAM instead of ~300MB!
Click to expand...
Click to collapse
And the verdict on LWPs?
still just as broken :/
phone feels snappier when loading menus and stuff though.. like going through settings and stuff.
Heh... well adjusting the mifrees to get more free ram is the easy part.
The hard part is the OOM grouping fixes that always keeps the launcher snappy and finding minfree values high enough that the phone never lags but not so high that it deters multitasking.
So the big question is, is multitasking just as good as before?
When you leave an app and go back to it later, it still remembers what you were doing?
well I'm not usually a big multitasker but I'm able to switch between 5 apps (2 of which are games) seamlessly.. not sure if it's good or not as it's probably the most I've tried at once :3
Probably gonna call it quits for the night though, nearing 3am and I gotta be at work tomorrow morning. Thanks for all your help! really appreciate it
EDIT: Interesting? After Reboot I looked at my new minfree values using your script and found they are different from what I set, they are now 12, 18, 36, 121.094, 128.906 and 136.719
seems slightly odd but okay, still snappier than what I started with anyway I better sleep, will be back tomorrow night!
Akmo or amm may be applying settings on boot
Sent from my Milestone using Tapatalk
I uninstalled both before running this script to avoid that
Sent from my MB860
maybe those are your roms default values?
either way, the V6 settings arent sticking... so you need SM to load at boot either /data/99SuperCharger.sh or /system/etc/init.d/99SuperCharger
Updated V6 SuperCharger includes MegaMemory setting... check it out!
Thanks! how do apply this megamemory setting? also I noticed that after my friend played a game on my atrix it never quit after closing it, the phone ended up getting REALLY hot to the point where I felt it through my pants in class later and looked to find my batter on 17% after 5 hours of being unplugged.. I guess I just have to screw with the minfrees or MegaMemory settings depending on which will help me more..
First off i take no credit for the virtuous oc daemon itself, it was developed by rmk40.
And credit goes to -viperboy- for the idea, i used his rom and really liked the oc daemon and saw the difference it makes. Check his rom out here. It has a nice interface to control the oc daemon and other features of the rom.
You can get more info here
DON'T use any apps to adjust cpu with this ie., setcpu, cpumaster, etc.
Ok, here is the deal flash the zip file the script will run by itself the only adjustment you have to make is the virtuous oc settings. This should work with any rom and probably any device i just don't have any other devices to test it on.
Here is how:
Open root explorer (or whatever file manager you use) and navigate to /system/etc/virtuous_oc, you will see 6 files named:
sleep_governor
sleep_max_freq
sleep_min_freq
wake_governor
wake_max_freq
wake_min_freq
These are the files you edit to your liking, i only edited wake_max_freq to read 1836000 or 1.8ghz
The two governor file have different settings and they are:
conservative
userspace
powersave
ondemand
performance
Again edit to your liking i left them ondemand myself seems to work good. I don't really know what the settings do exactly when it comes to these but they seem pretty self explanatory.
To see if it's working all you need to do is open terminal emulator or adb shell and type one of the following:
Current CPU frequency
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Current CPU governor
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Current min CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Current max CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
It autostarts using init.d, so MAKE SURE your rom supports init.d, if it doesn't you can still use it but it has to be started manually by entering the following in terminal emulator:
Code:
/system/xbin/virtuous_oc
If you overclock MAKE SURE your kernel supports it, I'm not responsible for any damage incurred
In the future i want to make an app to control the settings but i am still learning that part.
Big thanks to rmk40 for this awesome daemon and -viperboy- the bad ass idea !!
EDIT:
A basic rundown of the oc daemon is it scales up your cpu when you screen is on and scales it down when it is off, so your cpu is not overclocked continuously. It does save on battery as long as you don't get crazy with the overclocking.
rugedraw said:
The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
Click to expand...
Click to collapse
Added my pcm controls to the downloads, this will underclock/overclock(soon i hope) your battery when the battery reaches a specified percent. See this post for more details: http://forum.xda-developers.com/showthread.php?t=1227938
Changelog:
8/11
-Added Juwe11 ram optimization script
-Added speed up SD hack (Set at 3072) Details here
8/14
-Added Uninstaller
8/24
-Added virtuous_oc_pcm
Sweetness! To OC or UC, do you need to to increase or decrease the processor speed by certain increments? If so, please add them the OP for all of us noobs.
Thanks!
Edit: Since you didn't reserve any additional posts, feel free to shoot me a PM if you want me to add anything to this post in the future.
rugedraw said:
Sweetness! To OC or UC, do you need to to increase or decrease the processor speed by certain increments? If so, please add them the OP for all of us noobs.
Click to expand...
Click to collapse
Basically you can set them to what you want within reason, the way i do it is
1836000 is 1.8ghz
1188000 is 1.1ghz
So if you just put a . in between the first 2 numbers its roughly the ghz so
1288000 would be roughly 1.2ghz, at least that's my understanding if i'm wrong i'm sure someone will correct me. I wouldn't go crazy and set it at 2288000 that might do some damage.
Woooohooooo!!!! Im going in. Thank you sir!
hTc Evo [3D]
smokin1337 said:
I wouldn't go crazy and set it at 2288000 that might do some damage.
Click to expand...
Click to collapse
The phone would most likely reboot/crash.
Sent from my PG86100 using XDA App
DDiaz007 said:
The phone would most likely reboot/crash.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
And die! Haha
Id hate to be the one tackling that script :/
hTc Evo [3D]
Why yes, I'll take one thank you.
Dude! Freakin' awesome! I've been hoping someone would create this. Thanks!
smokin1337 said:
Basically you can set them to what you want within reason, the way i do it is
1836000 is 1.8ghz
1188000 is 1.1ghz
So if you just put a . in between the first 2 numbers its roughly the ghz so
1288000 would be roughly 1.2ghz, at least that's my understanding if i'm wrong i'm sure someone will correct me. I wouldn't go crazy and set it at 2288000 that might do some damage.
Click to expand...
Click to collapse
Actually, 1288000 is 1.3 rounded up and 118000 is the stock 1.2 speed, but I get what you're saying.......maybe I didn't do a good job of explaining myself. If you want 1.5, you can't set it at 150000......you'd have to set it at 1512000 (or something like that) because it must go up or down by fixed increments. I don't remember what the exact increments are, but I can look it up and post it if you'd like.
Edit: The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
I haven't tried using this method yet, as I'm already OC'd using viperboy's script. Maybe someone else can test this and confirm it is accurate.
Sent from my PG86100 using XDA Premium App
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Thanks rugedraw i added the frequencies to the op.
clamknuckle said:
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Click to expand...
Click to collapse
SetCPU can take up to several seconds to adjust, and it uses RAM also. A Daemon is instantaneous, and uses little to no RAM.
Sent from my PG86100 using XDA App
clamknuckle said:
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Click to expand...
Click to collapse
This is developed by Virtuous Unity for stability in OC the CPU, Set CPU uses some voltage to run and has been known to be unstable at times, this is the most stable way to control OC frequencies right from boot.
The Daemon works great (I have a version of this I'm testing on the MT4G at the moment) and there are benefits to using it, I would have to say it's important to spend some time reading information on Kernels to better understand what your using and the risks behind it.
Found Here: http://forum.xda-developers.com/showthread.php?t=1143177
( Scroll to the 4th Post for full information on the Daemon )
State-of-the-art-solution
So we (more precisely rmk40) thought of a better solution.
He wrote a native C Daemon which changes the governors instantly without any lag.
This leads to major performance improvements right after turning on the screen and in the lockscreen.
But at the moment this solution is a little bit harder to configure. We are planing to make a GUI for this, so you get the same comfort as using SetCPU.
Nevertheless you can even now adjust the daemon to your needs.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
Click to expand...
Click to collapse
smokin1337 said:
Thanks rugedraw i added the frequencies to the op.
Click to expand...
Click to collapse
No worries.........glad I can help with the little stuff. However, it seems like basic math is too hard for me. The correct increments are 54,000 and NOT 48,000. After some careful review, some of the high end OC frequencies had typo's, as well. I changed the info in myl post, but please update the OP, as well. I'm sure most people will be referring to that.
Just set this up on Rewind 2.1 and it appears to be working awesome.. definitely seems smoother then using a screen off profile in setcpu..
What I don't get is why Google doesn't incorporate something like this in all Android builds. It seems there are many things that can be manipulated to improve battery life on Android devices but that these solutions are just being ignored. Anyhoo, I don't think I will ever use SetCPU again...
Useless without voltage control
So this will work with nets kernel, and not against it? Just use it instead of setcpu?
NCspecV81 said:
Useless without voltage control
Click to expand...
Click to collapse
It definitely isn't useless without voltage control. I don't see how saving battery and using no system resources is useless. Plus, you cannot edit voltages on the E3D kernels yet, the sysfs HAVS interface needs to be implemented first.
-viperboy- said:
It definitely isn't useless without voltage control. I don't see how saving battery and using no system resources is useless. Plus, you cannot edit voltages on the E3D kernels yet, the sysfs HAVS interface needs to be implemented first.
Click to expand...
Click to collapse
I believe him. Hell, I all those frequencies I posted came from the OC script he designed for his rom.........which is awesome.
I have just flashed my ROM with streakdroid by dj_steve.
1st issue and the most annoying one : everything is so BIG ! it's like i am using phone on 2x zoom mode -.-
i typed for 240 dpi in install.txt but i think higher value would be better. am i wrong?
2nd : i set cpu beyond 1000 mhz and phone hangs and reboots. -.-
Overclocking was my main moto. it's not working QQ
I even tried using setcpu application
am i doing something wrong?
Higher dpis = larger everything
You can only safely OC to 1128mhz, after that it depends on your device, streaks tend to not OC very well even if it uses the same cpu as many other devices
TheManii said:
Higher dpis = larger everything
You can only safely OC to 1128mhz, after that it depends on your device, streaks tend to not OC very well even if it uses the same cpu as many other devices
Click to expand...
Click to collapse
"Rebased again off dell 351 and a couple of others
rebuilt all kernel versions from base, 1.22 and 1.267ghz overclocks work now, "
but what i noticed is 1.267 ghz makes phone crash. worked fine on 1.22 ghz though.
So i will flash rom again but with 120 dpi.
I tried to but it said battery low and turned down my request.
/tactical facepalm
isn't 10 % battery enough for this >_>
Anyways this time i will try go launcher.
PS : some guys said they got 2 k score on quadrant. 17xx is the max >_>
because if u clock is over that value.. it crashes >_>
but i will try quadrant after i OC at 1.22 with performance option.
because it helped my nenamark boost fs from 15.1 to 20.x with same ghz set -.-
on demand didn't work properly it looks.smartass made it 16 fps.
I feel like doing a nuclear facepalm.
120 dpi is too small XDDD
LOL.. i mean seriously. time to flash again XD?
edit: ok.. even 1.22 hanged at some point -.-
if you're rooted and have something like root explorer you can edit:
system/build.prop
change ro.sf.lcd_density=xxx to whatever value you want, common ones are 120/160/240, anything else might work but there's no guarentee
TheManii said:
if you're rooted and have something like root explorer you can edit:
system/build.prop
change ro.sf.lcd_density=xxx to whatever value you want, common ones are 120/160/240, anything else might work but there's no guarentee
Click to expand...
Click to collapse
thanks again but no. i don't have a root explorer and i am not rooted.
it was easy. ( maybe i did something wrong but it worked XD)
i simply flashed device again XD because i didnt factory reset before i flashed it.. it retained my settings and simply changed DPI XD
160 is perfect for me
Yea 160 is the default resolution, if you don't specify anything that's what you would get.
Sent from my Dell Streak using Tapatalk
Hey there, android enthusiasts!
Hopefully this post will gather many experienced users and solve these problems and doubts once and for all.
I've searched pretty much everywhere on google and the usual material showed up, copied and pasted around the web.
So I'm posting here, hoping that developers and hackers come and share their precious knowledge, producing new material that will put light in this often misunderstood field.
1) What does vfs_cache_pressure do? How does it interact with RAM and Swappiness?
2) What happens when I have Z-Ram enabled and Swappiness set at 0?
3) Are the init.d tweaks by franco's developers team still good for Nougat and Oreo? I understand these guys know what they do and put a good amount of effort in finding the best settings, however maybe they were wrong, or they intended to engineer them for a different kind of usage (I'm thinking about the perennial debate between Performance, Balanced, and Multitasking).
The VM tweak sets Swappiness at 0. Is this stupid if I have z-ram on because that z-ram will never be used?
4) That also tweaks vfs_cache_pressure at 100. Why not using lower values of vfs_cache_pressure like 50, or even 30 or 10? These all raise perceived performance and overall fluidity, at the expense of real performance. Even though this seems counterintuitive, one only needs to try these settings to be convinced of their value in overall fluidity and smoothness (to know more about that, see Tales from Responsivenessland by Rudd-o, and also Imoseyon's Sysctl tweaking for faster, longer lasting Android)
5) What about dirty_ratio and dirty_background_ratio? Why values of 20 and 5 respectively? What happens if we set them at, say, 90 and 55? How do they interact with swappiness and vfs_cache_pressure? I remember reading somewhere that setting them high would delay writes and save battery, but at what price?
6) How do dirty_background_ratio, dirty_ratio, swappiness and vfs_cache_pressure all interact with low memory killer values?
7) Not related: What does the Arch Power option do, exactly? Why is it good/bad for x or y?
8) What is RQ Affinity and how should I set it and why?
No one?
I've been looking for answers to some of these same questions. I know Google is my friend but when i search for what feels like forever and only find more questions, it gets frustrating. So like the OP said.....NO ONE?
Shameless bumb, we need answers
Nolfer said:
Shameless bumb, we need answers
Click to expand...
Click to collapse
Sorry for the necro.. but in May 2019 I wrote this and this on Telegra.ph in this subject, hope it still helps and you are still interested.