Related
Hey everybody, just wanted to share the below build.prop performance tweaks. I have been using them for some time now trying different values to see what works the best. From what I have been able to tell any difference made using these tweaks is most noticeable using Stock or a Stock based Roms. Performance wise I would not expect to find the Holy Grail within these lines but they do seem to make a difference and can help with a few minor annoyances. Feel free to test them out and let everyone know what you think, at your own risk that is.
General Performance
debug.sf.hw=1
Edit existing line,
dalvik.vm.heapsize=48m
Saves power
ro.ril.disable.power.collapse=1
pm.sleep_mode=2
windowsmgr.max_events_per_sec=60
wifi.supplicant_scan_interval=180
*If you don’t keep Wi-Fi active lowering the value below the default of 90 seems to make Wi-Fi connect faster after being turned on but will consume more power if turning Wi-Fi off has been forgotten when not in range of a known network.
ro.mot.eri.losalert.delay=1000
*Should smooth out disconnects and reconnects, saving battery. Seems to brake tethering with CM7, let me know if anyone else experiences this issue.
Raises quality of images
ro.media.enc.jpeg.quality=90
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Increased Media & Streaming Performance
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
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
*Note: I don't know why but the forum is placing spaces in the above lines that are not there. The spaces are not present when I edit and have even tried retyping them in Word and then pasting the lines in but it still shows the spaces after saving, kind of frustrating. The ends for the above lines should all be the same ending values for each line (=4096,87380,256960,4096,16384,256960). I don’t know why but for whatever reason anytime I save the post the spaces appear.
Disable error checking (Should speed things up a bit)
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
Disable sending usage data
ro.config.nocheckin=1
To make the phone ring faster when dialing out
ro.telephony.call_ring.delay=0
Disable black screen issue after call (Thanks to Whyzor for finding why looking into the other tweaks)
ro.lge.proximity.delay=150
mot.proximity.delay=150
Disable USB Debugging icon from Status Bar. (Just the Icon, debugging remains enabled.)
persist.adb.notify=0
Improve 3g data speeds
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=20
ro.ril.hsupa.category=6
ro.ril.hsxpa=3
There is some debate on the effectiveness of these lines, see comments below. If you have used the 3g script put out by the developer of theV6 Turbocharger script then they have already been applied to your device. It may just be in my head but why I haven’t seen any difference in speed tests YouTube definitely seems to display much faster, especially the thumbnails on the startup page after opening the App.
Next few can be found in the CM7 Performance settings but am including them in case someone would like to use them on another Rom like Miui.
Lock Home Screen into memory
ro.HOME_APP_ADJ=1
Use Jit (Dalvik just-in-time compiler)
dalvik.vm.execution-mode=int:jit
Enable Surface dithering (Improves image quality at the cost of performance)
persist.sys.use_dithering=1
Allow purging of assets (System can free more Ram when needed)
persist.sys.purgeable_assets=1
Disable animation for faster startup
debug.sf.nobootanimation=1
To apply any of the above Tweaks you will need a File Explorer with Root Permission. I use Root Explorer so the below steps are assuming Root Explorer is being used. This can also be done using ADB or QtADB; if ADB would be preferred in place of a File Explorer then you probably do not need directions for doing so. You will find instructions for using the QtADB interface below. It is also important to check that any of these lines have been included with your Rom.
1, Navigate into the system folder.
2, Mount the folder as R/W by tapping on the Mount R/W tab found at the top of the screen.
3, Long press on the Build.prop file and select open with text editor.
4, Add desired lines at the bottom of the script.
5, Tap menu key and select save and exit. The original Build.prop will be saved as Build.prop.bak.
6, Save the file in safe place just in case you would like to switch back
7, Reboot!
Please note that on occasion a 2nd reboot was required for the tweak was applied, USB debugging notification for example. Unless noted I have not had any issues with these lines breaking anything. With that said I also wipe both the Dalvik and Cache Partitions when performing the reboot.
This can also be done very easily using QtADB for those who are not familiar with ADB. QtADB can be installed in a few minutes by following the directions provided in the link below.
http://androidforums.com/triumph-all-things-root/494579-adb-gui-noobs.html
Once installed among many other very useful features this will give you the ability to just drag and drop the Roms Build.prop file onto your computers desktop, open the file in notepad or on other text editor, add the desired lines and then drag & drop the modified Build.prop file back into the system directory on the Triumph and reboot the phone all on your computer and without actually touching the device.
Before giving more details on how to use QtADB for the purpose of modifying the Build.prop having ADB in some form or another can be very helpful in general. One example is that after updating to CM7 one of my favorite Apps would FC when started. I was able to do a logcat with ADB and send it to the developer of the app. Based on the information provided in the logcat the developer was able to fix the issue in the next release. Anyway it’s very simple so here we go,
1, select /system/ from the dropdown outlined above in Red.
2, Drag and drop the Build.prop file highlighted Blue into the adjacent area on the left, follow the blue arrow. I have desktop selected for easier navigation but ware on the computer the file is moved does not matter as long as you remember where the file has been moved. Changing the location the file is saved is as easy as selecting the directory from the dropdown like was done with the Red outlined box in the first step above.
3 open the build.prop file now located on your computer inside notepad or another text editor, add the lines you would like to use at the end of the text file and then save. In notepad you may need to select Word Rap from the format tab from the menu at the top of the Notepad Window for the file to display correctly. I use notepad ++ and never have issues with the file displaying incorrectly. Would highly recommend making a copy of the original build.prop before editing and keeping in a safe place before editing the file.
Notepad++ can be downloaded here,
http://notepad-plus-plus.org/download/v5.9.8.html
4, once we have made our edits it’s time to move the modified file back to the Triumph. Drag and Drop the modified Build.prop back into the devices system folder. Follow the blue arrow from the below example.
5, after the file has been moved back into the system folder select the Shell tab outlined in the black box.
6, Type reboot into the command line and your Triumph will now reboot using the modified Build.prop. Please note that on occasion a 2nd reboot was required for the tweak was applied, USB debugging notification for example. Unless noted I have not had any issues with these lines breaking anything. With that said I also wipe both the Dalvik and Cache Partitions when performing the reboot. If you would like to wipe caches just type "reboot" recovery into the command line.
I also came across this App for editing the build.prop. I don't have much experience with the App but if anyone would like to check it out,
https://market.android.com/details?id=com.joeykrim.buildpropeditor
Thanks for posting this, but you should know that build.prop entries are highly rom specific. So what works for one rom might not do anything in another rom. That applies even when both roms are, for example, Froyo. The worst thing that can happen is that your entries end up doing nothing. For example, for the proximity sensor, only one of those would do anything on your device (if either one even worked). I think ro.lge.proximity.delay is for LG phone roms. The LG optimus V has many ro.lge entries. You should also verify that the build.prop entries are being saved at all. With the Optimus V, the kernel would overwrite some of the entries after the build.prop values were read in. To see what your final values are, open adb shell or terminal emulator and type in "getprop".
I'm still trying to decide between a modified stock rom and miui rom based purely on batter life. I've been trying to tweak values on both, but nothing seems to change. After overclocking and undervolting, build.prop tweaks, blocking apps from using data, and streamlining the roms, I still get ~3% loss per hour on idle on both roms. I used to get 1% on the optimus v.
Thanks, the ADB trick is very helpfull. The battery thing is tough.
freddysam said:
I'm still trying to decide between a modified stock rom and miui rom based purely on batter life. I've been trying to tweak values on both, but nothing seems to change. After overclocking and undervolting, build.prop tweaks, blocking apps from using data, and streamlining the roms, I still get ~3% loss per hour on idle on both roms. I used to get 1% on the optimus v.
Click to expand...
Click to collapse
That 3% loss is about what I get on the gb/ics based roms when wifi is enabled and left on. Make sure that you don't have wifi or bt enabled if you're using one of those roms and want your phone to deep sleep.
Has anyone tried these on CM7?
I wanna try these out, but it's my gf's phone and I really dont wanna **** it up xD
xLoveHateLegend said:
Has anyone tried these on CM7?
I wanna try these out, but it's my gf's phone and I really dont wanna **** it up xD
Click to expand...
Click to collapse
I have put the majority of these tweaks into a script that runs on boot.
The script can be found here,
http://forum.xda-developers.com/showthread.php?t=1609729
The Build.prop script or Hollyname script as I like to call it is posted below the 108 script. If you follow the instructions it will not make any permanent changes to the build.prop and can easily be applied or disables. Also yes I have been testing these on CM7 for the most part.
Found this while I was doing some searching around. These are well known edits to the build.prop. Just thought it would be nice not to have to look all over the place. This is not my work I am just passing it along.
What is build.prop: The build.prop file is your android handset’s ‘ID card’.
- It tells applications the specifications of your device, so that apps can change their interface or function for your specific device.
- Editing the build.prop file is most commonly used for changing LCD density, build number and your device’s model or manufacturer.
- Changing your ‘fingerprint’, model or manufacturer can trick some apps in the market to become compatible with your device.
SOME OF THESE TWEAKS ARE CAUSING SOME ISSUES. ALWAYS MAKE A BACKUP OF THE DEVICE. I WILL BE TESTING OUT ALL THE TWEAKS AND REMOVING THE ONES THAT ARE CAUSING THE ISSUES.
TWEAKS: build.prop
path: /system/build.prop
# Fast Reboot
persist.sys.purgeable_assets=1
# 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
# 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
# Off The Proximity Quiclky After Call
mot.proximity.delay=25
ro.lge.proximity.delay=25
# 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
#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
Wipe both Caches in Recovery after adding or changing the above lines
Original Thread: http://www.s3forums.com/forum/galaxy-s3-hacking-mods/474-list-some-build-prop-tweaks.html
Enjoy!
Now i gotta pull they build.prop off my phone and edit It
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
Now i gotta pull they build.prop off my phone and edit It
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I changed my build.prop -- specifically LCD density, and my phone stopped booting... <.<
had to odin-resurrect it.
tijayz said:
I changed my build.prop -- specifically LCD density, and my phone stopped booting... <.<
had to odin-resurrect it.
Click to expand...
Click to collapse
I changed build prop for Google wallet and the same thing happened to me, had to do the same thing with Odin
Sent from my SCH-I535 using Tapatalk 2
nevermind this post.
yea so I put all these edits in.
# Ringing Will Start Immediately
ro.telephony.call_ring.delay=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
#Force To Remain Launcher In Memory
ro.HOME_APP_ADJ=1
# 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
# Power Save Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
#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
# Fast Reboot
persist.sys.purgeable_assets=1
# Increasing The Video Recording Quality
ro.media.enc.hprof.vid.bps=8000000
# 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
Click to expand...
Click to collapse
and now I get the custom screen then just a black screen and my phone never boots.
You need to put a disclaimer at the top, USE WITH EXTREME CAUTION!
Yikes. Is this from a VZW version, or international, or something else?
The performance ones sound good, but I'm a little afraid to even try them based on everyone else's experiences.
ponyboy82 said:
Yikes. Is this from a VZW version, or international, or something else?
The performance ones sound good, but I'm a little afraid to even try them based on everyone else's experiences.
Click to expand...
Click to collapse
Leave them alone, unless you know what you are playing with. I guess, you can mess around, but you may have to flash the ROM again.
jcurley said:
Leave them alone, unless you know what you are playing with. I guess, you can mess around, but you may have to flash the ROM again.
Click to expand...
Click to collapse
Yeah, I should clarify that I'm staying away from this. I was just curious. It seems like Samsung would've enabled all the HW acceleration they could.
ponyboy82 said:
Yeah, I should clarify that I'm staying away from this. I was just curious. It seems like Samsung would've enabled all the HW acceleration they could.
Click to expand...
Click to collapse
Not always, but unless you understand what you are changing, you will be doing trial and error. So make a change, if it works, great, if not flash your backup.
that is why I donate to the developers. It is hard work for some of these tweaks.
UNTIL SOMEONE ELSE CAN CONFIRM THIS, DO NOT USE THESE ON YOUR PHONE.
THESE DO NOT APPEAR TO BE USA VERIZON GALAXY SIII FRIENDLY OR EVEN IN ITS OPERABLE RANGE IN SOME CONDITIONS.
I.E.
LCD Density should be more like 300+,
VM Heap is 200+, dropping it down to 64m is unfathomable.
Max events per second are 300+, dropping to 150 will essentially cut your max in 1/2.
These would have probably worked well on my Bionic, Droid, Droid X but not S3.
When I get some time tonight I will test out each one of these and see which ones cause a problem and will remove them.
yeah it looks like there's multiple settings for the max events per second. 500 is more reasonable than 150 to increase performance, but my tweaked build.prop from beans rom is 310 right now and smooth.
vm heap should be ~256m
video recording quality 12000000
again, these are for my device specifically so they could vary if you're on stock odexed/custom rom.
So if running stock or beans stripped rom, the hang up would happen and the phone wouldn't boot.
However, I have figured out a way to get the settings to stick..
I took the zip file from Beans 50GBDropbox Rom, and took build.prop in it and modified it. Once modified, I pushed it back into zip and reflashed the entire package. That made build.prop to stay and work the way I wanted it to. (ie. LCD density @ 240)..
So I don't think its a value limitation, I think it more of a "tamper check" mechanism of some sort.
Signal tweaks and net speed tweaks are for gsm at&t phones not Verizon
Sent from my SCH-I535 using xda app-developers app
while i was surfing on net i found this and thought it will be helpful to our Dev's, so i am posting them here ...
# Fast Reboot
persist.sys.purgeable_assets=1
# 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 hardware 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
# 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
# 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
# Increasing It Will Make Mobile Smoother
windowsmgr.max_events_per_sec=150
# Scrolling Responsiveness
windowsmgr.max_events_per_sec=500
Source
pudup said:
Looking good.
Sent from my GT-I9103 using XDA
Click to expand...
Click to collapse
Thank you.......
Sent from my GT-I9103 using xda app-developers app
This is under hardware performance
Code:
debug.performance.tuning=1
CallMeVentus said:
This is under hardware performance
Code:
debug.performance.tuning=1
Click to expand...
Click to collapse
Thank you I've edited the post..
this is common everyone must be knowing, just sharing for who doesnt knows
Code:
ro.build.version.release
fake version of ur android
Code:
ro.sf.lcd_density
change density of lcd. (PPI)
Code:
wifi.supplicant_scan_interval
wifi scan interval time, bigger value will make phone to search for wifi at long intervals, usable to extend bat life.
use Rom Tollbox/build prop editior or similar app to directly modify values without notepad editing.
Can anyone please tell what is this and whether this is useful for our phone or not?
http://forum.xda-developers.com/showthread.php?t=991276
Sent from my GT-I9103 using xda premium
nvo2411 said:
Can anyone please tell what is this and whether this is useful for our phone or not?
http://forum.xda-developers.com/showthread.php?t=991276
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
the v6 super charger script is present in NEO ROM v3.0
pankaj88 said:
the v6 super charger script is present in NEO ROM v3.0
Click to expand...
Click to collapse
Hey pankaj buddy, I tried using this script on my phone but got confused with all those options. Can you tell me which is the best setting for our phone? and does this really work?
Note: I'm on a stock ROM.
Anyone?
windowsmgr.support_rotation_270=true;
How helpful is this? Will it allow auto-rotation in TW launcher?
The-Droidster said:
Hey pankaj buddy, I tried using this script on my phone but got confused with all those options. Can you tell me which is the best setting for our phone? and does this really work?
Note: I'm on a stock ROM.
Anyone?
Click to expand...
Click to collapse
place the script in etc/init.d/
flash a kernel that supports init.d scripts.
the script will get executed at every boot..
Sent from my GT-I9103 using xda app-developers app
The-Droidster said:
windowsmgr.support_rotation_270=true;
How helpful is this? Will it allow auto-rotation in TW launcher?
Click to expand...
Click to collapse
Just that it helps when u turn ur phone upside down. It will not work on Launchers (Twlauncher). Its only applicabale to windows inside. Infact, by default, this value has been set to 180 so u can turn you mobile left or right to get the rotation. By making this tweak, u are making it to rotate another 90 degrees to make it a 270 degree rotation. For all the stuffs, where 180 degree is working, 270 degrees will apply to those alone. Not for launchers.
a noob question..
I'm on ICS rom odexed by default, rooted and with ardatdat kernel. Can i use rom toolbox to tweak some of these build.prop parameters? such as wifi scan interval...etc.. ?
chandanbs said:
a noob question..
I'm on ICS rom odexed by default, rooted and with ardatdat kernel. Can i use rom toolbox to tweak some of these build.prop parameters? such as wifi scan interval...etc.. ?
Click to expand...
Click to collapse
yes you can edit build.prop, better use this to edit
https://play.google.com/store/apps/details?id=org.nathan.jf.build.prop.editor&hl=en
I thought i should be on deodexed rom to edit the build prop?
So its fine if i go ahead and use the suggested app to edit the values given in the following thread (created by you) right??
http://forum.xda-developers.com/showthread.php?t=1802639
Looks like i have an issue with launching this app (build prop editor) on ICS rom..
I just got it installed from google play store..
Is it a known issue? If so i will try and indicate this to the developer..
chandanbs said:
I thought i should be on deodexed rom to edit the build prop?
So its fine if i go ahead and use the suggested app to edit the values given in the following thread (created by you) right??
http://forum.xda-developers.com/showthread.php?t=1802639
Looks like i have an issue with launching this app (build prop editor) on ICS rom..
I just got it installed from google play store..
Is it a known issue? If so i will try and indicate this to the developer..
Click to expand...
Click to collapse
Even if the app doesn't work, just copy over the build.prop file to the pc ----> edit it using any of the text editors and then copy it over to the phone in /system. Make sure to have a backup ready...just in case
Thanks.. anyway.. i used the following app (very informative.. and some properties come preloaded.. we can just add them in...) to tweak the build props..
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en
IMPORTANT
After a month of testing in several roms, I decide to release the beta version!
It's almost same as the alpha version, but with several changes!
See the changelog!
Atention!
This is not the real project butter introduced in Android Jelly Bean!
This is just compilation of tweaks!
All tested buy me, one buy one!
Click to expand...
Click to collapse
MUST READ THIS FIRST
It is logical that adreno_config.txt is only for all those devices, which have the adreno graphics and qualcom cpu.
But down in the attachments you will find Project-Butter-for-ICS_v1.0 -Without_Adreno-Config-alpha2.zip,
This is for all other devices which doesn't have Qualcom CPU, and Adreno Graphic.
For those who doesn't know what is project butter please first watch this video: Project Butter
The code is for developers only, to implement it into there roms.
Down in the attachment will be the zip file for every regular user, if want to try it!
Files that I tweak are:
build.prop
adreno_config.txt
egl.cfg
libGLES_android.so
Some of this tweaks are well know for the Devs, but, as I could see checking all of the current known ICS roms for DS, are not!
Click to expand...
Click to collapse
Down below I'll explain all of the tweaks!
build.prop
Code:
#Grpahics & performances tweaks
com.qc.hardware=true
debug.sf.hw = 1
debug.composition.type=gpu
debug.enabletr = true
debug.qctwa.preservebuf = 1
debug.egl.hw=1
debug.egl.profiler=1
debug.performance.tuning=1
debug.gr.swapinterval=1
dev.pm.dyn_samplingrate=1
persist.sampling_profiler=0
persist.sys.NV_FPSLIMIT=60
persist.sys.ui.hw=1
persist.sys.use_16bpp_alpha=1
persist.sys.use_dithering=1
persist.sys.ui.hw=1
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.sf.compbypass.enable=1
windowsmgr.max_events_per_sec=250
#Media quality improvements
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=true
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=75
video.accelerate.hw=1
#Dalvik tweaks
dalvik.gc.type=precise
dalvik.vm.heapstartsize=5m
dalvik.vm.dexopt-data-only=1
dalvik.vm.verify_bytecode=false
dalvik.vm.jniopts=forcecopy
dalvik.vm.dexopt-flags=m=v,o=y
dalvik.vm.execution-mode=int:jit
#Other Performance Tweaks
ENFORCE_PROCESS_LIMIT=false
persist.android.strictmode=0
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
ro.min_pointer_dur=1
ro.telephony.call_ring.delay=0
ro.sec.proximity.delay=0
ro.HOME_APP_ADJ=1
adreno_config.txt
Code:
Use hardware-assisted binning.
from [COLOR="DarkRed"]binning=sw[/COLOR] to [COLOR="DarkRed"]binning=hw[/COLOR]
[COLOR="Navy"][SIZE="4"]Updated[/SIZE][/COLOR]
Use 2D hardware BLTs.
from [COLOR="DarkRed"]2D.HwBlt=0[/COLOR] to [COLOR="DarkRed"]2D.HwBlt=1[/COLOR]
Enable tiled textures. Tiled textures are faster to render, but slower to load.
from [COLOR="DarkRed"]textureTiling=0[/COLOR] to [COLOR="DarkRed"]textureTiling=1[/COLOR]
Playing with the egl.cfg could cause boot loop on some devices !
egl.cfg
Code:
remove the line:
0 0 android
libGLES_android.so
Code:
mv /system//lib/egl/libGLES_android.so /system/lib/egl/libGLES_android.so.bak
EDIT:
For testing purposes only
I activate the MultiSampling Antialiasing (MSAA) in adreno_config.txt
Аttention
MSAA may slowdown a bit the GUI due to exchange of the graphics performance!
Code:
Specify the multisampling antialiasing smoothing strategy.
from [COLOR="DarkRed"]MSAASmoothing=Normal[/COLOR] to [COLOR="DarkRed"]MSAASmoothing=High[/COLOR].
Specify the allocation strategy for multisampling antialiasing buffers.
from [COLOR="DarkRed"]MSAABufferAllocation=on_demand[/COLOR] to [COLOR="DarkRed"]MSAABufferAllocation=always[/COLOR]
Force the MSAA antialiasing mode to the value in MSAAMode.
from [COLOR="DarkRed"]forceMSAAMode=0[/COLOR] to [COLOR="DarkRed"]forceMSAAMode=1[/COLOR]
Specifiy the antialiasing mode to use if forceMSAAMode is enabled.
from [COLOR="DarkRed"]MSAAMode=0[/COLOR] to [COLOR="DarkRed"]MSAAMode=2[/COLOR]
Maybe go a little too far with the antialiasing mode, but you can choose between 0 = default, 1 = 2x antialiasing, and 2 = 4x antialiasing
You can find the zip down in attachment!
Simply put in your sdcard, and flash it via any recovery!
CHANGELOG:
Code:
[COLOR="Silver"]Fixing buildprop.sh script.
Now it'll make all changings in build.prop correctly!
[SIZE="4"]build.prop[/SIZE]
Setting windowsmgr.max_events_per_sec to reasonable 250 = SingleCore max
[B][SIZE="4"]adreno_config.txt[/SIZE][/B]
Activating 2D Settings
Activating tiled textures[/COLOR]
[COLOR="Black"][SIZE="4"][FONT="Arial Black"][B]build.prop tweaks[/B][/FONT][/SIZE][/COLOR]
debug.composition.type=gpu
persist.sys.NV_FPSLIMIT=60
dev.pm.dyn_samplingrate=1
persist.sys.use_dithering=1
New update released,
IMPORTANT
If you get any scroling problems,
try changing debug.gr.swapinterval=0 to debug.gr.swapinterval=1
This will force the GPU rendering device to wait for the previews frame to be finished before pushing the next frame!
The framerate will be decreased, but you'll get more fluid graphic animations!
ATTENTION
This is a standalone flash zip
I tried to activate vsync clock.
But it is likely this tweak does not change anything!
I simply activate vsync_clk in the kernel, but this depends on how the developer compiling the kernel you are using!
Tested with several ICS roms with Sense 3.6-4 / A, and amidabuddha tweaked kernel 8.0.
Strange, but any kernel abouve v8.0 doesn't change anything in the performances!
vSync_Activator reuploaded!
Anyway!
I've attached some print screen!
Sources:
Tweaking Adreno Config
Tims-evo-v-4g-tweaks-3-800-in-quadrant
Build.prop tweaks for all!!!
Build-prop-performance-tweaks
totiadrenalin said:
Reservet
Click to expand...
Click to collapse
Most look good...but somehow doubt this 1 only...
windowsmgr.max_events_per_sec=1000...
thought it should around 120 to 150 for single core processor
flashed on miui v4 official, but no change on build.prop
hboot 7.00 s-off
slurpdroid said:
flashed on miui v4 official, but no change on build.prop
hboot 7.00 s-off
Click to expand...
Click to collapse
Try to push it manually and set permissions.
on fallout v5
i have flashed the zip file.
1) The file " /system/lib/egl/libGLES_android.so" has not been properly renamed in "/system/lib/egl/libGLES_android.so.back ".
2) the line "0 0 android" has been properly removed
3) the build.prop has not been properly edited
thank you!
edit: s-off hboot 7.xx
Ok!
I'll try to fix problems!
Is v1.0-alpha1 different to the one posted here?
old.splatterhand said:
Is v1.0-alpha1 different to the one posted here?
Click to expand...
Click to collapse
Project-Butter-for-ICS+MultiSampling Antialiasing (MSAA)_v1.0-alpha1.zip and this one are not!
Because of the MSAA activated in the Project-Butter-for-ICS+MultiSampling Antialiasing (MSAA)_v1.0-alpha1.zip.
But Project-Butter-for-ICS_v1.0-alpha1.zip and this one
are almost the same!
Except the fixes in updater-script and buildprop.sh.
And that this is a official, with explanation on every tweak, and changes!
Is this the same as the one you've posted in virtuous thread? I've tried it but notice no difference.. can this be installed in virtuous rom? what changes are we expecting here? thank you
maybe this will help you..... http://forum.xda-developers.com/showthread.php?t=1855722
Dreamtheater2003 said:
Is this the same as the one you've posted in virtuous thread?
Click to expand...
Click to collapse
The answer of that is written directly above your question.
I've flashed the tweaks (with msaa) on a very stripped down stock ics using apex launcher and amidabuddhas Kernel, and it does seem buuuttery smooth
Sent from my HTC Desire S using xda app-developers app
will this works for
http://forum.xda-developers.com/showthread.php?t=1567715
I've flashed both alpha 1 and alpha 2, but it crashed my whole rom. I've to reinstall rom after installation.
when I start rom after flashing this zip files, I got blank screen all the time.
If flashed the Alpha 2 witho MSAA. I think the App Drawer is much smoother than without the "patch". At the home screens I´ve noticed no really improvements.
I using Nexx´s Cyanogemod 9 with the Apex launcher.
v1.0alpha2 no MSAA didnt work well with IceColdSandwich v8.5... firstly I thought it didnt boot because the screen stays black... but when plugged on cable and run adb logcat it shows it works... so I tried to switch the screen on with power button but nothing happend... on second push it instantly showed crt off animation and of course screen turned off... I am going to try alpha2 with MSAA...
edit: the same symptoms with 1.0 alpha 2 + MSAA as well...
No problems here with Alpha2 & MSAA. Seems a little bit smooth.
Thank You, works pretty good :good: on Xperia arc S, i Must Mount /systen before installation
Maybe I'll Include to One of My ROM's ( if u allow)
Sent from my LT18i using xda app-developers app
Thanks, now scrolling is smoother than on iPhone
Sent from my HTC Desire S using xda app-developers app
jader13254 said:
Thank You, works pretty good :good: on Xperia arc S, i Must Mount /systen before installation
Maybe I'll Include to One of My ROM's ( if u allow)
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
I put the code with reason.
Anyway. I just put together Tweaks.
And I don't say that this is a real project butter.
Because to port the real project butter, some build.prop, and adreno_config.txt tweaks are not enough.
first we will need to activate the triple frame buffer in the gpu drivers. Triple frame buffers
Also we need to activate vsync.
That's wy i name this thread near Project butter
Open build.prop with text editor on Root explorer and write this on it:
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000