I have two phones, a Huawei m860 and an m835. They are both basically the same phone, except the m835 has a smaller screen.
I have a CM 7.1 ROM that runs great on the m860 with the larger screen, but is out of scale on the m835 with the smaller screen.
I edited the BUILD.PROP file and changed the LCD.SCREEN.DENSITY from 160 to 120. But when I inject the edited file back into the zip file, ROM Manager says the ROM is bad and refuses to flash it.
Anyone know how to properly recompile the ROM with the edited BUILD.PROP file, so that I can flash it?
You can use an app to change the screen density.
Can you elaborate a little? What app?
1. You can use LCDDensity
2. Or if you don't want to have an app running in the background, you can simply install ES File Explorer and (as you know) go to /system/build.prop and change the density and reboot. This is permanent or until you change it back or flashing the/a ROM again.
Thanks, I was able to edit the /system/build.prop file after flashing the ROM, and that did the trick once I rebooted.
Now though, I've discovered that the screen does not change orientations when I turn the phone as it should. Any have any ideas how to fix that?
-TheGE128
Related
So have anyone noticed various apps incompatibility issues?
I noticed this after updating to CM7.1 that my navionics app was "incompatible" from the market place even though I had it on the stock device.
After flashing back to stock/cognition, it worked again.
Today I flashed to the "unnamed" rom, now I noticed that some games, like Let's Golf! 3 is incompatible.
This brings me to the question, what is the official LCD density of the AT&T SGS2 so that I can set with an app or something to ensure the greatest compatibility of apps?
Thanks
The official density is 240. I too found problems when getting away from that so I have left it alone. I am used to the bigger fonts now.
What app did you use to set the LCD density?
You can modify the build.prop file in the system folder. The app I use is 'Root Explorer' and the method is below:
The line to modify is 'ro.sf.lcd_density=240'
- make sure folder is mounted as 'R/W'
- long press the 'build.prop' and select 'open in text editor'
- change the current value (240 in the example above)
- hit save and exit
- reboot
Your existing build prop is saved as a .bak file
This is the process I use with 'Root Explorer' - may work similarly with other file apps
Hey, try Font Size app and select small fonts... I use tht.
Sorry for the noob question but what do I get by changing the screen density in my phone.
Sent from my GT-I9100 using XDA
There's a procedure, but why do you want to try this?
1. Open Root Explorer.
2. Go to /system
3. Click on Mount RW (It should appear as Mount RO, that’s when it is correct!)
4. Look for build.prop. Long press on the file and press Open file in Editor
5. Scroll down to ro.sf.lcd_density=240
6. Change the value to anywhere between 180 and 240. The lower the value, the higher density your screen will have.
7. Click on the Menu button, and Save and Exit.
8. Reboot.
Be careful because you may encounter some problems with the market. If so change to 240dpi when want to use market and then back to your option....
Easier to use density modder app from play store
Thanks guys
Get an app from palystore and nothing is going to happen to your device, just keep the values between 160 to 240 and you are fine. All the new market apk's work perfectly!
on what depends if dpi changes work ? if i change dpi from 240 to 192 or whatever, on reboot it hangs on yellow triangle. the build.prop is in the kernel or in the OS ??
spirotech said:
on what depends if dpi changes work ? if i change dpi from 240 to 192 or whatever, on reboot it hangs on yellow triangle. the build.prop is in the kernel or in the OS ??
Click to expand...
Click to collapse
if ur phone doesn't start then wipe data,cache,dalvik cache and reboot.which method r u using to change dpi?
There was a bug in some pre-release versions of ICS where ro.sf.lcd_density appeared twice in the build.prop and if both instances weren't changed to the same number, the phone would hang on the boot screen, I'm not 100% sure that this persisted in release versions but it's a possibility and a possible cause of boot problems.
is the ability to change the dpi dependant of the kernel i use?
Has anyone changed their DPI? I'd like to make everything a hair smaller. I am on the new ICS leak with root. Will changing the DPI cause touchwiz to break? Should I just wait until a stock rom comes out? If not what tool/settings are known to work?
thanks
bump
Rom Toolbox is the only app that has worked for me in ICS.
Im not sure how touchwiz will react since I use Apex.
Use a root a file explorer, go to /system mount r/w, long press on build.prop open in text editor.
ro.sf.lcd_density= 320
Is the line you're looking for, just change the number to the dpi you want, save, reboot, profit.
Ok so I installed CWM and rooted. Then I tried Rom Toolbox Lite (as I had done before on my Skyrocket)
I was trying to lower the density a bit. I went to 260(original 320) and now it won't let me go over 280.
Anyone know of another app that can adjust LCD density?
nest75068 said:
Ok so I installed CWM and rooted. Then I tried Rom Toolbox Lite (as I had done before on my Skyrocket)
I was trying to lower the density a bit. I went to 260(original 320) and now it won't let me go over 280.
Anyone know of another app that can adjust LCD density?
Click to expand...
Click to collapse
Just use a root explorer and manually edit the build.prop file. I use ES file Explorer and its built in file editor.
Posted by Mr. Z's Galaxy S3.
zanderman112 said:
Just use a root explorer and manually edit the build.prop file. I use ES file Explorer and its built in file editor.
Posted by Mr. Z's Galaxy S3.
Click to expand...
Click to collapse
Well did that, and now phone won't boot up. Going to reflash stock rom.
Reflash of stock rom fixed the boot and lcd issue and all my apps were still there which was even better
Hey guys, Im here to complain. I'm super tired, so I probably won't be very easy to understand.
Anyway, my Huawei Activa 4g was rooted and all was well. I went to change the DPI with the DPI Modded app from the play store, and its all screwed up now. I can't get past my lock screen, it only shows the clock and the emergency call button. I can't swipe the dots, and they aren't just invisible. I was dumb and deleted my backup.
Please, get back ASAP, as I am panicking.
PS: Usually I sound much more intelligent, but I literally nodded off three times as I wrote this.
You have a custom recovery like CWM, right? When you used the DPI Modded app, did it make a backup of your build.prop file on your SD card? If not, do you remember what your stock DPI value was prior to you changing it?
I can tell you what to do, but it's easier if you just follow this guide. Since you can't boot into your ROM, boot into recovery and follow the rest. adb works in both the ROM (if USB debugging is enabled) and in custom recoveries.
http://forum.xda-developers.com/showthread.php?t=1236732
If you have the backed up stock build.prop file, then you can directly skip to the part where you copy it from sdcard to the system partition. If you don't have it, then you need to open this build.prop file (that you get on your computer using adb pull) with a text editor and change the value of this one line ro.sf.lcd_density=, to whatever the stock DPI value was before you changed it. If you don't remember, then try 160. If that doesn't work, repeat the process with 240. Standard DPIs for devices are -
LDPI (Low DPI) = 160
MDPI (Med DPI) = 240
HDPI (High DPI) = 320
Your phone falls into the LDPI category, so 160 should work. Any DPIs other than these are non-standard DPIs and cause compatibility issues. Even to use to these standard DPIs, the ROM needs to support DPI scaling. Usually stock ROMs don't, while custom ROMs especailly AOSP ROMs like CyanogenMod, AOKP, Paranoid Android etc do. If you don't have the Android sdk installed on your computer, and you need the adb files, then use the attached file. Remember to open command prompt in the extracted zip folder, otherwise it'll return 'adb not found'. CMD needs to be opened in the same directory to be able to detect the adb.exe file. Alternatively, you can open cmd directly in the folder by running 'Start_here.bat'.
or go to recovery an clear dalvik caseh
-fluffy- said:
or go to recovery an clear dalvik caseh
Click to expand...
Click to collapse
That won't help because his stock ROM is incompatible with whatever custom DPI he set. Dalvik cache is only related to apps, and this has nothing to do with apps. Only way to fix this is to change the LCD density back to stock value in build.prop.