Database Users

Pandora killed by google nav audio?

I've recently noticed a problem with my 2.2 evo. Back when I had 2.1, I would stream pandora while Google Nav was running in the background. Whenever Google Nav had to issue an instruction, it would pause pandora's playback and then resume it after the instruction is given.
Now that I have 2.2, I've noticed that when google nav gives an instruction, pandora is killed. Or at least suspended in a way that I have to manually restart playback.
Does anyone know how to fix this issue? its kind of annoying to have to tap the play button to get pandora started up again...

This a known issue and was told it was on pandoras end.
Sent from my PC36100 using XDA App

Noticed this a few days ago. Really annoying.

novanosis85 said:
This a known issue and was told it was on pandoras end.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Told by whom?
Is there a fix in the works?
the reason i ask is that there is no mention of this issue on pandora's website =/

There are a bunch of threads on this already, and they all look the same - OP states the issue, someone mentiones that its a known issue, there's no known fix, and that it's being worked on (although it's actually not specific to pandora, apparently it happens with a few other streaming music apps), a few "me too's", and then someone like me comes in and tells the op that he should have searched first. then the thread slowly moves off the main page, and we wait for the next one.
edit - a dissenter, that's new! lol - it's listed on the google code bug list here;
http://code.google.com/p/android/issues/detail?id=9569
feel free to star it up!

[INFO] Music beta had updated

Hey all,
I am in Taiwan, and I got an update about Google Music beta last night.
Cause I had slept, so I did not test it yet.
I will report the states after trying it.
Hope this update can solve some issues in 3.1.

Sigh ... still hold the same issues ...
Wait for next update

It won't install for me. I can see the update but when I click to update it doesn't do anything.
I guessed it was because I'm not in the US and the Music Beta is for US only, but now I see you're in Taiwan and installed it fine.
So did you do anything special to get it to work?

Shawn_230 said:
It won't install for me. I can see the update but when I click to update it doesn't do anything.
I guessed it was because I'm not in the US and the Music Beta is for US only, but now I see you're in Taiwan and installed it fine.
So did you do anything special to get it to work?
Click to expand...
Click to collapse
I was having the same issue - could see the update but it just flashed "allowing access" then did nothing. But suddenly today it updated - I'm in UK

czm said:
I was having the same issue - could see the update but it just flashed "allowing access" then did nothing. But suddenly today it updated - I'm in UK
Click to expand...
Click to collapse
Thanks, I suppose I'll keep trying.
Anything new or interesting other than the cloud service stuff?

I'm in the UK, received a Music Beta invite on Monday, currently uploading music to Google. Working fine. Sideloaded Music which says its version 3.0 to my DHD as the TF was sent back and awaiting a new one.

Shawn_230 said:
Thanks, I suppose I'll keep trying.
Anything new or interesting other than the cloud service stuff?
Click to expand...
Click to collapse
I don't see anything about the cloud beta (I don't have an invite) - can't see anything new in in the app

czm said:
I don't see anything about the cloud beta (I don't have an invite) - can't see anything new in in the app
Click to expand...
Click to collapse
Yeah, I just managed to run the update and nothing seems changed.
I was mistaken and the update has nothing to do with the Music Beta, I guess the big banner up top in the Market threw me off.

IM HAVING MAJOR ISSUES WITH MUSIC BETA AND MUSIC APP 3.01!! Is anyone else seeing the following?
I have the most updated music app on both my TF and Nexus S 4g and they both experience the same problem. When I am playing music from both online and offline music (shuffling all lets say) it will play a few songs fine and then it gets completely hung up and wont respond to any input. The app will not reset even if i kill the music app, when i go to reopen music it takes to a black screen with nothing on it. Its very weird and very annoying when a tab and phone cant do something as simple as playing a song. In order to fix it I have to turn the phone or tab off completely and then turn it on and it plays some songs then eventually gets hung up. Again, this is happening on my gingerbread 2.3.4 device and my honeycomb 3.1 device.

