Database Develop

[MOD] Increase resolution on webtop

to increase resolution on webtop
edit xorg.conf file (/osh/etc/X11/xorg.conf)
Code:
Section "Screen"
Identifier "Screen HDMI"
Device "Tegra HDMI"
Monitor "HDMI"
DefaultDepth 24
SubSection "Display"
Depth 24
# Uncomment to override the preferred resolution chosen by UseEDIDModes
Modes "1280x720"
ViewPort 0 0
# Defaults to the size of the chosen mode
Virtual 1366 1024
EndSubsection
EndSection
change line Virtual to eg
Code:
Virtual 1920 1080
and from a terminal execute
Code:
xrandr -s 1920x1080

Does that resolution work with the dock?
Sent from my NINJATRIX

I tested it with multimedia dock and fullHD TV

error
something to the tune of "size not in available modes"
i'm using the hdmi hack, no dock

aaron.a said:
error
something to the tune of "size not in available modes"
i'm using the hdmi hack, no dock
Click to expand...
Click to collapse
Make sure you use a resolution your tv/monitor supports. Technically you should be able to set the res from the little monitor icon on the top of the screen.

For more flexibility you can comment the virtual mode out and write several resolutions in modes like : Modes "1920x1080 1680x1050 1280x800" and so on. Than use the xrandr command for different monitors/tvs

Lapdock?!?
How about the Lapdock? I have a strange problem in lapdock, where when I try to change the default display resolution (on the settings icon inside webtop) it does nothing at all, and my screen stops being full screen (i get black straps on the monitor edges).
Should I change this line to make my screen defaults to lapdock native display resolution of 1366x768?
Code:
# Uncomment to override the preferred resolution chosen by UseEDIDModes
Modes "1366X768"
ViewPort 0 0
And still alter the other line as well for when i plug my phone on my Full HD TV?
Code:
# Defaults to the size of the chosen mode
Virtual 1920 1080
Thanks in advance.

this requires the webtopmod? not able to run xrandr.

this is from a-trix.net site right?

Hi,
If I change the resolution to full HD and if I try the webtop on a HD Ready TV, will it work ?
Thank you.

Ronaldo_9 said:
this is from a-trix.net site right?
Click to expand...
Click to collapse
yes I first publish on that forum

-JFK- said:
Hi,
If I change the resolution to full HD and if I try the webtop on a HD Ready TV, will it work ?
Thank you.
Click to expand...
Click to collapse
You can obtain different configuration changing xorg.conf file
a desktop at fullHD resolution that scroll on HDready resolution
or a desktop at fullHD scaled on another resolution
for reference
http://www.x.org/releases/current/doc/man/man5/xorg.conf.5.xhtml

i got it going. an error on my part. i added an additional line for my resolution instead of adding it inside the quotes
thanks for sharing you're knowledge's =D

can you elaborate please, is this done inside webtop? cause i searched my /osh folder with root explorer and there's no etc folder in it

I get xrandr: not found.
Point me the right way please?
<edit> Would this be a path issue?

^^^^^^^^^^^^^^^^^^
Same
Sent from my MB860 using XDA App

CaelanT said:
I get xrandr: not found.
Point me the right way please?
<edit> Would this be a path issue?
Click to expand...
Click to collapse
The same to me!
And I am needing the webtop for videos.
But...
One thing that I realized, for pictures and musics the resolution its ok, but for videos not. Why?

xrandr appears to be in /usr/bin so that shouldn't be an issue.
Code:
# which xrandr
/usr/bin/xrandr
#

My issue is that when I run xrandr (and this is on a Photon, not an Atrix) is that it comes back with "No display".

John Kotches said:
My issue is that when I run xrandr (and this is on a Photon, not an Atrix) is that it comes back with "No display".
Click to expand...
Click to collapse
Solved this, also set up the adas user to pull up @ 1920x1080 automatically on login by updating .profile.
Regards,

[How-to] auto-switch to 1080p on slimport, using tasker

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:

Change resolution on the phone or on the connected display? USB-C to TV Example!

Hi guys!
Does anyone know how we could change the resolution on the phone. Or at least the external screen?
My use case would be connecting the phone via USB-C to a TV.
TV is 1920x1080 and phone is 2340 x 1080.
Because of that I get black bars on top and bottom.
It's also only a mirror image. Is there some app or way to kill the mirror of the screen and then launch an app only on the connected screen in whatever the resolution the screen is (most often 1920x1080)
My use case for this is to play with bluetooth joysticks on a TV for example.

Mad_Duke said:
Hi guys!
Does anyone know how we could change the resolution on the phone. Or at least the external screen?
My use case would be connecting the phone via USB-C to a TV.
TV is 1920x1080 and phone is 2340 x 1080.
Because of that I get black bars on top and bottom.
It's also only a mirror image. Is there some app or way to kill the mirror of the screen and then launch an app only on the connected screen in whatever the resolution the screen is (most often 1920x1080)
My use case for this is to play with bluetooth joysticks on a TV for example.
Click to expand...
Click to collapse
I use second screen to change resolution and dpi settings, you need to do a bit of back end work to support, the app walks you through the options but only allows mirroring.

Swellwoo said:
I use second screen to change resolution and dpi settings, you need to do a bit of back end work to support, the app walks you through the options but only allows mirroring.
Click to expand...
Click to collapse
App requires root unfortunately

You can run the following on a pc with phone in developer mode and USB debug
"adb shell pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS"
You need to install Android sdk. Command line on pc but you do not need to root phone.

Swellwoo said:
You can run the following on a pc with phone in developer mode and USB debug
"adb shell pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS"
You need to install Android sdk. Command line on pc but you do not need to root phone.
Click to expand...
Click to collapse
Thank You!

Does this work guys?
It's annoying the black bars on top and bottom.
Before I try, do I need to have it plugged into the pc and TV at same time?
Or once done it's change forever?
Cheers

Has anyone noticed when connected via USB-C to the monitor/TV now, Tablet mode is missing on Android 10 (compared to 9) it only has Mirror and TwinDock Modes now where as before it has the 3 options.

yes this does work, ive just done my Motorola nexus 6
Setup ADB on your PC.
Enable USB debugging on your phone:
Open Settings & go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and youll see Developer options, open it.
Tick the USB Debugging checkbox.
Connect phone to the PC.
Open a command window on the PC and issue the following commands to change screen resolution to 720 x 1280 and density to 280:
adb shell wm size 720x1280
adb shell wm density 280
Reboot phone with the following command:
adb reboot
this works perfect playing codmobile, it no longer overheats and gaming become alot faster for me
the asus rog 2 has a physical resolution of 1080 x 2340 Pixels, and a pixel density of 391 on a 6 inch screen
change it to
adb shell wm size 720x1280
adb shell wm density 280
and you will notice longer battery life, no more overheating and your gaming will become alot faster.

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