Raspberry pi apple carplay

Wireless Apple CarPlay on the Raspberry Pi 3/4 with a Dongle

I recently picked up a Carlinkit Wireless Apple CarPlay Dongle from AliExpress and wanted to see if I could get it to work with the Raspberry Pi 3. After some tinkering, I found a way of getting it to work by using a Raspberry Pi Android image and the application supplied with the dongle. In this post, we will go over the process of installing an android image to the Raspberry Pi, downloading the application, the settings in the application and the issues I found with the device and what I did to fix them. At the end of the article, I will sum up if it is even worth even purchasing one of these dongles.

#Android for the Raspberry Pi The Raspberry Pi has many distros that range from Raspberry Pi OS to Net BSD, Android has been ported many times to the Pi but most of the versions ported have been completely unstable or even cost money like Emerita OS. The version we are using today is the best one I could find after searching, This is KonstaKANG LineageOS 16.0 (Android 9). This image is available for both the Raspberry Pi 3 and 4 which is available to download here (Raspberry Pi 3 Version, Raspberry Pi 4 Version). Note both these versions are still not 100% stable and if you are experiencing any crashes or issues it might be worth trying other Android images for the Pi.

Once you have downloaded the image for your Raspberry Pi you will need to grab balenaEtcher, this program is used to write images to an SD Card. To write the image you will need to open balenaEtcher and select the file you want to flash, then insert the SD card into your computer, select the device and start the flash. Once the flash is complete you can remove the SD card and insert it into the Raspberry Pi. You are now ready to power up the device and go through the setup process for the operating system, this involves setting the time, region and a few other items. After this, you should be at the home screen and ready to proceed onto the next step.

#Installing the Right App From my research I have found there to be two different types of dongles that are used for CarPlay, these two dongles run different apps. The Carlinkit dongle I have is the first type which uses the AutoKit application and the other type uses the ZBox Application. I have found the download for the AutoKit application here (http://www.carlinkit.com/autokit) but I have been unable to find the ZBox application online (If you have a copy feel free to forward it to me to host). Installing each app is quite simple as all you need to do is direct your browser to the links above and the APK will start downloading, once the download is complete you will need to go into settings and enable installing untrusted packages. Once that is done you can open the APK and proceed with installing the application.

AutoLink App Main Screen AutoLink App Main Screen

#Customizable Settings With the AutoKit application, there are many settings to configure, some of these settings are vital for having the app function correctly and some are cosmetic. The setting you may need to play around with is the working mode setting, this setting changes the way the app communicates with the CarPlay dongle. The speed mode is the fastest mode but does have issues with some devices like the Raspberry Pi where it stutters due to the low CPU performance, fluency mode works on some other devices but threw an error screen on the Pi, compatible mode is the slowest mode but it works correctly on the Pi. Another option of note is the ability to change the logo of the exit button in CarPlay, there is a number of popular brands and other icons to choose from.

Working Mode Options Working Mode Options

Logo Option Screen Logo Option Screen

#Issues and Fixes Over the period of testing out the device I found many problems caused by the application and operating system, these ranged from choppy music to no display at all. The most common problem I got was the overall choppiness with the application, this would be either choppy music, slowness in the user interface, device crashes or even weird messages like the one pictured below. The fix I found for this issue was to set the speed of the device to compatibility, which fixed all of the above issues except for slowness in the user interface. I couldn’t find any way of having the device run at a smooth speed and had to deal with the slowness. Another issue I had with the Android image not working on my HDMI to DVI converter and this was due to the video driver with KonstaKANG Android Images not supporting some display devices. The way I solved this was by connecting it to another display and enabling the SwiftShader software renderer by opening a terminal and entering the following command.

#Summary Overall I got the CarPlay dongle working with the Raspberry Pi but I found the experience to not be acceptable for use on a day to day basis. The Raspberry Pi Android image ran well but the application for the dongle was not stable and even after the fixes caused the device to crash at times. I would not recommend buying this device and instead put the money towards a car stereo or device that has CarPlay inbuilt.

Источник

Raspberry pi apple carplay

Hi guys!!
Just an idea Apple carplay is available for aftermarket.
It means Carplay could be available on every hardware.

It could be possible use raspberry for that??

Thanx in advance.

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

Well , unless Linux Carplay software drops from the sky , the
disucussion is moot.

Re: Apple Carplay

ghans wrote: Well , unless Linux Carplay software drops from the sky , the
disucussion is moot.

Re: Apple Carplay

CarPlay is basically running on the iPhone and the client ie in-car infotainment system is tethered.

The issue here is that the Client Software is not » open-source» and to be honet most of what CarPlay does can already be achieved though not in a single software package. If you could reverse engineer the Client App I am sure it may be useful, but would not see it as a high priority to any Linux Guru’s..

Re: Apple Carplay

Re: Apple Carplay

Obviously a gap in the market , perhaps the VMLite guys will
fill it ?

Re: Apple Carplay

ghans wrote: Obviously a gap in the market , perhaps the VMLite guys will
fill it ?

Re: Apple Carplay

VMLite released the first working Airplay Mirroring reciever for the Pi , so i wonder whether they are interested
in a Carplay reciever ? You might want to contact them.

Re: Apple Carplay

ghans wrote: VMLite released the first working Airplay Mirroring reciever for the Pi , so i wonder whether they are interested
in a Carplay reciever ? You might want to contact them.

Re: Apple Carplay

ghans wrote: VMLite released the first working Airplay Mirroring reciever for the Pi , so i wonder whether they are interested
in a Carplay reciever ? You might want to contact them.

Re: Apple Carplay

Re: Apple Carplay

