not seeing this being discussed here on xda but I know I'm not alone in experiencing this problem
Basically once connected to car unit, opening up google maps or waze will lead to a freeze
display still shows Maps, and seemingly everything is working in the background but the image stays frozen
typically I need to tap the multitask button, then jump back into the app running Android Auto for everything start moving again
running this on the Galaxy S20
car unit is a Rockchip PX6 tablet as far as I can tell
App that hosts Android Auto is Zjinnovate Zlink (something like that)
works flawlessly with CarPlay.. just not so much AA + Gmaps and Waze
tried: adjusting resolution in dev options
toggling wireless projection
ideas anyone?
I have the same problem ?
use Headunit Reloaded for Android Auto on px6, much better thank anything else, and even works with wireless AA
matrixx1 said:
use Headunit Reloaded for Android Auto on px6, much better thank anything else, and even works with wireless AA
Click to expand...
Click to collapse
will look into that, thank you
yellowchilli said:
not seeing this being discussed here on xda but I know I'm not alone in experiencing this problem
Basically once connected to car unit, opening up google maps or waze will lead to a freeze
display still shows Maps, and seemingly everything is working in the background but the image stays frozen
typically I need to tap the multitask button, then jump back into the app running Android Auto for everything start moving again
running this on the Galaxy S20
car unit is a Rockchip PX6 tablet as far as I can tell
App that hosts Android Auto is Zjinnovate Zlink (something like that)
works flawlessly with CarPlay.. just not so much AA + Gmaps and Waze
tried: adjusting resolution in dev options
toggling wireless projection
ideas anyone?
Click to expand...
Click to collapse
additional info - freeze only happens when music is playing
playing either from Spotify or YouTube Music has the same effect on either GMaps or Waze
Related
5.1 did not fix the bluetooth issues I had...it actually added another bug.
New with 5.1:
-When playing music with Google Play Music, whenever I switch tracks, the screen turns on. Why?
Still a problem after 5.1:
-Sometimes Bluetooth plays but without sound - it takes some weird opening/closing/pausing/starting maneuvering to hopefully get it working
-Pause during notifications does not work properly - I've tried this with Google Maps and a few different podcast apps. With Google Maps Navigation on and a podcast playing...when Google Maps wants to talk, it pauses the podcast (as the setting says) but the Google Maps notification is muted. It's just silence until it is done and then the podcast resumes.
Is anyone else having these sort of issues?
Nexus 6, 5.1D, stock, rooted ,twrp, with my 2013 Cadillac ATS
Yes it is happening to others myself included. why? I have no idea. But you are certainly not alone.
Sent from my Google N6 on VZ
I just posted this in the General section ....
OTA'd the 5.1 update on 3/26/15.
Since then, contact addresses fail to appear on vehicle displays over Bluetooth.
Rebooted phone / Forgot and paired phone to vehicle, no fix.
Phone is paired to 2 vehicles with the same results.
Can anyone confirm this?
Having the same issue. If you disable ambient display, the screen will stay off when selecting tracks with Bluetooth. My issue with Bluetooth is that every few days I have to reboot the phone to get the BT to work. I can't even toggle Bluetooth. When I do, it says Bluetooth turning off, it toggles back on by itself. Tried force closing all running apps but dosent help.
Bluetooth...
jeffreii said:
5.1 did not fix the bluetooth issues I had...it actually added another bug.
New with 5.1:
-When playing music with Google Play Music, whenever I switch tracks, the screen turns on. Why?
Still a problem after 5.1:
-Sometimes Bluetooth plays but without sound - it takes some weird opening/closing/pausing/starting maneuvering to hopefully get it working
-Pause during notifications does not work properly - I've tried this with Google Maps and a few different podcast apps. With Google Maps Navigation on and a podcast playing...when Google Maps wants to talk, it pauses the podcast (as the setting says) but the Google Maps notification is muted. It's just silence until it is done and then the podcast resumes.
Is anyone else having these sort of issues?
Nexus 6, 5.1D, stock, rooted ,twrp, with my 2013 Cadillac ATS
Click to expand...
Click to collapse
When it comes to bluetooth problems, especially with cars and this phone you will find very few helpful answers. Sad but true, not many Nexus 6 people seem to use hands free automobile applications on their device. I had to buy a new head unit for my car along with all the other bullcrap to make it look nice in my car to get some of these puzzling problems to disappear. Android Auto works great if you have the supporting gear in your car and follow the instructions about how to pair phone with car and use the right USB port and wire in your Nexus. After that, everything works as expected. Unfortunately you do have to spend some cash and time to do this but it is the future and if you plan and use your phone in car more than anywhere else, it is worth the investment and will improve with time. The only good take away from all this is, so far only nexus devices running lollipop work with Android Auto supporting head units.
vvveith said:
When it comes to bluetooth problems, especially with cars and this phone you will find very few helpful answers. Sad but true, not many Nexus 6 people seem to use hands free automobile applications on their device. I had to buy a new head unit for my car along with all the other bullcrap to make it look nice in my car to get some of these puzzling problems to disappear. Android Auto works great if you have the supporting gear in your car and follow the instructions about how to pair phone with car and use the right USB port and wire in your Nexus. After that, everything works as expected. Unfortunately you do have to spend some cash and time to do this but it is the future and if you plan and use your phone in car more than anywhere else, it is worth the investment and will improve with time. The only good take away from all this is, so far only nexus devices running lollipop work with Android Auto supporting head units.
Click to expand...
Click to collapse
It wasn't perfect, but my Bluetooth was just fine pre 5.1...I can deal with the quirks and avoid spending $$ on Android Auto (for now at least)...but these major bugs need to be fixed ASAP.
Do we know if this is fixed?
Is this fixed in 5.1.1? Is there an issue logged with google? Anyone?
I have my nexus 6 rooted with 5.1.1 stock and the bluetooth doesn't work. I cannot see any device but the other devices can see it.
I have tried to fix it clearing cache and data (only bluetooth) but the problem is still there.
Do you have any idea guys?
This morning I remembered my experiments with my old gt-9100 and I have decided to do wipe cache and wipe dalvik-cache.
And now... bluetooth is alive!!!
[emoji39]
Is there a way to run my Spotify or Waze on it? I have the hacked spotify installed on my rooted Galaxy S7 Edge..
Thanks
Spotify is already compatible with Android Auto. If it's on your phone, it will show up as an audio option in Android Auto.
Waze is coming (soon I hope).
I assume you are referring to Android Auto, and not your radio itself.
ScottBroker said:
Is there a way to run my Spotify or Waze on it? I have the hacked spotify installed on my rooted Galaxy S7 Edge..
Thanks
Click to expand...
Click to collapse
cz9h3d said:
Spotify is already compatible with Android Auto. If it's on your phone, it will show up as an audio option in Android Auto.
Waze is coming (soon I hope).
I assume you are referring to Android Auto, and not your radio itself.
Click to expand...
Click to collapse
I was referring to the radio. Pandora and Google maps show up on the radio. And , in theory, my phone is locked when I plug the usb in and I cannot use any function on it that is not on the radio....
LOL - okay - I'm going to regurgitate a lot. If you're a super user, excuse me telling you stuff you already know...
-The IO6 radio is standard on the Malibu premier, which includes navigation. This is not Google Maps, it has fully self-contained maps (and are they on the SD card for 2016, I think?).
-Your radio also has the Pandora app built in, so if you have Pandora installed on your phone, and the phone connected via bluetooth, the app will leverage your phone and play Pandora.
Are you currently using Android Auto? I would highly recommend playing around with it if you haven't, I find it immensely useful.
-Depending on when your vehicle was built, you may or may not have Android Auto compatibility. If you don't, your dealer will do a free reflash of your radio to get it. Follow the next two steps to see if you do.
-Your phone has to at least have Android 6.0 and have the Android Auto app installed. Just go to the Google Play store, search for Android Auto. If you can see/download it, then your phone is recent enough.
-When you now plug your phone in (must use the USB cable for AA), the "Projection" icon will change to Android Auto on your Malibu's screen, and you can launch AA.
Note: I had issues when connecting some phones for the first time for AA - had to actually change the connection from USB Charging to MTP - by pulling down the notifications and manually changing this - I think (hope) this isn't required in most cases, now.
What's great about Android Auto?
-Google Maps: the real-time traffic for this is awesome. It will be much much more useful than your XM Traffic on your factory navigation.
-Lots of music choices, including Spotify. Also Audible, Podcasts, etc.
-Messaging - you can have your incoming texts/etc, read aloud, and respond back with your voice.
Of course all of this does use your phone's data (or you can leverage your free 3GB of 4GLTE if you haven't used it yet, by connecting your phone to your car's network).
Disclaimer - I work for GM.
Hope this helps...
I have a 2016 Malibu Hybrid. I start waze before I plug in the phone then proceed to use AA.
In Android Auto, When I'm listening some music from my phone and having G. Maps on the screen, there's always some lags in music when the map's moving (like in an higwith exit road)
I have a rooted Pixel 3 and a Mazda 3 2018 (Android Auto from MZD AIO)
I've seen in developper's options many options about bluetooth, what should be the best parameters?
Thanks!
I see the same thing when using my Chinese dongle on my android head unit. I've played around with developer settings in Android auto and the settings on the dongle and nothing seemed to help. It seems to be something low level in the dongle (in your case the head unit or mod app) that causes this where moving the map seems to overwhelm to the system.
Using the same headunit and phone but instead using Emils' head unit reloaded application I do not get any sound issues, even when running in 720p mode.
It seems like the issue we're seeing is more to do with the Android auto implementation in hardware/software.
Ok, I'll try it and see how it's going. Thanks
I've read on some forums that Android Auto does not support swiping and multitouch. I have Android Auto working on my headunit with a carplay / AA dongle, and it will only let me interact with it by using the arrow buttons at the top and bottom of the scroll bars, as well as using the + / - to interact with maps. Basicaly prodding the screen is the only way to do anything. Any sort of more "advanced" gesture like a swipe doesn't work.
Is this regular behaviour for Android Auto? I had a hire car last month that had AA and I could swipe and pinch to zoom on maps without any issue.
I'm wondering at the moment if this is the carplay dongle and whether headunit reloaded would offer a better experience.
Thanks for your advice.
So, to answer my own question and for anyone that may have similar issues, head unit reloaded on my unknown Chinese branded android car stereo works as expected. In fact it works great. Multitouch, swipe etc, all working.
Must be my carplay dongle that doesn't work correctly with android auto, though it was good for carplay.
I have a separate Samsung S10 phone for Android Auto use only in my car (Mercedes EQC). The Android Auto phone is used for Google Maps, media control (controlling a Pi with a 2 TB SSD and a music library of around 200 000 tracks hidden in the center console - I don't use streaming at all, both for privacy reasons and because a lot of my underground extreme metal is not on any streaming services). The problem is that the car puts that phone as the first phone in the list, and sometimes it doesn't even connect by BT to my phone and my wife's phone. Can I block Android Auto from using the phone part of it, or make it think that the S10 is a tablet, so I avoid this problem? I have tried to turn off the phone radio (flight mode, and then only activate wifi, which I use to connect to the Pi), but that doesn't help.
Did you check in Android Auto Settings if "keep Bluetooth on" is on?
Yeah, that one was off, but t seems that AA doesn't obey it. But it got me thinking, and I remembered that I had this working the last time I was messing around with AA. I finally found it in AA Tweaker, a tweak named "connect automatically to bluetooth" or something like that. Finally I got it working! Thanks for jogging my memory!