The app selector (home button) has a display scaling option that allows standard or default mode, for apps that don't work well in 2340x1080p, you can run them in 1920x1080p.
HOWEVER, this is centered from the top left, resulting in awkward displays especially in landscape mode. with 420 width of pixels on the right side and none on the left.
Is there a way to center the output, starting the black bars/image at 210 pixels from both sides respectively?
Rooted solutions are fine.
Yes true, i used to play pubgm with this view
You can use FK Manager actually
Related
How can I set surface.rotation to always be 90 degrees so I'm always in landscape? I found an app that limits rotation to 0 and 90 but I would like to always be in landscape. Can I change a value for surface.rotation in android.view.display.getrotation with SQlite?
public int getRotation ()
Since: API Level 8
Returns the rotation of the screen from its "natural" orientation. The returned value may be Surface.ROTATION_0 (no rotation), Surface.ROTATION_90, Surface.ROTATION_180, or Surface.ROTATION_270. For example, if a device has a naturally tall screen, and the user has turned it on its side to go into a landscape orientation, the value returned here may be either Surface.ROTATION_90 or Surface.ROTATION_270 depending on the direction it was turned. The angle is the rotation of the drawn graphics on the screen, which is the opposite direction of the physical rotation of the device. For example, if the device is rotated 90 degrees counter-clockwise, to compensate rendering will be rotated by 90 degrees clockwise and thus the returned value here will be Surface.ROTATION_90.
This is something I haven't seen before. I just got a Nexus 6, and on the first day I had it, I poked around on the phone with the OOB configuration, and chrome did work in landscape. Videos would be full screen, etc. Since then, I have:
Upgraded to 5.0.1
Rooted the phone
Removed the encryption
Changed the dpi to 493 with textdroider
Replaced the google launcher with Nova
Set the desktop grid to 8x7
Now, if I switch the chrome into landscape mode, the page takes up the whole screen for about a second, but then half of the screen becomes black, like there is an overlay over it. It cuts off the bottom half of the page. This happens when playing full screen videos in chrome too. Everything else on the phone, including the desktop.
I put the dpi back to its original value, but that didn't matter, so I changed it back. I've also set the desktop grid in Nova back to its original settings, which also didn't matter. I tried using chrome beta, but it has the same issue. Has anyone experienced this before? I haven't found any other examples of this. I tried to take a screenshot to post here, but the screenshot came out looking normal.
Fixed it.
Setting the DPI back to 560 fixed the issue. It must just not like the 493. I tried 520, but that didn't work either. I'm going to try 480 now, since 493 looked pretty nice.
cptInsane0 said:
This is something I haven't seen before. I just got a Nexus 6, and on the first day I had it, I poked around on the phone with the OOB configuration, and chrome did work in landscape. Videos would be full screen, etc. Since then, I have:
Upgraded to 5.0.1
Rooted the phone
Removed the encryption
Changed the dpi to 493 with textdroider
Replaced the google launcher with Nova
Set the desktop grid to 8x7
Now, if I switch the chrome into landscape mode, the page takes up the whole screen for about a second, but then half of the screen becomes black, like there is an overlay over it. It cuts off the bottom half of the page. This happens when playing full screen videos in chrome too. Everything else on the phone, including the desktop.
I put the dpi back to its original value, but that didn't matter, so I changed it back. I've also set the desktop grid in Nova back to its original settings, which also didn't matter. I tried using chrome beta, but it has the same issue. Has anyone experienced this before? I haven't found any other examples of this. I tried to take a screenshot to post here, but the screenshot came out looking normal.
Click to expand...
Click to collapse
Change lcd density to 560 in /system/build.prop, save changes, exit, and then reboot. 520 was the closest I've found that was free of issues but chrome would still have that issue in landscape with side buttons down. In landscape with side buttons up, however, chrome works fine in landscape in 520. I'm sure other values will provide the same but it seems other apps get affected.
480 was a no-go
Nope, issue persists on 480 too. Guess I'm going to be stuck at 560 until this is figured out.
cptInsane0 said:
Setting the DPI back to 560 fixed the issue. It must just not like the 493. I tried 520, but that didn't work either. I'm going to try 480 now, since 493 looked pretty nice.
Click to expand...
Click to collapse
460 DPI seems to work for me. I had issues with 480 and other DPI I tried as well. Seems hit or miss at certain settings.
460 works fine. I started at 480 and had half black screen as well.
I have been fiddling with different settings and 498 was the lowest/smallest I have been able to get with out any issues what so ever. With other numbers that I have seen seem to work but then I always end up with letters in the keyboard being cut off from the pop-up when I tap them. I don't know much about how the screen works and how scaling works to figure it out which DPI's will work with out any issues.
493 dpi over here.
I experience half black screen bug in landscape when i rotate my phone in such way that my power/volume buttons are on the buttom of the phone and if the keyboard is not present.
if I rotate the phone in proper direction, meaning, when the phone is in a landscape position and my power/volume buttons are located at the top of the phone, bug isn't present.
if keyboard is present and the phone is in landscape mode( power/volume buttons on the bottom) position results in keyboard flashing/constantly trying to redraw itself every time I press on keyboard.
Black overlay bug is system wide for me, not just in chrome(also present in other browsers, message app, file manager, etc), so I think the bug lies in Google Keyboard not liking 493dpi in landscape.
{ I'm as well, removed the encryption, root'ed, 5.0.2(AOSP, LRX22G, Pure Shamu) with Nova(12x7 grid) as default launcher. }
I just wanted to let you know that this issue seems to be resolved on Android 6 / Marshmallow.
I'm now able to set the density to 384dpi without getting the infamous half black screen in landscape mode (when the phone is rotated clockwise).
FYI: 384dpi is the highest value possible to keep the UI in tablet mode (including 4-way screen rotation, etc). From 385dpi up the UI switches to phone mode.
- Please install this app on your phone > https://play.google.com/store/apps/details?id=com.crystalmissions.dpichecker
- Set display size to default settings
- Open DPI Checker app
- Take a screenshot (Volume Down + Power Button)
- Post Screenshot here (Under the 'Attach Files' Section)
After the latest update, about a week or two ago, I noticed a fuzziness to my display with jagged icon edges and odd font sizes. I downloaded the above app, and when I opened it, it stated something like 320x533, I really cant remember, but it was a really far off display density from the Moto E4 Plus' reported 720p - 720x1280.
I just want to see if other are having this issue or if it was just me. Thanks.
The below screenshot is an example. I have already set my display back to 720x1280.
Code:
adb shell
Code:
wm size 720x1280
Code:
wm density 320
Anybody?
I can't seem to find the attachments button
photos.app.goo.gl/Tu7PhsYgOxX1NM0y2
Hmmm... Wonder why my display is so off...
Thanks for posting.
@qweedleguy screenshot:
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?