a list of build.prop tweaks

Search This thread

Jose Hidalgo

Member
Jun 15, 2012
21
0
Lyon
I must say I'm very surprised that ES File Explorer causes bootloop while Jota Text Editor does not.

Can you confirm that ES File Explorer still causes problems, even in its latest version ? That would be quite surprising !!! :eek:

Moreover, I have tried editing build.prop with Jota. It doesn't want to save the modified file...
 

Jose Hidalgo

Member
Jun 15, 2012
21
0
Lyon
Please forgive me, but again, I'm surprised. I'm no expert, but I don't understand how a text editor simply "can" cause boot loops, sometimes yes and sometimes not.

In this topic, I read a clear explanation : ES Explorer's carriage returns would not be "unix compatible". OK.
But if that's true, then there should be a problem always, not only from time to time.
And most of all, I can't imagine a second that the developers of a widely used app, made especially for Android, would skip an error as huge as the compatibility of their carriage returns !
So if that error has existed, I can't imagine that it wouldn't have been corrected in the next version of the app, months ago.

I'm not trying to prove you wrong, and I don't mean to offend anyone. I'm just trying to understand from a cartesian point of view, that's all. Can somebody help me understand this ? Thank you. :)
 
Last edited:

dheeraj (dhlalit11)

Senior Member
Sep 30, 2011
2,540
1,510
fatehabad (hry)
previously I had bootloops while editing with es file explorer

then I was working on a flashable zip edited the updater-script with es-file explorer and while flashing got an error after Googling got that updater-script's line break code is wrong so edited it with jota and changed line break code with it and and then it was a successful flash

I am not talking technically, its my experience

maybe the reason could be something else, I just wanted to inform everyone

you should ask the estrongs for brief details
 

vasu1

Senior Member
May 21, 2012
291
12
hello sir,,
if i edit the buid.prop file before installing the rom ,,, by opening the file and edit it through notepad and pasting any of these commands in the file and then installing the rom will it work???
 

chemicalrage

Senior Member
Oct 17, 2011
1,217
759
hello sir,,
if i edit the buid.prop file before installing the rom ,,, by opening the file and edit it through notepad and pasting any of these commands in the file and then installing the rom will it work???

Yes, it will work & that is how people create winzip Custom ROM(s). I recommend you download http://notepad-plus-plus.org/download/v6.2.3.html and open build.prop in that and edit.
 
Last edited:
  • Like
Reactions: vasu1

vasu1

Senior Member
May 21, 2012
291
12
Yes, it will work & that is how people create winzip Custom ROM(s). I recommend you download http://notepad-plus-plus.org/download/v6.2.3.html and open build.prop in that and edit.

one more ques can i place it anywhere in the file??? just copy and paste in the file,... or at a paricular place in the file,,,??
cats.jpg
 

Attachments

  • cats.jpg
    cats.jpg
    131.8 KB · Views: 188

jeremypt

Member
Dec 29, 2012
39
2
Do I really need to do this first?

"before editing write these commands in terminal:
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=v
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot"


Cant I just edit the file on my computer using Notepad++ and replace it?

BR
 

jeremypt

Member
Dec 29, 2012
39
2
SO, I do that, copy the file to my computer and edit it with the notepad++. Then I replace the file and reboot the phone?


When i put this ones "rm /data/dalvik-cache/*" and "rm /cache/dalvik-cache/*" I get this message "rm failed for /data/dalvik-cache/", permission denied. Also I cant reboot it with the command. (tried with abd and with terminal)
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 87
    Build.prop is a file which is used to define the device's properties it is found in /system. devices cannot boot if the build.prop file is not in state proper, so better edit the file wisely.

    before editing write these commands in terminal

    setprop dalvik.vm.verify-bytecode false
    setprop dalvik.vm.dexopt-flags v=n,o=v
    rm /data/dalvik-cache/*
    rm /cache/dalvik-cache/*
    reboot


    BUILD.PROP TWEAKS:-

    persist.sys.purgeable_assets=1

    reboot will be very fast

    ro.media.enc.hprof.vid.bps=8000000

    increasing the video recording quality

    ro.media.dec.jpeg.memcap=8000000

    also for jpeg pics

    ro.media.enc.jpeg.quality=100

    increase the quality of JPEG pics

    windowsmgr.support_rotation_270=true;

    can make the screen rotate to 270 degree

    dalvik.vm.heapsize=64m

    increase vm heap size to 64mb may resolve some fc's

    windowsmgr.max_events_per_sec=150

    increasing it will make mobile smoother but if you are conservative decrease it

    wifi.supplicant_scan_interval=180

    increase the time of scan interval of your wifi

    debug.sf.hw=1

    Render ui with gpu

    video.accelerate.hw=1

    Video acceleration enabled

    debug.performance.tuning=1

    performance will increase

    ro.config.nocheckin=1

    Disable sending usage data (probably isn't functional, but can't hurt)

    ro.ril.disable.power.collapse=1
    pm.sleep_mode=1


    Deeper sleep/better battery life

    ro.telephony.call_ring.delay=0

    ringing will start immediately

    ro.kernel.android.checkjni=0

    disable error checking

    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


    wireless speed will increase

    media.stagefright.enable-meta=true

    media.stagefright.enable-scan=true

    media.stagefright.enable-http=true

    media.stagefright.enable-record=false


    video streaming will be better

    debug.sf.nobootanimation=1

    no bootanimation will show up while booting, will decrease booting time

    ro.HOME_APP_ADJ=1
    force to remain launcher in memory

    persist.adb.notify=0

    will disable usb debugging popup in notification

    ro.config.hwfeature_wakeupkey=0

    disable waking up of phone by volume buttons, changing value to 1 will enable the wakeup

    ro.lge.proximity.delay=25
    mot.proximity.delay=25


    off the proximity quiclky after call
    no need to wait for screen to come


    ro.sf.lcd_density=160

    will let you feel tablet like screen



    If you change build.prop and got boot loop then flash below package in recovery

    *Squadzone rom package:- http://db.tt/fPItBvjW

    if you want to echo something in build.prop, do it like the example below

    Code:
    echo key=value >> /system/build.prop

    remember two arrows '>>' are required else it will remove all previous lines and will only add that line
    9
    it is always great to press thanks button
    6
    windowsmgr.support_rotation_270=true; (15-april-2012)

    ro.media.enc.jpeg.quality=100 (15-april-2012)

    ro.media.dec.jpeg.memcap=8000000 (15-april-2012)

    ro.media.enc.hprof.vid.bps=8000000 (15-april-2012)
    4
    reserved if meteor falls on first post
    3
    NOTE:- Do not use es file explorer's text editor to edit build.prop device will bootloop, instead use jota text editor

    before editing write thesecommands in terminal

    setprop dalvik.vm.verify-bytecode false
    setprop dalvik.vm.dexopt-flags v=n,o=v
    rm /data/dalvik-cache/*
    rm /cache/dalvik-cache/*
    reboot


    BUILD.PROP TWEAKS:-

    thank you very much ...
    If there is a GUI to beginner users it will be awesome ..
    again thanx a lot .
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone