Database Users

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 !

Need some HELP with a few build.prop tweaks !

Heya guys if someone could just try these build.prop tweaks or tell me whether these actually work on SGY i'd be gratefull ! i tried but can't be sure so if anyone espeacially on stock can help then it is appreciated ! thanks in advance
# Render UI with GPU
debug.sf.hw=1
persist.sys.composition.type=gpu
#Lock Launcher in memory
ro.HOME_APP_ADJ=1
# Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=250
#Save Some battery
pm.sleep_mode=1
# Improve overall media quality
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Tweaks for battery saving
pm.sleep_mode=1
wifi.supplicant_scan_interval=120
# Turn on Just In Time in dalvik virtual machine
dalvik.vm.execution-mode=int:jit
Click to expand...
Click to collapse

Bump

then...why don't you test it by yourself (lol)

kurotsugi said:
then...why don't you test it by yourself (lol)
Click to expand...
Click to collapse
Like i said in the above post i tried but didn't see any difference so i need to know whether these are valid or not !

type getprop and you'll see your tweak there.

thanks kuro! that was all I needed!

nope...that command only use to check whether your script is executed or not. it doesnt tell you whether if the new prop really working or not.
EDIT:
if you want a proof, in terminal type
Code:
su
setprop kucing.meong.lucu 1
getprop
you'll find kucing.meong.lucu in your prop list.

kurotsugi said:
nope...that command only use to check whether your script is executed or not. it doesnt tell you whether if the new prop really working or not.
EDIT:
if you want a proof, in terminal type
Code:
su
setprop kucing.meong.lucu 1
getprop
you'll find kucing.meong.lucu in your prop list.
Click to expand...
Click to collapse
Okay got it!
My scripts are getting executed btw is there a way to know whether they are working?

unless if you know all the prop stuff inside android system, you'll never know which one is really working or not. some of rom have additional hidden prop. some of prop mod will work on all rom but some of them only work in certain rom. in your tweak,
Code:
# Render UI with GPU
debug.sf.hw=1
persist.sys.composition.type=gpu
# this one will mostly working. however, the differences isn't significant.
#Lock Launcher in memory
ro.HOME_APP_ADJ=1
# seems doesn't work in ICS
# Increase overall touch responsiveness
debug.performance.tuning=1 #work
video.accelerate.hw=1 #work
windowsmgr.max_events_per_sec=250 # the max value is 90. when you set higher than 90 you'll get nothing.
#Save Some battery
pm.sleep_mode=1 #work
# Improve overall media quality
ro.media.enc.jpeg.quality=100 #work
ro.media.dec.jpeg.memcap=8000000 # I highly doubt this one.
ro.media.enc.hprof.vid.bps=8000000 #work
# Tweaks for battery saving
pm.sleep_mode=1
wifi.supplicant_scan_interval=120 #work. be carefull with the value
# Turn on Just In Time in dalvik virtual machine
dalvik.vm.execution-mode=int:jit #the devault set is jit. no need to set it again.
# the other famous stuff,
dalvik.vm.heapsize=128m #if you set it higher than 64 it doesn't affect your system. 48 is enough. it doesn't matter since it doesn't improve your devices performance at all

Okay thanks kuro learned a lot from you!

[Guide]Build.prop Wiki

