DPI changing in JB - Galaxy S II Q&A, Help & Troubleshooting

Heyo,
I was wondering if there are other people here that can't change the dpi after they moved to JB.
I've tried altring the build.prop file which gave me a soft brick after I rebooted the phone and got the same result with "DPI Changer" and "LCD Density Modder" apps with other people leaving bad reviews on the play store for these apps because apparently they got the same results as I had.
So what's going on with JB and DPI changing?

tal123 said:
Heyo,
I was wondering if there are other people here that can't change the dpi after they moved to JB.
I've tried altring the build.prop file which gave me a soft brick after I rebooted the phone and got the same result with "DPI Changer" and "LCD Density Modder" apps with other people leaving bad reviews on the play store for these apps because apparently they got the same results as I had.
So what's going on with JB and DPI changing?
Click to expand...
Click to collapse
I just edited the build.prop and restart, all OK then.
Which value dpi are you trying to set?
Sent from my GT-I9100 using xda app-developers app

i changed mine in build.prop to 220 and had no problems except market incompatibility, but a modded vending apk fixed that

Related

LCD Density?

With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
I have unfortunately touchwiz can't handle the change, i mean it still works but it doesn't adapt to the new size, neither does the dialer. tried turning off compatibility mode in spare parts, but that did nothing.
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Okay im looking at that line so how do i edit it? Forgive me im new to this stuff /
SGS2 rooted and Overclocked to 1.5ghz stock rom p
No prob. Using Root Explorer, navigate to /system/ and make sure to hit the button in the top right "Mount R/W"
Long press "build.prop" and select Open in Text Editor
Make the change to the line "ro.sf.lcd_density=240" to whatever you want (200 probably works best)
Hit Menu softkey and choose "Save & Exit"
Root Explorer will automatically save a backup copy of build.prop
Reboot your phone to apply DPI change.
There is also a free root file manager called Super Manager, but I haven't used it.
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
nickshertzer said:
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Click to expand...
Click to collapse
Nick I tried your method several different ways and have been going around an around with this for several weeks on our phone and also Sprint version too and the revert back does not stick or still allow to download/update the apps from the market. Tried restarting, clearing cache and resetting the market data and restarting but it still would persist and not allow the updates and incompatibility. The only success I experience is right after I update to a newer version of ROM or clean install all together (which for obvious reasons) resets the phone and then allows the update actions. It is just very frustrating that the DPI change would hinder "Certain Apps" from updating. Anyone have ideas on a future solution besides Nicks input on the manual fix? I think we have brilliant screens with lots of potential for various display options and I miss using the 200dpi settings, but application updates and use of the market is much more important for daily use.
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
fone_fanatic said:
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
Click to expand...
Click to collapse
I have used the dialer files from this thread you mentioned and it all works fine on this ROM the only down side is once you theme that it changes to the themed dialer and goes with the 240 adjusted dialer. I would hope you could share your input and steps (If not too complex) to allow themers to integrate into their themes for multi dpi users.
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
poofyhairguy said:
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
Click to expand...
Click to collapse
this has been posted as an issue, go here and star it to bring it to the attention of the android devs.
qwertyaas said:
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
Click to expand...
Click to collapse
Lowest res on the market? 800x480 is the industry standard at the moment. Not the best, but certainly not the lowest.
Sent from my Galaxy S II (i777) using XDA Premium.
I use 180 on a daily basis. In order to get around the dialer issue. I replace contacts.apk in Unnamed 2.21 with the one from Mikey's Serendipity 8.2 works perfectly except for the already in-call dialer pad which i rarely ever use is still small but the regular dialer is now stretched to full screen. It comes down to editing a .xml file or two if you want to attempt yourself.
Hperdroid has touchwiz that works on 160. it is my understanding most market things work with that density
Sent from my GT-I9100 using xda premium
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
hekoman said:
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
Click to expand...
Click to collapse
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Man_Cave_Tech said:
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Click to expand...
Click to collapse
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
jazzboyrules said:
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
Click to expand...
Click to collapse
Ok, thanks for the input. I'll give that a try when I get home from work tonight.
Sent from my Galaxy S II (i777) using XDA Premium.
I've been using a LCD Density of 185 for as long as I can remember. It's rare now to see an app that doesn't like a custom lcd density setting. Occasionally I run into an app on the market that doesn't like it, and I get the banner at the top of the screen. Since I edit the build.prop for my density setting I have to keep an app handy just incase I get the market issue. But it's an easy fix- use app to get back 240 density> manage applications> market> clear data. Open market> download desired app! Love 185. Probably wouldn't go any lower personally but... for the most part, most apps will happily still work and fill the screen
What do we won lowering the density?
RatusNatus said:
What do we won lowering the density?
Click to expand...
Click to collapse
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Coreym said:
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Click to expand...
Click to collapse
But it's not the same using a launcher that gives you more columns and rows?
Just saying
Saludos desde Ecuador

