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!
I have the lg g5 t mobile as the title says it im unable to add lines to build prop. My phone is stock rooted tried with root browser and build prop editor both of which fails. I cant even seem to type anything in the build prop file and the only way i can type in the file is if i delete a line to replace my own build prop stuff.
I have tried with both 10A rom and 10D no improvements
The build.prop gets truncated because it's so large. adb pull it to your pc, make your edits, then push it back and set permissions.
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.