Database Develop

Google voice commands / "oke google"

Hi,
I'm wondering if some of you KLD / KLG / MX / etc unit owners are using google voice commands. I can't use it properly on my unit, it crashes all the time. Sometimes it works, but usually it crashes. I'm using Malaysk rom. Is there anybody who can you use google voice without any problems? Or is there a simpel solution to fix my issues? I'm using a external mic connected with a jack to the backside of my unit.

I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing

Missing features.
carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
Click to expand...
Click to collapse
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!

aledesma said:
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!
Click to expand...
Click to collapse
Phone calls? No. I believe this is a common issue, there is no phone hardware onboard. Though I'm not that familiar with that feature.
Email and other task could be handled with Autovoice if Google app can not. Again, not that familiar.
For me, the main missing feature was choice of navigation app. Nav questions will only launch GMaps, newer version can launch Waze or your nag app choice, by default.

carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing
Click to expand...
Click to collapse
Thanks for your comment. I tried your solution and its working better, i still get some errors time to time, but is much better...thanks

[
aledesma said:
Hi, Does your okay google now allow you to make phone calls, send email etc.... what features are you loosing out by going this route. Thanks!!!!
Click to expand...
Click to collapse
If you have a phone connected via BT you can make phone calls using OK Google.

Tumke32 said:
Hi,
I'm wondering if some of you KLD / KLG / MX / etc unit owners are using google voice commands. I can't use it properly on my unit, it crashes all the time. Sometimes it works, but usually it crashes. I'm using Malaysk rom. Is there anybody who can you use google voice without any problems? Or is there a simpel solution to fix my issues? I'm using a external mic connected with a jack to the backside of my unit.
Click to expand...
Click to collapse
I've read some posts in the Malaysk ROM thread and many people have modded their units by opening them up and re-runing the internal mic. It's that mic, not the external, that is used for voice commands and apparently it is an unshielded wire that allows for a lot of interference and therefore unreliable google voice. I'm still foggy on the voice dialing but someone somewhere got this to work but not through the native bluetooth app. I think I read that they used the RK3066/Rk3188 app in the google play store or something...I'm just getting started with my unit and it's not even installed yet. Hopefully some of this was insightful for you.

newt_dunbarton said:
I've read some posts in the Malaysk ROM thread and many people have modded their units by opening them up and re-runing the internal mic. It's that mic, not the external, that is used for voice commands and apparently it is an unshielded wire that allows for a lot of interference and therefore unreliable google voice. I'm still foggy on the voice dialing but someone somewhere got this to work but not through the native bluetooth app. I think I read that they used the RK3066/Rk3188 app in the google play store or something...I'm just getting started with my unit and it's not even installed yet. Hopefully some of this was insightful for you.
Click to expand...
Click to collapse
I am using the latest Malaysk ROM dated 10th January 2016 for RK3188 1024*600. It lets me speak Ok Google and Call (contact name) to the phone when after pressing the call button. The way it works for me is:
1. Whatever is playing on the unit, it stops when I press the call button on my steering;
2. It launches the unit's dial screen;
3. I say 'OK Google', it launches the ok google listener on the phone;
4. I say 'Call (contact name)' and it calls.
Few things I had to manage before this started working was:
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
2. Enable to XPOSED MTC in the XPOSED framework in the head unit;
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
Hope this helps.

Can you elaborate on this process please?
carter.w.jason said:
I have spent a lot of time with this issue. My views are that the OEM version of the Google app is the only stable version(for voice use) for these HUs. My JY solution was to extract the Velvet.apk from the factory ROM. After updating to a Malsysk ROM, I replaced the pre updated apk back to the older factory version. You will lose out out on some updated features, but having a working voice command is nice tradeoff.
Velvet.apk, OEM JY Version
https://drive.google.com/file/d/0B0iQtPEIFgeHR3hQdGlvd2RrVUk/view?usp=sharing
Click to expand...
Click to collapse
Did you go to file manager and replace the Malaysk version? Where is it located? or did you simply install with with apk instal app. Than you so much!!!!

aledesma said:
Did you go to file manager and replace the Malaysk version? Where is it located? or did you simply install with with apk instal app. Than you so much!!!!
Click to expand...
Click to collapse
Uninstalled with Titanium Backup. Velvet.apk is located in /system/priv-app. Copy/Paste replacement Velvet.apk using Root Explorer. !!! Set file permissions to 644 with Root Explorer !!! Reboot.

shaiq123 said:
I am using the latest Malaysk ROM dated 10th January 2016 for RK3188 1024*600. It lets me speak Ok Google and Call (contact name) to the phone when after pressing the call button. The way it works for me is:
1. Whatever is playing on the unit, it stops when I press the call button on my steering;
2. It launches the unit's dial screen;
3. I say 'OK Google', it launches the ok google listener on the phone;
4. I say 'Call (contact name)' and it calls.
Few things I had to manage before this started working was:
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
2. Enable to XPOSED MTC in the XPOSED framework in the head unit;
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
Hope this helps.
Click to expand...
Click to collapse
Hi,
1. Enable the option to receive commands over bluetooth in Google Now settings in the phone;
Were can i find this option? I have a nexus 5 and i updated my google now, but there no option like that in google now. Or do you mean the option "bluetooth headset" under voice?
3. Change the setting to integrate with phone's google now interface (something like that) in XPOSED MTC module.
I can't find any options in Xposed MTC related to what you are writing. Are you sure this option is in Xposed MTC?

Thank you!!!
carter.w.jason said:
Uninstalled with Titanium Backup. Velvet.apk is located in /system/priv-app. Copy/Paste replacement Velvet.apk using Root Explorer. !!! Set file permissions to 644 with Root Explorer !!! Reboot.
Click to expand...
Click to collapse
I will give it a shot!!!

Hi there,
I to have been wondering about the best way to get voice dialling working and as my google voice crashes the HU more often than not, I think it is best to do this as shaiq123 has suggested by pressing the call button the steering wheel and then Ok Googling the phone to make the call.
But my phone goes to lock screen in the car and that stops this working. What I would like is that when my phone connects to the car bluetooth it
1) stops it going to lockscreen
2) activates wifi hotspot
3) activates 'ok google' if it is not normally activated
and it reverses on disconnecting.
Is this something easily done or do I need some kind of app to do this?
A final thing that would be helpful, is that it would be useful to give the play music command to direct the HU to play music from an HU attached SD card rather than the phone memory. Is there a way to also configure that (i.e. that the command would seek music stored on HU rather than phone first?)
Cheers

