Sponsored

Native Android Auto Development Thread

BeepBoop321

Well-Known Member
First Name
Eric
Joined
Jan 12, 2025
Threads
7
Messages
53
Reaction score
37
Location
USA
Car(s)
2025 Supra 3.0 Premium
Could anyone confirm if the HUD arrows/indicators are working with Carplay?
Sponsored

 

darkhounds

Member
First Name
Liam
Joined
Nov 4, 2026
Threads
0
Messages
5
Reaction score
1
Location
South africa
Car(s)
Mkv supra
Update: coding REMOTE_HMI, A4A and A4A_Remote_Apps to Aktiv worked, thanks! Android Auto now shows in Media.
Wireless still won't connect though. My Galaxy Z Fold 8 pairs fine with the car as a normal Bluetooth phone (Toyota26595), calls and audio work, but the phone just sits on "Connecting to Android Auto" forever. There's no Android Auto toggle on the phone's Bluetooth page for the car.
In /dev/shmem/nbt-aad.log the daemon registers the "AndroidAuto" SPP service and then loops on "waiting for /dev/btspp0 (No such file or directory)", re-registering every 100–150 s. wfd0 is up at 172.16.222.1. So it looks like the phone never opens the Bluetooth SPP connection, which is the same as issue #96 with the Fold 8.
Things I've tried: unpair/re-pair, clearing Android Auto storage, home Wi-Fi off, and Bluetooth audio playing. I also tried a second phone with no luck.
Setup: 2020 SA Supra, NBT EVO ID6, firmware NBTevo_T24081I, nbt-aad v1.9.33 with NBT_ALT_WIFI=DIRECT and NBT_KEEP_PF=1.
Is there anything else to try for wireless? Otherwise I'll try USB on v1.9.43.
 
OP
OP
nanaisu

nanaisu

Well-Known Member
First Name
Ronnie
Joined
Jul 2, 2024
Threads
2
Messages
325
Reaction score
494
Location
United States
Website
bananaisu.com
Car(s)
2022 Supra 3.0 Premium
Update: coding REMOTE_HMI, A4A and A4A_Remote_Apps to Aktiv worked, thanks! Android Auto now shows in Media.
Wireless still won't connect though. My Galaxy Z Fold 8 pairs fine with the car as a normal Bluetooth phone (Toyota26595), calls and audio work, but the phone just sits on "Connecting to Android Auto" forever. There's no Android Auto toggle on the phone's Bluetooth page for the car.
In /dev/shmem/nbt-aad.log the daemon registers the "AndroidAuto" SPP service and then loops on "waiting for /dev/btspp0 (No such file or directory)", re-registering every 100–150 s. wfd0 is up at 172.16.222.1. So it looks like the phone never opens the Bluetooth SPP connection, which is the same as issue #96 with the Fold 8.
Things I've tried: unpair/re-pair, clearing Android Auto storage, home Wi-Fi off, and Bluetooth audio playing. I also tried a second phone with no luck.
Setup: 2020 SA Supra, NBT EVO ID6, firmware NBTevo_T24081I, nbt-aad v1.9.33 with NBT_ALT_WIFI=DIRECT and NBT_KEEP_PF=1.
Is there anything else to try for wireless? Otherwise I'll try USB on v1.9.43.
Are you also seeing:
[BluetoothManager] [ XXX.XXX] ServiceRequestError from the phone: XX:XX:XX:XX:XX service 'SPP'
We've seen it on a few Samsung series phones & Xiaomi specifically and I need ADB logs to troubleshoot
 

Naijaboy

Member
Joined
Aug 30, 2024
Threads
0
Messages
7
Reaction score
7
Location
MD
Car(s)
24 GR Supra
How do you handle going between different versions? Uninstall/install or just reinstall over the existing version?

Never mind. I was able to answer my own question, the software handles reinstallation cleanly over existing files.
 
Last edited:

darkhounds

Member
First Name
Liam
Joined
Nov 4, 2026
Threads
0
Messages
5
Reaction score
1
Location
South africa
Car(s)
Mkv supra
Update: USB works! 🎉

2020 SA Supra, NBT EVO ID6, NBTevo_T24081I, Galaxy Z Fold 8. I updated from v1.9.33 to v1.9.43 (release 360) and turned on "Android Auto over USB (beta)". With the phone on the console USB port and a data cable, Android Auto launches fine.

@nanaisu, to answer your question: yes, wireless shows the ServiceRequestError. The car is detected as Toyota, so NBT_SPP_DIRECTION was 0 and those lines weren't being logged. After setting NBT_SPP_DIRECTION=2, the phone requests SPP about every 5 s and the car refuses it within 2–3 ms:

