Database Develop

Scaling issues with custom DPI

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.

[Q] Looking for a ROM with the capabilities of SlimKat/SlimLP?

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

Android 5.1 display density issues with 493 for contact thumb nails and some pictures

I just upgraded from 5.0.1 to 5.1 and I've noticed that when I change my resolution from the factory default of 560 to say the native res of 493, the contact thumb nails are distorted. If I use the terminal command "wm dentity 560" to go BACK to 560, it fixes it. Normally I run 493 which is the native res for this screen.
5.0.1 does not have this issues, only 5.1.. I also tried other resolutions and I get this issue on everything but 560.
I'm using CleanROM 2.2 which is a stock based ROM.
Also I noticed pictures in some image browsing apps do not display correctly. They show as super zoomed in on one section and I an not zoom out. ES File Explorers image app does this but for example QuikPic does not.
If I go back to 5.0.1, all problems solved though.
Just wondering about other 5.1 users experiences with stuff like this.

493 is not the native DPI. PPI and DPI are NOT the same.

Just to echo what @akeller said, DPI is not linked to resolution. DPI is not the same as PPI. PPI (Pixels per Inch) are how many physical pixels are in an inch of your display. This obviously cannot be changed.
Lets say you have a 5" screen at HD resolution (1080p) and also a 10" screen at the same resolution. As you can imagine, you have the exact same amount of pixels on the display, but the display is bigger so the pixels are also bigger.
This means that assets on your screen (icons, buttons etc) will also be much bigger, so you are not taking advantage of a bigger screen as you can only fit the same amount of stuff on it. For this reason, DPI is used as a scaling method to make assets smaller, to fit more on the screen. There is no hard-and-fast rule as to what DPI to use. Generally, the bigger the display, the smaller the DPI should be to make bvetter use of it. OR, the lower the resolution, the smaller the DPI should be. There is no direct link to PPI and DPI.

After you run "wm density 493" also run just "wm density". Now you'll probably see that it reports two values, 560 and 493. The solution is to also edit build.prop (change 560 to 493).

AA 480p issue

Hey folks,
I am using this module to enable AA on my BMW headunit:
a.aliexpress.com/_U4Jz5
It kinda works nice except for one thing, resolution is not so clear due to dpi settings. Someone else dug into the system and found that in
etc/androidauto/androidauto_config.xml
The resolution is set to 480p instead of 720p and dpi is set to 150 instead of 180.
We have no SSH access but can only upload .bin update files as we dont know the password.
Does anyone know if it would be possible to change 720p to true and up the dpi somehow?
Carplay apparantly is 720p on this unit.
<DisplayWindow><!-- Head Unit side configuration--> <X_Coordinate value="0"/> <Y_Coordinate value="0"/> <DisplayWidth value="1280"/> <DisplayHeight value="480"/> </DisplayWindow> <Display><!-- Phone side configuration--> <DisplayWidth value="232"/><!-- Physical width--> <DisplayHeight value="87"/><!-- Physical height--> <Density value="170"/> <RealDensity value="153"/> <ViewingDistance value="400"/> <Resolution480P value="true"><!-- fps: 30 or 60--> <fps value="30"/> </Resolution480P> <Resolution720P value="false"> <fps value="30"/> </Resolution720P>

Nobody?

Anyone?

Do you have a copy of the BIN? My guess is unpacking and repacking the BIN will be the hardest part of this. You probably won't be able to do this without source scripts. You are in the right place regarding the XML file inside. All android head units, regardless of what they are, have to tell our phones what resolution to serve up. If the head unit says to run 1024x600 then that is what you are getting.
An alternative would be to ask the manufacture to release an update set to the proper settings.
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
Here you go The Andream unit you have should likely work with one of these firmwares. Do a lot of reading there before you proceed. I cannot be responsible for you flashing the wrong software to your unit.
I have a similar unit to yours and was able to get mine running at the proper resolution.

@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream (version: NBT-02B) unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).

ckarv said:
@heresy_fnord, when you say the proper resolution, what resolution are you referring to? I have the Andream cool:unit myself, and flashed the latest .BIN with the AA Widescreen fix, but I feel the scale is slightly off. Text and elements are too small compared to the screen size (I have 8.8", 1280x480).
Click to expand...
Click to collapse
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.

heresy_fnord said:
OK, my guess is the physical screen size is the issue. If you are certain the 8.8" screen also runs 1280x480 then the settings for DPI are probably not appropriate. Here is what I see for a 10.25" screen:
<Display>
<DisplayWidth value="244"/> 244mm is 9.6" width
<DisplayHeight value="92"/> 92mm is 3.62" height
<WidthMargin value="0"/>
<HeightMargin value="0"/>
<Density value="220"/>
<RealDensity value="133"/> This calculator indicates a real density of just a hair over 133PPI
So for example, your real density should be set to 155PPI based on that logic. I don't know what your update file was set to. I don't know what your display width and height should be set to since I don't know how the 8.8" screen measures length and width. Finally, I think they are setting the Density of the widescreen fixed update to 210 and you might try 220 which is as big as it can be set before it cuts back over to the non-widescreen view, and see if that works.
Click to expand...
Click to collapse
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks

ckarv said:
I've put some effort into looking into this now, basically reading 100 odd pages in the "Andream MMI Box - Wireless CarPlay & Android Auto" thread (starting on pg. 135), over at the Bimmerpost forum.
Findings:
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
* Attached a picture of my screen with 200 dpi.
You are using a "Density" value of 220, do you have an example of what that looks like in practice?
Thanks
Click to expand...
Click to collapse
- 720p = true setting is required to display AA in "Wide" format (ie. clock, second app on the right side of the display, map and vertical bar with "home", active app, notification and assistant buttons on the left).
This is accurate.
- From reading results of testing over at the other forum, the Physical width/height settings did not seem to make a difference to output.
I don't know, perhaps this is true.
- Density on the other hand is used to scale the elements on screen, and this also impacts readability and sharpness of the objects/text.
-- from some testing, the conclusion was that "200" is the optimum value for the 1280x480, 8.8" screen, although eg. "210" was tested.
-- unsure if changing "Real Density" will make a difference to output (similar to physical measurements)
* Also, I think my scale is correct, or as specified in the firmware. Text and elements just seems so small compared to CarPlay that wife uses.
Your scale of text is set by the DPI essentially. Its a combination of resolution and DPI. Basic example, if I was to set my DPI to 200, the text on my screen would be smaller.
* Attached a picture of my screen with 200 dpi.
This is a 10.25" screen with 220DPI
In your case, the one update file was made for a 10.25" screen. The thing is, there will be a DPI difference between the two even if the resolution is the same. I suspect you need check with that community to see if there is an update that maintains widescreen mode but uses the different DPI.
EDIT: To be fair, I think your screen looks "normal" but then, it looks like your clock and such are the same scale as mine. Maybe AA is just smaller text in general?

[Question] Pixel 5 screen resolution change fix?

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.