Mr Bigglesworth said:
Hi there,
I to have been wondering about the best way to get voice dialling working and as my google voice crashes the HU more often than not, I think it is best to do this as shaiq123 has suggested by pressing the call button the steering wheel and then Ok Googling the phone to make the call.
But my phone goes to lock screen in the car and that stops this working. What I would like is that when my phone connects to the car bluetooth it
1) stops it going to lockscreen
2) activates wifi hotspot
3) activates 'ok google' if it is not normally activated
and it reverses on disconnecting.
Is this something easily done or do I need some kind of app to do this?
A final thing that would be helpful, is that it would be useful to give the play music command to direct the HU to play music from an HU attached SD card rather than the phone memory. Is there a way to also configure that (i.e. that the command would seek music stored on HU rather than phone first?)
Cheers
Click to expand...
Click to collapse
You could achieve the first part using Tasker, you would just create a profile to run your tasks that actives when your phone connects to the headunit. Its a great app for automating stuff like that.

dc5daft said:
You could achieve the first part using Tasker, you would just create a profile to run your tasks that actives when your phone connects to the headunit. Its a great app for automating stuff like that.
Click to expand...
Click to collapse
Thanks - in fact this morning I have downloaded the trial for Tasker as well as Automate to see if they can do what I am looking for.
I've decided what would be really helpful would be if I could
1) Use app to detect when phone connects to car HU via bluetooth
2) Launch Wifi Hotspot
3) set the camera button to unlock screen and activate google voice
Now 1&2 look like its not too difficult and may even be doable using the Sony Smart Connect app (on a Z2, not rooted).
3 doesn't seem to be as instantly obvious. In tasker, I put in a new profile>event>hardware>button camera, also selected non beginner settings so could pit priority to highest and activate stop event, then put the task as launch voice search app - but it just keeps doing the camera?

Mr Bigglesworth said:
Thanks - in fact this morning I have downloaded the trial for Tasker as well as Automate to see if they can do what I am looking for.
I've decided what would be really helpful would be if I could
1) Use app to detect when phone connects to car HU via bluetooth
2) Launch Wifi Hotspot
3) set the camera button to unlock screen and activate google voice
Now 1&2 look like its not too difficult and may even be doable using the Sony Smart Connect app (on a Z2, not rooted).
3 doesn't seem to be as instantly obvious. In tasker, I put in a new profile>event>hardware>button camera, also selected non beginner settings so could pit priority to highest and activate stop event, then put the task as launch voice search app - but it just keeps doing the camera?
Click to expand...
Click to collapse
Create a new Profile>State>Net>BT Connected then click the magnifying glass next to name and select the name of your headunit. This will mean whenever your bluetooth is connected to the headunit it will run the tasks associated with it. It will give you the option to name and create a task once you create your profile then create new>Net>WiFi Tether and set to On.
I have a Z2 as well and just tried the camera button as a profile and it didn't work for me either, you'll need to do some googling on that, not sure why it doesnt work. It's best to set a flash (Alert>Flash) in your task as a test to see if your task runs but I'm sure you need to need to have root to unlock the screen.

dc5daft said:
Create a new Profile>State>Net>BT Connected then click the magnifying glass next to name and select the name of your headunit. This will mean whenever your bluetooth is connected to the headunit it will run the tasks associated with it. It will give you the option to name and create a task once you create your profile then create new>Net>WiFi Tether and set to On.
I have a Z2 as well and just tried the camera button as a profile and it didn't work for me either, you'll need to do some googling on that, not sure why it doesnt work. It's best to set a flash (Alert>Flash) in your task as a test to see if your task runs but I'm sure you need to need to have root to unlock the screen.
Click to expand...
Click to collapse
Thanks for this - and yes this where I had got to (which make me feel better!). And I too think the camera button may not be workable without root.
I think I need to change my plans and see if I can prevent the lockscreen to come on when connected to this bluetooth device. That way I can fall back to using ok google as the lockscreen prevents ok google from completing requests.
Okay - think I've done that and it was easy enough, now have a profile which when connected to HU through bluetooth does (1) set off wifi tether and (2) Set keyguard off. Then with (3) double tap to wake screen and (4) Ok google should be able to do what I need it to.
Last thing I'm wondering if you could do is to create a large voice dial icon (double normal size etc) on screen (in case initial ok google doesn't work)...

[Android 4.1+] HeadUnit Reloaded for Android Auto with Wifi

