Related
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
This is a tweaked versions of CARBON-JB-UNOFFICIAL-B11 so all credit goes to @killersloth for the ROM. Without his work this ROM wouldn't be possible. So if you like this ROM please go to the CARBON ROM thread and click the "Thanks" button.
As this is a huge upgrade from my Tweaked Xperia ROM I decided to make a new thread.
I have added the @Jon Lee 10.2.1_ovation-kernel-Mar-22-2015. OptiPNG, Zipped and Odexed the ROM. Patched services.jar with "Ultimate Jar Power Tools". Added my little tweaks to it. Replaced the launcher with the Google Now launcher. I added the Lollipop keyboard and the Sony Walkman music player with the UPNP/DLNA Media Server. Also added a custom sound engine that will greatly improve the sound quality.
When flashing the ROM use TWRP. TWRP can format cache and data to F2FS. Formatting cache and data to F2FS will wipe everything off of the internal SD. So backup before formatting.
As you can see from the attached images when using the "Yellow kernel" with F2FS I am seeing really good benchmarks. So if you can live with the bugs its a smooth and fast ROM.
CARBON-JB4.3-SuperCharged-v1.1-ovation.zip (344M)
I have also baked in a modified version of Flash that will trick websites into thinking its the desktop version. This will get around blocks like the one used at hulu.com
To get AC3 sound working in MX Player I have included a custom Arm v7-Neon codec.
I have also added some terminal commands to the ROM.
Each command needs to run as root to work. To do this type SU in the terminal followed by the command you want to run.
fixfc - Fix apps force closing.
sclean - Clean the dalvik cache and cache partition
v6 - run the V6 SuperCharger script.
fixalign -ZipAlign AND Fix Permissions
vac - SQLite VACUUM & REINDEX to optimize databases
zepalign - "ZepAlign" / Wheel Alignment Script (ZipAlign) optimizes all your apps
Battery life is pretty good. Watching 720p video and just general usage (web Surfing, listening to music etc. Not Gaming) I am seeing around 4 and half hours screen on time with about 10hrs of total usage.
Please feel free to give feedback. The more info I get the better I can make this ROM. Also it gives me a general idea of how much interest there is in it.
Thanks to:
@rhyang for TWRP.
@Jon Lee for the Yellow kernel.
@jisoo for compiling CarbonRom JB3.
@privateeromally for grabbing the NOOK apps from the Galaxy Tab 4.
Here are my tweaks: (Already built into this ROM)
Universal tweaks to Build.prop
Code:
#Networking
wifi.supplicant_scan_interval=180
ro.ril.disable.power.collapse=1
ro.ril.transmitpower=true
ro.ril.hep=1
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
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
net.tcp.buffersize.default=6144,87380,110208,6144,16384,110208
net.tcp.buffersize.wifi=262144,524288,1048576,262144,524288,1048576
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=true
media.stagefright.enable-record=true
#Misc
ro.media.enc.jpeg.quality=100
ro.media.dec.hprof.vid.quality=100
ro.media.dec.jpeg.memcap=20000000
ro.media.enc.hprof.vid.bps=20000000
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
ro.media.enc.hprof.vid.fps=65
persist.sys.NV_FPSLIMIT=65
persist.sys.use_dithering=2
debug.overlayui.enable=1
persist.sys.ui.hw=1
video.accelerate.hw=1
ro.fb.mode=1
hw3d.force=1
debug.sf.hw=1
debug.enabletr=true
debug.qctwa.preservebuf=1
dev.pm.dyn_samplingrate=1
persist.sys.composition.type=c2d
debug.composition.type=gpu
debug.composition.type=cpu
debug.performance.tuning=1
ro.sf.compbypass.enable=0
persist.sys.purgeable_assets=1
debug.egl.hw=1
debug.egl.profiler=1
ro.vold.umsdirtyratio=20
windowsmgr.max_events_per_sec=90
persist.sys.smoothscrollbar=true
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
touch.presure.scale=0.001
ro.config.hw_menu_unlockscreen=false
debug.mdpcomp.maxlayer=3
debug.gr.numframebuffers=3
debug.gr.swapinterval=1
persist.sampling_profiler=0
dev.pm.gpu_samplingrate=1
#Disable the ADB notification Icon
persist.adb.notify=0
#Disable Google OTA Update checkin
ro.config.nocheckin=1
#Disable Google Report service
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
#Disable Logcat
logcat.live=disable
#Dalvik Tweaks
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-flags=m=y
dalvik.vm.checkjni=false
dalvik.vm.dexopt-data-only=1
dalvik.vm.verify-bytecode=false
dalvik.vm.lockprof.threshold=500
dalvik.vm.jmiopts=forcecopy
persist.sys.dalvik.multithread=false
#For Nook HD+ Only
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=79m
dalvik.vm.heapsize=258m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
#Zygote
ro.zygote.disable_gl_preload=true
#Memory Hacks
ro.HOME_APP_ADJ=1
ENFORCE_PROCESS_LIMIT=true
ro.sys.fw.bg_apps_limit=12
ro.config.low_ram=true
#HWUI TWEAKS
ro.hwui.disable_scissor_opt=false
ro.hwui.texture_cache_size=24
ro.hwui.layer_cache_size=16
ro.hwui.gradient_cache_size=0.5
ro.hwui.patch_cache_size=128
ro.hwui.path_cache_size=4
ro.hwui.shape_cache_size=1
ro.hwui.drop_shadow_cache_size=2
ro.hwui.r_buffer_cache_size=2
ro.hwui.texture_cache_flush_rate=0.6
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=256
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=512
hwui.text_gamma_correction=lookup
hwui.text_gamma=1.4
hwui.text_gamma.black_threshold=64
hwui.text_gamma.white_threshold=192
hwui.use_gpu_pixel_buffers=true
hwui.render_dirty_regions=false
hwui.use.blacklist=true
#BATTERY TWEAK
ro.mot.eri.losalert.delay=1000
pm.sleep.mode=1
#Enable Quick Power-On mode
ro.config.hw_quickpoweron=true
Sound Tweaks to build.prop (must include Sound_Engine.zip in the ROM).
Code:
#Beats/Sony
ro.product-res-path=framework/SemcGenericUxpRes.apk
ro.somc.sforce.supported=true
ro.service.swiqi3.supported=true
persist.service.swiqi3.enable=1
tunnel.decode=true
tunnel.audiovideo.decode=true
persist.speaker.prot.enable=false
media.aac_51_output_enabled=true
dev.pm.dyn_samplingrate=1
htc.audio.global.state=0
htc.audio.lpa.a2dp=0
htc.audio.global.profile=0
htc.audio.q6.topology=0
htc.audio.enable_dmic=1
persist.htc.audio.pcm.samplerate=44100
persist.htc.audio.pcm.channels=2
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=analog
htc.audio.swalt.mingain=14512
htc.audio.swalt.enable=1
htc.audio.alc.enable=1
#Bravia Engine Service
ro.service.swiqi2.supported=true
persist.service.swiqi2.enable=1
#Sony Xloud & Clearbass +
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.somc.dmnorm.supported=true
persist.service.dmnorm.enable=1
ro.sony.walkman.logger=1
ro.somc.clearphase.supported=true
persist.service.clearphase.enable=1
mpq.audio.decode=true
#Resampling
af.resampler.quality=255
persist.af.resampler.quality=255
#Beats Engine
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
Zips are NOT flashable. Must add them manually to a ROM.
no replies ??
Well.. you have to realize, it is an old version of CM to post. I am reading it because I installed cm11 and Bluetooth isn't working- pretty much the main and only thing I want this tablet for(it is just a cheap gauge pod for my car that happens to stream netflix or whatever..
Firstly - F2FS is something most here may not understand. They will understand wiping their sd card. And I do understand what it is, and what the benefits are.. Just not sure it is worth is because..
Secondly - You mentioned bugs. What bugs? What works, what doesn't? An older version of CM I would expect it to be near flawless..
Thirdly- You posted your build prop. Which someone can unzip and see. You didn't show which edits you made, and what they do.
Fourth(ly?) - You mentioned features as if they are baked in, then added zip files of those same features and said they have to manually add them to the rom - I have built roms, so I know what you mean.. most probably do not. Nor do I find it worth the effort, or I would just build my own rom.
Fifth-ly.. your number of posts vs your thanks meter may have many hesitant to flash your rom and hope they don't own a brick. I had probably 5x your posts/thanks before I started doing more than being a contributor.
So less is more, and more is less. If there are bugs, say what they are. Rather than post your build prop as text, just say what you did. And "supercharger" is nothing more than edits people can make themselves- you get more powerful results with a kernel that can be modified, and no offense.. it just isn't useful these days. Devs do far more powerful things on the back end they don't even bother to remember/mention than what the supercharger scripts can do.
Where is your GIT? Are you building from scratch.. or just rebaking a cake that was made for a different device?
IMHO- you just need more time and experience, and you will be building your own build from scratch, pulling little tweaks from different rom developers, and giving them credit.. until then you are just offering up a(maybe?) brick-your-own-device-thread.
I'll pass, but good luck. I at least am trying to offer you feedback at why you aren't getting much response.
KnowledgeBroker said:
Well.. you have to realize, it is an old version of CM to post. I am reading it because I installed cm11 and Bluetooth isn't working- pretty much the main and only thing I want this tablet for(it is just a cheap gauge pod for my car that happens to stream netflix or whatever..
Firstly - F2FS is something most here may not understand. They will understand wiping their sd card. And I do understand what it is, and what the benefits are.. Just not sure it is worth is because..
Secondly - You mentioned bugs. What bugs? What works, what doesn't? An older version of CM I would expect it to be near flawless..
Thirdly- You posted your build prop. Which someone can unzip and see. You didn't show which edits you made, and what they do.
Fourth(ly?) - You mentioned features as if they are baked in, then added zip files of those same features and said they have to manually add them to the rom - I have built roms, so I know what you mean.. most probably do not. Nor do I find it worth the effort, or I would just build my own rom.
Fifth-ly.. your number of posts vs your thanks meter may have many hesitant to flash your rom and hope they don't own a brick. I had probably 5x your posts/thanks before I started doing more than being a contributor.
So less is more, and more is less. If there are bugs, say what they are. Rather than post your build prop as text, just say what you did. And "supercharger" is nothing more than edits people can make themselves- you get more powerful results with a kernel that can be modified, and no offense.. it just isn't useful these days. Devs do far more powerful things on the back end they don't even bother to remember/mention than what the supercharger scripts can do.
Where is your GIT? Are you building from scratch.. or just rebaking a cake that was made for a different device?
IMHO- you just need more time and experience, and you will be building your own build from scratch, pulling little tweaks from different rom developers, and giving them credit.. until then you are just offering up a(maybe?) brick-your-own-device-thread.
I'll pass, but good luck. I at least am trying to offer you feedback at why you aren't getting much response.
Click to expand...
Click to collapse
What was the point of this post?
pinguy1982 said:
What was the point of this post?
Click to expand...
Click to collapse
Are you serious?
xecutionkrk said:
no replies ??
Click to expand...
Click to collapse
I'm more or less responding to this guy, why there's no posts.. Read what I said- it's constructive feedback. Why no one has replied are the multiple reasons I stated below..
If you need me to say it more concisely, most developers have a high level of skill and knowledge, and their work (ROMs) are unique and distinct.
You however released an old version of cm, say it has bugs, not what they are, and basically you describe what sounds like a bad (or dangerous/brick) port of someone else's work.
If it was working for anyone else, I'd like to see their comments that say so.
Sent from my Samsung Galaxy S5 using XDA Free mobile app
Here is a simple magisk module applying some of the techniques for performance improvements related to touch sensitivity on the shield tablet, referenced in this thread.
I made this magisk module because I wanted to fix touch latency on my tablet systemlessly.
These are the things this modules changes / replaces
/system/user/idc/sensor00fn11.idc
Code:
touch.pressure.calibration = amplitude
touch.pressure.source = default
touch.pressure.scale = 0.001
/system/usr/idc/touch.idc
Code:
touch.pressure.calibration = amplitude
touch.pressure.source = default
touch.pressure.scale = 0.001
Additions to build.prop (using post-fs-data.sh)
Code:
ENFORCE_PROCESS_LIMIT=false
MAX_SERVICE_INACTIVITY=false
MIN_HIDDEN_APPS=false
MAX_HIDDEN_APPS=false
CONTENT_APP_IDLE_OFFSET=false
EMPTY_APP_IDLE_OFFSET=false
MAX_ACTIVITIES=false
ACTIVITY_INACTIVITY_RESET_TIME=false
MAX_RECENT_TASKS=false
MIN_RECENT_TASKS=false
APP_SWITCH_DELAY_TIME=false
MAX_PROCESSES=false
PROC_START_TIMEOUT=false
CPU_MIN_CHECK_DURATION=false
GC_TIMEOUT=false
SERVICE_TIMEOUT=false
MIN_CRASH_INTERVAL=false
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
ro.zygote.disable_gl_preload=false
windowsmgr.max_events_per_sec=180
debug.sf.hw=1
debug.composition.type=gpu
persist.sys.ui.hw=1
persist.sys.composition.type=gpu
debug.performance.tuning=1
touch.pressure.scale=0.001
view.touch_slop=4
ro.min_pointer_dur=0.001
touch.size.calibration=geometric
touch.size.scale=100
touch.size.bias=70
touch.pressure.calibration=amplitude
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.ril.disable.power.collapse=0
dalvik.vm.heaptargetutilization=0.75
sys.usb.config=mtp,adb
dalvik.vm.dexopt-flags=m=y,v=n
ro.debuggable=1
ro.kernel.android.checkjni=0
ro.secure=0
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
debug.egl.hw=1
ro.config.disable.hw_accel=false
video.accelerate.hw=1
Thanks @m0nt3s for the original tweaks!
Thanks @topjohnwu for Magisk!
Hoping to see if this works for anybody. Also, you have a little derp in the title OP
I've noticed touch improvement while charging my tablet using the nougat RR rom. Thank you for this.
MishaalRahman said:
Hoping to see if this works for anybody. Also, you have a little derp in the title OP
Click to expand...
Click to collapse
Yeah, I'm not sure if this will work on any other devices because it makes changes specifically for the NVIDIA SHIELD.
It replaces the entire touch.idc file which contains specific information to NVIDIA SHIELD, so while the changes I've made could be applied to another devices IDC, it would have to be that devices IDC file. Also touch latency seems to be a very scares problem, so I'm not sure other devices would even benefit from this mod. It could even make it worse.
I can't figure out how to fix the title typo lol
Edit: fixed it, thanks!
I get download unsuccessful every time I try
Thank you, Thank you, Thank you!
This module works great. Noticeable improvement upon first reboot after installing! You've just breathed some more life into this aging tablet!