Good bye DPI changing? - Galaxy S6 Edge Q&A, Help & Troubleshooting

Before we could and still can change DPI for the phone but now that xposed is not working, we can't change specific apps that need original stock DPI. I hope I can live with the original DPI settings lol

---

Brava27 said:
Before we could and still can change DPI for the phone but now that xposed is not working, we can't change specific apps that need original stock DPI. I hope I can live with the original DPI settings lol
Click to expand...
Click to collapse
Have you tried changing the DPI? I tried with textdroider and despite trying a few different values it didn't change. Textdroider reported the proper value but there was no change in anything.

---

you know you have to be rooted to change dpi, right?
if you are, do it in the build prop

---

wase4711 said:
you know you have to be rooted to change dpi, right?
if you are, do it in the build prop
Click to expand...
Click to collapse
Yes I know that and changing it in the build.prop is what textdroider does. I've done it with app and manually and it doesn't change anything.

---

so, when you save the new build.prop, and you open it again, it shows that your density settings are saved?
And, then after rebooting, the old density is back in the build prop?
I wont get my phone until later today, so I cant try it now, but that's strange..

---

wase4711 said:
so, when you save the new build.prop, and you open it again, it shows that your density settings are saved?
And, then after rebooting, the old density is back in the build prop?
I wont get my phone until later today, so I cant try it now, but that's strange..
Click to expand...
Click to collapse
Yes the new value shows after manual (and after textdroider) edit and save/reboot but the screen DPI doesn't actually change. The value is shown, but the screen is the same.

---

There are actually a few different values, the one that is 400 is the one I'd been changing. I wasn't sure what the two 640 values were and haven't changed them. Never seen a build.prop with multiple values. Didn't know if maybe those two values corresponded to the left and right edge screens since there are settings for them.

---

Have you found out any more info about this setting?

---

Has anyone tried running this via adb shell:
wm density 380 (or whatever density you want)
This worked fine without root on my Xperia phone. Just curious as I am thinking about getting this phone, but not setting density is a potential dealbreaker.

---

Alright so an update, it's the first 640 value that changes the DPI. The one under #system.prop for universal7420. I changed it to 580 and the attached pic is the result. I loaded google now launcher to test the scaling and it appropriately scales itself to use the whole screen whereas TW moved itself to the top left of the display. I guess the next challenge is to make TW properly scale.

---

I noticed that last night. I wonder what the other 2 dpi settings control?

---

adb works
I have successfully changed the DPI using adb on normal S6, though Play Store now believe it to be a tablet. Also, most of touchwiz hates it, not a big deal for most things, camera may be the biggest annoyance when its only taking up the upper right 60% of the screen.

---

Has anyone sucessfully changed the per app DPI, like you can with Paranoidandroid?

---

Look for "buil prop editor" on play store!! But the kamera and keybord looks like a#$

---

Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,

---

wikidavid said:
Dears, you can easily swap de dpi with a simple app : Resolution changer.
Kind regards,
Click to expand...
Click to collapse
What are you doing? trying to pad your post count? Exact same reply in three different threads about DPI, as well as your other post in the same threads asking "dears to please not use the double post..." WTF?

---

schollianmj said:
What are you doing? trying to pad your post count? Exact same reply in three different threads about DPI, as well as your other post in the same threads asking "dears to please not use the double post..." WTF?
Click to expand...
Click to collapse
I'm just trying these things :
1) delete double post/overflow on the forum
2) give a solution anyway.
Don't be upset, there's no reason to... Have a nice day !

---

boosting1bar said:
Have you tried changing the DPI? I tried with textdroider and despite trying a few different values it didn't change. Textdroider reported the proper value but there was no change in anything.
Click to expand...
Click to collapse
I also tried the same thing with no results

---

Hi,
I changed my DPI successfully by changing the first occurrence of ro.sf.lcd_density from 640 to 540 in /system/build.prop using the built-in texteditor in root explorer (and rebooting afterwards ofcourse).
Then I noticed the camera didn't work properly anymore, so I created a fix for that (see this post).
Hope you'll get it to work, it seems the same to me as on earlier devices with as exception that the ro.sf.lcd_density occurs multiple times in the build.prop file.
Cheers,
Bane.

---

For testing different resolutions:
- have a functional adb
- enable USB debugging on device (developer options)
- connect device to your PC via USB cable. Then start a cmd in folder containing adb.exe. Type "adb devices" (without quotes) in the command prompt to check if adb recognizes the phone
- If is OK, type "adb shell wm density ZZZ" (no quotes) where "ZZZ" is the pixel density value you want to try (default is 640)
- no reboot needed, the change is on-the-fly
- check the programs (Samsung ones - dialler, calendar, camera, launcher, etc...)
- the change will disappear when you reboot your device.
per-app DPI...not; only with Xposed, when will be available.
Once you find the desired resolution it can be inserted in build.prop