Database Users

Screen after 2.3.4 Update

Hey Guys, I updated and rooted my phone to 2.3.4 HK...
Anyways, I remember seeing a post about an app that lets you enable the whole screen.
It appears that I have some dead space on the main home screen and I can not place any widgets in it (Its in the bottom)...
Any way I can fix that ? I cant remember the app name for the life of me.
thank you,
Alex

Hey, just use root explorer or shell in order to edit the build.prop in your system folder (or just use CWM and mount your /system folder to your computer). in the build.prop, there is a section that describes the ppi and for some reason, it's set as default to 240. Change it to 275 and it should fix all screen issues.

thanks for your response!! I checked thru Root Explorer, and only found
dpi... not PPI.. is that what you meant? Cause I see that listed as 240.
Also, do I need to reset after the edit?
Thanks a lot!!

The stock launcher seems to be messed up, get a different launcher.
Sent from my MB860 using XDA App

Some people have complained about the resulting effects of changing the build.prop file with this fix. Better to just use a different launcher than stock as was said.

LCD density for root I believe it is the 270 setting you need to select.
Sent from my MB860 using XDA App

Any way to edit build.prop while running from SD CM7?

Runnning CM7 on a Nook color "OFF THE SD" card and cannot edit my build.prop file. Is this because the system is running off of that card ? I have tried to use the ES File Explorer but cannot "mount" the system when I go in the settings.
I don't want to load this OS in to the internal memory just yet and thought it would be great to make the changes needed for the app store and netflix.
All the threads I see relate to if the OS is running on internal memory not the SD.
Thanks in advance,
housej55

Try root explorer yes it costs money but it is one of the most useful apps you can buy.
Sent from my NookColor using Tapatalk

Hope I can learn something new today, I've seen a lot of threads/posts indicate about changing the build.prop. Why is that? What's that for? and in what case, we need to modify it?

votinh said:
Hope I can learn something new today, I've seen a lot of threads/posts indicate about changing the build.prop. Why is that? What's that for? and in what case, we need to modify it?
Click to expand...
Click to collapse
I edit it to set the LCD density to 187 (defaults to 161); that's pretty much the screen resolution, so if buttons are too small to hit, you can make everything bigger.
Other things in there tell Android what platform is running, so that if an app (market, netflix, etc) cares, it can check.
And you can modify it when running from SD, use Root Explorer, navigate to /system, then tap the "mount R/W" button to enable writing, long-press the file, pick "open in text editor", make your changes, menu/save&exit, reboot.
Sent from my NookColor using XDA Premium App

How to edit build.prop file on almost any android phone SAFELY?

So guys...after surfing many websites..restoring my nandroid backup for almost 10 times i finally found a safe way to edit the build.prop file.. I don't exactly know if this happens on other android smartphones but whenever you try to edit the build.prop file via any editor on your phone or in my case even via adb i get bootloops...
So i tried remounting system and then unmounting it...i tried many file editors file explorers but every time what i got was a god damn phone stuck at the galaxy s2 logo
And also i would mention that I SEARCHED OVER XDA TOO!!.....the guys had great tools developed but they did not work in my case either.
So no more talkingss.....just how to do it...its rather very simple...you just need an app called Rom Toolbox...its free as well as paid too...download as per your requirement.. AND obviously YOU NEED ROOT.
Well open it(duh) and go into the performance tab and select the build.prop editor...well i will explain you what these values stand for...i am not going to explain each and every value but the ones you would require...leave the unlisted in the comments...
ro.build.date - Change your roms build date
ro.build.description - Your phone's description
ro.build.display.id - Change the build no.(dont use it on custom roms....respect the devs)
ro.build.product - Change your model number....
ro.build.version.release - change the android version(not really actually )
ro.product.brand - Phone's company (Samsung in my case)
ro.product.device - Change the device name
ro.product.model - change the model number
ro.sf.lcd_density - Change the lcd density(dont ask me what it is...google it)\
So guys dont change the values out of range like setting lcd density to 5000...or anything else...and also if anything happens to your phone I AM NOT RESPONSIBLE....
also this is my first thread so guys bear with me....i am a new semi pro java developer i would really like to contribute....

build.prop editing = Root Explorer, long press, open in text editor...