ServiceRequest from the phone: 'Liam's Z Fold8' 4C:EC:EE:xx:xx:xx service 'SPP'
ServiceRequestError from the phone: 4C:EC:EE:xx:xx:xx service 'SPP'

That was 9 errors in 2 minutes, with A2DP connected the whole time: services: ... A2DP_SOURCE(1), AVRCP(1), HSPGW(1), HFPGW(1) ... SPP(0)

Happy to capture phone ADB / HCI snoop logs for wireless if you tell me what you need. Thanks for the help getting this going!
 
OP
OP
nanaisu

nanaisu

Well-Known Member
First Name
Ronnie
Joined
Jul 2, 2024
Threads
2
Messages
325
Reaction score
494
Location
United States
Website
bananaisu.com
Car(s)
2022 Supra 3.0 Premium
I'll see what I can take back with that & see if there's settings we can change, or maybe added parameters that need to be added somewhere
 
OP
OP
nanaisu

nanaisu

Well-Known Member
First Name
Ronnie
Joined
Jul 2, 2024
Threads
2
Messages
325
Reaction score
494
Location
United States
Website
bananaisu.com
Car(s)
2022 Supra 3.0 Premium
Update: USB works! 🎉

2020 SA Supra, NBT EVO ID6, NBTevo_T24081I, Galaxy Z Fold 8. I updated from v1.9.33 to v1.9.43 (release 360) and turned on "Android Auto over USB (beta)". With the phone on the console USB port and a data cable, Android Auto launches fine.

@nanaisu, to answer your question: yes, wireless shows the ServiceRequestError. The car is detected as Toyota, so NBT_SPP_DIRECTION was 0 and those lines weren't being logged. After setting NBT_SPP_DIRECTION=2, the phone requests SPP about every 5 s and the car refuses it within 2–3 ms:

ServiceRequest from the phone: 'Liam's Z Fold8' 4C:EC:EE:xx:xx:xx service 'SPP'
ServiceRequestError from the phone: 4C:EC:EE:xx:xx:xx service 'SPP'

That was 9 errors in 2 minutes, with A2DP connected the whole time: services: ... A2DP_SOURCE(1), AVRCP(1), HSPGW(1), HFPGW(1) ... SPP(0)

Happy to capture phone ADB / HCI snoop logs for wireless if you tell me what you need. Thanks for the help getting this going!
Yeah, please if you could get ADB Logcat logs, you'll need to enable USB Debugging:
https://www.xda-developers.com/install-adb-windows-macos-linux/
For Bluetooth logs:
Developer options -> Enable Bluetooth HCI snoop log -> Enabled (you can select filtered if you like), & restart Bluetooth. Then connect to the car, try to start AA.

Make sure your phone is plugged into your computer. For ADB Commands:
adb devices
Make sure you can see your phone, and accept the popup that says "Trust device XYZ"
adb logcat -b all > adb-logs.txt

Or apparently, you can run try dialing: *#9900# then select "Run dumpstate/logcat" and copy the logs to your phones storage & send them. You can email them to me at: [email protected] or send them to me in DMs. Your choice.

Thank you!
 
Joined
Jun 14, 2022
Threads
4
Messages
22
Reaction score
9
Location
Portland, OR
Car(s)
GR Supra 2022
Is audio running through Wi-fi successful yet versus Bluetooth and curious about the sound quality for Lossless. Also is there a way to have a preference to change when the turn shows on the HUD I think right now it shows half a mile out I think?
 
OP
OP
nanaisu

nanaisu

Well-Known Member
First Name
Ronnie
Joined
Jul 2, 2024
Threads
2
Messages
325
Reaction score
494
Location
United States
Website
bananaisu.com
Car(s)
2022 Supra 3.0 Premium
Is audio running through Wi-fi successful yet versus Bluetooth and curious about the sound quality for Lossless. Also is there a way to have a preference to change when the turn shows on the HUD I think right now it shows half a mile out I think?
1. Yes, it's properly usable, the biggest missing thing is the thumb knob for media controls doesn't work. I have a fix, I've tested it in my car and is usable. I don't know about other BMWs though. It tracks the location of the cursor & mimics the skip/previous button. I'm not sure about portability, but I can release a test build tomorrow.
2. Yes, I have a feature I'm going to roll out in the next hour or so that has an always show option. I had always run mine with it in the env file, so was unaware of the half mile limit.
Sponsored

 
 








Top