Hi,
there an app to change hdmi output resolution? Or a custom Rom that supports it?
elgar said:
Hi,
there an app to change hdmi output resolution? Or a custom Rom that supports it?
Click to expand...
Click to collapse
[How-To] HDMI Fullscreen Toggle Script
The script has a resolution argument, although 1920x1080 and 2560x1440 are the only ones I have ever heard used with a N10. The script can be run manually from a terminal session or if you can install SManager through a shortcut icon on the desktop. See issues with SManager here.
3DSammy said:
[How-To] HDMI Fullscreen Toggle Script
The script has a resolution argument, although 1920x1080 and 2560x1440 are the only ones I have ever heard used with a N10. The script can be run manually from a terminal session or if you can install SManager through a shortcut icon on the desktop. See issues with SManager here.
Click to expand...
Click to collapse
Thank you very much. I looked at the thread, but can't understand, how do I change resolution to a different one for my monitor?
elgar said:
Thank you very much. I looked at the thread, but can't understand, how do I change resolution to a different one for my monitor?
Click to expand...
Click to collapse
Both the script and raw commands require a terminal emulator app so make sure one is installed. Android Terminal Emulator
Here are the raw resolution change commands if you want to try them yourself. Each needs to be entered at the command line prompt so you always at least need a terminal emulator app.
1) Set screen resolution to 1920x1080:
am display-size 1920x1080
2) Set screen resolution to 2560x1440:
am display-size 2560x1440
3) Reset screen resolution:
am display-size reset
To use the "hdmi_toggle.sh" script in a terminal session:
On a PC:
1) Copy the script directly from the post.
2) Then paste it into a text editor and save with the name "hdmi_toggle.sh"
On your N10:
3) Copy the "hdmi_toggle.sh" script to some directory on your N10.
Running the HDMI toggle script:
a) Open the terminal session emulator app on your N10
b) At the command prompt create a directory for the toggle state file:
mkdir "/scdard/hdmi_toggle"
c) At the command prompt enter (replace the "/directory/ to script/" with the scripts location)
cd "/directory/ to script/"
d) Run the script by entering at the command prompt:
sh ./hdmi_toggle.sh "/scdard/hdmi_toggle" "1920x1080"
The resolution on the N10 should have changed.
e) To return to your original N10 resolution repeat the command in "d"
sh ./hdmi_toggle.sh "/scdard/hdmi_toggle" "1920x1080"
You will not need to do step "b" after the first time as the directory is already created.
This looks like a pain but it is much easy if the script is combined with SManager as explained in the thread. For those without SManager the pain is limited as I do not suspect people will use HDMI a lot.
3DSammy said:
[How-To] HDMI Fullscreen Toggle Script
The script has a resolution argument, although 1920x1080 and 2560x1440 are the only ones I have ever heard used with a N10.
Click to expand...
Click to collapse
Can half the native resolution too (1280x800) and it'll work fine.
3DSammy said:
Both the script and raw commands require a terminal emulator app so make sure one is installed. Android Terminal Emulator
Here are the raw resolution change commands if you want to try them yourself. Each needs to be entered at the command line prompt so you always at least need a terminal emulator app.
1) Set screen resolution to 1920x1080:
am display-size 1920x1080
2) Set screen resolution to 2560x1440:
am display-size 2560x1440
3) Reset screen resolution:
am display-size reset
To use the "hdmi_toggle.sh" script in a terminal session:
On a PC:
1) Copy the script directly from the post.
2) Then paste it into a text editor and save with the name "hdmi_toggle.sh"
On your N10:
3) Copy the "hdmi_toggle.sh" script to some directory on your N10.
Running the HDMI toggle script:
a) Open the terminal session emulator app on your N10
b) At the command prompt create a directory for the toggle state file:
mkdir "/scdard/hdmi_toggle"
c) At the command prompt enter (replace the "/directory/ to script/" with the scripts location)
cd "/directory/ to script/"
d) Run the script by entering at the command prompt:
sh ./hdmi_toggle.sh "/scdard/hdmi_toggle" "1920x1080"
The resolution on the N10 should have changed.
e) To return to your original N10 resolution repeat the command in "d"
sh ./hdmi_toggle.sh "/scdard/hdmi_toggle" "1920x1080"
You will not need to do step "b" after the first time as the directory is already created.
This looks like a pain but it is much easy if the script is combined with SManager as explained in the thread. For those without SManager the pain is limited as I do not suspect people will use HDMI a lot.
Click to expand...
Click to collapse
Thanks a lot! I have tried also "am display-size" command. It also changes the resolution. Does the script work the same?
P.S. Never mind. Just found an answer.
HDMI resolution changer app
I quickly put together this app that changes the resolution when the HDMI cable is plugged / unplugged.
It also uses the am display-size commands and requires su permission. The default resolution is set to 2560x1440 when HDMI is plugged in and can be adjusted in the app.
https://docs.google.com/file/d/0B8C1BFemNlbzS196YTlDNmFSQ3c/edit?usp=sharing
The only annoying thing is when changing to 1920x1080 (at least through terminal) is that your phone gets reset to phone mode so you lose on-screen buttons as well as ruin your launcher (Apex). If you do a am display-size reset you get the on-screen nav buttons back but it's still phone mode, meaning you'll only have them on the right-hand side in portrait.
At least in CM10.1/AOSP. Bit better with AOSPA since you can change it on the fly, but AOSPA has horrible performance if you're doing two displays + gaming.
sbradymobile said:
I quickly put together this app that changes the resolution when the HDMI cable is plugged / unplugged.
It also uses the am display-size commands and requires su permission. The default resolution is set to 2560x1440 when HDMI is plugged in and can be adjusted in the app.
https://docs.google.com/file/d/0B8C1BFemNlbzS196YTlDNmFSQ3c/edit?usp=sharing
Click to expand...
Click to collapse
Wow, thanks! I'll check out when I have a chance!
espionage724 said:
Can half the native resolution too (1280x800) and it'll work fine.
Click to expand...
Click to collapse
Which screen density do I put if my screen resolution is 1440*900? What's the formula?
sbradymobile said:
I quickly put together this app that changes the resolution when the HDMI cable is plugged / unplugged.
It also uses the am display-size commands and requires su permission. The default resolution is set to 2560x1440 when HDMI is plugged in and can be adjusted in the app.
https://docs.google.com/file/d/0B8C1BFemNlbzS196YTlDNmFSQ3c/edit?usp=sharing
Click to expand...
Click to collapse
this app is requesting permission to almost everything on your tablet...
elgar said:
Which screen density do I put if my screen resolution is 1440*900? What's the formula?
Click to expand...
Click to collapse
Desired width / actual width (2560) * actual density (320). So in the case of 1440x900 it would be 180.
mrruin said:
this app is requesting permission to almost everything on your tablet...
Click to expand...
Click to collapse
That is for the superuser access permission; all apps that use su should have that warning. Code is available here if you would like to take a look: https://github.com/sbradymobile/HDMIRes.
This app works really well. But for some reason hdmi out doesn't work on my 19 inch LG monitor.
Is it possible to have a non-root requirement for such an on-off app?
I can do terminal trick non root so hoped it would be doable. Cheers anyway
Sent from my Nexus 7
sbradymobile said:
I quickly put together this app that changes the resolution when the HDMI cable is plugged / unplugged.
It also uses the am display-size commands and requires su permission. The default resolution is set to 2560x1440 when HDMI is plugged in and can be adjusted in the app.
https://docs.google.com/file/d/0B8C1BFemNlbzS196YTlDNmFSQ3c/edit?usp=sharing
Click to expand...
Click to collapse
This great app stopped working in 4.3.
Can you please fix it?
Animor said:
This great app stopped working in 4.3.
Can you please fix it?
Click to expand...
Click to collapse
Here is a link to the update.
https://docs.google.com/file/d/0B8C1BFemNlbzai14Z3ZtckQ5X2s/edit?usp=sharing
sbradymobile said:
Here is a link to the update.
https://docs.google.com/file/d/0B8C1BFemNlbzai14Z3ZtckQ5X2s/edit?usp=sharing
Click to expand...
Click to collapse
Thank you.
I get an error message when trying to install it:
There was a problem parsing the package.
Click to expand...
Click to collapse
Animor said:
Thank you.
I get an error message when trying to install it:
Click to expand...
Click to collapse
I just put up a new signed package at the same link; let me know if you have problems installing it.
Package is fine now, thank you!
sbradymobile said:
I just put up a new signed package at the same link; let me know if you have problems installing it.
Click to expand...
Click to collapse
Hi,
I have checked the app and there are few problems with it:
1. When disconnecting the HDMI cable, resolution didn't change back to original. I had to reboot the N10.
2. I have set HDMI resolution to 1920x1080, but for some reason it didn't display correctly on my 1080p TV. The picture was cut/cropped a bit.
Please assist...
Related
Hi, I am thinking of buying Nexus 7, but I would really like to have some way to stream it's display to at least computer. That can be most easily (well, more like the most primitive way) by sending content of framebuffer via wifi. That however requires the framebuffer to be accessible and reasonably big (eg. small).
Now, I do not have it yet, and I do not know anybody who has it, so I am asking you to get some info about framebuffer for me. It will not take more than 5 minutes and only things you need is ADB and root.
So, if you decided to help me, thank you, and let's get started.
I want you to just run several commands on your device under root and then send me the result files.
1. Device permissions
Code:
ls -l /dev > /sdcard/xda_tass.txt
ls -l /dev/graphics >> /sdcard/xda_tass.txt
These two commands will tell me what device files are available on N7 and their permissions. The output is saved to file on sdcard (well, I hope the memory in N7 is called /sdcard. If not, just change it to some existing path).
2. Testing the framebuffer
Code:
time (cat /dev/graphics/fb0 > /dev/null) >> /sdcard/xda_tass.txt 2>&1
This command will tell me how long does it take to read framebuffer. Run it 3-5 times, so that I have some average values. If "/dev/graphics/fb0" does not exist, try "/dev/fb0".
Code:
cat /dev/graphics/fb0 > /sdcard/xda_tass.dat
Copies the framebuffer into file, so that I know how big it is and which format does it have. This is like taking screenshot, so make sure there is not something embarrassing on your display
3. Send me the files
Take files "xda_tass.txt" and "xda_tass.dat", ZIP em' up and put it somewhere. That is all.
I would be really glad if somebody could do that for me, thanks
Here you go
http://db.tt/3WBr5BWK
Also the sdcard is now /storage/sdcard0, yeah idk why
Sent from my Nexus 7 using Tapatalk 2
Thank you
Looks okay, even though the framebuffer is huge. Well, I suppose it is not a problem to compress it on that quad-core craziness. And, it has two framebuffers (fb0 and fb1) - I wonder why.
Also, I cannot decode data from that framebuffer. Could you please get me also the second framebuffer?
Code:
cat /dev/graphics/fb1 > /storage/sdcard0/xda_tass_fb1.dat
Tasssadar said:
Thank you
Looks okay, even though the framebuffer is huge. Well, I suppose it is not a problem to compress it on that quad-core craziness. And, it has two framebuffers (fb0 and fb1) - I wonder why.
Also, I cannot decode data from that framebuffer. Could you please get me also the second framebuffer?
Code:
cat /dev/graphics/fb1 > /storage/sdcard0/xda_tass_fb1.dat
Click to expand...
Click to collapse
Here you go
http://db.tt/Nt6kBM83
Sent from my Nexus 7 using Tapatalk 2
Data from fb1 look about as random as those from fb0 to me. Gonna need some more samples, but I can do that by myself once I'll have my own N7.
Thanks for helping me
Tasssadar said:
Data from fb1 look about as random as those from fb0 to me. Gonna need some more samples, but I can do that by myself once I'll have my own N7.
Thanks for helping me
Click to expand...
Click to collapse
No problem lol
Sent from my Jelly Nexus S
@Tasssadar how did you decode the framebuffer? I'm actually trying to get a screenshot of MultiROM, but I can't figure out how to decode it. I'm trying to open it with GIMP by changing the settings and moving the width value, but I can't get a clear image.
Your signature says you have the 2013 Nexus 7. MultiROM doesn't use framebuffer on that device because of severe kernel driver bug. You can still take screenshots though - tap on the screen with four fingers at once. The screen should flash and screenshot will be saved to /sdcard/multirom/ (accessible in Android only with root in /data/media/0/multirom).
The format should be RGB Alpha and the dimensions should be 1200x1920.
Tasssadar said:
Your signature says you have the 2013 Nexus 7. MultiROM doesn't use framebuffer on that device because of severe kernel driver bug. You can still take screenshots though - tap on the screen with four fingers at once. The screen should flash and screenshot will be saved to /sdcard/multirom/ (accessible in Android only with root in /data/media/0/multirom).
The format should be RGB Alpha and the dimensions should be 1200x1920.
Click to expand...
Click to collapse
Damn, you put so many easter eggs in MultiROM
That's interesting though... That's why when pulling the framebuffer I only got a black screen. In the recovery, instead, I could get something "visible" (still not the actuall image, though).
@Tasssadar Is it still possible to take screenshots on the new multirom for flo? When I tap with four fingers nothing happens.
Since v27, screenshots are taken with power+volume down combo like in Android ( you have to press power button first though, cause I'm lazy). They are also saved as PNG instead of raw data, and they are in folder /sdcard/Pictures/Screenshots like Android screenshots. I mentioned it in the changelog
Protip :
tutorial on howto increase Nook's "resolution" by changing /system/build.prop
http://forum.xda-developers.com/showthread.php?t=823522
Can someone do a compare?
I scanned the thread and performed the following actions:
First I used the "test" commands to experiment with settings. I discovered that I liked a density setting of 133 best.
# setprop qemu.sf.lcd_density 133
# busybox killall system_server
So I modified my /system/build.prop by changing the line
#ro.sf.lcd_density=240
to
ro.sf.lcd_density=133
and rebooted.
So, everything is certainly smaller, but as I have only one NST, I cannot determine if I think the text is sharper because I can't do a side-by-side comparison. So, is there somebody out there with two NSTs who is willing to make this change to one of them and then do a side-by-side comparison and report back?
David0226 said:
So, everything is certainly smaller, but as I have only one NST, I cannot determine if I think the text is sharper because I can't do a side-by-side comparison. So, is there somebody out there with two NSTs who is willing to make this change to one of them and then do a side-by-side comparison and report back?
Click to expand...
Click to collapse
You can do few screenshots and compare them side-by-side.
screenshots?
how do you do a screnshot on nook? , ( for those of us that don't know) , thanks
steelworker said:
how do you do a screnshot on nook? , ( for those of us that don't know) , thanks
Click to expand...
Click to collapse
dude...wtf?
Just type "screenshot android" into your search engine.
I use 'ddms' via adb.
http://www.makeuseof.com/tag/how-to-capture-screenshots-with-your-android-mobile-phone/
No real difference
Here are two screen shots I took. (Thanks for the link osowiecki). The first was taken with the density set to 160 (standard) and the second with it set to 120. There is some difference in the size of the header and footer lines, but I see no real difference in the size of the book text. Setting the density to 120 does allow the standard B&N library app to display nine titles on one screen instead of six. Otherwise I see no difference when using the standard B&N reader.
I did these tests using the LCDDensity app.
Here are screenshots of the library app in each density ...
I can't confirm any changes for text based books, but it definitely helps with converted comics. No idea why the screenshots are green, used "screenshot" tool from within adb shell. Tried with default DPI, 133, 120, and also pulled the image from the unconverted CBR for comparison.
neoman4426 said:
No idea why the screenshots are green ...
Click to expand...
Click to collapse
My screenshots taken with the screenshot tool in ADB shell were green also. You will get better results by following the procedure outlined in the link in osowiecki's post.
Was the first thing I tried, couldn't get it to recognize my device. I'm not sure if it's a wired ADB only thing, or a "doesn't work on Linux for some reason" thing or what. ah well, I kind of like the green look
I didn't know where to put this and I own a moto g so I decided to put it here.
As many people will know, in android 4.4 an inbuilt screen recorder was released. This recorder requires you to initiate the recording process using ADB and USB debugging, this seems great until you notice that the maximum length of a recording is 3 minutes.
Now, on windows I made a batch file which looks something like this:
CALL :Record
SET /a var1=0
:record
SET /a var1+=1
SET /a name=%var1%
adb shell screenrecord /sdcard/recording%name%.mp4 --bit-rate 3145728
GOTO :record
Click to expand...
Click to collapse
The batch file basically creates a loop which restarts the recording every time the previous recording finishes, every time the script loops 1 will be added to the number in the recording meaning the files will not overwrite each other so it will start with a file named "recording1.mp4" and then after 3 minutes it will make a new recording named "recording2.mp4".
I decided to use a 3mbps bit rate as it looks decent in 720p and doesn't effect the framerate in games as much as the default 4mbps although you can change it at any time by editing the .bat file.
There is a small gap between the recordings but it seems bearable between the test recordings I have done. It can be ended by pressing CTRL+C and then pressing Y to clear batch process.
You should be able to put this into notepad and save it as a .bat file and place it inside your adb folder within the android sdk folder.
I have attached the .bat file for download purposes.
Update
I have updated the bat file so that the user inputs the filename and bit rate before the recording starts, I also got rid of the %name% variable as it wasn't actually needed and I don't know why I included it at the time.
The new file looks like this:
@ECHO off
ECHO Welcome to TheDJGr33n's ADB recording script for windows.
SET /p filename=Filename:
ECHO I usually use 3mbps.
SET /p mbps=Bitrate(In mbps):
SET /a bitrate=%mbps%*1048576
CALL :Record
SET /a var1=0
:record
SET /a var1+=1
ECHO Recording %var1% started Filename:%filename%%var1%.mp4 at bitrate %mbps%mbps.
adb shell screenrecord /sdcard/%filename%%var1%.mp4 --bit-rate %bitrate%
GOTO :record
Click to expand...
Click to collapse
I will attach the new bat file to this reply.
TheDJGr33n said:
I have updated the bat file so that the user inputs the filename and bit rate before the recording starts, I also got rid of the %name% variable as it wasn't actually needed and I don't know why I included it at the time.
The new file looks like this:
I will attach the new bat file to this reply.
Click to expand...
Click to collapse
Is it possible to use screen recording with audio in non root moto g
androidsatti said:
Is it possible to use screen recording with audio in non root moto g
Click to expand...
Click to collapse
To do this I would recommend you get a 3.5mm to 3.5mm cable, these can be found on amazon for under £1, I would post a link but I'm unable due to the lack of posts on this account.
You would plug one end into your phone's headphone port and the other into your PC, then you could use a program like audacity to record the input as a microphone. The audio would need to be synced up in editing later but it could work.
Thanks friend I l try it
Sent from my XT1033 using XDA Free mobile app
Hi friend
I used this batch file and I am able to get decent frame rates for games.after 3 mins its showing y/n to continue.but I didn't got the screen recording for more than 3 mins
Sent from my XT1033 using XDA Free mobile app
I tried the adb Shell to change the Size of default Screen size from 1080 to 2k. This i did with Mac. My phone is not rooted.
Open terminal
adb shell
Then type
wm size 1440x2560
and to go back to default use
wm size 1080x1920
It works with reboot as well.
If we change the density from 480 - 640 using WM density 640. Icons looks very small. I think by default Sony doesn't supply icons for that density. Not sure if someone already said this. You can issue the same using mobile terminal emulator as well. You can download that app from Play Store.
I am not able to take screenshot as i get "Couldn't capture screenshot. Content may be protected or the memory may be full."
Try and let me know. If it is already mentioned here. Apology. Please close this
Francis.
With Nova Launcher. With the below settings. The Phone looks awesome.
wm size 2160x3840
wm density 800
The Phone looks awesome. But with default launcher icons are so small.
sweeet i am watching this thread. thx alot
This doesn't work with the mobile terminal with unrooted Phone. Just an update. You can use both Mac and Windows CMD for doing this.
what is the default pixel density of xperia z5 premium??
480
fesar said:
I tried the adb Shell to change the Size of default Screen size from 1080 to 2k. This i did with Mac. My phone is not rooted.
Open terminal
adb shell
Then type
wm size 1440x2560
and to go back to default use
wm size 1080x1920
It works with reboot as well.
If we change the density from 480 - 640 using WM density 640. Icons looks very small. I think by default Sony doesn't supply icons for that density. Not sure if someone already said this. You can issue the same using mobile terminal emulator as well. You can download that app from Play Store.
I am not able to take screenshot as i get "Couldn't capture screenshot. Content may be protected or the memory may be full."
Try and let me know. If it is already mentioned here. Apology. Please close this
Francis.
Click to expand...
Click to collapse
My apologies for being a complete noob but could you give me an exact procedure for how to do this on Windows? I desperate need to change the awful DPI on this otherwise perfect phone.
@Traczyc
Download android sdk tools open up adb shell enter the commands hes given and done. Its all the same on windows.
Btw It looks great thanks fesar
sfex3best said:
@Traczyc
Download android sdk tools open up adb shell enter the commands hes given and done. Its all the same on windows.
Btw It looks great thanks fesar
Click to expand...
Click to collapse
Thanks, I managed to figure it out and I can confirm that it works! This is just so awesome! It's just too bad that the screenshot function doesn't work on any resolution above 1080P.
I got also one more question. When you change the resolution using ADB, does the phone actually start to output content in that resolution or is it just an illusion?
Traczyk said:
Thanks, I managed to figure it out and I can confirm that it works! This is just so awesome! It's just too bad that the screenshot function doesn't work on any resolution above 1080P.
I got also one more question. When you change the resolution using ADB, does the phone actually start to output content in that resolution or is it just an illusion?
Click to expand...
Click to collapse
2k resolution on YouTube becomes available, so I guess it works
Edit: One more thing, if everything has this weird scaling a reboot usually fixes this.
Happy new year!
I confirmed the change with some screen resolution apps and in YouTube and it both confirms it as 2k. I hope Sony makes this as permanent and with an option for real 4k as well.
fesar said:
I confirmed the change with some screen resolution apps and in YouTube and it both confirms it as 2k. I hope Sony makes this as permanent and with an option for real 4k as well.
Click to expand...
Click to collapse
Didn't you say you were running it in 4K now?
fesar said:
With Nova Launcher. With the below settings. The Phone looks awesome.
wm size 2160x3840
wm density 800
The Phone looks awesome. But with default launcher icons are so small.
Click to expand...
Click to collapse
Sent from my E6853 using XDA Free mobile app
"wm size" only emulates resolution, so real resolution is still FHD and 4K upscaling won't work when you are not watching image/video.
Real resolution is controlled by kernel:
https://github.com/AndroPlus-org/an...rm/boot/dts/qcom/dsi-panel-satsuki.dtsi#L3025
AndroPlus said:
"wm size" only emulates resolution, so real resolution is still FHD and 4K upscaling won't work when you are not watching image/video.
Real resolution is controlled by kernel:
https://github.com/AndroPlus-org/an...rm/boot/dts/qcom/dsi-panel-satsuki.dtsi#L3025
Click to expand...
Click to collapse
Yes agreed. But I prefer having my resolution on the visual screen to be better than 1080p.
fesar said:
Yes agreed. But I prefer having my resolution on the visual screen to be better than 1080p.
Click to expand...
Click to collapse
Tks
With Nova Launcher prime and Tesla Unread With the below settings.
The Phone looks awesome.
wm size 2160x3840
wm density 800
but i also have the screenshots problems? I have also tried to delete or rename Pictures folder but problem still remain.
Any solution?
Tks
jumbonosich said:
Tks
With Nova Launcher prime and Tesla Unread With the below settings.
The Phone looks awesome.
wm size 2160x3840
wm density 800
but i also have the screenshots problems? I have also tried to delete or rename Pictures folder but problem still remain.
Any solution?
Tks
Click to expand...
Click to collapse
I'm actually new to using adb. Does anyone mind doing a step by step guide on how to do this? I would greatly appreciate your help and time.
Any screen shots and evidence, like the youtube app.
is it possible to change the dpi of navigation bar thru adb shell?
nvm
image hosting 10mb limit
imgupload
When it comes to screen Sony definitely tops the list above other manufacturers but our Xperia Z5 Premium doesn't always use 4K HD Resolution Screen, only when watching 4k video or things right? so why not to make it work in always 4K mode? more pixels- more fun
Warning: Note that on high brightness battery usage will be much more than 1080p screen mode
it requires Rooted device also
1.Download Terminal Emulator from play store
2. open app and write "su" without quotes
3. give it root access and write " wm size 2160×3840 " also without quotes
Screen will became "ugly", to fix it now type "wm density 820" also without quotes. after that all should work fine, play any video and you'll notice color changes and much More improvements, however there's always a way back to 1080p
to do it
wm size 1080×1920
wm density 420
Don't forget to click Thanks Button
感谢楼主的分享，支持楼主！
Just thank you! It gave it a different and nice appearance but I noted two things. First the phone works a little slower and the other thing is when I tried to make a call the caller interface didn’t open so I was not able to make the normal functions like turning off the microphone, hanging up the call, etc. Unfortunately I had to put it back to 1080p.
you don't need root for this, you can do it with adb command though a pc without root
"adb shell wm size 2160×3840"
"adb shell wm density 820"
cheers
Elfmirth said:
you don't need root for this, you can do it with adb command though a pc without root
"adb shell wm size 2160×3840"
"adb shell wm density 820"
cheers
Click to expand...
Click to collapse
its really good
Zur75 said:
Just thank you! It gave it a different and nice appearance but I noted two things. First the phone works a little slower and the other thing is when I tried to make a call the caller interface didn’t open so I was not able to make the normal functions like turning off the microphone, hanging up the call, etc. Unfortunately I had to put it back to 1080p.
Click to expand...
Click to collapse
Is there any way to solve the problem for now?
HD2killers said:
Is there any way to solve the problem for now?
Click to expand...
Click to collapse
Hi Guys! I know you have lurking about that unutilized 4k screen of our phone, Why not enjoy "1440x2560" density of 534 works perfectly fine the only down side are glitchy looking start-up since it was designed to in 1080p and multi tasking has no thumbnails on it about it looks and feels good!
Just do
adb shell wm size 1440x2560
adb shell wm density 534 <-----------IMO this is the density, fonts looks smaller but legible.
ENJOY!
"You can do the same also on your Z1, Z2, Z3, Z4 Tablet, Z5, Z5 Compact ..... and on your crapold device, because this is not changing the display resolution
Seriously guys..... this is changing the resolution of the VIRTUAL display (not the physical one), so like this you are getting 4k emulation on 1080p physical resolution.
To change the physical display resolution you need to do "quite a few more steps", which cannot be done in a simple way like this (and surely not without root).
Moreover, even if -- yes, there is a way -- it's not doable on stock ROMs, as it misses the required implementation.
I am almost done here so, on Open Devices, you will be able to get real [email protected] whenever you want."
Copied from this discussion...
I wana buy Xperia Z5 Premium only for VR to watch 4K videos. Is still good? Can I play UHD 180° videos smooth, without any reboot with this mod?
hi does anyone have issues taking screenshots with these settings enabled? every screen shot says error app does not allow?
crusader0071 said:
hi does anyone have issues taking screenshots with these settings enabled? every screen shot says error app does not allow?
Click to expand...
Click to collapse
I try resurrection os but disabled