Hi guys!!
Just an idea Apple carplay is available for aftermarket.
It means Carplay could be available on every hardware.

It could be possible use raspberry for that??

Thanx in advance.

This should be feasible & I’m seriously looking into it. CarPlay isn’t Apple software, but an API that implementers (primarily car makers & aftermarket in car entertainment makers) address in code on whatever underlying platform they use. All OEM implementations, & at least most aftermarket, support Android Auto on the same hardware & OS as their CarPlay. To the best of my knowledge ARM64 is the most common hardware platform.

I’m very much interested in being part of an open source effort towards CarPlay on Raspberry Pi, & would favour Swift as the language.

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

It is my understanding that in order for Carplay to work on Raspberry Pi, one needs an apple Accessory Authentication chip that raspberry pi needs to read and tell the IOS on the apple device about the chip that it read. From there on it is pretty straight forward. One needs to write code that communicates with the IOS. The protocol standard is defined in the MFi accessories guide available to all registered MFi entities. This code can be in any programming language and any platform of your choice.

The registration to MFi is available to any registered company that wishes to design and test the design of an apple accessory including carplay. The registration is free but you need a registered company to do the registration. Once you are registered in the MFi program you can also order very limited quantities of authentication chips from apple to test your design. You cannot manufacture these devices with this registration only design and test for a third party.

Hope this helps.

Re: Apple Carplay

Re: Apple Carplay

The authentication will indeed be a tricky one to tackle. This project shows how another device has done the mfi authentication, which was then hijacked for communication over serial. https://github.com/ndusart/freedelity-lightning Implementation of the mentioned protocols (which presumably are also documented for mfi developers) should be a breeze from this point on.

Now that software authentication is possible, i’m sure it is still no easy task, but at least became much more promising to spoof. Maybe a construction where the Pi forewards authentication traffic to an actual authentic mfi carplay device somewhere on the internet, and then again hijacks the line, much like the usb hardware variant.

Can anyone point us to more documentation on wireless mfi authentication?

Источник

Raspberry pi apple carplay

Hi guys!!
Just an idea Apple carplay is available for aftermarket.
It means Carplay could be available on every hardware.

It could be possible use raspberry for that??

Thanx in advance.

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

Well , unless Linux Carplay software drops from the sky , the
disucussion is moot.

Re: Apple Carplay

ghans wrote: Well , unless Linux Carplay software drops from the sky , the
disucussion is moot.

Re: Apple Carplay

CarPlay is basically running on the iPhone and the client ie in-car infotainment system is tethered.

The issue here is that the Client Software is not » open-source» and to be honet most of what CarPlay does can already be achieved though not in a single software package. If you could reverse engineer the Client App I am sure it may be useful, but would not see it as a high priority to any Linux Guru’s..

Re: Apple Carplay

Re: Apple Carplay

Obviously a gap in the market , perhaps the VMLite guys will
fill it ?

Re: Apple Carplay

ghans wrote: Obviously a gap in the market , perhaps the VMLite guys will
fill it ?

Re: Apple Carplay

VMLite released the first working Airplay Mirroring reciever for the Pi , so i wonder whether they are interested
in a Carplay reciever ? You might want to contact them.

Re: Apple Carplay

ghans wrote: VMLite released the first working Airplay Mirroring reciever for the Pi , so i wonder whether they are interested
in a Carplay reciever ? You might want to contact them.

Re: Apple Carplay

ghans wrote: VMLite released the first working Airplay Mirroring reciever for the Pi , so i wonder whether they are interested
in a Carplay reciever ? You might want to contact them.

Re: Apple Carplay

Re: Apple Carplay

Hi guys!!
Just an idea Apple carplay is available for aftermarket.
It means Carplay could be available on every hardware.

It could be possible use raspberry for that??

Thanx in advance.

This should be feasible & I’m seriously looking into it. CarPlay isn’t Apple software, but an API that implementers (primarily car makers & aftermarket in car entertainment makers) address in code on whatever underlying platform they use. All OEM implementations, & at least most aftermarket, support Android Auto on the same hardware & OS as their CarPlay. To the best of my knowledge ARM64 is the most common hardware platform.

I’m very much interested in being part of an open source effort towards CarPlay on Raspberry Pi, & would favour Swift as the language.

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

Re: Apple Carplay

It is my understanding that in order for Carplay to work on Raspberry Pi, one needs an apple Accessory Authentication chip that raspberry pi needs to read and tell the IOS on the apple device about the chip that it read. From there on it is pretty straight forward. One needs to write code that communicates with the IOS. The protocol standard is defined in the MFi accessories guide available to all registered MFi entities. This code can be in any programming language and any platform of your choice.

The registration to MFi is available to any registered company that wishes to design and test the design of an apple accessory including carplay. The registration is free but you need a registered company to do the registration. Once you are registered in the MFi program you can also order very limited quantities of authentication chips from apple to test your design. You cannot manufacture these devices with this registration only design and test for a third party.

Hope this helps.

Re: Apple Carplay

Re: Apple Carplay

The authentication will indeed be a tricky one to tackle. This project shows how another device has done the mfi authentication, which was then hijacked for communication over serial. https://github.com/ndusart/freedelity-lightning Implementation of the mentioned protocols (which presumably are also documented for mfi developers) should be a breeze from this point on.

Now that software authentication is possible, i’m sure it is still no easy task, but at least became much more promising to spoof. Maybe a construction where the Pi forewards authentication traffic to an actual authentic mfi carplay device somewhere on the internet, and then again hijacks the line, much like the usb hardware variant.

Can anyone point us to more documentation on wireless mfi authentication?

Источник