opencardev / crankshaft Goto Github PK

Feature Request
Add an Info tab to show basic information. Include the following;

1. Crankshaft version
2. OpenAuto version

• Phone: Pixel 1 - Android Oreo 8.1
• Image 2018-02-28

The audio is choppy when navigation is used at the same time as podcast playback. It happens in OpenAuto too. Find a way to mitigate the problem.

Galaxy s8+ IMG 2018-03-02
Maybe make the terminal accessible so people can change things such as screen rotation through boot/config.txt and master volume through alsamixer.

The volume lowering of music from Google Music is delayed by a few seconds from when navigation (Google Maps) info is played.

Example:
Turn left in 400 ft. And then a couple seconds later the music volume will decrease.

This happens when on the main screen, when I have the map displayed I get stuttering like issue #16 . I have not yet tried to see if the issue happens with other notifications like text messages.

I did notice a long buffering with music also. I press skip to next song and it would take about 3-4 seconds to change what is coming out, however the display showed the next song. This could be a related buffering issue or a completely different issue.

I am using version 2018-03-05

I don't see this as currently implemented (correct me if I'm wrong!) but would it be possible to implement custom key binding? Like if you have a USB button connected to the Pi, or a USB gadget, having said gadget do an action like "Pause/Play" or "Mute" and volume controls would be wonderful. That way people can integrate their own buttons in the car!

The pain is not over yet. When listening to podcasts and driving at the same time, audio stutters badly. Revert OpenAuto's change to resolve this problem.

I'm used to OLED screens, the 7" official touchscreen is very washed out colour wise, having the option to make it more vibrant would be ace!

When I enter "Settings" and select the "Bluetooth" tab, and select the "Use local adapter" radio option and then save settings, the settings app closes. I briefly see the terminal prompt, and then I see "Waiting for device" again.

If I enter settings, my change doesn't seem to be persisted, and "Disable bluetooth" is selected.

• What phone do you have? What OS version?

Google Pixel (2016)
Oreo (8.1.0)

• Does it happen with OpenAuto on X11 too, or you don't know?

Don't know

• Did you try to compile OpenAuto with Xorg instead of EGL? Did you follow the build instructions on https://github.com/f1xpl/openauto/wiki/Build-instructions? What is your libQt version and does that come with raspbian?

No. Nope. Whatever version comes with Crankshaft 2018-08-28

I got a raspberry pi with no display, so thought of hooking it up to my monitor with HDMI cable. I could boot it up and connect my pixel to the device. I get the message that Android auto is enabled, on my pixel, but the display on the monitor still shows nothing conncected. I have a mouse connected too, but it won't do much most of the time.

• What phone do you have? What OS version? Google pixel; Andrid 8.1

• Did you try to enable and run autoapp under X11 dev mode? Follow this: https://github.com/htruong/crankshaft/wiki/Crankshaft-dev-mode

• Please provide any further information that you might find helpful.
  

Definitely not a high priority, but this would also be a great enhancement.

While I have an Android phone that's compatible, I have friends and others that don't, and sometimes I might need my phone not to be plugged in (for one reason or another).

It might be useful to allow buttons to be placed on the main screen that link/point to other raspberry Pi apps so that, say, a different music player can be launched, or custom scripts can be run, like OBD tools etc.

It would be nice to eventually be able to have an automated build system in Docker or any continuous integration system. There are more scripting needed before that becomes a reality.

Some phones were reported to have problems connecting to OpenAuto. The problem goes away with official OpenAuto on X11. Figure out a way to get around the problem.

It would be nice to be able to distribute OpenAuto/Crankshaft as a Debian package. Figure out how.

It would be great if a gpio pin would trigger the input on the camera port on the rpi3.

• What phone do you have? What OS version? Pixel 2XL
• Did you try to enable and run autoapp under X11 dev mode? Follow this: https://github.com/htruong/crankshaft/wiki/Crankshaft-dev-mode
• Please provide any further information that you might find helpful.

Hi i am using this as primary head unit need some sort of volume control in the application

Would be nice to be able to control brightness of the Pi on the crankshaft UI without having to go into dev mode. This would help several of us from having to go thru adding a physical momentary button (like what everlander did and controlling this thru the GPIO )

Maybe even set a brightness profile based on time of the day?

Some users want a hardwired shutdown button, so let's use GPIO 3 as a trigger for shutdown.

I can't seem to find it this supports Waze alongside google maps. Screenshots don't show the proper navigation which allows you to choose Waze or Google. I searched through the source and openauto but couldn't find anything referencing Waze

