[Q] Change screen density in build.prop - ZenFone 2 Q&A, Help & Troubleshooting

I am trying to change the screen density, as the default 480 density is just ridiculous.
But editing the build.prop changes nothing, as I saw in another thread, I should be modifying the file that references my phone model which should be build.ze551.dual.2p3GHz.prop (Zenfone 2 4GB, 32GB, 2.3ghz, dual sim).
But even including the line: "ro.sf.lcd_density=360" (this line does not exist there, I have to add it). Nothing happens after reboot.
I believe that I am editing the correct file as I tried to add the line "qemu.hw.mainkeys=0" and after reboot I got screen software buttons.
but the density does not change. I know I could use the method of execute in adb: "adb shell wm density 360" but with this method the swiftkey keyboard software does not work correctly and I heard that changing the density with build.prop it would work.
Can someone help me ? I really want to change the density.

check this thread: http://forum.xda-developers.com/zenfone2/general/tip-adjusting-dpi-root-t3098690

aktentasche said:
check this thread: http://forum.xda-developers.com/zenfone2/general/tip-adjusting-dpi-root-t3098690
Click to expand...
Click to collapse
Thanks. but as I said this method is what I am trying to avoid because a lot of apps stops working correctly like Whatsapp, Instagram, Photo editing software, Swiftkey, power save app, etc.
I've done the build.prop method on a lot of other devices and it always work like a charm, everything works nice. But for some reason it is not working with Zenfone and I am trying to figure out why.

JuniorBR790 said:
Thanks. but as I said this method is what I am trying to avoid because a lot of apps stops working correctly like Whatsapp, Instagram, Photo editing software, Swiftkey, power save app, etc.
I've done the build.prop method on a lot of other devices and it always work like a charm, everything works nice. But for some reason it is not working with Zenfone and I am trying to figure out why.
Click to expand...
Click to collapse
I'm also having the same issue. I haven't been able to find any sort of solution for this either. I might try a custom ROM just do I can do the build.prop change for density.
Sent from my ASUS_Z00AD using Tapatalk

Related

Change pixel density

Just now I applied a trick to have more info on my screen by changing the dpi setting. To to so in /system/build.prop modify the following line:
Code:
ro.sf.lcd_density=240
I changed it to 200. After modifying the settings in Launcher Pro I now have 6 rows and 5 columns in my homescreens which still have enough space in between.
You need root access to change system files. The file manager also needs to have root access. I used Super Manager for this.
I got this hack from doid-life. They also give an alternative way using adb.
You can also alter the build.prop by installing the PropEditor-0.3.apk from the following link;
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
Thanks, that made it a lot easier!
Now I also changed these lines:
Code:
ro.wifi.channels=14
wifi.supplicant_scan_interval=90
This way all 14 wifi channels are available (also in 3G mobile hotspot) and the phone scans every 90 seconds for new wifi networks instead of the default 45 seconds. As I always have wifi on that saves some battery.
Ok this is weird. I just discovered that anything else than 240 dpi renders the dialer unusable. Sometimes it opens to only close again a split second later. Pitty because I really like the lower dpi setting. Back at 240 dpi it feels like a phone for the vision impaired.
Can i ask how exactly are the changes brought to dpi adjust?
Sent from my MB525 using XDA App
Can someone please post a screenshot? Because I think this will make everything smaller so it's very hard to read anything.
LCDDensity for Root makes the same, you can find it on the market, free of charge.
Foxhound.kl said:
You can also alter the build.prop by installing the PropEditor-0.3.apk from the following link;
http://code.google.com/p/net-widgetron-propeditor/downloads/detail?name=PropEditor-0.3.apk
Click to expand...
Click to collapse
Cool thanks for this.
I started changing screen density with my HD2 when they only had android from sd card. Basically lower number means "higher definition" and you can fit more things on the screen.
so waht does having 14 channels for WIFI do?
When I change the pixel density, I get FC when opening „phone„. I am using Pay's ROM.
Jt612 said:
so waht does having 14 channels for WIFI do?
Click to expand...
Click to collapse
It allows people to connect to broadcasts on all possible WiFi channels around the world.
So North Americans who might be originally limited to 1-11 (is the NA device locked to this though?) won't miss out on the odd coffee shop hotspot overseas that broadcasts on 13.
m11kkaa said:
When I change the pixel density, I get FC when opening „phone„. I am using Pay's ROM.
Click to expand...
Click to collapse
Try to download spare parts from the market (if its not in that rom already) and uncheck compatibility mode and restart your phone. might work.

