I'm trying to get tweaks for the build.prop? I can't find any thread for the NS. I mostly want a tweak for touchscreen responsiveness and some battery tweaks if possible.
xda<3 said:
I'm trying to get tweaks for the build.prop? I can't find any thread for the NS. I mostly want a tweak for touchscreen responsiveness and some battery tweaks if possible.
Click to expand...
Click to collapse
youre not going to find any. you can change your screen resolution, or maybe some data speed tweaks..
Yeah or rom toolbox offers some as well
Sent from my Nexus S using XDA App
simms22 said:
youre not going to find any. you can change your screen resolution, or maybe some data speed tweaks..
Click to expand...
Click to collapse
umm well i found some for the motorola atrix that worked like a charm for my nexus s.. My screen is much more responsive
xda<3 said:
umm well i found some for the motorola atrix that worked like a charm for my nexus s.. My screen is much more responsive
Click to expand...
Click to collapse
nice!
by why was your screen not that responsive in the first place?
if you use the ondemand governor, and set the sampling rate to 15000 and up threshold to 98, ui gets a speed boost.
simms22 said:
nice!
by why was your screen not that responsive in the first place?
if you use the ondemand governor, and set the sampling rate to 15000 and up threshold to 98, ui gets a speed boost.
Click to expand...
Click to collapse
Sometimes I would have to tap twice on an icon to get it open.. Could be that I was taping too quick before the page could load? idk. But it seems better now. It wasn't thaaaat bad though.
data speed tweaks have got me nothing . maybe worse sometimes
Well...I suppose this isn't devvin, but, I learned a little about build.prop modifications from the devs and experience on my Acer Iconia A100. Soooo, I decided to share a few tweaks that have made me notice some difference in performance.
Here is a cut of the lines I added into the build.prop:
============================================================================
# Added by justjackyl#
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapstartsize=8m
debug.performance.tuning=1
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
pm.sleep_mode=1
ro.config.nocheckin=1
ro.ril.disable.power.collapse=1
video.accelerate.hw=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=150
=============================================================
This should give a slight boost on overall responsiveness, video performance, slight memory performance to the dalvik VM, and decrease wirelesss canning to save battery, as well as boost wireless performance and throuput, as well as possible power saving across the board (only slight increase, say 5-10% MAX so don't expect huge savings!)
Anyone willing to test with me? These tweaks really pumped life into my Tegra 2 tablet, and seem to being doing the same, while being stable so far, on my G2x.
To use the mod, you just need to use a root access file browser, browse to system, rename the current build.prop to build.prop.bak and copy and paste in the build.prop.mod one. Just make sure whichever one you are using, it is named build.prop with no extensions, so rename build.prop.mod to build.prop, and same to restore your back up original.
Than boot into recovery, wipe cache and dalvik cache, reboot and good to go.
Your first couple reboot cycles may be slower than normal as dalvik cache is rebuilding.
File----> justjackyl's build.prop mod for G2x
Posting this to see it in tapatalk and start trying it...!
ready, i put it after the V6 build.prop entries... only thing that i dont have used are the signal mods becouse v6 already have imput different values...
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
Click to expand...
Click to collapse
DankoFGL said:
Posting this to see it in tapatalk and start trying it...!
Click to expand...
Click to collapse
This should work on any CM7.2 ROM, maybe GB. I'll test that later.
It will not brick or cause bootloop on a CM7.2 ROM.
i use last cm7 nightly and worked well...
DankoFGL said:
Posting this to see it in tapatalk and start trying it...!
ready, i put it after the V6 build.prop entries... only thing that i dont have used are the signal mods becouse v6 already have imput different values...
Click to expand...
Click to collapse
I've actually never even used V6, so now I feel sorta stupid because I suppose most my tweaks are there. lol
Not, not all your tweaks are there, i use all of the twaks that you posted with the exception of the net edits
Enviado desde mi LG-P999 usando Tapatalk 2
DankoFGL said:
i use last cm7 nightly and worked well...
Click to expand...
Click to collapse
So you did notice a difference?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Let me test it for one or two days, i getting a litle better battery performance while sleeping, also my max events per sec are 200 and worked better than 150 at scrolling
Enviado desde mi LG-P999 usando Tapatalk 2
DankoFGL said:
Let me test it for one or two days, i getting a litle better battery performance while sleeping, also my max events per sec are 200 and worked better than 150 at scrolling
Enviado desde mi LG-P999 usando Tapatalk 2
Click to expand...
Click to collapse
Thanks, I'll keep that in mind.
I wonder if it may be a difference between Faux054 and Trinity158
Has you see any difference between this two kernels?
Enviado desde mi LG-P999 usando Tapatalk 2
DankoFGL said:
Has you see any difference between this two kernels?
Enviado desde mi LG-P999 usando Tapatalk 2
Click to expand...
Click to collapse
In contrast to this mod?
Or between the two kernels themselves?
With or without the mod, talk.about your experience
Enviado desde mi LG-P999 usando Tapatalk 2
DankoFGL said:
With or without the mod, talk.about your experience
Enviado desde mi LG-P999 usando Tapatalk 2
Click to expand...
Click to collapse
Well...the mod itself is in testing, as these mods worked on a Tegra 2 tablet, but may not work so well for this Tegra 2 phone.
As for the kernels...
I started modding in Jan 2012 and faux was the first GB kernel I ever found, and so I kinda became a faux fanboy when going for CM7 ROMs.
I've used Trinity, but not much experience with the ELP series. (cricketAC intro'd me to those)
I've used faux and can't even remember how old.
Both SOD randomly. I was able to control it more with faux.
Both random reboot, not often. I found faux OOM Panic and reboot more often than Trinity, but I don't multi tasks too hard, so I kept it in control, but faux would lag like an SOB sometimes.
Both OC nicely, but I prefer faux over Trinity in this case. Faux offers more steps in between frequencies than the Trinity I used, while both obtained an OC of >=1.5GHz.
The steps in frequencies are important to me as An underclock at 750MHz than next step is 1GHz, with Trinity, or an underclock of I think 654MHz and steps to 816Mhz, 912MHz and 1GHz, as with faux.
With the steps being laid out, I had better battery with faux as it had more room to play with frequency steps than Trinity. If you only can jump from 750 to 1Ghz when 750 wasn't enough, than your using more juice than if you jumped from 654 to 816 to 912 and CPU finds 912 was enough, well you didn't hit 1GHz and saved a little bit more juice.
So faux wins in battery.
But, faux does not like to OC above 1.4MHz IMO as it heats up so fast >1.4GHz it freezes.
Trinity will sustain itself much longer at >=1.5GHz much longer before the overheat freeze.
It is really hard to pick. IMO
Faux
Pros: Battery, OC in smaller steps possible, great performance in gaming environment (just one large single task), less SOD than trinity
Cons: Overheats quicker at OC, seems to panic more in multi task situations, more random reboots than Trinity
Trinity
Pros:Smoother multi taks performance, more stable at higher OC speeds, less random reboots than faux
Cons: Consumes more battery, less tweaking OC steps, more SODs than faux
I think it really comes down to personal use. These are just my experiences for my uses. Results vary.
Okay, i've to say... that is one of the best explaniations post of the kernels i've readed, so thanks you, i will stay with faux more time according what you say...
Thanks you
Enviado desde mi LG-P999 usando Tapatalk 2
justjackyl said:
Well...I suppose this isn't devvin, but, I learned a little about build.prop modifications from the devs and experience on my Acer Iconia A100. Soooo, I decided to share a few tweaks that have made me notice some difference in performance.
Here is a cut of the lines I added into the build.prop:
============================================================================
# Added by justjackyl#
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapstartsize=8m
debug.performance.tuning=1
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
pm.sleep_mode=1
ro.config.nocheckin=1
ro.ril.disable.power.collapse=1
video.accelerate.hw=1
wifi.supplicant_scan_interval=180
windowsmgr.max_events_per_sec=150
=============================================================
This should give a slight boost on overall responsiveness, video performance, slight memory performance to the dalvik VM, and decrease wirelesss canning to save battery, as well as boost wireless performance and throuput, as well as possible power saving across the board (only slight increase, say 5-10% MAX so don't expect huge savings!)
Anyone willing to test with me? These tweaks really pumped life into my Tegra 2 tablet, and seem to being doing the same, while being stable so far, on my G2x.
To use the mod, you just need to use a root access file browser, browse to system, rename the current build.prop to build.prop.bak and copy and paste in the build.prop.mod one. Just make sure whichever one you are using, it is named build.prop with no extensions, so rename build.prop.mod to build.prop, and same to restore your back up original.
Than boot into recovery, wipe cache and dalvik cache, reboot and good to go.
Your first couple reboot cycles may be slower than normal as dalvik cache is rebuilding.
File----> justjackyl's build.prop mod for G2x
Click to expand...
Click to collapse
These tweaks were posted 5-6 months back, and there is another thread for them too. They are fine, not a major improvement though.....
old thread: http://forum.xda-developers.com/showthread.php?t=1806868
5 hours of battery with always the screen on and using is good?
Enviado desde mi LG-P999 usando Tapatalk 2
DankoFGL said:
5 hours of battery with always the screen on and using is good?
Enviado desde mi LG-P999 usando Tapatalk 2
Click to expand...
Click to collapse
Your battery life is not due to these tweaks...I`ve tried them a long ago.Trust me on this one
BigDig said:
These tweaks were posted 5-6 months back, and there is another thread for them too. They are fine, not a major improvement though.....
old thread: http://forum.xda-developers.com/showthread.php?t=1806868
Click to expand...
Click to collapse
That one is for stock GB 2.3.4, OP states.
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
justjackyl said:
That one is for stock GB 2.3.4, OP states.
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
If you scroll the pages, they posted an cm7.2 buid prop also. The tweaks are fine, but nothing magnificent....
BigDig said:
If you scroll the pages, they posted an cm7.2 buid prop also. The tweaks are fine, but nothing magnificent....
Click to expand...
Click to collapse
Oh well. I tried.
Sometimes we overlook things on accident ...
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Yesterday, I noticed an improvement under low light conditions, by switching over to mdp composition type, instead of c2d, without needing picture stabilization.
Here's a preview of my build.prop setup with MDP (mobile display processor) active.
Code:
debug.sf.hw=1
debug.sf.swaprect=1
ro.sf.compbypass.enable=0
debug.egl.hw=1
debug.egl.buffcount=4
debug.gr.swapinterval=0
debug.composition.type=mdp
persist.hwc.mdpcomp.enable=true
persist.sys.composition.type=mdp
debug.mdpcomp.maxlayer=0
debug.disable.bwc=1
debug.mdpcomp.logs=0
debug.mdpcomp.maxpermixer=-1
debug.mdpcomp.mixedmode.disable=1
debug.mdpcomp.idletime=0
debug.qctwa.preservebuf=1
debug.qctwa.statusbar=1
com.qc.hardware=1
debug.qc.hardware=1
dalvik.vm.heapsize=36m
debug.hwc.dynThreshold=1.5
dev.pm.dyn_samplingrate=1
dev.pm.dyn_sample_period=500000
persist.demo.hdmirotationlock=false
The attachments below show the improvement.
Impressive Quadrant Score
I've also gotten 25000+ consistently with this modification. I'm a photographer, so I'm very happy with the Galaxy S5's performance now. I do a lot of multimedia multitasking on the go and at times the phone lagged pretty bad. The battery has improved as well. Here are a few more build.prop modifications I'm using that may contribute to the camera and system performance.
Code:
ro.hwui.panel_bit_depth=32
hwui.use_gpu_pixel_buffers=true
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,m=y,o=v
Here's my Quadrant score screenshot. ☺
I'm not quoting your long op, but those images look exactly the same!
ldeveraux said:
I'm not quoting your long op, but those images look exactly the same!
Click to expand...
Click to collapse
wat
you should look on a computer screen
tygib said:
wat
you should look on a computer screen
Click to expand...
Click to collapse
And you think MDP looks better? OK good luck with that...:good:
ldeveraux said:
And you think MDP looks better? OK good luck with that...:good:
Click to expand...
Click to collapse
I never said anything about either one looking better than the other. I commented on you saying they look exactly the same, which they don't. Congrats on being a sarcastic dumbass when you're wrong. :good:
tygib said:
I never said anything about either one looking better than the other. I commented on you saying they look exactly the same, which they don't. Congrats on being a sarcastic dumbass when you're wrong. :good:
Click to expand...
Click to collapse
I don't care
ldeveraux said:
I don't care
Click to expand...
Click to collapse
You cared enough to type out a reply after hitting quote reply, so obviously you do care. Thanks for trying though.