This Threader is a Spin-off of the original: [Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p by the late :crying: @mikereidis.
App links: https://www.b3itlabs.com/prod.php?id=1
PlayStore: https://play.google.com/store/apps/details?id=gb.xxy.hr
Previous XDA Lab purchases can be downloaded using: https://www.b3itlabs.com/download.php
Last edited: 20/04/2023
Version 7.X Released
- It has braking changes for WiFi, this is mainly due to recent Android SDK limits, like toggling WiFi, BT, getting Mac address and others. Therefore WiFi connection now does need a helper app on the phone.
- Dropped GLES20 as too many issues reported by different bad implementations
- Resolution is now automatically detected based on the cars screen.
- SelfMode (running on phone screen) works without the need of activating developer options in Android Auto.
Last edited: 07/02/2021
Version 6.3 Beta 1 released
- Re-wrote whole rendering process to use GLES20, in simple terms video render should use GPU
- Much better scaling approach
- Added support for native AA Wireless. This will only work on the units where the BT is accessible from the Android, as many of those android powered Chinese units, have a separate BT board. For devices which supports this, no headunit server or no WiFi Launcher is needed.
- Changed key mapping, user can now define their own buttons as they wish.
Last edited: 21/06/2020
Version 5.2 released
- Removed WiFi Direct
- Improved menu UI CREDIT and THANKS TO @sebaw
- Updated margin setting
- Added option to record audio using BT mic (motorcycle helmets)
- Added button to reconnect WiFi connection ( phone and unit depended won't work on all units, please read app forum for how to connect)
- Option to disable touchscreen
- Removed brightness adjustment (some users experienced problems adjusting brightness after using previous version, sadly they need to do a factory reset of the unit, and update to current version)
Version 5 released
- New UI CREDIT and THANKS TO @sebaw
- New over-scan approach allowing any resolution units to work properly (including portrait mode)
- New mic source (should help with speech recognition)
- Added option to keep status bar (user request)
- Added welcome setup
- Added possibility to use old USB driver (android built in one) in case you cannot get it connected with the new version
- Added option for Gain control on mic
- Added option to keep Wifi off (for USB use)
- Changed Wifi Direct implementation (you will need to install the Wifi Launcher for HUR on the phone to use Wifi Direct)
- Removed option to stretch full screen as this is not needed any more (it will always be full screen)
- Fixed Incoming mode not setting password for some devices
- Fixed app crash when Wifi toggled during app running
- Fixed night icon colors for devices running 4.x
- Fixed app freeze if permissions denied
- Fixed app crash after device unplugged when using native android USB driver.
- Fixed day/night calculation if share GPS turned off
- Code cleanup
- Other bug fixes.
Also a big THANK YOU to @ppietak for helping with code cleanup and bug fixes!
Version 4.5 released
- Fixes for USB shuttering
- New USB driver
- Fixes for reverse camera not resuming on some units
- Added support for incoming connection listener (automating Wifi) - Experimental, read below how to connect
Version 4.4 Released
Change log
Fixed broken touchscreen
Changes on WideScreen mode and HD
Fixes for Rotary
Potential fix for black screen for second connection over Wifi
Left/Right hand driving position option (for widescreen)
Buffer setting for mic (could help when Assistant does not hear what you're saying)
Enjoy XDA Ad Free and check out:
Version 4.3 Released
Change log
Fixed double skip on Spotify when using SWC
No more decoder workaround needed (updated code for video playback)
Added support for rotary (arrow keys can be used for non-touch input)
Enhanced mic input (mic sampling rate can be adjusted in settings for better compatibility)
Added intent: "gb.xxy.hr.WifiP2P" for Wifi-Direct start
Added app color scheme (dark menu for night)
Mapped Key N to open Maps (N=Navigation)
Mapped Key L to open Multimedia (L = Listen)
Changed USB code, hoping to help those who suffered for USB disconnection problems
Fixed a serious bug in share GPS code
For some rooted android headunits the app can now disable the default call screen being overlayed when HUR is running (only if HUR is set as the navigation app!) This will require ROOT
Version 4.1 Released
Change log
Removed Google Play Services dependencies
Honda compatibility fixes
Some other small bug fixes
Version 4.0 Released
How to use the app?
USB Mode
Plug in the USB to your device (in case of tablet use an OTG cable), when prompted make sure you allow HUR to be the default app for the action and you check the always box.
If you are running the app on a device with Android 7.0 or higher, you might need to pull down the notification bar and select the connected USB device before the app starts (this is device dependent)
If the app does not start automatically when you plug in your phone, you can always open HUR, tap the USB button and select the phone from the list.
Wifi Mode
READ SECOND POST​
Self Mode (when Android Auto and HUR are running on the same device)
Open HUR and press the self mode button. (you need to make sure Android Auto, Google Play Service, Google maps, Google Text To Speech is also installed on the device and it's up to date)
FAQ / Troubleshoot
All I get is a black screen
- If you are using an Android powered headunit (Joying, Xtrons, etc) look for a setting on your device which allows Video Playback during drive
- Try changing HUR settings and enable Software decoding
What does the "Share GPS" do?
- Share GPS actually forwards the GPS data of your device to the phone, so phone will need to do less work, comes really handy if you have an Android powered headunit, with external GPS antenna, however, if you using a tablet which is built into the dashboard, it's possible that you want to turn off this feature, because your phone will have a more accurate GPS fix.
What is the Sink Audio
- This option enabled HUR to work as a speaker for your phone. If you disable this option, all the sounds will be outputted on your phone speaker (or if your phone is connected to a Bluetooth device, then they will be played back on that)
My carrier doesn't provide data allowance for Wifi, what can I do?
Wifi data used between phone and tablet is classed as intranet not internet so it won't count against your data usage, but do be careful if you have auto-updates enabled on the device running HUR those updates will be downloaded over the phone's Wifi hotspot and that will incur data costs.
I have audio-sink enabled but phone calls are coming from the phone speaker. Why?
Android Auto is designed to sink all the audio over USB (Wifi) except phone calls where it will ALWAYS use a Bluetooth headset, if none is connected it will just flip the phone to speaker mode.
Are any hardware keys supported?
Volume Up
Volume Down
Media Next
Media Prev
Media Play
Media Stop
Media Rewind
Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
F key - Same as Phone Key
M Key - Mic
H Key - Takes you to home screen
What about intents?
gb.xxy.hr.playpause Same as pressing the Play/Pause media button.
gb.xxy.hr.next Same as pressing the Next media button.
gb.xxy.hr.prev Same as pressing the Prev media button.
gb.xxy.hr.mic Triggers microphone input.
gb.xxy.hr.phone Same as pressing the dial key (answer phone call when ringing, takes you to dialer screen otherwise).
gb.xxy.hr.day Enables day theme.
gb.xxy.hr.night Enables night theme.
gb.xxy.hr.togglenight Switches between day and night theme.
I need more help.
- Feel free to ask a question on this thread, or you can always drop me an email to [email protected]
How do I collect a bug report / logcat
1. Enabling Developer Mode
1. Open Settings > About phone.
2. Scroll down to the Build number.
3. Tap the Build number 7 times in quick succession until "You're now a developer" appears.
4. Return to the Settings menu and select Developer options.
5. At the top of the screen, make sure 'Developer options' is set to On (green).
6. Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
7. Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.
2. Capturing a Bug Report
It's very important to do this right after you experience the issue again, so your device can log at least one occurrence of the issue.
1. Hold the Power button down until the menu appears.
2. Select Take bug report. and wait for the device to capture the bug report.
3. Tap the 'Bug report captured' notification when it appears.
4. Share the bug report. (I recommend to email it to yourself.)
5. Download the bug report to your computer.
6. Send the bug report by email to [email protected]
IF YOU UPGRADED TO ANDROID AUTO 2.X
Dial Pad is broken - Workaround available:
- Open AA -> About -> 3 dot menu -> Developer settings -> Application mode -> change to developer. This will bring back the Dial screen.
Version 3.0 Released
Changelog:
​
- Move USB functions from C to Java
- USB popup numbers limited to 2 and they should remain saved
- App will only start on a phone manufacturer vendor
- App is now running in multi-thread for better performance
- Much enhanced Wifi speed
- Better USB stability
- Should work on RK3188 units as well
- App runs as service so can be run in the background as well
- While running in background supports notification control for media
- While running in background on units running 5.0+ and above you will enjoy Heads-Up notifications for navigation
- Ability to rename the "Headunit" to your own prefered string.
- Fixed Wifi-Direct so can connect over Wifi-Direct as well, but not all devices seems to work
- Moved string to XML so translation to other languages should be implemented in the future
- Fixes some memory leaks
- Supports custom hardware keys
Version 2.5a Released
- Fix for USB close bug in 2.5
Version 2.5 Released - Attention contain BUG
- Left/Right button goes into endless loop
- Added support for ARM64
- Changed car name from Emil to Headunit
- Added mirror output support for HUD display.
Version 2.4 Released
- Improved performance (Wifi should be on par with USB now, even with Audio transport enabled)
- Improved touch sync (no accidental long touches and other strange occasional bugs)
- Option to share the GPS with the phone (reduce battery usage footprint on phone)
- Final fixes for Day/Night calculation and theme switching
- Auto volume adjust fixes (on supported ROM, the volume adjuster is hidden from the user)
- Software decoding works with Audio as well.
Version 2.3 Released
- Improvements and fixes for auto volume adjust
- Improvements and fixes for hardware key input
- Wifi speed improvements (should be able to run smoothly even with transport sound enabled)
- Tweaks for SelfMode (home and recent app button can be used to gracefully exit the app)
And the biggest change:
- Unlimited Browsing support - This is experimental and hacky it's possible that Google will close the loophole at some point but for the time being it works.
Version 2.2 Released - With some major changes
- Fixes for Communication Error 2 received with Play Service 10.X
- New Self mode
- Corrected channels order
- Unlimited browsing working when car is parked (only for Android Auto 1.6)
- Totally changed the Day/Night toggle logic, now the calculations are done inside the headunit app and updated each 10 minutes, so if you're driving all day the sunset/sunrise should be correct. even if you are 500 miles more to the north or west or whatever.
- Added Auto adjust volume option (works for bluetooth audio as well).
- Changed all the key mapping, and using real keys instead of simulated touches:
Supported hardware keys:
Volume Up
Volume Down
Media Next
Media Prev
Media Play
Media Stop
Media Rewind
Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
F key - Same as Phone Key
D key - Changes to Day theme
N Key - Changes to Night theme
M Key - Mic
H Key - Takes you to home screen
The following keys are still usable but they are based on simulated touches:
Up Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
Version 2.0 Released
Changelog:
- Fixed calculated night mode
- Added support for Software decoding (should work now with any device) - If you have problems running HUR, go to settings and enable Software decoding. Do not use software decoding with audio transport, the audio playback will suffer a lot, consider streaming the audio from the phone to a A2DP directly or using a cable to connect the phone Jack to the stereo AUX, or if your phone is rooted you might want to consider Wifi Audio streaming app, it's too much to ask from the Software decoder to do both Audio and Video, unless you have a very strong CPU, but if that is the case I'm pretty confident that the Hardware decoding will work on the device.
- Added option for letterbox display (prevent distortion of stretch)
- Added option to start the app when connected to Wifi
Software Decoding
- Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.
Version 1.5 Released - Key features
- Stable Wifi connection
- Added support for Android 7.0 (Self mode as well)
- Self mode running in stable and usable way
- Connecting USB cable will start app automatically (even if phone is running Android 6.0 or 7.0)
- Supports keyboard shortcuts:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
R = Prev Track (only works in Entertainment tab)
- Uses light sensor (if available) for toggling Day/Night theme.
If you are updating from version older than 1.2 please read:
You won't be able to install it over the old one (Key signature changed!), so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
1) On XDA Labs, click the download Stable
2) When prompted to install select Cancel
3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
4) Locate the newly download APK and copy it somewhere else.
5) Uninstall the old version
6) Install the APK which you just copied.
If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.
App requirements:
- Android 4.1 or higher
- H264 Hardware decoding!
How to use the app: (Please read this steps before asking for help)
1) USB OTG
- Plug in the OTG cable to your tablet, connect your phone, done!
2) Self mode (for AA 2.0) - See Video
- Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
- Exit Android Auto
- Start HUR and select Self
3) Wifi
- From the phone create a Wifi hotspot
- Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
- Connect your tablet to the newly created Wifi hotspot
- Start the Headunit Reloaded app
- HTC ATTENTION! If your phone is a HTC, please change the default IP address to: 192.168.1.1
- Select Wifi
4) Wifi Direct (not supported by all phones/tables)
- Start Headunit Reloaded on the tablet
- Select Wifi Direct
- On the phone go to Settings -> Wifi -> Advanced -> Wifi Direct, join the group. (Do not try to connect as to a normal Wifi it will not work!)
- On the phone start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
Other important notes:
Software Decoding
- Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.
To exit the app
If you are connected with USB, just unplug the USB cable, DO NOT use the exit from the menu. If you are running Wifi, Wifi Direct or Self mode, ALWAYS use the exit button from the left drawer menu!
Audio transport option
Will forward (sink) all the audio from the phone to the tablet if enabled, EXCEPT phone call audio, that will go trough the phone speakers or Bluetooth Handsfree if connected. If you wish to stream all the audio from the phone directly to your A2DP bluetooth, then simply disable the Transport Audio option.
Day/Night toggle
The device running the Headunit Reloaded app will be responsible for changing the theme. You can chose between using the light sensor of the device to toggle between day and night mode, or you can use calculated sunset sunrise mode, or even force it to one theme only. If you have previously installed AA Helper to your phone, please uninstall it!
Auto Start on Wifi
This option will launch HUR whenever you are connected to a Wifi (specific Wifi can be named)
Auto increase volume on speed
The logic behind is a very simple approach, every time the speed increases it will send a vol + key to the phone and every time the speed decrease it will send a vol - to the phone. This requires the device running HUR to have a GPS receiver.
OLD STUFF:
Version 1.3 (Wishlist version) - Released
- Added option for easy car mode toggling. (Car mode can be disabled if not using Self mode - avoid conflict with other Car apps)
- Auto Hide status + action bar while running the app no need to use the Hide option from menu
- App will automatically close when Wifi connection is lost
Version 1.2b - Released
- Buffer overflow protection - Special Thanks to invis-zz from GitHub (https://github.com/invisi-zz) - This should random crashes while using the app.
- Removed Send Log feature (it was classed as backdoor/trojan and Google was blocking the app on playstore)
- Updated OpenSSL library to 1.0.1t (used OpenSSL contained vulnerabilities and Play store blocked the app)
- Managed to get the app on PlayStore (wonder if it will stay...) - https://play.google.com/store/apps/details?id=gb.xxy.hr
Signature Key changed!!!!
I had to update the APK signature key (I'm trying my luck with Play Store), this means if you try to install the new version you won't be able to install it over the old one, so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
1) On XDA Labs, click the download Stable
2) When prompted to install select Cancel
3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
4) Locate the newly download APK and copy it somewhere else.
5) Uninstall the old version
6) Install the APK which you just copied.
If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.
Version 1.1 Stable - Released
Jumping the version number due to significant amount of changes:
Removed Day/Night/Auto mode (see bottom of this post for a better solution.)
Added new setting for 720p Video - Fully working now (even on Wifi)
Changed Self mode start sequence (if the phone is rooted it will start automatically and then go back to HU), if your device is not rooted, please use the following sequence to start Self mode:
Start HU app
Select Self mode
When AA opens select Start Developer Server
Added support for hardware keys (simulating touches), so if your tablet is integrated with the car remote you can control AA from the remote.
Hardware keys as follow:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
R = Prev Track (only works in Entertainment tab)
Some other minor tweaks, to improve stability and make Self mode connect 9 out of 10 times.
Fully integrated x86 native binaries
Declared app as CAR HOME, for those using SelfMode it is crucial, that when you get prompted which should be the default CAR HOME app (Android Auto or HU) you select HU!!! - This is needed to be able to bring back the HU on top after a successful connection is established. AA is trying to override everything..... and to block the user out of his phone as soon as it's connected to the car.
Transport Audio option will affect USB connections as well (You can keep the audio on your phone/bluetooth, when connected with the OTG cable)
Version 1.03b released - Beta
- You will find it in XDA Labs (under the Beta version)
- Fixes Wifi/Self mode for some devices which didn't connect before
- Increased stream buffer size to match the DesktopHeadUnit app (128Kb vs 64Kb)
Version 1.02 release
- Fixed wifi not connecting on some device only after numerous attempts (see explanation below if interested)
The issue looks to be related to the timing, on some occasions and on some devices the phone either sends the SSL data too soon, either too late, either to slow and because the TCP socket is set to non-blocking mode, it can end up in a missed packet in the initial Handshake. I have tweaked this now, so the TCP socket will connect in non-blocking mode, but will switch to blocking mode and wait for full message after a successful connection and once the SSL Handshake is out of the way it will revert back to non-blocking mode, uhhh event reading this makes me dizzy
This however could make the initial startup slightly slower than it was.
- Corrected AutoStart option (Working properly now)
- Fixed USB device overlapping Settings text on the drawer menu
- Added "Send Log" function to be used if there are problems for easier debugging.
Version 1.01 released
- Potential Wifi disconnect fix (see: http://forum.xda-developers.com/showpost.php?p=68078605&postcount=16 for details)
- AutoStart option added to the menu
Very sadly Mike passed away this year and his software stopped working after a Google Update, he left us a slightly outdated GPLv3 version of the software at: https://github.com/mikereidis/headunit which I have used to rebuild (or ty to) rebuild up to his latest build with some additional small modifications as well as fixing the issue caused by Google.
The forked version can be found on: https://github.com/borconi/headunit if anybody is intersted.
Since the app released by him isn't working any longer I have created the new version of it and slightly re-name it just to avoid any confusion.
I take almost no credit in this app, except for some minor changes, and finding the fix for what Google have broke (changed), which was a painful task.
I'm not a developer as such, and this app would never have existed if it wasn't for @mikereidis, however I have spent now several weeks studying the app and understanding how it's working and I plan to continue with the maintenance/development of the app.
I have published the app on XDA Labs under the new name: "Headunit Reloaded Android Auto" and it is now available for purchase. As I have stated previously I'm intending to support all of Mike's customers, so if you have purchased Mike's application before, please email me a proof of purchase to [email protected] and you can have a free copy of the spin-off app.
How to use (Self / Wifi ) ?
1) Self mode.
See instructions in version 1.1
2) Wifi Mode
Start AA on your phone, tap the header 20 times till you become a developer, once that is completed from the menu select Start Head Unit server. Now start tethering on the phone, connect the tablet to the newly created wifi hotspot, start HU on your tablet and select Wifi. This will make the HU app try to connect to the default Android gateway (192.168.43.1), if you need to change this, use the Settings menu from the HU option list. If HU doesn't start on first, do try a few more times, first setup sometimes proves tricky. If this is the first time you connect your phone to the a HU, please make sure you answer all the questions on the phone.
3) Wifi p2p
This is not supported by all devices and might not work for your device, plus sometimes it can be slightly buggy. Start WifiP2p on the tablet from the HU. On the phone go to Wifi Direct (this is usually found in Advanced Wifi settings settings - DON'T TRY TO CONNECT LIKE TO A NORMAL WIFI and look for a new available connection. If you can see one tap to join. Once you joined the network, give it about 30 seconds or so, then open the AA on the phone and start the head unit developer server (same as describe it above). If you're lucky it will work instantly, if not you might need to play around with it.
Other Options:
Possibility to toggle the Audio mirroring when using a Wifi connection. By disabling the Audio mirroring, you will keep all the audio on your phone rather than on the tablet (or on the handsfree) if the phone is connected to the handsfree. This will improve the performance greatly, since audio will use up a significant quantity of Wifi bandwidth when communicating between the 2 device.
USB OTG connection.
Have remained unchanged and it will work same way it did till now, see original threader for details.
I will monitor both Threads and will do my best to help and support everybody.

Well done! Thanks so much for your hard work Emil.

*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.

Syphe said:
*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.
Click to expand...
Click to collapse
What version of Android is your unit running? I haven't heard of any with less than lollipop being able to run this so far, h.264 decoding is absent or poorly implemented.
Edit....see the bottom of this post
http://forum.xda-developers.com/showpost.php?p=68010519&postcount=1449

Wifi Mode - Starting with HUR 7.X
Braking changes with version 7.X
Only for phones running Android 9 or higher, if you still use Android 8 phone, you won't be able to connect over WiFi. Device running HUR, can have any version of Android.
Phone Setup:
Install Wifi Launcher for HUR on the phone ( https://play.google.com/store/apps/details?id=com.borconi.emil.wifilauncherforhur&hl=en_US )
Make sure you give the app all the permissions, including draw over other apps, otherwise it cannot start Android Auto from the background!
Open the app and select the car's BT adaptor from the list (make sure phone is NOT connected to the car's BT, but BT is enabled!)
If you want your phone to create the hotspot, turn on the option to Enable hotspot (this will probably not work if you are on Version in the USA due to carrier limitations!), likewise if you want your car to create the hotspot or you want to use an incar wifi module, leave this option turned off.
Only turn on the legacy option if HUR specifically instruct you so.
Car/Headunit setup:
Connect to the phones hotspot or if you are using an incar WiFi connect to that network. Alternatively if you want HUR to create the hotspot and connect your phone to it, enable the option in HUR settings.
Open HUR
As soon as the 2 devices are on the same network, HUR will fire up on your car screen.

Emil Borconi said:
Hi Syphe.
The core of the app is the same as the original, and the app does require a hardware H264 decoding supported by the OS. Till now we are not aware of any chinese HU which support this. Please contact me by email and I'll refund your purchase.
Click to expand...
Click to collapse
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"

Christopher Price said:
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"
Click to expand...
Click to collapse
Yeah I thought about that myself.... will probably create a small check app in the near future (just need to catch up with all my other work now, which has been pushed behind to get this done)

bugger, thought it was quite promising when everything started to connect itself
I've been building my own app to do simple notification mirroring over a wifi tether, but this would have been much easier haha.

Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!

kevster0522 said:
Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!
Click to expand...
Click to collapse
Hi.
Yeah the XDA labs app can sometimes play funny, if your having any kind of issues feel free to contact me directly be email, on [email protected]

Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later

fmark said:
Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later
Click to expand...
Click to collapse
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..

Emil Borconi said:
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..
Click to expand...
Click to collapse
Yes, my phone has 4G connection while tethering.
Lets try the debug output. Could you please send me the .apk with debug messaging? I'm curious to see what is going on when it fails to connect.
Thank you!

Im interested too because isnt working on my s4 and nexus7 2012

wpostma said:
Im interested too because isnt working on my s4 and nexus7 2012
Click to expand...
Click to collapse
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?

Christopher Price said:
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?
Click to expand...
Click to collapse
It might be about the Wifi connection, I had some connectivity issues over Wifi myself the last day, but they were fully random, at a first look they point to the TCP socket.... I'm investigating this.
I got some Wifi disconnected myself but it is very random, it can occur after 1-2 minutes or after 3-4 hours... so testing potential FIX for the issue isn't going to be easily. At the first investigation it looks to be something related with the pooling/keeping connection alive. I have tweaked this and made a new build, currently running for about 20 mins and looks OK, but as said the disconnect can occur randomly at any point.
The worst part is that the logs do not give any hint on what could be the cause of this, neither on the HU part, neither on the AA side, they only mention a broken PIPE bu no hint on what can be the cause...

I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?

Christopher Price said:
I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?
Click to expand...
Click to collapse
setting socket to keppalive looks to sort the problem, I'm trying to figure out failing handshake at the moment. On TCP sometimes the handshake fails, trying a few more times passes..., handshake over usb always passes....
Looking at the code and notes Mike seems to struggle with it as well in the past...

When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?

skitty said:
When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?
Click to expand...
Click to collapse
Emil Helped me with this problem. You don't actually connect through your wifi networks menu, use Wi-Fi Direct instead. Found here: wifi networks menu > 3-dot menu > Advanced > Wi-Fi Direct

[APP][5.0+]AndroidAuto carNotifier (Multi-language and Email support)

Beta 1.0 released
I will like to start saying a very big thank you to @bggold who asked me to consider this in the first place
While there isn't any way to use the nice Google Assistant voice, and it's still rough around the edges, this demonstrates how we can use Android Auto in a multi-lingual environment as well as how to read out and reply emails.
The concept is very simple, instead of relaying on Android Auto to read out the notifications I have created a small app which mimics that behaviour, with some extras:
1) It try to do a language detection for each test, and use the appropriate TextToSpeech
2) It allows the user to select which app notification does he/she want's to read
3) If the content is really long (like a lengthy email) the app will prompt the user if it want's to go ahead with the message readout or not
4) If notification supports quick-reply the app will prompt the user for a reply (in the same language as the the original message)
Planning to support a lot of languages but there I will need user input, I have translated the basic strings to around 70 languages using Google translator, but I can tell it's not quite right (I can see with the languages I do speak)
Best part, app won't be affected by 3rd party restriction at all and it won't require root either, however I'm pretty sure Google will not allow it on the PlayStore
Beta version available now on XDA Labs.
App will be payable, however current beta is free so grab a copy while you can
To use the app you will need to enable unknown sources in Android Auto, simply open Android Auto, go to About, tap the "About Android Auto" header 10 times till you become a developer, then from the 3 dotted right menu select developer options and enable "Unknown sources"

