[MOD] Build.Prop Tweaks - Milestone XT720 Android Development

I’ve been scouring XDA and the net for some ways to make our phones a little bit better. What I have found is that you can alter your Build.Prop to work to your advantage.
Did you know that if there is an app exclusive to the Droid X and only works for the Droid X (not withstanding hardware issues), we can change our Build.Prop from Milestone XT720 to Droid X (whatever that model number is) and get into the market and download it?
There also other “tweaks” to you Build.Prop that are beneficial in many other ways, Data strength, Video and Camera resolution, GPS lock, Power saves,…
The below is what I have been able to find, save and test for most of our builds on the Milestone XT720, but first…
Choice is something that has been fought for, relinquished, dreamt of and lost. Here in XDA we have a choice to either use on not to use. This is YOUR choice. If YOU decide to use these tweaks, any problems that arise are YOUR responsibility. Now that is out of the way, here you are.
Oh and one other thing:::::::::::Make a backup of at the very least your /system because if something goes awry while editing the Build.Prop, all you have to do is restore your /system, since that is where the Build.Prop is located.
**XT720 Users->I have not tested these on any of the MIUI builds or Fjfalcon's CM7 release (per Sebastiman -all tweaks but camera work on Fjfalcon's CM7).**
Per Fjfalcon some of these are NOT working on [ROM][KANG][2012.01.30] CyanogenMod 7.2.0 RC0 Milestone XT720
If any Devs want to use these, that is cool. Just make sure you put in your OP that they are already on there so no one duplicates them on their Build.Prop.
Motorola XT720 "Stock" Build.Props are located here (thanks to AA1973 and 3rdstring) http://forum.xda-developers.com/show....php?t=1327141
I presume most of us are using Root Explorer or something extremely similar. You just need to have Root access and able to edit the Build.Prop text. I user Root Explore so that is what these are based off.
1, Open "Root Explorer" and click the R/W
2, Go to /system/build.prop.
3, Long-presson Build.Prop and you’ll see a pop up.
4, Text Editor.
5, Type in those few line of words below into the last line of the text then save.
6. Reboot twice
Data Tweaks Increase download/upload/3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8 (or 10,12,14) Still looking for more of these though.
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
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
For some reason XDA won't let me take out the spaces between 4096, 16384. I have edited it twice and it still shows up with the spaces on OP. Should read 4096,16384 for all 5 (default, wifi, umts, gprs and edge) with no space between 6,1 or 16384
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
POWER SAVES
Allows the phone to sleep better
ro.ril.disable.power.collapse=1
Saves power when phone is sleep
pm.sleep_mode=1
Allows your wifi to scan less, saving more battery
wifi.supplicant_scan_interval=150 or 180 (your choice)
Helps Scrolling Responsiveness
windowsmgr.max_events_per_sec=150
Increase overal touch responsivenss
Debug.performance.tuning=1
Video.accelerate.hw=1
MEDIA TWEAKS
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-record=false
Increases quality of photo and videos
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Raises quality of JPEG images
ro.media.enc.jpeg.quality=90 or 100 (your choice)
Better camera and video taking results
camera/camcorder mods
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led ***May interfere with Xenon
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
BOOT TWEAKS
Gives your phone no boot animation
debug.sf.nobootanimation=1 ***This might freak out some people not seeing their animation and cause unnecessary battery pulls***
SYSTEM TWEAKS
Forces your home launcher into memory
ro.HOME_APP_ADJ=1
Change the Dalvik VM heap size
dalvik.vm.heapsize=64m can use 24, 32 is default, 48, 64
To disable usb debugging popup
persist.adb.notify=0
To give your phone an HD effect fitting a little more on the screen, look for this in your current build.prop and change the 240 to:
qemu.sf.lcd_density=X (225 or 230) ***This has been known to cause FC’s for the Market, so may not be a good tweak but I still put it in here just in case*** See Changelog
To stop the phone from waking up when pressing the volume key
ro.config.hwfeature_wakeupkey=0
To make the phone ring faster when dialing out
ro.telephony.call_ring.delay=800
Disable black screen issue after call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Screen ppi or font density
ro.sf.lcd_density=240
THESE ARE ONES THAT I DO NOT KNOW WHAT THEY DO AND HAVE NOT TESTED
To enable the hard key lights to stay on while the screen is on and not timeout
ro.mot.buttonlight.timeout=0
Try disabling BLN if your having trouble getting this to work
To make the phone come off of the "black screen" in the middle of, or the end of phone calls when you pull the phone away from your face
mot.proximity.delay=150
**May kill the dialer**
Render UI with GPU
debug.sf.hw=1
Fix some application issues
ro.kernel.android.checkjni=0
Defrags database files
for I in \
‘find /data –iname “*.db”’
do \
sqlite3 $i ‘VACUUM; ’ ; ***This might be something for devs to look into using for something, not sure what***
Credits to the following and links to their pages.
Master&Slaves http://forum.xda-developers.com/showthread.php?t=1151608
knzo http://forum.xda-developers.com/showthread.php?t=1227269
Jokersax11 http://forum.xda-developers.com/showthread.php?t=1263768
Change/Edit log:
11/4/11:::
1-Per peshovec qemu.sf.lcd_density::: if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
2-Per Sebastiman all tweaks work on Fjfalcon's CM7 except camera ones (caused boot loop)
11/9/11:::
Took out spaces in net.tcp.buffersize as was a copy/paste issue from Word.doc to XDA.
1/6/12:::
Took out some of the Motorola XT720 ROM specific verbiage as this is being view by way more people/devices than the XT
2/1/12:::
Noted the some of these are not working on [ROM][KANG][2012.01.30] CyanogenMod 7.2.0 RC0 Milestone XT720

WOW Awesome dude! Nice work! Can't wait to test them! I wonder if there are reversals? Or probably is if I knew anything about coding lol. Great job dude looks promising. Can't believe the excitement we are still getting out of our phones lol.

LibertyMonger said:
I wonder if there are reversals?
Click to expand...
Click to collapse
Just make sure you have a back up of /system because that is where the build.prop "lives". Also I have found that when I edit them, it creates a .bak backup, but you can never fail restoring a nandroid of just the /system.
As a side note, AA1973 gave the "stock" Build.Pro for the MIUI and 3rdstring (of course) uploaded a .zip with damn near the rest of them here http://forum.xda-developers.com/showthread.php?t=1327141
Plus is you adjust a value, wirte down what the original was and if new doesn't work for you, jsut pust back in the original. This way you shoudl only have to restore /system nandroid is something screws up majorly.

Great work there!
I'd like to call attention to
Code:
Change the Dalvik VM heap size
dalvik.vm.heapsize=64m
Since we have rather limited memory, its better if we stick to a heap size of 32 (default in most roms) personally I use 24 and feel that multitasking is much better than at 32 when most apps get killed repeatedly.

That's cool. I know that when I was on Kahl's V4, mine was at 48 and never had a problem with it. Think the intervals are 24, 32, 48, 64
Edited OP with that.

look cool man, will be take time to check & test soon!

ro.media.capture.flash=led ***Might want to check with MZ or Fjfalcon on these b/c of Xenon... In tweaking the camrera and camcorder is it ok to skip this one if it is not sure?

abet1017 said:
ro.media.capture.flash=led ***Might want to check with MZ or Fjfalcon on these b/c of Xenon... In tweaking the camrera and camcorder is it ok to skip this one if it is not sure?
Click to expand...
Click to collapse
Try it out but ok to skip too. I have read that this might have something to to with the LED notifications that we have all been looking for. Will keep looking into this weekend for that part.

build.prop text files
Hey Wood, would we be able to use these build.prop tweaks? There are text files to download and place on SDCard rename them to build.prop then use root explorer to move them to /system

Woodrube said:
To give your phone an HD effect fitting a little more on the screen, look for this in your current build.prop and change the 240 to:
ro.sf.lcd_density=X (225 or 230) ***This has been known to cause FC’s for the Market, so may not be a good tweak but I still put it in here just in case***
Screen ppi or font density
ro.sf.lcd_density=240 ***This is how MZ and Peshovec fixed the tiny little Korean keyboard on CM6***
Defrags database files
for I in \
‘find /data –iname “*.db”’
do \
sqlite3 $i ‘VACUUM; ’ ; ***This might be something for MZ, Fjfalcon and Peshovec could use for something, not sure what***
Click to expand...
Click to collapse
Thanks for your hard work, i'd like to put some comments
ro.sf.lcd_density -> if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
qemu.sf.lcd_density (here there is typo for the keyboard it should be qemu.sf.lcd_density, instead of ro.sf.lcd_density)
about defraging the database, may be including as part of openrecovery is better. I don't see the point to be defraged at every start..

