How do I increase the speed of my Z1 by increasing the RAM and CPU?
not any help sorry but am curious to know why you need extra speed (faster cpu)?
can understand underclocking the cpu to save battery but the phone already runs incredibly fast, an extra 100/200mhz wont make much difference other than kill your battery quicker.
Hanozy said:
How do I increase the speed of my Z1 by increasing the RAM and CPU?
Click to expand...
Click to collapse
You can use any of the apps from the Play Store such as:
https://play.google.com/store/apps/details?id=it.sineo.android.noFrillsCPU
https://play.google.com/store/apps/details?id=com.antutu.CpuMasterFree
There you can change governors and try to overclock your CPU. DO BARE IN MIND THAT THIS COULD POTENTIALLY BRICK YOUR PHONE !!!!
If you don't know what you are doing, don't play with fire.
The device is already super fast. You could downclock it if you want more battery life but its safer to just use apps such as Greenify or the built in stamina mode.
I guess I meant I need to increase my batterylife, I already have Greenify and I did mean underclocking but it came out wrong. I want to drastically increase my batterylife without installing a ROM.
Well if you want to OC you'd need a kernel that supports that. To increase ram, you can delete system apps that you don't need, use greenify to hibernate apps and in developer options, lower background process limit. If you want to make things snappier, you could lower the window animation, transition animation and animator duration (in dev options)
Ahki767 said:
Well if you want to OC you'd need a kernel that supports that. To increase ram, you can delete system apps that you don't need, use greenify to hibernate apps and in developer options, lower background process limit. If you want to make things snappier, you could lower the window animation, transition animation and animator duration (in dev options)
Click to expand...
Click to collapse
I did all that, thanks. Is 0,5 good?
Hanozy said:
I did all that, thanks. Is 0,5 good?
Click to expand...
Click to collapse
Yes 0.5 is good. I currently have mine set on it too
Ahki767 said:
Yes 0.5 is good. I currently have mine set on it too
Click to expand...
Click to collapse
Great, thanks!
Sent from my C6903 using xda app-developers app
Related
ok, nothing seemed to be making the touchscreen responsive with the ICS beta n its derivatives.
except one thing just did.
i changed the sampling rate from 200000(2 lak) to 20000 (20 hazar), n of course i had to change the up-threshold so i changed that to 95 (i did all these in rom-toolbox's kernel tweaks settings)
now everything is super-responsive (app startups, physical buttons, onscreen buttons, switching, yo name it) N while you are just lets say reading stuff on the screen, the cpu is generally at its lowest
what that means is : both responsiveness and higher battery.
please comment.
UPDATE : check the 7th post on this forum for more tweaks for snappy app launching n switching here http://forum.xda-developers.com/showthread.php?t=1570374#post24186676
UPDATE : ADDITIONAL TWEAK (more battery life) : in rom-toolbox change powersave bias to 35 (in rom toolbox) : saves a lot more battery by preventing the cpu from rushing to full-frequency while you are doing simple tasks like flicking the screen.
UPDATE : 3/31/12 : an interesting observation about "force gpu" 's causing poor performance on my post here : http://forum.xda-developers.com/showthread.php?t=1570374&page=2#post24266342
UPDATE : 4/7/12 : want even more battery life n smoothness?
add these to your build.prop save , reboot into recovery, clean dalvik-cache and /cache partition then reboot into system. things should be faster. and oh, underclock it.
ro.kernel.android.checkjni=0
dalvik.vm.execution-mode=int:jit
ro.ril.disable.power.collapse=0
ro.mot.buttonlight.timeout=1
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v
you can also do a semi-odex using titanium backup's integrate system dalvik into rom thing, but then you won't be able to change any file in the rom (like applying patches, mods etc until you've either done undo integration thing in titanium backup or just used adb shell to delete *.odex from /system/apps n rebooted)
UPDATE : 4/28/12 : if you are using a derivative of the .562 ICS then you can change the kernel tweaks/sysctl settings to dirty_ratio = 80 dirty_background_ratio = 20 and vfs_cache_pressure = 20 to get snappy app startups up_threshold and powersave_bias can both be set to 90 and select ignore_nice_load. if you use lots of apps then raise the dirty background ratio and dirty ratio both by 15 points and reduce vfs_cache_pressure by 15 for low cpu usage while the apps are running. i've noticed that many of the custom roms have started getting my tweaks or similars preincluded , plus the official ics is much better than icsbeta in memory management. and oh, use arcknight kernel. its super awesome for both features and battery life. i switch my governor to interactivex or smartassv2 when i am recording using the 14mbps camcorder mod, and then back.
the android backup & restore under person in settings should be turned off. it takes a lot of cpu, battery, data n memory. its aweful.
if this works for you, press the thanks button.
How can this be done?
Duvel999 said:
How can this be done?
Click to expand...
Click to collapse
i used rom toolbox pro, its free version is available here - https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
anything else that can edit sysctl.conf (e.g. https://play.google.com/store/apps/details?id=com.jrummy.sysctl.config and https://play.google.com/store/apps/details?id=scd.atools ) will also work.
Gonna try it
system seems to be a bit snappier
thx mate
thnx mate.
for snappy app switching i discovered another bunch of settings
in rom toolbox's kernel tweaks under performance, change min free kbytes to [CORRECTION]8192[not 8096] (or [UPDATE] 6144 - whichever one you like), dirty ratio to 95, dirty background ratio to 70 and vfs cache pressure to 5 (n of course check the apply on boot option)
let me know how you like this additional tweak
UPDATE: some observations ; high dirty ratio causes lower cpu usage n faster app-switching, low dirty background ratio causes faster app startups but uses too much cpu, vfs cache pressure above 5 or 10 causes high cpu usage n lags. (i use lots of apps)
UPDATE #2 FURTHER IMPROVEMENTS (fast all around with acceptable cpu usage, super app switching, n decently fast launcher without sacrificing cpu-speed n battery life)
Kernel Tweaks :
reduce dirty background ratio to 50
check the OOM kill allocating task (if your device crashes after this, uncheck this, it may kill the android system n android os processes as well in some cases)
Auto Memory Manager :
foreground 6
visible 8
secondary 32
hidden 40
content 48
empty 120
Thnks
[white10char]
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
perhaps kickass kernel script
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
check the 98kickasskernelizer (i'd find the respective values - especially min-free n change them in the script itself), there are two other not so popular scripts out there too that you may be using.
please share with us whatever was causing the overriding of rom toolbox's (or sysctl etc)'s settings.
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
hansip87 said:
Hey there thanks for the tip. Already tried it but I don't think there's any major improvement. In fact, antutu graphic score is down a bit. But don't know why. Maybe just my phone.
sent from my white ray using XDA App
Click to expand...
Click to collapse
the benchmarks dont tell you about usability. better responsiveness is due to faster cpu response to situations.
antutu's benchmark tests for continuous high performance (battery hogging w/lags) while running just one app.
my settings are for giving great experience (touch, app switching and app launching as well)
think of it as antutu being a mr. universe test, while mine are a gymnastics olympics tournament.
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
darth5zaft said:
Well thanks. A lot less sluggish when scrooling..
Sent from my LT18i using XDA
Click to expand...
Click to collapse
thank you.
i just posted another slight tweak for higher battery life. its in the first post.
sunbriel said:
The up-threshold and powersave bias settings do not stick for some reason. They return to default values after a reboot even though Apply on boot is checked.
Sent from my LT15i (Xperia arc) on KA ICSony
Click to expand...
Click to collapse
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
estuardo4 said:
It is the same for me. I guess we'll have to review each init.d script to see what is the one that is changing these values on restart.
Click to expand...
Click to collapse
Could it be that these settings are conflicting with Supercharger?
Sent from my LT15i (Xperia arc) on KA ICSony
hootnath said:
i tried 6144, restarted n it sticks. try 8192 (i haven't tried restarting after that) : my 8096 was a mistake - i accidently doubled 1024 to 2048 n that to 4096 and then stupidly to 8096.
it is possible that numbers that are not multiples of 1024 are ignored if set on boot.
that occurred to me since init.d scripts are loaded much before rom-toolbox gets a chance to do its magic.
Click to expand...
Click to collapse
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
estuardo4 said:
I tried and it stuck after a reboot. It is working fine now. My battery is lasting more indeed, but wifi is always on, even after I made the suggested changes. I guess I'll have to reinstall Doomkernel v04 and JJ's ROM from scratch. But even with wifi always on, I'm having better battery life and less lag.
Thank you again.
Click to expand...
Click to collapse
i found another interesting thing today.
the force GPU for 3d in the settings -> developer options actually uses a lot of the cpu and causes lags. i turned it off and have instead done the following
Get rid of CPU rendering:
Navigate to /system/lib/egl/
Open the file named "egl.cfg"
Delete the first line. It should say "0 0 android" or something similar
Go back into the egl folder and delete libGLES_android.so
What this does is remove the entire soft-rendering pathway from the OS.
source : http://www.ifans.com/forums/threads/ics-performance-tweaks.369959/ ;
now, i have changed the powersave bias in teh romtoolbox's kernel tweaks to 95 instead of {correcton}35{not]95. the cpu is spending more time @ 122mhz and deep sleep now without lags (which means more battery)
if this thing works for you, please press thanks.
hello guys I want to know in iphone when you click power button the screen turns on immediately but in Zeus 6.33Bn (also all roms I have tested contains stock rom ) it opens after 2/3 seconds some times if there is a lot of apps are working it take 5-15 seconds to open
any solutions ??
Why not using task killer ?
Vinzgore said:
Why not using task killer ?
Click to expand...
Click to collapse
what??
will it affect ??!!!
He mean: Why dont you close some unnecessary app?
and I don't see a big difference between 2/3s and immediately to wake up the phone ^^
no14me said:
He mean: Why dont you close some unnecessary app?
and I don't see a big difference between 2/3s and immediately to wake up the phone ^^
Click to expand...
Click to collapse
I agree!
But using auto task killer will speed up a bit your phone.
If you want you phone even better, use supercharger script.
Sent from my LG-P970 using Tapatalk 2
Some guys say that the ATK are bad for phone
hemo-ali said:
Some guys say that the ATK are bad for phone
Click to expand...
Click to collapse
To my mind, it changes nothing or nearly nothing i use advanced task killer and im using it seldom, after charging only, or when i want to play some demanding game...
But, sticking to the topic, i would advice changing processor governor, what were you using? Are you using custom lockscreen like go launcher or widget locker?
Hbohd said:
To my mind, it changes nothing or nearly nothing i use advanced task killer and im using it seldom, after charging only, or when i want to play some demanding game...
But, sticking to the topic, i would advice changing processor governor, what were you using? Are you using custom lockscreen like go launcher or widget locker?
Click to expand...
Click to collapse
I'm using zeus and it has the default ginger bread lockscreen and I'm on smartass2
Its quite weird, because smartass2 is rather aggressive governor. However, this long-time waiting (5-15sec) comes from lowering CPU frequency to really low, deep sleep numbers.
If its a real problem for you, you can easily increase lowest CPU freq and see if it changes anything. And second thing which comes to my mind, check in build.prop line "pm.sleep_mode=1". It causes device to get into deep sleep.
But, of course these changes will affect battery life... quite strongly :/
Hbohd said:
Its quite weird, because smartass2 is rather aggressive governor. However, this long-time waiting (5-15sec) comes from lowering CPU frequency to really low, deep sleep numbers.
If its a real problem for you, you can easily increase lowest CPU freq and see if it changes anything. And second thing which comes to my mind, check in build.prop line "pm.sleep_mode=1". It causes device to get into deep sleep.
But, of course these changes will affect battery life... quite strongly :/
Click to expand...
Click to collapse
thnx all
Does anyone use the Trickster Mod app on stock kernel? I have the donate version and i take advantage of the charging LED light. If so what, if any tweaks did you try? I also use the multi core power save tweak set a 2. For anyone that may know, would using titanium backup to convert Trickster Mod to a system app have any advantages?
Doubtful. AFAIK Trickster mod just makes the changes at startup, it doesn't need to run all the time.
BTW I have both enabled, the multi core power saver and mp-decision.
Cool to know it works with the stock kernel. Is there a noticable difference in performance and does it give you better battery life?
sman789 said:
Cool to know it works with the stock kernel. Is there a noticable difference in performance and does it give you better battery life?
Click to expand...
Click to collapse
It's tough for me to say if it gives better battery life due to a lot of changes in settings, e.g. greenify, app permissions etc working in connection. I will say it doesn't hurt. When my phone is asleep I lose about 1 to 1.5 percent per hour which is okay with me. Performance is fine for my needs. Plus I like the LED feature to know when my phone is charge by the status of the green light without having to psychically unlock the MX and check. But to say how much of a difference is hard to tell without setting everything else back to default and just using Trickster.
Can someone help me with the lmk in the kernel tweaker app?
I want the lmk to almost kill nothing and keep as much as possible running
So how do i set the preset?
To very light?or very aggresive
demon2112 said:
Can someone help me with the lmk in the kernel tweaker app?
I want the lmk to almost kill nothing and keep as much as possible running
So how do i set the preset?
To very light?or very aggresive
Click to expand...
Click to collapse
Try with very light, very aggresive will kill most of your idle apps.
I have read alot of articles on the lmk and how to tweak it but the numbers confuse me does the numbers mean the total free ram there is before that proces gets killed?
See below
demon2112 said:
See below
Click to expand...
Click to collapse
What numbers? on the right side of the slider?
Jup
This is how I setup my rom after flash, and device is working very well with 52 installed apps
1. Configure settings
-Go to wifi and disable scanning always on
-Open mobile network and chose 2G (use 3G only when you need it)
-Go to more and then to mobile broadcasts and disable all (when it enabled, consume RAM)
-configure sound,display, and interface... As you want
-go to accounts and disable sync which you don't need.
-go to About and taping on blablabla, you know to enable Developer options and rom performance.
-Go to developer options set all animations(you have three) to 0.5
-Performance??
-you don't need it, I will show you in next step.
2. Flash this:
L Speed
Or make this manualy
2.1. Install&Configure TricksterMod
-For cpu freq the best is to set device default, like on stock rom, don't forget to press Lock freq.
-Minfree setup
-8mb
-12mb
-17mb
-25mb
-29mb
-33mb
-Syscontrol setup
-Set swappiness to 60
-Set vm.vfs_cache_pressure to 40
-vm.dirty_ratio = 90
-vm.dirty_background_ratio = 70
Set this from tricksterMOD
-CPU freq
The best is
-Min freq
320Mhz
-Max freq
1008mhz
-Scheduler
SIO
-Governor
SmartassV2 or SmartassH3
-GPU freq
-That is your choice min freq will increase battery life, but some laggs is possible, max freq will drain battery faster, but there is less possibility to have lag.
After all don't forget to set run on boot.
3.Install&Configure Greenify
-You already know Hibernate what you want expect Alarm clock, messaging apps, trickster mod, etc.
You already know if you hibernate app with push notifications, you don't get it.
4. Apps
-what about apps??
There is too much apps which user don't use, that apps use ram like other.
Now you need to delete everything what you don't use (live wallpapers, cm wallpapers, etc.) or change apps with some lightweigh, like gallery and keyboard. Download QuickPIC and google keyboard (lollipop themed) {{i will add link later }}
5.build.prop
-leave build.prop to default as much as possible.
-change DPI to device standard, in some reasons my device lag on 200, then I move back to 240 as default. This is for L7.
For L5, there is no line that define DPI, you can skip this step.
-Change ro.max.fling from 4000 to 8000 (don't add ro.min)
-Change vm.heapsize to 64m (I don't go under that, but difference is big from 128 to96 choose between 96 or 64
-Change lowRAM from false to true (you will get little more free RAM).
When you change it to true, you will lose transparent statusbar.
6.init.d
-keep device without any special tweaks, devs which make this rom, they choose the best.
Helpful tips:
-Don't use battery boosters, ram boosters and apps call like that. System do better than one app. There is low memory killer (lmk).
Also this app use ram which you maybe need for something.
Nice tips buddy!
Good job!
Sent from my IdeaTab A2107A-H using Tapatalk
skyinfo said:
Nice tips buddy!
Good job!
Sent from my IdeaTab A2107A-H using Tapatalk
Click to expand...
Click to collapse
Thanks dude
Realy good,i add some of the sets into my rom,thanx!!!
NERDIFIED TILL DEATH!!!
thnx a lot, i hope it all works for me too
since gpu freq is not changing to 245 (for some reason) I decided to stick with 380 because I run ePSXe on my phone
turkiktxhc said:
thnx a lot, i hope it all works for me too
since gpu freq is not changing to 245 (for some reason) I decided to stick with 380 because I run ePSXe on my phone
Click to expand...
Click to collapse
Is device faster???
Everyone who have L7 know speed
-CALIBAN666- said:
Realy good,i add some of the sets into my rom,thanx!!!
I
NERDIFIED TILL DEATH!!!
Click to expand...
Click to collapse
I will post video tonight to see speed of my device
But say me how to post video on xda
Paget96 said:
Is device faster???
Click to expand...
Click to collapse
It's extremely fast at this point, i'm only afraid of it gradually slowing down after days of use
right now, it's really fine
-CALIBAN666- said:
Realy good,i add some of the sets into my rom,thanx!!!
NERDIFIED TILL DEATH!!!
Click to expand...
Click to collapse
Quality is too bad, but.
https://www.youtube.com/watch?v=tm5ay4alFPQ&feature=youtube_gdata_player
Vrh brate
Thank you for these settings
Paget96 said:
This is how I setup my rom after flash, and device is working very well with 52 installed apps
1. Configure settings
-Go to wifi and disable scanning always on
-Open mobile network and chose 2G (use 3G only when you need it)
-Go to more and then to mobile broadcasts and disable all (when it enabled, consume RAM)
-configure sound,display, and interface... As you want
-go to accounts and disable sync which you don't need.
-go to About and taping on blablabla, you know to enable Developer options and rom performance.
-Go to developer options set all animations(you have three) to 0.5
-Performance??
-you don't need it, I will show you in next step.
2. Install&Configure TricksterMod
-For cpu freq the best is to set device default, like on stock rom, don't forget to press Lock freq.
-Minfree setup
-8mb
-12mb
-17mb
-25mb
-29mb
-33mb
-Syscontrol setup
-Set swappiness to 60
-Set vm.vfs_cache_pressure to 40
-vm.dirty_ratio = 90
-vm.dirty_background_ratio = 70
-Gpu freq
-That is your choice min freq will increase battery life, but some laggs is possible, max freq will drain battery faster, but there is less possibility to have lag.
After all don't forget to set run on boot.
3.Install&Configure Greenify
-You already know Hibernate what you want expect Alarm clock, messahing apps, trickster mod, etc.
4. Apps
-what about apps??
There is too much apps which user don't use, that apps use ram like other.
Now you need to delete everything what you don't use or change apps with some lightweigh, like gallery and keyboard. Download QuickPIC and google keyboard (lollipop themed) {{i will add link later }}
5.build.prop
-leave build.prop to default as much as possible.
-change DPI to device standard, in some reasons my device lag on 200, then I move back to 240 as default.
-Change ro.max.fling from 4000 to 8000 (don't add ro.min)
-Change vm.heapsize to 64m (I don't go under that, but difference is big from 128 to96
-Change lowRAM from false to true (you will get little more free RAM).
6.init.d
-keep device without any special tweaks, devs which make this rom, they choose the best.
Only if you want add zipalign.
Click to expand...
Click to collapse
pretty good and usefull tips :good: :good: but if i edit the build.prob i get black screen on boot
Jobloxx said:
pretty good and usefull tips :good: :good: but if i edit the build.prob i get black screen on boot
Click to expand...
Click to collapse
You think bootloop?? Or just black screen??
Anf which device you use?
Dj_Luxor said:
Thank you for these settings
Click to expand...
Click to collapse
no problem
Thanks for using my setup.
Paget96 said:
You think bootloop?? Or just black screen??
Anf which device you use?
Click to expand...
Click to collapse
When i manually edited the build.prop I ended up black screen too, then i tried out the build.prop Editor app, which worked for me.
vangama said:
When i manually edited the build.prop I ended up black screen too, then i tried out the build.prop Editor app, which worked for me.
Click to expand...
Click to collapse
Then ok
@Paget96 really cool! This is actually what I'm trying to do bro and thanks muchly for this configuration tips. I got more infos:thumbup:
Paget96 said:
You think bootloop?? Or just black screen??
Anf which device you use?
Click to expand...
Click to collapse
No blackscreen and i have l7
junephel said:
@Paget96 really cool! This is actually what I'm trying to do bro and thanks muchly for this configuration tips. I got more infos:thumbup:
Click to expand...
Click to collapse
Ok
Thanks for helping.
Added little stuff
Maybe someone use it
Jobloxx said:
No blackscreen and i have l7
Click to expand...
Click to collapse
now working used an editor working great