Alright great S2 users!
I´m Chris from Omega Team and today I present to you my little tutorial about build.prop file. Couldn't find something similar in here, so I decided to start this thread. I already got a thread about it in Galaxy S3 section and decided to port it also to Galaxy S2 forum.
So before I start just one thing. It took me many hours to get all the information and as you can see there are still some points missing. So if you got some information about them, please pm me and for sure I put you on the credit list! If you try to mod the build.prop, please back it up first and make a nandroid backup in case something went wrong. Also don´t do anything unless you have a clue about it! Please hit thanks if you think the information in here are useful! And I´m glade for any feedback and suggestion from you guys! I´m not responsible for any damage you phone get when you messing around with this values!
Credits:
To Vegeta1, for give me a first start and his great support!
To Omega Rom Team, for their great support and being like a second family!
1. You will find the build.prop file in root path/System. You can open it with a build.prop editor from Play store or open it for example with the build in text editor in an app like root explorer.
2. For what you need a build.prop? Here´s a good explanation from 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.
3. Let´s get started
# begin build properties
# autogenerated by buildinfo.sh
Version Number of 4.1.2
ro.build.id=JZO54K
Current Rom version on Phone: by editing this value, you will change what are standing in Settings/About Phone/Buildnumber. For Example you can change it to Omega by Indie or what ever you like.
ro.build.display.id=Omega v16.2 - XXLSJ
Your current Modem version
ro.build.version.incremental=I9100XXLSJ
Current sdk version of Framework plus Codename
ro.build.version.sdk=16
ro.build.version.codename=REL
Android Version on Phone
ro.build.version.release=4.1.2
Current Kernel version
ro.build.date=Tue Nov 6 02:17:01 KST 2012
ro.build.date.utc=1352135821
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-111
This means its a official release
ro.build.tags=release-keys
Model Number plus Manufacturer
ro.product.model=GT-I9100
ro.product.brand=samsung
Name
ro.product.name=GT-I9100
Device
ro.product.device=GT-I9100
The phone’s board is listed as “smdk4210,” which means it will most likely use Exynos 4210, supporting a maximum clock speed of 1.2GHz.
ro.product.board=smdk4210
System Images
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
Nothing to say
ro.product.manufacturer=samsung
Current default Country settings. If you change that line for example to ro.product.locale.language=de and ro.product.locale.region=De, the phone will set to German after a factory reset
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 14 channels you can paste the same number in here.
ro.wifi.channels=
Nothing interest on the next few points. Most are explained above.
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9100
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100-user 4.1.2 JZO54K I9100XXLSJ release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:4.1.2/JZO54K/I9100XXLSJ:user/release-keys
ro.build.characteristics=default
# Samsung Specific Properties
ro.build.PDA=I9100XXLSJ
ro.build.hidden_ver=I9100XXLSJ
ro.build.changelist=462349
# end build properties
#
# system.prop for smdk4210
#
Ril Specific: Here some from aosp to that: RIL daemon reads rild.lib path and rild.libargs system properties to determine the Vendor RIL library to use and any initialization arguments to provide to the Vendor RIL
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
Here you can set the Pixel per inch. The smaller you set it the smaller apps, icons and fonts will be. But be careful if you set it to low apps can crash! Also you can´t set it higher than the default value!
ro.sf.lcd_density=240
Minimum brightness of your screen
ro.lcd_min_brightness=40
This point is about rooting. It´s setting if the device running on the emulator or running in secure mode
ro.kernel.qemu=0
This point speak for itself
ro.tvout.enable=true
Maybe someone can light me up on that point.
persist.sys.storage_preload=1
Same here
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# Multimedia property for Smart View
media.enable-commonsource=true
# System property for Default Brightness
I think this point also need no explanation
ro.lcd_brightness=160
#
# ADDITIONAL_BUILD_PROPERTIES
#
Support for OpenGl 2.0
ro.opengles.version=131072
System property used to enable or disable dirty regions invalidation.
debug.hwui.render_dirty_regions=false
System property defining default error report receiver
ro.error.receiver.default=com.samsung.receiver.error
This controls the smallest amount of memory given to a single application.
dalvik.vm.heapstartsize=5m
The dalvik.vm.heapgrowthlimit property limits how large an Android application’s heap can get.
dalvik.vm.heapgrowthlimit=48m
The dalvik.vm.heapsize property defines an absolute maximum for the heap size for an application.
dalvik.vm.heapsize=128m
Same as above, setting the pixel per inch
ro.sf.lcd_density=240
No clue about the next point. Help is appreciated.
ro.sec.fle.encryption=true
Here you can set the standard media sounds for each notification. But they got to match with the one in system/media/audio/...
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=A_toy_watch.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
That means your phone is still usable, even you got no Sim card in it.
keyguard.no_require_sim=true
Format of date
ro.com.android.dateformat=MM-dd-yyyy
Setting this value from unknown to wifi-only can fix some stand by issues.
ro.carrier=unknown
Needed for Play store. Some guys modded it to pay with her Phone bill, but i don't know if that still works.
ro.com.google.clientidbase=android-samsung
Defines weither to use UMTS (0), HSPDA/UMTS(1), or HSDPA/HSPUA(2) respectively.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=1
Defines what class speeds to use with EDGE. Setting this value to 12 can improve the data speed significant on lower connections.
ro.ril.gprsclass=10
Value for adb. Is a pipe connection in the adb client.
ro.adb.qemud=1
No clue. Maybe someone can light me up.
ro.com.google.apphider=off
Google Mobile Service Version with build number
ro.com.google.gmsversion=4.1_r3
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, u=n means do not optimize for unprocessor and m=y means register maps yes
dalvik.vm.dexopt-flags=m=y
Bluetooth name of the device
net.bt.name=Android
The dalvik.vm.stack-trace-file property allows you to specify the name of the file where the thread stack traces will be written.
dalvik.vm.stack-trace-file=/data/anr/traces.txt
This point stands for "Debug SurfaceFlinger Hardware" or GPU hardware acceleration
debug.sf.hw=1
Video Acceleration
video.accelerate.hw=1
Increase the touch responsive of the screen
debug.performance.tuning=1
Disable sending usage data
ro.config.nocheckin=1
Increase the quality of JPEG pics
ro.media.enc.jpeg.quality=100
increasing the recording quality of Pics and videos
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Here you can set the delay of time your phone starts to ring when you recieve a call. 0=disabled
ro.telephony.call_ring.delay=0
This point set the delay after a call. This fix Black screen issues.
ro.lge.proximity.delay=15
mot.proximity.delay=15
Next two points should safe some battery if they are enabled but the problem is that they are not in source code elsewhere and should have no effect. This means that adding this value to your build.prop will have no effect at all. This parameter is a kernel parameter and will only work when passed directly to the kernel on boot.
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
Already explained
ro.config.nocheckin=1
For the last two points. These commands enable or disable the error profiler in the android. For most android users, there is no use in having error profiling . however , some applications might make use of this for generating error reports.
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1

