Native Android Auto Development Thread

[nanaisu]

So, I probably should have made this thread a little bit sooner, but this thread is going to be for keeping track of the latest updates in the native android auto project && eventually serve as a full guide on how to deploy it on your car.

Where The Code Lives:
Because I don't want to be one of those people who never delivers on it, I'm periodically going to push milestone updates to GitHub, so in case I drop this, someone can hopefully pick back up on it.

The code will live here: https://github.com/Sq00ky/Supra-iDrive6-Android-Auto

Each milestone sub folder will have major project milestones in it, ex:
Milestone 2: Phone -> Head Unit Android Auto Video Streaming (Complete)
Milestone 3: Head Unit hosts AA server w/ touch controls & Bluetooth SPP Registration -> WiFi (Complete - some DPI adjustments needed.)
Milestone 4: iDrive Knob controls + Audio streaming (WIP)
Milestone 5: Native integration into iDrive via HMI Plugins (Not Started)

Babblings & Credit Where It's Due:
So, I'm going to preface it with this: This is 100% an AI generated project. I don't have the skills to do this, I recognize this. I'm nowhere near skilled enough in reverse engineering or software development. I wish I was. The amount of time and work it would take to get to this point without AI would be unreal. Believe me, there's no one more resistant to this stuff than me. But... here it is doing things I can't do. So, embrace the future old man, or something.... I'm sorry if this offends you, it offends me. But gotta do this before some vendor decides they want to do it and sell it. We've paid for MMI units for too long. Screw that. Let's open source a solution.

Requirements:
Hardware: 1x ODB -> enet cable (and optional USB A/C -> ethernet adapter if you need it)
^ this may also be possible with a wireless ODB adapter too, I've never tried.
1 Flash Drive
SSH Access to your Head Unit - see @a90.faz's thread: SSH Access Guide - Supra NBTEvo Headunit

Building:
This leverages QNX Momentics / 6.5.0 from Archive.org. Please only build this project on a virtual machine. I can't guarantee the safety of things hosted on archive.org. It's not available from Blackberry for download anymore. I can release builds for testing if absolutely needed. These should be treated as testing only, not full featured, and is not ready to use in motion.
- Create a project, name it whatever you want
- Add the files in the GitHub Repository to the project folder
- Right click on the folder in Momentics
- Build

You should have 2 files in there, nbt-aad (NBT Android Auto Daemon - this runs AA) screen_test (this is a demo project to ensure screen rendering works properly).

Copy nbt-aad to a flash drive, and plug it into your car.

Deploying:
Connect your ODB -> ENet cable to your laptop, grab your SSH Client of choice and run the following commands

ssh [email protected]
# pwd is ts&SK412
on -f /net/hu-omap/ /bin/sh
cd /tmp/
ls /mnt/
cp /mnt/yourflashdrivenamehere/nbt-aad ./
./nbt-aad

After executing ./nbt-aad, the Android Auto Daemon will be running. This is not how the final state will work. It will be launched via the iDrive menu, similar to Apple Car Play if possible. this process has not been built yet, and is only workshopped.

Proof or GTFO:
Initial Build -

Milestone 2 w/ Touch Controls -

Contributions:
If you're looking for a way to help, I'm currently looking for a free way to enable SSH for folks. The goal is for this to be 100% open source. It's currently possible to generate a code with HUTool, and have it enabled with FeatureInstaller, but that sucks and costs people money. A standalone python script to open it would be immensely better. But... it seems to require a L5 security key that may be a private key.

This works on my head unit and that doesn't mean it'll work on yours. I'm also looking for testers to prove portability across multiple istep versions. If you have SSH open and are feeling like you want to donate some time, please let me know. I can send you a pre-compiled binary to try.

Disclaimer:
I'm not responsible for what you do with SSH access. If you accidentally delete something, break something, or brick something, I can't help you. You'll need to bring it to Toyota and see if they can reimage it, or order you a new head unit. I haven't broken anything, I've crashed the Head Unit, and it seems fairly resilient, and will load from a known good config if it crashes too many times, but that's just my experience.

Firmware:
If anyone is interested, I can provide binaries, but please only reach out if you're 1000000% serious about helping the development process in some way.

Questions:
I'm happy to answer anything, or try to. Replies will be human written, not robot written. Happy to share info about the development setup, or anything you might want to know!

Sponsored