Weitere Informationen unter ).įor that, I did install the Android Auto App (as it is necessary for < Android 10). More information under ” (roughly translated from German: keine installierten Apps für dieses USB-Zubehör. When I tried to connect via Android Auto, I got the following error message: “Android Open Automotive Protocoll - no Apps installed for this USB-device. Can someone explain to me in easy words what is missing in MicroG to support Android Auto? Is it realistic that we will see this in the near future? However, there seem to be ways of overcoming this (see here: microG + Android Auto fully working | | XDA Forums), but they require flashing (i.e., installing from scratch) /e/ and I’m not sure if this will really help. It seems to be that the Problem is related to MicroG, which does not support Android Auto at all (see here: Implementation Status (I know that using these apps goes partly against the idea behind /e/ and is not the best option for some of us, but let’s leave out that discussion here!) Making Android Auto work would be a big benefit for some of us, you could control apps like GMaps or Spotify directly from your car. The tendency is however negative (see e.g., here: /e/ and Android Auto?) I wondered, if /e/ supports Android Auto (or can be made doing it), but I did not find a clear answer to that in the forum.
Is it possible to use an /e/ Smartphone with Android Auto?
0 kommentar(er)