(Q) Words with Friends not compatible?

After flashing one of the ICS Roms, the android market says my device isn't compatible with Words with Friends and I can't download it..any ideas?
jdefran said:
After flashing one of the ICS Roms, the android market says my device isn't compatible with Words with Friends and I can't download it..any ideas?
Click to expand...
Click to collapse
Often Android market compatibility issues arise from changes made to the LCD-density property in the build.prop file.
If you've got root access, you can google your device and 'build.prop' to find the standard. You can use ES File Explorer (or a range of others) to change the property. Then if you change it back, it should work again. That's if it's a market compatibility issue.
I've got an SGS2, and when I installed earlier ICS ROMs they also had problems with Words with Friends. It would install properly, but then freeze or crash...leading to the acore process ending.
If it's a custom ROM, try posting in the forum where you DL'ed it. Either the dev will already know about it, or he won't. In either case, he should be able to tell you if there's a fix, if there's a fix-work-in-progress, if it's a samsung problem, or if you're just SOL.
If it's a stock ICS from Sammy...well, you might just be out of luck.
Like the gentleman said above. It's probably due to changing your resolution. Fortunately, I had the same problem and did a lot of research and found a fix. There's 2 ways to fix it.
1. Set it back to the default resolution, then reboot and clear the market's memory.
2. Pay for LCD Density Modder Pro (3 bucks) on android market. It can fix it so the resolution doesn't screw up the market any more. This is the route I took and it worked great.
iivisionii said:
Like the gentleman said above. It's probably due to changing your resolution. Fortunately, I had the same problem and did a lot of research and found a fix. There's 2 ways to fix it.
1. Set it back to the default resolution, then reboot and clear the market's memory.
2. Pay for LCD Density Modder Pro (3 bucks) on android market. It can fix it so the resolution doesn't screw up the market any more. This is the route I took and it worked great.
Click to expand...
Click to collapse
All LDMP does is have you download and install a modded market, right?
(Not knocking the app, just asking)
Sent from my SPH-D710 using XDA App
sideload the apk??
or another trick ive read recently is to use the browser and find the app on the web market, click install, select the browser on the pop-up, sign into your account, select browser again on pop-up, click the back button once and that time select market not browser....hope u can follow all that and that it works??

Real-Time DPI Changer (no reboot required)

I was tired of the camera not working properly when using a custom DPI. I made an app which lets you change it without reboot (especially nice for ART as rebooting takes 5 minutes or so for me).
Just put it in /system/priv-app and set the permissions to rw,r--,r--.
Let me know if you have any questions.
Does this change all apps at once or does it work on an app by app basis ?
Sent from my SHIELD Tablet
ShrekOpher said:
Does this change all apps at once or does it work on an app by app basis ?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
It's everything. I was thinking of possibly maming a version later on that monitors tge running app to change dynamically though.
So now that I did this, how does one undo this? Even if I change build.prop your app takes priority..I want to know for when we get app settings and then I can have build.properties set to 500 and this set to 640 and then remove and boom happy xD thank you though, works like a charm!
ChrisJ951 said:
It's everything. I was thinking of possibly maming a version later on that monitors tge running app to change dynamically though.
Click to expand...
Click to collapse
Thanks for making this much needed MOD/APP ... but I don't really get how to use it though. Do I just put a custom DPI (for example 540) in the box? But if I do that, the whole ROM will change to that DPI. How do I change specific apps into a desired DPI, and everything to a different DPI ?
Thanks.

Changing DPI on the Smartwatch 3

