Database Users

Change LCD Density without the app

Hey Guys,
So if you want to change the LCD density on your Gen8 (tested on the 70, should work on others but changes, as ever, are done at your own risk) without using the LCD Density Changer app then this is how...
I have had to do this as even with the Root +rw on file system, the LCD density changer changes didn't stick (probably OK for the others)
You will need to use the +rw file system mod as documented here:
http://forum.xda-developers.com/showthread.php?t=930197
(thanks Chulri!!)
Anyhoo... to business.
All you need to do for this is to add the following line into /system/build.prop:
ro.sf.lcd_density=XXX
Using rootexplorer was the easiest for me, I copied the file to dropbox, made the change on my computer and then recopied back into /system - note, if you use root explorer, make sure /system is mounted as RW, not RO
You will be able to abd push the file though if you don't want to use dropbox, but I couldn't find my cable when I did this
Reboot.

For some reason after changing lcd density, inputting text in landscape makes the whole textbox fill the screen,
Anyone else have that problem?

oi oi oi whats all this then?!

TheDeadCpu said:
Hasn't this been posted like.. Twice a week or so on XDA?
Click to expand...
Click to collapse
If it has, the I apologise, but I struggled to find it without using the LCD density changer app

[Q] AmeriCanAndroid is good, but how can I change lcd_density to 240?

I have tried change lcd_density in "startup.txt", but does not work

Boot it.. install any tool like romtool box or so. Change density. Or else edit build.prop from system folder( after mounting it as rw. After dat u have to change the permission of the file to rw,rw,rw) using any text editor. U can see the line corresponding to lcd density. Change the value( number only to 240 or desired level) . Save.reboot into recovery. Do a permission fix. And wipe cache and dalvic cache if u need. Reeboot phone. Done.
send from my hd2 @ miui 1.12.2

summit_zhang said:
I have tried change lcd_density in "startup.txt", but does not work
Click to expand...
Click to collapse
Install File Expert (file explorer).
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=240
Exit editor saving the file
Browse to Internal storage /system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=240
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
Hopefully this works! If not, try changing density to 160 (instead of 240) as many advise this is better. However a 240 density, makes display larger, while 160 is very much similar to what you now have.

Just open Root Explorer. Open up /system/build.prop and edit density to 190
Hf
Sent from my HTC Pyramid (HD2 Leo)

[Q]Costum DPI + Android market.

Hi there,
I am a user of the Redux2 HD2 ROM. With my own set 192 DPI. However as you will probably know many apps do not show up (cus of the old market, new one you'll see its "incomapatable"). And i was wondering if there was any fix for this. problem that sloves it well.
Now you have to change the DPI back, reboot, install apps, change DPI, reboot. There must be another way to this.
Since the HD2 has such an huge screen it is (imo) waaaaaaay more comfortable then the stock (oversized icons) 240DPI.

I agree that the 240 dpi makes the icons (and the whole display) too big for HD2. The ROM I use, had 167 dpi as default, but this caused compatibility problems to the newest Market app, so I changed it to 160. Here's how:
Install File Expert (file explorer). (you can use your preffered explorer for this, but keep in mind that you need to have root access and be able to change file permissions!)
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage/system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
This setting of 160 dpi might seem too small to you (compared to the 192 that you use) but trust me, after a couple of days you will like it and you won't have issues with the Market!

Sysifos said:
I agree that the 240 dpi makes the icons (and the whole display) too big for HD2. The ROM I use, had 167 dpi as default, but this caused compatibility problems to the newest Market app, so I changed it to 160. Here's how:
Install File Expert (file explorer). (you can use your preffered explorer for this, but keep in mind that you need to have root access and be able to change file permissions!)
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage/system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
This setting of 160 dpi might seem too small to you (compared to the 192 that you use) but trust me, after a couple of days you will like it and you won't have issues with the Market!
Click to expand...
Click to collapse
I think the question was more of trying to find a way around the DPI problem, not just changing it.

What if change the product name from HD2 to other native Android device in build.prop?
Could this work?

tharche said:
What if change the product name from HD2 to other native Android device in build.prop?
Could this work?
Click to expand...
Click to collapse
No since it wont change the fact that it uses a DPI that is not standard.
And i tested the 160 DPI and for some reason my rom (Redux2 HD2) is not compatable with those DPI settings (white statusbar if app is open) And some other weird glitches

Try this market, it's the old one but it's modified so the DPI isnt checked.
I use it and never had the problem of apps not showing up (as far as i know)
Just flash it in CWM or take the vending.apk inside the zip and move it to the /system/app/ folder on your phone
Please tell me if it helped.

Maxp101 said:
Try this market, it's the old one but it's modified so the DPI isnt checked.
I use it and never had the problem of apps not showing up (as far as i know)
Just flash it in CWM or take the vending.apk inside the zip and move it to the /system/app/ folder on your phone
Please tell me if it helped.
Click to expand...
Click to collapse
tested it. did not work.

try this then http://forum.xda-developers.com/showpost.php?p=20623581&postcount=10,
maybe in combination with Market Enabler to show country specific apps

[Q] Hero Stock Rom .. Any possibility to run newer apps

I just installed my Hero's stock rom.. Android 1.5 with the first version of sense..
I did this with the sole purpose of seeing how it actually ran back then, compared to all the custom roms thats out there.. And i actually think it runs damn well! Its very snappy and it does have the functionality i need.. But most of the apps i use does not support Android 1.5 anymore which is a problem for me..
Is there any way you can "fake" that the android version you are running is maybe 2.1 ? So that i can download the apps i need, or would that not work? I remember that when i had a Tattoo i could fake the resolution of the display, so that more apps would show, and it worked fine actually.

You can try Change model!
If i remember correctly I've a solution:
You need root privileges (and I think you've =)) and a file manager as ES File Explorer.
In ES go to Setting -> Root Option -> Explore as Root and Mount File Sistem
In system folder find and open file build.prop, make a backup and edit the original
Setting, for example:
ro.product model=Nexus S
ro.product manufacturer= Samsung
Save and now you can install all apps...

I don't think it's that simple. Try this:
Reference: http://developer.android.com/guide/appendix/api-levels.html
Tool: http://code.google.com/p/android-apktool/
1 - Put the apk you want to change in the apktool folder and open cmdline.
2 - Run: apktool decode name.apk
3 - Use notepad to edit the AndroidManifest.xml and change the value for 'minSdkVersion':
<uses-sdk android:minSdkVersion="3" /> (3 or whatever version of Android you want your app to be compatible with.)
4 - Build a new apk. eg. apktool b C:\apktool\name name2.apk
Even if the apk installs; some or all features of the app may not work. Also, you will probably need to change the 'AndroidManifest' of any new version or update.
The other option is to find older versions of the app.

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