I'm used to only having one build.prop file to edit; on the SHT-AL09 there are three build.prop files - there's a system/build.prop, a vendor/build.prop, system/vendor/build.prop. The system/build.prop file is different/smaller than the other two files, one of which I presume is a vendor supplied backup.
Please excuse me if this is a stupid question - but which file(s) need to be edited to successfully implement build.prop tweaks?
Also, build.prop permissions are traditionally set to 644. However, out of the box, our build.prop permissions appear to be set to 600.
This thread can also serve as a place to share build.prop tweaks that are confirmed to not result in bootloops. Personally, I am looking forward to increasing sling velocity.
I guess build.prop tweaks are a thing of the past?
I figured out that the system/vendor/ folder is the same as the root/vendor/ folder; change a file in one and it is changed in the other as well. I have also confirmed that editing either the build.prop or default.prop files in the vendor folder affects system config. In the default.prop folder I changed the value for 'qemu.hw.mainkeys,' and afterward Nova Launcher was suddenly unable to turn the color of the text in my status bar to a dark color.
I don't plan on playing around much until we have a working recovery, but so far I have edited the following existing lines in my build.prop file:
dalvik.vm.heapsize=700m
dalvik.vm.heapstartsize=35m
dalvik.vm.heapgrowthlimit=140m
dalvik.vm.heaptargetutilization=0.72
dalvik.vm.heapmaxfree=15m
And have added the following lines:
net.tethering.noprovisioning=true
ro.config.nocheckin=1
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
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hspda=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
windowsmgr.max_events_per_sec=90
I couldn't say for sure that I have seen an improvement, but I think I've seen some improvement in overall stability/multi-tasking. At least, there have been no ill effects. I am also getting better data speeds in certain parts of town via T-Mo - but that could be random or related to experimentation with my APN.
Also...VOLTE is enabled by default in the stock build.prop - unfortunately it is a known issue that Huawei phones don't get VOLTE on T-Mo (in the US) unless they have US firmware.
thref23 said:
I guess build.prop tweaks are a thing of the past?
I figured out that the system/vendor/ folder is the same as the root/vendor/ folder; change a file in one and it is changed in the other as well. I have also confirmed that editing either the build.prop or default.prop files in the vendor folder affects system config. In the default.prop folder I changed the value for 'qemu.hw.mainkeys,' and afterward Nova Launcher was suddenly unable to turn the color of the text in my status bar to a dark color.
I don't plan on playing around much until we have a working recovery, but so far I have edited the following existing lines in my build.prop file:
dalvik.vm.heapsize=700m
dalvik.vm.heapstartsize=35m
dalvik.vm.heapgrowthlimit=140m
dalvik.vm.heaptargetutilization=0.72
dalvik.vm.heapmaxfree=15m
And have added the following lines:
net.tethering.noprovisioning=true
ro.config.nocheckin=1
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
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hspda=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
windowsmgr.max_events_per_sec=90
I couldn't say for sure that I have seen an improvement, but I think I've seen some improvement in overall stability/multi-tasking. At least, there have been no ill effects. I am also getting better data speeds in certain parts of town via T-Mo - but that could be random or related to experimentation with my APN.
Also...VOLTE is enabled by default in the stock build.prop - unfortunately it is a known issue that Huawei phones don't get VOLTE on T-Mo (in the US) unless they have US firmware.
Click to expand...
Click to collapse
You mean you added and edited these lines in the vendor build.prop right?
The I can't mod the system build.prop, after every restate it restores the old one. What can I do about it?
Marcopoloy13 said:
You mean you added and edited these lines in the vendor build.prop right?
The I can't mod the system build.prop, after every restate it restores the old one. What can I do about it?
Click to expand...
Click to collapse
I think the system/build.prop is rewritten according to the vendor/build.prop at boot. I'm not sure. You don't have to do anything about it - just edit the vendor file instead of the system file.
Be careful with heapsize values. I pushed the dalvik.vm.heapsize to 900m, with .6 heaptargetutilization - and it bootlooped me. I had tested those values on my Sony Z3TC first and they worked...
Don't know exactly what difference it makes, but I am currently using:
dalvik.vm.heapsize=720m
dalvik.vm.heapstartsize=36m
dalvik.vm.heapgrowthlimit=144m
dalvik.vm.heaptargetutilization=0.67
thref23 said:
I think the system/build.prop is rewritten according to the vendor/build.prop at boot. I'm not sure. You don't have to do anything about it - just edit the vendor file instead of the system file.
Be careful with heapsize values. I pushed the dalvik.vm.heapsize to 900m, with .6 heaptargetutilization - and it bootlooped me. I had tested those values on my Sony Z3TC first and they worked...
Don't know exactly what difference it makes, but I am currently using:
dalvik.vm.heapsize=720m
dalvik.vm.heapstartsize=36m
dalvik.vm.heapgrowthlimit=144m
dalvik.vm.heaptargetutilization=0.67
Click to expand...
Click to collapse
I don't think that the vendor and system ones are the same or will be generated from it, there are not the same, things like dalvik.vm.heapgrowthlimit isn't in the system one just in vendor.
I have instead an GSI, so there are very different .
For Example on the system one it says the right security patch and release (8.1.0 - 2018-07-05) while on the vendor one it is still the values from the EMUI Rom (8.0 - 2018-06-01)
So there must be a way to mod the system build.prop, the MagiskHide Props Config Module runs a script on startup to modify the fingerprint, but I don't know how to modify more that this with this module or write my own script.
Related
I don't see the normal wifi scan interval setting in the build.prop file. Others have mentioned adding wifi.supplicant_scan_interval=90 to the file but no one has said it works. Anyone here found how to change the scan interval?
drewcam888 said:
I don't see the normal wifi scan interval setting in the build.prop file. Others have mentioned adding wifi.supplicant_scan_interval=90 to the file but no one has said it works. Anyone here found how to change the scan interval?
Click to expand...
Click to collapse
that is in gingerbread roms only....
Is this a samsung thing that they only put it in gingerbread roms. Because I have edited 2.1 and 2.2 android build.prop from other phone manufacturers for changing the interval
anyone know about my above question
drewcam888 said:
I don't see the normal wifi scan interval setting in the build.prop file. Others have mentioned adding wifi.supplicant_scan_interval=90 to the file but no one has said it works. Anyone here found how to change the scan interval?
Click to expand...
Click to collapse
It's not in the build.prop file on froyo. Use Blade Buddy (app) - in advanced settings; or to edit the text file directly in root explorer, navigate to data/local.prop (long press & edit text) - I set mine to 180.
{SDCharge Humb£e 1.25}
is that the location for gingerbread Roms?
drewcam888 said:
is that the location for gingerbread Roms?
Click to expand...
Click to collapse
Not sure, haven't used a GB rom for a samsung phone yet. But I think, according to an above post it might not... I came from a DX & moto had everything in the build.prop.
{SDCharge Humb£e 1.25}
pyroelite said:
It's not in the build.prop file on froyo. Use Blade Buddy (app) - in advanced settings; or to edit the text file directly in root explorer, navigate to data/local.prop (long press & edit text) - I set mine to 180.
{SDCharge Humb£e 1.25}
Click to expand...
Click to collapse
On my Charge, there is no data/local.prop
Inside the data folder, there is another folder named local, but nothing editable is inside.
I did a file search in Root Explorer for files named .prop
default.prop
/system/build.prop
/system/default.prop
were the only files that showed up.
Chris
Yeah, if you don't have it, it may have been created by blade buddy. Not sure if the file is functional or references another file... (I'm used to everything being in the build.prop file on moto) - guess I'll have to do some more searching.
{SDCharge Humb£e 1.25}
I have installed the ep1h leak. The scan interval is listed in the build.prop one more reason to leave froyo
You need root.
Backup first your oryginal build.prop file.
Tested on froyo v10d firmware.
You do this on your own risk!
You must add entire line and restart phone.
To make the phone ring faster when dialing out:
ro.telephony.call_ring.delay=0
Disable blackscreen issue after a call:
ro.lge.proximity.delay=25
mot.proximity.delay=25
Better scrolling speed:
windowsmgr.max_events_per_sec=160
To save battery by decreasing the amount of time Wifi looks for an access point:
wifi.supplicant_scan_interval=250
and save battery
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
Increase touch responsiveness
debug.performance.tuning=1
Change the Dalvik VM heap size:
Edit this value, the line exist in oryginal build.prop
dalvik.vm.heapsize=32m(standard value)
Enable the hard key lights when screen is on:
ro.mot.buttonlight.timeout=0
Disable boot animation:
debug.sf.nobootanimation=1
Render UI with GPU
debug.sf.hw=1
Keep launcher into memory:
ro.HOME_APP_ADJ=1
Thanks for this mod, y hope will help on some roms
Thanks
The most entrys are not in my build.prop?
Sent from my LG-P920 using xda premium
You must add entire lines to build.prop
to apply these changes should add to build.prop?
because many of these items are not present in the original build.prop!
boostermbkking said:
to apply these changes should add to build.prop?
because many of these items are not present in the original build.prop!
Click to expand...
Click to collapse
Yes, read the reply from the post above yours
http://forum.xda-developers.com/showthread.php?t=1210341
Thaks for the tweaks, but this tweak I do'nt work :
Enable the hard key lights when screen is on:
ro.mot.buttonlight.timeout=0
How to use this mod? Ok.I now how.
tiggerbcn said:
Thaks for the tweaks, but this tweak I do'nt work :
Enable the hard key lights when screen is on:
ro.mot.buttonlight.timeout=0
Click to expand...
Click to collapse
Try ro.mot.buttonlight.timeout=1
This tweak i found in droid x and maybe do not work.
vados77 said:
How to use this mod?
Click to expand...
Click to collapse
You must add lines to your build.prop file f.e You do this with root explorer.
adixtra said:
You must add entire lines to build.prop
Click to expand...
Click to collapse
How to do this?
1) Download any root file editor(ES File Explorer, Root explorer)
2) Navigate to /system/ and copy/paste build.prop to /sdcard/
3) Open & edit /system/build.prop
4) Change or add choosen lines
5) Save changes and restart phone
adixtra said:
mot.proximity.delay=25
ro.mot.buttonlight.timeout=0
Click to expand...
Click to collapse
These 2 strings won't work on our O3D "mot." says it's for motorola maybe replacing "mot" with "lge" will make them work.
BTW "mot" is shortcut from motorola...
Resolved the problem
Try wiping your device. Turn off phone then press and hold voll down and power. When u see lg logo release buttons and wipe data, cache.
Or try LGmobileSupportTool and emergency recovery
adixtra said:
Try ro.mot.buttonlight.timeout=1
This tweak i found in droid x and maybe do not work.
Click to expand...
Click to collapse
Does not work, or modified as follows:
ro.lge.buttonlight.timeout=1
Thanks
tiggerbcn said:
Does not work, or modified as follows:
ro.lge.buttonlight.timeout=1
Thanks
Click to expand...
Click to collapse
This is working for you??
dont work for me
Hi guys
I added all the lines except leaving the VM heaps at 32m.
I find lots of difference in performance and also battery life..
Thanks for the tweaks..
Yaa...I know. you can find a lot of tweak in this forum. I just want to share the tweak I've made for you. this tweak is an enhanced version this old tweak http://forum.xda-developers.com/showthread.php?t=1714217. that tweak is for GB. I'm not recommend you to install that stuff to your system. if you're using ICS device, especially Xperia one, you can use this tweak instead.
all the files could be downloaded here:
v_0.1 : http://www.mediafire.com/?c4ua4cwwd0e774j
v_0.2 : http://www.mediafire.com/download.php?9ua4lz8wafqq79w
v_0.2.1 : http://www.mediafire.com/download.php?2bqcgbkt01banl6
(this latest update only contain add blocker tweak. you need to copy the hosts file into /system/etc to install it.)
sorry, no flashablel zip file yet, since we don't have working cwm at this moment.
PRE-REQUIREMENTS
1. rooted device
2. init.d support system
3. busybox with symlink installed
if you don't have a rom with init.d support, you can made it by yourself. simply create file named "install-recovery.sh" in /etc. and put these stuff inside that file
Code:
#!/system/bin/sh
# init.d activation script
busybox run-parts /system/etc/init.d/
to test your init.d script you can made a simple script in init.d contain
Code:
#!/system/bin/sh
# test code
touch /data/tes_kucing.log
echo "kucing meong" > /data/tes_kucing.log
if it succes, you'll find tes_kucing.log in /data after you reboot your device.
WHAT INSIDE IT?
this tweak consist of several parts.
1. kuro1 tweak - system tweak
2. kuro2 tweak - prop tweak
3. kuro4 tweak - sound enhancement
4. local.prop tweak
5. zipalign tweak
all the details about the tweak is already inside the tweak files.
HOW TO INSTALL
simply copy all files into their respective folders and give them rwxrwxrwx permission. after that type these command in your terminal
Code:
su
rm /data/dalvik-cache/*
reboot
after boot, check /data and see if you could find all the log files. if you got any problem, you can report here and show me the log files.
CHANGELOG:
v_0.2.1 (2-1-12):
- add blocker.
- this is a little addition for v_0.2. you need to install v_0.2 then copy hosts file to /system/etc to use the complete tweak.
v_0.2 (9-12-12) :
- new optimized script
- auto root for blast tool. no need to type su. just type "blast" in your terminal and the script will run with root permission
v_0.1 :
- initial public release
Click to expand...
Click to collapse
TERM OF USE AND SHARING:
this thread intent is for sharing. feel free to use, edit, distribute all material inside this thread which came from me. if there any parts of this mod which comes not from me please refer to the original dev I've mentioned in this thread. if want to share it to another forum or modify it you don't have to ask my permission. no need to credits, put links or whatsoever. you'll only need to remember that you should held all the responsibility by using this mod, modify it or distribute it. DO IT WITH YOUR OWN RISK
Click to expand...
Click to collapse
SPECIAL FEATURE
this tweak pack has special feature to clear up your memory so that you'll have more space to run app or run heavy app like games. in your terminal type
Code:
su
blast
a script will run and your memory will freed up. all the information about the memory you can get in your screen.
EDIT: if you're using the new version you only need to type 'blast' in your terminal.
GPS tweak
this tweak will make your gps acquire your postition relatively faster. to install it simply replace your gps.conf with this one and reboot. http://www.mediafire.com/download.php?vdkrzx55qkzqn27
please note that this gps.conf file is optimized for indonesian region. I'll show you which part I modified from the original one so that you can optimize your gps according to your country.
Code:
# more ntp server
NTP_SERVER=id.pool.ntp.org
# the line above is the ntp server for indonesia. you can replace it with your region id. the form will be <country code>.pool.ntp.org
NTP_SERVER=asia.pool.ntp.org
NTP_SERVER=europe.pool.ntp.org
NTP_SERVER=africa.pool.ntp.org
NTP_SERVER=north-america.pool.ntp.org
NTP_SERVER=south-america.pool.ntp.org
NTP_SERVER=oceania.ntp.org]
I also modify this part
Code:
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=1
# that line above is to enable intermediate position report. less accurate but faster gps lock
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# orig 5000
ACCURACY_THRES=100
# this line define the accuracy threshold if you activate intermediate position. If I'm mistaken the value is written in meter. less number means more accurate position, longer gps lock. while higher number means faster gps lock but less accurate position. you can modify this value on your own.
can you make a flashable since we have recovery for a few days now? im gonna test if it works.
Until there's update for this stuff there won't be any flashable zip. I know, its not convenience to copy the files one by one but I need to make sure the filesgot copied into system. Last time I checked into cwm thread there's a report about problem when install a flashable zip.
smokerman said:
can you make a flashable since we have recovery for a few days now? im gonna test if it works.
Click to expand...
Click to collapse
If you want tweaks...
Just visit the super thread for tweaks
http://forum.xda-developers.com/showthread.php?t=1908269
You can get many tweaks in flashable zip... Even bravia engine and xloud
Sent via 'rooted' BEETEL landline
thread updated with a lil new optimized tweak
thread updated with gps tweak as I've promised. check post 3#
3. kuro4 tweak - sound enhancement
Click to expand...
Click to collapse
Does that affect headphones volume which is not the best on stock? I'm sure the headphones volume is limited on purpose and I'm looking to boost it up since none of the Google Play volume boosting apps work on ICS and above.
i'm afraid not. the sound enhancement tweak is used to enhance the sound clarity, not the headphone volume. if you want a louder volume on your headphone you can try using eq app like the one in my beat bass app thread. try the latest one.
thread updated with add blocker tweak.
Nice work........
thanks for the mod... working fine on J .75 firmware . Ah, can you tell me how to enable boot animation. __
Goto /data/local.prop delete debug.sf.nobootanimation or change the value to zero
Not working for my Xperia Miro, phone stuck at Battery status after reboot.
Also cant find my region code for GPS tweak I am from and in Bulgaria.
Thanks
battery status? are you using cm10? which version of it?
Could you make this for flash gordon?
Sent from my ST26i using xda app-developers app
pardon me? what do you mean with flash gordon?
kurotsugi said:
battery status? are you using cm10? which version of it?
Click to expand...
Click to collapse
CM 10 FXP 220, just before enter the system there si battery status for JB 4.1 and my phone stuck there.
Also where to find my region code, I mean I am from, BUlgaria, but dont know is it "bul" or "bg" or someth. for the GPS tweak.
kurotsugi said:
pardon me? what do you mean with flash gordon?
Click to expand...
Click to collapse
Its an application That fakes recovery for xperia j and other phones without cwm. U can flash zips with it
Sent from my ST26i using xda app-developers app
Hey everyone, I need some information on local.prop and build.prop.
First of all, are these two files loaded on every boot or just once after you flash them?
Also, what is the difference between the two? I have gone through several ROMs/mods, and I have seen that some people use local.prop for the same values that some other people use build.prop.
What is the difference? If I am cooking my own rom, can I just add any line I have on local.prop to build.prop and delete it?
Thanks!
Hi.
I have a XOLO-ONE [non-rooted] and recently updated it via the "software update" option in the system information tab of settings. It runs Lollipop 5.0.0.
I noticed that before updating, it showed a prompt saying "no update.zip found in root of memory card, download?" I found out that you can download the update.zip from xolo's official site. It was about 30 mbs.
Now, i wonder if i can edit it's contents(updater-script, apps, etc...) and apply the update to my phone?
I repeat, it is NON-ROOTED.
The zip file contains the following folders:
META-INF
PATCH
SIG
SYSTEM
scatter.txt [FILE]
type.txt [FILE]
There is no boot.img.
Has anyone tried it? Was it successfull? If yes then please write. Your opinions would be appreciated.
Yes you can do so and its possible flashing a update.zip using stock recovery.
You can edit and change apps amd do anything but remember to update any changes you have done in zip to updater-script carefulley. And set correct permissions to them
Peace
:good::laugh::victory:
Thanks man.
Uh, can tell me how to edit the build.props file?
It is stored as a .p file.
Yes why not opsn the file as a text file in any text editor either on amdroid or on pc.
Now you can change the following things.
1-- change the android version
ro.build.version.release=4.4.2
Edit the number to version you want
2-- change the screen pixel density
ro.sf.lcd_density=200
Edit the value to nearby values only.MY DEFAULT WAS 240 AND I CHANGED IT TO 200 AND IT LOOKS NICE.
3-- change the delvic heap value
dalvik.vm.heapstartsize=10m
dalvik.vm.heapgrowthlimit=68m
delvik.vm.heapsize=256m
Edit the values but only multiply the default values by 2. If any value after multiplying is mord than the ram of your device itself then do mot change the value.
4-- add these lines to the build.prop in end for display enhansment
video.accelerate.hw=1
debug.sf.hw=1
debug.performance.tuning=1
debug.egl.hw=1
debug.composition.type=gpu
After doing so save the file normallt.
Zip the folders and flash them again.
Peace
I would do that but.....
Yes, I would do that but the problem is that the file has a .p extension.
I did some research and found that it is a patch file created by using a program called BSDIFF ( or something like that). The installer-script processes that file by comparing it's checksum and patching the data into the existing file..
Now I'm not sure if creating a custom build. Prop. P file and updating my. Zip file with it will be okay. What if I get into a boot loop? My xolo isn't rooted either.
But, I'm not the expert.
So, tell me about your opinion. Is it safe?
Thank you for your help. ( for before & in advance )
no just name it as build.prop and nothing else. itd a property file and not a .p file.
simply place the build.prop in zip file with this name only. no other name OK.
and flash it.
but if you are rooted then just edit the original file in aystem folder and savf it there only. just open and edit and reboot to see effects.
peace
Sent from my SM-G355H using XDA Free mobile app