I know that local.prop is loaded after build.prop when the system is booting, however, my question stems from this
If I would put some lines from build.prop in local.prop and change them, would the changed settings take effect or would the build.prop settings overwrite the local.prop settings anyway?
For example:
build.prop
ro.sf.lcd_density = 160
local.prop
ro.sf.lcd_density = 120
When the system boots, would the density be 160 or 120?
Thanks, whoever helps on this
Density would be 160.
waffle_ said:
Density would be 160.
Click to expand...
Click to collapse
Thanks man
HEROEVO said:
Thanks man
Click to expand...
Click to collapse
No problem.
Lines in the build prop that start with RO mean read only and cannot be overwritten by the local prop. You would have to edit the line in the build prop. Anything in the build prop that does not start with RO would be overwritten by local prop. For instance my local prop has the auto backlight line edited to disallow it by changing the = 1 to = 0. I also have the default brightness line to be max bright by changing that line from = 143 to = 255.
il Duce said:
Lines in the build prop that start with RO mean read only and cannot be overwritten by the local prop. You would have to edit the line in the build prop. Anything in the build prop that does not start with RO would be overwritten by local prop. For instance my local prop has the auto backlight line edited to disallow it by changing the = 1 to = 0. I also have the default brightness line to be max bright by changing that line from = 143 to = 255.
Click to expand...
Click to collapse
You da man Duce!
How do you save build.prop ? I get access denied
tmanbt said:
How do you save build.prop ? I get access denied
Click to expand...
Click to collapse
You have to enable read/write mode. Little button on top of the screen on root explorer when browsing files and folders. It will say r/o before you press it.
nandroids are for
sissies
Related
alright... I rooted my nook color, and I was wanting to change the screen specs to match the galaxy tab, but when I open my system > build.prop file in the root explorer, I can't change anything... any suggestions??
this is because the NookColor's stock LCD density is 169.333, which is pretty low (Galaxy Tab is 240). Unlike resolution, which is hardware-based, density is software-based and can be changed. If you search the market for LCD density, there are a couple apps that will do this--a free one that won't survive a hard reboot, and a paid one that (supposedly) will.
If you want to make it permanent for free, you can edit your build.prop file. Again, use Root Explorer to open system/build.prop (BACKUP FIRST!), find the following two lines:
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
If you wanted your density to be 250, you'd replace them with the following single line:
ro.sf.lcd_density=250
Save the edited file, and reboot.
Click to expand...
Click to collapse
Mount the /system partition as r/w first, there is a button on the top.
Forgot to mention that I tried that.. I restarted root explorer... no change
Sent from my HTC Glacier using XDA App
I just did it with mine no problems.
Sent from my LogicPD Zoom2 using Tapatalk
long press "build.prop" and select "open in text editor" from the popup menu.
Also 240 will be way to big. The menus wont fit. Im on 200 right now and some screens are off but not to bad.
sent from my Rooted Nook Color using Tapatalk
arda99 said:
long press "build.prop" and select "open in text editor" from the popup menu.
Click to expand...
Click to collapse
thanks... only time I'd used it was on my HTC Glacier (mytouch 4g), and I didn't have to do that... works like a champ
Can't get /system into r/w
I'm trying to change my build.prop file to change the display density on my NC.
I have an edited file waiting to be used.
I want to rename the original build.prop to something like build.old and copy the new file in next to it.
But Root Explorer won't change /system to r/w.
I can't rename the original file or paste the new file.
I can flip root "/" back and forth from r/o to r/w without problem.
But nothing happens when I touch or hold the button when in /system.
?????????
Did you figure this out? I am having the same issue modifying files for the hulu fix.
Is there any possibility of modding /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq without modding the kernel?
Just in case you don't know, cpuinfo_max_freq is the file that limits the maximum processor speed to 1000mhz.
cpuinfo_min_freq is the one that limits the minimum processor speed to 100mhz (i've no interest in modding that file).
I know i can acquire this with a custom kernel or by modding one myself, but i'd like to know if there's any way of doing this other than with a custom kernel.
Tried using root explorer and change permissions to write too apart from read and then modding, without success.
Tried changing permissions using root explorer and then using an init.d script
Tried a few more things, but so far none have worked.
Thanks
You did everything correct but one thing more open root explorer.
# Go to desire file (make sure you have it on rw)
# Now press and hold the file
# a menu will popup
# go to open in text editor and you can edit it
Enjoy
i have just tried it.. normally when i change any system file with text editor, i click on "save&exit" and it says it is saved and the original file is named as xxxxxxx.bak..
but this time there is no .bak file and the original file is not changing.. i write 1200000 but when i try to open it again it turns back into 1000000 ...
kkube said:
You did everything correct but one thing more open root explorer.
# Go to desire file (make sure you have it on rw)
# Now press and hold the file
# a menu will popup
# go to open in text editor and you can edit it
Enjoy
Click to expand...
Click to collapse
Tried that too. Root explorer says it's modded it but if you open it again, no change has been applied
Apparently, it's read only even after changing permissions.
or that file is modified by something else all the time.. obviously we have to change something else before that..
_delice_doluca_ said:
or that file is modified by something else all the time.. obviously we have to change something else before that..
Click to expand...
Click to collapse
The kernel. Just wanted to find out if there was another way, it'd be much simpler than modding a kernel. It seems there isn't
Just a trial idea, copy that file to as card, then edit it. See if it saved then, then rename old one as xxxx.bak and paste the edited file there.
I can't do it as I am on a custom kernal and i am able to change it as I said.
Check it out and tell if that's any help
Sent from my GT-I9000 using XDA Premium App
coldflid said:
Is there any possibility of modding /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq without modding the kernel?
Just in case you don't know, cpuinfo_max_freq is the file that limits the maximum processor speed to 1000mhz.
cpuinfo_min_freq is the one that limits the minimum processor speed to 100mhz (i've no interest in modding that file).
I know i can acquire this with a custom kernel or by modding one myself, but i'd like to know if there's any way of doing this other than with a custom kernel.
Tried using root explorer and change permissions to write too apart from read and then modding, without success.
Tried changing permissions using root explorer and then using an init.d script
Tried a few more things, but so far none have worked.
Thanks
Click to expand...
Click to collapse
Its impossible, i tried this command on terminal: echo 1800000 > /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq it says permission denied (i was su)
Use Tegrak Overclock
Edit System Files
I have the same problem
think you have to edit the init.rc file
Ok so when i wrote the title for this post, there where other posts that came up, but none of them are geared towards the nook color. I looked in the system folder but nothing was there with the build prop file name just a build. Can someone point me in the right direction on what to change. I am thinking of changing the file to match either my Droid Eris or a Nexus S. Or even a tablet?
Not sure I understand exactly what you're asking, but the build.prop is in /system. Sounds like you would want to change the build fingerprint, but you need to look at the one from your phone to make sure you know what to change it to.
I tried that but there are 2 flies located in the system folder, one that says build, and another that says build prop. The Nook Color does not have that second folder so I do not know what to change to change the fingerprint of the device.
Wrong thread
waffleb051 said:
I tried that but there are 2 flies located in the system folder, one that says build, and another that says build prop. The Nook Color does not have that second folder so I do not know what to change to change the fingerprint of the device.
Click to expand...
Click to collapse
build.prop is the file you will be changing... the fingerprint is one of the settings inside build.prop
ianPhillips1 said:
Wrong thread
Click to expand...
Click to collapse
As of now yes
DizzyDen said:
build.prop is the file you will be changing... the fingerprint is one of the settings inside build.prop
Click to expand...
Click to collapse
Ok I'll whip up so modded buil.prop files test them then upload them on this thread.
Hi, how do I change asylum's rom dpi?
Is there any way to change it like Paranoid Android rom? I could just change it in the option settings easily.
But I don't find it in asylum's rom. If i'm not wrong, it is using 240dpi.
Am I able to disable or enable on screen soft keys?
Download Romtoolbox Lite or Pro and use the build.prop editor or tweaker and set ro.sf.lcd_density to your liking.
213, 240, 320 ...
Otherwise manually by editing build.prop with root explorer.
Mount system RW.
EDIT build.prop
Change the following line
ro.sf.lcd_density=213 (tablet mode)
Add another line saying
qemu.hw.mainkeys=0 (softkeys)
Close and save
Mount system read only.
Reboot.
I have GingerDX installed on a stock kernel. My ro.product.manufacturer in build.prop says "Sh!tEricsson" and I wanted to change that, cause now I can't install Sony Ericsson Backup&Restore and can't restore a backup where all my contacts are saved.
Anyway, it looks like the changes I make do not save. I've followed all steps in tutorials - mounted /system as R/W in Root Explorer, changed permissions to 'write' for group and others before making changes (and changed back after saving). I press 'Save' or 'Save and Exit' and it's all fine. Then I change the /system back to R/O. I can reopen build.prop it in any other file editor and the change is still there, but SE B&R still says I don't have a Sony Ericsson product and after a reboot the ro.product.manufacturer line is reverted back to "Sh!tEricsson". I've tried Root Explorer, ES File Explorer, Prop Editor and BuildPropEditor, nothing works. Any ideas?
Check /system/bin. Some roms have a build.prop there that you also have to edit.
Sent from my rooted tomato using xda app
Yes there are 2 build.props..
One in /system and other in /system/bin.
you have to edit them both to change your build.prop successfully...
Thanks for a quick reply guys! I had no idea about the second file. Everything works now, cheers! :highfive:
make a flashable zip
Sent from my X8 using xda app-developers app
Build Prop is not saving
I tried apps to edit Build prop when ever I reboot the device all Build prop stays the same as before after edited