The feedback items are already customizable when you create your own Screen and Template. All you have to do is create a list of CarFeedbackItem from the CarFeedbackItemProvider and use CarFeedbackAction and show the CarGridFeedbackScreen.
What is not customizable, is if you're using a higher level screen such as CarRoutePreviewScreen or MainScreenManager. Then the feedback items are hard coded.
When updating the car feedback implementation. Please update the public documentation to include a section about how feedback works in android auto https://github.com/mapbox/android-docs/pull/2087
The feedback items are already customizable when you create your own
Screen
andTemplate
. All you have to do is create a list ofCarFeedbackItem
from theCarFeedbackItemProvider
and useCarFeedbackAction
and show theCarGridFeedbackScreen
.What is not customizable, is if you're using a higher level screen such as
CarRoutePreviewScreen
orMainScreenManager
. Then the feedback items are hard coded.Solution here seems as simple as, adding
CarFeedbackItemProvider
to the constructor of screens. Null could disable the feedback action. But there is refactoring needed to extract the hard coded feedback items https://github.com/mapbox/mapbox-navigation-android/blob/623705630c6b2cf20e16db82bbd56c5264bfdde4/libnavui-androidauto/src/main/java/com/mapbox/androidauto/car/feedback/ui/CarFeedbackItem.kt#L38-L41EDIT:
When updating the car feedback implementation. Please update the public documentation to include a section about how feedback works in android auto https://github.com/mapbox/android-docs/pull/2087