This is an awesome idea, but it doesn't seem to work for me.

I've flashed the image and can boot the RPi 3 with no problem. The screen comes up, waiting for a device to be connected. However, when I connect my phone (OnePlus 3), Android Auto starts on the phone, but nothing happens with the UI on the PI.

The log shows some errors, but nothing that tells me anything useful:

Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.443027] [0x6d7d0310] [info]    [AaApp] [USBApp] Device connected.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.443862] [0x6d7d0310] [info]    [AaApp] [AndroidAutoEntity] start.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.445805] [0x72807000] [debug]   [AaApp] [AudioInput] create.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.446484] [0x72807000] [debug]   [AaApp] [AudioOutput] create.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.446867] [0x72807000] [debug]   [AaApp] [AudioOutput] create.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.447189] [0x72807000] [debug]   [AaApp] [AudioOutput] create.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.447493] [0x6d7d0310] [info]    [AaApp] [AudioInputService] start.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.454069] [0x6d7d0310] [info]    [AaApp] [AudioService] start, channel: MEDIA_AUDIO
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.454443] [0x6d7d0310] [info]    [AaApp] [AudioService] start, channel: SPEECH_AUDIO
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.454617] [0x6d7d0310] [info]    [AaApp] [AudioService] start, channel: SYSTEM_AUDIO
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.454774] [0x6d7d0310] [info]    [AaApp] [SensorService] start.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.454981] [0x6d7d0310] [info]    [AaApp] [VideoService] start.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.455171] [0x6d7d0310] [info]    [AaApp] [BluetoothService] start.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.455355] [0x6d7d0310] [info]    [AaApp] [InputService] start.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.571513] [0x6e7d0310] [info]    [AaApp] [AndroidAutoEntity] version response, version: 1.4, status: 0
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.571598] [0x6e7d0310] [info]    [AaApp] [AndroidAutoEntity] Begin handshake.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.587691] [0x6d7d0310] [info]    [AaApp] [AndroidAutoEntity] Handshake, size: 2282
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.651121] [0x6d7d0310] [info]    [AaApp] [AndroidAutoEntity] continue handshake.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.664682] [0x6efd0310] [info]    [AaApp] [AndroidAutoEntity] Handshake, size: 51
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.665141] [0x6efd0310] [info]    [AaApp] [AndroidAutoEntity] Auth completed.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692294] [0x6efd0310] [info]    [AaApp] [AndroidAutoEntity] Discovery request, device name: Android, brand: OnePlus ONEPLUS A3003
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692371] [0x6efd0310] [info]    [AaApp] [AudioInputService] fill features.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692423] [0x6efd0310] [info]    [AaApp] [AudioService] fill features, channel: MEDIA_AUDIO
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692458] [0x6efd0310] [info]    [AaApp] [AudioService] fill features, channel: SPEECH_AUDIO
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692484] [0x6efd0310] [info]    [AaApp] [AudioService] fill features, channel: SYSTEM_AUDIO
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692507] [0x6efd0310] [info]    [AaApp] [SensorService] fill features.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692546] [0x6efd0310] [info]    [AaApp] [VideoService] fill features.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692574] [0x6efd0310] [info]    [AaApp] [BluetoothService] fill features
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.692596] [0x6efd0310] [info]    [AaApp] [InputService] fill features.
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.760468] [0x6efd0310] [info]    [AaApp] [AndroidAutoEntity] requested audio focus, type: 4
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.760523] [0x6efd0310] [info]    [AaApp] [AndroidAutoEntity] audio focus state: 3
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.765763] [0x6efd0310] [info]    [AaApp] [AudioInputService] open request, priority: 0
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.765811] [0x6efd0310] [info]    [AaApp] [AudioInputService] open status: 0
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.771176] [0x6d7d0310] [info]    [AaApp] [AudioService] open request, channel: MEDIA_AUDIO, priority: 0
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.771245] [0x6d7d0310] [info]    [AaApp] [AudioService] open status: 0, channel: MEDIA_AUDIO
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.776517] [0x6d7d0310] [info]    [AaApp] [AudioService] open request, channel: SPEECH_AUDIO, priority: 0
Feb 25 19:57:40 raspberrypi autoapp[362]: [2018-02-25 19:57:40.776587] [0x6d7d0310] [info]    [AaApp] [AudioService] open status: 0, channel: SPEECH_AUDIO
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.781982] [0x6efd0310] [info]    [AaApp] [AudioService] open request, channel: SYSTEM_AUDIO, priority: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.782103] [0x6efd0310] [info]    [AaApp] [AudioService] open status: 0, channel: SYSTEM_AUDIO
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.789278] [0x6d7d0310] [info]    [AaApp] [SensorService] open request, priority: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.789327] [0x6d7d0310] [info]    [AaApp] [SensorService] open status: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.796448] [0x6d7d0310] [info]    [AaApp] [VideoService] open request, priority: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.796505] [0x6d7d0310] [info]    [AaApp] [OMXVideoOutput] open.
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.805836] [0x6d7d0310] [info]    [AaApp] [VideoService] open status: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.806322] [0x6e7d0310] [info]    [AaApp] [InputService] open request, priority: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.807010] [0x6e7d0310] [info]    [AaApp] [InputService] open status: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.815449] [0x6d7d0310] [info]    [AaApp] [AudioService] setup request, channel: MEDIA_AUDIO, config index: 1
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.815511] [0x6d7d0310] [info]    [AaApp] [AudioService] setup status: 2, channel: MEDIA_AUDIO
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.821015] [0x6efd0310] [info]    [AaApp] [AudioService] setup request, channel: SPEECH_AUDIO, config index: 1
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.821073] [0x6efd0310] [info]    [AaApp] [AudioService] setup status: 2, channel: SPEECH_AUDIO
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.826355] [0x6d7d0310] [info]    [AaApp] [AudioService] setup request, channel: SYSTEM_AUDIO, config index: 1
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.826413] [0x6d7d0310] [info]    [AaApp] [AudioService] setup status: 2, channel: SYSTEM_AUDIO
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.832486] [0x6d7d0310] [info]    [AaApp] [SensorService] sensor start request, type: 13
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.837997] [0x6d7d0310] [info]    [AaApp] [VideoService] setup request, config index: 3
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.838050] [0x6d7d0310] [info]    [AaApp] [OMXVideoOutput] init, state: true
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.838362] [0x6d7d0310] [info]    [AaApp] [VideoService] setup status: 2
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.839197] [0x6d7d0310] [info]    [AaApp] [VideoService] video focus indication.
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.843652] [0x6efd0310] [info]    [AaApp] [InputService] binding request, scan codes count: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.843704] [0x6efd0310] [info]    [AaApp] [InputDevice] start.
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.843737] [0x6efd0310] [info]    [AaApp] [InputService] binding request, status: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.849817] [0x6efd0310] [info]    [AaApp] [SensorService] sensor start request, type: 10
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:57:40.855333] [0x6efd0310] [info]    [AaApp] [VideoService] start indication, session: 0
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225190] [0x6e7d0310] [error]   [AaApp] [SensorService] channel error: AaSdk error code: 10, native code: 1
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225293] [0x6e7d0310] [error]   [AaApp] [SensorService] channel error: AaSdk error code: 10, native code: 1
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225379] [0x6e7d0310] [error]   [AaApp] [AudioService] channel error: AaSdk error code: 10, native code: 1, channel: SPEECH_AUDIO
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225445] [0x6e7d0310] [error]   [AaApp] [AudioService] channel error: AaSdk error code: 10, native code: 1, channel: MEDIA_AUDIO
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225476] [0x6d7d0310] [error]   [AaApp] [AudioInputService] channel error: AaSdk error code: 10, native code: 1
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225504] [0x6e7d0310] [error]   [AaApp] [AudioService] channel error: AaSdk error code: 10, native code: 1, channel: SYSTEM_AUDIO
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225560] [0x6d7d0310] [error]   [AaApp] [AndroidAutoEntity] channel error: AaSdk error code: 10, native code: 1
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225613] [0x6e7d0310] [error]   [AaApp] [BluetoothService] channel error: AaSdk error code: 10, native code: 1
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225655] [0x6d7d0310] [info]    [AaApp] [USBApp] quit.
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225700] [0x6d7d0310] [info]    [AaApp] [AndroidAutoEntity] stop.
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225741] [0x6d7d0310] [info]    [AaApp] [AudioInputService] stop.
Feb 25 19:58:01 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225845] [0x6d7d0310] [info]    [AaApp] [AudioService] stop, channel: MEDIA_AUDIO
Feb 25 19:58:06 raspberrypi autoapp[362]: [2018-02-25 19:58:01.225909] [0x6d7d0310] [info]    [AaApp] [AudioService] stop, channel: SPEECH_AUDIO
Feb 25 19:58:06 raspberrypi autoapp[362]: [2018-02-25 19:58:01.226038] [0x6d7d0310] [info]    [AaApp] [AudioService] stop, channel: SYSTEM_AUDIO
Feb 25 19:58:06 raspberrypi autoapp[362]: [2018-02-25 19:58:01.226102] [0x6d7d0310] [info]    [AaApp] [SensorService] stop.
Feb 25 19:58:06 raspberrypi autoapp[362]: [2018-02-25 19:58:01.226156] [0x6d7d0310] [info]    [AaApp] [BluetoothService] stop.
Feb 25 19:58:06 raspberrypi autoapp[362]: [2018-02-25 19:58:01.226203] [0x6d7d0310] [info]    [AaApp] [InputService] stop.
Feb 25 19:58:06 raspberrypi autoapp[362]: [2018-02-25 19:58:01.226239] [0x6d7d0310] [info]    [AaApp] [InputDevice] stop.
Feb 25 19:58:06 raspberrypi autoapp[362]: [2018-02-25 19:58:01.227407] [0x6d7d0310] [info]    [AaApp] [USBApp] Waiting for device...
Feb 25 19:58:06 raspberrypi autoapp[362]: [2018-02-25 19:58:01.227558] [0x6d7d0310] [debug]   [AaApp] [AndroidAutoEntity] destroy.

