I'm looking to change my build prop on my nexus 7 due to some apps and games on market saying game or app is not compatible with my device. I know the device is more than capable of running all games and is very frustrating. How do I change the build prop and what risks are involved in the procedure? CNT find much on the search for changing build prop but get un related results.
Sent from my Nexus 7 using xda premium
Sirus2012 said:
I'm looking to change my build prop on my nexus 7 due to some apps and games on market saying game or app is not compatible with my device. I know the device is more than capable of running all games and is very frustrating. How do I change the build prop and what risks are involved in the procedure? CNT find much on the search for changing build prop but get un related results.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Well first off you need to be rooted. My experience with editing the build.prop is limited to just LCD density which I think is what you're after? Anyway its easy assuming you're rooted... I just use a root file explorer like es or root explorer... set the folder or file as read/write... edit the file and change the LCD density = to whatever... 213, 160, etc.... save and exit.... reboot.... that's what I've always done anyway across all my devices
Related
Xperia X8 battery capacity tweak
BY FREDDIE, ON JULY 26TH, 2011
Introduction
I have been inspecting the Xperia X8 build.prop file when I realize that the battery capacity parameter was not the same as my hardware listed.
The build.prop has been changed after the Eclair update and SE developer may have change the value for compatibility among all region handset. In Android 1.6 version, the battery capacity was set 1200mAH which is correct for my hardware, however in the latest update the battery capacity has been changed to 950mAH. So I decided to change back the value.
Requirement
Rooted device
Root explorer android application
Android ADB
Notepad+ windows application
Procedure
1. Connect your device, turn on debug mode on your android and run this command in italic.
adb pull /system/build.prop C:\
adb pull /system/bin/build.prop C:\
This will fetch file called build.prop from your android and store it at root of C: drive.
2. Now edit the 2 build.prop using Notepad+ and change the parameter:
ro.semc.batt.capacity=1200
Change from 950 to the capacity of your battery.
3. Open Root Explorer and mount the /system folder to read-write (rw)
4. Store the build.prop file back to the X8 by running command:
adb push C:\build.prop /system
5.Set permissions for 2 build.prop in root explorer like this:
[V][V][V]
[V][0][V]
[V][0][V]
6. Reboot your X8 and see if you can get a better life.
Comment or improvement please use the form below.
TnX, i'm sure it will work, but i don't have time.
Its true. Can I change it with RE?
Answer: no.
Sent from my Shakira using Tapatalk
Sysytem/Bin
I don't have a build.prop on my system/bin...weird.
Does this make sense on a custom ROM like GingerDX?
codfreak said:
Does this make sense on a custom ROM like GingerDX?
Click to expand...
Click to collapse
I think, yes...
Chris_Castro said:
I don't have a build.prop on my system/bin...weird.
Click to expand...
Click to collapse
Are u sure ???
This is one of the most important files... you must have it...
Do yu have ROOT ???
Do yu have Root-Explorer (or similar) ???
Do yu looked with Root Explorer into /system (should be one of the last ones) and than the 3th of 4th file ist build.prop
and yu must have it...
@Dare-Devil: I changed it with RE... ???
I think we must wipe battery stats after it...
I am gonna have a look if life is longer...
In GingerDX ROM, the build.prop file don´t have the ro.semc.batt.capacity line, even none linke with any battery text...
This really works??!!
Yes, I don't have it...
Sent from my X8 using XDA App
like.no.other87 said:
In GingerDX ROM, the build.prop file don´t have the ro.semc.batt.capacity line, even none linke with any battery text...
Click to expand...
Click to collapse
Same in Kuya, is this for stock rom only? Or could i add the line myself?
Sent from my X8 using XDA App
corsav6 said:
Same in Kuya, is this for stock rom only? Or could i add the line myself?
Sent from my X8 using XDA App
Click to expand...
Click to collapse
I added the line, now monitoring.
Sent from my X8 using XDA App
It exist on Gc rom
Sent from my Shakira using Tapatalk
Added the line in Gingerdx , now charging, will reply with the results in 2 hours or so
Sent from my X8 using XDA App
i tried this.. waiting for the result.. i also managed to edit the name below the lockscreen im using GC 7.4
The comment in the previous line states:
Code:
# Constant values for Battery test in Service menu
So those values probably are not affecting anything during the normal usage of the phone. They are only used during the test-battery mode, accessible from the secret service menu.
Any other opinions?
i've found this in the build.prop of the gingerdx as well:
ro.product.brand=Sh!tEricsson
Same ro.product.brand=Sh!tEricsson
+1 to Dx
boyngeemmaa said:
i tried this.. waiting for the result.. i also managed to edit the name below the lockscreen im using GC 7.4
Click to expand...
Click to collapse
how did u change the text below the lockscreen? :O what file is it in?
And? does this really work? im on gingerdx!
Goodbye!
So guys,I wanted a long time ago,in a rom far far away ( ) to change my LCD density,because I found it very cool to make my screen seem like a higher resolution one.Also,it's like it grows in size,because more things fit in the same physical space.
However,in Samsung roms(I think only the HyperDroid rom doesn't have this problem,without me being 100% sure) problems can arise when changing DPI in the build.prop .One problem was that the camera was FCing,other problems included incompatibilities with the market etc.My deterrent to lower my DPI was the non-functioning camera.
Anyway,I visited the Desire HD forums 3 days ago,and I found something rather interesting in the IceColdSandwich rom thread.So,for this one all credit goes to LordClockan(Rom and kerned developer for the Desire HD) and alienmind(He and LordClockan are on the same team,or kind of,I don't exactly know),who found out about this(Or at least that's where I heard it from).
So,to change your dpi you can go to /data/local.prop (if the file isn't there just create it with root explorer) and write this line: qemu.sf.lcd_density=xxx,where "xxx" is whatever value you want.
So,while this isn't the best superduperwow tweak ever,and while some may already know it,it is useful after all,so I thought of sharing it with you guys.
Hi,
this solution isn't working for me :-( Tried on the latest leaked ICS 4.0.3. LPH original Samsung and Pure ICS Special edition 6.1 - http://forum.xda-developers.com/showthread.php?t=1451346. Both with the same result. Nothing happened. DPI is still 240. Checked several times - name and location of local.prop file and corectness of the string qemu.sf.lcd_density=xxx (xxx is 170 in my case) Any advices, pls?
Mikous said:
Hi,
this solution isn't working for me :-( Tried on the latest leaked ICS 4.0.3. LPH original Samsung and Pure ICS Special edition 6.1 - http://forum.xda-developers.com/showthread.php?t=1451346. Both with the same result. Nothing happened. DPI is still 240. Checked several times - name and location of local.prop file and corectness of the string qemu.sf.lcd_density=xxx (xxx is 170 in my case) Any advices, pls?
Click to expand...
Click to collapse
First,I think it has to have the right permissions.Dunno which it needs exactly,but try chmod 777.Also,the dpi value must be a multiple of 8,so try 168 or 176 if you want to be close to 160.Try these and report back.
Meanwhile,I'm wondering why the thread has a 1 star rating.It's not anything spectacular,but wtf?Anyway,I ain't here for being congratulated,so be it.
EDIT:Bear in mind that nothing will change in your build.prop .There,it'll still show 240.You will just see the difference.
Has anyone tried changing the dpi on gb roms?
Sent from my GT-I9100 using xda premium
drelite08 said:
Has anyone tried changing the dpi on gb roms?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
yep tried and worked very well with this app
https://play.google.com/store/apps/details?id=com.birdapi.android.dpipro&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5iaXJkYXBpLmFuZHJvaWQuZHBpcHJvIl0.
changed to 200 dpi
looks awesome
I used build.prop Editor to add a new property and it worked like charm
Thanks
gnan10 said:
yep tried and worked very well with this app
https://play.google.com/store/apps/details?id=com.birdapi.android.dpipro&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5iaXJkYXBpLmFuZHJvaWQuZHBpcHJvIl0.
changed to 200 dpi
looks awesome
Click to expand...
Click to collapse
I tried that software (the free version) and got a soft brick so backup if you want to try it.
tolis626 said:
First,I think it has to have the right permissions.Dunno which it needs exactly,but try chmod 777.Also,the dpi value must be a multiple of 8,so try 168 or 176 if you want to be close to 160.Try these and report back.
Meanwhile,I'm wondering why the thread has a 1 star rating.It's not anything spectacular,but wtf?Anyway,I ain't here for being congratulated,so be it.
EDIT:Bear in mind that nothing will change in your build.prop .There,it'll still show 240.You will just see the difference.
Click to expand...
Click to collapse
Thanks for advices. I did everything as you said. Changed value to 176. Check premission - granted 777. The value 240 checked in the build.prop Without success It seems that system ingore this file completely. Whatever is in local.prop file, DPI is still 240
It was the same yesterday when my S2 was running on latest beta leak LPH and the same behaviour with today's official ICS from Smamsung LPQ.
Hello everyone,
I have installed androidx86 on my old netbook and google play says most of the apps isn't compatible with that.I've looked into some topics and i understand that my build.prop file is not giving any info to google play and google play isn't giving me the apps.so im gonna use some info from note 10.1 and lie to google play.with your help of course.for simple : can anyone send me his build.prop file ?
Here u GO!!!!!!!!
txtmikhail said:
Here u GO!!!!!!!!
Click to expand...
Click to collapse
thanks buddy
okb1100 said:
I have installed androidx86 on my old netbook and google play says most of the apps [aren't] compatible with that. I've looked into some topics and i understand that my build.prop file is not giving any info to google play ...
Click to expand...
Click to collapse
Changing your build.prop (and more exactly, your build information) won't really help you too much in this case; you're running an Intel-chip Android build, and most of the apps in the Play Store expect an ARM-chip based Android build. While the majority of the Apps rely on only Java (which is cross-platform) for their main code, if they need any ARM-only Native Code libraries they simply won't link on an Intel-based Android.
Now that you have a GNote build.prop (and you REALLY shouldn't change any of the lines except the ones that start with "ro.build."), please report back and let us know if my suspicions are correct, though.
kcrudup said:
Changing your build.prop (and more exactly, your build information) won't really help you too much in this case; you're running an Intel-chip Android build, and most of the apps in the Play Store expect an ARM-chip based Android build. While the majority of the Apps rely on only Java (which is cross-platform) for their main code, if they need any ARM-only Native Code libraries they simply won't link on an Intel-based Android.
Now that you have a GNote build.prop (and you REALLY shouldn't change any of the lines except the ones that start with "ro.build."), please report back and let us know if my suspicions are correct, though.
Click to expand...
Click to collapse
You were right.Some apps worked but not much.For example dropbox worked but chrome didn`t.I think i will stop right here and install ubuntu.
Edit : Of course i didn`t changed any of these lines except ro.build.
Please Dont Flame Me i know this was answered before but i cant find it in my searches there was a thread on how to edit the build prop of the nexus 7 to the kindle fire so you can play the Optimum app on it . could someone please just point me in the right direction with out chewing me out too much thank you .......lol
Post #14 has a link to the edited build prop http://forum.xda-developers.com/showthread.php?t=2021453&highlight=optimum&page=2
Make sure you backup your original build prop before you make any changes.
What is Optimum?
His cable provider.
Bigup BK
so i back up my build prop and use this with an editor like rom tools right ?
Hi this is a build prop for a z3v but you guys can use it as a resource it has lots of sound mods,z5 stuff, battery saving, turning off logging much more. I'm posting this cause there's not much build prop stuff on xda that's not from 3 or 4 years ago. Yes 95% of this works maybe more im testing things still.
https://mega.nz/#!Bswz3Qya!AiEGXkJcyeOjF-JMJCSOomXsC0XKqwxevFW8PMjejj0
Im use z3v and after replace this file my phone bootloop!
an.tckt.bvt said:
Im use z3v and after replace this file my phone bootloop!
Click to expand...
Click to collapse
Haven't tried this personally but you did set the correct permissions didn't you?
Lord Takyon said:
Haven't tried this personally but you did set the correct permissions didn't you?
Click to expand...
Click to collapse
Yes, my bad! Thi's first time I try, i have no experience
most important is don't change build.prop related within "ro.build.version.sdk" and "ro.build.version.release" if you have different phone model / firmware
now i can't flash by used flashtool and repair with verizon upgrade assistant - sony not work also. any idea for this problem ?