Hi to all!
Well I've read some guides about how to decrease the resolution on my Z2 running latest Marshmallow Existenz ROM 5.6.5. Changed resolution to 720x1280 and system DPI to 253 (I have rather a good eyesight that is why do not mind small UI elements ).
Some apps were not satisfied with the DPI I told them to work in that is why I tailored some of them using Xposed module App Settings.
But there are some issues I could not repair :crying::
1. The bootanimation displays normally, but after some seconds only half of the screen is filled (so it says ''Xpe'' and then ''Existe''). Tried to install smaller (720x1280) bootanimation but the result is the same. I can live with that
2. The Recents' thumbnails are enormous. Even 1/5 of the app is displayed in the thumbnails. I thought initially that it is caused by SystemUI's messed settings with the DPI so I played with App Settings to repair it (both ''DPI'' and ''Screen (dp)''). Still with no luck.
Thought it might be connected somehow to Android WebView which is operating in country's local app with used stuff called Finn. There the thumbnail is also really huge, before the whole picture would fit in the thumbnails.
3. Is the suggestions/xperia menu search. The ''suggested'' apps are much bigger that the icons displayed in menu.
So it might be some scalling issue, but I have no idea which application would I need to adjust.
https://postimg .org/image/53me7e9i9/
https://postimg .org/image/5uf4d6bvl/
https://postimg .org/image/wtiz8bych/
https://postimg .org/image/dcy9lt38h/
https://postimg .org/image/ku7h10srl/
My phone is running Android 6.0.1, with root, with xposed modules related to UI: AppSettings, GravityBox, Xperia Home by Serajr
Any help in the matter will be appreciated! ::laugh:
Vixificent
No one ? - I don't believe no one really had that issue! At least say: 'Happens to me too'.
Keep it hd 1080x1920 and change DPI to 320
Sent from my D6503 using XDA-Developers Legacy app
Thank you for your input! However it is not the solution I am looking for. I just wanted to have lower resolution for a better performance. I am I the only one who is meeting such issues?
Vixificent said:
Thank you for your input! However it is not the solution I am looking for. I just wanted to have lower resolution for a better performance. I am I the only one who is meeting such issues?
Click to expand...
Click to collapse
I tried it and got the same like you.
Sent from my D6503 using XDA-Developers Legacy app
I reduced my resolution to 540x960 and set the dpi to 240. Performance and battery life felt largely the same. Graphics were mostly unaffected except for weird glitches like the ones mentioned in the OP (walkman aka music would straight up stop working though). Text looked blurry, perhaps a subpixel rendering thing.
At the end I returned to 1080p. It was not worth tickling my OCD for little to no benefit.
Thank you for your replies! Wow Pixelado, your resolution was pretty low. Beacause no newer Xperia has that resolution, the Sony apps could cease to work. I wanted to keep something still lower yet 'compatible'.
Yes the performance is pretty much the same. Antutu did not gave a higher score, even gave a lower on CPU and higher on 3D a bit. What I noticed was after playing 3D game for around 20 mins the temperature was around 53C, before in 1080x1920 it was over 61C (in a thin rubber cover). What are your observations?
Best regards,
Vixificent
I came back to 1080p as suggested. Thanks! :good:
Related
Hello Tablet Z community,
This is my first post in this devices forums since getting mine last week. It's a great device, love it, etc.
I've never owned an Android device with a screen resolution this high so I've yet to encounter this problem - some of my games (specifically the emulator PPSSPP) have relatively low framerates (compared to my less powerful Samsung P6810 @ 800x1280). I know with computers in particular it's trivially easy to change resolutions in games/the OS, especially to increase FPS but I've never seen a method to do this on Android and Google searches turn up people mentioning device resolution without changing them.
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change but I would be willing to endure temporarily to increase FPS.
Any advice and suggestions would be greatly appreciated
I would be interested to know about this, iv just loaded ppsspp however havent been able to play any of the playable games listed, I did see a few videos of the xperia z playing well, however that has the same resolution and specs.
juzza87 said:
Does anyone know if it's possible to, ideally, force a different resolution for a particular application? A less than ideal solution would be a system wide change
Any advice and suggestions would be greatly appreciated
Click to expand...
Click to collapse
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Cat McGowan said:
That was recently discussed in this thread: LCD Density Changes and Results (With Pics)
Click to expand...
Click to collapse
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
daveid said:
This is very different, setting the DPI to a non-stock value just resizes the userspace, the resolution is fixed and unchangeable as the OP is thinking. Compared to a Windows PC where you can change the resolution, in Android you only have the ability to change the dpi, which states how large the pixel-to-screen size is. A smaller number indicates a smaller pixel-to-screen size, meaning the information shown on screen is sized for a laeger screen (making it smaller, since the screen is a fixed size). And a larger number has the reverse effect. Android UI guidelines set the optimal dpi for resolution vs. screen size, to mainain a similar experience across devices (similarly sized icons and fonts, etc). Again, this has nothing to do with adjusting the physical resolution of the device, which (to my knowledge) is not possible in Android.
Click to expand...
Click to collapse
Heh. Thanks for the schooling, but it was unnecessary, I didn't just fall off a turnip truck.
Thanks for the replies guys, at least now I know for sure..
[[MODS-Please move to Right Section if needed, Sorry if posted in wrong section]]
I have been trying to get used to the DPI adjustments on the GPe ROM. It appears that the default DPI is set at 400 on install but using ROMToolBox (You can use your favourite app to change DPI), I was able to tweak it to the most optimum number and concluded that DPI 289 is the most comfortable to the eye and compatible with Apps. I went all the way down to early 210s and tracked it all the way up but could not find any DPI better than 289 that accommodated the application options menus, the operation of the camera on the default GPe Lock Screen and the much nicer arrangement of the icons on the App Drawer.
You can off course try to experiment with different setups and share your findings but I think I am on to something. Enjoy the Post!
AWFRONT said:
I have been trying to get used to the DPI adjustments on the GPe ROM. It appears that the default DPI is set at 400 on install but using ROMToolBox (You can use your favourite app to change DPI), I was able to tweak it to the most optimum number and concluded that DPI 289 is the most comfortable to the eye and compatible with Apps. I went all the way down to early 210s and tracked it all the way up but could not find any DPI better than 289 that accommodated the application options menus, the operation of the camera on the default GPe Lock Screen and the much nicer arrangement of the icons on the App Drawer.
You can off course try to experiment with different setups and share your findings but I think I am on to something. Enjoy the Post!
Click to expand...
Click to collapse
wrong section bro,btw try set to 290.
Agree. I've set mine to 290 as well
Sent from my C6806_GPe using xda app-developers app
not GPe, but I have SlimKat set to 280, might just tyr 290 to see what the fuss is about
EDIT:
No real difference at 290 compared to 280, except that chrome popped out of tablet mode at 290
I've used all my android phones till now (galaxy nexus, xperia z and now z ultra) at tablet LCD density (half the default setting) - 160 for ZU, rotation locked on landscape, with large font size and at times custom font types too.
Try DPI 260 its perfect
jutley said:
Try DPI 260 its perfect
Click to expand...
Click to collapse
Thanks for the share but as I stated in my original post, if we want to enjoy using our XZU at its best as a GPe ZU, then the lowest DPI we should go for is 289 for the following reasons; Lock screen is intact with camera shortcut visible, Applications Drawer is more unified and certain applications are better handled with their options/menus visible. At DPI 260 The UI is broken, lockscreen is not complete and applications with menus have their menus missing i.e try RealCalc to see what I mean.
I would really like to hear from anyone who can go much lower than the DPI of 289 and share their findings as to whether the above issues could be experienced. If not I really want to push it as low as possible to get the best out of the XZU screen real estate without compromising stability and completeness of the UI features.
AWFRONT said:
Thanks for the share but as I stated in my original post, if we want to enjoy using our XZU at its best as a GPe ZU, then the lowest DPI we should go for is 289 for the following reasons; Lock screen is intact with camera shortcut visible, Applications Drawer is more unified and certain applications are better handled with their options/menus visible. At DPI 260 The UI is broken, lockscreen is not complete and applications with menus have their menus missing i.e try RealCalc to see what I mean.
I would really like to hear from anyone who can go much lower than the DPI of 289 and share their findings as to whether the above issues could be experienced. If not I really want to push it as low as possible to get the best out of the XZU screen real estate without compromising stability and completeness of the UI features.
Click to expand...
Click to collapse
220 dpi definitely starts to break the UI on slimkat where 280 or 290 (camera on locksceen fails at 280 but works at 290) is good for most apps that I use, I then use app settings and bump a few apps down to 220-240 (gmail etc)
How on earth are you capable of doing anything with a DPI under 200? I can't imagine getting anything done with that kind of DPI when I'm walking, or even standing up. 320 (stock) is in my opinion the best since all UI elements are properly sized and they can be tapped on without having to aim for anything.
Sent from my C6833 using Tapatalk
>Change Screen Resolution<
Introduction:
I'm going to write this guide to teach you how to change the Screen Resolution of your Xiaomi Mi3/Mi4 AOSP/CM Based ROM to improve the graphics performance of your Mi3 without stressing your CPU/GPU while playing games.
What you need to Download:
Resolution Changer by NoMone:
https://play.google.com/store/apps/...apk&pcampaignid=APPU_1_TXl1VcrLFoWB8QXozIGIBA
Root Browser:
https://play.google.com/store/apps/...ser&pcampaignid=APPU_1_oXl1VczIG4_s8AX7-YLQCQ
Note: Default Screen Resolution of Xiaomi Mi 3 is 1080x1920FHD @480 DPI, well what we are going to do is Change it into 720x1280HD @320 to improve performance. (Don't worry about getting the icons bigger, the reason why we have to reduce the DPI on the Build.prop is to avoid glitches and make the Icons and UI at the normal size when changing the resolution, because using the Resolution Changer alone will cause some glitches on other apps )
Steps:
1. Open Root Browser; and find /system/build.prop and open it using RB Text Editor.
2. Find ro.sf.lcd_density=480 and change it to 320.
3. Click Save.
4. Open Resolution Changer; Enter 720 Width, 1280 Height, 320 DPI
5. Click Apply and wait for it to change.
6. Click Yes to Confirm and Skip on the next dialog.
7. Now exit the app and Reboot.
After rebooting, you'll see that you've changed the Screen Resolution to FHD>HD. :good:
Congratulation, to prove it do an Antutu Benchmark test and you'll see the difference. :good:
Additional Info:
(OPTIONAL IF YOU'RE USING CUSTOM DPI ON FULL HD)
If you were using a custom DPI on FULL HD for example;
You're using 400 or 380 or 370 on 1080x1920FHD Resolution,
Do these to properly change resolution to avoid getting the UI or Icons Bigger than Normal.
Example;
If you are using 400DPI on 1080x1920FHD.
400÷3=133DPI
400-133=267DPI
so the right DPI that you're going to use would be; 267DPI on 720x1280HD PLEASE, DONT FORGET to CLICK THANKS!
Everything is working almost perfectly. Some icons are larger than they used to be. But that wasn't problem. Real problem is that SwiftKey keyboard didn't scale. So I had to revert back to Google original keyboard to reset resolution back to 1080p
Sent from my MI 3W using XDA Free mobile app
Silac_8 said:
Everything is working almost perfectly. Some icons are larger than they used to be. But that wasn't problem. Real problem is that SwiftKey keyboard didn't scale. So I had to revert back to Google original keyboard to reset resolution back to 1080p
Sent from my MI 3W using XDA Free mobile app
Click to expand...
Click to collapse
Oh I forgot to write something about Swift Keyboard, Sorry since I used Google Keyboard. but aside from Swiftkey everything is fine :good:
I have done this years ago. Not only CM/AOSP but all rooted phones.
Thanks for putting some guide though. :good::fingers-crossed:
bluerain28 said:
I have done this years ago. Not only CM/AOSP but all rooted phones.
Thanks for putting some guide though. :good::fingers-crossed:
Click to expand...
Click to collapse
I wrote this guide for those who are confused and experiencing glitches when using the Resolution Changer alone and of course for the beginners
added additional info.
I just noticed. I used 294 DPI for 720x1280
bluerain28 said:
I just noticed. I used 294 DPI for 720x1280
Click to expand...
Click to collapse
Alright! ?
Initially tried this with MIUI v5, turned out to be very bad. The icons became very large and going to back to native resolution didn't help either. Fortunately I had nandroid backup.
Later I tried it on MIUI 6, it worked!
Some glitches are there:
- On recent apps screen
- camera effects selection screen
- Calender and clock icons turned invisible
- Minor glitches in clock app
Otherwise everything looks good, and performance bump is noticeable. Excited to find out how much it improves battery life.
Thanks for sharing.
pra300 said:
Initially tried this with MIUI v5, turned out to be very bad. The icons became very large and going to back to native resolution didn't help either. Fortunately I had nandroid backup.
Later I tried it on MIUI 6, it worked!
Some glitches are there:
- On recent apps screen
- camera effects selection screen
- Calender and clock icons turned invisible
- Minor glitches in clock app
Otherwise everything looks good, and performance bump is noticeable. Excited to find out how much it improves battery life.
Thanks for sharing.
Click to expand...
Click to collapse
No problem
that's why it's for CM/AOSP Based ROM but I'm glad that it worked for you though there are some glitches.
Hi im using a a33 tab with screen dpi 160 and 480x800 resolution. Can I change this to higher resolution and dpi?
sent from xda app in my s710 using tapatalk . (*ﾟ▽ﾟ)ﾉ
andywoody12 said:
Hi im using a a33 tab with screen dpi 160 and 480x800 resolution. Can I change this to higher resolution and dpi?
sent from xda app in my s710 using tapatalk . (*ﾟ▽ﾟ)ﾉ
Click to expand...
Click to collapse
You can but, I won't recommend it because it would just stress out the processor and gpu of that low-end tablet, just leave that be.
Better use gl tools
While everyone gets larger icons,i am getting small icons,small screen,and all the app including resolution changer itself says the current settings is 1080x1920 with 320dpi.
Where am i doing it wrong?
I am on cm12 latest nightly.
same problem as Jongla here, running the same CM 12 nightlies. I guess the problem is that resolution changer doesnt change anything after you apply, current settings are kept as FHD res. Maybe try a different app to do it.
QQboss said:
same problem as Jongla here, running the same CM 12 nightlies. I guess the problem is that resolution changer doesnt change anything after you apply, current settings are kept as FHD res. Maybe try a different app to do it.
Click to expand...
Click to collapse
Try this method.Its easier and works just fine.
http://nexus5.wonderhowto.com/how-t...xus-6-by-lowering-display-resolution-0159881/
thanks buddy, this one works like a charm
cool trick..
It's become blurry, not clear like before
Guys, if you're using a CM rom, just install Xposed and install the App Setting module. Then, you just choose the app, turn on the custom settings, choose the resolution and dpi you want, and the app will run with those defenitions without having to mess with the entire UI on the device...
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
webleeper said:
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
Click to expand...
Click to collapse
Sorry, don't know. Probably issue related to rooting and the settings you changed.
Thanks for the quick reply but I'm not rooted.
webleeper said:
@duraaraa any info or direction that you can provide on this?
I upped the resolution from stock 1080x2160 to 2160x4320 and left dpi at stock so I can have more screen real estate and still have a comfortable viewing experience. The issue I'm facing now is, I cannot capture a screenshot I get an error.
System UI
Couldn't Capture Screenshot
Screenshots are not allowed by this app or your organization.
steps to reproduce:
up your resolution to 2160x4320 and take a screenshot
Any guidance would be appreciated.
Click to expand...
Click to collapse
Mate 10 pro panel is only 1080p to begin with,
In what way did you upped the resolution ?? The setting wont give you that resolution option.
otonieru said:
Mate 10 pro panel is only 1080p to begin with,
In what way did you upped the resolution ?? The setting wont give you that resolution option.
Click to expand...
Click to collapse
no need for root or settings to change DPI or Resolution
adb shell wm size 2160x4320
adb shell wm overscan reset
webleeper said:
no need for root or settings to change DPI or Resolution
adb shell wm size 2160x4320
adb shell wm overscan reset
Click to expand...
Click to collapse
uh... well... you already understand that this method is "only faking" the number for the app to think that it run on that size of screen right ? Hardware & stock OS wise, the limitation is still on 1080p
I dont think the system UI app of EMUI 8 itself was made to handle that number
Normal 4K itself is only 3840 x 2160, and i dont think i ever found any phone running 4K+ (18:9)
This is just like asking why sometimes the play store act weird when we change our DPI
So answer is that : because it simply didn't support it
I've done #wm size 720x1280 & wm density 320 to 720p screen for long battery life. and I found the system's screenshot can not take whole screen(720p one).
It looks like the screenshot component take a 480p screen and the same 720p adjusting on AEX 5.x is fine.
so I thought maybe the screenshot on pie still mistake 720p screen for 1080p screen and take a 480p picture（expect: 1080p x 720/1080 = 720p, but now: 1080p x 720/1080 x 720x1080 = 480p）
But I notice that keep wm size 1080x1920, whatever which density（320 480 240）I've set, the screenshot could take a complete screen picture. while I change density, whatever resolution (720x1280, 480x800, 1080x1920), screenshot just take the top left part of screen...
partial screenshot is same condition , take a top left part of what I selected .
the screenshot on different resolution is the last issue I can found on AEX 6.0, which not contain on AEX5.x（maybe this is pie issue but still expect you can fix it） if I don't need change the resolution, the ROM is PERFECT?
can you fix this ?? thxxxxx a lot
XDrz said:
I've done #wm size 720x1280 & wm density 320 to 720p screen for long battery life. and I found the system's screenshot can not take whole screen(720p one).
It looks like the screenshot component take a 480p screen and the same 720p adjusting on AEX 5.x is fine.
so I thought maybe the screenshot on pie still mistake 720p screen for 1080p screen and take a 480p picture（expect: 1080p x 720/1080 = 720p, but now: 1080p x 720/1080 x 720x1080 = 480p）
But I notice that keep wm size 1080x1920, whatever which density（320 480 240）I've set, the screenshot could take a complete screen picture. while I change density, whatever resolution (720x1280, 480x800, 1080x1920), screenshot just take the top left part of screen...
partial screenshot is same condition , take a top left part of what I selected .
the screenshot on different resolution is the last issue I can found on AEX 6.0, which not contain on AEX5.x（maybe this is pie issue but still expect you can fix it） if I don't need change the resolution, the ROM is PERFECT
can you fix this ?? thxxxxx a lot
Click to expand...
Click to collapse
Who is gonna fix what? Just use the phone the way its supposed to be used i dont understand what you are doing and why. If anyone, huawei can fix your issue i guess.... good luck talking to them.
You should read this, particularly the long answer near the top which explains the size vs density changes.
https://stackoverflow.com/questions...to-use-adb-shell-wm-to-simulate-other-devices
I think this is actually a bug in android pie. My phone has a 4k display, but normally uses HD res unless in gallery app. So I changed wm size and density to match the display (and despite what some other say, this actually changes the visible resolution, IF your display has this many physical pixels).
Screenshots worked worked fine in oreo, but after updating to pie, there are black borders on the picture.
Display
Spodi2290 said:
I think this is actually a bug in android pie. My phone has a 4k display, but normally uses HD res unless in gallery app. So I changed wm size and density to match the display (and despite what some other say, this actually changes the visible resolution, IF your display has this many physical pixels).
Screenshots worked worked fine in oreo, but after updating to pie, there are black borders on the picture.
Click to expand...
Click to collapse
No Huawei phone has a 4k display, this whole thread is a waste of space really, guy setting his phone display to something that is not supported and wondering why his screenshot won't work, damn mate 10 pro is 2160x1080 and can't be any more than that, if the problem was the screenshots not working in a supported mode there might be a reasonable and were but as it stands this thread should be closed and deleted
revjamescarver said:
No Huawei phone has a 4k display, this whole thread is a waste of space really, guy setting his phone display to something that is not supported and wondering why his screenshot won't work, damn mate 10 pro is 2160x1080 and can't be any more than that, if the problem was the screenshots not working in a supported mode there might be a reasonable and were but as it stands this thread should be closed and deleted
Click to expand...
Click to collapse
The whole point of my post was more like: its not a Huawei only "bug", but effects all (or at least most) pi phones with a custom wm size set. Maybe I was beating around the bush too much... :angel:
Spodi2290 said:
The whole point of my post was more like: its not a Huawei only "bug", but effects all (or at least most) pi phones with a custom wm size set. Maybe I was beating around the bush too much... :angel:
Click to expand...
Click to collapse
Hi, have you found any solution for the screenshots when you change the screen resolution? You're right it happens only in pie and with different phones, in oreo the multitasking previews resize when you enter to the app but the screenshots are ok, in oreo the previews in multitask are ok but the screenshot miss a part of the screen.
I have just bought 10.8 version and I like it, but was really surprised to find out there is no way to change resolution like for example in this video (I am not allowed to post links, but you can search it on youtube under the name: How to Change Screen Resolution in HUAWEI P20)
Is that a bug of some kind and we may hope that this feature will be introduced in some later EMUI updates?
With developer options enabled you can set a custom DPI, effectively changing your resolution
This method doesn't actually change resolution, just the size of the icons, text etc. You can try and check it yourself with some app like CPU-Z for example.
The only option I found is using ADB commands like "wm size 1200x1920" and "wm density 209". This does truly change resolution and sets appropriate DPI for this resolution at 10.8 display size. Needless to say that this method is cumbersome and besides that DPI value has to be reapplied after each reboot, otherwise it resets and homescreen looks messed up.
But yes, when set correctly to 1200x1920 and 209 DPI it looks good and what's more important games run a lot faster.
So why would Huawei remove the option (which is already present in EMUI 8) to easily change resolution specifically for our device is beyond my understanding.
And here is reply from Huawei support:
Thank you for contacting Huawei. We widely appreciate your preference and we thank you for your email.
Regarding to what you kindly shared to us, we appreciate that you point out this issue, we kindly inform you that your screen resolution is unable to be modified unless it is done through a third party application. Due to this, we have forwarded your request to our Research and Development department. Receiving your feedback and inquiries means a lot to our company, since our only way to improve is through acknowledging our customer's experiences.
Yeah it doesn't change the resolution but your command shouldn't either because the same amount of pixels is used. Changing the resolution is basically only possible with amoleds (which we don't have) because single pixels can be disabled.
So that's probably the reason why the huawei p20 has it and we don't. As for what you are doing it should be the same as changing dpi. Grouping small physical pixels to one bigger virtual pixel, decreasing the amount of different content the tablet has to render and therefor making the tablet run faster.
I was able to set my screen res to something else using a third party app on my note 2 (amoled) but not anymore on the LG g5 (ips LCD)
Hope what I'm trying to say is understandable.
lolmensch said:
Hope what I'm trying to say is understandable.
Click to expand...
Click to collapse
Hehe, my honest answer is not quite. But I would appreciate if you could tell me which DPI should I set in Developer Options to get the same effect as I am getting with "wm size 1200x1920" and "wm density 209" in terms of speed gain and homescreen look (not distorted or messed up, etc).
Edit: Tried changing DPI only without changing resolution today. Result: no speed gain in any games I played.
I'm using this app to change resolution and dpi.
https://play.google.com/store/apps/details?id=com.farmerbb.secondscreen.free
It required root access (I'm using magisk). But author said that it just need adb access for those don't have root. Works brilliantlu on my M5 8.4.
oldpoem said:
I'm using this app to change resolution and dpi.
https://play.google.com/store/apps/details?id=com.farmerbb.secondscreen.free
It required root access (I'm using magisk). But author said that it just need adb access for those don't have root. Works brilliantlu on my M5 8.4.
Click to expand...
Click to collapse
For the M5 8.4, what did you set things to?
Ivanbarker said:
For the M5 8.4, what did you set things to?
Click to expand...
Click to collapse
I created 2 profile. One for casting to TV , other for lower resolution.
Ivanbarker said:
For the M5 8.4, what did you set things to?
Click to expand...
Click to collapse
As far as I undertand to avoid distortion for your 8.4in it should be something like 1920x1200 and 270 DPI.
Though again, as far as I understood, you can play with DPI as much as you like, it doesn't influence game speed or battery drain like resolution does.
oldpoem said:
I'm using this app to change resolution and dpi.
https://play.google.com/store/apps/details?id=com.farmerbb.secondscreen.free
It required root access (I'm using magisk). But author said that it just need adb access for those don't have root. Works brilliantlu on my M5 8.4.
Click to expand...
Click to collapse
Thanks, I am going to check out this app. The problem is that I don't want to root my M5 in order not to void the warranty. So going to try the ADB way and hope permissions will not reset after reboot.
the_zealot said:
Thanks, I am going to check out this app. The problem is that I don't want to root my M5 in order not to void the warranty. So going to try the ADB way and hope permissions will not reset after reboot.
Click to expand...
Click to collapse
After you've lowered your resolution from stock 2560x1600, do you find better battery life?
EDIT: Also if I want to change it back to normal, do I jsut change the resolution back to 2560x1600 and 359 dpi?
Ivanbarker said:
After you've lowered your resolution from stock 2560x1600, do you find better battery life?
EDIT: Also if I want to change it back to normal, do I jsut change the resolution back to 2560x1600 and 359 dpi?
Click to expand...
Click to collapse
I have not been using this tablet long enough to notice major difference in battery drain from changing resolution. I was mostly interested in speed gain in games. But from the fact that there is an option in Settings menu to automatically lower resolution to save battery, I conclude that there must me some (albeit a small) advantage in overall power consumption when using lower resolution.
And yes, to get back your native resolution and DPI, I guess you can either use ADB commands "wm size reset" and "wm density reset", or just set 2560x1600 if you are doing it through an app. As for DPI, it depends on which display settings you use in the Settings menu (large, small, etc.) but the default (factory) one seems to be 480. All this Resolution-DPI stuff seems to be very confusing as for me.
the_zealot said:
And yes, to get back your native resolution and DPI, I guess you can either use ADB commands "wm size reset" and "wm density reset", or just set 2560x1600 if you are doing it through an app. As for DPI, it depends on which display settings you use in the Settings menu (large, small, etc.) but the default (factory) one seems to be 480. All this Resolution-DPI stuff seems to be very confusing as for me.
Click to expand...
Click to collapse
Thanks! I was unaware you could reset it like that!