I can also see the update Music by Google Inc, but it does not install. It says V3.0.1 from 26th May 2011!
Any suggestions how to I get it updated?
rio
PS: I'm in UK

Shawn_230 said:
It won't install for me. I can see the update but when I click to update it doesn't do anything.
I guessed it was because I'm not in the US and the Music Beta is for US only, but now I see you're in Taiwan and installed it fine.
So did you do anything special to get it to work?
Click to expand...
Click to collapse
At first, I had same problem as yours.
But after 3 hrs later, the Update is working for me.
I didn't know what happened but mostly is the market's issue ( I guess).
Any way, this update changed not thing.
And I still use PowerAMP to play music. But the UI is designed for 800x480.
So I wish the Music Beta can fix those issues quickly ...

Is there any relationship between the Music Beta updates from Marketplace, and the status of the Invite? I recieved the update yesterday, but my Invite is still being processed. Wondering if my TF is being preped for the activation....
Sent from my Transformer TF101 using XDA Premium App

[Q] Nexus Q stops playing music after 20 min

I have a Q that stops playing music after 20 min and displays "music player has stopped". When I restart it, it displays "cannot play the stream you requested". It still shows I'm connected to the Q and allows me to add music to it but will not allow me to play music until I reset it by unplugging it and plugging it back in. It then will play for another 20 to 30 minutes before it displays the same message again. I've tried using the Ethernet connection as well instead of WiFi...still has the same issue.
Any ideas? I'm getting frustrated...so any help would be greatly appreciated.

Fit101 said:
I have a Q that stops playing music after 20 min and displays "music player has stopped". When I restart it, it displays "cannot play the stream you requested". It still shows I'm connected to the Q and allows me to add music to it but will not allow me to play music until I reset it by unplugging it and plugging it back in. It then will play for another 20 to 30 minutes before it displays the same message again. I've tried using the Ethernet connection as well instead of WiFi...still has the same issue.
Any ideas? I'm getting frustrated...so any help would be greatly appreciated.
Click to expand...
Click to collapse
Ditto - it was acting this way a while ago, but only over the last few days has it gotten like this. I've got 10k+ songs up on Play (and yeah, I use the service to buy music when possible) - so this ranks as extremely annoying...
Cheers!

The interesting thing is that in my Google Music account it shows what devices I have that are authorized to access Google Music, however the Nexus Q does not show up on that list. This is concerning to me, I wonder if it has something to do with why the Q is shutting music down intermittently like that.

I don't think the Q has ever shown up in the authorized device list (and don't think it should since anyone should be able to play music through it).
As for the issue playing music - I see this as well on all of my Qs (3) and it sucks.

I know this is unsupported hardware - but at least for me, this device sort of fulfills the promise of what makes Play Music 'tick' - and I use it as intended daily. So this thing just blowing up and not working (and I was just about to grab another from eBay) - blows, hard. Since there's nothing to replace it at the moment aside from moving to another 'ecology'.... (Sonos, etc)...

It seems that it stopped working correctly for me somewhere around the last update of the Play Music app (no hard data on this, just seems about the right timeframe to me). So I'm hoping another update fixes it. As I said, I have 3 Qs and all of them have this problem so getting another from ebay won't fix your issue (EDIT: misread your post on reasons for getting another...I'm holding out hope that i/o this year will shed some light on future support of these devices - if not, as long as they keep them working as they were i'll be happy enough).

I am also having a lot of connectivity issues with my Q lately. I was starting to think it was my rom on my phone causing it but am now starting to wonder if this is a server side issue with google play.
I am running AOKP PUB, Franco r102 and the volume boost mod on my nexus 4. I previously was running stock and feel like these issues were not happening until flashing these roms / mods.
Edit : good theory about the google play / services update.

