Black bars (safe area insets) on Lenovo M8/M10

Configuration Frontend
, , ,
1

Hi all,

I’m seeing a new issue on my Lenovo M8 and M10 tablets running the HA Companion app. After updating to Home Assistant 2025.5+, my dashboards no longer fill the full screen. Instead, there are black bars at the top and bottom of the display. I run dashbaords in fully kiosk mode and this has been great for over a year.

  • Fullscreen / immersive mode is already ON in the Companion app.
  • It worked fine before (I checked an old June backup — same problem now, which points to frontend/WebView changes, not my config).
  • I use kiosk-mode to hide header/sidebar.
  • Issue has arisen on M10 and M8 at the same time.

Cause (I think):

  • Recent HA frontend builds (2025.5+) started respecting safe-area-inset-top/bottom.
  • On Lenovo M8/M10, Android System WebView reports non-zero insets for the status/nav bars.

Workarounds tested:

  • Companion app fullscreen toggle → no effect.
  • CSS loaded via extra_module_url → not applied (only JS modules load here).
  • Custom theme with safe-area-inset-top/bottom: 0px → didn’t resolve.
  • Fully Kiosk Browser with immersive mode → fixes the issue completely (dashboards back to true fullscreen).
  • A tiny JS module injected via extra_module_url to override insets also works.

Ask:

  • Is this new safe area behavior intentional?
  • Could Companion app on tablets force viewport-fit=cover or ignore safe area when fullscreen is enabled?
  • I also note the HA App is crash when reopening on teh lenovo Tablets.
    Any help appreciated thanks
2 Likes
2

Same issue for me!! So frustrating!

3

@seaniefield

Can you share exactly what you did that worked for this workaround
What was the exact file name and file content you did and where did you place it to make it all work?
It’s hard to load Fully Kiosk Browser in my situation

4

It did not work, I eventually jumped to Fully Kiosk Browser as it was the quickest soluion. I spent months getting a working dashboard and was not willing to spend time tinkering around the edges. Fully Kiosk browser seems to work great for my situation.

Sorry I cant be of more help.

1 Like
5

That’s still very useful info, thanks :pray:t2:
It seems they are fixing the android app but we’ll see if it addresses all the issues. The dev mentioned he was not able to reproduce on any of the emulators he runs so it’s a bit of a blind fix based on users’ feedback and that’s always risky