[Q] Why do information apps report the DPI as 160dpi?

I changed my DPI to 132 dpi in the build.prop file and rebooted. If I run an information app like SystemPanel or Android System Info, they report the DPI as 160dpi. Which one is the real DPI of the tablet? Why do they report this density? If 132dpi is the true density, then why do the fonts look odd in menus and a lot of apps?
Sent from my Touchpad using Tapatalk
mjsztainbok said:
I changed my DPI to 132 dpi in the build.prop file and rebooted. If I run an information app like SystemPanel or Android System Info, they report the DPI as 160dpi. Which one is the real DPI of the tablet? Why do they report this density? If 132dpi is the true density, then why do the fonts look odd in menus and a lot of apps?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
afaik, android only recognizes like 4 dpi's: LDPI, MDPI (160), HDPI, something elsedpi. So, as far as the app knows, your running MDPI, but changing you value will still result in visual changes. I'm not 100% sure if this is accurate, but i think it is, lol
it works this way because there is so many densities and so many screen sizes in android.

[Q] Android DPI

This is probably more of a general Android question (as opposed to device-specific) and one that I've never been able to fully fix on any of my Android devices. When I change the dpi (currently on my RAZR HD XT926) it breaks several Play Store apps. Sometimes I can't download new apps because it will say "your device is not compatible..." and I can't even get updates to current apps I have installed. As soon as I change back to the default dpi and reboot, everything works perfectly. Is there a way around this when changing the dpi on an Android device?
Thanks,
caseym
Thanks
do u want to change the dpi of the app or your phone
nag xperia said:
do u want to change the dpi of the app or your phone
Click to expand...
Click to collapse
Phone. I know how to change the DPI...I just want to know if there is a way to do it and NOT break the market.
Create a file /data/local.prop with permissions set to 644. Put this line in it:
qemu.sf.lcd_density=nnn
where nnn is the dpi. Reboot.
See http://forum.xda-developers.com/showthread.php?p=29413138
This will change your display, but doesn't affect Play. It works on both my Nexus 7 and HTC Desire S.
Sent from my HTC Desire S

[REQ] Per App DPI changer.

Changing DPI gives us some @#$%^&**( in mind. because some other apps are misbehaving and not working.
the question is can we have this app http://www.xda-developers.com/android/per-app-dpi-adjustment-for-the-galaxy-note-2/
BUT it is only available for galaxy note 2. yes a smart tablet. not a phone. can someone got this working on our devices, changing the dpi on build.prop automatically during opening an app then restarting the whole framework while opening the app.
EDIT: (someone used it on an s2 and it's working) there's still hope =')
zenesis said:
Changing DPI gives us some @#$%^&**( in mind. because some other apps are misbehaving and not working.
the question is can we have this app http://www.xda-developers.com/android/per-app-dpi-adjustment-for-the-galaxy-note-2/
BUT it is only available for galaxy note 2. yes a smart tablet. not a phone. can someone got this working on our devices, changing the dpi on build.prop automatically during opening an app then restarting the whole framework while opening the app.
EDIT: (someone used it on an s2 and it's working) there's still hope =')
Click to expand...
Click to collapse
Need android 4.0 +
Why editing build.prop restarts your framework?
Use apps like "lcd density " & "lcd resolution " its easier :beer:
This is Jay-z-s

Changing DPI

Coming from N5, I've played around a lot with the DPI settings, to find the perfect spot (361).
Can you also change the DPI settings on the Z2? N5 has it via editing the build.prop but don't know how Sony does this. I'm yet to receive the phone (on Tuesday) but wanna know in advance.
You can simply edit the build.props to change the dpi
Something to know about xperias is they are extremly close to AOSP with the way the firmware works
Its how xperia FWs are, they are very light
Sent from my D6503 using XDA Premium 4 mobile app
I used DPI Changer app from the play store to change mine, also allows you to backup & restore build.prop file as well
It can be a pain to find the correct DPI that doesn't cause issues with some apps, I originally changed it to 400 for a couple of weeks but that was still a bit too big, 320 was too small, 360 was fine but Tv Show Favs app layout got a bit missed up (the main screen was instead a bar on the left of the screen) Ended up settling on 370.
Oh, it's pretty much the same? Good news then!
On my N5, I use 361 due to issues that 360 causes with some apps, and hoping to do the same on soon-to-be-mine Z2, since it was the perfect spot. But if that won't work, and 370 works (as per above post), that's great! Cheers guys.
BanziBaby said:
I used DPI Changer
Click to expand...
Click to collapse
Thanks man, this works wonders!
BanziBaby said:
I used DPI Changer app from the play store to change mine, also allows you to backup & restore build.prop file as well
It can be a pain to find the correct DPI that doesn't cause issues with some apps, I originally changed it to 400 for a couple of weeks but that was still a bit too big, 320 was too small, 360 was fine but Tv Show Favs app layout got a bit missed up (the main screen was instead a bar on the left of the screen) Ended up settling on 370.
Click to expand...
Click to collapse
I'm trying to figure out why DPI Changer doesn't work for me. I also tried Texdroider, which I previously used on an LG G2 with success. Both apps appear to go through the motions, but when I apply the changes and reboot, nothing is changed.
I'm running a D6503 rooted .402, locked boot loader and I installed SuperSU from the Play Store. Running Root Checker confirms I am rooted.
I'm hoping to be able to set the DPI so it can match the look and feel of the Z Ultra
Thanks in advance for any help!
Hadn't thought of changing DPI in quite a while, actually since my Xperia Z. I'm too going to play around with DPI till I find something a bit smaller but then again not too small. I've always thought that the interface had gotten unnecessarily big after the Xperia T.
Edit: Anyone happen to notice what the original DPI value was on the Z2? I changed mine a little too quick..
If anyone likes the ZU the exact DPI is 320
For Z2 Tablet it is 140
And for default it is 480
Sent from my D6503 using XDA Premium 4 mobile app
@orbitalcomp I did have issues with SuperSU granting root to dpi changer, had to apply the new dpi twice & even then sometimes it wouldn't apply on reboot, also had issues with AdAway failing to copy & apply the new hosts file, tried using the full unroot option in SuperSU but it just stuck saying uninstalling please wait. Had to use Solid Explorer to delete the SuperSU apk file & the binary then downloaded the recovery version of clockworkmod superuser & flash that, no issues with dpi changer or AdAway or any other root apps.
Maybe it just me but I have always found SuperSU to be a bit flaky & buggy at times both on the Z2 & my old Galaxy S & Galaxy S3, never had any issues with clockworkmod superuser
I have setted DPI to 320 by editing build.prop.
Then you can apply some different DPI settings App per App using AppSettings Xposed, working great!
BanziBaby said:
@orbitalcomp I did have issues with SuperSU granting root to dpi changer, had to apply the new dpi twice & even then sometimes it wouldn't apply on reboot, also had issues with AdAway failing to copy & apply the new hosts file, tried using the full unroot option in SuperSU but it just stuck saying uninstalling please wait. Had to use Solid Explorer to delete the SuperSU apk file & the binary then downloaded the recovery version of clockworkmod superuser & flash that, no issues with dpi changer or AdAway or any other root apps.
Maybe it just me but I have always found SuperSU to be a bit flaky & buggy at times both on the Z2 & my old Galaxy S & Galaxy S3, never had any issues with clockworkmod superuser
Click to expand...
Click to collapse
Thanks for the reply, BanziBaby. Not sure if you had the same issue originally, but when installing SuperSU from the Play Store it would not update the binaries on first run. After a reboot, SuperSU would open and it was able to grant permissions to the different apps, but I guess it wasn't a full grant.
Is there anyway to install a working version of SuperSU without going through recovery? I'm assuming I have to unlock my boot loader to install a recovery, right?
sensei_sai said:
I have setted DPI to 320 by editing build.prop.
Then you can apply some different DPI settings App per App using AppSettings Xposed, working great!
Click to expand...
Click to collapse
Do the stock apps all handle the 320 dpi just like the Z Ultra, meaning there are more icons allowed on the home screen, dock, and app drawer?
I remember when I had my ZU, I was even able to install tablet apps straight from the Play Store since it apparently registered as a tablet/phone hybrid. That would be nice on the Z2 as well.
orbitalcomp said:
Thanks for the reply, BanziBaby. Not sure if you had the same issue originally, but when installing SuperSU from the Play Store it would not update the binaries on first run. After a reboot, SuperSU would open and it was able to grant permissions to the different apps, but I guess it wasn't a full grant.
Is there anyway to install a working version of SuperSU without going through recovery? I'm assuming I have to unlock my boot loader to install a recovery, right?
Do the stock apps all handle the 320 dpi just like the Z Ultra, meaning there are more icons allowed on the home screen, dock, and app drawer?
I remember when I had my ZU, I was even able to install tablet apps straight from the Play Store since it apparently registered as a tablet/phone hybrid. That would be nice on the Z2 as well.
Click to expand...
Click to collapse
When changing DPI to 320 all apps load into phablet mode (aka ZU size) and some which dont support phablet load into tablet size
In other words... No problem
Sent from my D6503 using XDA Premium 4 mobile app
I have an issue with the Xperia launcher when I change DPI..
The icons on the launcher just get smaller and smaller and unlike google now launcher it doesn't adapt to the changed DPI.
Anyone else have this? I really don't want to switch away from Sony's launcher and smaller dpi is pretty awesome on a larger screen.
lyubor said:
I have an issue with the Xperia launcher when I change DPI..
The icons on the launcher just get smaller and smaller and unlike google now launcher it doesn't adapt to the changed DPI.
Anyone else have this? I really don't want to switch away from Sony's launcher and smaller dpi is pretty awesome on a larger screen.
Click to expand...
Click to collapse
with which DPI? If I remenber well I had the same until I switched to 320 DPI, which is just perfect.
With everything I randomly tried around 400. Rebooted twice after applying 320 and it actually worked!
Ended up using the DPI Changer app, since editing the build.prop directly didn't seem to work after multiple reboots, but 361 is doing the job so far.
Success!
I was finally able to get my root and SuperSU binaries to take after some trial and error from reading the Easy Root Tool thread. Took a combination of installing the SuperSU.apk and rooting multiple times to do it.
Now I'm running 320dpi after changing the setting in DPI Changer...it looks fantastic! I always thought the Z Ultra had the best looking dpi for a smartphone, now it looks perfect on the Z2.
Couple things I noticed...the launcher now rotates to landscape, plus I'm not able to install the tablet version of Slingplayer like I could on the ZU, says it's incompatible in the Play Store. No big deal really, since the phone version works fine, I just like having the full remote of the tablet version.
Thanks to everyone for their input!
orbitalcomp said:
Success!
I was finally able to get my root and SuperSU binaries to take after some trial and error from reading the Easy Root Tool thread. Took a combination of installing the SuperSU.apk and rooting multiple times to do it.
Now I'm running 320dpi after changing the setting in DPI Changer...it looks fantastic! I always thought the Z Ultra had the best looking dpi for a smartphone, now it looks perfect on the Z2.
Couple things I noticed...the launcher now rotates to landscape, plus I'm not able to install the tablet version of Slingplayer like I could on the ZU, says it's incompatible in the Play Store. No big deal really, since the phone version works fine, I just like having the full remote of the tablet version.
Thanks to everyone for their input!
Click to expand...
Click to collapse
Can confirm that also on Z3 is 320DPI for Home launcher just amazing
Xperia Z2 dpi change
I have tried to use all application in playstore as well as build.prop editing in system but still nothing happens I'm running in marshmallow 6.0.1 with 23.5.A.1.291 build hope you could help me guys thanks
pulizpunk said:
I have tried to use all application in playstore as well as build.prop editing in system but still nothing happens I'm running in marshmallow 6.0.1 with 23.5.A.1.291 build hope you could help me guys thanks
Click to expand...
Click to collapse
You need to reboot after editing.
Sent from my Sony D6503 using XDA Labs

Categories

Resources