Emil Borconi said:
Beta 1.0 released
I will like to start saying a very big thank you to @bggold who asked me to consider this in the first place
While there isn't any way to use the nice Google Assistant voice, and it's still rough around the edges, this demonstrates how we can use Android Auto in a multi-lingual environment as well as how to read out and reply emails.
The concept is very simple, instead of relaying on Android Auto to read out the notifications I have created a small app which mimics that behaviour, with some extras:
1) It try to do a language detection for each test, and use the appropriate TextToSpeech
2) It allows the user to select which app notification does he/she want's to read
3) If the content is really long (like a lengthy email) the app will prompt the user if it want's to go ahead with the message readout or not
4) If notification supports quick-reply the app will prompt the user for a reply (in the same language as the the original message)
Planning to support a lot of languages but there I will need user input, I have translated the basic strings to around 70 languages using Google translator, but I can tell it's not quite right (I can see with the languages I do speak)
Best part, app won't be affected by 3rd party restriction at all and it won't require root either, however I'm pretty sure Google will not allow it on the PlayStore
Beta version available now on XDA Labs.
App will be payable, however current beta is free so grab a copy while you can
To use the app you will need to enable unknown sources in Android Auto, simply open Android Auto, go to About, tap the "About Android Auto" header 10 times till you become a developer, then from the 3 dotted right menu select developer options and enable "Unknown sources"
Click to expand...
Click to collapse
Thanks for making this app!
After first start it asked for notification permission and then it was gone to build the list of installed apps/services - endless...
So I've forced close the app after minutes, went to app info/permissions, and enabled unselected permissions for it.
After that the app works now, as it should!
I'll test the functionality today while using AA in my car.
Regards bitstra