Is it possible to have conditional statements in build.prop?
Is it possible to have conditional statements in build.prop?
For example:
if P1 == 0
ro.xxx.yyy=value1
else
ro.xxx.yyy=value2
endif
where P1 is either a parameter or a predefined setting.
Thanks

Ian5723 said:
Is it possible to have conditional statements in build.prop?
For example:
if P1 == 0
ro.xxx.yyy=value1
else
ro.xxx.yyy=value2
endif
where P1 is either a parameter or a predefined setting.
Thanks
Click to expand...
Click to collapse
I think you mean like a script. Imo that's not possible.
Sent from my GT-I9300 using XDA Premium 4 mobile app

Pure awesomeness thank very much

Nice thread ! Now I understant what's in the Build.prop . I will take a look to my Build.prop tonight !
Thanks man !

maxflay said:
Nice thread ! Now I understant what's in the Build.prop . I will take a look to my Build.prop tonight !
Thanks man !
Click to expand...
Click to collapse
Glade you like it. And thanks for the feedback!
Sent from my GT-I9300 using XDA Premium 4 mobile app

SystemUpdateServices
I need to stop Android System Update downloads from happening after I restart the phone.
I am using DisableService app to uncheck (OFF) SystemUpdateServices (under Google Services Framework). After I restart the phone the SystemUpdateServices is check (ON) again. Does anyone know which properties controls the SystemUpdateServices?
Thank you.

Help help help !!!!!
I have mistakely deleted my build.prop of samsung galaxy s2.... I beg you please send me its file of build.prop in my gmail please mail me .......:crying::crying::crying:....

Increase the touch responsive of the screen debug.performance.tuning=1
Can I increase this number?

[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