Google Play music issue with Android auto - Samsung Galaxy S8+ Questions & Answers

Since one week I am not able to play Google Play Music anymore through Android Auto. It says service isn't available at the moment. All other functions work. Has anybody the same issue? I have a 2017 Jetta and a Galaxy S8+ with latest T-Mobile updates.
Thanks

This is a related issue.
Here is a link http://www.androidpolice.com/2017/06/12/not-just-google-play-music-isnt-behaving-android-auto/

Mine was doing this last week too, started playing music on my phone before connecting it to the car and it has been fine since.
Not sure what is causing it though, it doesnt look like either of those apps updated recently to make it happen

Somestimes , the music can not be installed from Google ,but already indicate that can be downloaded

Related

[Q] Google Music app sometimes can't play radio

Hello! I've been a Google Music All Access subscriber since nearly day 1, and I haven't had any issues with the service until recently. I can't pinpoint a specific time this started, but it was before Lollipop rolled out to my Nexus 5 (problem probably started about a month ago?). GMAA has mood radio stations that you can pick based on the time of day, so for work, bedtime, etc. Often (>50% of the time now) when I try to play one of these radio stations, I get an error that states "Couldn't prepare radio. Please try again." The error persists for specific radio stations; trying other stations makes it work (but the original station still doesn't work). I've attached a screenshot of the error.
Has anyone else encountered this problem? It's REALLY annoying and I'd like to get it fixed! I'll contact Google directly if I have to, but I'd prefer to avoid that.
vaindil said:
Hello! I've been a Google Music All Access subscriber since nearly day 1, and I haven't had any issues with the service until recently. I can't pinpoint a specific time this started, but it was before Lollipop rolled out to my Nexus 5 (problem probably started about a month ago?). GMAA has mood radio stations that you can pick based on the time of day, so for work, bedtime, etc. Often (>50% of the time now) when I try to play one of these radio stations, I get an error that states "Couldn't prepare radio. Please try again." The error persists for specific radio stations; trying other stations makes it work (but the original station still doesn't work). I've attached a screenshot of the error.
Has anyone else encountered this problem? It's REALLY annoying and I'd like to get it fixed! I'll contact Google directly if I have to, but I'd prefer to avoid that.
Click to expand...
Click to collapse
Did you ever end up finding a solution to this problem. I've been experiencing it for a couple months now. I emailed Google Play app support but have not gotten a response from them even after numerous attempts.
I keep having this issue too and its so annoying...if anyone has a fix please share.
vaindil said:
Hello! I've been a Google Music All Access subscriber since nearly day 1, and I haven't had any issues with the service until recently. I can't pinpoint a specific time this started, but it was before Lollipop rolled out to my Nexus 5 (problem probably started about a month ago?). GMAA has mood radio stations that you can pick based on the time of day, so for work, bedtime, etc. Often (>50% of the time now) when I try to play one of these radio stations, I get an error that states "Couldn't prepare radio. Please try again." The error persists for specific radio stations; trying other stations makes it work (but the original station still doesn't work). I've attached a screenshot of the error.
Has anyone else encountered this problem? It's REALLY annoying and I'd like to get it fixed! I'll contact Google directly if I have to, but I'd prefer to avoid that.
Click to expand...
Click to collapse
PartimusPrime said:
I keep having this issue too and its so annoying...if anyone has a fix please share.
Click to expand...
Click to collapse
Found a solution that worked for me I grabbed the old APK from APK mirror and installed that version instead ( grab oct 21 2014 release) install this version and play a few of the contextual radios they all seemed to work on that version. After playing the ones that weren't working I installed the newest version again and they continued to work.
http://www.apkmirror.com/apk/google-inc/google-play-music/google-play-music-5-7-1717q-1530520-apk/ this is the version that I used to get it working again.
Here's what worked for me... I completely uninstalled the app. It was installed by default as a system app. Then installed again through the Google Play store. Haven't had any issues so far ??
PartimusPrime said:
Here's what worked for me... I completely uninstalled the app. It was installed by default as a system app. Then installed again through the Google Play store. Haven't had any issues so far
Click to expand...
Click to collapse
Thanks for this. I started getting the same error so I followed your instructions. I'm not rooted so I couldn't completely remove the app. But I uninstalled as much as i could and cleared everything I could and the radio stations are working again.
Hey guys
I know I'm late to the party but I found a fix to this issue and I wanted to see if it works for other people. I did this on a galaxy S7 running Android 7.0 and running the latest version of Google play music. Here's what I did:
1. Tap the 3 dot menu on the playlist in question and select "create new playlist"
2. Name the playlist something different from the original
3. Remove one song from the playlist (I don't think it matters which but I removed the first song)
4. Put the song back in the playlist.
5. Check to see if the radio function works for the new playlist
6. Delete the old playlist and rename the new on to what the old playlist was called.
7. Now you should have a playlist that is identical to the original and the radio function should work for it.
Hope this helps.

2015-11-23 Gear Plugin and Manager Release in U.S. Problems

Hi all-
There was a new version of both the Gear Manager and the Gear Plugin on the play store in the U.S. today. I am using a non-Samsung phone (Nexus 6) running a CM based Lollipop ROM (AICP) and I found that the Gear Plug In does not allow notifications to get to the watch or for the watch to control the music player.
I had been running version 15101601N (last portion of version number) and everything worked great. When I installed 15111841N from the Play Store the watch still showed up as connected but no notifications were getting to the watch. I restored my old version of the Plugin with Titanium and everything worked again. I tried this twice with the same result, even resetting the watch while the new plugin was installed (the watch would not even get through the setup process).
My theory is there is something with the new plugin that is not allowing the phone and watch to actually exchange data even though they are connected.
Note that the new version of the Gear Manager causes no problems as it is currently installed and working with the old Plugin.
If someone knows a work around, please let me know. If not, I hope this helps someone else sort their problems if they occur for them.
Cheers,
Fred
Is notification access still checked on your phone? are you getting other notifications with the new plugin? I haven't updated mine (yet)
Edit - I installed the updates on mine with no issues. I'm receiving my notifications and music controls seem to be working fine
Thanks for the reply. I just noticed that I did not see the Samsung Accessory Service which also had an update. I installed that and then the new Gear Plugin and it works fine.
Sorry for the post.
Fred

Anyway to fix Bluetooth issues?

This issue only started for me about a month ago and has gotten progressively worse.
Every time I open Google apps that could be used to stream music (play music, YouTube), I get a message saying that Bluetooth has stopped.
It happens whether I'm actually connected to a Bluetooth device or not and I can't find a way to prevent it. It never used to happen while using power amp either.
Is there anything that can be done?
Edit: It happens any time I play music now
Edit 2: The problem seems to be related to an update of the play music app. I uninstalled the update and only have the base version of the app now and everything is working fine.
Try going into apps in sttings if ure rooted use a diffrent app manager and clear the cache and data on bluetooth

Google Play Music isn't working with all songs thru Android Auto, no idea what to do

So i recently got a new phone, and while AA worked perfectly great with my Galaxy S7E, it seems to have a few issues with my Huawei Mate 9 (purchased from Best Buy's website, unlocked US version i assume). It seems its a UI issue Huawei has a problem with across multiple devices as to why phone calls don't show on the AA screen, so i guess there isn't a whole lot i can do about that one, but Google Play Music about 3/4 of the time says the song is playing but i don't hear anything even though the volume is up. Is press my steering wheel controls to move it to the next song, and i have to keep going until i find a song that'll play. I thought maybe it was a cached music issue so i cleared the google play music cache, but nope. Reset AA, reset my headunit, uninstalled AA and reinstalled, pretty much most troubleshooting steps. Thought i managed to fix it last night, but nope. The issue came back this morning. Everything else seems to work fine in AA but that. I stream all my music thru my own library thru google play music so its kind of an important app for me, so its frustrating that this is happening. Everything works fine if i just play music over bluetooth, but doing it thru AA causes this issue and im not sure why. Any ideas? Thanks.

Here WeGo non Samsung phone

So it seems that the Here wego maps/navigation app is not available for the s3 if you aren't using a Samsung phone. (I happen to use an LG v20)
Has anyone found a way to side load the app? Or what is the best alternative maps application for the s3?
Ok I found a way around the issue for anyone watching this thread... It's a little crazy and not for everyone.... I happen to have a Samsung Galaxy S7 as a work phone... I connected my S3 to that phone, where it installed HERE by default.... I then backed up the watch to my samsung account and then reconnected the watch to my LG V20 and restored the backup which included HERE.... Boom.... Problem solved
That's strange.. I got my S3 R-760 back in October 2017 from the UK. Immediately paired to a Sony Z5 and has been like that ever since, even after the ROM updates. One of the first things I did was to install HERE. Can't remember how exactly but it wans't a hassle so I assume straight from the watch or the store. I guess it has been removed after I installed it. Using it now as a standalone, no connection to the phone is required, just direct connection to the internet via wifi or hotspot. Of course I do not have the convenience of using it through the phone which could make it easier to search etc, but it is good enough.
Nice workaround you found, but for those that do not have the option of a Samsung phone, this thread could help: https://forum.xda-developers.com/gear-s3/help/wego-t3724511/page3
Hmm - I downloaded from Google onto my OnePlus 5T, installed on watch from Gear store and that was it.
UK / stock OnePlus 5T

Categories

Resources