natojohnsonwros16838 said:
I don't think the Q has ever shown up in the authorized device list (and don't think it should since anyone should be able to play music through it).
As for the issue playing music - I see this as well on all of my Qs (3) and it sucks.
Click to expand...
Click to collapse
I would think that considering you need a Android device to initially sync it with your Google Music account, you're accessing your music account as one of your devices and therefore should show up on your device list...but I could be wrong.

I don't think that was ever right - remember, a Nexus Q can play content from _any_ compatible device's content stream - it piggyback's that device's authorization for a specific track or video - that's why it works well for groups... anyone can add any of _their_ content to it's playlist.
So I don't think device or account specific auth is the core issue. I think it's related to lack of updates as the play service backend changes, certainly - but little else...
I sort of think that Googlers themselves with Nexus Qs that see these issues will ultimately come to our rescue - but it will be slow to happen...

Same problem with my nexus q and the latest Google music update.
Sent from my Nexus 4 using xda app-developers app

So is this Q a paperweight? What to do?

i created a google group describing the issue. Please star it so we can get an official response.
https://productforums.google.com/fo...oid-devices/other-google-products/0a0nDlo7Bz8

agalvin13 said:
i created a google group describing the issue. Please star it so we can get an official response.
https://productforums.google.com/fo...oid-devices/other-google-products/0a0nDlo7Bz8
Click to expand...
Click to collapse
Done!

My response keeps getting deleted ?

After seeing this thread I've been playing music for over an hour with no issues. Maybe its fixed? Maybe it only effects some users?
I should add that I'm using both a stock Nexus 4 and a Nexus 7 to control the Q.

El Daddy said:
After seeing this thread I've been playing music for over an hour with no issues. Maybe its fixed? Maybe it only effects some users?
I should add that I'm using both a stock Nexus 4 and a Nexus 7 to control the Q.
Click to expand...
Click to collapse
Are you dropping one song at a time on the Q or are you sending a whole play list and letting it run?

Fit101 said:
Are you dropping one song at a time on the Q or are you sending a whole play list and letting it run?
Click to expand...
Click to collapse
First, I played a short 28 min album from my Nexus 7. Then, queue'd up a few songs from my N4 to play after the album was over. Played without an issue.
I've scrolled through tracks just to test that out as well.
---------- Post added at 09:46 AM ---------- Previous post was at 09:34 AM ----------
Looks like I've spoken too soon. Just ran into the "couldn't play the stream you requested" problem. The blue ring is on my tv with the track info floating over it. Nothing is playing.

El Daddy said:
First, I played a short 28 min album from my Nexus 7. Then, queue'd up a few songs from my N4 to play after the album was over. Played without an issue.
I've scrolled through tracks just to test that out as well.
---------- Post added at 09:46 AM ---------- Previous post was at 09:34 AM ----------
Looks like I've spoken too soon. Just ran into the "couldn't play the stream you requested" problem. The blue ring is on my tv with the track info floating over it. Nothing is playing.
Click to expand...
Click to collapse
Yes, sounds like you are sharing the same issue we are. There's an old saying "Misery loves company"...I just hope Google gets off their rear end and fixes this. I built a whole kiosk at my business dedicated to the Nexus Q and the ability to allow my members with Android devices to stream music to it. Now I kind of feel like an arse.

I wonder who we can get a hold of to let Google know about the issue. I have a feeling contacting support would be useless. Anyone know who the engineers were that worked on the Q? I wonder if we could ping them on G+ or something. I'm sure there isn't a big enough user base for the tech sites to cover it, so going that route wouldn't work either.
I mean I love the Q but it does 2 things and 1 of them doesn't work. That should be a big enough issue for Google to fix.

El Daddy said:
I wonder who we can get a hold of to let Google know about the issue. I have a feeling contacting support would be useless. Anyone know who the engineers were that worked on the Q? I wonder if we could ping them on G+ or something. I'm sure there isn't a big enough user base for the tech sites to cover it, so going that route wouldn't work either.
I mean I love the Q but it does 2 things and 1 of them doesn't work. That should be a big enough issue for Google to fix.
Click to expand...
Click to collapse
I did contact Google tech support in the beginning when it first started happening, and have been in contact with them via email ever since. Because of the limited quantity of units out there, the tech support has very little data, nor much ability to help. I have also emailed them a link to this thread in hopes that it would spark some deeper tech support. It may help if we all follow that route, Maybe the squeaky wheel gets the grease? LOL