karendar said:
build.prop editing = Root Explorer, long press, open in text editor...
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA

Or build.prop editor from the market.

Never had any trouble editing the LCD Density with root explorer :/

B3311 said:
Or build.prop editor from the market.
Click to expand...
Click to collapse
I second this.

I had bootloops....
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......

rohan999 said:
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
Click to expand...
Click to collapse
Check for ownership and permissions before restarting. They are probably messed up and are causing bootloops. Or you made a typo somewhere and cause bootloops that way. Root Explorer always works fine for me.

No bootloops here either using root explorer or rom toolbox
Sent from my GT-I9100 using Tapatalk

rohan999 said:
I had bootloops dont you guys read.......!! I used root explorer...and text editor too
May be its the rom thats causing problems......
Click to expand...
Click to collapse
Maybe it's you bro
Sent from my GT-I9100 using xda premium

Please be dont be too hard on him. And i heard someone said it needs to be edited at two places sometimes, but i didnt read the threaded comments till the end. Its lost now. I guess thats that the thread starter means. On some roms, it caused bootloops. Is there any special thing to be taken care of cuz bootloop does happen on certain roms when u edit the build.prop on certain custom roms? On stock deodexed roms, no issues for me
Sent from my GT-I9100 using xda premium

The OP is definitely onto something, because it happened to me.
Specifically, I was trying to edit the DPI setting. Out of the stock ROM, the lcd_density setting was present twice in the file (kind of strange, but oh well - normally it shouldn't cause problems). Edited from 240 to 200 without typos, I'm not allowed to do that due to my line of work , reboot, bam! boot loop.
Replaced the build.prop from backup, edited with "build.prop Editor" from Market - no problems. Really don't see what was the difference, except the duplicated key which was gone after editing with build.prop Editor (probably it does some sort of unique key checking). Oh well, not serious enough to investigate further.

VAXXi said:
The OP is definitely onto something, because it happened to me.
Specifically, I was trying to edit the DPI setting. Out of the stock ROM, the lcd_density setting was present twice in the file (kind of strange, but oh well - normally it shouldn't cause problems). Edited from 240 to 200 without typos, I'm not allowed to do that due to my line of work , reboot, bam! boot loop.
Replaced the build.prop from backup, edited with "build.prop Editor" from Market - no problems. Really don't see what was the difference, except the duplicated key which was gone after editing with build.prop Editor (probably it does some sort of unique key checking). Oh well, not serious enough to investigate further.
Click to expand...
Click to collapse
How did u replace it with ur backup? I normally restore back my nandroid. Is there a much simpler way such as putting it in an update zip or something? Mind to share?
Sent from my GT-I9100 using xda premium

kyleforge said:
Maybe it's you bro
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
bpivk said:
Check for ownership and permissions before restarting. They are probably messed up and are causing bootloops. Or you made a typo somewhere and cause bootloops that way. Root Explorer always works fine for me.
Click to expand...
Click to collapse
override182 said:
Please be dont be too hard on him. And i heard someone said it needs to be edited at two places sometimes, but i didnt read the threaded comments till the end. Its lost now. I guess thats that the thread starter means. On some roms, it caused bootloops. Is there any special thing to be taken care of cuz bootloop does happen on certain roms when u edit the build.prop on certain custom roms? On stock deodexed roms, no issues for me
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
thank you really mate....you are not like the others who just need a reason to insult.....well this is my first thread...so its noobish....but i am a programmer (java) so i will be bringing some good roms later..

override182 said:
How did u replace it with ur backup?
Click to expand...
Click to collapse
I made a copy of /system/build.prop before editing it, of course. After rebooting and getting the bootloop, it's just replacing this file from the backup copy.

I've been using build.prop editor from Nathan Campos, 0 issues so far.

VAXXi said:
I made a copy of /system/build.prop before editing it, of course. After rebooting and getting the bootloop, it's just replacing this file from the backup copy.
Click to expand...
Click to collapse
Im still not clear on this. How did u managed to replace when u cant boot the device and edit it back again to the working build.prop. Did u push back via adb or some update.zip?
Sent from my GT-I9100 using xda premium

The device boots just fine, it just doesn't complete the booting process and remains at the spinning S with blue particles. You can use ADB during that time.

VAXXi said:
The device boots just fine, it just doesn't complete the booting process and remains at the spinning S with blue particles. You can use ADB during that time.
Click to expand...
Click to collapse
Noted. Thx
Sent from my GT-I9100 using xda premium

rohan999 said:
thank you really mate....you are not like the others who just need a reason to insult.....well this is my first thread...so its noobish....but i am a programmer (java) so i will be bringing some good roms later..
Click to expand...
Click to collapse
Most of us didn't insult. Don't jump the gun. Just giving the other side of the coin. Root explorer editing works fine, as others have stated it's possibly a messed up rom giving weird permissions to build.prop. chmod 644 build.prop usually solves the issue though.
I can't speak for everyone, but I wasn't hard on you... Noobs are noobs and I'm fine with that. Most info is readily available on the forums though... Just not necessarily on this forum. XDA is bigger than the sgs2 forums and other communities have very interesting ideas and threads!
***edit*** yeah, after re-reading, noone was harsh in any way. So... yeah!
Sent from my GT-I9100

Soft key color change?

I'm curious if anyone has used Rom Toolbox, and knows if it can change the color of the three soft key colors (you know, back, home, task mgr)? Or do you know how to do this WITHOUT running a ROM. I'm not a big fan of ROMs. I know how to manually replace the boot animation, but figured if ROM Toolbox can do both of these, then I will use it. Either my search skills are very crappy (which I know to be fact, lol) or nobody has ever really posted about this. Any help would be appreciated. These are last two things I need to finish my customizing. Thanks.
EDIT: CRAP! Can a mod move this to the Q&A? That's where I was, and I somehow ended up in the General section, lol. Thanks.

Edit the systemui.apk file, in the res/drawable-hdpi folder all the icons are there.
Custom ROM not needed, just root since it's a system file.
Sent from my Nexus 7 using xda premium

More difficult than thought. I extracted SystemUI.apk from "system/app", replaced the default images with the ones I want to use, zipped it back up, renamed it from SystemUI.zip to SystemUI.apk, and then when I attempted to paste it back into system/app, it wouldn't let me since the folder is read only. I can't seem to change the permissions of "/system/app" so that I can paste this in there. I had a feeling this try wouldn't work, as I got the instructions from a Galaxy Nexus instruction which stated that it would really only work if a deodexed ROM was installed, but figured i'd give it a shot anyway.
I also tried using ROM ToolBox. Created my theme, but it says the theme is incompatible when I try to install it (followed the directions step by step for creating the theme). Looks like I may have to contact the developer of RTB since it would appear that the Nexus 7 isn't supported yet.
"We have compared the images and apps with your current system and have determined that this theme will not work for your current device setup."
Any other thoughts? Am I doing something wrong? Just don't really have a need for a full fledged ROM. Just wanna change 3 little software buttons, lol.
EDIT:
Forgot to mention that I also tried Zip Themer, but like RTB, it doesn't support Nexus 7 yet. I'll be sure to inform both developers

Use root explorer, put the modded apk on your SD then using the phone copy it from SD to /system/app with root explorer and click the mount r/w button at top , or use adb t push it to the device
Sent from my Nexus 7 using Tapatalk 2

If your rom is odexed (which the stock.rom is), then you will not be able.to achieve what you want...
You will need to deodex your rom before theme'ing
Sent from my HTC One X using xda premium

Need help with build.prop edit

I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?

in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Hi,
Same thing for me with Root Explorer, instead I use build.prop Editor
EDIT: not fast enough :laugh:

qsec said:
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Click to expand...
Click to collapse
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.

Maybe it's related to my root access? TB is showing I'm rooted, but check out my superuser app when I try to update an install new binaries...

Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.

EniGmA1987 said:
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
Click to expand...
Click to collapse
Downloaded and installed... Removed the old one. Still not letting me edit... Looks an feels like it is but won't enter any characters. At least RE isn't giving me the "too large" error anymore

in_dmand said:
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Click to expand...
Click to collapse
i had the same issue, couldn't figure out why. try replacing a commented line with the code to disable the nav bar

How do I know if it's just a commented line and not necessary to the program?

in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
i had the same issue any help?

If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app

maxkanick said:
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You are right, I have tried to edit it on pc and stuck on a bootloop.

Use build.prop editor app from playstore
_____________________________________Read more write less and be smart