How do I update my CPC200-Autokit

[BlueWave]

Try to update firmware of your dongle to the latest version.

[GuyCramer]

Hi, I made a fresh install of oap 16 but when I load the carplay plugin, it opens and immediately closes.

Someone can help me?

I don't know how to fix this

My setup:
a. What is the version of your RPI? - RPI4B
b. Power supply details - Official RPI charger
c. Model of external sound card - Sabrent Sound Card
d. Do you have microphone input? - Yes
e. Details of your Bluetooth dongle. - Sabrent 4 Port Portable USB 3.0 Hub
f. Touchscreen model - Official 7inch RPI display


—>
I have the same problem. When I connect mine IPhone it looks like it’s rebooting. iPhone charges en stops, screen is going black and back to the menu. (No reboot)


when I connect it to a android device it works also the CarPlay.
I have this device:
https://www.amazon.nl/dp/B08C9YH6B7/ref=...E_SCE_dp_1

could it be a power problem?
version of the device:2021.05.06.2039

have plugged the dongel on a external powered USB Hub. Now it’s working

[3063DPrinting]

I have tried several times to get in contact with the supplier of the dongle and they have been no help to provide any update support. All of the videos I have seen show the update needing to be done though an android device. I do not own an android device. Does anyone have a method of updating these without an android device. I tried the posed update file in this thread, but I had no success. At this point it almost feels impossible to run Car Play.

[BlueWave]

I have tried several times to get in contact with the supplier of the dongle and they have been no help to provide any update support. All of the videos I have seen show the update needing to be done though an android device. I do not own an android device. Does anyone have a method of updating these without an android device. I tried the posed update file in this thread, but I had no success. At this point it almost feels impossible to run Car Play.

The easiest way if you do not have any Android tablet is use VirtualBox with Android x86.

https://www.virtualbox.org/
https://www.android-x86.org/documentatio...albox.html

[Randy2576]

[/quote]

The easiest way if you do not have any Android tablet is use VirtualBox with Android x86.

https://www.virtualbox.org/
https://www.android-x86.org/documentatio...albox.html
[/quote]

I am trying to do this and have installed the latest version of Virtualbox with the latest version of Android-x86.  This is running a simulation of an android tablet on my windows 10 machine without a problem.  I also installed the updates and extensions without a hitch.  Next I downloaded the Autokit APK and installed it on the virtual tablet.  Again, that went smoothly.  Once I configured USB as input, I started up Autokit which then instructed me to insert the USB Carplay dongle.  I plugged in the dongle, but this is where the problems begin.  The dongle isn't recognized by neither windows nor virtualbox.  When I plug it in, I hear the system sound for a device being plugged in, then nothing for about 15-20 seconds, then the sound of the device being rejected.  When I use control panel to check the error message, it says  "unable to get descriptor or descriptor too short".  Doing a google search on this, it basically means the computer isn't getting basic information from the dongle, so it doesn't know what to do with it.

So, if you have gotten Virtualbox set up with Android and a working version of Autokit, and have gotten the dongle recognized, I'd like to know how you did it.  At this point, I have spent several hours trying to get this to work and have gotten close, but not quite there.  You say using Virtualbox is the easiest way, so I have to assume you have done this.  Please let me know what steps I must be missing to get this to work.

Thanks

[Randy2576]

Anyone?

[GSPW]

I doubt it's gonna help but when I have similar issues while running Windows images on Linux systems it's usually down to missing/faulty drivers.

[Randy2576]

From everything I've learned so far, it's down to three things.

One, the dongle is configured for linux, specifically Android Auto. Since it's meant to interface with AA, trying to plug it into a Windows USB port will cause Windows to not recognize it.

Two, VirtualBox and Android OS have a documented history of USB interface issues - gotta look into that a bit more.

Three, the actual dongle may be defective.

My hope is that I can find a step by step installation of VirtualBox running Android on an windows machine with properly configured USB support. If I can find that, a Carplay dongle in good working order should be recognized by VirtualBox. Then if my USB Carplay adapter is still not being recognized, I can pretty much determine that the dongle is at fault. The drivers don't come into play until the software recognizes that hardware is being plugged into the USB port. Baby steps.

[BlueWave]

The dongle will connect and disconnect from time to time (in period of 10-20 seconds). That is normal behavior. Once it is detected by the app (Autokit) it will keep the dongle connected. Try to launch Autokit app on your emulator and attach the dongle to VirtualBox several times.

[Randy2576]

Got VirtualBox and Autokit installed and running. Autokit opens with a page asking to connect the dongle. No matter how many times I plug it in, wait and repeat, the dongle isn't getting detected.

I did make some progress though. One experiment involved flashing the Pi with the latest version of the KonstaKang OS. Once that was done, I downloaded the Autokit.asp and installed it - all on the Pi. It installed fine, and to my surprise, this time Autokit discovered the dongle and my phone. I was able to open Carplay, do screen mirroring, and thought I was getting close to what I wanted......but, I still wanted OAP in case I ever got an android phone, and because of several features OAP offers.

So I figured lets install OAP on the KonstaKang build and see what happens. Took the SD card out of the Pi, opened Balena on my desktop and flashed OAP to the SD card. After flashing successfully, I swapped the SD to the Pi and booted up. Took a little while, but it booted to OAP. I was cautiously optimistic.

Turns out that not only did OAP flash over, but it also brought along the Raspi desptop and seemingly wiped out KonstaKang and the Autokit asp. Back to square one as there was no Autokit and no way to get into the settings required for mirroring, etc. I was hoping that hooking the dongle to the Autokit software and enabling mirroring would flash the dongle, but that wasn't so. When I now pressed onto Mirroring in the OAP menu, it blinked the screen and did nothing more.

Got CarPlay to work by itself on a Raspberry Pi, but not with OpenAutoPro yet.

I should have asked this much earlier, but has anyone, and I mean anyone been able to configure CarPlay with OpenAuto Pro ON A Raspberry Pi with working Mirror mode? Not on a compatible Android head unit, but on a Raspberry Pi?

I feel like there's an answer right around the corner and I'm getting close......