[Q] YouTube app

Recently after last update i've got very annoying problem. At moments video is pausing but voice is still going. Doesn't help clearing cache and cookies and reinstall update. When I'm reading the opinions on play store I came across that other users s5 have the same problem. Is that Samsung fault? I hope that in the near future we've got new system update. What do you think?

Haven't seen or heard of that problem before. But as you say that you tried clearing your cache and say that others are also reporting the problem then it would appear to be a bug. Your recourse then is to wait until an update addresses the bug (or someone finds a workaround) or revert to an earlier firmware version. Pick the approach that you prefer.
.

Walter1922 said:
Recently after last update i've got very annoying problem. At moments video is pausing but voice is still going. Doesn't help clearing cache and cookies and reinstall update. When I'm reading the opinions on play store I came across that other users s5 have the same problem. Is that Samsung fault? I hope that in the near future we've got new system update. What do you think?
Click to expand...
Click to collapse
Same here, definitely a bug in app.

AlexianuS said:
Same here, definitely a bug in app.
Click to expand...
Click to collapse
Its a YT bug, hopefully the next update will fix it.

Share menu bug in OB11 and Stable 5.1.2

Here's my issue:
https://www.youtube.com/watch?v=nz8lBMJGMVI
In normal conditions, pinning an app in the share menu would bring that app to the top of the list (has been like this for years and years in android), but now, the menu doesn't reorder, as you can see in the video.
Tried with a clean install, starts working, but after installing one or more apps, it immediately get's bugged.
Can anyone confirm this? If you don't have that problem, can you post your system info?
I already sent the bug report to oneplus along with logs, but haven't gotten a response yet.

I have the same issue with that update :/

fjsferreira said:
Can anyone confirm this? If you don't have that problem, can you post your system info?
I already sent the bug report to oneplus along with logs, but haven't gotten a response yet.
Click to expand...
Click to collapse
I did not try with Pinning, but on my device, Direct Share no longer works. What I mean is, normally I have my frequent shared contacts right at the top with the corresponding app, so I could always directly share with my wife, for example... Now, that no longer shows up. Weird thing is that it shows up if I select multiple options to share... For example, in gallery, if its a single picture, no direct share, but if its more than one picture, everything works as before.
I am in touch with the bug team about this and they said they are looking into it. If I receive any further updates from them, I will post an update here as well.
It does seem strange though that not everybody seems to have this problem (or don't seem to have noticed!)
For now, Direct Share is too useful for me to live with this bug, so I am planning to downgrade to Beta 9 that worked fine for me.

karthikrr said:
I did not try with Pinning, but on my device, Direct Share no longer works. What I mean is, normally I have my frequent shared contacts right at the top with the corresponding app, so I could always directly share with my wife, for example... Now, that no longer shows up. Weird thing is that it shows up if I select multiple options to share... For example, in gallery, if its a single picture, no direct share, but if its more than one picture, everything works as before.
I am in touch with the bug team about this and they said they are looking into it. If I receive any further updates from them, I will post an update here as well.
It does seem strange though that not everybody seems to have this problem (or don't seem to have noticed!)
For now, Direct Share is too useful for me to live with this bug, so I am planning to downgrade to Beta 9 that worked fine for me.
Click to expand...
Click to collapse
Did you downgrade? If you did, did you dirty flash over the new version?

thevirgonian said:
Did you downgrade? If you did, did you dirty flash over the new version?
Click to expand...
Click to collapse
Yes, I did downgrade. Dirty flash of OB9 over OB11 worked just fine. However, to be doubly sure, I did disable screen-lock before I did it, AND backed up everything important.