07-03-2020, 09:06 PM
RPI 4b
Openauto Pro 9.0
Std Mic
External Bluetooth (I don't remember which one but I do know that it isnt broadcom.)
Hifiberry Amp2 HAT
Connected Pro
Samsung Galaxy S7 edge
At first install of OAP 9.0, I marveled at the speed it booted up, and said so here. At that time, the bootup occurred before I paired bluetooth. The sequence, in part, loaded bluetooth and notified me of the pairing then displayed the AA map screen (fyi, my phone screen briefly displayed AA then went blank).
After bluetooth pairing and then rebooting, the sequence goes from loading and notifying me of pairing bluetooth to a screen asking which way I want to start AA (but AA is already up and still displayed on my phone). Phone AA to OAP is a hit or mostly miss connection.
If I delete the bluetooth pairing, AA starts up in a normal and fast way just like the first install. Thinking it might be the external bluetooth adapter causing the conflict (just a guess), give me a URL to one that causes zero conflict and I'll change it out.
As you might guess, I can run all of the bluetooth features and I can run AA ... usually, just not at the same time. However, it's not a never and always proposition. Sometimes (rarely) bluetooth, AA and OAP connect the first time as intended. If it doesn't, I restart it time and again until it does. By that time, the car ride is over :-(
Openauto Pro 9.0
Std Mic
External Bluetooth (I don't remember which one but I do know that it isnt broadcom.)
Hifiberry Amp2 HAT
Connected Pro
Samsung Galaxy S7 edge
At first install of OAP 9.0, I marveled at the speed it booted up, and said so here. At that time, the bootup occurred before I paired bluetooth. The sequence, in part, loaded bluetooth and notified me of the pairing then displayed the AA map screen (fyi, my phone screen briefly displayed AA then went blank).
After bluetooth pairing and then rebooting, the sequence goes from loading and notifying me of pairing bluetooth to a screen asking which way I want to start AA (but AA is already up and still displayed on my phone). Phone AA to OAP is a hit or mostly miss connection.
If I delete the bluetooth pairing, AA starts up in a normal and fast way just like the first install. Thinking it might be the external bluetooth adapter causing the conflict (just a guess), give me a URL to one that causes zero conflict and I'll change it out.
As you might guess, I can run all of the bluetooth features and I can run AA ... usually, just not at the same time. However, it's not a never and always proposition. Sometimes (rarely) bluetooth, AA and OAP connect the first time as intended. If it doesn't, I restart it time and again until it does. By that time, the car ride is over :-(