Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Beta - Android Auto stuck on Connecting
#1
Hello,
I just installed the BETA version of OAP and everything is working except for Android Auto.

When I connect it via USB,  OAP just says 'connecting' but never actually opens the AA interface.
The lock screen on my phone says that AA is connected,  but if I actually open AA on the phone it says no connected cars.

It was working in current stable release of OAP,  but since I had to reflash the card to try the beta,  not sure if I could have messed something else up removing it from the car.

Any thoughts?

Using a Galaxy S8
I've tried connecting the USB cable via the powered HUB and also directly to the PI
I have a USB soundcard, and mic installed and appear to be working in OAP
Reply
#2
Steps I've tried so far,
1. Clear Cache of AA
2. Uninstall/Reinstall AA
3. Move USB cable to pi directly

So far no luck
Reply
#3
So far nobody have reported similar issue, therefore we would say that it is your setup configuration...

Try to reproduce the issue several times and send us this log file from RPI: /home/pi/.openauto/cache/openauto.log
At email: software@bluewavestudio.io
Reply
#4
Just sent.
Also, I tried it with my wife's phone and the same thing is happening. AA just says connecting and never displays the UI.
Reply
#5
(07-30-2019, 08:54 PM)Chrisfromwa Wrote: Just sent.
Also, I tried it with my wife's phone and the same thing is happening. AA just says connecting and never displays the UI.

There is no phone connection phase visible in provided logs. Did you try to connect/disconnect the phone several times? If yes, it looks like your Raspberry PI did not detect USB connection.
Reply
#6
Yes, I've tried it several times with 2 phones.
When I connect the cable the PI displays a prompt about a media source has been connected and the phone displays a prompt asking if it's OK to allow data to transfer between connected device

I selected OK for this.
Reply
#7
Here is what I see on the lockscreen of the phone
[Image: lockscreen.jpg]


and here is what the OAP screen displays


Attached Files Thumbnail(s)
   
Reply
#8
Please try collect logs once again because in those provided there is no single line that phone was connected to the USB.
Reply
#9
I've tried again,  brought the whole system back into the house.
Tried it with the original cable,  and a brand new cable.    

Any ideas of what else I can do to get this working?   I was so close to finally getting all of this installed in the car.

Here is the log again.  This is trying to start it with 2 different cables.
I also tried different USB ports (note that all other USB Devices seem to be working OK)

[2019-07-31 14:00:21.511655] [0x712fa260] [warning] [OpenAuto] [RecentAddressesList] failed to read configuration file: .openauto/config/openauto_wifi_recent.ini, error: .openauto/config/openauto_wifi_recent.ini: cannot open file. Empty list will be used.
[2019-07-31 14:00:21.609205] [0x712fa260] [warning] [OpenAuto] [ObdConfiguration] failed to read configuration file: .openauto/config/openauto_obd_pid_info.ini, error: .openauto/config/openauto_obd_pid_info.ini: cannot open file. Empty list will be used.
[2019-07-31 14:00:21.609698] [0x712fa260] [warning] [OpenAuto] [ObdConfiguration] failed to read configuration file: .openauto/config/openauto_obd_sport_dashboard.ini, error: .openauto/config/openauto_obd_sport_dashboard.ini: cannot open file. Empty list will be used.
[2019-07-31 14:00:21.610025] [0x712fa260] [warning] [OpenAuto] [ObdConfiguration] failed to read configuration file: .openauto/config/openauto_obd_detailed_dashboard.ini, error: .openauto/config/openauto_obd_detailed_dashboard.ini: cannot open file. Empty list will be used.
[2019-07-31 14:00:21.666271] [0x712fa260] [debug]   [OpenAuto] [UI::TemperatureSensorController] sensor is not configured.
[2019-07-31 14:00:21.668781] [0x712fa260] [info]    [OpenAuto] [DayNightManager] OpenAuto manual mode changed, mode: 1
[2019-07-31 14:00:21.668945] [0x65dfa370] [info]    [OpenAuto] [AndroidAutoApp] Initialized display region width: 800, height: 452, x: 0, y: 28
[2019-07-31 14:00:21.669100] [0x65dfa370] [info]    [OpenAuto] [AndroidAutoApp] Initialized screen geometry width: 800, height: 452, x: 0, y: 28
[2019-07-31 14:00:23.174564] [0x712fa260] [info]    [OpenAuto] [BluetoothInitializer] starting backend...
[2019-07-31 14:00:23.175529] [0x712fa260] [info]    [OpenAuto] [HandsFreeModemsList] telephony availability changed: true
[2019-07-31 14:00:23.949289] [0x712fa260] [error]   [OpenAuto] [BluetoothInitializer] Error initializing bluetooth manager: Cannot find org.bluez.Media1 object!
[2019-07-31 14:00:24.040319] [0x712fa260] [info]    [OpenAuto] [BluetoothInitializer] Obex service start result: 1, error: 0
[2019-07-31 14:00:24.072098] [0x712fa260] [info]    [OpenAuto] [Phonebook] obex manager operational changed, value: true
[2019-07-31 14:00:24.083792] [0x712fa260] [info]    [OpenAuto] [AutoConnector] discovery already started.
[2019-07-31 14:00:24.084015] [0x712fa260] [info]    [OpenAuto] [TelephonyController] Activating.
[2019-07-31 14:00:24.084114] [0x712fa260] [info]    [OpenAuto] [OpenAuto] Initializing interprocess routines.
[2019-07-31 14:00:24.084952] [0x712fa260] [info]    [OpenAuto] [OpenAuto] Initialized interprocess routines.

so to add to the mystery even more, in settings I selected the auto start AA.
and when I connect the USB,  I do see the icon in the upper right hand corner.

but if I click on resume nothing happens.


Attached Files Thumbnail(s)
   
Reply
#10
I've notice if I reboot the PI,  and try and connect the cable.
I initially get this warning,  but it goes away on it's own.



More about my phone:
Android Version:  9
Android Auto Version:  4.4.592344


Attached Files Thumbnail(s)
   
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)