mapbox / mapbox/mapbox-maps-android
Android Auto render issues
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 578
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Description
## Environment
- Android OS version: 15
- Devices affected: OnePlus Nord 4
- Maps SDK Version: 11.6.0
## Observed behavior and steps to reproduce
We have some customers who at times have issues in android auto with render problems + reversed large bitmap.

Unsure how to reproduce since its not a problem everyone is having. Furthermore this also appears to be a somewhat recent issue and was not something we have heard of before
## Expected behavior
This is how its supposed to look like

## Notes / preliminary analysis
The speedometer is a BitmapWidget from com.mapbox.maps.renderer.widget
We add this widget to the map as such
```
fun attachWidgets(mapboxCarMapSurface: MapboxCarMapSurface, showSpeedometer: Boolean) {
this.mapSurface = mapboxCarMapSurface.mapSurface
with(mapboxCarMapSurface) {
mapSurface.addWidget(logoWidget)
if (showSpeedometer) {
mapSurface.addWidget(speedometerWidget)
speedometerWidget.startObservers()
}
}
}
```
which is called when onAttached is triggered from MapboxCarMapObserver
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the BitmapWidget usage in attachWidgets and the onAttached path from MapboxCarMapObserver, using the Android Auto render screenshots and the listed Android 15, OnePlus Nord 4, and Maps SDK 11.6.0 environment. Done means identifying and correcting the intermittent render and reversed-large-bitmap behavior so the widget matches the expected appearance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100