I purchased the Nexus 4, 5, and 6 as each has come out. I love the devices, as well as the toolkit.
My issue is this, all of the roms available operate in 'Phone mode' which is useless to me, as the games and apps I use need to run in TABLET mode. I didn't even know there was a difference until I tried numerous other ROMS and had no luck.
Only Slimkat and SlimLP (to my knowledge) run applications in tablet mode, allowing for a much, much better viewing experience.
Without going through all of the methods described in previous threads about the 'XPosed Framework', is there a custom ROM that offers tablet mode functionality like the SlimRoms?
I would prefer to just stick to SlimLP, but it is extremely buggy, and causes me many problems on a daily basis, especially with phone calls, and this is the phone i use for work, and I cannot afford to keep having issues such as the ones with SlimLP until the bugs are worked out.
Any suggestions? Thanks in advance!
flash any rom then change the dpi to set it into "tablet" mode. thats how slim did it, its not a special mode. by default, the n6 dpi is 560, lower it to below 400, like 390 or something. and you have a nexus, it doesnt need a toolkit, as it easier to do things the right way. learn the right way to do things.
simms22 said:
flash any rom then change the dpi to set it into "tablet" mode. thats how slim did it, its not a special mode. by default, the n6 dpi is 560, lower it to below 400, like 390 or something. and you have a nexus, it doesnt need a toolkit, as it easier to do things the right way. learn the right way to do things.
Click to expand...
Click to collapse
OK, so learn the right way to do things. Again, I Googled this already, and was driven to installing something called the XPosed Framework, which I do not want to deal with. So the 'right way' according to some pretty exhaustive Googling comes up with nothing about DPI or it's built in functionality, which is what I am asking for.
Is there any simple way to do what I need to do. If not then that is fine, but changing DPI is not available in any of the ROMs I am aware of, and if it is, please let me know which ones there may be.
I am not an android developer or debugger, I am simply an end user looking to enjoy my phone. I don't know what 'it doesn't need a toolkit' means, but I do know I had to root using Wugfresh's toolkit.
Doesn't changing the DPI affect the amount of pixels I am able to see? Or does it only affect applications?
SidedX said:
OK, so learn the right way to do things. Again, I Googled this already, and was driven to installing something called the XPosed Framework, which I do not want to deal with. So the 'right way' according to some pretty exhaustive Googling comes up with nothing about DPI or it's built in functionality, which is what I am asking for.
Is there any simple way to do what I need to do. If not then that is fine, but changing DPI is not available in any of the ROMs I am aware of, and if it is, please let me know which ones there may be.
I am not an android developer or debugger, I am simply an end user looking to enjoy my phone. I don't know what 'it doesn't need a toolkit' means, but I do know I had to root using Wugfresh's toolkit.
Doesn't changing the DPI affect the amount of pixels I am able to see? Or does it only affect applications?
Click to expand...
Click to collapse
many, if not most custom roms, have an option to change the dpi in that roms settings. im using terminus, and it has an option to change the dpi. also, you can change the dpi in your build.prop(then reboot to have it take affect). there are also apps that you can use to change your dpi.
simms22 said:
many, if not most custom roms, have an option to change the dpi in that roms settings. im using terminus, and it has an option to change the dpi. also, you can change the dpi in your build.prop(then reboot to have it take affect). there are also apps that you can use to change your dpi.
Click to expand...
Click to collapse
Thanks, I'll do a full backup, and I will mess around. I honestly wish I had asked sooner, as SlimLP has been disastrous.
Thank you again.
SidedX said:
OK, so learn the right way to do things. Again, I Googled this already, and was driven to installing something called the XPosed Framework, which I do not want to deal with. So the 'right way' according to some pretty exhaustive Googling comes up with nothing about DPI or it's built in functionality, which is what I am asking for.
Is there any simple way to do what I need to do. If not then that is fine, but changing DPI is not available in any of the ROMs I am aware of, and if it is, please let me know which ones there may be.
I am not an android developer or debugger, I am simply an end user looking to enjoy my phone. I don't know what 'it doesn't need a toolkit' means, but I do know I had to root using Wugfresh's toolkit.
Doesn't changing the DPI affect the amount of pixels I am able to see? Or does it only affect applications?
Click to expand...
Click to collapse
OK so although some ROMs add "DPI" options in settings, it is not needed. DPI as always is changed in /system/build.prop under LCD density.
As for pixels, that's PPI not DPI. DPI is not related to pixels in any way. DPI is a scaling method.
Think of it this way, if you have a 5".display with 1080 pixels by 1920 pixels, you have a HD display with a very specific amount of pixels. If you have a 10" tablet with the same amount of pixels, each pixel would be bigger. Therefore, everything on a screen would be bigger. This means a tablet would have everything too big and you wouldn't take advantage of a bigger screen. So android use something called DPI to scale objects on the screen. Smaller DPI makes everything smaller on screen. This way, you take advantage of more screen real estate. Apps etc can use lower DPI to identify a phone from a tablet and they will act differently if those apps have a tablet "mode".
There are no real links between pixels. Just the bigger the screen and lower resolution, the lower the DPI needs to be and the smaller the screen with a higher resolution, the higher the DPI should be.
rootSU said:
As for pixels, that's PPI not DPI. DPI is not related to pixels in any way. DPI is a scaling method.
Think of it this way, if you have a 5".display with 1080 pixels by 1920 pixels, you have a HD display with a very specific amount of pixels. If you have a 10" tablet with the same amount of pixels, each pixel would be bigger. Therefore, everything on a screen would be bigger. This means a tablet would have everything too big and you wouldn't take advantage of a bigger screen. So android use something called DPI to scale objects on the screen. Smaller DPI makes everything smaller on screen. This way, you take advantage of more screen real estate. Apps etc can use lower DPI to identify a phone from a tablet and they will act differently if those apps have a tablet "mode".
There are no real links between pixels. Just the bigger the screen and lower resolution, the lower the DPI needs to be and the smaller the screen with a higher resolution, the higher the DPI should be.
Click to expand...
Click to collapse
Wow, OK. I always thought I would be turning my 1440p QHD display into a 1080p. Never knew there was a difference.
Thank you. This forum has been the most helpful, and I honestly should have come here first instead of spending over a month on my own fighting with this device.
SidedX said:
Wow, OK. I always thought I would be turning my 1440p QHD display into a 1080p. Never knew there was a difference.
Thank you. This forum has been the most helpful, and I honestly should have come here first instead of spending over a month on my own fighting with this device.
Click to expand...
Click to collapse
Yeah completely different. You don't lose any resolution or image quality by lowering the DPI. I set mine at 400. Not for "tablet" or anything. I just like the look of everything at that size instead of the giant size of 563 or whatever it is by default.
But yeah, you're welcome
Related
Been playing with the Bionic for a day now, (came from LG G2X) and it's pretty amazing. Have it all rooted and such.
Used "Root Explorer" and decided to changed the density from 240 to 190. Looks very nice on that big screen. Everything seems to be working normally, except the lock screen is a little funky. But I didn't mind.
I've never done or heard of changing the pixel density before. What does it do and how did you do it please?
art0605 said:
Been playing with the Bionic for a day now, (came from LG G2X) and it's pretty amazing. Have it all rooted and such.
Used "Root Explorer" and decided to changed the density from 240 to 190. Looks very nice on that big screen. Everything seems to be working normally, except the lock screen is a little funky. But I didn't mind.
Click to expand...
Click to collapse
Ohhhhh. If you have used ROMS for other phones, for me it was the X, then you would know about that. Like "Liberty toolbox" and not other "Tool-boxes" let you turn screen settings up or down. To the thread starter, any way to get a pic of "Before" and "After"?
mikecheat04 said:
I've never done or heard of changing the pixel density before. What does it do and how did you do it please?
Click to expand...
Click to collapse
It's an effect you put on the framebuffer to give the illusion of having a higher resolution on your phone. If you lower the pixel density value, it will make everything more spaced out and smaller in general, giving the illusion of the phone having a higher resolution. It adds nothing besides a placebo affect and breaks certain things, such as the lockscreen and the background image for the pull-down bar. If you don't care about those things, you can try it out and test it for yourself. I recommend a value of 200.
Check out lcd density in the market, it is free and there are some screen shots. I have mine set at 200. Make sure to get spare parts from the market and turn off compatibility mode to make some of the troublesome apps fill the screen.
200/220 seems to be the nicest with the pentile display and century gothic as the new stock font, anything lower and you really really see the pixels...bleh
since I changed the stock DPI to 520(via ADB) , I'm having a couple apps acting out, SwiftKey being the main offender to the point is rendered useless
I tried clearing data/uninstall but it didn't solve the issue. I'm stock rooted. Anyone knows how to fix this?
Change your DPI back. You can't modify system appearance and expect everything to cooperate!
Donjuanal said:
Change your DPI back. You can't modify system appearance and expect everything to cooperate!
Click to expand...
Click to collapse
^^^ This.
I am using 380 dpi and it works great on everything though. 380 puts the phone into tablet mode, but using dpi numbers that are not necessarily tied to anything can cause issues.
EniGmA1987 said:
^^^ This.
I am using 380 dpi and it works great on everything though. 380 puts the phone into tablet mode, but using dpi numbers that are not necessarily tied to anything can cause issues.
Click to expand...
Click to collapse
Dang. That would make everything tiny.
sgloki77 said:
since I changed the stock DPI to 520(via ADB) , I'm having a couple apps acting out, SwiftKey being the main offender to the point is rendered useless
I tried clearing data/uninstall but it didn't solve the issue. I'm stock rooted. Anyone knows how to fix this?
Click to expand...
Click to collapse
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Sent from my Nexus 6 using Xparent BlueTapatalk 2
Skripka said:
Dang. That would make everything tiny.
Click to expand...
Click to collapse
Na, it's perfect size. You get to see so much on screen without everything being so small you cant read it.
nexus6R3plicant said:
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Click to expand...
Click to collapse
Really? I never knew that. Odd that 380 works perfect since that is not a multiple of 80 and it puts the Nexus 6 into tablet mode. Ill try 400 later and see how it is.
EniGmA1987 said:
Na, it's perfect size. You get to see so much on screen without everything being so small you cant read it.
Really? I never knew that. Odd that 380 works perfect since that is not a multiple of 80 and it puts the Nexus 6 into tablet mode. Ill try 400 later and see how it is.
Click to expand...
Click to collapse
The first ones had DPI of 160 then the s2 etc was 240 etc and so forth
Sent from my Nexus 6 using Xparent BlueTapatalk 2
finally got it to work
I used BuildProp Editor and changed the line ro.sf.lcd_density 520 for a 520 DPI
all apps are scaling correctly now no need to go back to those gigantic icons on stock DPI
sgloki77 said:
finally got it to work
I used BuildProp Editor and changed the line ro.sf.lcd_density 520 for a 520 DPI
all apps are scaling correctly now no need to go back to those gigantic icons on stock DPI
Click to expand...
Click to collapse
I was able to change my density using the following ADB shell commands, but it caused a few glitches with apps as others mentioned (Play Store, KeePass2Android keyboard, DSub, etc):
Code:
adb shell
wm density 480
exit
Perhaps those glitches are due to the build.prop still having the default density after applying ADB shell commands:
Code:
ro.sf.lcd_density 560
Next, I tried using a couple of different build prop editing apps, but none actually change the file even though I'm granting root access. Can anyone advise why this might be? Which app specifically did you use (play store link)?
Another method I tried was editing a copy of build.prop using a text editor, then used TWRP to replace the original and set permissions to 644. This caused my phone to get stuck at the colored dots boot screen, and forced me to do a nandroid restore in TWRP.
Seems like this should be easier...any advice?
acc3d said:
I was able to change my density using the following ADB shell commands, but it caused a few glitches with apps as others mentioned (Play Store, KeePass2Android keyboard, DSub, etc):
Code:
adb shell
wm density 480
exit
Perhaps those glitches are due to the build.prop still having the default density after applying ADB shell commands:
Code:
ro.sf.lcd_density 560
Next, I tried using a couple of different build prop editing apps, but none actually change the file even though I'm granting root access. Can anyone advise why this might be? Which app specifically did you use (play store link)?
Another method I tried was editing a copy of build.prop using a text editor, then used TWRP to replace the original and set permissions to 644. This caused my phone to get stuck at the colored dots boot screen, and forced me to do a nandroid restore in TWRP.
Seems like this should be easier...any advice?
Click to expand...
Click to collapse
use https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi its so simple.
Wait 380 put's the phone in Tablet mode?
Do apps think it's a tablet then? I'm missing Xposed and Tablet Metrics for making Spotify think I've got a tablet so I can use the skip song feature for free.
---------- Post added at 08:33 AM ---------- Previous post was at 08:02 AM ----------
Oh wow multiples of 80 actually do fix things that break! I had changed my DPI from 560 to 490 and it looked GREAT but various icons inside of apps were broken in the sense that they did not display correctly. I changed my DPI to 480, a multiple of 80 and everything displays correctly now.
I did not know Google used multiples of 80, you would think some of the quick change apps would reflect that or let you know that!
Thanks everyone!
I just tried the adb shell wm density trick to change it to 480
Looks soo much better, but i had the visual problems.
I used custom DPI on my nexus 5 with XPOSED reporting stock DPI to play store to install apps.
I want to use 480 for the nexus 6 , but i have to be rooted to edit.
Using CF autorrot is just as easy as it was for the nexus 5?
I know i need to oem unlock, i havent done that. After unlocking, using CF auto root gives me SU. Will sideloading OTA-s stiil work with root or not?
I read that since lollipop , OTAs dont work if you have any modification. It was working fine with my rooted nexus 5 on Kitkat, but since lollipop something changed.
How do I change the DPI?
---------- Post added at 08:08 AM ---------- Previous post was at 08:08 AM ----------
konaman said:
How do I change the DPI?
Click to expand...
Click to collapse
Never mind I see the app above
I'm having some difficulties with keyboard after changing the dpi to 480 so i am going back to stock dpi.
nexus6R3plicant said:
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Sent from my Nexus 6 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Where did you get that info? Why multiples of 80? Supposedly the native DPI of the Nexus 6 should be 493 and that's not a multiple of 80
Here's some info I found on reddit
"
The old "decide layout based on DPI" method has been deprecated since Honeycomb. Android guidelines since 3.2 indicate apps should specify a tablet layout based on the minimum resolution-independent "space" it needs to look comfortable -- the system will tell the app if that is actually the case.
Also, 480 dpi is in fact one of the "native" resolutions (XXHDPI) Google advises devs to include alternate resources in. So at 480, the system would not have to scale graphic resources for most apps, possibly making them look better. And no, 480 should not force common apps into tablet layout (source: Note 3 at native 480 dpi).
I do agree that scaling to even numbers is better; the best is to shoot for a multiple of 4 or 8, just because of how resizing algorithms work in general. So if 480 doesn't float your boat, 492 would be a very good alternative."
https://www.reddit.com/r/nexus6/comments/2mwtl9/psa_while_rooted_set_your_n6_to_its_native_493_dpi/
Chad_Petree said:
Where did you get that info? Why multiples of 80? Supposedly the native DPI of the Nexus 6 should be 493 and that's not a multiple of 80
Here's some info I found on reddit
"
The old "decide layout based on DPI" method has been deprecated since Honeycomb. Android guidelines since 3.2 indicate apps should specify a tablet layout based on the minimum resolution-independent "space" it needs to look comfortable -- the system will tell the app if that is actually the case.
Also, 480 dpi is in fact one of the "native" resolutions (XXHDPI) Google advises devs to include alternate resources in. So at 480, the system would not have to scale graphic resources for most apps, possibly making them look better. And no, 480 should not force common apps into tablet layout (source: Note 3 at native 480 dpi).
I do agree that scaling to even numbers is better; the best is to shoot for a multiple of 4 or 8, just because of how resizing algorithms work in general. So if 480 doesn't float your boat, 492 would be a very good alternative."
https://www.reddit.com/r/nexus6/comments/2mwtl9/psa_while_rooted_set_your_n6_to_its_native_493_dpi/
Click to expand...
Click to collapse
That thread is BS. The native PPI (pixels per inch).is 493. DPI is *nothing* to do with PPI. It's something entirely different. DPI is a Scaling method to make things bigger or smaller and has no direct relationship to pixels.
If you have a 5" screen with a 1080p resolution and a 10" screen with a 1080p resolution, they both have the same amount of pixels. So the pixels are much bigger on 10" screen, so all the buttons, icons etc would also be much bigger. This is not making good use of a bigger screens. So android implemented DPI to allow these assets to be scaled. What they are scaled to is completely subjective. There's no hard and fast rule. And they're Scaling within a set resolution so there is no loss of quality either.
Tablet mode comes in at under 300 DPI in later versions I believe.
danarama said:
That thread is BS. The native PPI (pixels per inch).is 493. DPI is *nothing* to do with PPI. It's something entirely different. DPI is a Scaling method to make things bigger or smaller and has no direct relationship to pixels.
If you have a 5" screen with a 1080p resolution and a 10" screen with a 1080p resolution, they both have the same amount of pixels. So the pixels are much bigger on 10" screen, so all the buttons, icons etc would also be much bigger. This is not making good use of a bigger screens. So android implemented DPI to allow these assets to be scaled. What they are scaled to is completely subjective. There's no hard and fast rule. And they're Scaling within a set resolution so there is no loss of quality either.
Tablet mode comes in at under 300 DPI in later versions I believe.
Click to expand...
Click to collapse
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Chad_Petree said:
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Click to expand...
Click to collapse
I believe its 493 for stock but 560 for aosp. regardless, I enjoy using 532 DPI.
simms22 said:
I believe its 493 for stock but 560 for aosp. regardless, I enjoy using 532 DPI.
Click to expand...
Click to collapse
560 is stock stock stock. Which makes for some funny big icons
Chad_Petree said:
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Click to expand...
Click to collapse
That's because those sites are sort of wrong.
Forgetting android for a moment, in the printing industry and by extension, IT, DPI means Dots Per Inch. Literally how many dots in an Inch can be printed on a page. Dots and pixels seem very interchangeable at this point, but even there they are not. When a print designer mocks up a product for review, the pixels in electronic format do not translate to how many dots a printer can print. But because these two ideas are (somewhat incorrectly) seen as synonymous, and essentially a pixel on a screen is technically a "dot", the incorrect terms are used when it comes to screen technology.
All those sites that say the DPI is 493 are wrong. They mean PPI. The link you posted even uses PPI and then interchanges it with DPI. For screen hardware though, it certainly should be PPI.
Where we get even muddier here is that even the android developer documentation uses DPI to reflect the screen density as dots per inch. But android is using this in the software and not in the hardware. DPI is used to tell the OS what screen it has and from that the OS and Apps can decide how they should be displayed. Where as it seems right that the DPI should be set the same as the PPI, this rarely is the case. As we see with the nexus 5 and 6, Google set the DPI in android higher than the PPI because it looks better. So when Google are setting the DPI different to the PPI, we must be careful how we use these terms. The native PPI of the N6 i 493 but the native DPI is 560.
Edit > Further clarifying statement..PPI is a physical characteristic of a screen. DPI is a virtual representation of a screen.
Hi Guys,
If you wanna be normaly screen size (not original screen size of Htc Desire 510) than download this apk to your phone:
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer&hl=hu
NOMone Resolution Changer (its free)
Open the app and you see
"Width" "Height" "DPI"
Change Width to 720
Change Height to 1280
Change DPI to 312
and click on apply
Or second way:
Open the app
Click on "Select device template"
and choose Motorola Moto X or Htc One X
Click on apply and you done
If you dont like this sizes,dont worry,apk will restore stock sizes after 10 sec and after 1 minutes too.
I hope its helped to some people.
Good Luck to all.
Use this all the time (different app, same effect) but it can seriously eat ram depending how far up you go. While it makes stuff look prettier, it can slow down your device.
Also our aspect ratio is weird. 720x1280 causes a border effect. Use 768x1366 at 300dpi. Looks great and uses the same amount of ram.
I don't know if it's just me or not but everything seems tiny on my screen, including the HTC home,back, and recent apps button.
this does not work on my 510.
any idea why?
do i have to be rooted?
hlebleh said:
this does not work on my 510.
any idea why?
do i have to be rooted?
Click to expand...
Click to collapse
Yes.
I've done this with a different app, but now my widgets & some other stuff seem rather disproportional.
Any way to fix this?
Other than this, however. The 720P looks much better on this phone. Thanks for the tip.
---
UPDATE: The biggest problem so far that I'm experiencing is that I cannot use my favorite keyboard. The buttons are out of place. Too big, can't fit the space allocated. SwiftKey & TouchPal are both out.
All the resolutions dont suit it they are all too big
After changing resolution, reboot your phone. The resolution will stick but everything else will resize to normal. If it doesn't, lower your DPI. All issues regarding "stuff size" should be resolved by lower DPI. Experiment, you'll find what works for you.
But again, RAM is an issue. I've asked pattyboi to adapt Swap into his kernel so I can test out RamExpander. With Swap enabled we should see a bit of a performance boost, but it can be risky if you don't know what your doing. Until we have a Swap capable kernel (and it actually works) were stcuk with what we got. From what I've read up on it, Swap seems like a viable solution to many performance issues with the 510
Okay so I'm really puzzled about how you can just change the resolution, how does it work??? Does the screen have a resolution more than the stock 480-800? I dont understand
So, that changing resolution? Is that works at all?
I just want to ask. At this low dpi am i stressing my cpu more? I don't play any games. Mostly use my device for multimedia, social, forums and whatsapp. So is it fine if i keep this dpi. or its better I change it to normal like 493??
Im on N dp3
akholicc said:
I just want to ask. At this low dpi am i stressing my cpu more? I don't play any games. Mostly use my device for multimedia, social, forums and whatsapp. So is it fine if i keep this dpi. or its better I change it to normal like 493??
Im on N dp3
Click to expand...
Click to collapse
normal dpi is 560, not 493.
While setting the DPI lower doesn't affect the CPU or GPU, changing the DPI is of little benefit unless your eyesight is bad. I'd set the DPI back to stock and forget it.
I know. I was talking about small screen size in android n which is around 490. And i have it at custom 331. Is it ok? Or is it bad for performance. And cpu is doing more work?
Strephon Alkhalikoi said:
While setting the DPI lower doesn't affect the CPU or GPU, changing the DPI is of little benefit unless your eyesight is bad. I'd set the DPI back to stock and forget it.
Click to expand...
Click to collapse
I see. Thank-you. Stock is just a little too big for me. Thanks again.
akholicc said:
I just want to ask. At this low dpi am i stressing my cpu more? I don't play any games. Mostly use my device for multimedia, social, forums and whatsapp. So is it fine if i keep this dpi. or its better I change it to normal like 493??
Im on N dp3
Click to expand...
Click to collapse
The native resolution of the N6 display is 493.
Google's default is 560 that's not logically on a display of 1440 x 2560 pixels. The capabilities of the display are not fully used with Google 's idiot 560 dpi.
A dpi value of 384 or less, puts the N6 in tablet mode (2 columns in Settings menu). And the icons are smaller and more rows and columns are available.
I've used several dpi values and did not notice less battery life. Or cpu stress.
My favorite is 384.
I disagree with the sentiment that the display isn't fully or properly utilized at the DPI Google set. Naturally you're entitled to your opinion, but the Nexus 6 isn't a tablet. The tablet interface is a matter of user choice, not a design flaw. If it were a design flaw, then any 5.5" - 6" device with a QHD screen should be in tablet mode by default.
Strephon Alkhalikoi said:
I..... If it were a design flaw, then any 5.5" - 6" device with a QHD screen should be in tablet mode by default.
Click to expand...
Click to collapse
Most 5-6" recent smartphones have a display with 1080x1920 pixels (FullHD). Phones with qhd display cannot be compared with the N6 because of the lower resolution (960x540 pixels).
The N6 is one of the few with 1440x2560 pixels (WQHD)
The default dpi of 560 that Google used does not fit the native resolution of the N6 display.
You're right. I used the wrong acronym to refer to the screen, thus I will restate my point: this is not a design flaw. If it were, any device in the 5.5" - 6" range with a resolution identical to the Nexus should be in tablet mode by default. They are NOT. Even devices that have the same screen size but a lower resolution are not in tablet mode by default. This is because these devices are not tablets, even if they can be used as such.
DPI is device independent, if I recall Google's documents on the matter correctly. That number does not have to equal the device PPI of 493, thus what Google chose to use is just as valid as any other number.
Strephon Alkhalikoi said:
DPI is device independent, if I recall Google's documents on the matter correctly. That number does not have to equal the device PPI of 493, thus what Google chose to use is just as valid as any other number.
Click to expand...
Click to collapse
That's correct, but I don't agree with Google.
The default DPI 560 means in practice larger icons and titles. Too large imo. I want more and smaller icons on the main screen and in the launcher.
The tablet mode is a different thing. I think it nice to have a 2 column settings menu. That's personal. In Android N preview it doesn't work anymore.
I don't see the larger icons and titles as a problem, and Google likely doesn't see it as a problem either. I know Samsung doesn't see it as a problem, as on the Galaxy S4 they did the same thing. That device's 5" display had a PPI of 441, but a DPI of 480. Fortunately, the S4 could be rooted and the DPI changed. Something I'm sure you've done here with the Nexus 6.
Hi guys,
I used to use this method with mostly all of my devices in the past: LG G3, Galaxy S5, Amazon Kindle Fire tablets (including 8'' and 10''). All of them work just fine. But not this Pixel5!
Using the "adb shell wm size" command. I changes the screen resolution of my devices down a notch, for example from 1440p to 1080p, or 1080p to 800p and so on. Then I adjust the density accordingly. They all turn out the Ok-ish screen resolution and have a much better GPU performance for gaming.
My current S10 has the native changing resolution from Samsung, So I don't use it for my S10.
But with the Pixel 5, there is a problem. The camera cut - out on the screen become so weird and placed on the off center position, and the Pixel 5 is unusable
I really love to use my pixel 5 at 720p or 900p, and I believe the Adreno 620 (snapdragon 765G) on the Pixel 5 will handle game at the lower resolution much much better.
Does anyone have a fix for this? please help!
Thank you for your reading!
P.S: OMG, this was my bad for posting the thread into the wrong sub-forum. It was on the other tab of my web-browser. Thank you very much for moving it to the right place, Moderator!!
Why are you not changing the resolution in the settings like you do on the Samsung? A quick search suggest the Pixel 5 has such an option. You're best doing it the official way to guarantee everything will work correctly.
Because you're changing the resolution and DPI through what is basically a developer option, I think whatever is handling the camera cutout (An app? The WM? Android?) is not updating its position and that causes it to be misplaced. Therefore, I dont think you find a simple fix for this. Sorry.
richhaynes said:
Why are you not changing the resolution in the settings like you do on the Samsung? A quick search suggest the Pixel 5 has such an option. You're best doing it the official way to guarantee everything will work correctly.
Because you're changing the resolution and DPI through what is basically a developer option, I think whatever is handling the camera cutout (An app? The WM? Android?) is not updating its position and that causes it to be misplaced. Therefore, I dont think you find a simple fix for this. Sorry.
Click to expand...
Click to collapse
You must be mistaken the Pixel 5 with other phones, since we don't have the option for such a changing the resolution in the settings.
If you mean the display size? It's just a density change, not the resolution.
Thank you for your contribution anyway!
Hi, have you sovled the problem? I encountered a similar condition.