Audio works great, but the microphone is only listening after "hey siri". Even to confirm a message it stops listening. On phone calls the mic is not listening. I had a mic plugged into the USB, but I realized its not listening through it when i unplugged it and got the same behavior. I know some of the newer dongles have a mic, and/or it uses the phone's mic.

v3.0.1
Raspberry pi 4 on Bullseye
Carlink model: Model CPC200-CCPA

Why do we need a calinkit? Can we not plug an iPhone directly into the pi? If not, why not? And can a calinkit not be reverse engineered so the pi can do it?

Thanks

First of all, Huge thanks for your great effort.
WHen I tried to run setup-pi.sh I'm getting this following error. chmod: cannot access '/home/pi/Desktop/Carplay.AppImage': No such file or directory

Can you please sort this one?

Many thanks!

Could you have a look at this and see if you can make it so you don’t need the adapter
https://redpark.com/developer-tools/

While running the app on a touch screen display, it registers a duplicate touch entry while using the on-screen keyboard buttons on the app. Example: If I press ‘ae’, the text box shows ‘aaee’.
Not sure if it is due to hardware incompatibility, but it does not happen when I use the matchbox on-screen keyboard in raspberry pi os outside the app or a usb keyboard inside the app. I followed the installation procedure in the readme. I am using the 2gb Raspberry pi 4 with the waveshare 7.9 inch touchscreen display.

Same JavaScript error as this closed one #2

Using the latest source codes to build and run. Logs in the terminal after close the error popup:

> [email protected] start-electron
> export ELECTRON_START_URL=http://localhost:3000 && electron . --no-sandbox

/Users/xiaobu/Library/Application Support/ReactCarplay
2023-07-21 19:12:17.650 Electron[23376:286630] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
spawning carplay {
  dpi: 240,
  nightMode: 0,
  hand: 0,
  boxName: 'nodePlay',
  width: 800,
  height: 480,
  fps: 30
}
directory found
[23390:0721/191225.298061:ERROR:system_services.cc(34)] SetApplicationIsDaemon: Error Domain=NSOSStatusErrorDomain Code=-50 "paramErr: error in user parameter list" (-50)
WebContents #1 called ipcRenderer.sendSync() with 'fpsReq' channel without listeners.

The app window shows LOADING like this a few seconds after the last log:

Thanks for your awesome work and sharing!

It would be great to have a crowd-sourced list of all the adapter models that are compatible with this program. I purchased a Carlinkit CPC200-CP2A that is not compatible and figured it would be good for the community to have a centralized list of different adapters that have been confirmed to work to avoid this issue for other users

Running latest 64bit Raspberry OS, built my own AppImage for that arch.
Everything seems to be fine apart from the audio. Playing audio via carplay sounds like some monster moan. Very slow low frequencies.

Do you have any suggestion where to start the debugging? Which lib is responsible for this?

Is this the codebase for the https://www.npmjs.com/package/react-js-carplay.

I'm thinking specifically for a use case for a Tesla, which doesn't have a screen input but it does have a browser.

I know I need to serve up an HTTP page that connects to the websocket created by the app but im not entirely sure what to do with the websocket once connected. I'm guessing I need to run this react app somehow.

I know another option is a browser based VNC client but that's a performance hit.

When running react-carplay with the following command: sudo /home/pi/Desktop/Carplay.AppImage --no-sandbox the app will start but does not start the carplay stream.

Log output