Any idea on what might be the issue?

I also tried compiling aasdk and openauto from source, but it is the same error..

day and night mode is brilliant but the brightness is still blinding in night mode.

would it be possible to add manual, time or sunrise/sunset brightness control, please?

If you disable the onboard LEDs, you can lower the Pi's consumption by 30mA, which might make a difference for some (and those LEDs are not visible behind the dash anyways). Some power specs here.

To not have to worry much about filesystem corruption, it was necessary to mount the main FS read-only. Now that makes it very hard to save the settings if that turns out to be a requirement in the future. Figure out a way to do an overlay filesystem ala OpenWRT settings system.

In the current state of Crankshaft, every upgrade needs to be done by reflashing the SD card. A better way to upgrade would be either OTA or at least through a USB drive/Android phone.

The default volume level on image 2018-03-05- is low. Increase the default volume.

• What phone do you have? What OS version?: Pixel XL 8.1
• Did you try to enable and run autoapp under X11 dev mode? no
• Please provide any further information that you might find helpful.

Latest release 0.2.0 - plugging in the USB into the phone does not always trigger Android Auto to start. Restarting Pi sometimes help, sometimes doesn't.

P.S. such an awesome project, thanks to everyone for their hard work on this!

• Nexus 5x Android 8.1.0
• X11 Mode did not work with jumper. In fact it hung up when I tried to plug in my phone.
• Using these LCD settings:

