Related
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
After sideloading lots of apps onto the gear and comparing to the motoactiv, I have discovered the second most crippling thing about the gear after the lack of wifi is the square aspect ratio screen. It breaks 75% of the apps I try because they're designed for a 4:3 or wider screen and all the interface elements either overlap or are drawn off screen. It has excellent hardware, and with a normal aspect ratio like on other smartwatches it would run most apps and games perfectly.
The landscape/widescreen apps that do work tend to scale the image down so it fits within the width of the screen. Does anyone know if it might be possible to force apps to do this, or to fool them into thinking its a 320x240 screen? Like how paranoidandroid allows you to set the DPI for individual apps. It wouldn't be perfect not filling the screen, but it would at least allow the majority of apps to function.
If only it were 480x320 instead of 320x320...
ivant said:
After sideloading lots of apps onto the gear and comparing to the motoactiv, I have discovered the second most crippling thing about the gear after the lack of wifi is the square aspect ratio screen. It breaks 75% of the apps I try because they're designed for a 4:3 or wider screen and all the interface elements either overlap or are drawn off screen. It has excellent hardware, and with a normal aspect ratio like on other smartwatches it would run most apps and games perfectly.
The landscape/widescreen apps that do work tend to scale the image down so it fits within the width of the screen. Does anyone know if it might be possible to force apps to do this, or to fool them into thinking its a 320x240 screen? Like how paranoidandroid allows you to set the DPI for individual apps. It wouldn't be perfect not filling the screen, but it would at least allow the majority of apps to function.
If only it were 480x320 instead of 320x320...
Click to expand...
Click to collapse
What your asking from my knowledge is not possible..
One thing you can do tho is set the independent DPI's of apps like Paranoid Adnroid using xposed framework & app settings module.
You can also application titles, which breaks some apps although does free up some screen real estate.
Both the nexus 4 and the nexus 7 (2013) support slimport, which is very useful for mirroring the device to a big screen. However, neither device uses the standard 16:9 (1080p) aspect ratio. As a result, you end up with some cropping on a 1080p TV. For the nexus 4 it is even worse, since it outputs 768p upscaled to the TV's resolution.
However, the flexibility of android allows us to manually change the native resolution. In a console, we can type the command:
wm size 1080x1920
and the resolution will change. In the device screen the new resolution will look odd, however you now have true 1080p on the TV. To get back to the default resolution you type:
wm size reset
This solution works, but it is not very convenient. So I made two profiles for tasker, that automatically change the device resolution upon the connection of an HDMI cable and reset it when the cable is disconnected, thus automating the whole process.
I 'm attaching a screenshot of the two profiles, as well as a zip file so you can extract and import them in tasker.
In summary,
- you need root
- the HDMI plugged profile
reduces the device brightness to minimize battery consumption
increases volume
sets resolution to 1080p
enables WiFi
sets display timeout to 10 hours
activates display rotation
- the HDMI un-plugged profile
sets auto brightness back on
resets screen resolution
sets display timeout to 1min
These are optional settings that I found useful to automate, but they are all optional, and you can tweak them once you imported the profile to tasker.
I hope you find this useful!!! :good:
Hey guys, I am looking to buy this phone. I have one question, what is the aspect ratio of the display with notch being disabled? Someone please answer. Thanks in advance.
Musiclover49 said:
Hey guys, I am looking to buy this phone. I have one question, what is the aspect ratio of the display with notch being disabled? Someone please answer. Thanks in advance.
Click to expand...
Click to collapse
I believe it is back to being standard 16:9 or 16:10 with the notch disabled. Out of curiosity, why is the aspect ratio an issue?
Crossvxm said:
I believe it is back to being standard 16:9 or 16:10 with the notch disabled. Out of curiosity, why is the aspect ratio an issue?
Click to expand...
Click to collapse
After seeing many videos on youtube, I believe it is 18:9.
Aspect ratio is always an issue. I watch movies on my smartphone, so I need to know how immersive is the video watching experience. Thanks anyway.
No worries, videos will be shown correctly without the notch even if you don't disable it. You won't face with any issues about that.
Musiclover49 said:
After seeing many videos on youtube, I believe it is 18:9.
Aspect ratio is always an issue. I watch movies on my smartphone, so I need to know how immersive is the video watching experience. Thanks anyway.
Click to expand...
Click to collapse
Android 9.0 added support for the notch, and many apps have been quick to release updates perfecting it, Google's YouTube of course was one of the first. When you disable the notch in the settings, you get the full standard viewable area. With the notch enabled, you can pinch out to zoom which will fill every corner of the screen with very minimal peripheral loss. Everything I mentioned is with the nav bar disabled (fullscreen display mode). The end result is an experience not much different than with a "standard" phone.
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?