Both the nexus 4 and the nexus 7 (2013) support slimport, which is very useful for mirroring the device to a big screen. However, neither device uses the standard 16:9 (1080p) aspect ratio. As a result, you end up with some cropping on a 1080p TV. For the nexus 4 it is even worse, since it outputs 768p upscaled to the TV's resolution.
However, the flexibility of android allows us to manually change the native resolution. In a console, we can type the command:
wm size 1080x1920
and the resolution will change. In the device screen the new resolution will look odd, however you now have true 1080p on the TV. To get back to the default resolution you type:
wm size reset
This solution works, but it is not very convenient. So I made two profiles for tasker, that automatically change the device resolution upon the connection of an HDMI cable and reset it when the cable is disconnected, thus automating the whole process.
I 'm attaching a screenshot of the two profiles, as well as a zip file so you can extract and import them in tasker.
In summary,
- you need root
- you need a ppi setting lower than 288 otherwise the navbar disappears
the HDMI plugged profile
- reduces the device brightness to minimize battery consumption
- increases volume
- sets resolution to 1080p
- enables WiFi
- sets display timeout to 10 hours
- activates display rotation
the HDMI un-plugged profile
- sets auto brightness back on
- resets screen resolution
- sets display timeout to 1min
These are optional settings that I found useful to automate, but they are all optional, and you can tweak them once you imported the profile to tasker.
I hope you find this useful!!! :good:
UPDATE: Your device must be set to a ppi lower than 288. I am using 286 myself. To change your ppi:
Open the build.prop file from /system/build.prop
using a text editor/buildprop editor app, change the value of ro.sf.lcd_density=286
save the file, reboot
dont work anymore
Thanks for sharing.. It worked for me in a long time but not it wont change anymore..
Do you know what i could get a conflict? have just installed apps and then last night i wont change resolution when i connect slimport and i cant seem to fix it
Thanks for this, I tried testing the wm size reset command in terminal emulator but for some reason the navbar icons disappear and only come back when I Power Off and restart the device again, I'm on 4.4.4 if it makes any difference.
petanque said:
Thanks for sharing.. It worked for me in a long time but not it wont change anymore..
Do you know what i could get a conflict? have just installed apps and then last night i wont change resolution when i connect slimport and i cant seem to fix it
Click to expand...
Click to collapse
Make sure tasker is still active and root is working fine.
Q8-V08 said:
Thanks for this, I tried testing the wm size reset command in terminal emulator but for some reason the navbar icons disappear and only come back when I Power Off and restart the device again, I'm on 4.4.4 if it makes any difference.
Click to expand...
Click to collapse
I don't have that issue, however I'm also running at a lower PPI than the default. I'll try it out at stock PPI and see if I have any issues with the navbar. What is your setup? ROM, xposed, etc.
Sent from my Nexus 4 using Tapatalk
cpanos said:
Make sure tasker is still active and root is working fine.
I don't have that issue, however I'm also running at a lower PPI than the default. I'll try it out at stock PPI and see if I have any issues with the navbar. What is your setup? ROM, xposed, etc.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Stock rooted, qc optimized bionic+dalvik, latest dev preview gpu driver.
For the navbar to showup on my 40" tv in 1920x1080 I have to set the ppi to 288, 289+ it's hidden.
Using
https://www.sven.de/dpi/
http://pixeldensitycalculator.com
http://isthisretina.com
all say my ppi should be 55.07 though.
Q8-V08 said:
Stock rooted, qc optimized bionic+dalvik, latest dev preview gpu driver.
For the navbar to showup on my 40" tv in 1920x1080 I have to set the ppi to 288, 289+ it's hidden.
Using
https://www.sven.de/dpi/
http://pixeldensitycalculator.com
http://isthisretina.com
all say my ppi should be 55.07 though.
Click to expand...
Click to collapse
Thanks, I'm running on a ppi of 286 and everything works fine here as well. I will update the op to let people know that their ppi must be lower than 288 and add instructions on how to set that.
Im not sure if I can have the ppi change with tasker, however, people might be using a lower ppi permanently so having tasker switch it back to the default would suck.
Hi, thanks for this profiles... I don't have HDMI, but will this wm command work also with ChromeCast?
Ja_som said:
Hi, thanks for this profiles... I don't have HDMI, but will this wm command work also with ChromeCast?
Click to expand...
Click to collapse
Bump, I would like to know this as well!! Tia.
Sent from my Nexus 7 using Tapatalk
jblaze10 said:
Bump, I would like to know this as well!! Tia.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I tested it yesterday. I changed size with command from OP, but there was problem with navbar, I lost navbar in landscape mode, it appears only in portrait mode. When I played video in MX Player I could not go back...
This is maybe because of ppi, which I did not change.
Sent from my tablet./Odoslané z môjho tabletu.
Ja_som said:
Hi, thanks for this profiles... I don't have HDMI, but will this wm command work also with ChromeCast?
Click to expand...
Click to collapse
jblaze10 said:
Bump, I would like to know this as well!! Tia.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Interesting. You mean when mirroring the device to a chromecast? I dont see why this should not work, I will test it and report back, on vacations now
Ja_som said:
I tested it yesterday. I changed size with command from OP, but there was problem with navbar, I lost navbar in landscape mode, it appears only in portrait mode. When I played video in MX Player I could not go back...
This is maybe because of ppi, which I did not change.
Sent from my tablet./Odoslané z môjho tabletu.
Click to expand...
Click to collapse
Yes, you lost the navbar because of your ppi setting. Either change your ppi to anything lower than 288 or use a pie navbar app like LMT (havent tried that though).
I havent found a way to change ppi without the need to reboot the device so I can add it to the tasker profile.
Ja_som said:
Hi, thanks for this profiles... I don't have HDMI, but will this wm command work also with ChromeCast?
Click to expand...
Click to collapse
jblaze10 said:
Bump, I would like to know this as well!! Tia.
Click to expand...
Click to collapse
The wm command works perfectly with a Chromecast and you get the right resolution when mirroring. However, tasker cannot pick up when you do a screen cast (for now) so there is no way to automate the process (as far as I can tell).
Sent from my Nexus 4 using Tapatalk
No need to edit the build.prop.
See here: http://forum.xda-developers.com/showpost.php?p=45873206&postcount=3
wm size 1080x1920
wm density 288
To change it back:
wm size reset
wm density reset
Click to expand...
Click to collapse
Related
Running CM7 Nightly 118. The game installs fine, loads full screen, but the graphics are just large white boxes on a black background. The menu, gameplay, everything where the actual cannon would playable is this way.
The game itself is still playable - kind of.
Have you tried adjusted your screen resolution? I hear that helps with some games
You mean the density? No, I haven't...
IFLATLINEI said:
Have you tried adjusted your screen resolution? I hear that helps with some games
Click to expand...
Click to collapse
I'm sorry. Yes I meant screen density.
Have a suggestion on what to set it to? And will it mess up the display for other things that currently display full screen?
The title says so! Anyone has this issues?
Solution!!! Install ur original graphics controller... Ur resolution is not right!!!
Sent from my LG-P500 using Tapatalk
Check your resolution settings....read this thread
http://forum.xda-developers.com/showthread.php?t=1265544
I had the same problem (although my resolution was fine) and I was able to get the metro apps working again by restoring my system to its default state.
Aaron McCarthy said:
Check your resolution settings....read this thread
http://forum.xda-developers.com/showthread.php?t=1265544
Click to expand...
Click to collapse
Hmmm, will try when i come back home...
Sent from my LG-P500 using Tapatalk
@ aaron still not working!
Sent from my LG-P500 using Tapatalk
I am also not getting my metro apps working.
I have spent days trying to find an answer to why my metro apps weren't working. I installed it on two different machines and they worked on one but not the other. Screen resolution was not an issue since both laptop resolution was high than the threshold resolution. I also tried the going back to local log in instead of a windows live log in but found no love there as well.
The only difference was that i did a clean 32bit without dev tools on the one that worked and i did a save files and settings on the other using the 64bit non dev tools.
So I backed up what i could and did a clean install of the 64bit non dev tool version and when was all said and done my metro apps worked just fine. Installed the programs i wanted i.e. World of Warcraft, updated, switched to windows live login and all still worked.
Thats how i got my Windows 8 Dev Preview to work on my laptops.
For me, screen resolution was the problem. The thread says that any resolution lower than 1024*768 causes the metro apps to stop functioning. However, they still did not work on 1366*768. I lowered the resolution to 1024*768 and it worked! Maybe Metro currently does not support widescreen resolution??
Try different resolutions. Maybe it will work for you.
chaitanya91845 said:
For me, screen resolution was the problem. The thread says that any resolution lower than 1024*768 causes the metro apps to stop functioning. However, they still did not work on 1366*768. I lowered the resolution to 1024*768 and it worked! Maybe Metro currently does not support widescreen resolution??
Try different resolutions. Maybe it will work for you.
Click to expand...
Click to collapse
my metro apps work on 1366x768
Sent from my R800i using Tapatalk
My resolution is 1366x768 and when i first installed it no resolution worked. seems there are many different "solutions" out there and we as Preview Testers just have to keep trying to figure it out. That is till M$ fixes the issue. as of right now i love the new interface, or at least the challenge of figuring it out and how it fits in my world.
are you logged in using a Windows Live account? some people have had success logging in with a local account (which you can set up under Control Panel > Users > More...
I don't know if its obvious, but did you people install the correct drivers for the video and graphic cards? I have Nvidia 2GB GEforce and everything worked fine after installation of the drivers. The Windows 7 drivers work correctly, in case you were wondering.
akshay2000 said:
I don't know if its obvious, but did you people install the correct drivers for the video and graphic cards? I have Nvidia 2GB GEforce and everything worked fine after installation of the drivers. The Windows 7 drivers work correctly, in case you were wondering.
Click to expand...
Click to collapse
Finding drivers now...
Sent from my LG-P500 using Tapatalk
for me with a resolution 1920*1080 , it works before installing other programs but after installing some of them , they (metro apps) stop working .
so i start installing my programs one by one and found that metro apps stop working after installing Geovision surveillance system software ( i noticed that this software change .NET framework configuration and install Microsoft Visual C++ ) , so to make them work i have to uninstall geovision OR keep it and live with it.
found solution , geovision software also disable UAC , so i reenabled it , and what you know , metro apps is working again.
Phone: Galaxy Note 4 910C Exynos
I've been trying to get Evernote and Gmail to run in tablet mode for a few days with no avail.
I've tried Xposed app settings tweaks and a few other tablet-mode xposed mods which at most crashed the system UI.
Does anyone know a working way to accomplish that on the Note 4?
I have the same question?
I'm trying to accomplish this on Firefox to force it in tablet mode. I have no problems on my Note3 to get it, but on Note4 it wont work. Did anyone get it to work and how?
Im on DR.Ketan ROM with multi DPI on note4 ... and on my note3 (which works great without any modifying) im using x-note ROM.
muamers said:
I have the same question?
I'm trying to accomplish this on Firefox to force it in tablet mode. I have no problems on my Note3 to get it, but on Note4 it wont work. Did anyone get it to work and how?
Im on DR.Ketan ROM with multi DPI on note4 ... and on my note3 (which works great without any modifying) im using x-note ROM.
Click to expand...
Click to collapse
Use "App Settings" Xposed Module. You can change the DPI in a per app basis and force tablet ui mode too (touch "resolution" and apply the biggest one).
galaxynote2 said:
Use "App Settings" Xposed Module. You can change the DPI in a per app basis and force tablet ui mode too (touch "resolution" and apply the biggest one).
Click to expand...
Click to collapse
Yes, thats what i thought too but it didnt work on the note4 ... the largest resolution is 1000x1800 and it wont start in tablet mode, no matter what DPI i set.
Sent from my SM-N910F using Tapatalk
muamers said:
Yes, thats what i thought too but it didnt work on the note4 ... the largest resolution is 1000x1800 and it wont start in tablet mode, no matter what DPI i set.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Anyone ...
jedybg said:
Phone: Galaxy Note 4 910C Exynos
I've been trying to get Evernote and Gmail to run in tablet mode for a few days with no avail.
I've tried Xposed app settings tweaks and a few other tablet-mode xposed mods which at most crashed the system UI.
Does anyone know a working way to accomplish that on the Note 4?
Click to expand...
Click to collapse
muamers said:
I have the same question?
I'm trying to accomplish this on Firefox to force it in tablet mode. I have no problems on my Note3 to get it, but on Note4 it wont work. Did anyone get it to work and how?
Im on DR.Ketan ROM with multi DPI on note4 ... and on my note3 (which works great without any modifying) im using x-note ROM.
Click to expand...
Click to collapse
Hi,
there is an app that I've used for it on my n910f.
UI Tuner (aka Window Manager) on Google Play:
https://play.google.com/store/apps/details?id=com.bassel.uituner
It works like App settings. Go to menu in UI Tuner and select per app settings. From there you can choose the app you want to run tablet mode. Just type an lower density value and higher screen size. You can google for some tablet values.
More information you can find here on xda. Search for window manager.
It didn't work for me. Looks like there is no way to run firefox in tablet mode on note4 ...
muamers said:
It didn't work for me. Looks like there is no way to run firefox in tablet mode on note4 ...
Click to expand...
Click to collapse
Sorry mate. For other apps it worked for me. But Firefox app seems get some device information (assume from build.prop) to recognize which mode it should start, so it is no matter what dpi or screen size you have.
vbaschen said:
Sorry mate. For other apps it worked for me. But Firefox app seems get some device information (assume from build.prop) to recognize which mode it should start, so it is no matter what dpi or screen size you have.
Click to expand...
Click to collapse
Probably In Xposed AppSettings it changes the DPI like it should, but firefox just doesnt recognize it. I cant get behind the logic of that, because on the Note3 the same version works excellent in tablet UI. Looks like i have to switch completely to the RAM eater chrome.
Ill ask it in the ROM section, maybe its something ROM related or the dev could help me out.
muamers said:
I have the same question?
I'm trying to accomplish this on Firefox to force it in tablet mode. I have no problems on my Note3 to get it, but on Note4 it wont work. Did anyone get it to work and how?
Im on DR.Ketan ROM with multi DPI on note4 ... and on my note3 (which works great without any modifying) im using x-note ROM.
Click to expand...
Click to collapse
I found that setting the global DPI on my G4 with textdroider changed Firefox into tablet mode at a certain point (450 worked, with my device default being 640), but it doesn't work with App Settings.
My suggestion is to change your entire DPI to some smaller number with textdroider and adjust apps to a larger size as needed. Kinda annoying, but should do the trick.
Sent from my LG-H812 using Tapatalk
Hi,
I've changed the DPI of my A7 from 640 (stock) to 560 via adb:
Code:
adb shell wm density 560
Unfortunatelly many Apps have problems now and show display errors, e. g. too big icons, etc.
Anyone know, how I can fix this?
Thank you!
- PsP
Try 544. it corrected the keyboard and notification bell but my phone app is still off. I also found that editing the build.prop was a better way to change DPI if you're rooted.
Thank you, but I have no problems with the notification bell (lockscreen) or the keyboard (I use Google keyboard app). Also the dialer works well (I use the Truecaller app but also stock looks fine).
I also do not want to root my A7 because I want it as stock as possible ... :/ I know, the build.prop would be the "better" way. But with the stock 640 dpi everything is so big ... :/
The most problems have third party apps like tinder (crashes) or Google allo (the profile picture in the top right corner if I open a chat is too big)
I'm using 510.
I've installed the google keyboard as the ZTE does not support it.
PsP.Hc11 said:
Hi,
I've changed the DPI of my A7 from 640 (stock) to 560 via adb:
Code:
adb shell wm density 560
Unfortunatelly many Apps have problems now and show display errors, e. g. too big icons, etc.
Anyone know, how I can fix this?
Thank you!
- PsP
Click to expand...
Click to collapse
are you with TWRP + Rooted?
you can install Xposed and used Setting Apps Module allow you to change DPI per App which is one of the reason why i have xposed in any past device of mine.
I actually just changed my dpi to 560 and everything looks so much better! No errors, no goofy sized icons, everything seems to work.
xxBrun0xx said:
I actually just changed my dpi to 560 and everything looks so much better! No errors, no goofy sized icons, everything seems to work (except the bell, but I'm ok with that).
Click to expand...
Click to collapse
I believe the native screen density is 538, no clue why they change it from there.
xxBrun0xx said:
I actually just changed my dpi to 560 and everything looks so much better! No errors, no goofy sized icons, everything seems to work (except the bell, but I'm ok with that).
Click to expand...
Click to collapse
What isn't working with the notification bell? I'm on 560 DPI and have no problems with it - just with 3rd party apps like e. g. Google Allo, as i mentioned...
DrakenFX said:
are you with TWRP + Rooted?
you can install Xposed and used Setting Apps Module allow you to change DPI per App which is one of the reason why i have xposed in any past device of mine.
Click to expand...
Click to collapse
Nope.
PsP.Hc11 said:
I also do not want to root my A7 because I want it as stock as possible ... :/
Click to expand...
Click to collapse
PsP.Hc11 said:
What isn't working with the notification bell? I'm on 560 DPI and have no problems with it - just with 3rd party apps like e. g. Google Allo, as i mentioned...
Nope.
Click to expand...
Click to collapse
Your right, notification bell works great. Somebody mentioned earlier on the thread that it didn't work with 560 and I didn't have any notifications to test so I assumed they were correct. I've since gotten notifications and the bell works fine. Really enjoying 560!
Set it back to stock now because also apps like Snapchat or Instagram had problems with 560 dpi via adb shell wm ...
I was struggling with my phone freaking out while doing video chat on either Teams and Duo. Both apps did the same thing and I provided feedback to their developers that it appeared to start on my note 20 ultra 5g when android 11 landed.
Today I realized that if I changed my video resolution for the phone display from FHD+ to WQHD+ the freezing stops altogether...
Anyone else able to test this out?
My video Resolution is set to 16:9 FHD 1920x1080 (30 fps) and I use Duo to TeleHealth VideoChat with two different Doctors on a regular basis with absolutely no problems! Works great - Android 11/OneUI 3.0. I don't use "Teams" - hate it!!!
jimd1050 said:
My video Resolution is set to 16:9 FHD 1920x1080 (30 fps) and I use Duo to TeleHealth VideoChat with two different Doctors on a regular basis with absolutely no problems! Works great - Android 11/OneUI 3.0
Click to expand...
Click to collapse
I only have these three options
Yeah, that's screen resolution under "Display" - that's what I have also. What I was talking about was in Camera Video Settings! Open you're camera, go to settings and look for "Front Video Size" - select 16:9, then open the Resolution and see all the choices and grab what I said before.
jimd1050 said:
Yeah, that's screen resolution under "Display" - that's what I have also. What I was talking about was in Camera Video Settings! Open you're camera, go to settings and look for "Front Video Size"
Click to expand...
Click to collapse
I will have to check that out because that makes me wonder if the bug is a scaling issue between showing the preview of your camera on your display at different resolutions
I actually don't think one has anything to do with the other - my setting is probably what we're recording at to send to the other party!!! I have to log off so I'll check back later...
jimd1050 said:
I actually don't think one has anything to do with the other - my setting is probably what we're recording at to send to the other party!!! I have to log off so I'll check back later...
Click to expand...
Click to collapse
I checked and that's what mine was already. When using duo can you exit the app (while still on the call) and bounce between apps without issue?
dottat said:
I checked and that's what mine was already. When using duo can you exit the app (while still on the call) and bounce between apps without issue?
Click to expand...
Click to collapse
Sorry, just got your question AND I'm not staying - I have never tried, like I said, I only use it for Doctor's Appointments and never have a need to leave during the appointment. Short Telehealth Appointments and done... over and out! ??? Hope that helped!