After applying the tweaks, headset is not working... I don't know if it is related with the tweaks..... I'm using mz cm6 rc3 rom.
By rebooting I resolve the issue......

abet1017 said:
After applying the tweaks, headset is not working... I don't know if it is related with the tweaks..... I'm using mz cm6 rc3 rom.
By rebooting I resolve the issue......
Click to expand...
Click to collapse
Cool dude! Be interested in your feedback!

abet1017 said:
By rebooting I resolve the issue......
Click to expand...
Click to collapse
Don't forget you have to reboot twice.

peshovec said:
ro.sf.lcd_density -> if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
qemu.sf.lcd_density (here there is typo for the keyboard it should be qemu.sf.lcd_density, instead of ro.sf.lcd_density).
Click to expand...
Click to collapse
I will edit OP later on when I get to PC. Thanks for re-checking the lcd.density issue too

build.prop
All tweaks work fine on fjfalcons cm7
except the camera tweaks. it causes the phone to bootloop.

sebastimau said:
All tweaks work fine on fjfalcons cm7
except the camera tweaks. it causes the phone to bootloop.
Click to expand...
Click to collapse
Excellent. Will update OP and start working on fixing the camera tweaks.

Woodrube said:
Data Tweaks Increase download/upload/3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8 (or 10,12,14) Still looking for more of these though.
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
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
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
Click to expand...
Click to collapse
Hey Wood, do I type in all these commands? save after the first set? Or what do I do...?
---------- Post added at 08:47 PM ---------- Previous post was at 08:27 PM ----------
Woodrube said:
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[/B]
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
Click to expand...
Click to collapse
You see any typo's in here? The space between 163 84,? Is that correct?
***also have you tested these on Bravo?
***I got all the tweaks saved but I think I better leave well enough alone lol. Bravo is almost perfect as is everything is running great. What do you think Brian? Should I try these?

LibertyMonger said:
Hey Wood, do I type in all these commands? save after the first set? Or what do I do...?
Click to expand...
Click to collapse
You can type them all in at the same time, but when I did it I did ti in pieces to make sure each one was taking effect and if I got looped was able to determine which one caused it problem (like typo ro something like that).
LibertyMonger said:
You see any typo's in here? The space between 163 84,? Is that correct?
***also have you tested these on Bravo?
***I got all the tweaks saved but I think I better leave well enough alone lol. Bravo is almost perfect as is everything is running great. What do you think Brian? Should I try these?
Click to expand...
Click to collapse
I'll fix that in the OP. No spaces between 163 84. Should be 16384. XDA must have remarginalized them when I put it in here. I copied them from a WORD.doc when I was compiling.
I tested the data tweaks and a few of the system tweaks on Bravo and they worked fine. But if you have everything working fine for you, I would suggest either leaving it alone or bit-piece them in there. Don't want the lightning rod effect like you had in HM's ROM.
p.s. - Sorry I didn't respond sooner, I was mostly off-line this weekend and took a few extra days off. Kind of a brain recharge thing.

anybody have descriptions of these?
A lot of these are smaller / larger than what the "change to" value is...not sure how they're going to affect things, such as--
1. why are there 6 numbers for the tcp buffer sizes
2. I don't notice any performance diff modifying the max_events_per_sec
3. Proximity Delay-- is that in ms? If I think my prox delay is "too long" when I take phone away from face, I should make this smaller, right? How small is OK?

rancur3p1c said:
anybody have descriptions of these?
A lot of these are smaller / larger than what the "change to" value is...not sure how they're going to affect things, such as--
1. why are there 6 numbers for the tcp buffer sizes
2. I don't notice any performance diff modifying the max_events_per_sec
3. Proximity Delay-- is that in ms? If I think my prox delay is "too long" when I take phone away from face, I should make this smaller, right? How small is OK?
Click to expand...
Click to collapse
What ROM are you running? That would help me answer your questions a bit more clearly.

Related

[TIPS] Share your Tweaks,Tips & Fixes for Dell Streak 5 :)