bitstra said:
Thanks for making this app!
After first start it asked for notification permission and then it was gone to build the list of installed apps/services - endless...
So I've forced close the app after minutes, went to app info/permissions, and enabled unselected permissions for it.
After that the app works now, as it should!
I'll test the functionality today while using AA in my car.
Regards bitstra
Click to expand...
Click to collapse
Thanks. It was 3 am )) updating the app now.

This is exactly what I needed. Unfortunately I couldn't get it to work. Using Samsung S9 plus running Oreo. Gave read permission to the app, enabled developer settings on Android Auto, enabled unknown sources, enabled whatsapp and Gmail.
Whatsapp notifications haven't changed and it continues to read the foreign text in English. Gmail notifications don't pop up at all.
Any suggestions?

yavuzyay said:
This is exactly what I needed. Unfortunately I couldn't get it to work. Using Samsung S9 plus running Oreo. Gave read permission to the app, enabled developer settings on Android Auto, enabled unknown sources, enabled whatsapp and Gmail.
Whatsapp notifications haven't changed and it continues to read the foreign text in English. Gmail notifications don't pop up at all.
Any suggestions?
Click to expand...
Click to collapse
Not sure if you saw but there is a new release. It fixes this issue. Just remember to reboot after updating.

Unfortunately I have the same problem as @yavuzyay. I'm using a Samsung Galaxy S6 edge with Android 7.0 and Carnotifier Beta v3.