max_usb_current=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0
hdmi_drive=1

GPIO drivers are not working (might not be included in the latest build - Openauto 0.2.0 2018-03-13)

Even though touch does not work, it appears to be pulling data from my phone. Displays my local weather information after Android Auto starts. I can't get past that screen since touch is not working.

Is there a way to SSH in? When I attempt a connect, connection is refused.

• What phone do you have? What OS version? HTC 10 (2016) running Android 8.0.0
• Did you try to enable and run autoapp under X11 dev mode? Follow this: https://github.com/htruong/crankshaft/wiki/Crankshaft-dev-mode. Yes. I tried to adjust output volume using alsamixer but still without a luck
• Please provide any further information that you might find helpful.

First of all, I am using Raspberry Pi 2 and connecting my HTC 10 running Android 8.0 through the HTC OEM USB Type-C cable.

As for the sound card, I am using an external USB sound card Sound Blaster Play! 2. I could hear crackles when I play music through Google Play Music. The crackles and pops in the beginning of audio output are very noticeable. I am using the crankshaft-2018-03-13.zip build.

I also tried to reproduce this issue with Raspberry Pi 3 and same Sound Blaster Play! 2 USB sound card and this could be reproducible. With Pi's built-in 3.5mm output jack, this problem cannot be reproducible.

I was wondering what the ETA on Wireless Android Auto was and if anyone has had a chance to implement it? It would be so nice honestly as I don't really wish to plug in my phone every time I get in the car. Here is the hardware I have as of right now.

• Pixel 2 XL (Android Oreo 8.1.0, March Security Patch)
• Standard Official Raspberry PI Display

I am using an egalax hdmi screen and usb touchscreen. Everything is working great except my x-axis is flipped for the touchscreen. Is there any setting to flip the x-axis?

• What phone do you have? What OS version?:
  GM-930F (Galaxy S7 with 7.0)

• Did you try to enable and run autoapp under X11 dev mode? Follow this: https://github.com/htruong/crankshaft/wiki/Crankshaft-dev-mode
  Not yet, but will do soon (same issue occurs when I build openauto myself)

