CM12.1 support DPI adjustment natively (if you see some apps still show bigger font, then try modify the build.prop to same value, this may help.)
========================
B320/B322 update screwed up below DPI adjustment. Thanks @medwatt testing, see #45 for details. For values like 240 or 260, the phone is completely blank, and if you do 'adb shell logcat *:E', you can see the resource not found error all over the place.
========================
Edit on July 3, 2015:
On Lollipop B309, the ro.sf.lcd_density is in build.prop already and set to 320, we can change it to smaller value: (make a backup first)
Code:
ro.sf.lcd_density=240
you can use any number between 240 to 320. Save then reboot. (Thanks @ArkAngel06 point out this entry still works)
Then everything is working fine. No expose needed and didn't see any big problem so far.
One problem we noticed is stock 'Browser' app FC, pls use your favorate 3rd party browser instead. (The one i currently use is boat browser)
========================
Following is original post for JellyBean 4.3
===Normal disclaims applies, be careful and know how to use adb to restore /system/build.prop before you try this=============
You phone may brick if this file got corrupted.
ROOT is required to change the LCD density.
Today trying to play around the DPI of display, and noticed the stock value is 320:
Code:
getprop | grep dens
[ro.sf.lcd_density]: [320]
But our 720p display native DPI is 240. That's why all the stuff display so big??
Anyway, I backed up /system/build.prop, and play a little bit.
I recommend simply use Root Browser with "RB Text Editor" to do the task. Other DPI changer app may work and convenient, but it is more risky and may do some change unknown to the phone. Due to lack of backup/restore recovery right now, I prefer manually editing the file myself.
Adding following to the end of /system/build.prop.
Code:
ro.sf.lcd_density=264
For some different varies like Consumer Cellular version, or MT2L05 version, you can try following if above doesn't work:
qemu.sf.lcd_density=264
Not sure it is a bug or what, when I use ES file explorer to edit the file, If I select edit mode right after open the file, it won't scroll to the end of file. I have to scroll to the end first in view mode, then select edit mode. Anyway, Root Browser editor works without any problem.
Following is some test result:
Code:
______________ System UI________ Settings__________ Gallery
180__________force close
200______________ok____________ force close______ force close
220______________ok____________ force close______ force close
240(native)______ok____________ force close______ force close
260______________ok____________ force close______ force close
264______________ok________________ ok____________force close
280______________ok________________ ok____________force close
320(stock)______ ok________________ ok________________ ok
Also, for all DPI less than 320, the stock lock screen shortcut is not displayed properly.
I think I will stick with 280 (update, now I am using 264) for a few days and see if I found more problems. And it should be easy to find an alternative gallery app.
The smaller font and everything actually make the display more clear and sharp
PS. I know there is font size in display settings, but the DPI change will make system zoom everything based on this new display density.
Thanks aragon257 and others feedback, some info from below is collected from the replies. Thanks.
MORE INFO/UPDATE:
. There is Exposed framework modules (like app settings) to do per app DPI settings. Please see end of this post for more info.
. The app force closing caused by lower DPI is purely software (view layout arrangement) issue, so lowering DPI will not do any harm to hardware.
. List of Apps that Force Close. I list them from higher DPI to lower DPI, The apps that crashes in higher DPI will also crash in lower DPI.
DPI 264 or 280: Currently I am using 264.
Lock Screen: No crash here. The app short cut moved to center of the circle, and requires less distance swipe to unlock.
Gallery (Also affecting camera since it start Gallery when you view pictures)
Alternative: "Galleray KK" and "Camera KK" from play store works pretty good, though it is Ads supported.
DPI 240:
Settings
Phone app when receiving calls.
Use Xposed Framework
OK, set DPI to 240 in build.prop, I need use Xposed module "App Settings" to set following App DPI to higher value to make the phone fully work:
Code:
Gallery(com.android.gallery3d): 297 (dp: 320x480)
Phone(com.android.phone): 264
Settings(com.android.settings): 264
SystemUI(com.android.systemui): 264
This number is set to lowest possible value, of course you can set to 320, then related apps will be bigger.
Please see attachment for some screenshot: (Left is stock 320 DPI, right is 264 DPI)
Thanks for doing all the research here
Use xposed and install app settings. Use it to give those apps that crash the default DPI. Just tried working great. And thanks about the tip of adb build.prop backing up.
Running at 240 DPI here.
Edit: Play store wouldn't download anything until I cleared the cache.
Edit again: Actually viewing images and trying to use the camera causes the gallery to crash... Ill fix it
FINAL Edit: Installed the kitkat camera and gallery. I had to unisntall the old gallery first. This works for me
Great, that xposed module is pretty cool, but for now I must resist as we don't have recovery yet
BTW, I have updated first post to correct the System UI FC number, it is 180, not 220. ie, DPI can be as low as 200 and the phone is still usable. So, native 240 is a pretty safe value.
Also, the "Huawei home" FC start showing up from 220 and below, though I am using Nova launcher.
Cheers.
I was having problems with incoming calls crashing the phone app. So back to 320, but using App Settings to change my downloaded apps to 240
Admired by this thread:
http://forum.xda-developers.com/galaxy-nexus/general/info-official-galaxy-nexus-lcd-density-t1392089
Call me bored, today I have tried more DPIs, and found 264 is the lowest number that Settings is working. Since the crashing is just cause by GUI view arrangement issue, nothing to do with hardware etc. So I will stick with 264 for now.
For the past few days with settings 280, I only noticed gallery is the problem. I didn't try too much widget/apps. Everything else I tried works pretty good.
Please refresh my memory, is lowering the DPI making the image smaller? If so, im interested.
yes, everything (font,icon,layout)will be smaller. but image actually maybe different story. try and see yourself!
so what apps are better in tablet mode for me to try?
Bobvark said:
so what apps are better in tablet mode for me to try?
Click to expand...
Click to collapse
I didn't use any particular tablet mode etc stuff, the lower DPI gives me more space asset, thats all.
xordos said:
I didn't use any particular tablet mode etc stuff, the lower DPI gives me more space asset, thats all.
Click to expand...
Click to collapse
ok, so Chrome, gmail, what would be good DPI for those? I'm a little worried about f'n up my phone and don't just want to do trial and error.
Is 240 the standard you all are using?
Bobvark said:
ok, so Chrome, gmail, what would be good DPI for those? I'm a little worried about f'n up my phone and don't just want to do trial and error.
Is 240 the standard you all are using?
Click to expand...
Click to collapse
264 or 280 should be safer. 240 the settings app wont work.
Added some screenshot to the 1st post.
I wanna mess with this later
aragon257 said:
I was having problems with incoming calls crashing the phone app. So back to 320, but using App Settings to change my downloaded apps to 240
Click to expand...
Click to collapse
ok, now with a twrp backup taken, I installed xposed and now i got exact same problem. 240 is really sweet dpi, even the lock screen layout is good.
I tried complete delete phone.apk, and contacts.apk, but looks like not easy to find a good replacement. other dialer app from play store still requires these two apks. And i checked my other phone 4.3 rom, they force close. will continue to the search.
Have you tried it with the xposed programs? I know it worked for gallery but not sure for settings.
oncouch1 said:
Have you tried it with the xposed programs? I know it worked for gallery but not sure for settings.
Click to expand...
Click to collapse
Thanks. Didn't try gallery with app settings module yet. For 240 dpi, call out/in problem is what I am focused on right now.
Was trying app settings with 240, I set phone dialer etc. at stock setting but forgot had face lock so when I restarted, crash due to camera (what a [email protected]!) Thank you guys for TWRP so I could restore! . On vacation and no PC to try and adb to modify build.prop.
Sent from my MT2L03 using XDA Free mobile app
xordos said:
Thanks. Didn't try gallery with app settings module yet. For 240 dpi, call out/in problem is what I am focused on right now.
Click to expand...
Click to collapse
yes, with exposed module, at 240 dpi, gallery/camera works fine, settings also worked, only phone app still FC. so now i am at 264, and use exposed to fix gallery.
Silly question, app settings didn't work on dialer?
oncouch1 said:
Silly question, app settings didn't work on dialer?
Click to expand...
Click to collapse
when calls come in, phone apps FC when dpi is 240 ( and app settings use 320 for com.android.phone)
EDIT:
OK, Maybe this defeat the purpose, set SystemUI to 264 resolve the incoming call problem. The incoming call crashed the phone app because the StatusBar trying to get a phone icon resource but failed.
To summary, In build.prop DPI set to 240, I need use Xposed "App Settings" to set following App DPI to higher value to make the phone fully work:
Code:
Gallery(com.android.gallery3d): 297
Phone(com.android.phone): 264
Settings(com.android.settings): 264
SystemUI(com.android.systemui): 264
This number is set to lowest possible value, of course you can set to 320, then related apps will be bigger.
Related
Hello
Can i change dpi stock 240. Someone have tested?
kvadde said:
Hello
Can i change dpi stock 240. Someone have tested?
Click to expand...
Click to collapse
A solid-state screen's DPI is a physical attribute, you cannot change it.
I believe OP is referring to the soft DPI settings in build.prop. You must root, then edit the ro.sf.lcd_density setting in build.prop. It's already 240 on CM, not sure about stock though.
Cat McGowan said:
A solid-state screen's DPI is a physical attribute, you cannot change it.
Click to expand...
Click to collapse
You are talking about PPI, not DPI
Stock DPI is also 240.
But why would you want to change that??
If some app is not displaying to your satisfaction, it's better not to modify build.prop, because it could lead to unexpected weird behaviors.
Better is to use the "Xposed Framework" with the module "App Settings"; there you can specify individual DPI settings for each app. The safer and more flexible solution! I use it without problems on all my devices.
Felimenta97 said:
You are talking about PPI, not DPI
Click to expand...
Click to collapse
You have it backwards.
kvadde said:
Hello
Can i change dpi stock 240. Someone have tested?
Click to expand...
Click to collapse
As you didn't specify whether you want this on stock firmware or an AOSP ROM, I'd suggest to try the PACman port to the XTZ, as it includes per-app DPI modifier. It's currently in nightlies and no fully stable release as of yet, but it's worth to try if you really need that feature.
DPI = Dots Per Inch
PPI = Pixels Per Inch
The reason we've started to use PPI instead of DPI is because of PenTile, since that technology yields more pixels than dots per inch (dots are shared between adjacent pixels). Both are properties of the hardware but by telling Android you have a different DPI you can scale the UI. This procedure will make graphical elements that makes use of their physical size on the display (rulers, printing tools, etc.) show up at incorrect sizes.
For example, if you have a virtual measurement tape, you'll need to multiply all values with the original DPI divided by the new DPI. So if you choose to change your tablets DPI to 120, making every UI element scale to half of the original size, you'd need to multiply every value by 240/120=2 for it to match up with the real world.
I hope this clears things up.
Shanliang- said:
As you didn't specify whether you want this on stock firmware or an AOSP ROM, I'd suggest to try the PACman port to the XTZ, as it includes per-app DPI modifier. It's currently in nightlies and no fully stable release as of yet, but it's worth to try if you really need that feature.
Click to expand...
Click to collapse
As I already said: No need to change firmware. Just install Xposed framework with App Settings module on rooted device, and you can freely modify DPI per app.
[[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...
Now that we have root and kernel adiutor, we might be able to change the dpi to the screen dpi with it.
Has already someone changed this?
According to the dpi calculator:
https://www.sven.de/dpi/
We should have ~197 dpi, but there is 280 in the build.prop
Actually how many dpi does our watch have?
I set the calculator above to 2.3 so the result reads 1,63x1,63 display.
But other calculators are different...
Change it for whole android is not perfect. Try instead the Xposed module app settings to change dpi for specific apps.
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!