Thanks to @yavuzyay for bugreport and Turkish language input.
I have identified the problem where the app was crashing in case you where using AA on the phone only, and this has been now fixed.
@CeldeSuS - Are you phone only or are you using AA on the car? If phone only, download the new beta 1.4

Emil Borconi said:
@CeldeSuS - Are you phone only or are you using AA on the car? If phone only, download the new beta 1.4
Click to expand...
Click to collapse
I'm using AA on the car (Alpine X802D-U head unit). I'll try the new beta anyway and report back.

Awesome. Works perfectly.

V4 work fine with SM960F(android 8.0) & RLink1 !
Great job!

Very good stuff!
I use it with the now playing feature - basically phone picks up music on the radio,.detects the song and artist and throws a notification. This app picks that up and shows it as a notification on the car screen! I have disabled read out. So it stays as a simple notification.
Quick question - haven't been able to try it - if I set zero seconds as the duration, will it leave the notification forever?

Tested but not working as expected. Line is an application which doesn't support Android Auto.
Positive: Yes, Car Notifier shows there is a message on Line.
Negative: Can't do anything, it won't read the message, the notification stays in grey color and nothing happens when I click on the message.
Cheers
Tom

tom1807 said:
Tested but not working as expected. Line is an application which doesn't support Android Auto.
Positive: Yes, Car Notifier shows there is a message on Line.
Negative: Can't do anything, it won't read the message, the notification stays in grey color and nothing happens when I click on the message.
Cheers
Tom
Click to expand...
Click to collapse
You can't click the notification to have it read at this time. If you want them read to you enable the read option.

