Tripnraver and Fanboys that wants to start trouble follow this Link! If you want to clear up the Discussion and stop fighting write me a PM and if not stay at Modaco, i even post the link for you all
Open TripNHome
XDA Users stay here and help collecting some nice X10 Tweaks to help the whole Community, every Dev/Cooker knows other Tweaks so i would like to invite all to share there best Tweaks here. Above i post some basic Tweaks and a example File how it looks like.
build.prop Tweaks
# Network
HTML:
ro.ril.hep=1
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=5
ro.telephony.call_ring.delay=1000
# Product
HTML:
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
mot.proximity.delay=100
# Performance
HTML:
dalvik.vm.startheapsize=48m
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-flags=m=y
dalvik.vm.dexopt-data-only=1
dalvik.vm.lockprof.threshold=200
windowsmgr.max_events_per_sec=300
VM Tweaks
HTML:
echo 95 > /proc/sys/vm/dirty_ratio
echo 20 > /proc/sys/vm/vfs_cache_pressure
echo 4096 > /proc/sys/vm/min_free_kbytes
echo 1 > /proc/sys/vm/oom_kill_allocating_task
echo 60 > /proc/sys/vm/dirty_background_ratio
echo 1000 > /proc/sys/vm/dirty_expire_centisecs
echo 2000 > /proc/sys/vm/dirty_writeback_centisecs
Minfree Tweak
HTML:
echo 1536,3072,4096,15360,17920,20480 > /sys/module/lowmemorykiller/parameters/minfree
SD Card Tweak
HTML:
echo 2048 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
echo 2048 > /sys/devices/virtual/bdi/default/read_ahead_kb
build.prop Tweaks go to system/build.prop
other Tweaks go to system/etc/install-recovery.sh
I attached 2 sample files with these Tweaks included.
shall we edit these even if running 3.6?
bodomfan said:
shall we edit these even if running 3.6?
Click to expand...
Click to collapse
No
10 Characters
Wolfbreak said:
No
10 Characters
Click to expand...
Click to collapse
Lol ok,dumb question really.its probably all included ,iv posted a request in the rom thread
im liking v3.6 atm similar to 3.5,you got any new plan sfor releases,it would be kwl if you could get achotjans green signal bar in there as he said you have his permission and also the samsung galaxy s type gingerbread battery icon,would look sexy and very gb
You can flash the Addon yourself if you like it i dont need to include it. The ROM Style will stay same, all Theme modifications the Users can flash themself like they want it becouse everyone likes different i wont touch the Theme, everyone can flash what they want becouse i cant make a Theme everyone will like becouse thats just not possible, some like Blue, some like Carbon.....
BTW this doesnt has something to do with this Thread so please keep it clean
Wolfbreak said:
You can flash the Addon yourself if you like it i dont need to include it. The ROM Style will stay same, all Theme modifications the Users can flash themself like they want it becouse everyone likes different i wont touch the Theme, everyone can flash what they want becouse i cant make a Theme everyone will like becouse thats just not possible, some like Blue, some like Carbon.....
BTW this doesnt has something to do with this Thread so please keep it clean
Click to expand...
Click to collapse
ok thanks
10 characters
Hopefully you can create flashable zip for us.
Thanks Wolfbreak!!
You can edit buildprop w the flashtool or w rootexplorer, depending on which rom you are running, some of these tweaks may already be implimented!!
Zip file is too easy!! Explore research have fun.... just make a back up first....
Best regards,
Chris
Sent from my X10 TripNMiUI-Iris using XDA App
Already did it manually using Flashtool and Root Explorer.
But for others who need quick progress, WB should create flashable zip for them.
AND
If can, maybe WB should consolidate addon such as Bravia Engine, FPS uncap, xLoud, Audio Fix, in one flashable zip.
Hi wolfbreak
I was changing the tweaks u had given
I was changing the below tweak
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
mot.proximity.delay=100
and i found that max num of touch was 4 instead of 2 by default.... does this mean anything?
2Wolfbreak : according to this http://www.linuxinsight.com/proc_sys_vm_oom_kill_allocating_task.html I wouldn't do this "echo 1 > /proc/sys/vm/oom_kill_allocating_task". Placing 0 performs better, and prevents some unexpected FCs.
awesome man.>!!!
Thats a good initiative I was thinking of starting something like this for past two day but was wait that some actual dev to start it and i will contribute more.
ohk so here are one or two simple tricks from my side.
those who don't want to mess with install-recover.sh and prefer keeping the init.d style work
here is how you can enable init.d support.
add one line at end of your install-recovery.sh
Code:
# trying run-parted
/system/xbin/busybox run-parts /system/etc/init.d
some more tweaks which might overlap with the existing tweaks posted here...
http://forum.xda-developers.com/showthread.php?p=16441133#post16441133
Note : as usual non of the credit to me all credit to Dev's.
Request
Can someone point all guides of framework customization and howtos related to that at one place.
stuff like replacing the background image to adding a reboot option and simmilar stuff.
all links at one place would be just fine for new dev's (don't get angry if its already there and i missed it, coz there are chances of it too...)
So what do these tweaks actually do?
*improve* your phone will be the sarcastic answer, but forgive me if I won't blindly apply tweaks without having at least some idea as to what they are doing?
anantshri said:
Can someone point all guides of framework customization and howtos related to that at one place.
stuff like replacing the background image to adding a reboot option and simmilar stuff.
all links at one place would be just fine for new dev's (don't get angry if its already there and i missed it, coz there are chances of it too...)
Click to expand...
Click to collapse
If u need help PM me.
blueowl0708 said:
So what do these tweaks actually do?
*improve* your phone will be the sarcastic answer, but forgive me if I won't blindly apply tweaks without having at least some idea as to what they are doing?
Click to expand...
Click to collapse
That's actually a good question i will see what i can help you with then later on other remaining could be answered by otheres.
# Product
HTML:
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
mot.proximity.delay=100
This tweak is basically a build.prop tweak which is making system aware of a dual touch capable system.
# Performance
HTML:
dalvik.vm.startheapsize=64m
dalvik.vm.heapsize=64m
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-flags=m=y
dalvik.vm.dexopt-data-only=1
dalvik.vm.lockprof.threshold=150
windowsmgr.max_events_per_sec=80
These are basically VM related tweaks first making heapsize 64M i.e. larger default is smaller. also this last line makes your system more responsive i keep something higher then 250 in place of 80.
VM Tweaks
HTML:
echo 95 > /proc/sys/vm/dirty_ratio
echo 20 > /proc/sys/vm/vfs_cache_pressure
echo 4096 > /proc/sys/vm/min_free_kbytes
echo 1 > /proc/sys/vm/oom_kill_allocating_task
echo 60 > /proc/sys/vm/dirty_background_ratio
echo 1000 > /proc/sys/vm/dirty_expire_centisecs
echo 2000 > /proc/sys/vm/dirty_writeback_centisecs
VM Tweaks basically change min free bytes and kill level's of application used internally by android for memory management.SD Card Tweak
HTML:
echo 2048 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
echo 2048 > /sys/devices/virtual/bdi/default/read_ahead_kb
This is a simple tweak which specifies the read ahead buffer which is by default 128Kb effectively making your SDCard i/o faster.
Hope these could clarify your doubts remaining ones wolf or others might give a try to explain.
a flashable zip file would be nice
ive been trying to place my own tweaks within the install-recovery.sh file however when i flash zip the file seems to have changed however nothing actually takes effect. new to this side of things so could just be a schoolboy error lol. can say if i use the simple install-recovery.sh file from Z's uncap fps or even yours from your rom and flash it.. it all works well! if i try to edit any of yours and flash again.. nothing happens! wat am i missing?
I am referring to this thread:
http://forum.xda-developers.com/showthread.php?t=771232
I'd like to add/change some of these settings on my Archos 70 IT (no phone).
Windows max events
wifi scan level
Dalvik heap size
Unfortunately, the thread says, the values have to be adjusted in the build.prop, but I don't have these settings in there. In my opinion I should have the settings above as they are common in Android.
In fact, I'd like to add all settings of Autokiller memory optimizer.
What I did so far:
IO scheduler, set to noop
Added
http://www.xda-developers.com/android/the-best-ram-optimisation-script-for-android/
and changed the settings for lowmemorykiller
SD Card Cache, I have an app for that.
Can anybody tell me how to add the other settings in a script?
http://andrs.w3pla.net/autokiller/kernel
Even if you don't have some of the values already there, you can add them. Check out this thread: http://forum.xda-developers.com/showthread.php?t=1227269 .
Thanks.
One more question:
Are these files executed on boot?
I'd feel better if I have the additional settings in an own script such as /system/etc/init.d/S99ownscript.
This is, as I understand it, executed as the last scricpt. (R before S, and then numbers)
Is this possible or do I have to write the settings in the boot.prop or init.d file?
Are the build.prop and init.d files executed at each boot or only once, when the machine is set up?
€dit:
I added the following to my S99 script:
ro.HOME_APP_ADJ=1
ro.media.enc.jpeg.quality=100
debug.sf.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
Click to expand...
Click to collapse
What do I have to enter in terminal to check, if these values are active?
For example:
cat /sys/block/mmcblk0/queue/scheduler
Click to expand...
Click to collapse
to check, which scheduler is active.
*push*
nobody?
lordofazeroth said:
One more question: Are these files executed on boot?
I'd feel better if I have the additional settings in an own script such as /system/etc/init.d/S99ownscript.
Is this possible or do I have to write the settings in the boot.prop or init.d file?
Are the build.prop and init.d files executed at each boot or only once, when the machine is set up?
Click to expand...
Click to collapse
Yes, those files (build.prop and init.d) are executed at every boot. It is possible to make your own script, but it's better if you make a flashable one so that it will always stay and you wouldn't have to worry about if it was executed or not (since it will be "in" the rom and always executed).
I searched on google to find out how to know whether JIT is on.
The only information I can find is to look at build.prop.
There's nothing all all regarding dalvik.vm.execution-mode inside build.prop?
I can find nativehelper.so in /system/lib.
I have added dalvik.vm.execution-mode=int:jit to build.prop..
So the question is how do I know JIT is ON??
I'm on:
Android Version: 2.3.6
Build # : GINGERBEAD.DXKT5
BaseBand : S5830DXKT4
Any help would be appreciated.
PropModder has such a value editor
Herpderp Adreno + Tegra.
Hi,
i'd like to tinker with a custom rom for my device (YuanDao N101 tablet), more precisely I would like to change the default screen refresh rate of Jelly Bean. I've been searching these forums and came across this thread, where at some point they mention this:
changelog 18.06.2012:
and also have changend default screen refreshrate from 60 to 56, with the possibility to change it:
echo 1 > /sys/kernel/refreshrate/enable (60 hz)
echo 0 > /sys/kernel/refreshrate/enable (56 hz)
################################################## ####
Click to expand...
Click to collapse
So apparently it is possible to change the JellyBean refreshrate at some level.
What I cannot find on these forums or elsewhere is information about how to go about doing that. Can anybody please give information on this subject?
- can this be done simply by entering a console command in stock android?
- or do you need to change a variable in some system file?
- or do you need to make changes to the kernel and if so, where?
thanks
And where change it ?
Thanx
hi my guys
i've a silly question! coz im a Noob
lemme explain what is my mean:
custom kernels supports init.d and we can create own tweaks and save these files into init.d directory,
for example this one :
vm.dirty_ratio=20;
i found dirty_ratio in /proc/sys/vm/dirty_ratio.
but when i open this file with text viewer , i see another value for this parameter!
like this : 35
and other parameters that we can write in initd tweak files!
every time i change values , when i open original file in /proc/sys/vm/ i see constant values! ( for example 35 for dirty_ratio )
i think ROM or some apps control this parameter!
it means if we change this parameters for customization , we cant see any changes!
emmm , jelly sandwich - maxio made - custom rom control this parameters??????
or you have same problems with all ROMS???????
or this is a common situation??????
sorry for poor english!
My Device : Xperia Ray
ROM : Jelly Sandwich 8.5
Kernel : Advanced Stock.587
Unlocked , Rooted!
Maybe the init.d script not properly created..init.d script must have execution lines in the script and # symbol.
Sent from my gorgeous ST18i
yamin8000 said:
hi my guys
i've a silly question! coz im a Noob
lemme explain what is my mean:
custom kernels supports init.d and we can create own tweaks and save these files into init.d directory,
for example this one :
vm.dirty_ratio=20;
i found dirty_ratio in /proc/sys/vm/dirty_ratio.
but when i open this file with text viewer , i see another value for this parameter!
like this : 35
and other parameters that we can write in initd tweak files!
every time i change values , when i open original file in /proc/sys/vm/ i see constant values! ( for example 35 for dirty_ratio )
i think ROM or some apps control this parameter!
it means if we change this parameters for customization , we cant see any changes!
emmm , jelly sandwich - maxio made - custom rom control this parameters??????
or you have same problems with all ROMS???????
or this is a common situation??????
sorry for poor english!
My Device : Xperia Ray
ROM : Jelly Sandwich 8.5
Kernel : Advanced Stock.587
Unlocked , Rooted!
Click to expand...
Click to collapse
You can check your init.d scripts with script manager (or something similar) before you jam them into the init.d folder. This way you can test them with out having to reboot your device. There is a pretty good tut for init.d from irridaki here: http://forum.xda-developers.com/showthread.php?t=1422061 It is mostly for getting init.d to work on stock roms...but it should work on custom roms as long as there is init.d support....
to change a value in /proc you have to use:
Code:
echo [I]value[/I] > /proc/[I]path/to/file[/I]
so in your case it's
Code:
echo 20 > /proc/sys/vm/dirty_ratio
Haaop said:
to change a value in /proc you have to use:
Code:
echo [I]value[/I] > /proc/[I]path/to/file[/I]
so in your case it's
Code:
echo 20 > /proc/sys/vm/dirty_ratio
Click to expand...
Click to collapse
thnx man
yes, i saw this pattern for setting values to parameters
ill check it plus will tell u the feedback