Related
Hi all,
I've been a faithful WM user until I saw the beautiful work that matt (xandroid) has been doing. I followed his work since August of last year, and had Android on my touch pro2 (sprint).
I love everything about the work, but low battery part is just a killer for me. The latest Tiad version of froyo only lasts about 8 hours top (with minimum use - just email sync). I think Xandroid (FRX04) is lasting about 9 hours.
I keep going back and forth between FRX03/04 and Froyo work made by Tiad8. What are the relationship between these two work? I know the kernel is the same, but which is the one to go?
Battery life wise, are they any different (one better than the other)? or is that a kernel problem still? Has anybody been successful to run android on rhodium for all day with specific (old) kernel? As you can see, I don't care about camera, bluetooth, and etc.
As a user, I just want my phone to last a day for me. I work from 7 AM to 5 PM. As of right now, my phone won't last unless I charge it through USB during the day.
Let me know! Thanks all.
Mike
Well I dont think that we can compare the job of this 2 guys, tiad is triying to give us the missing parts like a good 3d and camera. and mathews is working righ know on stability and a ported version, both works are great, and im testing rightnow the FRX04 the battery last much longer than other builds. and i haven´t to hardreset the phone even once. on my rhod 500. working with GSM.
Sorry if I came out like comparing two works. I just wanted your two cents on battery; that's all.
Thanks!
There really is no difference with tiad8's build AFAIK. He just takes the latest and bundles them together for newbies. I wish he wouldn't name it different, as that makes it seem like it's completely different - when in reality the differences are minor - you can achieve the same build by dropping in the appropriate files.
With that said, battery life improvements are all going to happen at the kernel level. So you can take whatever build, and drop in a different kernel to improve battery life.
At this time, WisTilt2's test kernel is going to get you the best battery life. He's working on the rest of the devices so he can commit his code (basically our phone's are not sleeping correctly, the panel is still getting/sucking power even tho the screen appears to be off)
See the test kernel thread here.
Thanks for the post, Arrrghhh. You are talking about the wistilt2 kernel stripped version right?
I will try that with FRX04.
Thanks.
mike92585 said:
Thanks for the post, Arrrghhh. You are talking about the wistilt2 kernel stripped version right?
I will try that with FRX04.
Thanks.
Click to expand...
Click to collapse
Not sure what you mean by stripped version. I see now... that's down below in F22's post - focus on the first post . Just download the kernel-pack that's attached to the first post.
There was a discrepancy on the modules that needed to be included. It was sorted out, and the first post has the newest test kernel that WisTilt2 has provided me with.
I think they are "similar", but I must say that I always have issues with XDAndroid... It hangs when appears the Android home screen and I must reboot like 50 times before it works ok, also it's a little slow...In contrast, FroyoX always worked from the first time and is super fast without overclocking...That's my opinion!
nickleby said:
I think they are "similar", but I must say that I always have issues with XDAndroid... It hangs when appears the Android home screen and I must reboot like 50 times before it works ok, also it's a little slow...In contrast, FroyoX always worked from the first time and is super fast without overclocking...That's my opinion!
Click to expand...
Click to collapse
I'd honestly want to know the difference between the system image FRX04 and the 'Froyo X' system image. If there is a tangible difference, we need to change whatever tiad8 changed!
I wish that dude would work with us instead of in parallel to our work....
mike92585 said:
Hi all,
I've been a faithful WM user until I saw the beautiful work that matt (xandroid) has been doing. I followed his work since August of last year, and had Android on my touch pro2 (sprint).
I love everything about the work, but low battery part is just a killer for me. The latest Tiad version of froyo only lasts about 8 hours top (with minimum use - just email sync). I think Xandroid (FRX04) is lasting about 9 hours.
I keep going back and forth between FRX03/04 and Froyo work made by Tiad8. What are the relationship between these two work? I know the kernel is the same, but which is the one to go?
Battery life wise, are they any different (one better than the other)? or is that a kernel problem still? Has anybody been successful to run android on rhodium for all day with specific (old) kernel? As you can see, I don't care about camera, bluetooth, and etc.
As a user, I just want my phone to last a day for me. I work from 7 AM to 5 PM. As of right now, my phone won't last unless I charge it through USB during the day.
Let me know! Thanks all.
Mike
Click to expand...
Click to collapse
I was having a similar experience with my Sprint TP2. I updated to FRX04 and then the camera testing kernel but my battery life was about 6-8 hours.
I had it set to disable satellites but left "Use Wireless Networks" enabled and then last night I turned off all of the location options. Today I'm at 8 hours and the battery is only down to 68%. The other thing I looked at is that if you have Facebook, Twitter, Fourquare or any other apps running that any auto-refresh/updates/notifications are disabled.
Hopefully this helps you out. I've gone from hating my phone with it's constant lag in WM to loving using my phone with Android.
Mizofizo, let me see what you exactly did.
Since you use sprint and also in boston, we are pretty much on the same boat. However, no matter what I do, I can't get my battery to last all day. I always have both use wireless networks off and location options off as well. No facebook or nothing.
I am now at a point where I am even afraid to turn the screen on because of the battery drain.
Could you email me the startup.txt or pm me the detail? So you are using the stock FRX04 with which kernel are you running? Are you running the latest 1253?
This is my startup.txt that I have been using.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=1 physkeyboard=rhod210 hw3d.force=1 htc_battery_smem.fake=1 north_am_dialing=1 pm.sleep_mode=1"
boot
Note pm.sleep_mode=1.
Thanks in advance.
Mike
mike92585 said:
Mizofizo, let me see what you exactly did.
Since you use sprint and also in boston, we are pretty much on the same boat. However, no matter what I do, I can't get my battery to last all day. I always have both use wireless networks off and location options off as well. No facebook or nothing.
I am now at a point where I am even afraid to turn the screen on because of the battery drain.
My email is . Could you email me the startup.txt or pm me the detail? So you are using the stock FRX04 with which kernel are you running? Are you running the latest 1253?
This is my startup.txt that I have been using.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 [color=red][b]msmts_calib=0x9f.0x39a.0x35c.0x78[/color][/b] msmvkeyb_toggle=off [color=red][b]pmem.extra=1[/color][/b] gsensor_axis=2,1,3 force_cdma=1 [color=blue][b]physkeyboard=rhod400[/color][/b] hw3d.force=1 [color=red][b]htc_battery_smem.fake=1[/color][/b] north_am_dialing=1 pm.sleep_mode=1"
boot
Note pm.sleep_mode=1.
Thanks in advance.
Mike
Click to expand...
Click to collapse
I'd remove your email from the post - trust me, you'll get a ton of spam because of it. Just do <email> at <domain> dot com if you ever feel the need to put your email address into a forum (which I wouldn't do either )
Anyhoo, I highlighted in red/bold some of the commands you should consider removing. Especially the htc_battery_smem.fake!
Oh, and if you're on Sprint - is it a Sprint-branded phone? If so, that's a RHOD400. RHOD210 wouldn't even work on Sprint, as there's no CDMA radio in that device .
mike92585 said:
Mizofizo, let me see what you exactly did.
Since you use sprint and also in boston, we are pretty much on the same boat. However, no matter what I do, I can't get my battery to last all day. I always have both use wireless networks off and location options off as well. No facebook or nothing.
I am now at a point where I am even afraid to turn the screen on because of the battery drain.
Could you email me the startup.txt or pm me the detail? So you are using the stock FRX04 with which kernel are you running? Are you running the latest 1253?
This is my startup.txt that I have been using.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=1 physkeyboard=rhod210 hw3d.force=1 htc_battery_smem.fake=1 north_am_dialing=1 pm.sleep_mode=1"
boot
Note pm.sleep_mode=1.
Thanks in advance.
Mike
Click to expand...
Click to collapse
I would delete the options that arrrghhh specified.
I'm running FRX04 with the camera testing kernel. My startup.txt is as follows:
set RAMSIZE 0x10000000
set RAMADDR 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off force_cdma=1 gsensor_axis=2,1,3 pm.sleep_mode=1 hw3d.force=1 physkeyboard=rhod400 board-htcrhodium.is_cdma=1"
boot
Note that I don't have a rel_path since I put everything in the root of my SD card.
With my current config, yesterday at about 16 hours of use (including wifi and gps) I had about 38% battery left.
Thanks to both.
I finally see the green led light on my tp2. =D
Hopefully I will get some long battery life now... I will post back once I do!
I have used the startup.txt details above but I still have issues with my phone waking up! The light never turns green and it will not wake up after a while of not being used.... any suggestions?
Using XDAndroid FRX04 1/23/2011
AT&T Tilt2
Kernel 1250
scattaman said:
I have used the startup.txt details above but I still have issues with my phone waking up! The light never turns green and it will not wake up after a while of not being used.... any suggestions?
Using XDAndroid FRX04 1/23/2011
AT&T Tilt2
Kernel 1250
Click to expand...
Click to collapse
Why are you using kernel 1250 instead of 1253 or the one included in FRX04? I'd try just using FRX04 as is. Make sure that all unneeded syncing/services are turned off.
scattaman said:
I have used the startup.txt details above but I still have issues with my phone waking up! The light never turns green and it will not wake up after a while of not being used.... any suggestions?
Using XDAndroid FRX04 1/23/2011
AT&T Tilt2
Kernel 1250
Click to expand...
Click to collapse
SoD issues still ensue - devs are looking into a potential resolution/root cause.
mizofizo said:
Why are you using kernel 1250 instead of 1253 or the one included in FRX04? I'd try just using FRX04 as is. Make sure that all unneeded syncing/services are turned off.
Click to expand...
Click to collapse
Thanks but I've tried all the available kernels... including the one that came with FRX04... its just really annoying because it happens almost everytime I pput my phone down for 5 minutes
arrrghhh said:
SoD issues still ensue - devs are looking into a potential resolution/root cause.
Click to expand...
Click to collapse
Well its good to know that I'm not the only one...
scattaman said:
Thanks but I've tried all the available kernels... including the one that came with FRX04... its just really annoying because it happens almost everytime I pput my phone down for 5 minutes
Click to expand...
Click to collapse
It does happen, but it shouldn't be that frequent. Are you running any apps when you put your phone down...? Post your startup.txt too, just to make sure there's nothing funky in it.
Also, have you tried NOT OC'ing? Are you on pm.sleep_mode=1?
For those of you with decent battery life, how do you setup android when running for the first time?
slapshot30 said:
For those of you with decent battery life, how do you setup android when running for the first time?
Click to expand...
Click to collapse
What do you mean? I formatted my SD card, unrared FRX04 to the root of my SD card. Changed the conf file to point to the root and configured my startup.txt. Afterward, I setup the camera kernel as well. That's about it.
Support ended. Soon as app on market.
First
This looks interesting, nice to see you've got the files for Romania as well
Going to test it tomorrow (almost midnight).
Will test this in the Netherlands with JVS modem and Tornado ROM.
I will try this for sure. In case i don't see any difference.. is there a way to remove it?
I will try it tomorrow and reply in the evening.
Cheers.
will try it sounds great... thx!!
EDIT: i'v tested here in malaysia.. works great!!! locking fast... but i guess my old configuration works better' you could look at gps.conf i'm using here:
Code:
NTP_SERVER=my.pool.ntp.org
NTP_SERVER=0.my.pool.ntp.org
NTP_SERVER=1.my.pool.ntp.org
NTP_SERVER=2.my.pool.ntp.org
NTP_SERVER=3.my.pool.ntp.org
NTP_SERVER=0.asia.pool.ntp.org
NTP_SERVER=1.asia.pool.ntp.org
NTP_SERVER=2.asia.pool.ntp.org
NTP_SERVER=3.asia.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 5
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=1
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=0
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.host.com or IP
# SUPL_PORT=1234
SUPL_HOST=supl.google.com
SUPL_PORT=7276
# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234
#################################
##### EXTRA SETTINGS #####
#################################
# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1
#################################
##### AGPS Carrier settings #####
#################################
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE
#########################################
##### GPS QUICKEST FIX V1.3 By RJLM #####
#########################################
nice work! Giving it a try for sure.
I've read about this fix on some SGS2 forum, didn't imagine it would result on SGS1. It has something to do with using sony's gps definitions... someone tried to use x10mini gsp definitions (xtra.bin info and supl host) with same good results.
Thanks for the effort, gonna give it a try. In case anyone has doubts about it, just backup /system/bin/xtra.bin and /system/etc/gps.conf before applying the zip.
EDIT: just realized that there's no xtra.bin on /system/bin on stock JVS rom. Never looked for this file before, so don't know if its usual on sammys roms.
First impressions, faster gps lock indeed but not that much compared with previous conf. Need to make more tests (namely inside the city) because I think position accuracy got slight worse, but it could be placebo effect.
Setup: MDrive in Stock jvs rom + jvs modem + talon kernel. Portugal
Taptalked... holding it the right way.
Thanks for the great work! Will test Malaysia and report later!
No love for Chile?
Awesome, simply awesome.
Tried on both GalaxyS and Galaxy Tab7.
Locked within seconds, and that too from inside my room.
Great Job!
Sent from my GT-P1000 using xda premium
Tested for over an hour (running) no difference in accuracy.
Lock is fast, but mine was always fast anyway.
works differently in different devices & settings and different locations. Edited later.
WOW. I tried this in Greece, and I can already see a different behavior.
I went to Google Maps and tried turning my Galaxy around a bit, and to my surprise, the indicator was turning around almost in real time. HUNDREDS of times faster than with the regular GPS setting. And I had even set the satellites to "Europe" with SGS Tools. But this one seems to be working a lot LOT better. I'll have to try it outside to tell you more about it!
Thank you for your time and effort making this!
Does it work on Cyanogen?
@yoshinatsu nextweek Next week will bring further versions(version A default ,version B,version C version D,version E). It is not possible to create TWEAK for the whole world. Users can try and choose which version is best for him. Just takes time. Thanks
@farid993 YES
PFittech said:
@yoshinatsu nextweek Next week will bring further versions(version A default ,version B,version C version D,version E). It is not possible to create TWEAK for the whole world. Users can try and choose which version is best for him. Just takes time. Thanks
Click to expand...
Click to collapse
Haha, no it was a positive comment, sorry if it sounded weird.
Your fix seems to be working extremely well so far. It's certainly an big improvement over the regular GPS signal.
Big thanks PFittech, works great, lock in seconds. Work fine in Bulgaria
Awesome work. Huge improvement in Singapore.
Sent from my GT-I9000 using Tapatalk
Improvement seen from Switzerland. Awsome
I'm still on stock ROM wait for 1.28 version of ARHD. So I decided to find some tweaks to improve the performance mainly smoother scrolling. You need Root for this to work. Not sure if all of these tweak properly work or not. These tweaks are which I used in my older device change some of the values
I didn't create these tweaks. I just found them and still testing. I take no credit for these all credit goes to amazing developers of XDA Community.
Open your Build.Prop and add these values and restart your device. Make sure you take a backup of your current Build.prop.
I take no responsibility for what ever happens. Do it on your own risk
Code:
#
# Tweaks by ShyamSasi
#
windowsmgr.max_events_per_sec=500
ro.kernel.android.checkjni=0
ro.max.fling_velocity=4000
video.accelerate.hw=1
debug.sf.hw=1
# Faster transfer rate for net connections
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
# 3G TurboCharger Enhancment!
dhcp.tiwlan0.dns1=8.8.8.8
dhcp.tiwlan0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.tiwlan0.dns1=8.8.8.8
net.tiwlan0.dns2=8.8.4.4
net.tcp.buffersize.default=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.wifi=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,87380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
net.tcp.buffersize.umts=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.gprs=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.edge=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.hspa=6144,87380,524288,6144,16384,262144
ENFORCE_PROCESS_LIMIT=false
MAX_SERVICE_INACTIVITY=
MIN_HIDDEN_APPS=
MAX_HIDDEN_APPS=
CONTENT_APP_IDLE_OFFSET=
EMPTY_APP_IDLE_OFFSET=
MAX_ACTIVITIES=
ACTIVITY_INACTIVE_RESET_TIME=
Disable CPU RenderingI'm not responsible for anything that goes wrong with your device, you know the risks of flashing files to root. Make a backup first.It's been confirmed that this tweak on Froyo based roms, causes an endless bootloop and doesn't seem to work. Although it's been confirmed to work on Harmonica. So from what I know it will work best on GB and ICS (JB need tests).
I've red this article so i want purpose this method for tweak more smoothness from our beloved HD2!
XDA-news
OP words:
"I started this thread over at the LG-VM670 forums at Android Central. I thought maybe it was about time I share it over here on XDA since it's a pretty great tweak and it works without any added issues.
But keep in mind, if your phone doesn't have adreno200 gpu drivers, this won't work and could probably cause an endless bootloop. Now that that's covered, read up and do this carefully, this will not work on every device and is only meant for adreno200. I may have another tweak up my sleeve, but I need a device with something other than adreno200, such as tegra, to test it out on, which I don't have at the moment. Anyway, this worked out quite well for the Optimus V users, I believe it works on Xperia devices as well and it's been confirmed to work on Galaxy SIII. I'll try my very best to keep this thread updated, I don't have a ton of devices to test this on so I'd really appreciate the feedback so I can update the main post and list whatever devices this tweak works with (nobody wants a endless bootloop, so let's inform each other) oh and before I forget.. MAKE A NANDROID BACKUP ALWAYS!! Just in case
I found this tweak while trying to look for a loopy smothness tweak made for ICS, but I ended up finding something better than loopy smoothness, a guide to disable CPU rendering. With this tweak you can take full advantage of your device's GPU. In other words you disable software rendering and enable hardware rendering instead"
Original thread
(related to) http://forum.xda-developers.com/showthread.php?t=1575984
Confirmed working on:
- BobZhome CM9 [VM670]
- quattrimus CM9 [VM670]
- mrg666 MiRaGe IHO [VM670]
- BobZhome IHO [VM670]
- Galaxy SIII
- Xperia devices
- Tegra Device
- any device with working adreno200 drivers (in this case my LG myTouch 4G is a good example, it worked marvelously and more noticeably on this device)
HOW TO
(thanks for the summary to thierry_hd2)
1) MAKE A NAND BACKUP OF YOUR ROM. Just in case something would go wrong
2) To disable CPU rendering the ONLY things to do are:
- with a file manager with root access go to system/lib/eg
- open the file egl.cfg. DELETE everything inside the file but keep this line: 0 1 adreno200
- rename libGLES_android.so from egl folder. Don't delete it so if there is an issue with your ROM you can revert back to this file.
- REBOOT
That's all you have to to to disable CPU rendering. Depending on the ROM you are using you'll see some improvements or not (compile the poll on the top of the page)
TEST (for return back) Flashable .zip with original ROM files (not tested yet - for who have black screen, try it before recovery) TEST
(Thanks to blacksn)
http://forum.xda-developers.com/attachment.php?attachmentid=1331025&d=1347811207
MY IMPRESSIONS:
I'm trying it now on Tytung V2.7 and seems to works very well.!! :good: this trick can show the limit of benchmarking system (they will give you low score respect the new general smoothness).
Some feedback comes from some users that saw how with this hack, they can now play with GTAIII or other games more fluently.
In addiction to this explanation, disabling CPU rendering reduce battery juice!
Set the permission to rw-r--r-- for the egl.cfg file.
What might you benefit from? So far this is what I noticed.
- performance boost
- speed boost
- increased responsiveness
- better audio quality
- apps such as Facebook that would become slow and unresponsive are suddenly blazing fast
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Some universal Build.Prop Tweaks
If you want, you can apply some extra tweaks. These tweaks will help your HD2 feel even smoother and should improve battery life. Again depending on the level of optimisation of your ROM, you'll experience or not improvements.
- Just to be sure I could go back to the original build.prop; for first made a backup of it!!!
- Then I just opened the build.prop file (in the system folder) and made all the modifications manually. Some of the tweaks where already included, other tweaks had different values!
We need help to test & describe the strings. I'm convinced that using some of them, we can reach new level of optimization.
Thinks You need to know is:
1. All options starting with ro.ril is applied only once during boot
2. Most of other options can be applied after phone booted using "adb shell" or terminal direcly on phone with command "setprop option"
3. All prop settings can be read with command "getprop" and can be redirected to file with command "getprop >> /mnt/sdcard/file.txt"
4. Better/easy way is to rename file and not delete while testing. In case You renamed file and go wrong always can put phone in recovery, mount system, connect phone to pc and restore/rename affected file. This will save you a lot of time and nerves.
(http://forum.xda-developers.com/showpost.php?p=31690267&postcount=89)
After some tests i reached new scores on our known benchs:
Antutu: 3180 (1155Mhz Smartass V2)
Quadrant: 1215 (1155Mhz Smartass V2)
Vellamo: 966 (near Galaxy Note and Galaxy Nexus)
Open build.prop (using Build Prop Editor from market) and modify or add the following strings (if they are not just included). All these settings/tweaks are rom and Android version independent.
dalvik.vm.dexopt-flags m=y
CHANGE TO
dalvik.vm.dexopt-flags m=y,o=v,u=y
then Save & Reboot
In this mode we have set up app optimization for unicore...you set u=n only if you are using a device up to 2 cores.
#Render UI with GPU
debug.sf.hw=1
#debug.composition.type=gpu
debug.composition.type=c2d
debug.performance.tuning=1
debug.enabletr=true
debug.qctwa.preservebuf=1
dev.pm.dyn_samplingrate=1
video.accelerate.hw=1
ro.vold.umsdirtyratio=20
debug.overlayui.enable=1
debug.egl.hw=1
ro.fb.mode=1
hw3d.force=1
persist.sys.composition.type=c2d
persist.sys.ui.hw=1
ro.sf.compbypass.enable=0
ro.sf.lcd_density=240
debug.fb.rgb565=0
# Improve overall media quality
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.media.cam.preview.fps=0
ro.media.codec_priority_for_thumb=so
# This is a high density device with more memory, so larger vm heaps for it.
# and some dalvik speedups
dalvik.vm.heapsize=40m
# Get more RAM and faster responses by disabling verify-bytecode
#dalvik.vm.dexopt-flags=v=n,o=v,m=y
dalvik.vm.dexopt-flags=m=y,o=v,u=y
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-data-only=1
dalvik.vm.checkjni=0
dalvik.vm.checkjni=false
dalvik.vm.check-dex-sum=false
dalvik.vm.jniopts=warnonly
# gecata test
dalvik.vm.check-dex-sum=false
# gecata test
dalvik.vm.jmiopts=forcecopy
# Turn on Just In Time in dalvik virtual machine
dalvik.vm.execution-mode=int:jit
dalvik.vm.lockprof.threshold=500
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# For the default value of agps
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
# For HSDPA low throughput
ro.ril.disable.power.collapse=1
# For sensor sleep control
ro.ril.sensor.sleep.control=1
ro.wifi.hotspotUI=1
ro.tether.denied=false
# enable/disable data in roaming
#ro.com.android.dataroaming=true
ro.com.android.dataroaming=false
# For quick boot mode
# persist.sys.shutdown.mode=hibernate
ro.config.hw_quickpoweron=true
# Hide debuging icon from taskbar
persist.adb.notify=0
persist.service.adb.enable=1
# Enable egl profiler - enable harware egl profile
debug.egl.profiler=1
#Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-record=true
# Decrease time for screen off/on durrign call
ro.lge.proximity.delay=25
mot.proximity.delay=25
ro.mot.buttonlight.timeout=0
# Decrease dial out delay
ro.telephony.call_ring.delay=0
ring.delay=0
# Disable WiFi calling for EU models
ro.ril.enable.ganlite=0
#Noise Cancellation Off
htc.audio.alt.enable=0
htc.audio.hac.enable=0
### Kernel Tweaks
# Disable error checking (Should speed things up a bit)
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
### Allow purging of assets (System can free more Ram when needed) ###
persist.sys.purgeable_assets=1
# Disable strict mode checking
persist.android.strictmode=0
# Disable the zygote loader
ro.wmt.blcr.enable=0
# Keep launcher in memory
ro.HOME_APP_ADJ=1
# Won't let memory managers to kill Launcher
ro.PERCEPTIBLE_APP_ADJ=2
#ro.HOME_APP_MEM=2048
# Tweaks for battery saving
pm.sleep_mode=1
usb_wakeup=enable
proximity_incall=enable
power_supply.wakeup=enable
ro.config.hw_power_saving=1
ro.config.hw_fast_dormancy=1
ro.config.hw_quickpoweron=true
persist.sys.use_dithering=0
#improve battery under no signal -- need test
ro.mot.eri.losalert.delay=1000
# For sensor sleep control
ro.ril.sensor.sleep.control=1
# Qualcomm display settings -- Video acceleration and HW degugging
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.qc.hardware=true
com.qc.hardware=true
#Bravia Engine Service
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
# Xloud Engine
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
media.xloud.enable=1
media.xloud.supported=true
# More precisely incall volume control
ro.config.vc_call_vol_steps=15
# Increase overall scrool speed and enable rotation to 270 degree
windowsmgr.max_events_per_sec=170
windowsmgr.support_rotation_270=true
# Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
### Disable Logers (safe battery + performance gain)
### Disable checkin services, error reporting and logging
ro.config.htc.nocheckin=1
ro.config.nocheckin=1
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
### Touch tunning ###
touch.presure.scale=0.001
#ro.min_pointer_dur=
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
# Better signal reception
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
# Modify MTU from 1500 to 1472 on 3G network for speeding up
ro.ril.set.mtu1472=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=8
persist.data_netmgrd_mtu=1482
#net speed tweaks
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.hspda=4096,87380,256960,4096,16 384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,163 84,256960
# Google DNS Tweak -- fastest dns
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
RED= Suggested
PURPLE= Just inside or not useful
Using part of tweaked dalvik setting is not recommended, because whole section is result of many calculations and correlations in options. Also it is highly recommended after putting these setting in build.prop to delete cache and dalvik cache and after first boot to make power off and fix permissions in recovery.
Thx to all Devs that will give a hand
Thx to gecata & Pixelfreak for the list.
Thx to all users for feedback
Sounds really interesting, I'm definitely trying it out soon
Could you please correct the links so we don't have to edit them in address bar manually (showthread.php instead of show....php)?
Swamp_cz said:
Sounds really interesting, I'm definitely trying it out soon
Could you please correct the links so we don't have to edit them in address bar manually (showthread.php instead of show....php)?
Click to expand...
Click to collapse
Just correct them! Thx ^_^
Just tried it on my Barebone CM7.
Although the ROM is amazing fast, it seems that this tweak improves the performance.
With original config i had some slight lags in LancherPro. Now no more lags...
Anybody knows a proper way to test if this is working?
I have almost immediate results!
Cheers
Don't want to be a fun spoiler but some things are there for a reason
what's the negative side of this mod?
Swamp_cz said:
Sounds really interesting, I'm definitely trying it out soon
Could you please correct the links so we don't have to edit them in address bar manually (showthread.php instead of show....php)?
Click to expand...
Click to collapse
try to click on link instead of copy-paste...
pirlano said:
what's the negative side of this mod?
Click to expand...
Click to collapse
Its just editing the config file to read only the GPU. You will notice a huge improvement in day to day tasks. However benchmarks will go down. But that just proves how benchmarks don't mean crap after this i'm using my device lagfree! also internet experience is better than before.
Vellamo score: 939 using this trick.
Antutu: 3040 (1075Mhz) 3100 (1155Mhz)
Quadrant Score: 1134
this thing works for now on PARANOIDANDROID HD2 v1.5b ICS 4.0.4
tw1st3d83 said:
try to click on link instead of copy-paste...
Click to expand...
Click to collapse
I did click it, even the adress was broken. Now it's ok, because good guy devilpera64 already fixed that.
Swamp_cz said:
I did click it, even the adress was broken. Now it's ok, because good guy devilpera64 already fixed that.
Click to expand...
Click to collapse
I'm studing for some other build.prop string tweaks..maybe we can reach new performance level :good: i'm looking into all general thread of XDA for find someother things to add. Because surely other people discovered some general tips in other forum's region
Thanks for this, yes, benchmarks drop Down slightly (i have 3103 score at 1190 MHz with this tweak), but, it really improves perfomance. Thank you! \(°_°\)
Can we use the zip file from the original thread to install? And had anybody tried this ok CM7?
Sent from my HD2 using Tapatalk 2
mexicandroid said:
Can we use the zip file from the original thread to install? And had anybody tried this ok CM7?
Sent from my HD2 using Tapatalk 2
Click to expand...
Click to collapse
It's ok! but if you install it manually you are sure to do everything correct
Sorry I feel like tard but for the life of I can't seem to get the flash able zip.....it said to register android forum and I did but still just says attachment... no file. I know its me, could somebody lend me a hand the kids are making me nuts and I wanna try this before we leave lol
Edit sorry never mind just had to view thread in desktop mode, the zip showed then.
Sent from my NexusHD2 using xda app-developers app
its not an flashable zip. you must do it yourself.
I spent some time for build.prop tweaking. Here is it. The sections are self documented, but if You want I can explain more. All these settings/tweaks are rom and Android version independent.
#Render UI with GPU
debug.sf.hw=1
#debug.composition.type=gpu
debug.composition.type=c2d
debug.performance.tuning=1
debug.enabletr=true
debug.qctwa.preservebuf=1
dev.pm.dyn_samplingrate=1
video.accelerate.hw=1
ro.vold.umsdirtyratio=20
debug.overlayui.enable=1
debug.egl.hw=1
ro.fb.mode=1
hw3d.force=1
persist.sys.composition.type=c2d
persist.sys.ui.hw=1
ro.sf.compbypass.enable=0
ro.sf.lcd_density=240
debug.fb.rgb565=0
# Improve overall media quality
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.media.cam.preview.fps=0
ro.media.codec_priority_for_thumb=so
# This is a high density device with more memory, so larger vm heaps for it.
# and some dalvik speedups
dalvik.vm.heapsize=40m
# Get more RAM and faster responses by disabling verify-bytecode
#dalvik.vm.dexopt-flags=v=n,o=v,m=y
dalvik.vm.dexopt-flags=m=y,o=v,u=y
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-data-only=1
dalvik.vm.checkjni=0
dalvik.vm.checkjni=false
dalvik.vm.check-dex-sum=false
dalvik.vm.jniopts=warnonly
# gecata test
dalvik.vm.check-dex-sum=false
# gecata test
dalvik.vm.jmiopts=forcecopy
# Turn on Just In Time in dalvik virtual machine
dalvik.vm.execution-mode=int:jit
dalvik.vm.lockprof.threshold=500
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# For the default value of agps
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
# For HSDPA low throughput
ro.ril.disable.power.collapse=1
# For sensor sleep control
ro.ril.sensor.sleep.control=1
ro.wifi.hotspotUI=1
ro.tether.denied=false
# enable/disable data in roaming
#ro.com.android.dataroaming=true
ro.com.android.dataroaming=false
# For quick boot mode
# persist.sys.shutdown.mode=hibernate
ro.config.hw_quickpoweron=true
# Hide debuging icon from taskbar
persist.adb.notify=0
persist.service.adb.enable=1
# Enable egl profiler - enable harware egl profile
debug.egl.profiler=1
#Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-record=true
# Decrease time for screen off/on durrign call
ro.lge.proximity.delay=25
mot.proximity.delay=25
ro.mot.buttonlight.timeout=0
# Decrease dial out delay
ro.telephony.call_ring.delay=0
ring.delay=0
# Disable WiFi calling for EU models
ro.ril.enable.ganlite=0
#Noise Cancellation Off
htc.audio.alt.enable=0
htc.audio.hac.enable=0
### Kernel Tweaks
# Disable error checking (Should speed things up a bit)
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
### Allow purging of assets (System can free more Ram when needed) ###
persist.sys.purgeable_assets=1
# Disable strict mode checking
persist.android.strictmode=0
# Disable the zygote loader
ro.wmt.blcr.enable=0
# Keep launcher in memory
ro.HOME_APP_ADJ=1
# Won't let memory managers to kill Launcher
ro.PERCEPTIBLE_APP_ADJ=2
#ro.HOME_APP_MEM=2048
# Tweaks for battery saving
pm.sleep_mode=1
usb_wakeup=enable
proximity_incall=enable
power_supply.wakeup=enable
ro.config.hw_power_saving=1
ro.config.hw_fast_dormancy=1
ro.config.hw_quickpoweron=true
persist.sys.use_dithering=0
#improve battery under no signal -- need test
ro.mot.eri.losalert.delay=1000
# For sensor sleep control
ro.ril.sensor.sleep.control=1
# Qualcomm display settings -- Video acceleration and HW degugging
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.qc.hardware=true
com.qc.hardware=true
#Bravia Engine Service
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
# Xloud Engine
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
media.xloud.enable=1
media.xloud.supported=true
# More precisely incall volume control
ro.config.vc_call_vol_steps=15
# Increase overall scrool speed and enable rotation to 270 degree
windowsmgr.max_events_per_sec=170
windowsmgr.support_rotation_270=true
# Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
### Disable Logers (safe battery + performance gain)
### Disable checkin services, error reporting and logging
ro.config.htc.nocheckin=1
ro.config.nocheckin=1
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
### Touch tunning ###
touch.presure.scale=0.001
#ro.min_pointer_dur=
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
# Better signal reception
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
# Modify MTU from 1500 to 1472 on 3G network for speeding up
ro.ril.set.mtu1472=1
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=8
persist.data_netmgrd_mtu=1482
#net speed tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hspda=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
# Google DNS Tweak -- fastest dns
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
devilpera64 said:
I'm studing for some other build.prop string tweaks..maybe we can reach new performance level :good: i'm looking into all general thread of XDA for find someother things to add. Because surely other people discovered some general tips in other forum's region
Click to expand...
Click to collapse
Did someone try this on HTC HD2?
rikusuicide said:
its not an flashable zip. you must do it yourself.
Click to expand...
Click to collapse
It says right in the android forum link....things just got easier,here is a flash able zip if you don't want to do it manually... so I think it is. I just downloaded it and flashed successfully.
Sent from my NexusHD2 using xda app-developers app
FEATURES :
* Better Battery
- Deep Sleep Mode
- Scans WiFi Less Frequently (Saves Battery)
* Image Quality Increased
* Streams Video Faster
* Better Touch Response
* Faster Reboot
* Instant Call
- No Delay In Receiving/Making Calls
* Faster Launcher
- No/Very Little Lag
- Forces Launcher Into Memory
* Fixes FC Issues With Some Apps
* Fixes “Black Screen” Issue After Call
- Screen Appears Almost Instantly After Pulling Phone Away From Face
* Audio & Video Quality Increased
* Signal Tweaks
* Download & Upload Speed Increased
* Dalvic VM Tweaks
* Loads App Faster
* Frees More RAM
* Overall Performance Increased
And Many More ...
Click to expand...
Click to collapse
# Disable Error Checking
ro.kernel.android.checkjni=0
# Increase Quality Of MediaStreaming
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
# Disable BootAnimation
debug.sf.nobootanimation=1
#Force To Remain Launcher In Memory
ro.HOME_APP_ADJ=1
# Disable Waking Up Of Phone By Volume Buttons
ro.config.hwfeature_wakeupkey=0
# Off The Proximity Quiclky After Call
mot.proximity.delay=25
ro.lge.proximity.delay=25
# Signal Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
# NetSpeed Tweaks
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
# Google DNS Tweak
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# Photo And Video Quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100
# Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Scrolling Responsiveness
windowsmgr.max_events_per_sec=500
# Power Save Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
# Disables Debug Icon On Status Bar
persist.adb.notify=0
# Fast Reboot Allow purging of assets (System can free more Ram when needed)
persist.sys.purgeable_assets=1
Use Jit (Dalvik just-in-time compiler)
dalvik.vm.execution-mode=int:jit
# Increasing The Video Recording Quality
ro.media.enc.hprof.vid.bps=8000000
# Screen Rotate To 270 degree
windowsmgr.support_rotation_270=true;
# Increase VM Heap Size(resolve some fc's)
dalvik.vm.heapsize=64m
# Render UI With GPU
debug.sf.hw=1
# Increasing It Will Make Mobile Smoother
windowsmgr.max_events_per_sec=150
# Video Acceleration Enabled
video.accelerate.hw=1
# Increase Performance
debug.performance.tuning=1
# Disable Sending Usage Data
ro.config.nocheckin=1
# Deeper Sleep/Better battery life
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
# Ringing Will Start Immediately
ro.telephony.call_ring.delay=0
#Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
#wifi to scan less frequently
wifi.supplicant_scan_interval=180
#improve battery under no signal
ro.mot.eri.losalert.delay=1000
#makes apps load faster and frees more ram. (Edit exsisting line)
dalvik.vm.dexopt-flags=m=v,o=y
# Off The Proximity Quickly After Call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Download BulidProp editor from attach
Requirements: This app is compatible with 4.0 or newer and of course needs root access to write to your Android's /system directory.
I'm not responsible for any problem caused by editing the build.prop file. I've tested the app and haven't bricked my phones.
does it work on one x plus ?? Tslam ya hany
aliko007 said:
does it work on one x plus ?? Tslam ya hany
Click to expand...
Click to collapse
yes it's for android 4.x , good arabic
codexc said:
yes it's for android 4.x , good arabic
Click to expand...
Click to collapse
@codexc would these settings work on a stock rom or do I need to be on a custom rom?
I would advise anyone who posts this sort of tweaks to read http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/ and http://www.jeffmixon.com/examining-build-prop-tweaks-android-ics-comprehensive-guide-part-2/ to learn what does things and what does nothing
amirage said:
@codexc would these settings work on a stock rom or do I need to be on a custom rom?
Click to expand...
Click to collapse
yes, but some of works only on CM/AOSP
pandaball said:
I would advise anyone who posts this sort of tweaks to read http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/ and http://www.jeffmixon.com/examining-build-prop-tweaks-android-ics-comprehensive-guide-part-2/ to learn what does things and what does nothing
Click to expand...
Click to collapse
all tweaks in OP is works with android 4.x and up , i see your links and all tweaks has "BUSTED/CONFIRMED" there
regards
# Disable Error Checking
ro.kernel.android.checkjni=0
Click to expand...
Click to collapse
Busted. The checkJni default value is already false. Setting either property to false or 0 in your build.prop is simply redundant and will have no added effect on your device.
#Force To Remain Launcher In Memory
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
Busted. Remnant from Gingerbread days that is now hardcoded.
# Off The Proximity Quiclky After Call
mot.proximity.delay=25
ro.lge.proximity.delay=25
Click to expand...
Click to collapse
Busted. As you can probably tell, it only works for LG and Motorola, if it still works at all.
# Signal Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
Click to expand...
Click to collapse
Only works for HTC. No other RIL allows you to modify this sort of thing.
# NetSpeed Tweaks
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
Click to expand...
Click to collapse
Use these instead
net.tcp.buffersize.default 4096,87380,704512,4096,16384,110208
net.tcp.buffersize.wifi 524288,1048576,2097152,262144,524288,1048576
net.tcp.buffersize.lte 4096,87380,1220608,4096,16384,563200
net.tcp.buffersize.umts 4096,87380,563200,4096,16384,110208
net.tcp.buffersize.hspa 4096,87380,704512,4096,16384,110208
net.tcp.buffersize.hsupa 4096,87380,704512,4096,16384,262144
net.tcp.buffersize.hsdpa 4096,87380,704512,4096,16384,262144
net.tcp.buffersize.hspap 4096,87380,1220608,4096,16384,393216
net.tcp.buffersize.edge 4096,26280,35040,4096,16384,35040
net.tcp.buffersize.gprs 4096,8760,11680,4096,8760,11680
net.tcp.buffersize.evdo 4096,87380,563200,4096,16384,262144
net.tcp.buffersize.evdo_b 4096,87380,704512,4096,16384,262144
Click to expand...
Click to collapse
Taken from https://github.com/CyanogenMod/android_device_htc_endeavoru/blob/cm-10.1/ramdisk/init.rc. Some may not apply to the HTC One X, like the LTE setting for example.
# Photo And Video Quality
ro.media.dec.jpeg.memcap=8000000
Click to expand...
Click to collapse
Busted. Completely unused in ICS and above.
# Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
Click to expand...
Click to collapse
Busted. Both do nothing in ICS.
# Scrolling Responsiveness
windowsmgr.max_events_per_sec=500
Click to expand...
Click to collapse
Busted.
Many build.prop tweaks set this value to 300, but it seems this is a bad idea. As Google points out, Android maxes out at 60fps. The default value is already allow for a possible max_events_per_sec of 90. Even if you allow for 300 max_events_per_sec, you’ll only ever see 60 of these events in any given second. Therefore, any value much higher than 90 is unlikely to have any noticeable impact on your experience in general. Additionally, setting this value too high can starve other UI events that need to get processed, viz. touch inputs. You’re not likely to feel like your device is running very smoothly when it is busy processing thousands of scroll events instead of responding immediately to you clicking to try and open a link or an app. There may be some specific scenarios where increasing this value does appear to improve system feedback, but changing this value for all UI events across the board will likely cause more problems than it will solve.
Click to expand...
Click to collapse
# Power Save Tweaks
pm.sleep_mode=1
Click to expand...
Click to collapse
Busted. Actually selects a less efficient power mode. Furthermore, does nothing on non-MSM chipsets (ie. doesn't do anything on the One X)
# Fast Reboot Allow purging of assets (System can free more Ram when needed)
persist.sys.purgeable_assets=1
Click to expand...
Click to collapse
Busted. Only exists in CM codebase.
Use Jit (Dalvik just-in-time compiler)
dalvik.vm.execution-mode=int:jit
Click to expand...
Click to collapse
Useless. The default execution mode is usually JIT anyway.
# Increasing The Video Recording Quality
ro.media.enc.hprof.vid.bps=8000000
Click to expand...
Click to collapse
Set it to ro.media.enc.hprof.vid.bps=20000000 instead. The camera supports 20Mbps video fine.
# Increase VM Heap Size(resolve some fc's)
dalvik.vm.heapsize=64m
Click to expand...
Click to collapse
Busted. There's no point doing this, most app developers optimise their apps to go below this anyway.
# Increasing It Will Make Mobile Smoother
windowsmgr.max_events_per_sec=150
Click to expand...
Click to collapse
This was above anyway, busted.
# Video Acceleration Enabled
video.accelerate.hw=1
Click to expand...
Click to collapse
This was above too. Also busted.
# Increase Performance
debug.performance.tuning=1
Click to expand...
Click to collapse
Deja vu! Busted! Deja vu again!
# Disable Sending Usage Data
ro.config.nocheckin=1
Click to expand...
Click to collapse
Busted. Does nothing for Google services. ro.config.htc.nocheckin=1 will disable HTC checkin though.
# Deeper Sleep/Better battery life
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Click to expand...
Click to collapse
What's deeper than deep sleep also, I seem to have seen this somewhere before lol
#wifi to scan less frequently
wifi.supplicant_scan_interval=180
Click to expand...
Click to collapse
Actually, this causes wifi to scan every 180ms, which is more than what people usually need it to, so it actually scans more frequently than default. A better value would be 250 or so.
#improve battery under no signal
ro.mot.eri.losalert.delay=1000
Click to expand...
Click to collapse
Motorola only.
#makes apps load faster and frees more ram. (Edit exsisting line)
dalvik.vm.dexopt-flags=m=v,o=y
Click to expand...
Click to collapse
I don't think this does anything because the syntax is wrong. It should be dalvik.vm.dexopt-flags=m=y, if this even does anything at all.
# Off The Proximity Quickly After Call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Click to expand...
Click to collapse
I saw this somewhere up there.
Anyway, I've shown you here what works and what does not. I omitted those that I'm not sure about. Unsurprisingly, most don't work. So... this is more or less useless for the HTC One X.
pandaball said:
Busted. The checkJni default value is already false. Setting either property to false or 0 in your build.prop is simply redundant and will have no added effect on your device.
Busted. Remnant from Gingerbread days that is now hardcoded.
Busted. As you can probably tell, it only works for LG and Motorola, if it still works at all.
Only works for HTC. No other RIL allows you to modify this sort of thing.
Use these instead
Taken from https://github.com/CyanogenMod/android_device_htc_endeavoru/blob/cm-10.1/ramdisk/init.rc. Some may not apply to the HTC One X, like the LTE setting for example.
Busted. Completely unused in ICS and above.
Busted. Both do nothing in ICS.
Busted.
Busted. Actually selects a less efficient power mode. Furthermore, does nothing on non-MSM chipsets (ie. doesn't do anything on the One X)
Busted. Only exists in CM codebase.
Useless. The default execution mode is usually JIT anyway.
Set it to ro.media.enc.hprof.vid.bps=20000000 instead. The camera supports 20Mbps video fine.
Busted. There's no point doing this, most app developers optimise their apps to go below this anyway.
This was above anyway, busted.
This was above too. Also busted.
Deja vu! Busted! Deja vu again!
Busted. Does nothing for Google services. ro.config.htc.nocheckin=1 will disable HTC checkin though.
What's deeper than deep sleep also, I seem to have seen this somewhere before lol
Actually, this causes wifi to scan every 180ms, which is more than what people usually need it to, so it actually scans more frequently than default. A better value would be 250 or so.
Motorola only.
I don't think this does anything because the syntax is wrong. It should be dalvik.vm.dexopt-flags=m=y, if this even does anything at all.
I saw this somewhere up there.
Anyway, I've shown you here what works and what does not. I omitted those that I'm not sure about. Unsurprisingly, most don't work. So... this is more or less useless for the HTC One X.
Click to expand...
Click to collapse
you have some think new to add to you sign now cheers