"Read out notifications" is enabled in the settings, my Honda headunit is hacked and I have root access, so I don't think this is related to that.
Cheers
Tom

tom1807 said:
"Read out notifications" is enabled in the settings, my Honda headunit is hacked and I have root access, so I don't think this is related to that.
Cheers
Tom
Click to expand...
Click to collapse
I'm sure you have but have you checked all the permissions?

CarNotifier asks only permissions to Microphone and Phone, both are granted.
Wondering now whether it has something to do with the new Android Auto v3.8.584554 where some on Reddit claim, that notification is broken
Cheers
Tom
Edit: Maybe the the new AA version interferes with CarNotifier, because AA can show now also message preview
More edit: My friend tested on the Samsung S7 (I have a OnePlus 3T). Also on his mobile nothing happens with Line.
Can't read out and nothing happens in AA when click on it

Is there an app for Speed cams like in your obd2aa app, to have only the speed cam notification?

tom1807 said:
CarNotifier asks only permissions to Microphone and Phone, both are granted.
Wondering now whether it has something to do with the new Android Auto v3.8.584554 where some on Reddit claim, that notification is broken
Cheers
Tom
Edit: Maybe the the new AA version interferes with CarNotifier, because AA can show now also message preview
More edit: My friend tested on the Samsung S7 (I have a OnePlus 3T). Also on his mobile nothing happens with Line.
Can't read out and nothing happens in AA when click on it
Click to expand...
Click to collapse
I am running the new aa and it is working. Get Emil a bug report right after it happens.
The only thing you can do at this time is swip away the notifications. Clicking them will not do anything.
Thanks

After more testing, I do believe the culprit is Line. Gmail works as expected, Facebook also (just for test).
However, Line refuses, which is actually the reason to install the program in the first place.
Probably one of the few programs which won't work.
Great program though.
Cheers
Tom

Hi guys.
I'm finally back in the UK and in front of my PC, I've also managed to tied up quiet a few of my loose ends and I have no big project starting this year. I will dedicated the last 2 weeks of this years to the following:
1) Looking into fixing some of the FC for obd2aa, also try to find a solution for non-standard PIDs
2) Get AA GateWay to Beta/Stable version (most work needs to be done on this app)
3) Fix some issues and FC with HUR (including Waze sound cut off).
4) Get the carNotifier to a stable version.
January and February are again fully booked so I will focus on stability rather then adding new features especially because obd2aa and HUR and fairly mature apps with most of the functions already covered.
For some reason I'm not really getting any notifications from XDA and being a lot on the road I don't visit the site too often lately, therefore I will kindly ask you if you need support, please email me directly to [email protected].

Android Auto alternative

Hi,
I'm disappointed with AA. I think there is some space for an open source alternative to this system which is so closed.
Moreover the end of life of the standalone version makes me feel that Google doesn't care much about their customer experience.
I tried the Google Assistant driving mode and it's... a disaster for now.
I think it would be easy to create a great AA like launcher. But to make it succesfull there must be a community and an ecosystem around that. Apps are important even in automotive context.
Typically Waze is a key app that many drivers want.
At this time I'm wondering what is the best approach to start this kind of project. I see few show stoppers and I'm interested to get some thought from you about that.
1/ Head unit integration : long time ago I worked on the reverse engineering of the AA protocol. I discovered that the protocol is using SSL certificates. Head units holds a public key and mobile use a private key provided by Google Play Services. The problem is that these certificates have very short lifetime (about 6 months) and if I remember fine the root cerificate will expire in 2030 or something. I don't think that head unit s check the expiration date anyway (because many of them don't have system time). But for sure you need a Google private key in order to initiate communication with a head unit. The key could be captured decompiling code few years ago, don't know if it's still as simple as that.
If head unit really don't check the expiration date then it could be possible to replace the whole AA stack with an independent one.
But even if this work I'm not sure it's possible to disable the native AA protocol and take control of the USB port without rooting.
2/ Apps integration. There are 2 categories of Automotive apps : media apps and navigation apps. I think there are also a category for messaging apps.
Navigations apps are apps that provides an automotive friendly display. Waze does this for example.
Media apps are easy to integrate becaase they rely on the legacy mediabrowser APIs.
Integrating the navigation apps is tough. Because these apps are exposing a special AA service that only privileged apps can invoke (by default).
However apps dev can also allow a third party app to connect their dispkay service. This won't ever happen except if the car launcher become mainstream.
Good point is that would not require any change in implementations : it's just an access right problem.
I have seen a lot of car launchers in Play store. They all display the apps on native mode which is not what you want while driving.
Any comments to this ?

