2024-04-17, 07:57 AM
i have noticed that when using the android client over a direct Bluetooth car connection, the music queue is updated according to my choices and content is cached for cases when the client cannot connect to the network (tunnels, garages, etc).
but when i am using the client from an adroid auto terminal, the queue is not updated, the playlist choice are not remembered, and the content is not cached.
based on the fact that my android auto setup uses a Bluetooth connection other than the car Bluetooth connection, i have to ask:
is there an interaction between the play queue and the Bluetooth connection? is the play queue indexed/mapped/keyed on the Bluetooth connection but the client is not smart enough to recognize that it may be possible for the same client to use different connections. in my case, the second Bluetooth connection appears because i am using an external gizmo for wireless android auto. the original Bluetooth connection that remembers play queues and content is used for wired android auto connections
but when i am using the client from an adroid auto terminal, the queue is not updated, the playlist choice are not remembered, and the content is not cached.
based on the fact that my android auto setup uses a Bluetooth connection other than the car Bluetooth connection, i have to ask:
is there an interaction between the play queue and the Bluetooth connection? is the play queue indexed/mapped/keyed on the Bluetooth connection but the client is not smart enough to recognize that it may be possible for the same client to use different connections. in my case, the second Bluetooth connection appears because i am using an external gizmo for wireless android auto. the original Bluetooth connection that remembers play queues and content is used for wired android auto connections