OAP 8.0
RPI 4b
Samsung Galaxy 7Edge
Phone teathered via USB cable (because OAP wifi connect issues)
I start OAP at then plug in my phone's usb cable. As the system starts, I first encounter a pop-up message on the headunit that the phone is attached to RPI through bluetooth. This is confirmed through ConnectedPro as well. Then, I can see on the phone that AA opens and an AA message appears on the phone saying AA is connected to my car but the OAP screen appearing on the headunit display says [RESUME] [DAY/NIGHT] for a moment then goes to the AA connection screen that presents the multiple connection choices. When I select [USB] it starts trying to connect to the phone (but the phone is running AA already). After a while, OAP times out saying AA is not available. If I restart the RPI multiple times, it will eventually connect AA to- the headunit display. I have not yet figured out what's different when it finally starts after previous failed attempts. It appears to me that OAP starts AA on my phone but doesn't get the confirmation from my phone that it is looking for in the time period it has allowed. So it goes to the AA connect screen and then trys to start the program but fails becasue it is already running. I may have it totally wrong but it would explain the steps I encounter.
UPDATE: I've discovered somewhat of a work around for USB connection of phone to OAP/RPI. I start up AA on my phone and once it is fully up and running I then start the Pi. It still hangs at trying to connect via USB the first time. Then I power off the Pi and restart it. The phone connects to the headunit every time after the restart.
RPI 4b
Samsung Galaxy 7Edge
Phone teathered via USB cable (because OAP wifi connect issues)
I start OAP at then plug in my phone's usb cable. As the system starts, I first encounter a pop-up message on the headunit that the phone is attached to RPI through bluetooth. This is confirmed through ConnectedPro as well. Then, I can see on the phone that AA opens and an AA message appears on the phone saying AA is connected to my car but the OAP screen appearing on the headunit display says [RESUME] [DAY/NIGHT] for a moment then goes to the AA connection screen that presents the multiple connection choices. When I select [USB] it starts trying to connect to the phone (but the phone is running AA already). After a while, OAP times out saying AA is not available. If I restart the RPI multiple times, it will eventually connect AA to- the headunit display. I have not yet figured out what's different when it finally starts after previous failed attempts. It appears to me that OAP starts AA on my phone but doesn't get the confirmation from my phone that it is looking for in the time period it has allowed. So it goes to the AA connect screen and then trys to start the program but fails becasue it is already running. I may have it totally wrong but it would explain the steps I encounter.
UPDATE: I've discovered somewhat of a work around for USB connection of phone to OAP/RPI. I start up AA on my phone and once it is fully up and running I then start the Pi. It still hangs at trying to connect via USB the first time. Then I power off the Pi and restart it. The phone connects to the headunit every time after the restart.