I would also like to see an alternative way...but unfortunately I did not find anything yet.
I'm also not happy with everything on Android Auto.
For example:
- I have apps (e.g. navigation) that are not compatible with Android Auto
- I can't accept Whatsapp calls on Android Auto
- The navgation of media apps is not the best way (if you want to change the playlists, there are way too many inputs necessary)
- I can't turn off Google Maps (GPS) to preserve battery and reduce heat on the phone
- I need internet (I live in a rural area...therefore sometimes I don't have internet and then in a lot of times, Android Auto just crashes...)
- I don't like Google's update policy (it's just good luck if a new version of Android Auto works stable). I want to have a working version and leave it on the phone.

From a user standpoint I definately would like to see an AA alternative. I don't need to watch videos or anything like that but there are a few necessary apps for me that AA doesn't allow.

SOFO888 said:
- I don't like Google's update policy (it's just good luck if a new version of Android Auto works stable). I want to have a working version and leave it on the phone.
Click to expand...
Click to collapse
You can achieve that by disabling Android Auto automatic updates on Play Store app.

CaioTheBrain said:
You can achieve that by disabling Android Auto automatic updates on Play Store app.
Click to expand...
Click to collapse
No, unfortunately not. Every Google app has an expiration date, also Android Auto. This expiration date then forces you to update your app. Otherwise it will not start.

There are a few Android dongles that trick the car's headunit into thinking it is connected via Android Auto. However, most of the devices are CarPlay AI units that trick the headunit into thinking is is connected to a CarPlay device and then display the Android system through the headunit. But they are all buggy.
Perhaps something can be learned from how they do that. An app that mimics Android Auto but allows full user control would be great.

I am by no means an expert but I want to help do this! I liked using rooted devices for AA and having AA tweaker but I always felt like it was just the start of something not a finished product so I'm definitely down with this. What I feel like would be the simplest approach would be making an Android auto app that (it communicates with your phone and doesn't need data) runs on a cheap tablet that you put on your dash or wherever in the car and from there you have full control over the app and device. Just my thoughts

Did someone tried sreen2auto? Its mirroring your phone to your android auto. Search it on XDA forum.

drnightshadow said:
Did someone tried sreen2auto? Its mirroring your phone to your android auto. Search it on XDA forum.
Click to expand...
Click to collapse
I used to use Screen2Auto but it required too much upkeep every time Google made changes to Android Auto. The last time it broke I couldn't get it working again.

Question bluetooth metadata and controls not available

I have a 2012 Toyota Highlander, coming from a Galaxy S10+ where the metadata and controls came through to the stereo. I recently upgraded to the Pixel 7 and had a hard enough time just getting bluetooth to connect to the car. Now I can play through the stereo just fine, but can't control the music nor see metadata. This was working perfectly on the S10+. My screen doesn't even populate with the areas where Title/Artist/Album etc should be, it just shows a play and pause button (which actually work). I've tried multiple apps (spotify, Youtube, podcast app), no metadata. I've tried all versions of AVRCP and MAP on the phone, rebooted and reconnected, still no metadata. I have Bluetooth Volume Manager installed, though I don't see how that would affect anything.
I know many people are having this issue, but is there no resolution other than "it works for me"?

Have you tried to use Android Auto for your connection to your car. It certainly works using a USB cable connection between my car and my Pixel 7. I play all of my music from my phone and also from the radio while driving using the app.

Tailwind14 said:
Have you tried to use Android Auto for your connection to your car. It certainly works using a USB cable connection between my car and my Pixel 7. I play all of my music from my phone and also from the radio while driving using the app.
Click to expand...
Click to collapse
I can't even get Android Auto to run. It's updated in the Play Store, but no way to run it!

Have you done the setup process to link your car with the Android Auto app? I don't have a Toyota; so things may be different on you vehicle. However, when I was setting up my Android Auto; I had to go into the car's menu to set the proper access. You might check your car's Manuel regarding WiFi, Bluetooth, etc. connection authorizations. See if that helps.

Does your Toyota require the "Toyota Entune" app to sync your phone with the car?

poit said:
Does your Toyota require the "Toyota Entune" app to sync your phone with the car?
Click to expand...
Click to collapse
It never has for the many phones I've used with the car before, all Android.
Tailwind14 said:
Have you done the setup process to link your car with the Android Auto app? I don't have a Toyota; so things may be different on you vehicle. However, when I was setting up my Android Auto; I had to go into the car's menu to set the proper access. You might check your car's Manuel regarding WiFi, Bluetooth, etc. connection authorizations. See if that helps.
Click to expand...
Click to collapse
I don't know what setup process there is, but my Toyota is almost 11 years old, from before AA was released. The manual isn't terribly helpful much like the stereo settings. I had A Galaxy S5, LG V30, and a Galaxy S10+, all worked no issues with the stereo. I feel like the NVRCP isn't working properly.

Any more suggestions? Is there an app that can send the correct NVRCP stream to the car? Or something where I can test to see if it's working?

ldeveraux said:
Any more suggestions? Is there an app that can send the correct NVRCP stream to the car? Or something where I can test to see if it's working?
Click to expand...
Click to collapse
Can you, Have you opened Android Auto on you cellphone? If yes, you must sync you phone with the car's Bluetooth or by USB cable. If you car is visible, set the sync to you car. If no, I've got nothing else.

Tailwind14 said:
Can you, Have you opened Android Auto on you cellphone? If yes, you must sync you phone with the car's Bluetooth or by USB cable. If you car is visible, set the sync to you car. If no, I've got nothing else.
Click to expand...
Click to collapse
Again, I can't open Auto directly on my phone, it doesn't have an icon. I can find it in the apps list and the Play Store, but can't run it alone.

One last shot.
On you phone; go to the play store.
Click on you image in the upper right of the screen. That should take you to your Google Apps management screen.
Click on Manage apps & device. At the top of the screen you should have two choices "Overview" and "Manage". Click on "Manage".
Click on "installed". That should bring up a full list of all the apps that are installed on your phone; including Android Auto.
Click on Android Auto. That will open your Android Auto app.
Click on "What's New". Will give you a lot to read about both what's new but a lot of links including one to a list of compatible cars.
Follow the instructions and you should be able to find your car if it is compatible.
During this search you will also come across a page with "how to use android auto.
You might want to do some more searching on your own thru those pages as well.
I'm finished now.

Tailwind14 said:
One last shot.
On you phone; go to the play store.
Click on you image in the upper right of the screen. That should take you to your Google Apps management screen.
Click on Manage apps & device. At the top of the screen you should have two choices "Overview" and "Manage". Click on "Manage".
Click on "installed". That should bring up a full list of all the apps that are installed on your phone; including Android Auto.
Click on Android Auto. That will open your Android Auto app.
Click on "What's New". Will give you a lot to read about both what's new but a lot of links including one to a list of compatible cars.
Follow the instructions and you should be able to find your car if it is compatible.
During this search you will also come across a page with "how to use android auto.
You might want to do some more searching on your own thru those pages as well.
I'm finished now.
Click to expand...
Click to collapse
So the problem with trying this is it doesn't open. It is installed, but when I click on AA in step 4 above, it just takes me to the page in the store where I can uninstall/install updates to the app. I can't actually run it. I'm not in the beta either. WTF

Have you tried clearing Android Auto's data? Pixel Settings, Apps, See all apps, Android Auto, Storage & cache, Clear Storage.

ldeveraux said:
Again, I can't open Auto directly on my phone, it doesn't have an icon. I can find it in the apps list and the Play Store, but can't run it alone.
Click to expand...
Click to collapse
You can open Android Auto if you head to the Settings menu and search Android Auto. It will pop as the first result. From there you can connect with your car using a USB cable, or if you want the Wireless, you have to head all the way down to the About section and click on Version like 7 or 9 times until the developer menu pops (accessible through the 3 dots menu on the right top corner)

dexlemaffo said:
You can open Android Auto if you head to the Settings menu and search Android Auto. It will pop as the first result. From there you can connect with your car using a USB cable, or if you want the Wireless, you have to head all the way down to the About section and click on Version like 7 or 9 times until the developer menu pops (accessible through the 3 dots menu on the right top corner)
Click to expand...
Click to collapse
I can get into the Android Auto settings, but can't actually launch it. WTF?! Should I uninstall it completely though something like Titanium Backup then install from the store?