Hi Guys,
Thought I'd start a little thread for people to share their tweaks and tips so that others can enjoy too
Since I'm new to the Dell Streak, this would benifit me as well.
My Tweaks & Tips:
Boot Animation:
ICS Boot Animation Landscape (Full Screen Boot)
http://forum.xda-developers.com/showthread.php?t=1459717
Just edit the 'desc.txt' file to '800 480 24p 0 0 part0'
Apps:
-Rotation Locker (force landscape/portrait for all apps)
-Startup Manager (disable startup apps to save memory)
-Battery Defender (wifi off when screen turns off, bypass reboot bug! **WiFi Policy Bug**)
-Ram Manager Pro (great memory management app) ~50MB more
-System Cleanup (move apps from /data/app to/from /system/app/)
-Rescan Media (turn off media scanning service, to increase boot time)
Tweaks:
-Increase SD Cache (Speedup SD Write/Read Speeds) *Can be done by app*
Game Compatibility Tweak(Build.prop)
Change the build.prop brand & model :
ro.product.model=HTC Vision
ro.product.brand=HTC
ro.product.manufacturer=HTC
Signal Boost Tweak:
Follow djscopesofm's guide here:
http://forum.xda-developers.com/showthread.php?t=924440
Build.prop Tweaks:
**Make sure to Backup Nandroid before playing with Build.prop**
( I broke the WiFi connectivity while playing with some unknown settings, had to nandroid restore and test over and over again. )
#Signal Boost
ro.ril.enable.dtm=1
ro.ril.gprsclass=10
ro.ril.hep=0
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.enable.a53=1
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# Force launcher into memory
ro.HOME_APP_ADJ=1
#WiFi Scan to 3mins
wifi.supplicant_scan_interval=180
#Increase Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Net speed tweaks, choose what you need
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wimax = 4096,221184,524288,4096,16384,110208
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
The Following Tweaks causes instability on certain roms/builds. (Make sure to backup before changing settings to test)
**Broke my DHCP on WiFi**
# Allow power collapse, increases battery life
ro.ril.disable.power.collapse=0
# Puts the CPU into deep sleep but preserves registers
pm.sleep_mode=1
# When moving through zones or losing signal, having a delay
# smooths out constant disconnects and reconnects, saves battery life
ro.mot.eri.losalert.delay=1000
#To disable USB debugging popup
persist.adb.notify=0
#Disable error checking
ro.kernel.android.checkjni=0
#Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
#Decrease dialing out delay
ro.telephony.call_ring.delay=0
#Raise photo and video recording quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
#camera/video
ro.camcorder.videoModes=true
ro.media.capture.maxres=5m
#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-record=false
#Disable Boot Animation
debug.sf.nobootanimation=0
Click to expand...
Click to collapse
Fixes:
-change build.prop to HTC Vision/Google Nexus One for apps compatibility. (Games mostly)
-Delete Rogers's APN (isp.apn) to enable WiFi Tethering **Rogers AT&T Network related**
I will continue to keep adding to this list as I keep playing with my Streak.
Hope you guys share some tips with me too!
ROM
Official Olleh 407, thanks to http://www.streaksmart.com/ for the heads-up and to the Manii for the manual and support.
Set ro.secure=0 in default.prop by flashing a boot.img from GingerStreak 2.4
Cleanup
Used adb to delete unwanted apps:
Removed all Olleh market apps
Removed Lota, Logservice and Logmaster2 (both apk and odex files)
Removed Accuweather and ZinioReader
Tweaks
Installed free ADWLauncher from the market, replacing Dell Stage UI
Locked main screen to portrait
Custom Bootanimation
Removed the camera_click.ogg file from system/media/audio/ui
Custom /etc/hosts file sending advertising sites to 127.0.0.1
Dr Doppio said:
ROM
Set ro.secure=0 in default.prop by flashing a boot.img from GingerStreak 2.4
Click to expand...
Click to collapse
whats this sposed to do mate?
ro.secure is already set to 0 in all custom kernels.
I'm pretty sure you cant change it once the device has booted up, you need to modify the kernel (or rather it's ramdisk) and reflash.
crashDebug said:
whats this sposed to do mate?
Click to expand...
Click to collapse
Gives you root rights from adb without installing superuser and busybox. My approach may not be the proper way to achieve this, see below.
TheManii said:
ro.secure is already set to 0 in all custom kernels.
Click to expand...
Click to collapse
Yes, but I had flashed the official Olleh ROM, since that was the first time I was changing ROM and I wanted to be on the safe(r) side. I would now recommend to other noobs such as myself to go for a streamlined ROM, but then I didn't know better.
I'm pretty sure you cant change it once the device has booted up, you need to modify the kernel (or rather it's ramdisk) and reflash.
Click to expand...
Click to collapse
As far as I figured, changing dafault.prop required unpacking the bootimg, editing the file, repacking the image and flashing it back. I took a riskier shortcut to extract a bootimg from a different ROM that I assumed was pre-rooted and likely to have ro.secure=0. It was a stupid thing to do, but it luckily worked, and all it took was three lines with fastboot. I may add that the contents of the file changed a few times after reboots, and I noticed a file with ro.secure=1, ro.debuggable=1 at some point. I've also found in the file /firstboot/permissionadb.err a line "date time <adb>: permission secure=1", supposedly logging an error that I had caused by fooling around...
official olleh 407 installed + deodexed + language pack + portrait hack by themanii + superuser (rooted) + MattedbBlues theme + GoLauncher EX.
-tweaks
-using handcent sms (with darkness skin) for simple solution to everride the convertion from sms to mms
-i consider a tweak that i don't have any memory manager or things like that, i just use the applications i need and if something bothers me, i just freeze it using titanium backup.
-for end call freeze problem, i just use the option from settings>accesibility>power button ends call, solves that problem and i think is more "accesible".
-everything runs smooth, almost no problems i would say, but i noticed some problems, wifi tends to "lag" when using instant messaging applications, i know that this is a known bug, but works pretty ok otherwise, also i use Wifi Static for almost any wireless network i connect to.
-another problem i have noticed is that sometimes it just doesn't want to send SMS's, it just gives me a undelivered notification, and i resend it again, i also noticed that the sms is sent, but not entirely, so when this happens, if i resend it 4 times, that person recieves 3 incomplete messages and finally the complete one, also, this is a farly rare bug.
hope this helps!
Added new tweaks.
We thank you very much for your time in order to have the best settings in our phones...Is it possible to change the wifi settings in order to see channels 12-14 at 2.2.2 official android?
these are pretty 407/olleh related, and I confirm they are working in this rom ONLY.
here goes
ro.build.CUSTOMER_CONFIG_KT=0
to disable the sms/mms conversion in the stock messaging app.
note that there also is a line like this
ro.build.CONFIG_CUSTOMER_KT
which I have no idea what it does (but set it to 0 anyway)
ro.build.FEATURE.SHUTTERSOUND=0
set to 0 to show the shutter option in the camera app (note: this option alone does NOT disable the shutter sound, it just shows the option in the app!)
ro.build.OEM_PRESET_APN_LOCK=1
ro.build.OEM_PRESET_APN_HIDE=1
grants the ability to disable and delete preset APNs from Wireless Settings. They are locked in 407
debug.composition.type=gpu
to enable the "CRT off" animation which is disabled by default.
these are not all my findings, thanks to the original discoverers!
-----NEW FIX
I had a problem for some time now with long sms's, not the mms to sms convertion, solved it with handcent sms, but the phone would simply not send bigger than 3-4x160 sms's.
Code:
-put your mobile phone to GSM only mode, at mobile networks settings.
(this problem seems to be solved for now, hope this helps...)
Ya'll have covered just about everything I already do. One quick easy littke thing I found helpful is GPS Status & Toolbox for keeping the GPS and compass in line. Letting the app update AGPS data daily helps GPS lock time and there is a compass calibration app that I need to use regurely.
I'm not sure if other gb roms have it but in dsc 0.72 I stumbled upon the option to set up peak and non peak hours and shut data off after a set amount of time, if anyone's interested here's how to get to it
settings>wireless and networks>mobile networks>schedule data connection
with the non peak hours set up for when i'm asleep and peak to 15 minutes I'm able to get close to two and half days on a single charge with a few 5 minute phone calls and ~400 texts sent per day
Edit:
Setting this up WILL prevent all apps that rely on syncing while the phone is asleep from syncing, it's not much of an issue for me but to those who rely on apps syncing while the phone is asleep should be advised to set up non peak hours data shut off only.
[FIX] Wallstreak app - to center my 800 x 480 wallpapers perfectly
[TIP] Gingerstreak - 2.4.4 Rom with DSC-Team-Phoenix kernel , works flawless
[TIP] A Touch of ICS theme - to give it a nice black and blue look
[FIX] Widgetlocker - to bypass the default lock screen and make it a bit more usefull
[TIP] Extended controls - when the default power controll app is just a bit to limited for your taste
[FIX] Opera Mobile - a bug that my streak has is a browser that takes forever to load, Opera mobile solves this
[TIP] Streakled - a nice app that uses the Streaks led lights to notify you when youve received a e-mail or text message
simonbuschers said:
...
[FIX] Opera Mobile - a bug that my streak has is a browser that takes forever to load, Opera mobile solves this
...
Click to expand...
Click to collapse
I have noticed that cleaning up the cache changes browser load times immensely, from almost instanteneous after clean up to close to 1 minute after a couple of weeks without one. Other than that, I love desktop Opera, but haven't used the mobile version yet...

List Of Some Build.prop Tweaks

List Of Some Build.prop Tweaks
You Know the Drill i'm NOT responsible if anything happens to you phone
Click to expand...
Click to collapse
# 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
# 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
#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.
Use NotePad++ to edit via PC
Nice and usefull thread mate.
I don't know about windowsmgr.max_events_per_sec=500.Are you sure about? Cause for example in sgiii the default is 300 that is the highest i ever saw.
I just want to add a warning for new users who want to change build.prop.
The most of explorers like es explorer will make a stuck on boot after the changes (on ics ROM at least), so its recommended to edit build.prop before rom installation via pc.
Sent from my GT-N7000 using Tapatalk 2
eliashadow said:
Nice and usefull thread mate.
I don't know about windowsmgr.max_events_per_sec=500.Are you sure about? Cause for example in sgiii the default is 300 that is the highest i ever saw.
I just want to add a warning for new users who want to change build.prop.
The most of explorers like es explorer will make a stuck on boot after the changes (on ics ROM at least), so its recommended to edit build.prop before rom installation via pc.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
try to adjust between 150 to 500
eliashadow said:
Nice and usefull thread mate.
I don't know about windowsmgr.max_events_per_sec=500.Are you sure about? Cause for example in sgiii the default is 300 that is the highest i ever saw.
I just want to add a warning for new users who want to change build.prop.
The most of explorers like es explorer will make a stuck on boot after the changes (on ics ROM at least), so its recommended to edit build.prop before rom installation via pc.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
For me, editing with root explorer works perfectly.
Sent from my GT-N7000 using Tapatalk 2
I usually make a copy of build.prop in system. In case of boot issue, you can go in CWM and replace the modded with original.
eliashadow said:
Nice and usefull thread mate.
I don't know about windowsmgr.max_events_per_sec=500.Are you sure about? Cause for example in sgiii the default is 300 that is the highest i ever saw.
I just want to add a warning for new users who want to change build.prop.
The most of explorers like es explorer will make a stuck on boot after the changes (on ics ROM at least), so its recommended to edit build.prop before rom installation via pc.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
how to edit via pc?, notepad is weird
crossmedia said:
how to edit via pc?, notepad is weird
Click to expand...
Click to collapse
use Notepad++
Really useful topic Thanks. Will see if this helps gaining some more battery time.
Edit : added end of post.
Sent from my GT-N7000 using xda premium
thx that was very helpful, but i have one question
thehackersz said:
List Of Some Build.prop Tweaks
# Increasing The Video Recording Quality
ro.media.enc.hprof.vid.bps=8000000
Click to expand...
Click to collapse
as far as i know the note records 720p videos at 11mbps and records 1080p videos at 17mbps
how can a lower value (8mbps) increase recording quality
it would be more logical to set it to something like 20000000 (20mbps) or even more in order to improve quality
as it turns out, samsung camera parameters are stored /system/etc/media_profiles.xml
so changing these probably wont change anything
on the other increasing bitrate in the mentioned file does the trick and you can set very high bitrates (up to 30mbps for me)
but you can experiment with lgcamera tool before stting a defintive value
https://play.google.com/store/apps/details?id=rubberbigpepper.lgCamera&hl=fr
ro.ril.hsxpa=2 should be 3
And gprs class 12
thehackersz said:
List Of Some Build.prop Tweaks
#Force To Remain Launcher In Memory
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
This might result in the constant FC of Apex launcher. Apex conflicts being getting forced in memory from bootup after rom flash and hence FC. So kindly keep a second launcher in your /system/apps if you gonna use Apex with this tweak until Apex gets fixed.
(Side note - Happens in JB)
Thanks for listing everything out
With notecore kernel you so not breed does tweaks.
thehackersz said:
List Of Some Build.prop Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Click to expand...
Click to collapse
Ancient obsolete options that do nothing on recent Samsung devices
# Off The Proximity Quiclky After Call
mot.proximity.delay=25
ro.lge.proximity.delay=25
Click to expand...
Click to collapse
I think the fact that these will do nothing on a Samsung should be obvious from the "mot" (Motorola) and "LGE" (LG Electronics)...
# Signal Tweaks
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
Click to expand...
Click to collapse
Similarly, these will do nothing on a Samsung device. The reason why should, just like the above, be obvious...
Most of the others you listed likely won't do anything either - Over in the Infuse community, they were tested and found to do nothing. In addition, doing "strings" on the RIL binaries didn't find those other items in Samsung RILs.
# Power Save Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Click to expand...
Click to collapse
You copypastaed these twice? And as stated before, these are ancient obsolete options that do nothing on modern Samsung devices.
#improve battery under no signal
ro.mot.eri.losalert.delay=1000
Click to expand...
Click to collapse
This will do nothing. The reason why should be obvious (see above)
Config
Whats the best build.prop config for Cleanote 5 and Notecore kernel performance wise?
Any toughts?
Indeed the bitrate mentioned previosly is indeed lower than the stock figure, ive pulled this from my version also.
as well as max events build prop. This has been confirmed as useless even google states 90 is the most as it should be 1.5 times default fps which is 60. By setting this above 90 you induced stutter and lag, as the remaining processing time required to handle the additional values is counteractive
The link below is a good read on why some tweaks are counter productive
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
thehackersz said:
List Of Some Build.prop Tweaks
Wipe both Caches in Recovery after adding or changing the above lines.
Use NotePad++ to edit via PC
Click to expand...
Click to collapse
Both Caches ?
nokiamodeln91 said:
Both Caches ?
Click to expand...
Click to collapse
I guess that is refering to cache and dalvik.
Im sory if this doesnt make snse.. But in cwm.. There is option to wipe dalvik cache. .. Wheres the other... Is that cache partition?
nokiamodeln91 said:
Im sory if this doesnt make snse.. But in cwm.. There is option to wipe dalvik cache. .. Wheres the other... Is that cache partition?
Click to expand...
Click to collapse
yes, wipe cache partition and under advanced wipe dalvik cache
Drivingdroids said:
Whats the best build.prop config for Cleanote 5 and Notecore kernel performance wise?
Any toughts?
Click to expand...
Click to collapse
Flash speedmod kernel !