spawning carplay {
  dpi: 240,
  nightMode: 0,
  hand: 0,
  boxName: 'nodePlay',
  width: 720,
  height: 480,
  fps: 60
}
directory found
device connected and ready
starting projection
parsing type:  8  for length:  4 <Buffer aa 55 aa 55 04 00 00 00 08 00 00 00 f7 ff ff ff>
parsing 8 <Buffer e8 03 00 00>
Carplay message:  Support Wifi
unkown type:  13  with data::  <Buffer aa 55 aa 55 0d 00 00 00 0d 00 00 00 f2 ff ff ff>
unkown type:  14  with data::  <Buffer aa 55 aa 55 0d 00 00 00 0e 00 00 00 f1 ff ff ff>
unkown type:  18  with data::  <Buffer aa 55 aa 55 1c 00 00 00 12 00 00 00 ed ff ff ff>
parsing type:  8  for length:  4 <Buffer aa 55 aa 55 04 00 00 00 08 00 00 00 f7 ff ff ff>
parsing 8 <Buffer e9 03 00 00>
Carplay message:  undefined
test message i
parsing type:  8  for length:  4 <Buffer aa 55 aa 55 04 00 00 00 08 00 00 00 f7 ff ff ff>
parsing 8 <Buffer 07 00 00 00>
Carplay message:  undefined
test message 
parsing type:  204  for length:  32 <Buffer aa 55 aa 55 20 00 00 00 cc 00 00 00 33 ff ff ff>
parsing 204 <Buffer 32 30 32 31 2e 31 32 2e 32 32 2e 31 36 34 37 43 41 59 00 00 00 00 00 00 00 00 00 00 00 00 00 00>
version number:  2021.12.22.1647CAY
unkown type:  25  with data::  <Buffer aa 55 aa 55 7e 00 00 00 19 00 00 00 e6 ff ff ff>
unkown type:  1  with data::  <Buffer aa 55 aa 55 1c 00 00 00 01 00 00 00 fe ff ff ff>
Socket connected. sending data...
enabling wifi
parsing type:  8  for length:  4 <Buffer aa 55 aa 55 04 00 00 00 08 00 00 00 f7 ff ff ff>
parsing 8 <Buffer f2 03 00 00>
Carplay message:  undefined
test message r
auto connecting
parsing type:  8  for length:  4 <Buffer aa 55 aa 55 04 00 00 00 08 00 00 00 f7 ff ff ff>
parsing 8 <Buffer f2 03 00 00>
Carplay message:  undefined
test message r
non-audio found
unknown type:  11 false false
non-audio found
unknown type:  11 false false
non-audio found
unknown type:  11 false false
parsing type:  2  for length:  4 <Buffer aa 55 aa 55 04 00 00 00 02 00 00 00 fd ff ff ff>
parsing 2 <Buffer 03 00 00 00>
no wifi avail, phone type:  3
data received { status: true }
sending unplugged event
data received { status: false }
parsing type:  4  for length:  0 <Buffer aa 55 aa 55 00 00 00 00 04 00 00 00 fb ff ff ff>

Hello I was wondering if there is a way to run this in the launcher in Opendsh if so how to go about it

Hello, I have a raspberry pi 4 running debian buster 32 bit. (Raspberry PI OS (Legacy)). I need this version because of my 3.5" LCD drivers.

Anyways. I used the github script to install your app. The app begins at startup but throws that error. I am using an official CarlinKit CPC200-Autokit and it is plugged into the top USB 3.0 port on the pi 4. Is there something I am missing here? Maybe a setting I should have changed?

Thanks,
Alex

This is a great project, may I ask how the sound is output from bluetooth?

I followed the latest video you have on youtube but i cant get any further than ./setup-pi.sh It says

failed to create the file /home/pi/Desktop/Carplay.AppImage

Curl: (23) failure writing output to destination

chmod: cannot access ./home/pi/Desktop/Carplay.AppImage: no such file....

I have a fresh copy of raspbian on the sd card.

Was all working fine.

Ran an OS update and now just get an orange screen when Carplay launches. Phone recognises the connection and displays "driving on"

Current OS is Debian GNU/Linux 12 (bookworm)
6.1.0-rpi7-rpi-v8
Raspberry Pi 4 Model B Rev 1.2

Any ideas as was hoping to give this as a Christmas present 🤷‍♂️

running on Raspberry Pi Zero, under Raspbian OS v11 "bullseye" when I execute the AppImage
sudo ./react-carplay-armv7l-0.1.0.AppImage --no-sandbox
it gets
Segmentation fault

