Hi, I have an Xtrons PA78DLRIPL PX30 unit with android 8.1 and have a problem with sound from Copilot navigation app. There is no sound whatsoever when using this app, including key touch sounds and start up message. It's not related to the voice chosen for navigation as I've tried multiple voices and languages.
I have tried all settings for sound in the app but nothing works.
I have tried those settings I have found in system settings but nothing changes.
Other navigation apps work ok, Waze, TomTom, Google maps.
Unit is completely standard as I haven't plucked up courage to try rooting and installing other time.
Does anyone have any suggestions?
Related
Hey guys. I've recently started using Navmii on my MTCD device, its the only Navigation app that works well enough to be used as a daily driver (excuse the pun!). Anyway the issue I'm having is that if i have the radio or poweramp playing in the background, the Navigation Voice prompts are difficult to hear over the music. The easiest thing to to, obviously is to stop the media apps completely, however in the real world you would normaly want some music on in the background?
Ideally, the radio/poweramp volume would dip automatically when the Nav app starts a voice prompt, however in reality i know thats probably not possible. What I have managed to achieve so far is to set power amps voulme lower via its built in volume control, this way the Navigaton prompts are always louder, this works really well. However I cant see a way of doing this for the radio app, I am assuming that this is something to with the way the radio is managed via the MCU interface, and not directly via android.
Im wondering how other people manage this scenario, I cant be the only one?!
There is an option in the settings menu (GPS submenu) that lets you do precisely that.
it cant post a link but search youtube:
Android head unit 5.1.1 low GPS voice fix
i posted a fix for this issue
I have a Seicane px5 headunit for my Accord. I've been able to fix a various number of features that were lacking when I first installed the unit, including Google text to speech for the navigation.
While I'm super happy I was able to get Google tts to work with my navigation apps, specifically Here WeGo, I noticed my music, which is played over a2dp from my phone, doesn't mix with the navigation instructions. The voice nav starts but it doesn't play over my music in the background, just stops it momentarily while giving directions, if that makes sense.
I tried changing the sound settings from Switch to Mixing, but no changes.
I searched the forums here for a possible and it seems others have the exact "problem" I want to have lol.
Any guidance would be appreciated? Thank you.
Sent from my LM-V350 using Tapatalk
I have a PX6 6/64 GB head unit and using wired Android Auto with the Z-link app. It works fine, except the Google Assistant / Maps voice has very high volume and distorted sound compared to music. Which makes it impossible to use Google Maps and Spotify at the same time, in Android Auto mode. I have the same problem running stock or HAL9K ROM. Is it possible to adjust the voice volume in any way?
Apple CarPlay works good and has much better volumes and sound quality.
Thanks for any help!
You haven't mentioned what steps you have taken to try to self resolve the problem, which usually ends up in a circular guessing game.
Have you considered lowering the system volume in factory settings?
marchnz said:
You haven't mentioned what steps you have taken to try to self resolve the problem, which usually ends up in a circular guessing game.
Have you considered lowering the system volume in factory settings?
Click to expand...
Click to collapse
Thanks, well I have tried rebooting phone and head unit, regarding volume I only have one setting in my head unit, which seems to control everything.
After some more testing I have now realized that the problem is not really that the Google Assistant voice is too high. The problem is that when the voice starts it will lower the music but when the voice is finished it will not turn the music volume back to normal. So when I increase the music volume back to normal, next time the voice will be really high. Anybody else with this bug and a possible solution?
Earlier it was possibIe, but now I cant skip tracks in Spotify with my steering wheel control or buttons on radio, when I use sygic navigation app. If I go out of Sygic I can skip tracks again and in other apps it is also possibIe.
Do someone know how I can find a solution for this? I think somehow the sygic app is overlaying other apps so this causes the problem.
In realls old versions of Sygic it was also possibIe fyi.
Has anyone found a solution (apart from the FCC media buttons remapping) to use steering wheel keys with poweramp while using Sygic? Since Sygic version 18.4.2 steering wheel keys no longer work with poweramp (or any other player which is identifying bluetooth or headset keys?) while sygic is running on full screen.
I was able to fix this using Automate, at least for Spotify.
I created a "Key Pressed" item listening to "Media Next", then a "Is foreground app" item listening for Sygic, and a "Audio player control" item with command "Next" for Spotify.
The "is foreground app" item is kinda of unecessary as it works without it as well, both with Sygic running or not, but it think its worthy to prevent any double events or weird behaviour when Sygic isn't running.
On my dasaita px5 unit i had the same problem with sygic and poweramp. Next and Previous track not working. The same problem was reproducible on my tablet using a media keyboard. No response to media keys. Initially started out with automate but due to recent update of sygic i have been browseing through its settings; settings->bluetooth->play via bluetooth to On. This solved the problem for me. Some experimental function according to sygic. Before changing this setting i also noticed a drop in volume when PA was playing and Sygic was started. After changing this setting, no volume drop and expected response to media keys. Applied same change to the car unit and voila...all seems to work well now. No Tasker or Automate needed (but it was a nice opertunity to try automate)