• Please provide any further information that you might find helpful.
  Is there something I'm missing? Should I just build a dev mode version/jump the standard one and look in alsamixer?

This would be a nice feature to help to help new users get started with Crankshaft.

Samsung Galaxy S8+ 02/28/18 Image

When booted into the Read write mode (jumping GPIO 4 to ground) it will reboot with modified settings then immediately reboot wiping all settings back to default.

Please comment here devices that are known to work and not work. Specifically:

• Phone
• Raspberry Pi version/hardware.
• Any customization done to the distro.
• If it doesn't work, have you tried with other USB cables?

For people using custom HDMI touch screens, please try Starting Crankshaft in X11 mode on image 2018-03-10 or later.

There is very likely that OpenAuto will work with your phone regardless of whether Crankshaft works or not. If Crankshaft does not work for you yet, there is a big chance that if you know how to compile OpenAuto yourself, it will work.

• What phone do you have? What OS version? Pixel XL 2
• Did you try to enable and run autoapp under X11 dev mode? no
• Please provide any further information that you might find helpful:

Previous build had no sound problems using the USB sound card, I suspect the sound amplification on this build was for all not just the built in Aux

Thanks for your good job ;-)
Will the "Hifiberry" sound card work? Can two sound cards, one for the microphone and one for the sound (Hifiberry), be put into operation?

• What phone do you have? What OS version? Pixel 2 XL, 8.1
• Did you try to enable and run autoapp under X11 dev mode? Follow this: https://github.com/htruong/crankshaft/wiki/Crankshaft-dev-mode- no
• Please provide any further information that you might find helpful.
  none

I wanna to use it as standalone headunit.
I wanna set up at least standalone media.
Maybe any other app which is not depends to my phone.
And sometimes launch AA when it needed.

Is it possible with this distribution?

• The system doesnt startup and stops with a error screen.
• Did not get a chance to connect to the phone yet Galaxy Edge S7?
  Please find attached screen shots of the error
  
  

Some cases have the screen upside-down, this makes it tedious to leave the Android Auto launcher and modify the boot.txt. A dropdown menu can be added for the 4 display orientations in the "Display" tab.

Edit: Clarified title

Currently very little use for this, but perhaps a button on the main screen to return to Android Auto if a phone is connected? Since Android Auto allows us to return to the OS using a button, it seems only fitting to allow the opposite too!

Here is the use case: I have music on my USB stick that I'd like to play in the car's head unit via the Raspberry Pi/Android Auto when my phone is NOT connected to the Pi. Someone else had put in a requirement for running native apps on Pi when phone not connected. I'd like the ability to turn on the wifi and connect to a network so that I can transfer files to the pi's SD card or USB stick by ssh in without putting in the jumper, going into dev mode, etc.

It is possible to provide A2DP with the RPi3's Bluetooth chip. Figure out a way to allow users to connect to their stereo. Probably not going to happen before the overlay problem is solved.

The text in the current distro is ugly. We need to fix that.

Yanking out the USB cable is dumb and dangerous. Figure out a way to do it more gently.

It would be great if we could display a splash screen or at least no messages during boot. This would make the bootup look better for use day to day. Of course in dev mode those messages may be useful however, outside of dev mode they shouldn't be necessary.

Perhaps something like this would help: https://raspberrypi.stackexchange.com/questions/59310/remove-boot-messages-all-text-in-jessie/59311

what is the purpose of the lightning bolt icon in the upper right hand corner? is there a way to turn it off?

Hi all, using RPI3 with an Adafruit 5" screen. I can get the screen working (after editing the config.txt file with the Adafuit changes), but the touchscreen - unsurprisingly - doesn't. The touchscreen registers as a mouse and although Crankshaft does register the touch it doesn't take note of the position.

Doubt this is something anyone is worried about, I just happened to have a 5" screen already 😁 Would be nice to try in car properly before maybe getting new screen 😄

I noticed that AA should be able to use other apps, such as Skype. However I have not been able to find Crankshaft (using 0.2.0 and a Pi3 and an Adafruit 5" LCD with touch in X11 mode). Am I missing something or are they not supported?

I just wanted to ask quickly. I use Waze on my phone and when it is dark it goes into a night mode. Using it on crankshaft it doesn't. I was wondering if this is something that on official car units would be handled by turning on the headlights. If this is the case could a GPIO pin be used for the same effect? A simple switch could be used, or a light sensor connected to the GPIO pin to register light/dark?