I wonder if there is a possibility to change the width of the drop down panel which contain the notifications as I think it will be more cool to look like drop down panel in ipad which extend from both sides of the screen
Is there is a way ?
Ya, I agree. It's full screen in portrait mode, but not in landscape.
That's the way it was in 4.3 and it looked goofy. Reviewers and users *****ed and it was changed in 4.4.
Could you guys adjust the width of split screen in Landscape mode? I can't. (But the height in portrait mode adjustable!)
I want to know is it normal or there is a problem with my phone.
P.s. MIUI 10.4 9.4.18
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?
I've tried my best to keep my hands off cutout phones until this one. Can't help myself, the value is insane.
Anyway, I've always liked my phone on lower side of DPI. the thing is, the statusbar height does not change with any different DPI value, like it is with normal phones with no cutout. This is minor, but it bugs the hell out of me.
I'm on latest EU ROM, Magisk rooted
I read a thread on making phones like tablets by increasing the minimum width in developer options from 411 to 611. Has anyone played with the screen width for the Tab 8+? Is there anything to gain here?
Thanks,
Joe