[GUIDE]Build.prop explained [Updated 11/30]

Hello fellow xda members. Today i present you my little tutorial about the build.prop file. I have taken the reference build.prop from k2wl's aokp rom.
Please make a nandroid backup in case something goes wrong.
I´m not responsible for any damages to your phone.
CREDITS
-Chris_84
-k2wl (for refrence build.prop)
-xda-developers
Click to expand...
Click to collapse
What is the build.prop ?
TheManii: Build.prop is what holds the majority of the runtime flags that are used when android boots, think of it as being
similar to config.sys on dos or environment variables in various OS's. It only holds variables, it cant run any scripts on it's own. Whatever is placed inside depends on android itself to pay attention to the flag and actually use it.
In easier words it is a file in your android system that maintains certain parameters on your phone in order for your phone to run.
These properties are device specific and can change depending upon the various specifications of the device and also includes some system properties.
Click to expand...
Click to collapse
Where is build.prop located?
You will find the build.prop file in root/system/build.prop. You can open it with a root explorer/es explorer which has a built in text editor.
Click to expand...
Click to collapse
How to edit build.prop?
1.With a root explorer or ES file exploreror.
copy /system/build.prop to the root of the internal sdcard (/mnt/sdcard).
2.Edit it using a text editor (ES and root explorer have an inbuilt text editor) or on computer using notepad++.
3.Be careful as some of the parameters already exist. Just change their values.
4. Overwrite /system/build.prop with the edited file.
5. Make sure that the permissions are still rw-r--r--:
6. Reboot into recovery
wipe cache and dalvik cache.
Make sure to edit existing line if present
Click to expand...
Click to collapse
LETS BEGIN
This mentions that the build prop is built by build info shell script during the compilation of the ROM.
# begin build properties
# autogenerated by buildinfo.sh
Version name of 4.2.2(jellybean)
ro.build.id=JDQ39
Current rom version on phone
ro.build.display.id=aokp_i9082-userdebug 4.2.2 JDQ39 eng.k2wl.20130827.005402
Your current modem version
ro.build.version.incremental= eng.k2wl.20130827.005402
Current sdk version of framework plus codename
ro.build.version.sdk=17
ro.build.version.codename=REL
Current android version on phone
ro.build.version.release=4.2.2
This is the time and date of when the Kernel was built.
ro.build.date=Aug 27 00:54:58 IST 2013
Other Kernal Details
ro.build.date.utc=1377545098
ro.build.type=userdebug
ro.build.user=android-build
ro.build.host=k2wl-HP-EliteBook-8440p
Test keys means that the ROM is not an official version of the ROM. Release keys are for official releases.
ro.build.tags=release-keys
Model Number
ro.product.model=GT-I9082
Phone Manufacturer
ro.product.brand=samsung
This name is the codename of the
device.
For example-
HTC Explorer - pico,
Nexus 7 - grouper
Nexus 4 - mako
Galaxy Ace - cooper
Grand - baffin
ro.product.name=baffin
System Images
It is the first instruction set (CPU + ABI
convention type) of the code. Ours is an arm type arch cpu and abi version 7a )
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
Default Country settings.
Language of software
Region of software
ro.product.locale.language=en
ro.product.locale.region=GB
If you not able to connect to your wifi, you can try to set here the same number of channels as your router currently got. For example: Your router is set to 12 channels you can paste the same number in here.
ro.wifi.channels=
Here you can set the standard media sounds for each notification. But the file should be present in system/media/...
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=A_toy_watch.ogg
Your phone is still usable, even if sim card is not inserted.
keyguard.no_require_sim=true
Default format of date
ro.com.android.dateformat=mm-dd-yyyy
Your bluetooth name
net.bt.name=Samsung Galaxy Grand Duos
Disable Boot Animation
debug.sf.nobootanimation=1
Your battery capacity (in MHz)
ro.semc.batt.capacity=1200
The setup wizard when you flash a custom rom and it asks your language, gmail id etc
ro.setupwizard.mode=DISABLED (or ENABLED or OPTIONAL)
Here you can set the default density (in pixel per inch)(default is 240)
ro.sf.lcd_density=240
Minimum brightness of your screen
ro.lcd_min_brightness=40
Your default brightness
ro.lcd_brightness=160
Basically you control the class-loading and dalvik-vm there. Here you can set different values.
v=a means verify all,
v=f means verify full,
o=v means optimize verify,
v=n will turn off bytecode verification
u=n means do not optimize for unprocessor
m=y means register maps yes
dalvik.vm.dexopt-flags=m=y
Enables multi touch
ro.product.multi_touch_enabled=true
Max number of multi touches
ro.product.max_num_touch=2
Disable sending usage data
ro.config.nocheckin=1
Here you can set the delay of time your phone starts to ring when you recieve a call.
ro.telephony.call_ring.delay=0 (0 means disabled)
Disable waking up of phone by volume buttons ro.config.hwfeature_wakeupkey=0
Off the proximity quickly after call
mot.proximity.delay=25
ro.lge.proximity.delay=25
This property is supposed to keep the launcher in memory under the assumption that it would somehow make it faster
ro.HOME_APP_ADJ=1
Allows your phone to use an ext-4 file system
ro.ext4fs=1
Disables debug icon on status bar
persist.adb.notify=0
Key lights stay on while screen is on
ro.mot.buttonlight.timeout=0
Disable notification sound when SD is inserted
persist.service.mount.playsnd=0
Disables location of device. Also delete /system/app/networklocation.apk and /system/framework/com.android.location.provider
.jar
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
To enable the timeout of hard key lights to stay on when screen is on and lights off when screen is off
ro.mot.buttonlight.timeout=0
To enable the menu button too unlock the phone
Not sure if it works
ro.config.hw_menu_unlockscreen=true
Proximity sensor debounce time
mot.proximity.delay=450
mot.proximity.distance=60
Default data roaming is enabled
ro.com.android.dataroaming=true
Judging from its name I assume people think it disables some kind of logging mechanism. But 'no'.The “ulog” referred to in this property is an HTC-specific service that HTC calls the User Behavior Logging Service. This service is centered around tracking user behavior related to the HTC Sense launcher. The HTC ULog tracks some basic things like the number of ANRs and/or crashes, but it also potentially tacks things like your wallpaper selection, your installed apps and your locatio (HTC specific)
profiler.force_disable_ulog=1
Unlike the latter, this one actually does turn off sending device crash log data to HTC. This will make your device run faster/smoother/better (HTC specific)
profiler.force_disable_err_rpt=1
# Increase Quality Of MediaStreaming
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
# 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
# Google DNS Tweak
net.wlan0.dns1=8.8.8.8
net.wlan0.dns2=8.8.4.4
net.pdp0.dns1=8.8.8.8
net.pdp0.dns2=8.8.4.4
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.eth0.dns1=8.8.8.8
net.eth0.dns2=8.8.4.4
net.gprs.dns1=8.8.8.8
net.gprs.dns2=8.8.4.4
# Touch Responsiveness
Scrolling Responsiveness
Faster Scrolling
debug.performance.tuning=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=500
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
# Media Tweaks
Increase photo and video quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100
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
Better Flashlight intensity & camera-flash quality
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=65
ro.media.capture.flashIntensity=70
# Signal Tweaks
Defines weither to use [0=UMTS] [1=HSDPA only] [2=HSDPA & HSUPA] [5=No significant information has been found but it makes the switch between WiFi and HSxPA nearly instantaneous (note works like "2" but better)]
Here you can improve your Data speed if your provider supports it. Set this to 0 if you want lower speeds, and up to 2 for faster speeds.
ro.ril.hsxpa=2
Defines what class speeds to use with EDGE.
Class 10 will significantly save battery, unless you use EDGE/GPRS instead of 3G)
12 is the default value for most modern phones.
Setting this value to 12 can improve the data speed significant on lower connections.
ro.ril.gprsclass=10
0=off
1=Default
no change when turned off. In some phones stability is increased when turned off.
ro.ril.hep=1
Enable "dual transfer mode" on EDGE networks. Requires different GPRS class settings. Only set this to 1 if your network allows simultaneous transfer of Circuit switched (CS) voice and Packet switched (PS) data over the same radio channel (ARFCN). Turning this off on some carriers, including Optus (AU) and AT&T increases upload speeds.
ro.ril.enable.dtm=1
Enable increased ciphering on
HSDPA/HSUPA, for increased security, but decrease in performance.
ro.ril.enable.a53=1
Adds the 3G prefix e.g. Optus 3G, etc. Purely cosmetic
ro.ril.enable.3g.prefix=1
Other signal tweaks
ro.ril.hsdpa.category=10
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
# Dalvik VM tweaks
This controls the smallest amount of memory given to a single application.
dalvik.vm.heapstartsize=5m
This value represents the maximum allowed amount of memory that the Dalvik Virtual Machine can allocate to the applications. A higher value means faster apps but more RAM consumption.
dalvik.vm.heapgrowthlimit=48m
The dalvik.vm.heapsize property defines an absolute maximum for the heap size for an application
dalvik.vm.heapsize=128m
This point stands for "Debug SurfaceFlinger Hardware" or GPU hardware acceleration
debug.sf.hw=1
Explained Earlier(change to this to load apps faster and free more ram)
dalvik.vm.dexopt-flags=m=v,o=y or m=y
This property can set the execution mode of the Dalvik VM. The VM can run in three modes: fast, portable, and JIT. It is possible to compile Android without JIT support, but the default is to include it. In general, JIT is the execution mode you are going to want on your device. This is why you will see most build.prop files setting this property to “int:jit”.
In ICS or lower , there is no need to define this setting in your build.prop
dalvik.vm.execution-mode=int:jit or int:fast
Others
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapmaxfree=2m
dalvik.vm.lockprof.threshold=500
# Improve battery
improve battery under no signal
ro.mot.eri.losalert.delay=1000
Bluetooth OPP low speed to save power
debug.bt.lowspeed=true
Wifi to scan less frequently
wifi.supplicant_scan_interval=240
System can free more Ram when needed
persist.sys.purgeable_assets=1
This property purports to significantly increase your battery life by putting signaling your device to use a better power mode when your phone is idle. Recommended values range from 0, 1, 4 with the most common be 1
pm.sleep_mode=1
To save battery turn off wifi, internet, bluetooth, gps, lower the brightness at night, kill all apps running in background, clear ram, underclock if kernal supports and also switch off the animations settings>display>no animation.
Reserved
Sent from my GT-I9082 using XDA Premium 4 mobile app
that is awesome work
informative posts. :good:
medozse7s said:
that is awesome work
Click to expand...
Click to collapse
Dwama said:
informative posts. :good:
Click to expand...
Click to collapse
Thank you very much! It's a honor to get such a good feedback from ual!
Sent from my GT-I9082 using XDA Premium 4 mobile app
Digitizer problem
Hello,
any idea if there is a property which would control the digitizer orientation? My digitizer got mixed up after flashing a new ROM version and the manufacturer`s stock is not the same stock as used to be inside the tablet.
ATM my digitizer is mirrored top-down in landscape and there might be a build.prop to compensate. Does such setting exist?
Joe
awesome NOOB guide for the build.prop! had a doubt, can i edit the build.prop and change the wallpaper?
when the rom is loaded i want the default wallpaper to be like the stock rom! is it possible?
if so then which are the lines i need to edit! pls inform!
WBR
ReyTech.
Awesome Awesome Guide....Very informative Post...Keep up the good work...
Sent from my GT-I9082 using XDA Premium 4 mobile app
Awesome work... Hats off..... Thank you...
Sent from my GT-I9082 using XDA Premium 4 mobile app
joeprusa said:
Hello,
any idea if there is a property which would control the digitizer orientation? My digitizer got mixed up after flashing a new ROM version and the manufacturer`s stock is not the same stock as used to be inside the tablet.
ATM my digitizer is mirrored top-down in landscape and there might be a build.prop to compensate. Does such setting exist?
Joe
Click to expand...
Click to collapse
Two methods to do that.
1. By editing your build.prop
ro.sf.hwrotation=xx in /system/build.prop should do the job.
xx = 00 (portrait mode - default)
xx = 90 (landscape mode)
xx = 180 (full tilted)
2. What you need to do is edit yourAndroidManifest.xml*file and specify the orientation for your activity, as well as handle orientation changes yourself:
Then your activity will always run in a landscape mode regardless of the device orientation.
However note that this will affect all applications running on the device.
ReyTech said:
awesome NOOB guide for the build.prop! had a doubt, can i edit the build.prop and change the wallpaper?
when the rom is loaded i want the default wallpa per to be like the stock rom! is it possible?
if so then which are the lines i need to edit! pls inform!
WBR
ReyTech.
Click to expand...
Click to collapse
Decompile framework-res.apk then go to
res/drawable-sw600dp-nodpi/default_wallpaper.jpg
Replace the image that you want with resolution of 1440x1080.
Recompile and push the framework-res.apk to system/framework/here.
Hope it helps.
Amazing!!!!!!!!!!!!!!!!!!
Wowwwwwwwwwww..... Great Work Mate...........
Thumbs Up :good:
Thanks man ......helped a lot to understand the inside of android.....
Sent from my GT-I9082 using Tapatalk
GREAT explanation !! Is all of the information still relevant to KitKat ? I just want to be sure.
Can anyone tell me what line is this for?
" persist.sys.recovery_update=false "
thankss alott
Any way to enable the notification led from the build
Sounds Great, Thanks for sharing.
Great topic
losing signal
hi any one has/have an idea for fixing my problem to my kata i3s mt6582 kitkat 4.4.2 when in my house i have a signal i can use data connection surfing etc,
but when it come to my work or when i go to my work my signal are losing and its totally drop the signal,
any idea on how to fix lossing of signal
:crying::crying::crying::crying::crying::crying::crying::crying:
persist.sys.recovery_update=false
subhad43 said:
Can anyone tell me what line is this for?
" persist.sys.recovery_update=false "
Click to expand...
Click to collapse
This basically means that when the system will update/auto update over the air, or OTA, or Delta updates, or for that sake even when you manually flash the new update, the system will not replace your custom recovery.
You can view this under the Developer Option, where the option "Update Recovery" or "Update Cyanogen Recovery" is turned off by default.
This is to help with custom recovery , as inbuilt recovery is limited and does not have all the customisations.

