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...

Android Resize Resolution / Calibrate Screen Height & Position

Hello, i have the 1cm dead touchscreen zone in the top and bottom, not good for the android taskbar...
Can we recalibrate the resolution / screen parameter to reduce a little the screen height to fix the problem ??
Thank you.

same problem here .. heeeelp

yeeeeeeeeeeeee .. after month or more looking for solution and tried everything on web i finally found it broo
download from the play store NOmone resolution changer and use it
our default settings is 1024 768 160
u just change the first number i use 880 768 160
as i have 2 cm below of dead touchscreen :S
i hope this works for u

I7V said:
yeeeeeeeeeeeee .. after month or more looking for solution and tried everything on web i finally found it broo
download from the play store NOmone resolution changer and use it
our default settings is 1024 768 160
u just change the first number i use 880 768 160
as i have 2 cm below of dead touchscreen :S
i hope this works for u
Click to expand...
Click to collapse
Than You, i had no success with NOMONE Resolution Changer, impossible to install for me tough Play Store (not allowed in my country) and the multiple apk found on the net was not good, an error 'probleme with parsing installer' something like this.
I found "Resolution Changer Pro" who work very well, the perfect resolution for me is : 970 x 768.

Or even easier, use a simple adb debug shell command:
Code:
adb shell
wm overscan 0,300,0,400
For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
The above command will shrink the useful screen area with 300px from top and 400px from bottom.
Feel free to experiment those parameters to find the best fit for your situation.

Hi guys! I start to thank you a lot for your suggestions but before making any disaster i should be really grateful if you could give me an help.
I need to resize the screen of my Nexus 7 (2013) in order to fit with the car-dash enclosure where i'm willing to install it.
The enclosure i bought was supposed to fit for the nexus display but regrettably whilst the latter is of abt 15.3cm wide x 9.5 cm "tall" (sorry for my english) the enclosure has a window of 15.3 cm wide but only 8.7 cm tall which would make impossible the access to the softkeys.
In view of the above and considering also that there is no space available to enlarge the window of the enclosure i thought and hoped it would have been easier to resize the screen.
Now the question is: considering that the measures reported are relevant to the device in landscape mode may i kidly ask you the command variables that i have to amend to cut off the 0.8 cm on the bottom side of the screen (again landscape mode).
Thanks a lot in advance for your help!

Hello, Please i need help. I have a Dead Touch Zone (at the bottom 30% aprox.), i installed and i resized screen with ADB (adb shell wm overscan 0,0,0,600) BUT... I can´t use some apps (google play, whatsaap, etc) because it shows like they are behind backgroud.. Check pics attached for understanding.

eric_thefool said:
Hi guys! I start to thank you a lot for your suggestions but before making any disaster i should be really grateful if you could give me an help.
!
Click to expand...
Click to collapse
Did you solve the problem?

davis_llb26 said:
Hello, Please i need help. I have a Dead Touch Zone (at the bottom 30% aprox.), i installed and i resized screen with ADB (adb shell wm overscan 0,0,0,600) BUT... I can´t use some apps (google play, whatsaap, etc) because it shows like they are behind backgroud.. Check pics attached for understanding.
Click to expand...
Click to collapse
Did u get through with this problem..??
i too have the same problem but mine is 25% of the screen so i can use whats app and all other app but the plain box is disturbing me too...

Confirm the adb route works without root!
silvake said:
Or even easier, use a simple adb debug shell command:
Code:
adb shell
wm overscan 0,300,0,400
For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
The above command will shrink the useful screen area with 300px from top and 400px from bottom.
Feel free to experiment those parameters to find the best fit for your situation.
Click to expand...
Click to collapse
A long time since the original post and answers, but I thought it should be noted that this method works well. Thanks silvake.
My Mecer tablet stopped responding in the top 2-3cm after many years of loyal service. Could have been a drop or simply age. It is still useful and wish to give it to someone in need. So searching around and several different sites yielded some results. Note this is not a mainstream device so rooting was not an option nor attempted. Indeed drivers and any info is sparse for this device.
For anyone attempting this, I will outline my method and steps.
1. Enable USB debugging. There are many tutorials. Settings->About->Build number(tap x 7); Developer Options->USB debugging
2. Connect device with USB Cable. Give permission on device. You will need to make sure that windows installs drivers. At first windows failed to install all drivers. Not sure how it managed, but it connected eventually.
3. Download adb: https://android.izzysoft.de/downloads.php. I used https://android.izzysoft.de/downloads.php?file=adb-binaries-windows-29.0.4.zip. Decompress to desired folder. Open cmd to the folder.
4. Run adb.exe with 'adb devices' and confirm device is listed. First attempt showed:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
0123456789ABCDEF unauthorized
I had to give permission on the device. Reconnected USB.
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
List of devices attached
0123456789ABCDEF device
Success! Device is now connected.
Next get the current display stats:
Type 'adb shell'
Confirm connection. Mine showed: [email protected]:/ #
Type: ‘dumpsys display | grep mBaseDisplayInfo’
Below is the capture of the operation:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
[email protected]:/ # dumpsys display | grep mBaseDisplayInfo
mBaseDisplayInfo=DisplayInfo{"Built-in Screen", app 800 x 1280, real 800 x 1280, largest app 800 x 1280, smallest app 800 x 1280, 55.84 fps, rotation0, density 190 (190.0 x 190.0) dpi, layerStack 0, type BUILT_IN, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
This is not really required but helps to determine the current stats to make a guess on the number of pixels to adjust the screen by.
Next is the command to adjust the screen. The 4 numbers are the coordinates. Since mine was the top area I adjusted only that.
Type: wm overscan 0,50,0,0
The update is live and you should see the screen drop 50 pixels from the top.
This was not enough for me so repeat until the pull down of the status bar starts working again.
Here is the whole list to adjust the screen until everything is working again:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
[email protected]:/ # wm overscan 0,50,0,0
[email protected]:/ # wm overscan 0,70,0,0
[email protected]:/ # wm overscan 0,80,0,0
[email protected]:/ # wm overscan 0,100,0,0
[email protected]:/ # wm overscan 0,200,0,0
[email protected]:/ # wm overscan 0,120,0,0
[email protected]:/ # wm overscan 0,140,0,0
[email protected]:/ # wm overscan 0,150,0,0
[email protected]:/ # wm overscan 0,160,0,0
[email protected]:/ # wm overscan 0,170,0,0
[email protected]:/ # wm overscan 0,180,0,0
[email protected]:/ # wm overscan 0,190,0,0
[email protected]:/ # wm overscan 0,195,0,0
[email protected]:/ # exit
So I had to move the screen 195 pixels down until the dead touchscreen area was excluded.
Screen is obviously smaller but the frustration of having to rotate the device 180 to be able to pull down the status bar is removed. Much worth it.
Now a child in need of education can still learn and we have saved the device from landfill and reduced the carbon footprint.
You might have to adjust the pixel density to compensate for the loss, but I left it untouched. Your results will vary so I cannot assist.
Excerpt from another site:
"Additionally decreasing the density through the settings (Display & lights > screen > LCD density) or the wm command helped compensating for the lost display area:
wm density 360"
Hope this helps someone as it helped me.
T

Hello amazing people,
I am looking for your guide/advice for solving a screen resolution issue.
I am using a 4:3 ratio screen with a LCD driver on Radxa Zero.
the poblem is that the screen looks stretched laterally. I think its due to aspect ratio becuase the lcd is of 4:3 aspect ratio.
can anyone help me how can I change the aspect ratio using adb?
I have worked with size and density but failed to produce any results.
Many thanks to this amazing community.

the side of may cellphone is not working

[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?