Related
Hi, I'm running into the issue that the screen is being rendered larger than the physical size of the screen so status boxes sometimes partially off screen and app icons get half hidden in the corners.
I plaid around with build.prop, but it didn't really help any. Is there a way to modify the home screen without changing the resolution? Also, if anyone knows of a way to change icon sizes short of installing a different launcher, that would be a huge plus.
TIA!
I've read that there are limitations in place for the preview image that kind of create this problem. If I understand the problem correctly it may be a case of changing pixel density but the preview image doesn't let you go beyond a certain density so even then the problem still exists. It's probably just something we have to deal with until Honeycomb becomes publically available for development.
This makes sense. The only reason I care about this is that when I use Aldiko, I can't see the top line of text because it pushes the words above the actual screen.
Does anyone have a recommendation for an E-Reader that they use successfully on HC???
xdadidida said:
Hi, I'm running into the issue that the screen is being rendered larger than the physical size of the screen so status boxes sometimes partially off screen and app icons get half hidden in the corners.
I plaid around with build.prop, but it didn't really help any. Is there a way to modify the home screen without changing the resolution? Also, if anyone knows of a way to change icon sizes short of installing a different launcher, that would be a huge plus.
TIA!
Click to expand...
Click to collapse
You changed the LCD density in build.prop and the screen didn't change???
What is your lcd _density set at?
Sent from my NookColor using XDA App
I haven't really looked into this but I do know there are ports of honeycomb for various phones such a the evo, maybe try pulling the build.prop from one of those and see howe they altered screen density.
Sent from my PC36100 using XDA App
i've tried changing the number but havent had much success through the buid.prop. Any ideas on a good number and which number to change? Looks like there are 3 density numbers
For Honeycomb, I found that 120 is the best lcd density, it shows all the options when you expand the settings from the clock, it also displays the correct number of running apps in the quick change button (or whatever you call it) Also, Lcddensity is a good app for trying out diffrent settings. For Aldiko, I recommend increasing the margin size to see the top line of text, not a perfect solution, but it works.
Hi,
I am new to the p7. I am used from my Samsung and nexus devices to adapt via build.prop DPI in order to see more things on screen.
Build.prop has no DPI setting. How (which app?) Proved to securely change DPI? And what is stock DPI for 1080 and 720p (rog)?
Thanks
No one feeling the need to show more on screen? [emoji22]
Hi,
Have you found a solution for this yet?
I've recently got myself a P7 and I'm trying to get something similar to 240 dpi(like my s3).
People have mentioned ROG tech, but I can't find that option anywhere.
ROG setting is under Settings - Power Saving, then menu (upper right corner) setting.
Rog? I tgought its resolution (I.e HD 720p instead of full HD1080p)? Is there also a setting for density hidden besides ROG?
rog doesnt do the trick
I've activated ROG, but all it does it help the battery to last longer, by reducing performance and screen res.
What I (and op) are looking for, is something to change the dpi (pixel density/LCD density). Like on samsung phones, you can do it through build.prop
No one managed to edit dpi?
Still have a problem...
Where.is the rog option in emui3?
changing dpi on P7 ??? such little screen ?? NO POINT it is tiny already ..
I have a p9 updated to nougat and I find no option in the settings----> display to change the screen size. I saw that in the developer settings there is the "minimum width" and I set it as 420 (for having a very condensed screen) but some camera elements have glitches. How can you have the condensed screen without having glitches? * I do not have the root *
Thanks much
Giovanni9921 said:
I have a p9 updated to nougat and I find no option in the settings----> display to change the screen size. I saw that in the developer settings there is the "minimum width" and I set it as 420 (for having a very condensed screen) but some camera elements have glitches. How can you have the condensed screen without having glitches? * I do not have the root *
Thanks much
Click to expand...
Click to collapse
The "minimum width" setting is the dpi. For the camera if you set the dpi higher the Pro mode switch goes towards the shutter button, but if you set the dpi over 410 this switch glitches out and stays in the air. So the simple answer is don't set the dpi over 410.
_Frostplexx_ said:
The "minimum width" setting is the dpi. For the camera if you set the dpi higher the Pro mode switch goes towards the shutter button, but if you set the dpi over 410 this switch glitches out and stays in the air. So the simple answer is don't set the dpi over 410.
Click to expand...
Click to collapse
Yes, I was wrong to write, I said how to change the DPI of the screen. I set 409 to not have pro mode on the depth shutter and have the most condensed screen.
How does huawei not put it in the settings accessible to everyone (in the display to understand)?
Giovanni9921 said:
Yes, I was wrong to write, I said how to change the DPI of the screen. I set 409 to not have pro mode on the depth shutter and have the most condensed screen.
How does huawei not put it in the settings accessible to everyone (in the display to understand)?
Click to expand...
Click to collapse
I could be wrong, but i think its stock and manufacturer puts the dpi slider outside the developer settings, because you could mess up your screen. And i think it's accessible enough that people who know what DPI even means can change it. And you also don't need to mod anything to access developer settings, so everybody can use them.
_Frostplexx_ said:
I could be wrong, but i think its stock and manufacturer puts the dpi slider outside the developer settings, because you could mess up your screen. And i think it's accessible enough that people who know what DPI even means can change it. And you also don't need to mod anything to access developer settings, so everybody can use them.
Click to expand...
Click to collapse
Right, I did not think so
hey there,
i run Oreo on p9 AL10 and dev settings are 420dpi and no glitches in camera or anywhere.
Question, how to make settings survive a boot? it always defaults back to 360dpi after boot.
i played with build.prop but nothing worked for me. any ideas?
thx
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?
Is there a way to make the fonts smaller? I've adjusted the font scale setting to the lowest under Settings>Display but I'm still finding the fonts quite large compared to the Pixel.
In Gmail in particular I'm only seeing 7 emails per screen
scoobiesnacks said:
Is there a way to make the fonts smaller? I've adjusted the font scale setting to the lowest under Settings>Display but I'm still finding the fonts quite large compared to the Pixel.
In Gmail in particular I'm only seeing 7 emails per screen
Click to expand...
Click to collapse
Try lowering minimum width. Enable developer option and scroll down to it, I don't know if you can go below 300dp, that's gonna be very tiny anyways.
I raised the width setting from 384 to 500. That's seems to have worked. Thanks
Go into developer mode then set smallest width DPI to 511 default is 411 bingo looks great now