Build.Prop tweaks working for most on LG G Stylo [Updated 9/18/2015]

Attention if you try this and end up with a brick or your device transforms and tries to destroy you; it's not my fault you did this not me. So just read all of this thread not just the O.P to get out of a bind if you reply with "the thread is too long i wont read it please help" don't expect anything short of "there's a search bar use it"
okay so i thought i'd make this thread over here as well since i'm hosting my threads on both XDA and AF
just a quick copy and paste
Here are some build.prop tweaks that i have tried out, there are plenty of ways to edit the build.prop file i personally use root browser (file explorer) which has a RB Text editor....
So the build prop editors on android tend to cut off the build.prop characters after a certain point so to get around this copy your build.prop from /system to your SD. Then transfer it from SD to the desktop of your computer after your comfortable with the edits; move the "original" one in the SD card to a new sub folder which probably want to name "original prop" then copy the edited one to the root of your SD then replace the one you have in /system then fix the permissions to 0644 and reboot and profit (you can use gedit on Ubuntu or Notepad++ on windows don't know about mac tho)
Does your phone tell you that you need to purchase an upgrade to your plan whenever you try and tether? Depending on your carrier, this line may help:
net.tethering.noprovisioning=true
#Helps scrolling responsiveness
windowsmgr.max_events_per_sec=240
#Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
#you can use multiwindow for all apps
#Default value is false, edit to true
persist.splitwindow.support_all=true
#Enable Permanent LTE Option
#default value is 8
ro.telephony.default_network=10
found this line in the prop
#property to enable DS2 Dap
audio.dolby.ds2.enable=false (if change to true, would also need to edit lge.music.xml in the etc folder to get it to work) JayBondzeWell has provided the edited file i will upload here but his part of the work (and you just unzip and replace your existing .xml file of the same name then fix permissions to 0644)
#Multi Users
fw.max_users=30
fw.show_multiuserui=1
^^^^thanks @Krlypumaa
#Liquid Smooth Ui (not the custom rom)
persist.service.lgospd.enable=0
persist.service.pcsync.enable=0
ro.ril.enable.a52=1
ro.ril.enable.a53=0
#Change android name and version
ro.build.display.id=Your ROM name
ro.build.version.release=5.1.1 (Android version number)
#More volume steps in call. (default is 6)
ro.config.vc_call_steps=20
#Default volume in call. (default is 3)
ro.config.vc_call_default=10
#Better call voice quality.
ro.ril.enable.amr.wideband=1
#Increase Quality Of Media Streaming (add to #system props for the MM modules)
media.stagefright.enable-meta=true
media.stagefright.enable-rtsp=true
#Increase VM Heap Size (default is 36m)
dalvik.vm.heapsize=72m
persist.sys.dalvik.hyperthreading=true
#makes apps load faster and frees more ram.
dalvik.vm.dexopt-flags=m=v,o=y
#Google DNS Tweak
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.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.wlan0.dns1=8.8.8.8
net.wlan0.dns2=8.8.4.4
net.eth0.dns1=8.8.8.8
net.eth0.dns2=8.8.4.4
net.gprs.dns1=8.8.8.8
net.gprs.dns2=8.8.4.4
#Game tweaks
persist.sys.NV_FPSLIMIT=60
persist.sys.NV_POWERMODE=1
persist.sys.NV_PROFVER=15
persist.sys.NV_STEREOCTRL=0
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_STEREOSEP=20
persist.sys.purgeable_assets=1
htc.audio.alt.enable=0
htc.audio.hac.enable=0
ro.config.hw_quickpoweron=true
#Qualcomm tweaks
com.qc.hardware=1
debug.qc.hardware=true
debug.qctwa.preservebuf=1
debug.qctwa.statusbar=1
#Better internet browsing & download speed
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.hspa=6144,87380,524288,6144,163 84,262144
net.tcp.buffersize.lte=524288,1048576,2097152,5242 88,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,8 7380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144, 87380,1048576
#Increase jpg quality to 100%
ro.media.enc.jpeg.quality=100
# Rendering Tweaks
debug.composition.type=c2d
debug.egl.hw=1
debug.enabletr=true
debug.overlayui.enable=1
debug.qctwa.preservebuf=1
debug.performance.tuning=1
debug.sf.hw=1
dev.pm.dyn_samplingrate=1
hw3d.force=1
ro.config.disable.hw_accel=false
ro.fb.mode=1
ro.sf.compbypass.enable=0
ro.vold.umsdirtyratio=20
persist.sys.composition.type=c2d
persist.sys.ui.hw=1
video.accelerate.hw=1
# Enable GPU Acceleration
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
persist.sys.composition.type=gpu
debug.qc.hardware=true
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
hw3d.force=1
ro.product.gpu.driver=1
persist.sys.use_16bpp_alpha=1
persist.sampling_profiler=0
hwui.render_dirty_regions=false
hwui.disable_vsync=true
# Saves some battery without reducing performances
wifi.supplicant_scan_interval=497
pm.sleep_mode=1
power.saving.mode=1
ro.ril.disable.power.collapse=0
ro.vold.umsdirtyratio=20
# Increase general Performance
debug.performance.tuning=1
# Increase some Performance
ro.secure=0
persist.sys.use_16bpp_alpha=1
ro.product.gpu.driver=1
ro.min.fling_velocity=8000
# Reduce the black screen time of the proximity sensor
ro.lge.proximity.delay=15
mot.proximity.delay=15
# Increase camera's photo and video recording quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=65
# Better Flashlight intensity and camera-flash quality
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
if you know of any more that work please comment them i will probably add them to the OP
Place this under addtional build properties under the dalvik heapsizemax line
What this does is helps the multithread line to tell the cpu to easily do more faster proccessing without overheating
persist.sys.dalvik.hyperthreading=true
:thumbup:
Sent from my LGMS631 using XDA Free mobile app
this post has nothing to with the above just trying something dd if=/storage/external_SD/libhtccamera.so of=/system/priv-app/HtcCamera/lib/arm/libhtccamera.so
6th_Hokage said:
this post has nothing to with the above just trying something dd if=/storage/external_SD/libhtccamera.so of=/system/priv-app/HtcCamera/lib/arm/libhtccamera.so
Click to expand...
Click to collapse
I knw you trying to see why htc cam does not allow you to insert pics... You need the htc.gallery to run with it.
Sent from my LGMS631 using XDA Free mobile app
Krlypumaa said:
I knw you trying to see why htc cam does not allow you to insert pics... You need the htc.gallery to run with it.
Sent from my LGMS631 using XDA Free mobile app
Click to expand...
Click to collapse
i was trying to get it to save pics to the external SD lol i don't mind not seeing the little thumbnails after the picture is taken
6th_Hokage said:
i was trying to get it to save pics to the external SD lol i don't mind not seeing the little thumbnails after the picture is taken
Click to expand...
Click to collapse
I jave the gallery app even yhe flashing.zip for the both cam n gallery... I can send it to you... The glash?zip will allow you to take pic in 4k, UHD and same as vids the only thing is that we don't have the 20mp cam so its very blub pics... But cool...
Sent from my LGMS631 using XDA Free mobile app
okay i added some more info if you guys wanna look
New for all of you....
http://forum.xda-developers.com/showthread.php?t=3206617
LG G STYLO (T-Mobile LGH631 & MetroPCS LGMS631) COLOR.OS CAMERA+Plugins
Support your DEVs https://www.gofundme.com/krlypumaa
Krlypumaa said:
New for all of you....
http://forum.xda-developers.com/showthread.php?t=3206617
LG G STYLO (T-Mobile LGH631 & MetroPCS LGMS631) COLOR.OS CAMERA+Plugins
Support your DEVs https://www.gofundme.com/krlypumaa
Click to expand...
Click to collapse
my phone dont have a build prop ? im on extrm turbo Rom
thugmafia said:
my phone dont have a build prop ? im on extrm turbo Rom
Click to expand...
Click to collapse
you'll have to ask where it's located then since to my knowledge the phone wont run unless it has one
thugmafia said:
my phone dont have a build prop ? im on extrm turbo Rom
Click to expand...
Click to collapse
it's located here /system/build.prop
Hey guys. I made a mistake. I made a copy of my build.prop and long story short, the file became corrupted. How do I fix this? Get a copy of another build.prop same device?
MrGanjaGreen420 said:
Hey guys. I made a mistake. I made a copy of my build.prop and long story short, the file became corrupted. How do I fix this? Get a copy of another build.prop same device?
Click to expand...
Click to collapse
You could just remove the edits from the one that is working
6th_Hokage said:
You could just remove the edits from the one that is working
Click to expand...
Click to collapse
i dont have one nor a copy. it just disappeared
MrGanjaGreen420 said:
i dont have one nor a copy. it just disappeared
Click to expand...
Click to collapse
you deleted the original?
6th_Hokage said:
you deleted the original?
Click to expand...
Click to collapse
yeah some how i deleted the modified one and then attempted to move the original back with root browser and it said failed and then the file was not there??
"if you try this and end up with a brick or your device transforms and tries to destroy you; it's not my fault you did this not me. "
Well, my phone is definitely bricked now because I followed your advice. Therefore, I'm going to tell everyone else that OP is a complete moron and has no idea what he is talking about. Do not listen to anything this poster says. It's your fault for posting ****ty, inaccurate instructions.
ihateboostphones said:
"if you try this and end up with a brick or your device transforms and tries to destroy you; it's not my fault you did this not me. "
Well, my phone is definitely bricked now because I followed your advice. Therefore, I'm going to tell everyone else that OP is a complete moron and has no idea what he is talking about. Do not listen to anything this poster says. It's your fault for posting ****ty, inaccurate instructions.
Click to expand...
Click to collapse
Maybe you shouldn't mess with your phone if you dont know what you're doing. Editing the build prop isn't hard and especially isn't if you follow directions and lord forbid you do a little research.
Thediesel1972 said:
Maybe you shouldn't mess with your phone if you dont know what you're doing. Editing the build prop isn't hard and especially isn't if you follow directions and lord forbid you do a little research.
Click to expand...
Click to collapse
Maybe you shouldn't make assumptions about the level of expertise of random people on the internet. Copy+Paste of those build.prop lines = dead phone. That means that the properties written are wrong. Plain and simple.
No worries though, the fix is really simple now! All I have to do is rip out the logic board, throw it in the trash, and put a new one in! Couldn't be simpler! /s
There is no possible way that you added all of those build.prop tweaks and still ended up with a working phone on the Boost rom. ADB pull your build.prop list and post it here, or it didn't happen.
ihateboostphones said:
Maybe you shouldn't make assumptions about the level of expertise of random people on the internet. Copy+Paste of those build.prop lines = dead phone. That means that the properties written are wrong. Plain and simple.
No worries though, the fix is really simple now! All I have to do is rip out the logic board, throw it in the trash, and put a new one in! Couldn't be simpler! /s
There is no possible way that you added all of those build.prop tweaks and still ended up with a working phone on the Boost rom. ADB pull your build.prop list and post it here, or it didn't happen.
Click to expand...
Click to collapse
I never said I used all of them at the same time...I just confirmed what did work some did work together tho

Fire TV Stick 4K/Lite/3rd Gen Build.prop Tweaks (Works with latest FireOS) (Need Root)

Before I start this tweaking guide for the Fire TV Stick 4K/Lite/3rd Gen, I'm not responsible for what you do to your device. Please follow this guide carefully to prevent confusion. First of all, you need to be rooted and unlocked to add these tweaks to your Fire TV Stick 4K. You also need a USB keyboard or a Bluetooth keyboard to successfully type in these tweaks yourself in the file, build.prop. Due to Amazon's operating system, typing these tweaks in will redirect you to the top page in which prevents being able to scroll down to an empty line if you do end up using the Amazon Fire TV remote/controller. It's important to not accidently make the Amazon Keyboard pop up. A sidenote too, using the Fire TV remote app while copying and pasting will not work therefore will lead to the code you pasted to show up as /. Go to the Amazon Appstore and install Total Commander, you need to hover over to file system root, Grant su permissions, go to system, then long press the build.prop file and press edit file, (use Total Commander's editor). Reboot after applying these tweaks!!! With your keyboard press and hold the arrow down to scroll to the last line and hit enter, then add the build.prop tweaks listed below:
Build.prop Tweaks:
Better Scrolling
windowsmgr.max_events_per_sec=150
ro.min_pointer_dur=8
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.scrollingcache=3
debug.sf.hw=1
Modify Logcat:
logcat.live=disable
Quicker Boot Up:
ro.config.hw_quickpoweron=true
Disable Boot Animation (Optional)
debug.sf.nobootanimation=1
Modify Error Profiler:
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
Disable Strict Mode Checking:
persist.android.strictmode=0
Improve Touch Responsiveness and Hardware Rendering:
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
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-rtsp=true
media.stagefright.enable-record=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
Better Signal Strength (Helps when internet has poor latency):
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
Disable Sending Usage of Data:
ro.config.nocheckin=1
Improved Net Buffersize:
net.tcp.buffersize.default=4096,87380,256960, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,40984,256960
net.tcp.buffersize.hsdpa=6144,87380,1048576, 7380,1048576
net.tcp.buffersize.hspa=6144,87380,524288,6184,262144
net.tcp.buffersize.umts=4096,87380,256960,4084,256960
net.tcp.buffersize.edge=4096,87380,256960,4084,256960
net.tcp.buffersize.gprs=4096,87380,256960,4084,256960
net.tcp.buffersize.evdo_b=6144,87380,104857,87880,1048576
IPv6 and IPv4 Tweaks (You can disable IPv6 if optional)
IPv4
net.ipv4.tcp_ecn=0
net.ipv4.route.flush=1
net.ipv4.tcp_rfc1337=1
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.tcp_sack=1
net.ipv4.tcp_fack=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_timestamps=0
net.ipv4.tcp_rmem='6144 87380 1048576'
net.ipv4.tcp_wmem='6144 87380 1048576'
net.ipv4.tcp_mem='187000 187000 187000'
net.ipv4.tcp_no_metrics_save=1
net.ipv4.icmp_echo_ignore_all=1
net.ipv4.tcp_moderate_rcvbuf=1
net.ipv4.conf.all.accept_redirects=0
net.ipv4.conf.default.accept_redirects=0
net.ipv4.conf.all.rp_filter=1
#net.ipv4.conf.<device>.rp_filter=1
net.ipv4.conf.default.rp_filter=1
net.ipv4.conf.all.send_redirects=0
net.ipv4.conf.default.send_redirects=0
net.ipv4.conf.all.secure_redirects=0
net.ipv4.conf.default.secure_redirects=0
net.ipv4.conf.all.accept_source_route=0
net.ipv4.conf.default.accept_source_route=0
net.ipv4.udp_rmem_min=6144
net.ipv4.udp_wmem_min=6144
net.ipv4.tcp_tw_recycle=1
net.ipv4.tcp_tw_reuse=1
net.ipv4.tcp_syncookies=1
net.ipv4.tcp_synack_retries=2
net.ipv4.tcp_syn_retries=2
net.ipv4.tcp_max_syn_backlog=1024
net.ipv4.tcp_max_tw_buckets=16384
net.ipv4.icmp_echo_ignore_broadcasts=1
net.ipv4.icmp_ignore_bogus_error_responses=1
net.ipv4.tcp_fin_timeout=15
net.ipv4.tcp_keepalive_intvl=30
net.ipv4.tcp_keepalive_probes=5
net.ipv4.tcp_keepalive_time=1800
net.ipv4.ip_forward=0
#
#net.tcp.default_init_rwnd=60
#
# IPv6
#net.ipv6.conf.all.accept_redirects=0
#net.ipv6.conf.default.accept_redirects=0
#net.ipv6.conf.all.use_tempaddr=2
#net.ipv6.conf.default.use_tempaddr=2
# Disable IPv6
net.ipv6.conf.all.disable_ipv6=1 #echo "0" > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
net.ipv6.conf.default.disable_ipv6=1
#net.ipv6.conf.$WIFI.disable_ipv6=1
These are all the tweaks I have added on my Fire TV Stick 4K/Lite/3rd Gen. So far it's been successful for me with performance improvements and apps that are horrible with scrolling. Let me know what you guys think! If you want even more performance out of your device on top of these tweaks to add in the build.prop, download and install Kernel Adiutor and set the CPU Governor to Performance. You'll now see it say 1690! Apply on Boot! Then reboot!
Surprisingly enough the Fire TV Stick Lite/3rd Generation Sticks have the same cpu frequencies as the Fire TV Stick 4K with .5 less of ram. You'll notice how fast your device gets with these tweaks enabled.
Thanks it works. Can i use this on a gen2 rooted stick?
navin23 said:
Thanks it works. Can i use this on a gen2 rooted stick?
Click to expand...
Click to collapse
Yes you can!
Skel40 said:
These are all the tweaks I have added on my Fire TV Stick 4K. So far it's been successful for me with performance improvements and apps that are horrible with scrolling. Let me know what you guys think! If you want even more performance out of your device on top of these tweaks to add in the build.prop, download and install Kernel Adiutor and set the CPU to Performance. You'll now see it say 1690! Apply on Boot! Then reboot!
Click to expand...
Click to collapse
Thanks for the tweaks.
I just copied the build.prop to my PC, made the tweaks and the copied back, checked the permissions and rebooted, took all of 15secs!
It does seem to be snappier now...
btw where do you set "performance" in KA? I set the min & max Freq to 1690 and applied on boot toggle. Not sure if it's persisting though...
tinybilbo said:
Thanks for the tweaks.
I just copied the build.prop to my PC, made the tweaks and the copied back, checked the permissions and rebooted, took all of 15secs!
It does seem to be snappier now...
btw where do you set "performance" in KA? I set the min & max Freq to 1690 and applied on boot toggle. Not sure if it's persisting though...
Click to expand...
Click to collapse
Go to CPU, CPU Governor and set that to performance and reboot. By default its set to interactive in which randomly sets the frequencies. So its best to set it as performance since it automatically changes to the maximum CPU frequency and stays put.
Just to make sure i am clear, I copied the build.prop from the system folder. Transferred to a computer, added this to the bottom of the file (using notepad ++).
windowsmgr.max_events_per_sec=150
ro.min_pointer_dur=8
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.scrollingcache=3
debug.sf.hw=1
logcat.live=disable
ro.config.hw_quickpoweron=true
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
persist.android.strictmode=0
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
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
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
ro.config.nocheckin=1
Then saved, copied back the to firestick4k overwriting existing build.prop- I used a mouse for solid explorer.
Skel40 said:
Go to CPU, CPU Governor and set that to performance and reboot. By default its set to interactive in which randomly sets the frequencies. So its best to set it as performance since it automatically changes to the maximum CPU frequency and stays put.
Click to expand...
Click to collapse
Thanks for that... I had forgotten about changing Governors!
Michajin said:
Just to make sure i am clear, I copied the build.prop from the system folder. Transferred to a computer, added this to the bottom of the file (using notepad ++).
windowsmgr.max_events_per_sec=150
ro.min_pointer_dur=8
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.scrollingcache=3
debug.sf.hw=1
logcat.live=disable
ro.config.hw_quickpoweron=true
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
persist.android.strictmode=0
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
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
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
ro.config.nocheckin=1
Then saved, copied back the to firestick4k overwriting existing build.prop- I used a mouse for solid explorer.
Click to expand...
Click to collapse
Yes... pretty much what I did...
What is the risk of using these on a firestick2 tank? (i great results with mantis, so i figure why not)
Michajin said:
What is the risk of using these on a firestick2 tank? (i great results with mantis, so i figure why not)
Click to expand...
Click to collapse
Extremely low. It's safe to add.
Skel40 said:
Extremely low. It's safe to add.
Click to expand...
Click to collapse
Very nice... Done.
Seems much better considering the tank is about as fast as a tank... Did the kernel performance also!
Seems much better considering the tank is about as fast as a tank... Did the kernel performance also![/QUOTE said:
Yes! Due to the tank being 1.3 GB of ram, it's not 1690, I forgot the max value but it still works regardless
Click to expand...
Click to collapse
@Skel40 why not using a Magisk module which will setprop systemless, instead of messing with system files?
Imho that way it's easier to test and also recover if something goes wrong, or simply if someone wants to go back to stock.
Edit: Added a Magisk module for testing.You can install it from Magisk Manager or with TWRP.
Pretoriano80 said:
@Skel40 why not using a Magisk module which will setprop systemless, instead of messing with system files?
Imho that way it's easier to test and also recover if something goes wrong, or simply if someone wants to go back to stock.
Edit: Added a Magisk module for testing.You can install it from Magisk Manager or with TWRP.
Click to expand...
Click to collapse
Yes! Perfect!!! What editor am I supposed to use for additional tweaks? I might as well update the guide for people to test out these tweaks themselves systemlessly. I wasn't familiar with systemless build.prop tweaks on Magisk before. Thank you!
does anyone know if it works on Fire Tv 2nd (sloane)? thank you
does anyone know if it works on Fire Tv 2nd (sloane)? thank you
Skel40 said:
Before I start this tweaking guide for the Fire TV Stick 4K, I'm not responsible for what you do to your device. Please follow this guide carefully to prevent confusion. First of all, you need to be rooted and unlocked to add these tweaks to your Fire TV Stick 4K. You also need a USB keyboard or a Bluetooth keyboard to successfully type in these tweaks yourself in the file, build.prop. Due to Amazon's operating system, typing these tweaks in will redirect you to the top page in which prevents being able to scroll down to an empty line if you do end up using the Amazon Fire TV remote/controller. It's important to not accidently make the Amazon Keyboard pop up. A sidenote too, using the Fire TV remote app while copying and pasting will not work therefore will lead to the code you pasted to show up as /. Go to the Amazon Appstore and install Total Commander, you need to hover over to file system root, Grant su permissions, go to system, then long press the build.prop file and press edit file, (use Total Commander's editor). Reboot after applying these tweaks!!! With your keyboard press and hold the arrow down to scroll to the last line and hit enter, then add the build.prop tweaks listed below:
Build.prop Tweaks:
Better Scrolling
windowsmgr.max_events_per_sec=150
ro.min_pointer_dur=8
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.scrollingcache=3
debug.sf.hw=1
Modify Logcat:
logcat.live=disable
Quicker Boot Up:
ro.config.hw_quickpoweron=true
Disable Boot Animation (Optional)
debug.sf.nobootanimation=1
Modify Error Profiler:
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.kernel.checkjni=0
ro.kernel.android.checkjni=0
Disable Strict Mode Checking:
persist.android.strictmode=0
Improve Touch Responsiveness and Hardware Rendering:
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
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-rtsp=true
media.stagefright.enable-record=true
Better Signal Strength (Helps when internet has poor latency):
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
Disable Sending Usage of Data:
ro.config.nocheckin=1
These are all the tweaks I have added on my Fire TV Stick 4K. So far it's been successful for me with performance improvements and apps that are horrible with scrolling. Let me know what you guys think! If you want even more performance out of your device on top of these tweaks to add in the build.prop, download and install Kernel Adiutor and set the CPU Governor to Performance. You'll now see it say 1690! Apply on Boot! Then reboot!
Click to expand...
Click to collapse
richardes said:
does anyone know if it works on Fire Tv 2nd (sloane)? thank you
Click to expand...
Click to collapse
Yes it does
Hi Skel40,
Is this mod already in your debloated ROM? (Fire TV Stick 4K (mantis) Debloated Rom [V.1_6.2.7.3])
tinybilbo said:
Thanks for the tweaks.
I just copied the build.prop to my PC, made the tweaks and the copied back, checked the permissions and rebooted, took all of 15secs!
It does seem to be snappier now...
btw where do you set "performance" in KA? I set the min & max Freq to 1690 and applied on boot toggle. Not sure if it's persisting though...
Click to expand...
Click to collapse
Using a ftp?
Sloane FireTV 2
Skel40 said:
These are all the tweaks I have added on my Fire TV Stick 4K. So far it's been successful for me with performance improvements and apps that are horrible with scrolling. Let me know what you guys think! If you want even more performance out of your device on top of these tweaks to add in the build.prop, download and install Kernel Adiutor and set the CPU Governor to Performance. You'll now see it say 1690! Apply on Boot! Then reboot!
Click to expand...
Click to collapse
Hey @Skel40 I see you've added some ipv4/6 additions to your file. Looking good.
Just wondering willl this work on Sloane?
I'm also looking to see if I can maybe get the normal android boot animation like you have on your Debloated 6.2.7.3 rom if that's okay.
Ive played around with build.prop for a while now and my last escapade was an alcatel pixie 3 4g which I managed to root with magisk via SPFT mediatek EMMC flash.
Believe it or not the little phone is actually snappier on stock, Debloated 5.1 lol, just goes to show how universal these tweaks are.
Anyway all good mate if you could help with the boot animation that would be great.
###EDIT ### working surprisingly well on Sloane FTV2
Bertonumber1 said:
Hey @Skel40 I see you've added some ipv4/6 additions to your file. Looking good.
Just wondering willl this work on Sloane?
I'm also looking to see if I can maybe get the normal android boot animation like you have on your Debloated 6.2.7.3 rom if that's okay.
Ive played around with build.prop for a while now and my last escapade was an alcatel pixie 3 4g which I managed to root with magisk via SPFT mediatek EMMC flash.
Believe it or not the little phone is actually snappier on stock, Debloated 5.1 lol, just goes to show how universal these tweaks are.
Anyway all good mate if you could help with the boot animation that would be great.
###EDIT ### working surprisingly well on Sloane FTV2
Click to expand...
Click to collapse
Remove the no boot animation line on the first page to restore the boot animation
Edit: That's great! These tweaks work for any android device with root permissions
Skel40 said:
Remove the no boot animation line on the first page to restore the boot animation
Edit: That's great! These tweaks work for any android device with root permissions
Click to expand...
Click to collapse
No m8 the "android" boot animation, the one you have on your rom instead of amazon logo, will it work on. Sloane? If so can you send me it, I have a "freedom firetv" with minions just now but I like your plain black screen android one at boot.

Categories

Resources