mapbox / mapbox/mapbox-maps-android

Map freezes or becomes black some times on Android Auto

Open
#2,251 21 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

auto-triaged bug :beetle:
Dominant language
Kotlin
Stars
578
Forks
161
PR merge metrics
No merged PRs in 30d

Description

## Environment

- Android OS version: 14
- Devices affected: Samsung Galaxy S21, Samsung Galaxy S22+, Samsung Galaxy Flip 3 (other users have reported this as well, I'll try to get their phone model)
- Android Auto version: 10.9.634644
- Maps SDK Version: 10.16.3 (Android Auto extensions 0.5.0)

## Observed behavior and steps to reproduce

Has been hard for us to reproduce. One user reports that the map is just always black, but alertboxes, navigation manuevers, speedometer and action strip is shown and works.

In our reproduced version of the bug, the map worked for some time but then froze. Everything except the map worked and the screen reacted to touch. According to the log scrolls, zooms and flings where detected as expected, but nothing happened on the screen. Clicking into a menu and going back the map turned black.

The map on the phone worked fine throughout all of this.

Will update with video of the behaviour if I can reproduce it again or make a user send a video.

## Expected behavior

Screen is not black.

## Notes / preliminary analysis

I've seen this in the log coming up rapidly (~50 times a second) on a device that experienced the issue, but I'm not sure this is related:
[maps-android\Mbgl-RenderThread]: renderThreadPrepared=false and Android surface is not valid (isValid=false). Waiting for new one.

The issue has only started appearing after updating to 10.16.3

## Additional links and references

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the Android Auto behavior with the phone map using Maps SDK 10.16.3 and Android Auto extensions 0.5.0. Investigate the repeated renderThreadPrepared=false and invalid Android surface log message, using the listed devices and Android Auto 10.9.634644 if the failure can be reproduced. Done means identifying and fixing the cause so the Android Auto map remains visible and responsive.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.