Related
Is there anything out there that can plug up to the car and sync bluetooth with phone to show error codes and what non like a scanner car mechanics have? It would be nice because I work on cars a lot and it would prolly save money because I could just quickly pop up my phone and plug it up on the go to see what is wrong with the car. If anyone could please link me if possible, thx X)
Android currently does not offer USB host support, it would not be able to interface directly with a USB ODB-II adapter. Also, its bluetooth stack only offers audio profiles (headset, hands-free, a2dp, avrcp), although there are some third-party options to change this. However, there is still a lot of work that would be needed to: 1) implement a bluetooth serial protocol to read the raw data from the ODB-II; and, 2) have custom software to allow you to read and display the ODB-II information read from the adapter.
this should be in the app forum
though I do have interest in this as well as OBDI
keep an eye out for this : http://code.google.com/p/android-bluetooth/
I'm sure there are OBD2 bluetooth adapters around
The device *does* have a serial RS232 port you know....
http://www.instructables.com/id/Android_G1_Serial_Cable/
** you can leave out the USB parts since that is intended to link up with your computer's USB port.
Along with this, you need the program to read/write the OBD2 commands to the car's computer. FYI OBD2 protocol is very simple, so it wouldn't be much work to implement.
The only issue with doing this is that there is really no need. You would have to carry around the right kind of plug to fit the car anyways, so you might as well pick up a cheap OBD2 scanner device.
I doubt there are any cars out there with ECUs that have any bluetooth capabilities... Audio systems (where the bluetooth is on cars) will most likely be separate from anything ECU related.... It may be possible, but I doubt it at this point... unless it is some new fancy mercedes/bmw kinda thing.
You completely missed the point.
The bluetooth interface won't be in the car, it will be a device connected to the OBD port.
glock30 said:
I doubt there are any cars out there with ECUs that have any bluetooth capabilities... Audio systems (where the bluetooth is on cars) will most likely be separate from anything ECU related.... It may be possible, but I doubt it at this point... unless it is some new fancy mercedes/bmw kinda thing.
Click to expand...
Click to collapse
Ahh... guess that makes more sence... looks like I read it wrong.
would be pretty bad ass .. and while having access to the obd2 port u can even implement stuff to monitor o2 readings and all sorts of other stuff
Im already barking up the same tree on some of my car forums. I see the future being ruled by android phones that are capable of giving you full racing telemetry, at first by log to your computer and eventually in real time info like a set of gauges. I would ideally want to use the OBD2 for the majority of the data logging while overlaying G forces from my phone.
http://legacygt.com/forums/showthread.php?t=116910
brandenk said:
Im already barking up the same tree on some of my car forums. I see the future being ruled by android phones that are capable of giving you full racing telemetry, at first by log to your computer and eventually in real time info like a set of gauges. I would ideally want to use the OBD2 for the majority of the data logging while overlaying G forces from my phone.
http://legacygt.com/forums/showthread.php?t=116910
Click to expand...
Click to collapse
LGT!
Used to be an active member, haven't been around since I wrecked my Legacy GT Ltd though.
lbcoder said:
The device *does* have a serial RS232 port you know....
http://www.instructables.com/id/Android_G1_Serial_Cable/
** you can leave out the USB parts since that is intended to link up with your computer's USB port.
Along with this, you need the program to read/write the OBD2 commands to the car's computer. FYI OBD2 protocol is very simple, so it wouldn't be much work to implement.
The only issue with doing this is that there is really no need. You would have to carry around the right kind of plug to fit the car anyways, so you might as well pick up a cheap OBD2 scanner device.
Click to expand...
Click to collapse
That's awesome! I wouldn't care if it's a serial cable or some bluetooth, just having the ability to not drag my laptop into the car would be useful (I guess my fault for buying a heavy 17")
I have seen a bluetooth dongle type thing that plugs into the port on the car and it is kinda huge, but idc what the size of the bluetooth adapter is. It is supposed to work for window based systems and also some smart phones. So it may be possible to write something to sync the obd2 bluetooth thing to the phone? And from there decode the data it recieves and place it out to english on the phone?
Any chance this would work?
ELM327 Bluetooth OBD-II Wireless Transceiver Dongle
Manufacturer's product description:
bluetooth ELM327 is the newly developed wireless scan tool. It supports all OBD-II protocols
• Works with all OBD-II compliant vehicles
• Wireless (Bluetooth)
• Software included for Palm, PDA
• Software included for Windows PC
• Software included for Windows Smartphone
• Supports ISO 9141, KWP2000
• Supports SAE J1850
• Supports CAN bus
Functions:
• Read diagnostic trouble codes, both generic and manufacturer-specific, and display their meaning (over 3000 generic code definitions in the database).
• Clear trouble codes and turn off the MIL ("Check Engine" light)
• Display current sensor data, including:
• Engine RPM
• Calculated Load Value
• Coolant Temperature
• Fuel System Status
• Vehicle Speed
• Short Term Fuel Trim
• Long Term Fuel Trim
• Intake Manifold Pressure
• Timing Advance
• Intake Air Temperature
• Air Flow Rate
• Absolute Throttle Position
• Oxygen sensor voltages/associated short term fuel trims
• Fuel System status
• Fuel Pressure
• Many others...
http://www.dealextreme.com/details.dx/sku.16921
Yes i guess, if it is possible to sync the phone with this and have someone write a program, it may be possible to get it working like a normal scanner itself?
Open-source linux based OBD GPS Logger
-http://icculus.org/obdgpslogger/
Maybe an easy port? (I am not a coder)
LinkinX said:
Open-source linux based OBD GPS Logger
-http://icculus.org/obdgpslogger/
Maybe an easy port? (I am not a coder)
Click to expand...
Click to collapse
That's pretty nice! Looks like most of the code is written in C and some in C++. It wouldn't be a direct port since Android apps are written in Java, but it might be worth checking out.
I would LOVE to have something like this on my phone!!
** EDIT **
The code is simple, I have no doubt this would be easy enough to port. The problem (at least for me) is that the interface cable is pretty expensive. I searched a little bit and it seems like it would cost over $100! Ouch!!
I have written an obd-II logger in the past using an ELM interface...
I do however think that a laptop is more easy to use for readings and logging. The android screen is just a bit too small to really make a useful app.
And obd-II kinda sucks for real use ( sampling rate etc )... purely diagnostics can be handy though.
Ive always used software like crome and ectune to map my cars ( purely honda ).. Something like that would be great to have in a pocket device to turn on/off launchcontrol etc
rogro82 said:
I do however think that a laptop is more easy to use for readings and logging. The android screen is just a bit too small to really make a useful app.
Click to expand...
Click to collapse
I see where you're coming from. However, there are ways to work around the screen real estate issue. I still think this would be a great app! Since you have experience in this area, can you recommend a place to pick up an ELM/USB interface at a reasonable price?
ximonx said:
keep an eye out for this : http://code.google.com/p/android-bluetooth/
I'm sure there are OBD2 bluetooth adapters around
Click to expand...
Click to collapse
http://androidcommunity.com/htc-hero-bluetooth-profiles-detailed-20090724/
Has anybody found out any information where we could maybe flash existing touchscreen headunits to be able to interact with Android Auto?
I have a Pioneer double din touchscreen headunit that has a USB port for data connections. Rather than spending $1,400 on another headunit with useless applications on it just so that I can never use them because I'll be using Android Auto is complete overkill. I'd much rather stick with what I have and flash a firmware onto it so that I can just plug my phone in and have the same user experience and integration that the new headunits are having.
I wish Android Auto development was open and accessible just like everything else Android.
Hey Guys
First of all: I realize that this is a rather long text, so I appreciate the effort of everyone who is going to read it!
Also, I asked a questions about 2 weeks ago, which was related to this topic, but was very specific about android wear (which I gave up on since then!).
So, actual post:
I want to build, or already am building an informational system for my motorcycle.
As the result of my work, I imagine a display (about 7 inches) in the dash of my motorcycle. It shall display information from my Smartphone (for example notifications about incoming calls etc.) as well as giving me the possibility to control the music on the smartphone (Android 5.1).
Also, I want to display further information, like speed, average speed, altitude etc. (hope you got the idea, basically just an advanced trip computer).
I started developing something, but ran into issues. I will explain my two concepts or ideas I had so far and explain, what the issues were I ran into. I then hope, that somebody here has a solution for my problem (which includes recommending hard- and software).
Firstly about my skills: I am experienced in programming "low level hardware", like Atmel's AVR Series (in plain old C) and developing the associated hardware for it. Also making custom pcb's at home isn't a problem for me, as long it doesn't come to some fancy BGA or SMD packages
On the programming side I am experienced the most in Java (and Android, which is basically Java of course). I know also C# and the .NET framework.
But I am willing to learn something new
The two ideas I had so far differed on the way how I wanted to let the raspberry pi (which I wanted to place in the cockpit) communicate with the smartphone.
In both concepts, I planned to have a raspberry pi with attached display in the cockpit on which I wanted to run a JavaFX application (already started programing). This application would then communicate with the smartphone over:
Idea 1: Java serialization:
I wanted to communicate over command objects. So for example I'd have an object for asking the altitude from the smartphone.
I'd then serialize this command object on the pi's side and deserialize on the smartphone. This isn't a problem, because there's java on either side (already got that piece working).
The smartphone would, after receiving and deserializing the object, get the actual altitude from the GPS sensor, pack the result in an answer-object, serialize it and send it back to the pi.
The issues I ran into were the following:
-Java Bluetooth library: I wasn't able to find a good, up-to-date, java library for communicate over Bluetooth in java. I then stuck to RXTX Library which did the job, but I always had the feeling of doing something "not so good". In particular I didn't want to just write on a COM-Port (which is emulated from the Bluetooth-module), because I had the feeling that COM-Ports may change after reboots if the OS feels like it, and I didn't want to build something which needed constant "tinkering". Also, writing to COM-Ports in 2015 just feels wrong, but this may be my personal problem
Idea 2: HTTP and Web Sockets
The basic idea was to have a webserver running on the smartphone and offering a REST-like API which I could access from the pi.
I also got this concept working, like so:
By using the NanoHTTPD library (from github) I was able to start a webserver on the android device. When then someone issued a POST-request on, for example, <IP>:<port>/api/music/next, the WebServer would receive this request and switch to the next song.
Actualizing data on the pi which changes often, for example the altitude, would have been achieved by using a WebSocket connection between the Java-App on the pi and the android webserver (which I also got to work).
I figured out that it would be a power consumption problem to let the smartphone offer a wifi hotspot (I don't want to have to connect the smartphone to cables on the motorcycle), so I decided to let the pi start a wifi access point (which isn't a power problem, because the pi is connected to on-board-power of the motorcycle).
However I then realized that the smartphone won't connect to an access point which doesn't offer internet access but only LAN-access.
And even if there was a way to force the smartphone to let it connect anyways, it isn't guaranteed that this will work too on future devices. And: The whole notification-stuff would have been needless, because as long as the smartphone is connected to a "dead-end wifi", it wouldn't receive emails or whatsapp-messages.
Idea 3: Using Bluetooth low energy:
It seems like the new, modern way, to let devices communicate over Bluetooth is to use Bluetooth low energy (BLE). (But I never worked with it before!).
However, there seems to be little to no support on raspberry pi for it, and it seems to be impossible to find a library for java which helps in using BLE. (If anyone knows one, please let me know).
I then thought about replacing the raspberry pi with an android board, because android has support for BLE. But I wasn't able to find a board which is supported from android 5.1+ and offers support for BLE. Even the Odroid-boards don't seem to support android >4.4 and BLE.
Summary:
In general I liked the second and third option much better. It seemed to be the the more versatile, modern way. The first way felt a bit like a hack.
However I found those problems I presented above, and until now, I couldn't think of a way around it.
If anyone here:
1) Solved this problem already
2) Knows a really good, NON-HACKY, community supported, Java (BLE) Bluetooth library
3) Knows a language or framework which would be well suited to solve the problem
4) Has another good idea how to solve it
Please let me know!
I just want to build something sophisticated, (which I could maybe make an open source project out of it) which isn't hacky.
I mean, the problem has to be solvable, look at the Pebble smartwatch. They also solved it without android wear.
I really want to emphasise that this is an open question. I am not limited / fixed on Java, Raspberry pi or anything.
I those have two requirements.
1) I don't want to connect the smartphone to a cable, either for data or for power
2) The solution needs to be something power saving, so no hotspot on the android device
3) Non-hacky, sophisticated solution
Best regards
Me =)
PS: As English isn't my native language, I maybe put some sentences wrong or wasn't able to express something clearly and unambiguous.
Please feel free to ask, I'd be pleased to clear any questions!
Any updates?
Hi!
I know this is an old thread, but I'm struggling with a similar issue - except I want to use it for roadcycling. Did you have any luck with your project?
All the best
Marius
After Google announced almost a full year ago that Android Auto would support phone connections without needing to rely on a USB cable, I have yet to find any news on this.
Is this still happening in the aftermarket HU's? Hoping this doesn't turn into another Android Wear situation where it lacks the attention it needs to make it a market hit.
Hi,
This is called "WIFI Projection", and it's included (hidden) in the last release. No one knows how to enable AND use it. Still in alpha!
I hope current HU with wired AA support can be upgraded to wireless with a simple USB dongle (not a Wifi dongle, but with an AA wireless adapter).
Just to make sure I understood correctly: the option is there in the OS, but it doesn't work on any device as of yet? As if the software support is there, but the hardware support is not?
I'm a bit disappointed that Android Auto wasn't discussed at the I/O keynote... I think there's lots of usability updates required to improve it...
Relevant:
https://arstechnica.com/cars/2017/0...finally-ready-to-talk-about-its-car-os/?amp=1
What gets me: is it really necessary to use a a different name for this? Chromecast comes in audio-only and video forms, Pixel comes in "XL" and "C" forms also, can't they just name it something like "Android Auto Standalone" and call it a day? It serves the same end goal of getting Android into your car's radio/head unit.
Still no news of the phone-based Android Auto and wireless that I can find. That said, if everything will be integrated into the radio to begin with, I'd welcome the lack of tethering. Might even get back to developing Android apps for myself now that I have a use for them, but for my car this time! Hopefully the aftermarket guys will be smart enough to bypass Android for the sound processing though. Would hate for a resource-hogging app to kill my radio!
Hey guys,
I've never had a touchscreen in a vehicle, other than a phone in a mount.
Researching options, and making a list of what I've found so far. Some ideas on how I could use custom systems, and hopefully some guidance from those who've been there, or know of options I've missed in my search engine hunt.
Think I might start with a Raspberry Pi and/or RockPi x86 board in a retail RPi touch enclosure, mounted in a car tablet mount. Going to test OpenDash, OpenAuto, i-Carus, Crankshaft board images.
GitHub - openDsh/dash: Join us on Slack! https://join.slack.com/t/opendsh/shared_invite/zt-la398uly-a6eMH5ttEQhbtE6asVKx4Q
Join us on Slack! https://join.slack.com/t/opendsh/shared_invite/zt-la398uly-a6eMH5ttEQhbtE6asVKx4Q - GitHub - openDsh/dash: Join us on Slack! https://join.slack.com/t/opendsh/shared_invite/zt-la39...
github.com
GitHub - f1xpl/openauto: AndroidAuto headunit emulator
AndroidAuto headunit emulator. Contribute to f1xpl/openauto development by creating an account on GitHub.
github.com
Downloads
i-carus.com
Crankshaft - GNU/Linux for your car with Raspberry Pi and Android Auto
getcrankshaft.com
I currently have no 3D printer for creating to spec board and LCD mount plates.
i-Carus offers a retail double din mounting solution for RPi type boards.
Shop
i-carus.com
They also have a search tool for 7 inch touchscreen fascia plates and wiring harness adapters for various vehicles.
Harnesses and dashboard kits for CarPC mounting
i-carus.com
Another provider for car wiring interface is CarPiHat, but doesn't offer any type of housing.
CarPiHat - Raspberry Pi Car Interface PCB by TJD's Electronic Stuff on Tindie
A PCB to help interface a Raspberry Pi to your car - Power supply, Isolated GPIO, CAN Bus, 12v Outputs
www.tindie.com
CarPiHAT - Car Interface HAT for Raspberry Pi
The TJD CarPiHAT is designed to make interfacing your Raspberry Pi to your car, boat, truck, or any other 12V based system much easier. Whilst shopping for a simple power supply and shutdown solution for his OpenAuto Pro installation, the designer (Sam Taylor-Jones) was unable to find a solution...
thepihut.com
Definitely a project to undertake, and want to use harness adapters and fascia plates so that when I change vehicles, I can just unplug, put factory system back, take my Linux box with me, put old harness & plate on ebay, and get new ones for a different vehicle.
The alternative to a Linux box will be to get a Head Unit from Atoto, Dasaita, Joying, Xtrons, Eonon, or some outfit like Phoenix Automotive. Then put a Hal9K or Malaysk ROM on it if I what longer term updates, and tweaks.
Going that route, probably Android 12 4gb/64gb, minimum. 7-13 inch screens. Some options there that are likely vehicle and ergonomic dependent.
Anyway, going to start with a phone mount for a stylus phone, a figure something out from there.
No purchase decisions made yet on double din mount unit, and open to options or advice.
James C said:
Hey guys,
I've never had a touchscreen in a vehicle, other than a phone in a mount.
Researching options, and making a list of what I've found so far. Some ideas on how I could use custom systems, and hopefully some guidance from those who've been there, or know of options I've missed in my search engine hunt.
Think I might start with a Raspberry Pi and/or RockPi x86 board in a retail RPi touch enclosure, mounted in a car tablet mount. Going to test OpenDash, OpenAuto, i-Carus, Crankshaft board images.
GitHub - openDsh/dash: Join us on Slack! https://join.slack.com/t/opendsh/shared_invite/zt-la398uly-a6eMH5ttEQhbtE6asVKx4Q
Join us on Slack! https://join.slack.com/t/opendsh/shared_invite/zt-la398uly-a6eMH5ttEQhbtE6asVKx4Q - GitHub - openDsh/dash: Join us on Slack! https://join.slack.com/t/opendsh/shared_invite/zt-la39...
github.com
GitHub - f1xpl/openauto: AndroidAuto headunit emulator
AndroidAuto headunit emulator. Contribute to f1xpl/openauto development by creating an account on GitHub.
github.com
Downloads
i-carus.com
Crankshaft - GNU/Linux for your car with Raspberry Pi and Android Auto
getcrankshaft.com
I currently have no 3D printer for creating to spec board and LCD mount plates.
i-Carus offers a retail double din mounting solution for RPi type boards.
Shop
i-carus.com
They also have a search tool for 7 inch touchscreen fascia plates and wiring harness adapters for various vehicles.
Harnesses and dashboard kits for CarPC mounting
i-carus.com
Another provider for car wiring interface is CarPiHat, but doesn't offer any type of housing.
CarPiHat - Raspberry Pi Car Interface PCB by TJD's Electronic Stuff on Tindie
A PCB to help interface a Raspberry Pi to your car - Power supply, Isolated GPIO, CAN Bus, 12v Outputs
www.tindie.com
CarPiHAT - Car Interface HAT for Raspberry Pi
The TJD CarPiHAT is designed to make interfacing your Raspberry Pi to your car, boat, truck, or any other 12V based system much easier. Whilst shopping for a simple power supply and shutdown solution for his OpenAuto Pro installation, the designer (Sam Taylor-Jones) was unable to find a solution...
thepihut.com
Definitely a project to undertake, and want to use harness adapters and fascia plates so that when I change vehicles, I can just unplug, put factory system back, take my Linux box with me, put old harness & plate on ebay, and get new ones for a different vehicle.
The alternative to a Linux box will be to get a Head Unit from Atoto, Dasaita, Joying, Xtrons, Eonon, or some outfit like Phoenix Automotive. Then put a Hal9K or Malaysk ROM on it if I what longer term updates, and tweaks.
Going that route, probably Android 12 4gb/64gb, minimum. 7-13 inch screens. Some options there that are likely vehicle and ergonomic dependent.
Anyway, going to start with a phone mount for a stylus phone, a figure something out from there.
No purchase decisions made yet on double din mount unit, and open to options or advice.
Click to expand...
Click to collapse
None of these are Android Auto. The horrible hacks from hal and Mal are modded roms but not Android auto either.
From my understanding, Android Auto syncs and mirrors information to and from a paired Android phone.
Haven't tested anything yet, and the software links I posted are mostly what I assume to be Raspbian/Debian that boot into a version of those features.
Really not that interested in tinkering stereos, and just want a dedicated and versatile touchscreen device in vehicle.
Was just looking at swing out dash monitor mounts for vehicles. Could use anything with Vesa mount. Probably Fedora/Red Hat with Android X86 rpm install for qemu and dual boot option.
https://www.l-trondirect.com/Havis/C-DMM-120
Will have two modes basically, driving and parked mobile office.
My Linux Touchscreen for vehicles can basically be implemented as an addition to any existing console infotainment system, via a dash swing mount, a floor mount, or seat desk for laptops, tablets, etc.
Question is what Android Auto option is the bottom line for cost, performance, and stability. Also, what AA options are worth spending extra for?
I've seen factory upgrade kits to add Android Auto to older in dash Navigation systems without that feature, starting around $700. Worth it, or better spent on other options?
Just began looking at options from Alpine, JVC, etc. I guess the lowest cost, stable performance option would be a Bluetooth connection to a simple audio receiver offered by real Trademarked Brands in the market place, $100.
Some Android Auto options from the name brands, ranging in cost from $250-$1000+.
Backup camera and DVR for safety and insurance purposes is smart.
Are there any comparisons between the name brand AA options and the Chinese factory AA options?
So far, I've seen some Chinese AA HU brands ranging in price from $50-$550, not including units for specific vehicle trims to accommodate extra large screens. Haven't seen any name brand kit options for specific vehicle trims so far.
Actually want to revise earlier statement, that lowest cost, stable in car Android option is a $100 Name brand Bluetooth Dash unit.
Lowest cost, stable, performance, phone-only option, keeping factory equipment would be a Bluetooth Aux/Cassette/Radio adapter, a dash/vent clip magnetic qi charger, and a case/clamp/sticker with metal plate.
Qi adapter for phones without. That, and adding a Backup cam DVR Rearview mirror unit.
This for old models, and newer trims without navigation or backup camera.
While reviewing this I saw a 7" Binize w/AA for $52, and a dash kit for $12. Cost is about on par with phone only, no cables to plugin option. The Binize comes with a backup cam according to product picture. So, some savings there. Performance comparison is likely another story.
Think I'm going with a Havis monitor mount for an older Ford with a standard double din radio without weird custom fascia plates I would either need to cut into, remake, or order kit for.
May replace factory radio with a 7 inch Chinese unit that has Android Auto features, and has a compatible Rockchip processor for running one of the roms available here.
The AA double din unit will be setting behind the Havis Vesa 75 swing monitor mount, which I'll attach a 13.3 inch Vesa mount Touchscreen monitor, connected to an old Lenovo ThinkCenter probably installed under a seat or somewhere similar. A Lenovo USFF with enough ram to run Windows subsystem for Android, and WSLinux for starters. Will run on rechargable battery bank, and will have to figure out USB gps, glonass antennas for PC. Will begin there, and move to Linux once I figure out hardware that works for everything I need. OpenDash for AA Linux/Windows purposes. Everything else I'm working on is basically a separate mobile office project.
Will either use Aux or Bluetooth to interface PC system into car audio system. Factory or Aftermarket stereo system will be used as needed as 13" touchscreen will need to be unlocked and "opened" to access manual or touch controls. Probably set it and forget it, mostly while tinkering with PC option.
Found this adapter for name brand aftermarket options, Maestro. https://www.idatalinkmaestro.com/en/compatible-products/all
Rather than go for a Chinese Android Head Unit, I'll just stick to factory or name brands supported by Maestro.
Will just mirror any apps I want to use from phone, if unsupported by Android Auto. Say a Lottery.apk for the state lotto. I find driving a good opportunity to sense lucky numbers and make picks, personally.
Will see how that works out before investigating further options. Namely, the expensive Chinese Android Head Units, and pole/dash mounts for tablet docks used in police vehicles.
For inexpensive head units, Atoto seems a good choice. F7 Linux based, S8 Android 10 based.
Lots of various configurations of each, from 7"-10" displays, single or double din enclosures.
Haven't decided on F7 or S8 yet, but I do know I want a single din with floating display that will work in a tractor or older vehicle without the built-in infotainment and navigation features newer vehicles offer.
Still going namebrand with maestro for newer vehicles.
Laptop and tablet dock mounts should work with either via Aux or Bluetooth.
Might do away with phone altogether, and try a watch phone instead, since I'll be packing along both a dash "tablet" and a 12" PC.
New models of watch phones are kind of on standby I hear, due to their chip supply chain drying up since COVID.
In any case, will try and Android 10+ watch phone with a head unit that supports wireless Android Auto.
Found this with watch phone firmware. https://fullandroidwatch.org/
Think my final solution for a vehicle Linux box, will be a single din head unit with an HDMI input attached to a Raspberry Pi or similar SBC. Stowing the board into the empty slot on a Metra dash kit. Head unit also supports Android Auto and Screen Mirroring. Will likely use a wireless TV keyboard/gamepad to tinker with Linux SBC for certain use cases. Maybe just Velcro Linux SBC and accessories in Metra slot, for easy removal to take indoors as required.
Umm.. Will figure it out, and test the Pi images posted earlier.
American made vehicles are better supported by idatalink Maestro adapters.
iDatalink Maestro
www.idatalinkmaestro.com
The Chinese Factory brands better support Asian designs with their own wiring harness adapters to retain all vehicle sensor features.
There are exceptions, and Metra is a resource to investigate.
Going Ford, Lincoln, Mazda. Alpine, JVC or whichever Chinese factory brand offers a suitable dash kit and harness adapter.. Long story short.