from the name i assume this was developed using react? will it be possible to access this through a web browser using the rpi as a hotspot? why am asking? simply tesla car web browser, since this works directly without android then it should be more performant than current rpi workaround with tesla. so can we access this through web browser? that would make this project a huge hit

I've tried running the latest packages including the 3.+ release with a very similar result. The carplay seems to run, as the phone appears connected and the music starts playing - there is output from the Pi. Also, it appears to react to touch as I've managed to hit the pause button somewhere on the screen.

However, the screen remains white, showing the mouse if moved though. Ive tried two different displays, both HDMI - a TV and a 7 inch touch-screen (not RPI official).

I've also tried running the same set up on Buster and Bullseye on RPI 4B 8gb.

This could be related to the issue #22 as in previous releases (1.0.5 and 1.0.6) I was getting the same error.

Below is the terminal output from Bullseye and Buster (as seen at the beginning, the dongle is 1314:1521):

Bullseye:

lexus@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 011: ID 1314:1521 Magic Communication Tec. Auto Box
Bus 001 Device 005: ID 0eef:0005 D-WAV Scientific Co., Ltd WS170120
Bus 001 Device 004: ID 046d:0aaa Logitech, Inc. PRO X
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lexus@raspberrypi:~ $ sudo /home/lexus/React_carplay/ReactCarplay-3.0.1-
armv7l.AppImage --no-sandbox
/root/.config/ReactCarplay
[1382:0205/175810.089991:ERROR:bus.cc(399)] Failed to connect to the bus: Could not
parse server address: Unknown address type (examples of valid types are "tcp" and on
UNIX "unix")
[1382:0205/175810.090474:ERROR:bus.cc(399)] Failed to connect to the bus: Could not
parse server address: Unknown address type (examples of valid types are "tcp" and on
UNIX "unix")
No protocol specified
No protocol specified
No protocol specified
No protocol specified
[1412:0205/175810.347140:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004
(initialize): ANGLE Display::initialize error 12289: Could not open the default X
display.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not
open the default X display.
[1412:0205/175810.347440:ERROR:gl_display.cc(508)] EGL Driver message (Critical)
eglInitialize: Could not open the default X display.
[1412:0205/175810.347571:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with
error EGL_NOT_INITIALIZED, trying next display type
No protocol specified
[1412:0205/175810.348172:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004
(initialize): ANGLE Display::initialize error 12289: Could not open the default X
display.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not
open the default X display.
[1412:0205/175810.348377:ERROR:gl_display.cc(508)] EGL Driver message (Critical)
eglInitialize: Could not open the default X display.
[1412:0205/175810.348520:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with
error EGL_NOT_INITIALIZED
[1412:0205/175810.348654:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[1412:0205/175810.386815:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to
errors during initialization
[1382:0205/175810.677446:ERROR:bus.cc(399)] Failed to connect to the bus: Could not
parse server address: Unknown address type (examples of valid types are "tcp" and on
UNIX "unix")
spawning carplay {
dpi: 240,
nightMode: 0,
hand: 0,
boxName: 'nodePlay',
width: 1024,
height: 600,
fps: 30
}
directory found
sending dpi
device connected and ready
unkown type: 24 with data:: <Buffer aa 55 aa 55 71 00 00 00 18 00 00 00 e7 ff ff
ff>
unkown type: 38 with data:: <Buffer aa 55 aa 55 00 00 00 00 26 00 00 00 d9 ff ff
ff>
unkown type: 1 with data:: <Buffer aa 55 aa 55 00 00 00 00 01 00 00 00 fe ff ff
ff>
No protocol specified
No protocol specified
No protocol specified

No protocol specified
[1442:0205/175811.182407:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004
(initialize): ANGLE Display::initialize error 12289: Could not open the default X
display.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not
open the default X display.
[1442:0205/175811.185215:ERROR:gl_display.cc(508)] EGL Driver message (Critical)
eglInitialize: Could not open the default X display.
[1442:0205/175811.185815:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with
error EGL_NOT_INITIALIZED, trying next display type
No protocol specified
[1442:0205/175811.189036:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004
(initialize): ANGLE Display::initialize error 12289: Could not open the default X
display.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not
open the default X display.
[1442:0205/175811.189975:ERROR:gl_display.cc(508)] EGL Driver message (Critical)
eglInitialize: Could not open the default X display.
[1442:0205/175811.190180:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with
error EGL_NOT_INITIALIZED
[1442:0205/175811.190613:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[1442:0205/175811.202102:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to
errors during initialization
No protocol specified
No protocol specified
No protocol specified
No protocol specified
[1451:0205/175811.370022:ERROR:angle_platform_impl.cc(43)] DisplayVkXcb.cpp:59
(initialize): xcb_connect() failed, error 1
ERR: DisplayVkXcb.cpp:59 (initialize): xcb_connect() failed, error 1
[1451:0205/175811.370568:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004
(initialize): ANGLE Display::initialize error 12289: Not initialized.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Not
initialized.
[1451:0205/175811.370870:ERROR:gl_display.cc(508)] EGL Driver message (Critical)
eglInitialize: Not initialized.
[1451:0205/175811.371051:ERROR:gl_display.cc(920)] eglInitialize SwANGLE failed with
error EGL_NOT_INITIALIZED
[1451:0205/175811.371263:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
starting projection
[1451:0205/175811.386732:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to
errors during initialization
No protocol specified
No protocol specified
[1459:0205/175811.486080:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is
disabled, ANGLE is
[1459:0205/175811.522482:ERROR:x11_software_bitmap_presenter.cc(142)]
XGetWindowAttributes failed for window 25165827
parsing type: 8 for length: 4 <Buffer aa 55 aa 55 04 00 00 00 08 00 00 00 f7 ff ff
ff>
parsing 8 <Buffer e8 03 00 00>
Carplay message: Support Wifi
unkown type: 13 with data:: <Buffer aa 55 aa 55 0d 00 00 00 0d 00 00 00 f2 ff ff
ff>

Buster:

pi@raspberrypi:~ $ sudo /home/pi/React_carplay/ReactCarplay-3.0.1-armv7l.AppImage --no-sandbox
/root/.config/ReactCarplay
[2712:0205/183609.365972:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2712:0205/183609.366281:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
No protocol specified
No protocol specified
No protocol specified
No protocol specified
[2742:0205/183609.649250:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[2742:0205/183609.649561:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[2742:0205/183609.649701:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
No protocol specified
[2742:0205/183609.650350:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[2742:0205/183609.650574:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[2742:0205/183609.650716:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[2742:0205/183609.650854:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[2742:0205/183609.686442:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[2712:0205/183610.016389:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
spawning carplay {
dpi: 240,
nightMode: 0,
hand: 0,
boxName: 'nodePlay',
width: 1024,
height: 600,
fps: 30
}
directory found
sending dpi
device connected and ready
unkown type: 24 with data:: <Buffer aa 55 aa 55 71 00 00 00 18 00 00 00 e7 ff ff ff>
unkown type: 38 with data:: <Buffer aa 55 aa 55 00 00 00 00 26 00 00 00 d9 ff ff ff>
unkown type: 1 with data:: <Buffer aa 55 aa 55 00 00 00 00 01 00 00 00 fe ff ff ff>
No protocol specified
No protocol specified
No protocol specified
No protocol specified
[2776:0205/183610.543691:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[2776:0205/183610.544046:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[2776:0205/183610.544231:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
No protocol specified
[2776:0205/183610.545206:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[2776:0205/183610.545475:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[2776:0205/183610.545628:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[2776:0205/183610.545780:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[2776:0205/183610.564742:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
No protocol specified
No protocol specified
starting projection
No protocol specified
No protocol specified
[2786:0205/183610.756925:ERROR:angle_platform_impl.cc(43)] DisplayVkXcb.cpp:59 (initialize): xcb_connect() failed, error 1
ERR: DisplayVkXcb.cpp:59 (initialize): xcb_connect() failed, error 1
[2786:0205/183610.757242:ERROR:angle_platform_impl.cc(43)] Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Not initialized.
ERR: Display.cpp:1004 (initialize): ANGLE Display::initialize error 12289: Not initialized.
[2786:0205/183610.757435:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Not initialized.
[2786:0205/183610.757567:ERROR:gl_display.cc(920)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[2786:0205/183610.757716:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[2786:0205/183610.771085:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
No protocol specified
No protocol specified
[2794:0205/183610.851136:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is disabled, ANGLE is
[2794:0205/183610.884361:ERROR:x11_software_bitmap_presenter.cc(142)] XGetWindowAttributes failed for window 27262978
parsing type: 8 for length: 4 <Buffer aa 55 aa 55 04 00 00 00 08 00 00 00 f7 ff ff ff>
parsing 8 <Buffer e8 03 00 00>
Carplay message: Support Wifi
unkown type: 13 with data:: <Buffer aa 55 aa 55 0d 00 00 00 0d 00 00 00 f2 ff ff ff>

Thanks for the great work btw!

Running v3.0.1 does not work (running the sudo command throws an error that it can't connect to bus), but using v1.0.6 and v1.0.5 sort of works, meaning carplay is recognized on my phone but the react app screen is blank. I can click on the blank screen and it recognizes input (i was even able to start/stop the music by trying to click in the middle of the blank screen) but nothing is shown.
Raspberry pi 4 on Bullseye
I think it might be because I have a slightly different Carlink model: Model CPC200-CCPA (versus the CPC200-Autokit shown in the demo)

How would I go about changing the resolution of CarPlay?

EDIT: So I was able to change the resolution in /root/.config/ReactCarplay/config.json but it doesn't change the view on the screen. The screen is still locked at the previous resolution, with it cutting off the sides of the CarPlay window that is extended to the resolution I input. I am using 1280x400 by the way.

Trying to install, however I get a syntax error

./ReactCarplay-3.0.1-armv7l.AppImage: 1: Syntax error: word unexpected (expecting ")"

Good day Sir!

I have the problem that the app is keep saying „requesting key frame“ as mentioned in #21
However, in my case, it didn‘t just started working.

Here are my logs:
log.txt

Maybe you have some ideas?
Thanks in advance

Hi,
I want to use joystick to navigate, so I need to change Up key to work as Up, hot like Home (and so I need to add a home key as well)
So is it possible to make it if I use a AppImage file?
Or how can I compile it using sources? what software do I need for that?

Hello,
I picked up a Carlinkit CPC200-CCPA from Amazon.

When I plug it in, about 25 seconds later Removable medium is inserted window opens, and 10 seconds after that it disconnects. When it disconnects a box in the top-right of the screen pops up saying:

Drive was removed without ejecting
Please use menu to eject before removal

If I run Carplay after it says it says that I disconnected it, I get the same errors as in #20. When I run lsusb the Carlinkit isn't listed.

If I run Carplay right after I plug the Carlinkit in, I get this error and then the app closes:

raspberry@raspberrypi:~/Desktop $ ./Carplay.AppImage
/home/raspberry/.config/ReactCarplay
spawning carplay {
dpi: 240,
nightMode: 0,
hand: 0,
boxName: 'nodePlay',
width: 799,
height: 479,
fps: 30
}
directory found
device not connected
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib/aarch64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
carplay connection
carplay connection
sending dpi
FATAL ERROR: LIBUSB_TRANSFER_ERROR
Aborted

When running lsusb the Carlinkit does show up until it disconnects itself.

Any advice?

Please use the format below to list if you have audio issues

• Dongle Firmware version (can be found in the logs when running the app from a terminal window)

• Did you purchase it on this firmware, or was it manually updated to this firmware

• Do you also get audio distortion when playing a text message (audio may be delayed from when you click play)

Hello, I want to add buttons for the next song, previous song, play/pause, etc to my steering wheel. Is it possible to trigger these events through signals from the GPIO pins? I believe issue #16 refers to this but only refers to keyboard inputs, not GPIO inputs.

Thanks for everything
-Nik

So I tried to run this on a pi zero 2 and its not really usable there with the lack of ram.

Is there recommended hardware for it?

Anyone had success with a pi 3b+ with 1gb ram?

I finally got around to update the build to the latest this weekend. It's 10x better when it comes to perfomance and sound quality. But.

After listening to music or using the maps. it's starting to stutter. and if i'm unlucky it freezes completly. When this is happening i can see that the bluethooth connection to the dongle is lost. Trying to connect it doesn't help since it wont let me unless i restart the program.

V3 also did have problems for me but it didn't stutter. it only frooze after a while. if i was lucky it worked without problem and if it frooze it would stop carplay from running and i could reconnect.

Atleast V4 doesn't crash on startup :)

RPi 4 4GB

When trying to build the app it is having troubles to do the pre build for the node usb module.

Here's the log:

> electron-builder build --linux AppImage --armv7l -c.extraMetadata.main=build/electron/main.js --publish never

  • electron-builder  version=22.14.13 os=5.15.32-v8+
  • loaded configuration  file=package.json ("build" field)
  • public/electron.js not found. Please see https://medium.com/@kitze/%EF%B8%8F-from-react-to-an-electron-app-ready-for-production-a0468ecb1da3
  • loaded parent configuration  preset=react-cra
  • description is missed in the package.json  appPackageFile=/home/volvo/Development/rtvi/package.json
  • electron-rebuild not required if you use electron-builder, please consider to remove excess dependency from devDependencies

To ensure your native dependencies are always matched electron version, simply add script `"postinstall": "electron-builder install-app-deps" to your `package.json`
  • writing effective config  file=dist/builder-effective-config.yaml
  • rebuilding native dependencies  [email protected] platform=linux arch=armv7l
  • install prebuilt binary  name=usb version=1.7.2 platform=linux arch=armv7l napi=
  • build native dependency from sources  name=usb
                                          version=1.7.2
                                          platform=linux
                                          arch=armv7l
                                          napi=
reason=prebuild-install failed with error (run with env DEBUG=electron-builder to get more information)
                                          error=prebuild-install info begin Prebuild-install version 5.3.6
    prebuild-install WARN install prebuilt binaries enforced with --force!
    prebuild-install WARN install prebuilt binaries may be out of date!
    prebuild-install info looking for cached prebuild @ /home/volvo/.npm/_prebuilds/5d82ba-usb-v1.7.2-napi-v4-linux-armv7l.tar.gz
    prebuild-install http request GET https://github.com/tessel/node-usb/releases/download/v1.7.2/usb-v1.7.2-napi-v4-linux-armv7l.tar.gz
    prebuild-install http 404 https://github.com/tessel/node-usb/releases/download/v1.7.2/usb-v1.7.2-napi-v4-linux-armv7l.tar.gz
    prebuild-install WARN install No prebuilt binaries found (target=4 runtime=napi arch=armv7l libc= platform=linux)

So even though I get an appimage at the end, when trying to launch it (after chmod +x) it only says "no such file or directory"

Libudev is installed. When trying to build the "node usb electron test app" which is using the latest node usb release it doesn't throw this error and builds successfully.

Is it maybe an issue with 1.7.2? I tried to pin the dependency on 1.7.1 but it's always going for 1.7.2.

Is it eventually possible to upgrade to the latest node usb release and see if that resolves the issue?

Not really an issue so sorry, but I tried to find where the auto start on launch is and disable it but could not find it. How would I go about disabling it as i have other scripts i want to load first and i want to optionally start the carplay from there.

I get the error
elise@raspberrypi:~/Desktop $
• /CarpLay.AppImage
A Javascript error uccurred In the main process
Uncaught Exception:
Error: No native build was found for platform=linux arch=arm runtime=electron abi fault libc=glibe node=18.17.1 electron=27.0.4|
Loaded from: /tmp/.mount_CarplaoLKjo2/resources/app.asar/node modules/usb at load.resolve. Load.path/tmp/.mount_CarplaolKjo2/resources/app.asar/node_modules/node-gyp-b
u1 ld/node-gyp-build.js: 60:9)
at load (/tmp/.mount_CarplaolKj02/resources/app.asar/node_modules/node-gyp-build/node-gyp-buil
d.js: 22:30)
at Object. (/tmp/.mount_CarplaolKjo2/resources/app.asar/node_modules/usb/dist/usb/b
indings.js:8:38
at Module. compile (node:internal/modules/cjs/loader: 1271:14) at Object..js (node:internal/modules/cjs/loader:1326:10)

Hello Rhys,

Im having a strange issue since yesterday and hope that you might be able to help.

I'm getting:

`Module not found: Error: Can't resolve 'fs'

Module not found: Error: Can't resolve 'path'`

I tried your app, the latest stable version of mine and I can't seem to compile it anymore. Also I tried some of the fixes you find online but without any luck.

The error appeared suddenly while I made some minor code changes. It stayed even after reverting everything as mentioned above.

Did you ever run into this issue before?

Cheers

Encountered a problem when using the touch that when pressing Settings it doesn't do anything. The button is pressable using touch and i can see the blue ish background but it doens't open the modal. Using the mouse however does open the modal.

Latest version.
Ingcool 7" Touch.
RPi 4b

am getting the error in the title aswell as
'directory found'
and then just aborted
any ideas?

Running on Ubuntu Desktop 20 and V1.0.4 and im running it locally, not over terminal.

root@beelink:/home/oc/Downloads# sudo ./ReactCarplay-1.0.4-armv7l.AppImage --no-sandbox
./ReactCarplay-1.0.4-armv7l.AppImage: 1: Syntax error: word unexpected (expecting ")")

Any ideas or ways to get better logs to help debug this?

App does not recognize/detect phone, following message is shown: "Connect iPhone to begin CarPlay". After a few seconds the following is output to the console:

volvo@raspberrypi:~ $ sudo /home/volvo/Desktop/Carplay.AppImage --no-sandbox

/root/.config/ReactCarplay
spawning carplay {
dpi: 240,
nightMode: 0,
hand: 0,
boxName: 'nodePlay',
width: 800,
height: 480,
fps: 30
}
directory found
device not connected
Socket connected. sending data...

14 0.225 0.7032967032967034
(node:1762) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'transfer' of null
at /tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/DongleHandler.js:247:29
at new Promise ()
at /tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/DongleHandler.js:246:13
at new Promise ()
at DongleHandler.serialise (/tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/DongleHandler.js:237:16)
at DongleHandler.sendTouch (/tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/DongleHandler.js:145:14)
at Carplay.sendTouch (/tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/Carplay.js:25:22)
at IpcMainImpl. (/tmp/.mount_CarplaAMpFNp/resources/app.asar/build/electron/main.js:99:17)
at IpcMainImpl.emit (events.js:315:20)
at Object. (electron/js2c/browser_init.js:161:9492)
(Use carplay --trace-warnings ... to show where the warning was created)
(node:1762) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:1762) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
16 0.225 0.7032967032967034
(node:1762) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'transfer' of null
at /tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/DongleHandler.js:247:29
at new Promise ()
at /tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/DongleHandler.js:246:13
at new Promise ()
at DongleHandler.serialise (/tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/DongleHandler.js:237:16)
at DongleHandler.sendTouch (/tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/DongleHandler.js:145:14)
at Carplay.sendTouch (/tmp/.mount_CarplaAMpFNp/resources/app.asar/node_modules/node-carplay/modules/Carplay.js:25:22)
at IpcMainImpl. (/tmp/.mount_CarplaAMpFNp/resources/app.asar/build/electron/main.js:99:17)
at IpcMainImpl.emit (events.js:315:20)
at Object. (electron/js2c/browser_init.js:161:9492)
(node:1762) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

Tried connecting the phone using Wi-Fi, BlueTooth, a lightning cable plugged in the Carlinkit adapter, and a lightning cable plugged in the rpi itself. Also created the udev rules using the setup-pi.sh script from this repo.

Raspberry Pi 3b+ (Linux raspberrypi 5.15.76-v7+ #1597 SMP Fri Nov 4 12:13:17 GMT 2022 armv7l GNU/Linux)
react-carplay release v1.0.4.
Carlinkit CPC200-CCPA
iPhone 6S
ffplay version 4.3.5-0+deb11u1+rpt2
ffmpeg version 4.3.5-0+deb11u1+rpt2

Any ideas? Let me know if any more info is needed.

Thanks!

Any chance of providing/supporting amd64 builds?

Hi,

when I run the executable 1.0.3 or 1.0.4 it waits a little and then I get this message in the terminal:

file downloaded, unzipping
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of AutoKit.apk or
AutoKit.apk.zip, and cannot find AutoKit.apk.ZIP, period.

I get this message as the GUI loads and it does go on to show a "connect iPhone" screen and then a blank screen once you do.

Any idea what's going on here?

Thanks,

Allan

Hi!
When the application starts, the Autokit.apk file is not downloaded, error 404. If i download the file from another site and unpack the assets folder, the application starts normally. But, at autorun, it tries to download the file again and does not see the assets folder

Thank you in advance for this amazing application.

I'm running a raspberry pi 3B, Raspberry Pi OS (64 bit) and a CPC200-U2W-Plus carlinkit dongle. Do you know if these two are compatible?

I've tried running the application and get a blank screen which shows 4 tabs at the top of a phone, setting, info, and exit button. I followed your installation instructions and everything downloaded correctly but I cannot get it to go past the electron screen.

I've plugged in the dongle and pressed the "Plug-In Carplay Dongle and Press" button with no reaction. Any help is greatly appreciated.

So i'm currently trying to get it working on my laptop, running linux. And the app is starting up and connecting with the dongle, also it seems that it recognizes the phone.
But then it keeps logging: "requesting key frame" and the carplay never shows something in the app.

Do you might have any idea what the problem could be?
Does this work with all iOS versions?

Thanks!

Hello,
Do you know if your application will be compatible with CPC200-TBOX?
I'm trying to connect it but with no luck.
I look forward to hearing from you soon.
Thanks.

Kind regards,
Javier

I keep receiving this error...

[1532:0826/035028.702828:ERROR:ozone_platform_x11.cc(239)] Missing X server or $DISPLAY
[1532:0826/035028.703101:ERROR:env.cc(255)] The platform failed to initialize. Exiting.

I'm going in circles, please help.

Hello, I'm trying to customize the app a bit to my needs but as of yesterday no matter what I do, the app crashes right after it tries to launch the CarPlay module, after the console log "directory found". The only code it throws is a SIGABRT.

Even tried downgrading from 18.4.0 to Node Version 16.15.1, NPM is 8.11.0.

Im new to node.js and I'm not sure what could cause this. I tried to do a fresh npm install on the main branch as well as the latest release with the same result when trying to run the app. What's weird is that it was working before and I didn't really change anything in my setup.

Hope somebody might know what to do..

Hello, I have this working perfectly on my RPi!
Thanks for your work on this!

One thing I am struggling with though, how do we set the Manufacture Icon on the device to show as say "Jaguar" rather than defaulting to "Audi MMI" - I can't seem to find any config files for the AutoKit it is using.

Installing AutoKit onto my Android device brings up the device settings and it is settable there

How have you changed yours?

Thanks!

Joshua

On the first start of the application i get following error.
file downloaded, unzipping
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of AutoKit.apk or
AutoKit.apk.zip, and cannot find AutoKit.apk.ZIP, period.