Database Develop

HDMI resolutions?

Is there a possibility to add custom ones?
Sent from my LG-P990 using XDA App

Go to Settings > HDMI > Resolution > and there you can select

Optimus2XPrime is right.
You can select the default display solutions only, you can not set an individual display solution (the only reason to set an individual display solution is if you want use a pc monitor with a special display solution).

Oh gosh...
Of course I want to use a normal monitor or whatever it would be hooked up to the DVI lanes... by default the phone outputs 1024*768 resolution to unsupported monitors.
Have anybody seen a option to set custom output presets there? Not 16:9 sized but 16:10...
Any Ideas...

HDMI tv out, only mirroring?

I tried the tvout with the offical hmdi adapter but it mirrors the tablet including the system bar, and since the resolution of the tablet is 16:10 and not 16:9 I get two black vertical stripes at both sides.
Is there a way to change this behavior? Like a full 16:9 or a 1080p out?

zooster said:
I tried the tvout with the offical hmdi adapter but it mirrors the tablet including the system bar, and since the resolution of the tablet is 16:10 and not 16:9 I get two black vertical stripes at both sides.
Is there a way to change this behavior? Like a full 16:9 or a 1080p out?
Click to expand...
Click to collapse
You'll need to change the settings on your TV to stretch the picture or zoom it, most TV's have a setting to automatically do this to hide black bars, the only problem is it alters the shapes, people end up with odd shaped heads etc

So basically there is no way to play on a tv a 16:9 fullhd video or a slidewhow without status bar? I mean, is mirroring the only one mode?

You can set this up to hide the status bar, but 16:9 is always going to be an issue as the tablet is not 16:9

Yes, but still tvout is a limited feature since I can't have an extended desktop or i.e. a slideshow played on tv while working on something on the tab...

zooster said:
Yes, but still tvout is a limited feature since I can't have an extended desktop or i.e. a slideshow played on tv while working on something on the tab...
Click to expand...
Click to collapse
Hang on......so you want to play a video to the TV in HD widescreen while still doing something on the tablet ?
I'm pretty sure there's no Android devices that do this

A kind of... My first aim is to play a slideshow on a tv in full screen mode, while seeing the slide's tree on the tablet and choosing which one to show in full screen on the tv.
Second aim is to disable tablet video and show only tv. It would be nice to play a 3d game on the tv, but as long as the video is doubled fps are so low that it's unplayable.

FPS won't be doubled as all you're doing is doubling up the video output, not the data going through the GPU, there's plenty of video's on youtube of folks using MHL adapters to connect to a TV to play games

Yes fps won't be halved but, since a tough game is very cpu intensive, doubling the video it lags a lot more the tablet. My tablet is much more laggy even simply swiping on the home screens or app drawer when connected to a tv.

Flash motley kernel and overclock to 1.4

I believe a Nexus Q will let you send video from the tablet to the TV whilst doing other stuff on the tablet, but it costs quite a lot.

Definitely hear some unrealistic multitasking wants. Also, doesn't ICS improve hdmi out options as far as full screen video, not just mirroring?
Sent from my SPH-D700 using Tapatalk 2

The Galaxy note 10.1 has this function in the movieplayer to only show the video while controls are shown on the tablet. This is exactly what you are asking if i understand you correctly.
I'm also looking for more possibilities in this area. Being able to see the picture Gallery while only showing the last picture (or non at the start) would be amazing!
If i find anything i will share it here

Incorrect aspect ratio on 1920x1200 display

I realized last night that my 1920x1200 display is scaling the Chromecast 1920x1080 signal to a full 1920x1200 resolution causing the entire display to be stretched vertically.
When hooking up the same display to my PC via the same HDMI port at 1920x1080 resolution, I get a 1:1 pixel mapping with black bars on the top and bottom of the image. Is there something in the image source that specifies whether to stretch or use a 1:1 pixel mapping? I went through all the settings on the monitor and nothing will give me the proper aspect ratio.

Same here, have you found a solution? It sucks!

Louer Adun said:
I realized last night that my 1920x1200 display is scaling the Chromecast 1920x1080 signal to a full 1920x1200 resolution causing the entire display to be stretched vertically.
When hooking up the same display to my PC via the same HDMI port at 1920x1080 resolution, I get a 1:1 pixel mapping with black bars on the top and bottom of the image. Is there something in the image source that specifies whether to stretch or use a 1:1 pixel mapping? I went through all the settings on the monitor and nothing will give me the proper aspect ratio.
Click to expand...
Click to collapse
You sure your TV isn't set to Stretch as opposed to normal?

Chromecast 1920x1080 from 1920x1200 Android device
Louer Adun said:
my 1920x1200 display is scaling the Chromecast 1920x1080 signal to a full 1920x1200 resolution causing the entire display to be stretched vertically.
Click to expand...
Click to collapse
Have you double checked all scaling options of your display? This user contacted Google to let them know of the same problem:
Louer Adun said:
Issues/Features I had contacted them about:
1080p content scaled to 1920x1200 on a 16:10 aspect ratio monitor (other devices scale properly)
Click to expand...
Click to collapse
But was this bug ever fixed? Answer: No!
Louer Adun said:
I just plugged the Chromecast in, and it updated (had been sitting on the shelf for a while). After the update, the same problem is exhibited. I have 2 aspect ratio options in the monitor settings, "Full" and "Fit". Both provide a 16:9 1920x1080p signal stretched to the 16:10 1920x1200 resolution.
Click to expand...
Click to collapse
---
The other way around: If you have a 1920x1080 display and want to mirror the display of Android device wich has a 1920x1200 resolution, use this app the app "SecondScreen" (https://www.xda-developers.com/cast-device-second-screen/) to set the resolution to 1920x1080 before casting to the Chromcast.
Its goal: "Second Screen aims at providing you with a way to properly cast your screen so that it looks is best whenever you are showing it off to your friends and family. It does so by allowing for a user selectable resolution and even DPI in order to take full advantage of your TV."

Chromecast2 on a HP 1920x1200 display
Louer Adun said:
Yeah, that's what it seems I need is a 1:1 pixel mapping. However connected to my computer this monitor will have a letterbox when set to 1920x1080 and the expected letterboxing.
Please note I only tested this with the first gen Chromecast, so maybe this isn't an issue with the second gen units.
Click to expand...
Click to collapse
I tested the Chromecast2 on a HP 1920x1200 display. Pixels are mapped 1:1 with the right display settings. I don't have a Chromecast1 to check with this display.

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?

General Change display aspect ratio

I know this was asked for like a million times but why is it not a thing?
Example: I have a car stereo that uses some app to stream my display to itself, and the current aspect ratio just looks bad
I know it's possible because of the smart view settings but why can't the user control it?
A Bixby routine to change the aspect along with opening the app for entering the car would be a lifesaver