wm overscan alternative?

[dudos]

Hi, I've search for a solution to the above title, but most are related to swipe gestures and removing the notification bar, which is not what I want to achieve really.

I have a phone (Rooted, S10+ Lineage 18.1, Android 11) embedded into car dash in portrait mode and the bottom of the screen (around 10%) is covered by the dash itself.

I can use "wm size" to shrink the display to make it usable, but that creates an ugly border at the top of the screen too. overscan used to be perfect on the previous phone (S7 in my old setup).

Is there anything at all I can use to do what overscan used to do? Or anyway to re-introduce overscan to Lineage 18.1?

 

[dudos]

I see if I do a "dumpsys display" I get amongst things:

D:\Android\adb>adb shell dumpsys display
...
mViewports=[DisplayViewport{type=INTERNAL, valid=true, isActive=true, displayId=0, uniqueId='local:0', physicalPort=0, orientation=1, logicalFrame=Rect(0, 0 - 2150, 1440), physicalFrame=Rect(445, 0 - 2595, 1440), deviceWidth=3040, deviceHeight=1440}]
...
DisplayDeviceInfo{"Built-in Screen": uniqueId="local:0", 1440 x 3040, modeId 1, defaultModeId 1, supportedModes [{id=1, width=1440, height=3040, fps=60.000004}, {id=2, width=1080, height=2280, fps=60.000004}, {id=3, width=720, height=1520, fps=60.000004}], colorMode 0, supportedColorModes [0, 7, 9], HdrCapabilities HdrCapabilities{mSupportedHdrTypes=[2, 3], mMaxLuminance=400.0, mMaxAverageLuminance=120.0, mMinLuminance=5.0E-4}, allmSupported false, gameContentTypeSupported false, density 420, 522.514 x 521.729 dpi, appVsyncOff 1000000, presDeadline 16666666, cutout DisplayCutout{insets=Rect(0, 142 - 0, 0) waterfall=Insets{left=0, top=0, right=0, bottom=0} boundingRect={Bounds=[Rect(0, 0 - 0, 0), Rect(1114, 0 - 1440, 142), Rect(0, 0 - 0, 0), Rect(0, 0 - 0, 0)]}}, touch INTERNAL, rotation 0, type INTERNAL, address {port=0}, deviceProductInfo null, state ON, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}

Is there any ini/conf files that control these viewport/logicalFrame/rect at startup?

 

[dudos]

Or could tasker be used to set it after the OS has booted? I've used tasker for a few primitive things, (connect bluetooth, start media , auto-power off etc), but never delved into the guts of system param changes.

 

[dudos]

Also as I'm a software developer (albeit with no Android application experience), I could even write a Java or Native C++ application to do it if that's possible? Looking into all the NDK/SDKs etc now, but have not found the solution so far. Any clues?

 

[Oswald Boelcke]

Hi, I've search for a solution to the above title, but most are related to swipe gestures and removing the notification bar, which is not what I want to achieve really.

I have a phone (Rooted, S10+ Lineage 18.1, Android 11) embedded into car dash in portrait mode and the bottom of the screen (around 10%) is covered by the dash itself.

I can use "wm size" to shrink the display to make it usable, but that creates an ugly border at the top of the screen too. overscan used to be perfect on the previous phone (S7 in my old setup).

Is there anything at all I can use to do what overscan used to do? Or anyway to re-introduce overscan to Lineage 18.1?

Hello and good afternoon, @dudos

Prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

forum.xda-developers.com

and the others. I've moved your thread to Android Q&A.

Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator