App crashes when accessing Media Browser after URI navigation (GrapheneOS)

[cyberman729]

Home Assistant Android app version(s):
2025.12.2+ (pre-release)

Android version(s):
Android 15 (GrapheneOS build BP4A.251205.006)

Device model(s):
Pixel 9 Pro

Home Assistant version:
2025.12.3

Last working Home Assistant release (if known):
Unknown - this is a new setup

Description of problem, include YAML if issue is related to notifications:

The app crashes with VK_ERROR_DEVICE_LOST GPU fault when accessing the Media Browser after navigating via a notification URI action. This only occurs on GrapheneOS, suggesting a compatibility issue with GrapheneOS hardened memory allocator.

Steps to reproduce:

1. Send notification with URI action button (example URI: /cameras-yaml/0)
2. Tap the URI action button to navigate to a dashboard
3. Dashboard opens successfully
4. Tap any link that opens Media Browser (e.g., link to camera recordings)
5. App immediately crashes with GPU device lost error

Expected behavior:
Media Browser should open normally.

Actual behavior:
App crashes in RenderThread with TRANSLATION_FAULT at GPU memory access level 3.

Important notes:

• Direct navigation to Media Browser works perfectly (without URI navigation first)
• After force-stopping the app, Media Browser works normally again until another URI navigation
• This only happens when Media Browser is accessed after URI-based navigation
• Running GrapheneOS (hardened Android) - crash does not appear to occur on stock Android
• Workaround: Removing URI action button from notifications prevents the crash

Notification YAML:

service: script.send_notification_to_phones
data:
  select_phones:
    - Pixel9
  title: 🔔 Doorbell
  message: Someone is at the front door
  image: /api/camera_proxy/camera.reolink_video_doorbell_wifi_fluent
  actions:
    - action: URI
      title: View Camera & Clips
      uri: /cameras-yaml/0

Companion App Logs:
See attached crash log file

Error in Home Assistant 30411e447c51.txt

[jpelgrom]

Does this also happen when accessing the media browser through Chrome on the device? The app doesn't really do anything this low-level.

[TimoPtr]

I'm aware of this bug, it is only present on Pixel's. It happens on a specific codec used by the stream, for some reason this codec crashes the Vulkan layer VK_ERROR_DEVICE_LOST when the stream is closing. The issue is not specific to Grapene it can be reproduced in the official ROM on multiple devices.

I didn't take the time to check if it was already tracked by Google. If you can @cyberman729 and if it doesn't exist open an issue there.

Can you try another codec like H265 instead of H264, it should solve your issue (but probably creates other issues on other part of HA).