Hi, I have now A5 2016, thinking about upgrade to 2017, but have one question - 2017 supports DPi change ? because 2016 no, and via ADB ( "ADB Shell wm density" from 480 to any lower caused bad Samsung apps scaling (camera, phone etc not full screen)
Devices have same resolution and both are 5,2" so I assume 2017 have 480DPI stock also. If its possible to lower it like 360 or 380 it will be great.
Unfortunately, no direct DPI scaling available (as it is still on Marshmallow). However, changing the font size to small(est) gives an excellent impression of a smaller DPI. With Nougat it will be possible, of course.
You Can Use Root Essentials But This Will Break Your System UI
Related
Hello guys,
I bought a new Wileyfox Swift and I'm really curious what dpi setting setting is the natural/standard one for a 5 " Display , especially for the wileyfox swift. It is said that the display has a natural of 296 ppi. which DPI Setting should I use in Cyanogen OS ? The standard of 320 DPI or a value near the natural ppi of the display? 300 DPI or less? I just want a setting the fit's the standard.
Does this value or setting has impact on other things or only the scale of things on screen?
Again, should the cyanogen os standard value of DPI be set near the standard PPI value of the smartphone display`?
thanks in advance for all helpful answers.
That is a neat little option.
Usually it affects the size of items which can be displayed. Depending on the apps you use, you'll find that their appearance and subtle part of functionality on the UX side will change a bit. Some layouts are available only for certain DPI settings. Play around with it and choose your favourite. With lower DPI you can get a bit more screen estate for content- text, icons, etc.
The difference between 300 vs 320 DPI is mostly unnoticeable. As you are looking for the natural look, you can leave it as either of the two. You can try with lower values as well. It is possible to have some problems here and there if you use DPI that is largely different than on the device (something like 240).
Pak0St said:
That is a neat little option.
Usually it affects the size of items which can be displayed. Depending on the apps you use, you'll find that their appearance and subtle part of functionality on the UX side will change a bit. Some layouts are available only for certain DPI settings. Play around with it and choose your favourite. With lower DPI you can get a bit more screen estate for content- text, icons, etc.
The difference between 300 vs 320 DPI is mostly unnoticeable. As you are looking for the natural look, you can leave it as either of the two. You can try with lower values as well. It is possible to have some problems here and there if you use DPI that is largely different than on the device (something like 240).
Click to expand...
Click to collapse
Thank you very much I guess I should consider a mental doctor because I'm switching from 300 to 320 and back several times a day lol. Some applications looking better with 300 but 320 looks more clear?!?
Anyway, appreciate you took your time to answer and I guess I'll keep the 300..... Or?.... Wow... Hard decision lol.
Take a look in this thread:
http://forum.xda-developers.com/xpo...2014-05-14-t2437377/post63835421#post63835421
I haven't tried this Xposed module to change the DPI on per-app basis. If you are on CyanogenMod instead of CyanogenOS, it is definitely worth a look.
Best case scenario- you won't change the DPI for the entire system and restart each time
Hi all,
I have read all the threads about DPI-changes but couldn't find a definite answer. Currently i am on firmware 1.95.401.4, build.prop says
Code:
ro.sf.lcd_density=640
(see screenshot) using Dev-Check it says dpi is 571.
I played around with DPI values a little and found that changing to a value lower than 530 the button in the camera will slide to the left, or in the screenshot downwards (see second screenshot, DPI is 471).
There are some other threads about changing DPI values which say the htc lockscreen will 'break', i did not encounter this problem, besides the button in camera i had no problems.
Long story short, my questions,
why is there the difference between those two values, what am i getting wrong?
(build.prop vs Dev-Check)
anyone encounterd other problems beside camera button by changing DPI to a value lower than 530?
if you have changed the DPI, what is your current value?
Dev Check just calculates the correct DPI for your device. But HTC just set another (higher) DPI, because then more icons can be displayed.
Might not be much use but I believe Nougat / Android 7 supports different DPI scaling (much anticipated feature!)
I want to change my DPI to lower then 530, but the camera button problem bugs me, it still appears in the latest HTC camera 8.50.917991.
Is there a workaround or different camera apk for this issue? I am not rooted and on Nougat.
Thanks
The attached image shows MobileSheetsPro running on my old Galaxy Note 10.1 (left) and on the S4 (right).
The note is 1280x800 and the S4 is 2560x1600.
I would expect the applications to look the same, but this is not the case. On the S4, the dialog is about 25% larger, the icons are larger, etc.
If you are familiar with MobileSheetsPro you can see that I needed to lower the font sizes used by the program (to about 80%) to get the same contents on the display. Other applications show similar differences.
DevCheck (see 2nd attachment) shows resolution 1280x800 and screen density 160dpi (mdpi), 1280dp x 800dp for the Note, and for the S4 resolution 2560x1600 and screen density 360dpi (xhdpi), 1138dp x 711dp. I find the red numbers puzzling.
Is this normal behaviour? Is MobileSheetsPro misbehaving? Is there some setting that can (needs) be adjusted?
'm confused about this as well. Just picked up a a new s4 for super cheap...and games are too zoomed. I used recheck and an online tool and they both show 1280 x 800. Tried changing min width in developer settings to no avail
My tablet is at home, and this isn't the behavior I remember, but i don't use Mobile Sheets, and it could be specific to software. Android does some weird treatments that are supposed to be based on resolution. The xhdpi is a clue to this. In your old tablet it was using the native resolution in determining what resources to use/scale. On the new one, it appears to behave as if it believes the dPI is higher than it really is and the resolution lower. Somebody who understands better how this works in Android will have to give a more complete answer.
Hello, I have a unit with 800x480 screen which I used to operate in a higher resolution set with Easy DPI. I was on Android 8 with the Hal9k mod. I upgraded to Android 9 (a stock HA rom) and rooted so Easy DPI can operate. Now I can change the resolution (1024x600 and 1280x720 both work) but the touch screen does not work after that (actually the bottom half is not working; I can only work on the upper half of the screen). Has anyone seen this before? Should I change anything else? I let the DPI to the default (240).
Thank you in advance,
A.
Just recently updated to stock A13 OOS (unlocked BL and rooted, LE 2125), and am wondering what the best way to change the display density system wide? The default settings are not quite small enough for my taste. Additionally, changing the smallest width setting within Developer Settings causes some undesirable outcomes; space below keyboard/home screen, weird Google Now spacing.
Also, when changing the smallest width developer setting, some elements of the system don't seem to respect that setting including lock screen date and clock, stock launcher, etc. I would prefer not to flash any custom roms as most I've tried have too many bugs.
I was wondering if there's any ADB command, magisk module, or anything I could do to make the display density smaller?
Have you played with Settings Font and Display size....
galaxys said:
Have you played with Settings Font and Display size....
Click to expand...
Click to collapse
Yes, display size is set to small, and so is font size
If it still comes out too big, i think you might have the same problem as I did. I had to factory reset after a fresh F16 install. No problems since.
You want this command:
adb shell wm density 560
Change the number until you find a density you like.