I decided to try changing the watch's DPI a little to see if I could make sideloaded apps more usable, and it worked! Settled on 220 for now, but will probably raise it. It was a bit of a crapshoot, since I've no idea what the stock DPI is.
Anybody else tried this? What values did you decide on? Thoughts?
[NUMINIT] said:
I decided to try changing the watch's DPI a little to see if I could make sideloaded apps more usable, and it worked! Settled on 220 for now, but will probably raise it. It was a bit of a crapshoot, since I've no idea what the stock DPI is.
Anybody else tried this? What values did you decide on? Thoughts?
Click to expand...
Click to collapse
Can you tell me Which sideloaded apps are working with 220 dpi?
donalberto17 said:
Can you tell me Which sideloaded apps are working with 220 dpi?
Click to expand...
Click to collapse
Well, I've only tried a few so far, but here's what I got:
- Browsers are now actually almost usable. UC Mini gives me the best experience so far. Chrome is ssssllllooooow, Firefox is okay-ish, CM Browser crashes on start.
- Stock Google keyboard is finicky, but manageable. Microsoft's handwriting keyboard got screwed up by the dpi change (it works, but the letters are off from where you actually touch the screen)
- Greenify is great
- ES File Explorer works okay
Curiously, only sideloaded apps seem to have been affected. Wear apps, watchfaces, etc. are the same. Notification cards are noticeably smaller, and so are Wear's system icons (charging and disconnected). So there's very little to mess up, and the change is really easy to reset even if you don't know the watch's stock dpi (I don't).
[NUMINIT] said:
Well, I've only tried a few so far, but here's what I got:
- Browsers are now actually almost usable. UC Mini gives me the best experience so far. Chrome is ssssllllooooow, Firefox is okay-ish, CM Browser crashes on start.
- Stock Google keyboard is finicky, but manageable. Microsoft's handwriting keyboard got screwed up by the dpi change (it works, but the letters are off from where you actually touch the screen)
- Greenify is great
- ES File Explorer works okay
Curiously, only sideloaded apps seem to have been affected. Wear apps, watchfaces, etc. are the same. Notification cards are noticeably smaller, and so are Wear's system icons (charging and disconnected). So there's very little to mess up, and the change is really easy to reset even if you don't know the watch's stock dpi (I don't).
Click to expand...
Click to collapse
Stock DPI is 280, btw did you made those apps system apps? or you just sideloaded those apps normally?
donalberto17 said:
Stock DPI is 280, btw did you made those apps system apps? or you just sideloaded those apps normally?
Click to expand...
Click to collapse
Nope, just installed normally with adb install. I can actually access /system partitions with ES anyway.
[NUMINIT] said:
Nope, just installed normally with adb install. I can actually access /system partitions with ES anyway.
Click to expand...
Click to collapse
Ok uc browser it's opening but not loading pages, can you explain me what I need to do? It needs to be a system app? and another question latest version of google keyboard will work?
donalberto17 said:
Ok uc browser it's opening but not loading pages, can you explain me what I need to do? It needs to be a system app? and another question latest version of google keyboard will work?
Click to expand...
Click to collapse
Oh yeah, the browser needs to be system. Sorry for being unclear!
As for the keyboard, yes, it will work. You need to install it and then enable it manually, like this:
Code:
adb shell ime enable com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME
then
Code:
adb shell ime set com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME
Okay, so UC loads pages just fine if you're on Wifi but not connected to your phone via Bluetooth. Weird.

Non-root DPI changing and Boost+

Just discovered a nice little trick that we get as a result of Boost+.
As some of you might know some apps don't play nice with changing the DPI via ADB.
For these apps you can add them to the Boost+ game battery booster and it will fix any issues.
I haven't come across any issues changing my DPI with build.prop file. What issues are you having?
Also, I have no clue what you screenshotted
Look at the play store after you change the DPI with adb. The top dev icons get giant and pixelated.
Same thing is happening in my screen shots with IRCCloud and the user icons. Second one is with Boost+ enabled.
_-..zKiLLA..-_ said:
I haven't come across any issues changing my DPI with build.prop file. What issues are you having?
Also, I have no clue what you screenshotted
Click to expand...
Click to collapse
This is about non-rooted devices, so changing the build.prop is not an option for those devices..
jollywhitefoot said:
This is about non-rooted devices, so changing the build.prop is not an option for those devices..
Click to expand...
Click to collapse
Oops forgot you needed root for that lol. Its been so long

Categories

Resources