How to Change DPI of Honor 8 Without Root Using ADBFor anyone looking to experiment with the DPI settings on the Honor 8, I'll give you a quick tutorial on how to do that. You can also check out screenshots of different DPI settings to see which one you want to go with.
Before you get started it's important to know what the default DPI is so that you can revert back to that if anything goes wrong. In ADB, type the command adb shell dumpsys display and you'll see that the default density is 480.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now to change your DPI, here is the command you'll want to put into ADB.
adb shell wm density *insert density here* && adb reboot
DPI set at 200
DPI set at 300
DPI set at 400
DPI set at 500 (fail)
DPI set at 600 (fail)
Looks like you don't want to go over 500 because it causes app crashes and messes up the UI. Between 300-480 is the sweet spot.
Let me know if you get stuck or have any questions.
Thanks, but I read somewhere else that you can change the resolution from software (like the note 7)
PalakMi said:
Thanks, but I read somewhere else that you can change the resolution from software (like the note 7)
Click to expand...
Click to collapse
Yes. But it only changes the resolution to 720p which means less pixels and doesn't look good, it's more for saving battery not to reduce density(dpi) of the screen. Correct me if I'm wrong.
BudaBang said:
Yes. But it only changes the resolution to 720p which means less pixels and doesn't look good, it's more for saving battery not to reduce density(dpi) of the screen. Correct me if I'm wrong.
Click to expand...
Click to collapse
You're correct
It's a shame Huawei doesn't add the option it has on phones with 5.5 inch screens (like the Nova Plus and Honor 5X) as surely the user can decide for themselves if they'd like smaller icons etc.
I assume Nougat will add support natively?
jonmorris said:
It's a shame Huawei doesn't add the option it has on phones with 5.5 inch screens (like the Nova Plus and Honor 5X) as surely the user can decide for themselves if they'd like smaller icons etc.
I assume Nougat will add support natively?
Click to expand...
Click to collapse
I hope so
I've settled for 440. What I don't understand is that on the S7 regular zoomed UI used to be 640 and Condensed is 570, while on the Honor 8 regular is 480 but I can't quite figure out what would be the equivalent of 570 on S7. I do realize the values are probably different because of the differrent resolution screens, ie. QHD vs FHD.
Don't forget screen size
PalakMi said:
Don't forget screen size
Click to expand...
Click to collapse
just use
wm size 1920x1080 for example
RatchetPanda said:
just use
wm size 1920x1080 for example
Click to expand...
Click to collapse
I meant like 5", 5.5" etc
RatchetPanda said:
just use
wm size 1920x1080 for example
Click to expand...
Click to collapse
what would this command cause?
MaTiCeK- said:
what would this command cause?
Click to expand...
Click to collapse
Change the resolution
Thanks very much for this fantastic mod.
Just migrated from an iPhone 5s, and frankly I was pissed off that despite having a large device, instead of being able to view more content, everything on the screen was huge. Setting the dpi to 400 fixed this.
is there something i missed i tried different dpi settings 300, 320, 380, 400 but when i use my smart cover, the notification and nav bar disappears as wel as that the smartview doesnt display correctly, thx in advance
edit: played with it some more and cant go lower than 420 (i tink its a sign ) but anytthing below that just makes the smartview not workeble and de nav bar disappears
On EMUI 5 it's possible to set the DPI from the phone settings (that's an android 7 feature actually).
I got used to DPI 420 on my nexus 5X, after changing honor 8 to the same, I feel right at home!
DrGreenway said:
How to Change DPI of Honor 8 Without Root Using ADBFor anyone looking to experiment with the DPI settings on the Honor 8, I'll give you a quick tutorial on how to do that. You can also check out screenshots of different DPI settings to see which one you want to go with.
Before you get started it's important to know what the default DPI is so that you can revert back to that if anything goes wrong. In ADB, type the command adb shell dumpsys display and you'll see that the default density is 480.
View attachment 3877074
Now to change your DPI, here is the command you'll want to put into ADB.
adb shell wm density *insert density here* && adb reboot
DPI set at 200
View attachment 3877078View attachment 3877079View attachment 3877080
DPI set at 300
View attachment 3877082View attachment 3877083View attachment 3877084
DPI set at 400
View attachment 3877086View attachment 3877087View attachment 3877088
DPI set at 500 (fail)
View attachment 3877092
DPI set at 600 (fail)
View attachment 3877093
Looks like you don't want to go over 500 because it causes app crashes and messes up the UI. Between 300-480 is the sweet spot.
Let me know if you get stuck or have any questions.
Click to expand...
Click to collapse
When I do this the navigation area stays large but the buttons shrink. What am I doing wrong
I see an option under Developer Options > Drawing > Smallest width . It was preset to 360, I changed it to 400(or whatever dpi you want to ).
Just wanted to share. I don't know if this is the correct way to set dpi, but my screen density sure reduced.
Edit : It doesn't set dpi , it sets dp(density independent pixel) . I found a formula on the Android documentation : https://developer.android.com/guide/practices/screens_support.html
It says px = dp*(dpi/160)
Px is the no. Of physical pixels (relates to the resolution of the screen which is fixed )
Dp is the virtual pixel unit which can be set in the developer options (smallest width)
Dpi is the screen density .
yalokiy said:
On EMUI 5 it's possible to set the DPI from the phone settings (that's an android 7 feature actually).
I got used to DPI 420 on my nexus 5X, after changing honor 8 to the same, I feel right at home!
View attachment 4000993
Click to expand...
Click to collapse
Great tip (and yes, I hit the Thanks Button), but I still have a question:
I just got my Honor 8 this weekend. The screen is great, and with the above I can easily customize the overall appearance.
The only problem is that as soon as I got the phone up and running, I noticed that the home screen icons (particular look really large and "cartoonish" for a phone with a relatively high resolution screen.
I realize the look is part of EMUI 5.
Adjusting this seems to help the size, but it has more of an effect on everything else than on the icons (actually homescreen, dock and app tray). I set the home screen to 5x5, which also helps, but the dock and app tray still look really big.
Is there anything else I can do to set the size of the icons in the tray or the dock?
Linuxslate said:
Great tip (and yes, I hit the Thanks Button), but I still have a question:
I just got my Honor 8 this weekend. The screen is great, and with the above I can easily customize the overall appearance.
The only problem is that as soon as I got the phone up and running, I noticed that the home screen icons (particular look really large and "cartoonish" for a phone with a relatively high resolution screen.
I realize the look is part of EMUI 5.
Adjusting this seems to help the size, but it has more of an effect on everything else than on the icons (actually homescreen, dock and app tray). I set the home screen to 5x5, which also helps, but the dock and app tray still look really big.
Is there anything else I can do to set the size of the icons in the tray or the dock?
Click to expand...
Click to collapse
Try changing the theme . That usually changes the style (and sometimes) the size of icons .
Thanks! Tried this today on my Honor 8, works like a charm with DPI 420.
Related
I've pulled this together from multiple sources, all will be acknowledged and linked to.
Basically, I've figured out how to setup a better DPI for lapdock use. Razr HD is 320DPI by default, and so far only 240dpi works for me. Home pages are still only displaying 4x4 grid, you'd have to change your grid settings through a replacement launcher.
Script credit goes to Dadooms, from this post: http://forum.xda-developers.com/showpost.php?p=34065014&postcount=88, his is credited to others in the same thread.
I've only modified the DPI settings from it.
Code:
#!/system/bin/sh
initdensity=320
tabletdensity=240
density=`getprop qemu.sf.lcd_density`
echo $density
if [ $density -eq $initdensity ]
then
echo "tablet"
setprop qemu.sf.lcd_density $tabletdensity
else
echo "telephone"
setprop qemu.sf.lcd_density $initdensity
fi
stop
sleep 1
start
You must be rooted for this to work! Root instructions here: http://forum.xda-developers.com/showthread.php?t=1943845
Next, install SManager and SMWidgets (only if you want to make a toggle widget for the script)
Create a file called TabletMode in /data directory, and paste the code from above into it.
Open TabletMode in SManager, select SU for superuser(root) access, and run. Your phone will quick-reboot and will come back in 240DPI with smaller icons and text. To clear the settings, run the script again, or just reboot the phone normally.
thanks for the post. any chance of getting some pics?
this is a good step towards making the lapdock useful again.
great, thank you! the only missing thing now is the native resolution, instead of hd mirroring.
but a great step into the right direction
Pics, as requested. Before and After with similar icons, same background. The circles widget behaves weirdly, not sure why.
Phone boots up at 120dpi, looks like tablet mode is enabled, but system ui crashes so softkeys and the dock doesn't load. I'm going to keep trying dpi settings to see if I can find one that'll boot into tablet mode properly. 120dpi DOES alter the icon grid to 6x8 I believe from 4x4, and it clears all the pages, so you can maintain your "phone" icon/widget layout and save your "lapdock" icon/widget layout separately.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some progress. While the stock launcher seems to throw a fit if the DPI is set to anything other than 240 or 320, Apex Launcher works just fine with 200. Here's some screenshots for you to look at. Settings: Autorotate on, icons 7 rows 10 columns.
I'm thinking of setting up Apex for Lapdock only mode once I get mine, and keep the stock launcher for phone mode. To change modes, I just swap launchers, then run the batch file.
I spent some time to figure out another improvments, using the razr hd with the lapdock:
- using apex launcher, you can disable the status bar using a widget -> gives some more space on the home screen
- apex also supports a "tablet ui" for more tablet ui feel. As it won't affect the system dpi, it's worth a try but not comparable with 240dpi build.prop setting
- "hide bottom bar" (available at play) is compatible with razr hd (root needed!). It is hiding the softkeys and also disables the status bar. This gives nearly the native
resolution of the lapdock and is really great for browsing and office At least for me, a major advance.
Have fun
EdwardN said:
Some progress. While the stock launcher seems to throw a fit if the DPI is set to anything other than 240 or 320, Apex Launcher works just fine with 200. Here's some screenshots for you to look at. Settings: Autorotate on, icons 7 rows 10 columns.
I'm thinking of setting up Apex for Lapdock only mode once I get mine, and keep the stock launcher for phone mode. To change modes, I just swap launchers, then run the batch file.
Click to expand...
Click to collapse
When i change the dpi to 200 via your script I still have pretty large black bars on top and bottom of my lapdock screen and the picture seems to be stretched though im not positive of this. Changing the dpi really only seems to change the size of the icons. Am I doing something wrong? It would be so so cool to have this replace my netbook but as it stands its going to remain unused.
JBmfG said:
When i change the dpi to 200 via your script I still have pretty large black bars on top and bottom of my lapdock screen and the picture seems to be stretched though im not positive of this. Changing the dpi really only seems to change the size of the icons. Am I doing something wrong? It would be so so cool to have this replace my netbook but as it stands its going to remain unused.
Click to expand...
Click to collapse
Try playing with the HDMI overscan settings. Display > Overscan. I read that someone else had it set to center of the bar for a decent display.
The lapdock is 1366x768, I believe, vs the phone's native resolution of 1280x720. Overscan should be able to adjust for the difference.
EdwardN said:
Try playing with the HDMI overscan settings. Display > Overscan. I read that someone else had it set to center of the bar for a decent display.
The lapdock is 1366x768, I believe, vs the phone's native resolution of 1280x720. Overscan should be able to adjust for the difference.
Click to expand...
Click to collapse
Thanks Edward. I thought i had already tried that and didnt see any overscan option in the display section but I will try again when i get home to my lapdock.
Yes, just as i thought. When i plug in my razr to my lapdock i have no hdmi settings available in the display section. I have brightness, wallpaper, auto-rotate screen, sleep, Font size, Roaming banner. Im on the leaked JB, not sure if that matters. I tried googling for a solution but didnt find much.
JBmfG said:
Yes, just as i thought. When i plug in my razr to my lapdock i have no hdmi settings available in the display section. I have brightness, wallpaper, auto-rotate screen, sleep, Font size, Roaming banner. Im on the leaked JB, not sure if that matters. I tried googling for a solution but didnt find much.
Click to expand...
Click to collapse
I don't have my Razr HD on JB yet. I'm waiting for either the Rogers JB release or the Cyanogen10 to mature a little more before trying it. Overscan IS an option in ICS.
EdwardN said:
I don't have my Razr HD on JB yet. I'm waiting for either the Rogers JB release or the Cyanogen10 to mature a little more before trying it. Overscan IS an option in ICS.
Click to expand...
Click to collapse
Yeah, hdmi is messed up in the Jelly Bean leaks. There is no overscan option. I am really having a hard time believing the newest leak 9.1.41 is actually going to be the official since it is missing such a key feature. Kind of pissing me off actually.
coolestmage said:
Yeah, hdmi is messed up in the Jelly Bean leaks. There is no overscan option. I am really having a hard time believing the newest leak 9.1.41 is actually going to be the official since it is missing such a key feature. Kind of pissing me off actually.
Click to expand...
Click to collapse
Sadly it appears to be the case even in the final versions, 4.1 for motorola means half-assed hdmi support, worse than 4.0
I suggest you to write to them! I did too.
I saw that ubuntu for android was released yesterday. Havent read up on it much yet but maybe this would be a way to make the lapdocks useful?
JBmfG said:
I saw that ubuntu for android was released yesterday. Havent read up on it much yet but maybe this would be a way to make the lapdocks useful?
Click to expand...
Click to collapse
Possibly. I'd prefer to have android still be the OS though, just for app convenience. I did manage to run ubuntu gui on my razrhd through a VNC window but it was slow as hell, so I terfed it.
In order to get my atrix lapdock working with my RAZR HD XT925 JB, i tried the solution suggested here.
But it didn't really fix the problem. The two black bars above and below the displayed area on the lapdock stayed there. The overscan option did completely disappear in 4.1.2 as already said here. This is quite frustrating.
Is there any other possibility to do an overscan, e.g. per build.prop?
It would be really nice, getting the (atrix) lapdock useable/working with jellybean!
andreas5232 said:
In order to get my atrix lapdock working with my RAZR HD XT925 JB, i tried the solution suggested here.
But it didn't really fix the problem. The two black bars above and below the displayed area on the lapdock stayed there. The overscan option did completely disappear in 4.1.2 as already said here. This is quite frustrating.
Is there any other possibility to do an overscan, e.g. per build.prop?
It would be really nice, getting the (atrix) lapdock useable/working with jellybean!
Click to expand...
Click to collapse
You are on 4.1.2 and changing the dpi with the script here affected your hdmi out resolution? That is further than I can get. I get ****ty 480 since 4.1.2. I have tried other roms and the only one different is CM10 which displays sideways so that is a huge deprovement.
Lack of support for lapdock is infuriating. With VPN and RDP I was able to leave my laptop at home most days.
gsdev said:
You are on 4.1.2 and changing the dpi with the script here affected your hdmi out resolution? That is further than I can get. I get ****ty 480 since 4.1.2. I have tried other roms and the only one different is CM10 which displays sideways so that is a huge deprovement.
Lack of support for lapdock is infuriating. With VPN and RDP I was able to leave my laptop at home most days.
Click to expand...
Click to collapse
I am angry about lapdock not working well. Can we all do something about it? HDMI as a whole isn't working well either. This is the Razr HD and it's advertised for having HDMI. But since jelly bean it's not working as it should.
Let's try fixing lapdock first, though. I really want to use it. Maybe webtop won't work, but there might be alternatives, right?
mtvdeo said:
I am angry about lapdock not working well. Can we all do something about it? HDMI as a whole isn't working well either. This is the Razr HD and it's advertised for having HDMI. But since jelly bean it's not working as it should.
Let's try fixing lapdock first, though. I really want to use it. Maybe webtop won't work, but there might be alternatives, right?
Click to expand...
Click to collapse
The solution might be to return to ICS, unfortunately. I don't know enough about how the hdmi works to really make any progress that way. There IS an app in market called Tablet Mode for samsung, but it does work to change the dpi setting without too much effort. HOWEVER. You must use a replacement launcher to use it, if you set the dpi to 192 it will cause constant forceclose of the stock launcher. You also need root. So far I've only tested it with ICS, and since I reinstalled jelly bean from full I don't have root to test it.
EdwardN said:
The solution might be to return to ICS, unfortunately. I don't know enough about how the hdmi works to really make any progress that way. There IS an app in market called Tablet Mode for samsung, but it does work to change the dpi setting without too much effort. HOWEVER. You must use a replacement launcher to use it, if you set the dpi to 192 it will cause constant forceclose of the stock launcher. You also need root. So far I've only tested it with ICS, and since I reinstalled jelly bean from full I don't have root to test it.
Click to expand...
Click to collapse
Whenever i've messed with the DPI it just looks like it makes everything smaller on the same portion of the screen. Until overscan is working i dont think there is anything to be done.
I used ROM toolbox and xposed to modify the DPI on my phone. The systemwide build.prop setting is 320 with a few apps manually adjusted to be the native 480. My issue is that the S-view cover window has now correspondingly shrunken, but I can't identify an app in xposed that looks to drive the S-view window. Does anyone know if this is a standalone apk or perhaps built in with another apk I can adjust. I don't want to lose my 320 DPI on the lock screen, status bar, notification bar, etc. but would ideally increase the S-view window back up to 480.
Thanks in advance for any info!
Sent from my SM-N900V using Tapatalk
bball840 said:
I used ROM toolbox and xposed to modify the DPI on my phone. The systemwide build.prop setting is 320 with a few apps manually adjusted to be the native 480.
Click to expand...
Click to collapse
Did you do the system wide 320 with ROM toolbox? Which apps did you feel like you had to restore to 480? Was it just because of looks or was it affecting functionality in some apps?
I really like 320 and did use ROM Toolbox to apply it to the build.prop. I ran my Note 2 between 220 and 240, and 320 on the Note 3 is pretty similar. Most apps work well, but I put the camera back to 480 using Xposed because the text for some of the menu options was overlapping at 320. Also, I'm using the AOSP browser for quick control capabilities and prefer those to be a little larger than 320 so bumped it up to around 400.
Sent from my SM-N900V using Tapatalk
Darn... If I set it to 320 I get that stupid weather widget on my lock screen... any way to get rid of that?
b00mb00mchuck said:
Darn... If I set it to 320 I get that stupid weather widget on my lock screen... any way to get rid of that?
Click to expand...
Click to collapse
My gear bypasses the lock screen, so I don't have a weather widget issue. I think I saw a thread by someone else asking about that question, though, so you may want to do a quick forum search.
b00mb00mchuck said:
Darn... If I set it to 320 I get that stupid weather widget on my lock screen... any way to get rid of that?
Click to expand...
Click to collapse
That was exact same thing I ran into. Nothing I froze fixed it. In the end I switched lockscreen to pin version and all is well.
Sent from my SM-N900V using Tapatalk 2
As FYI to anyone else with my original question, it sounds like the S-view cover code is embedded in the android package and thus not accessible by Xposed App Settings. So, if it is even possible to fix the issue, it is way above my head. My workaround, which gets pretty close to a solution but is a major pain, is to leave the system DPI alone at 480 in the build.prop but to then manually change most of the apps I use to be around 320. This scales the apps nicely, and I then shrunk what I could in Nova to size my home screen to my liking and then used Xposed Status Bar Mods GE to clean up the excess size in the status and navigation bars. Perhaps someday someone a lot smarter than me will come up with mods for the actual s-view window size and maybe even additional functionality additions!
Sent from my SM-N900V using Tapatalk
Subscribing for a solution. I would LOVE to figure this out as well.
bball840 said:
As FYI to anyone else with my original question, it sounds like the S-view cover code is embedded in the android package and thus not accessible by Xposed App Settings. So, if it is even possible to fix the issue, it is way above my head. My workaround, which gets pretty close to a solution but is a major pain, is to leave the system DPI alone at 480 in the build.prop but to then manually change most of the apps I use to be around 320. This scales the apps nicely, and I then shrunk what I could in Nova to size my home screen to my liking and then used Xposed Status Bar Mods GE to clean up the excess size in the status and navigation bars. Perhaps someday someone a lot smarter than me will come up with mods for the actual s-view window size and maybe even additional functionality additions!
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I used the same method, but it requires many changes within App Settings.
A solution to force 480 DPI for the S View lockscreen would be great !
+1, been looking like an animal for a solution.
subcribe to thread!
need s-cover window in 320dpi
It's probably packed with system ui and see it tgat changes it.
Sent from my SM-N900V using xda app-developers app
Hi Guys, i have a Galaxy Note 3 (SM-N9005) from Germany.
My S-View Cover is in delivery Status so i cannot test it but i have following find out:
The S_View File (XML, Smali and so on) are in the com.android.setings.
I have changed my DPI to 320 via buildprop and i use the app "Appsettings" to change the DPI on many Apps (eg. Phonecontacts)
When i change "com.android.settings" to original DPI the Systemsettings from Samsung are in this DPI.
I think its the Control of S-View Window.
You can test it.
I will test it when i have my S-View Cover
Hope that helps anybody
Sorry for my english
PS. The Notification Pulldown is still in 320 DPI
I found a new app in the battery usage list after buying a s view cover. GlanceViewmk
Maybe that has something to do with the s view window?
I am using the sprint version of the note 3, but I am looking for a similar solution to the dpi for the S-View Window. As a test to the theory below, I used Appsettings to change the dpi of com.android.settings to 320 since I am using the default dpi and it did change the dpi for the settings app, but did not make a difference to the dpi of the S-View Window. Hopefully we'll get this figured out soon.
dj alex z said:
Hi Guys, i have a Galaxy Note 3 (SM-N9005) from Germany.
My S-View Cover is in delivery Status so i cannot test it but i have following find out:
The S_View File (XML, Smali and so on) are in the com.android.setings.
I have changed my DPI to 320 via buildprop and i use the app "Appsettings" to change the DPI on many Apps (eg. Phonecontacts)
When i change "com.android.settings" to original DPI the Systemsettings from Samsung are in this DPI.
I think its the Control of S-View Window.
You can test it.
I will test it when i have my S-View Cover
Hope that helps anybody
Sorry for my english
PS. The Notification Pulldown is still in 320 DPI
Click to expand...
Click to collapse
i have my whole system at 360 dpi... install per app dpixposed and search for sview and set that to 480... that fixes the main screen the pain ins fixing the camera and action note... if u do the same thing with them it sort of fixes it but gets jacked up in other ways.. o also need to set phone app to 480 and that somewhat fixes it... u will see what i mean by somewhat when u try.. but its still better than it was....
benji667 said:
i have my whole system at 360 dpi... install per app dpixposed and search for sview and set that to 480... that fixes the main screen the pain ins fixing the camera and action note... if u do the same thing with them it sort of fixes it but gets jacked up in other ways.. o also need to set phone app to 480 and that somewhat fixes it... u will see what i mean by somewhat when u try.. but its still better than it was....
Click to expand...
Click to collapse
Can you elaborate? Is the app called "dpixposed" ? I've searched the xposed framework modules area in the app for "dpi" and do not see a module by that name. I have the "App Settings" xposed module installed, which allows users to tinker with dpi on a per-app basis, but "sview" doesn't turn up any results.
Maybe we can help you fix the other problems you're having, too? Can you elaborate on those? Screenshots, maybe?
Please give us more info, like a step by step with links to where we can download any required apps/modules/etc. Thanks!
DrPhant0m said:
Can you elaborate? Is the app called "dpixposed" ? I've searched the xposed framework modules area in the app for "dpi" and do not see a module by that name. I have the "App Settings" xposed module installed, which allows users to tinker with dpi on a per-app basis, but "sview" doesn't turn up any results.
Maybe we can help you fix the other problems you're having, too? Can you elaborate on those? Screenshots, maybe?
Please give us more info, like a step by step with links to where we can download any required apps/modules/etc. Thanks!
Click to expand...
Click to collapse
My bad app settings is what I was talking about
benji667 said:
My bad app settings is what I was talking about
Click to expand...
Click to collapse
Cool... so, what did you search for to change the DPI of the S-View window? Many have tried... none have succeeded.
DrPhant0m said:
Cool... so, what did you search for to change the DPI of the S-View window? Many have tried... none have succeeded.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
u have to restart your phone after too
originally for KITKAT roms only. Settings should work fine on lollipop.
OK, so I love changing the DPI of my phone and apps. so i thought why not share what I know with others.
These are the apps that I feel are needed to be changed , so if you think i missed one just tell me and I'll add it.
another note i don't use the touchwiz launcher and different roms can use one that's modded.
of course your phone needs to be ROOTED
you can use whatever app you like to change your DPI, I used xposed app settings and would suggest the same
NOTE 4 default DPI is 640
In xposed app settings to change your system DPI you turn on
android system & system ui
and change it to your desired DPI (320 for me).
(you can also change it using the build.prop)
I guess its necessary to say this:
IF YOU CHANGE YOUR DPI IN ANY WAY, DO AS STATED BELOW
These apps you will need to change back to stock: 640
camera
camera test
com.sec.android.gallery3d.panorama360view
com.sec.android.ofviewer
com.sec.android.sviewcover
com.sec.phone
contacts
gallery
incallui
com.android.mms
phone
photo studio
s health
samsung camera filter
touchwiz home
video trimmer
not changing some can cause it to not function properly or FC
These setting are recommended if you use them:
S-Voice
- you don't have to change the dpi to stock unless you want to but if you get a FC change the screen dp to 480x854
Samsung Keyboard
- you can leave it the same as your new DPI or change it to stock DPI if the secondary icons alignment bothers you, check the box 'apply res to widgets',
Lockscreen (com.android.keyguard)
- you don't have to change this one back to stock but if you use lockscreen security the bottom will look weird
- to change it to stock, enter the stock DPI (640) and check the box 'apply res to widgets'. A reboot will be requried
Smart Remote
-change dpi back to stock and change screen dp to 320x480
Calendar
-if you use it I recommend you change it back to stock because the on screen notification size will be off
Wink app
-it will think your using a tablet and causes issues so change to stock
Swiftkey
-resize using keyboards builtin resizer
PLEASE DON'T FORGET TO HIT SAVE ON EACH ONE AND REBOOT YOUR PHONE AFTER
IF I MISSED ANYTHING OR YOU WANT ANYTHING ADDED PLEASE TELL ME
THIS ARE MY PERSONAL SETTINGS AND IF YOU CHOOSE TO DO THE SAME ITS AT YOU OWN FREE WILL
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey, thanks for the expansive list! I wanted to do something with the DPI as well but I didn't know what it would look like.
Would you mind sharing some screenshots of your modified UI. Just want to get a good idea of what it looks like before I jump in. :laugh:
xfachx said:
Hey, thanks for the expansive list! I wanted to do something with the DPI as well but I didn't know what it would look like.
Would you mind sharing some screenshots of your modified UI. Just want to get a good idea of what it looks like before I jump in. :laugh:
Click to expand...
Click to collapse
sure just give me a bit I am actually at work lol. I will try to do a before and after.
my launcher is google now btw and i should probably turn off my wanam too lol
Any idea what to change so that the fingerprint scanner stuff on the lockscreen lines up properly? At 540 the text and the arrow are moved over to the left. I haven't been able to find the magic setting.
xfachx said:
Hey, thanks for the expansive list! I wanted to do something with the DPI as well but I didn't know what it would look like.
Would you mind sharing some screenshots of your modified UI. Just want to get a good idea of what it looks like before I jump in. :laugh:
Click to expand...
Click to collapse
images uploaded
abn.geek said:
Any idea what to change so that the fingerprint scanner stuff on the lockscreen lines up properly? At 540 the text and the arrow are moved over to the left. I haven't been able to find the magic setting.
Click to expand...
Click to collapse
i addressed that. if you use the fingerprint scanner and change its DPI it wont line up. you either have to live with it or change it to stock
Thank you for the visual comparisons! Definitely gonna play with it for sure. I feel that the UI elements are just too large and its confusing since its a large phone with higher resolution! Appreciate the screenshots!
kendonsh said:
images uploaded
i addressed that. if you use the fingerprint scanner and change its DPI it wont line up. you either have to live with it or change it to stock
Click to expand...
Click to collapse
Man I don't know why it doesn't work for you - see my fingerprint lockscreen attached - build.prop is set to 480 and modifying keyguard worked for me (setting via appsettings to 640 and apply res to widgets checked and then full reboot). This was when I was setting up my phone so I did clear cache and dalvik cache in TWRP at some point, though I'm pretty sure this worked before doing that.
dawheat said:
Man I don't know why it doesn't work for you - see my fingerprint lockscreen attached - build.prop is set to 480 and modifying keyguard worked for me (setting via appsettings to 640 and apply res to widgets checked and then full reboot). This was when I was setting up my phone so I did clear cache and dalvik cache in TWRP at some point, though I'm pretty sure this worked before doing that.
Click to expand...
Click to collapse
That's what I said. You have to change keyguard back to stock (640) or it won't line up. I showed examples in the first post. Lol
Sent from my SM-N910T using XDA Premium 4 mobile app
kendonsh said:
That's what I said. You have to change keyguard back to stock (640) or it won't line up. I showed examples in the first post. Lol
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My bad - the way you phrased your response to that guy was a bit unclear.
dawheat said:
My bad - the way you phrased your response to that guy was a bit unclear.
Click to expand...
Click to collapse
all is good
what is your screen resolution?? full hd 1080 ??
i use other app , set to full hd , 401 dpi , all things look normal , except camera (the left and bottom side have black screen)
a_tumiwa said:
what is your screen resolution?? full hd 1080 ??
i use other app , set to full hd , 401 dpi , all things look normal , except camera (the left and bottom side have black screen)
Click to expand...
Click to collapse
Did you even read the first post? I even added pictures
Sent from my SM-N910T using XDA Premium 4 mobile app
thanks~ Was wondering why the incall pop up wasn't lined, i wasn't thinking to search for "incall" lmao
kendonsh said:
Did you even read the first post? I even added pictures
Sent from my SM-N910T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i read it and view your images, but i didnt find u mention the resolution in width x height , only dpi
a_tumiwa said:
i read it and view your images, but i didnt find u mention the resolution in width x height , only dpi
Click to expand...
Click to collapse
Well you ended up changing your DPI from the default 640 so you must correct the apps I listed. Thats why your camera doesn't look right.
Cuz notice you said your DPI changed to 401 hense a change in DPI
Sent from my SM-N910T using XDA Premium 4 mobile app
I have been changing DPI for my android phones since the first Galaxy One. I changed to an iPhone and now back to Galaxy Note 4. I really don't get why the screen elements are so big which render a big screen useless unless you have sight issues. They should at least give us options to do this officially instead of having to fiddle with rooting>exposed framework>changing dpi>setting each app up or even having to find specially sized apk files.
Come on Samsung! Is there a way to fix the S Health Pedo Widget after changing the DPI?
Thanks for the guide :good:
Amazing guide! Thanks for this :highfive:
Hey kendonsh. I implemented all your DPI changes (at 480) and really loving it. Can you please point me in the right direction how to fix these two minor issues - see screenshots:
1. Meeting notification from calendar is not centred
2. When I add a frame to a photo it appears broken and too small
this one isnt working when setting it back to 640.. (com.sec.android.sviewcover) when i close my sview case Im only seeing have the image buttom half is black out where sliders are...
Any suggestions??
quantumtraveler said:
Hey kendonsh. I implemented all your DPI changes (at 480) and really loving it. Can you please point me in the right direction how to fix these two minor issues - see screenshots:
1. Meeting notification from calendar is not centred
2. When I add a frame to a photo it appears broken and too small
Click to expand...
Click to collapse
1. I forgot about that one you have to change calender back to stock sadly enough
2. I am not having that issue, I'll attach a screenshot. I have been editing my settings this past week since I had a rom update. I'll double check the setting difference and let you know
Make use of that super saturated 2k panel!
1. Download the Android SDK
2. Extract it to a desired location
3. Navigate through the extraction to SDK > Platform Tools
4. SHIFT+RIGHT CLICK anywhere inside this folder and click "open command window here"
6. Make sure you have the correct drivers for your phone
5. Turn on USB Debugging and plug your phone into the computer
6. Tell your phone to trust the computer
7. In the command window, run the following command but replace *** with the desired DPI (I use 540)
Adb shell wm density ***
8. Reboot phone to have changes fully take effect.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is wonderful news. Do you know what the stock DPI was?
isosunrise said:
This is wonderful news. Do you know what the stock DPI was?
Click to expand...
Click to collapse
Tis 640
PizzaSauce said:
Tis 640
Click to expand...
Click to collapse
Isn't 640 DPI better than 540? What do you gain from changing it to less dots per inch? Bit of a n00b since I always left displays stock on phones.
will.bates94 said:
Isn't 640 DPI better than 540? What do you gain from changing it to less dots per inch? Bit of a n00b since I always left displays stock on phones.
Click to expand...
Click to collapse
It changes the dots per inch.
The benefit is you can fit way more stuff on the screen and force apps into tablet mode on a non tablet device.
E. G. Dpi is 640 and the dialer may display 5 contacts. You change the DPI to 540 and it may display 7-8 on the same screen. It is almost necessary with a phone this big unless you have bad eye site because the phone utilizes the screen real estate so badly in Stock dpis
will.bates94 said:
Isn't 640 DPI better than 540? What do you gain from changing it to less dots per inch? Bit of a n00b since I always left displays stock on phones.
Click to expand...
Click to collapse
The setting determines what size the phone will make elements on the screen.
If the DPI setting is low like that, the device thinks it's a tablet and will scale things smaller for the bigger screen.
The device knows the screen's resolution. The device needs a setting to scale screen elements to a good size for the size of the screen.
So lower DPI effectively tricks the phone into thinking the screen is bigger than 5.7" and scales elements smaller for the bigger screen.
kimdoocheol said:
It changes the dots per inch.
The benefit is you can fit way more stuff on the screen and force apps into tablet mode on a non tablet device.
E. G. Dpi is 640 and the dialer may display 5 contacts. You change the DPI to 540 and it may display 7-8 on the same screen. It is almost necessary with a phone this big unless you have bad eye site because the phone utilizes the screen real estate so badly in Stock dpis
Click to expand...
Click to collapse
I SEE what you are saying! I was thinking we were reducing the amount of dots or pixels that will be used in the display, overall changing the resolution! Thanks for clearing that up bruh.
@PizzaSauce thanks man, this cleared up a lot. Thank god you made this happen, first time with a note and it felt like I was on a Playskool phone from fisher price.
will.bates94 said:
I SEE what you are saying! I was thinking we were reducing the amount of dots or pixels that will be used in the display, overall changing the resolution! Thanks for clearing that up bruh.
Click to expand...
Click to collapse
Yeah, you got it. If root ever comes out definitely get xposed framework and app settings which allows individual dpi settings for apps. I'm guessing this workaround does it on everything, which is still really cool cause the only way I know to do it manually is by editing the build.prop. Similar to how you can add capacitive buttons
Dialer app is missing logo and things seem odd. Can't add anymore apps to the screen, everything is just more smushed together. Running ART should I wipe cache via SDK?
Nothing is lined up either.
will.bates94 said:
Dialer app is missing logo and things seem odd. Can't add anymore apps to the screen, everything is just more smushed together. Running ART should I wipe cache via SDK?
Nothing is lined up either.
Click to expand...
Click to collapse
I noticed the stock dialer thing too. Ended up using a different dialer app; ExDialer w/ Android L theme
I don't know about not being able to add apps, I use Nova launcher though.
Not sure about the ART thing, I'm on Dalvik myself
Does this chance persist through reboots?
Just a heads up, the stock samsung apps bug out when you change the DPI. They are still usuable but for instance the dialer and camera apps no longer use the entire screen.
Dan1909 said:
Does this chance persist through reboots?
Click to expand...
Click to collapse
It will persist until you manually change it or do a factory reset
bobbarker2 said:
Just a heads up, the stock samsung apps bug out when you change the DPI. They are still usuable but for instance the dialer and camera apps no longer use the entire screen.
Click to expand...
Click to collapse
If a lower DPI setting is more important than using stock apps, there's a lot of great replacements out there.
If not, you're better off waiting for root and Xposed
AWESOME!!! Everything looks so much better now. The camera and phone thing is a bit annoying, but worth it to have everything else look so good. Thank you
Thank you, this was one of the only things i missed about my rooted Note 3.
Main reason for missing root on this phone. Thank you so much for sharing this information!
One of the four things I wanted root for
Thank you so much!
The dialer doesn't bother me in the least, but does any one know how to change the default camera (it is not in the default app settings) I found a great alternative, DSLR Camera, but I can't set it to be the default camera on the lock screen.
Thanks again!
Thanks! The size of this phone is pretty useless without this. The stock apps look weird but still work fine.
Can you post some pics of the stock apps? I ran like a 300DPI on my N3 and would like to see how the stock apps look when changed.
Sent from my SM-N910V using XDA Free mobile app
Hi all,
Many of you are struggling with frequent launcher redraw issue, and me too. So I try to find out why.
That is likely cause by few reasons, including CPU power limitation (not able to handle 320ppi density screen) or not enough memory for loading high resolution assets.
Founding:
Given that Nvidia Shield Tablet, which has a similar CPU and memory volume with Nexus 9, but have a 283ppi screen.
Difference screen density may be the key to their different performances.
Android system will load hdpi instead of xhdpi assets when screen desnity is between 240 and 320.
Since hdpi assets have lower memory footprint than xhdpi assets, which the system can have more free memory for other application to run, and hence reduces the chances of redraw due to insufficiency memory.
Trade off:
Screen resolution (1536 * 2048)
Relationship between px, dp and dpi:
px = dp * (dpi / 160)
Under factory density value (dpi = 320) You have 768dp * 1024dp as logical resolution
Under a smaller density value, for example dpi = 240
You have 1024dp * 1365.3dp as logical resolution
Under a larger density value, for example dpi = 400
You have 614.4 * 819.2dp as logical resolution
Since most of the thing(text, image assets) in android are measured in dp.
TL;DR:
Lower density value > more logical resolution (dp) > "smaller and more blur text and icons" and "more working space"
Higher density value > lesser logical resolution (dp) > "larger and clearer text and icons" and "lesser working space"
For your information:
Native ppi of nexus 9 screen is 288(obtained from this formula: sqrt(1536^2 + 2048^2) / 8.9 =~287.64 )
Member @GiantAxe suggest that 316 is a good number
And I believe that any number between 280 and 319 is good. (I found it is wrong, see the update below)
Steps:
* No root access is required. Stock Rom is good to go.
1. Enable debug mode on your device.
2. On your pc/mac, switch to your adb folder.
3. adb shell wm density 316
4. Restart your Tablet and try.
Restore to origin setting:
Replace the command at step 3 with
adb shell wm density reset
Let me know if this helps!
Thanks!
[2015-10-26 update]
I am wrong!
My hypothesis on using 316 density to force Nexus 9 to load hdpi assets seems wrong.
After performing several experiments on my Nexus 9, I compose the following tables:
Code:
Official Density | Actual Density Range | Assets Resolution
120 <=131 LDPI
160 132 - 181 MDPI
240 182 - 263 HDPI
320 264 - 363 XHDPI
480 364 - 526 XXHDPI
640 >=527 XXXHDPI
I write a small program to test, you can find and compile on your own here:
https://github.com/studenttwok/DPIReader
So, I set finally set my DPI to 260, in order to force Nexus 9 to load the HDPI assets instead of XXHDPI assets.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usually the free ram from 620MB to 720 MB, in my case.
And to reply, the performance of Nexus 9 will not increase, but the chances of application redrawn due to low memory will decrease, so you can spend less time on waiting GC and redraw to finish.
Sent from my Nexus 9 using XDA Free mobile app
Maybe this is why I've never had an issue I always run at the actual screen DPI of 288.
studenttwok said:
Hi all,
That is likely cause by few reasons, including CPU power limitation (not able to handle such 320ppi density screen) and not enough memory for loading high resolution assets.
Given that Nvidia Shield Tablet, which has a similar CPU and memory volume with Nexus 9, only have a 283ppi screen. Difference screen density may be the key to their different performances.
Click to expand...
Click to collapse
Small correction: I would note here that the Nvidia Shield Tablet uses the 32 bit version of the K1 chip, rather than the 64 bit version used in the Nexus 9. The screen resolution is also 1920x1200. The Kepler GPUs in both chips can easily handle those resolutions.
As you note , where the Nexus 9 has performance problems they are usually the result of the less than optimal amount of memory.
studenttwok said:
Hi all,
Many of you are suggesting from frequent launcher redraw issue.
That is likely cause by few reasons, including CPU power limitation (not able to handle such 320ppi density screen) and not enough memory for loading high resolution assets.
So I try to loader my nexus 9 screen density setting from 320 to 318.
318 is my pick and you can try any number between 280 and 319.
For your reference:
Native ppi of nexus 9 screen is 288(obtained from this formula: sqrt(1536^2 + 2048^2) / 8.9 =~287.64 )
System is expected to load the hdpi instead of xhdpi assets, and this seems improve the situation a lot.
Given that Nvidia Shield Tablet, which has a similar CPU and memory volume with Nexus 9, only have a 283ppi screen. Difference screen density may be the key to their different performances.
Steps:
1. Enable debug mode on your device.
2. On your pc/mac, switch to your adb folder.
3. adb shell wm density 318
4. Restart your Tablet and try.
Restore to origin setting:
Use
Replace the command at step 3 with
adb shell wm density reset
Let me know if this helps!
Thanks!
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
This made things snappier for me and no lag after hrs of use, good find man. Running 318 also.
This works for my device too. Even chrome is snappier. Thank you.
@studenttwok Is there a way to confirm that the change in density actually goes into effect? I have tried the solution by setting the density to 288 but I cannot see a difference neither graphically nor in performance.
billgs said:
@studenttwok Is there a way to confirm that the change in density actually goes into effect? I have tried the solution by setting the density to 288 but I cannot see a difference neither graphically nor in performance.
Click to expand...
Click to collapse
Everything gets smaller. It's impossible to not notice
I tried 318 but in the play store I already saw some icons that were pretty big and stretched out, didn't like it. Not terrible I guess but not sure if it's worth it for me.
Jensiehh said:
I tried 318 but in the play store I already saw some icons that were pretty big and stretched out, didn't like it. Not terrible I guess but not sure if it's worth it for me.
Click to expand...
Click to collapse
288 looks fine for me. Try that.
billgs said:
@studenttwok Is there a way to confirm that the change in density actually goes into effect? I have tried the solution by setting the density to 288 but I cannot see a difference neither graphically nor in performance.
Click to expand...
Click to collapse
You can use this command:
adb shell wm density
adb will show you the current density setting
The reason for me to pick 318 is it tends to 320 and try to preserve as many details as I can, and can force system to load hdpi assests instead of xhdpi. (319 is odd number and I don't' like it, personal preference)
You can try what @knitler suggests, use 288. It may look huge different in that density(everything is becoming noticeable smaller), but it may look good since image assets and font size are much more balanced.
@Jensiehh
I notice that as well, and again, personal preference matter
studenttwok said:
You can use this command:
adb shell wm density
adb will show you the current density setting
The reason for me to pick 318 is it tends to 320 and try to preserve as many details as I can, and can force system to load hdpi assests instead of xhdpi. (319 is odd number and I don't' like it, personal preference)
You can try what @knitler suggests, use 288. It may look huge different in that density(everything is becoming noticeable smaller), but it may look good since image assets and font size are much more balanced.
@Jensiehh
I notice that as well, and again, personal preference matter
Click to expand...
Click to collapse
288 is too small. You can pick the density on AICP and I got mine on 304. I'm diggin it. Increase the icon size on Nova and you're good! Thanks for the info.
This actually made typing for me in portrait a lot more bearable for me! And able to multitask!
Thx for the post, only thing i have noticed is swiftkey goes crazy in its size, just change keyboard to google insted.
will keep a eye on performance
I put it on 288 and it looks surprisingly good. I expected it to be much worse than 318, but it's not really the case. The icons in the play store were still a little stretched out, but they seem sharper than on 318.
So what has it really changed? It seems the rest is a little smaller? Not that much that it's disturbing though.
I went 240 and it was awesome for me before i sold my tablet. Try it
Just thought I'd mention that there's a huge difference between the nVidia shield CPU and the Nexus 9 CPU. Nexus 9 dual core Denver CPU isn't used in any other device, and is a completely unique architecture where as the Shield CPU uses (4 cores + 1) off the shelf ARM cores.
Can the wm density command be done through a terminal command?
Edit: It does via SU.
So far so good for me - will see how it behaves of the weekend but everything certainly feels snappier for me.
Much appreciated, seems to really help the N9!
I get this:
Code:
C:\Users\ix\Desktop>adb shell
[email protected]:/ # wm density
Error type 2
android.util.AndroidException: Can't connect to window manager; is the system running?
at com.android.commands.wm.Wm.onRun(Wm.java:81)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.wm.Wm.main(Wm.java:46)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:251)
1|[email protected]:/ #
The same happens when I issue this command as root from the terminal from inside device. When I say "wm density" there as a default user it replies "Physical density 320" but this user does not have permission to change this value.
Any ideas what can be the reason?