Yesterday I used my chromecast again. .... after using it when using notification shade a persistent error appears. ... only way to fix it is rebooting. Any ideas?
Enviado desde mi SM-P600 mediante Tapatalk
Can you elaborate some more? I'm not having any issues like yours so give some extra information please.
mantrajt said:
Yesterday I used my chromecast again. .... after using it when using notification shade a persistent error appears. ... only way to fix it is rebooting. Any ideas?
Enviado desde mi SM-P600 mediante Tapatalk
Click to expand...
Click to collapse
Seems a few of us are waiting for this to be fixed. Another forum member has sent their tablet back to samsung twice now hoping for a fix. This problem is apparent on my note pro as well, so I think we need sammy to push us a software fix
chgambini said:
Seems a few of us are waiting for this to be fixed. Another forum member has sent their tablet back to samsung twice now hoping for a fix. This problem is apparent on my note pro as well, so I think we need sammy to push us a software fix
Click to expand...
Click to collapse
Hope this doesn't take them soooo looooong
Enviado desde mi SM-P600 mediante Tapatalk
I wonder if the Samsung phones running 4.4 have this too or is it just the tablets? I know the 12 inch version has this issue too.
It's the primary reason I'm still running 4.3.
chgambini said:
I think we need sammy to push us a software fix
Click to expand...
Click to collapse
Not to be the bearer of bad news but if it's an isolated problem affecting a small percentage of users the likelihood of Samsung issuing an update for just this specific issue is pretty slim. I don't use Chromecast myself but I was at a friends house last night and tried it from my N10.1-14 running 4.4. I didn't have any issues and the notification panel didn't bork while I played with it during Chromecast playback. Since those with the issue didn't have it on 4.3 it's obviously a s/w compatibility issue or conflict. I'd try to narrow down what's unique on the Pro's and Note's running 4.4 that are having problems to find the ROM version/region, installed s/w, combination of s/w, configuration, or settings that are causing it. You guys huddling together to figure it out will be faster than waiting for a fix that may never come.
BarryH_GEG said:
Not to be the bearer of bad news but if it's an isolated problem affecting a small percentage of users the likelihood of Samsung issuing an update for just this specific issue is pretty slim. I don't use Chromecast myself but I was at a friends house last night and tried it from my N10.1-14 running 4.4. I didn't have any issues and the notification panel didn't bork while I played with it during Chromecast playback. Since those with the issue didn't have it on 4.3 it's obviously a s/w compatibility issue or conflict. I'd try to narrow down what's unique on the Pro's and Note's running 4.4 that are having problems to find the ROM version/region, installed s/w, combination of s/w, configuration, or settings that are causing it. You guys huddling together to figure it out will be faster than waiting for a fix that may never come.
Click to expand...
Click to collapse
I think the percentage is bigger than we think. I have tried all the floor models at my local best buy and they to mess up. I to doubt samsung will fix this. I am not sure how to isolate the problem. The note pro I have access to is completely stock, the stock wallpapers for lock and home screens have not even been changed. I have factory reset both devices and have not installed any app other than the pre-installed stuff. Calling samsung doesnt help, I have already read of other forum members sending their tablets in to just have them sent back without being "fixed". There are more than one thread about this throughout XDA and other sites.
I have owned my 2014 since nov 2013. I haven't changed anything on it other than the update to 4.4. Thats why I beleive it is the cause. The moment after the update was complete, the chromecast problem happened.
I will say again, chromecast works as always fof many, many apps. Listening to google play music and google play movies seems to be the biggest offenders. I have read that the Crackle app has problems too.
My 2014 and pro are bogh 32g US version purchased straight from samsung. Both have never been rooted.
chgambini said:
I think the percentage is bigger than we think.
Click to expand...
Click to collapse
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
blinkingled said:
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
Click to expand...
Click to collapse
I assume your using google play music/movies too
chgambini said:
I assume your using google play music/movies too
Click to expand...
Click to collapse
Pretty much anything that works with Chromecast crashes it. Twit Cast for Chromecast, Google Play Music and Videos, Chrome Beta, YouTube etc.
blinkingled said:
Pretty much anything that works with Chromecast crashes it. Twit Cast for Chromecast, Google Play Music and Videos, Chrome Beta, YouTube etc.
Click to expand...
Click to collapse
I can watch youtube and hbogo with no problems. Do you have the video playback issues as well? If I try to watch a video from g+ or a preview of a movie on google play, I will either get a black screen with audio only, or massive stuttering and lines while watching on the tablet in full screen.
I have sent feed back to Google on the music and movies apps. Lets see what kind of reply we get from them
blinkingled said:
I very much agree with this - I have tried Costco and BB models - 2014 and Tab Pro and Note Pro - all had the same issue. It's the lucky few that haven't had it.
Click to expand...
Click to collapse
What regions does it affect? Obviously you're in the U.S. My working device is from Latin America. Do Chromecast's themselves come with a single version of s/w that's deployed identically worldwide? Google updates Chromecast. Was the Chromecast's firmware the same before and after the N10.1-14 started crashing? You need to figure out what the devices that aren't working have in common and that includes Chromecast itself. Does screen mirroring work by means other than Chromecast? You'd think if something was majorly wrong with the N10.1-14's video, networking, or s/w drivers screen mirroring would be borked consistently. Just some things to think about.
I'll give you an example. Some folks with the OG N10.1 reported importing PDF's crashed S Note. A bunch of us weren't having any issues. We found out that even though the OG 10.1 was only six months old at the time there were eight different versions of S Note installed depending on region. Two of the eight had the PDF problem. Therefore I'd be careful about making assumptions about how wide spread the issue is. Chromecast's pretty popular and I think there would be more "WTF?" posts if it was as widespread as some think it is.
SamsE=BarryH_GEG;52798927]What regions does it affect? Obviously you're in the U.S. My working device is from Latin America. Do Chromecast's themselves come with a single version of s/w that's deployed identically worldwide? Google updates Chromecast. Was the Chromecast's firmware the same before and after the N10.1-14 started crashing? You need to figure out what the devices that aren't working have in common and that includes Chromecast itself. Does screen mirroring work by means other than Chromecast? You'd think if something was majorly wrong with the N10.1-14's video, networking, or s/w drivers screen mirroring would be borked consistently. Just some things to think about.
I'll give you an example. Some folks with the OG N10.1 reported importing PDF's crashed S Note. A bunch of us weren't having any issues. We found out that even though the OG 10.1 was only six months old at the time there were eight different versions of S Note installed depending on region. Two of the eight had the PDF problem. Therefore I'd be careful about making assumptions about how wide spread the issue is. Chromecast's pretty popular and I think there would be more "WTF?" posts if it was as widespread as some think it is.[/QUOTE]
I have 2 chromecast in my house. Yes the are updated OTA directly from google. The firmware was the same before and after the update. My note 3 on 4.4 works perfectly with chromecast with the same version of google play music/movies and the ssme apps overall installed. Samsungs allsharecast will work on my tablets. The only devices I have that exhibit this behavior are the note 2014 and note pro. Both stock us version, both crash on play music/movies, both have random issues with video play back. The 2014 was fine before 4.4, so this leads me to believe the update is causing it. I did not try the pro until I had issues with the 2014 to see if it was the same so I cant say it was good or bad out of the box. The pro did rec an update right before the 2014 rec 4.4.
chgambini said:
I have 2 chromecast in my house. Yes the are updated OTA directly from google. The firmware was the same before and after the update. My note 3 on 4.4 works perfectly with chromecast with the same version of google play music/movies and the ssme apps overall installed. Samsungs allsharecast will work on my tablets. The only devices I have that exhibit this behavior are the note 2014 and note pro. Both stock us version, both crash on play music/movies, both have random issues with video play back. The 2014 was fine before 4.4, so this leads me to believe the update is causing it. I did not try the pro until I had issues with the 2014 to see if it was the same so I cant say it was good or bad out of the box. The pro did rec an update right before the 2014 rec 4.4.
Click to expand...
Click to collapse
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
BarryH_GEG said:
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
Yes I have done a hard reset on both devices, skiping past adding any accounts and unchecking the restore app data box.
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
BarryH_GEG said:
Comparing to other devices isn't going to help you. Hell, my N10.1-14 works fine with Chromecast on 4.4 and others have said the same thing. So the issue isn't where it works, it's where it doesn't and why. Out of what you said this is what I took away...
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
No sdcard. I will try a hard reset again, unchecking all the google sync stuff. Got nothing to lose.......
Try downloading a free show or trailer in Samsung Hub Video. Does the issue occur with a Samsung app using Samsung-sourced content?
BarryH_GEG said:
Try downloading a free show or trailer in Samsung Hub Video. Does the issue occur with a Samsung app using Samsung-sourced content?
Click to expand...
Click to collapse
OK, hard reset, nothing installed, skipped past adding accounts. Went to settings, back up and reset unchecked restore apps data and added my Google account with all sync unchecked. Google music and movie still cause system.ui crash when touching the notification bar. Samsung hub plays fine. Samsung hub does use allsharecast to my Samsung TV and not the chromecast though
chgambini said:
OK, hard reset, nothing installed, skipped past adding accounts. Went to settings, back up and reset unchecked restore apps data aND added my Google account with all sync unchecked. Google music and movie still cause system.ui crash when touching the notification bar. Samsung hub plays fine. Samsung hub does use all casts hare to my Samsung TV and not the chrome cast though
Click to expand...
Click to collapse
Try turning off Chrome in Application Manager.
BarryH_GEG said:
Try turning off Chrome in Application Manager.
Click to expand...
Click to collapse
No change, still crashes
BarryH_GEG said:
The problem was introduced with 4.4 because your N10.1-14 worked fine with the same Chromecast device on 4.3. Is it something Samsung did in 4.4 specific to the Pros/Notes? Just for U.S. versions? Is it an issue in 4.4 itself that the specific Samsung s/w on the Pro/Notes is aggravating? It's not universal to 4.4 or 4.4 on the Pro/Notes because the problem's not happening beyond a subset of devices.
Your device is from the U.S. as is @blinkingled 's. Where are the other people reporting issues device's from?
You said the problem was there after a complete reset. Does that include preventing Google and Samsung from applying apps and settings stored in your accounts when you first start setup? I'd hard reset again skipping both the Samsung and Google account sign-ins. Go to Accounts in settings and add Google but quickly uncheck all the syncs so they don't add anything to your device. Same thing if Play tries to restore or update your apps. In Play, install one of the apps that was causing crashes. If with nothing but the basics on your tablet Chromecast is still crashing it's something in Samsung's update causing the problem. At least for the U.S.
You mentioned the Pro receiving an update. Since this isn't a universal problem there's no assurance that Samsung's devs even know about it. If 100 people worldwide report a problem and it makes it in to Samsung's problem tracking system that's a blip compared to the millions of devices sold since the N10.1-14 became available in October. And since it's related to third party h/w it goes to the bottom of the line. In the scenario I described above with the OG Tab 10.1 PDF issue Samsung did nothing to specifically address the problem even though people from affected regions reported it. The next wave of planned updates fixed the problem because all regions received an S Note update. So if we can't figure out the issue it's highly unlikely Samsung will either. That means if an update corrects it it'll be coincidence not because Samsung's diligently working on a solution. In other words, people affected that live and die by Chromecast are potentially going to have to live with this for a while.
EDIT: Do you guys with issues have external SD cards? Try removing them and soft resetting the tablet (hold power for seven seconds) to see if that makes a difference.
Click to expand...
Click to collapse
That's an extensive and well thought out debugging list - thanks :good: (I had posted a message some time ago to gather info from people having and not having the issue - but I think we only got 2-3 uncertain data points.) But at this point I have tried everything in your post - reset, with and without SD, without restoring apps, with and without updates. It still crashes. And the ChromeCast firmware was last updated was in mid April when it didn't have an issue with 4.3 - so that doesn't seem to be a factor either.
About being in the US - I think OP's tablet is Latin American version if I am not mistaken. It's really a mystery at this point as to why some of them work.
Related
Hi!
Does anyone have problem with Google Play Music after the KitKat upgrade?
After the upgrade when i try to play a song, it gives me an error after a few minutes: "Music Playback error. Can't play the track you requested,"
I tried to remove the updates from Play Music, clear data from Play Music and Media Storage, nothing helped.
It happens on wifi and mobile connection too, and with the songs that i made to offline.
I haven't found a soultion on the forum.
Does anyone have an idea?
Thanks!
Sorry for my English.
That might be a result of Google releasing Google Music in your country. Have you registered your account through a proxy before?
If so, you probably have playlists with tracks that is not available in your region that your account now is associated with. Try search for the songs again and see if you can play it from there.
Geggan said:
That might be a result of Google releasing Google Music in your country. Have you registered your account through a proxy before?
If so, you probably have playlists with tracks that is not available in your region that your account now is associated with. Try search for the songs again and see if you can play it from there.
Click to expand...
Click to collapse
Thanks for the tip. Play Music All Access released a half year ago, and before I didn't used a proxy to use the service. On 4.2.2 it worked well. Only on KitKat is this problem. I'll try to fix the update errors from the PC Suite, and a hard reset. I'll reply about it's success.
mastagw89 said:
Hi!
Does anyone have problem with Google Play Music after the KitKat upgrade?
After the upgrade when i try to play a song, it gives me an error after a few minutes: "Music Playback error. Can't play the track you requested,"
I tried to remove the updates from Play Music, clear data from Play Music and Media Storage, nothing helped.
It happens on wifi and mobile connection too, and with the songs that i made to offline.
I haven't found a soultion on the forum.
Does anyone have an idea?
Thanks!
Sorry for my English.
Click to expand...
Click to collapse
I had the same problem on 4.2, in my case clearing data uninstalling installing helped though... or it got fixed few days later... or I found a solution which I forgot.
I do realize that this won't help you much, just wanted to point out that it had nothing to do with the android version.
Also that the proxy stuff someone said is needed only to set it up... after that there is no need for any proxies. So I would say has nothing to do with it.
Also I am in a country that got play music just now and I had it since all access began... so again I think even that would not be a case.
I am a bit angry because in my country the all access is cheaper as in the US and I am not sure I can switch to the action price and if I will have the same songs as in US market...
Sent from my LG-D802 using Tapatalk
I have this problem and I haven't found a solution. It's really annoying. It seems completely random. Sometimes every song I play will give me the error.
Sent from my LG-D800 using Tapatalk
PAGOT said:
I had the same problem on 4.2, in my case clearing data uninstalling installing helped though... or it got fixed few days later... or I found a solution which I forgot.
I do realize that this won't help you much, just wanted to point out that it had nothing to do with the android version.
Also that the proxy stuff someone said is needed only to set it up... after that there is no need for any proxies. So I would say has nothing to do with it.
Also I am in a country that got play music just now and I had it since all access began... so again I think even that would not be a case.
I am a bit angry because in my country the all access is cheaper as in the US and I am not sure I can switch to the action price and if I will have the same songs as in US market...
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks for the information, i think it's not about the Android version too. I think LG made some changes, because on my Nexus 7 on stock 4.4.2 it works fine. I found some forums about this problem, but on the Optimus G model, and without a solution. So I think the problem is on LG's side. I wrote a mail to them about the problems after the update, and they replied they are working on to fix them. I hope they will fix this too.
Running out of things to try
I have had the exact same issue since updating to 4.4.2 on my LG G2. I had to reset the Google framework app to finally get the update after weeks of trying. So initially thought the error was due to that. So I factory reset my device & still get the errors.
I have tried clearing cache, data, uninstalling all updates to play music. Still the same problems.
Updated the play app & still no resolution.
When I'm on mobile data I get the error on every song I play. On Wi-Fi I can go 5 to 10 songs before the same error pops up.
I have contacted T-Mobile & they confirmed that a lot of users have reported this after the 4.4.2 update me not just with the G2 but also with the galaxy S4 & note 3 after updating to 4.4.2 as well. I told them all the trouble shooting I've done & they told me to contact Google to find a solution.
Google play music support was unaware of this issue & after running me through the same steps told me to contact LG
LG once again was unaware of the issue & tired running me thorough the same steps again. Their conclusion was that my phone/the app was having trouble communicating with the Google servers. & directed me back to Google or T-Mobile.
So it's really frustrating since 4.4.2 has fixed a lot of my other issues (GPS, Bluetooth meta data, etc) but has given me a different & so far solution-less problem. :banghead:
My wife's G2 is doing this as well.
I did dig up a thread from Android Central from last year where some people suspected some process needed for their Chromecast was somehow interfering.
Just curious, how many of you with this issue also have a Chromecast?
KYT said:
My wife's G2 is doing this as well.
I did dig up a thread from Android Central from last year where some people suspected some process needed for their Chromecast was somehow interfering.
Just curious, how many of you with this issue also have a Chromecast?
Click to expand...
Click to collapse
I have a couple of Chromecasts. Before the 4.4.2 update my G2 would not cast a full song or two onto the Chromecast. But after the update it's the other way around. It will cast fine with no errors but won't play a full song on my phone.
Did you know what about the Chromecast was causing this issue? Was it the Chromecast app?
---------- Post added at 02:27 PM ---------- Previous post was at 02:08 PM ----------
I tested out a couple of scenarios for at least playing songs that were cached on the device.
Had the same problems with data turned on & off. & even in airplane mode.
The only time it played without the playback error was when I took the SIM card out. It's a bit strange I know, but I'm going to see if maybe getting a different SIM card form T-Mobile does anything to this issue.
---------- Post added at 02:51 PM ---------- Previous post was at 02:27 PM ----------
Here's the acknowledgement from Google on the issue!
Hello I understand you are getting a Music Playback Error on your LG G2 after updating to the Kit Kat software. I want you to know we have a team of specialists working very hard to resolve this issue. At this time their is a compatibility issue with the newest version of Kit Kat that was rolled out by the carrier to the LG G2.
We are working very hard to resolve this and I apologize for any inconvenience this may have caused. I'd recommend using a different device for now but I totally understand if you wish to cancel the service. If you'd like I can cancel this subscription and refund you for your troubles. Please let me know what you decide, I'll be in touch with you as soon as I receive a response from our engineers.
If you have any other questions or concerns feel free to reply directly to this email for additional assistance or contacts us at our Google Support site for further information.
RedTiki said:
I have a couple of Chromecasts. Before the 4.4.2 update my G2 would not cast a full song or two onto the Chromecast. But after the update it's the other way around. It will cast fine with no errors but won't play a full song on my phone.
Did you know what about the Chromecast was causing this issue? Was it the Chromecast app?
Click to expand...
Click to collapse
No, I had just find a whole bunch of other threads for different phones from last year where people started having issues with google music who used Chromecast. It occurred to me that we have a Chromecast, and my wife uses it. I haven't used once, we both have T-mobile, but I have a Nexus 5. So I was just wondering if everyone else with a G2 and the same problem also had a Chromecast.
Maybe there's some service the Chromecast uses that foobars something Music uses. Someone else had mentioned that when Music errors like this, they restart their phone and if works properly. Maybe that Chromecast service doesn't start on boot, and so it doesn't cause an issue until after it is used.
*shrugs* just a theory.
KYT said:
My wife's G2 is doing this as well.
I did dig up a thread from Android Central from last year where some people suspected some process needed for their Chromecast was somehow interfering.
Just curious, how many of you with this issue also have a Chromecast?
Click to expand...
Click to collapse
I don't have a Chromecast. I wrote to Google, and replied they consulted my case to a higher tier. I hope they can fix it in the Play Music app. I'm waiting for newer informations.
I also have the same problem andere its gettin worse everyvday. I tried it with an older version of play music but with no luck.
I hope they come with a fix soon because its getting really frustrating.
Sent from my LG-D802 using XDA Premium 4 mobile app
Same problem here. On my old SGS2 all was fine. With my new LG G2 I have this issue too. Sometimes all fine, then it stucks every minute/second.
Android 4.4.2
really annoying bug
Same error here on T mobile LG G2 running KitKat. Sometimes Google Music just works but then it wont play a thing for a while. Especially frustrates me when I am driving or when at the gym.
jcrabapple said:
I have this problem and I haven't found a solution. It's really annoying. It seems completely random. Sometimes every song I play will give me the error.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
im having the same issue.. if i am on mobile data or wifi. if i turn them off i will get the err less, like 2 or 2 songs. this is my primary source of music!! please help
Finally managed to get a Logcat with all the details of the crash. Lots of information in this... The process "Nexstreaming" goes haywire when the crashes happen. Lots of A2DP references as well. Hopefully somebody can make heads or tails of all of this.
I had one song playing on loop during this Logcat. This particular song crashes more often than any other in Google Play (for me anyway) . I'm wondering if the audio subsystem is getting flooded with too much bandwidth for the BT codec to parse?
https://app.box.com/s/4ll2w5dwvz4429tmqu2m
Sent from my LG-D800 using Tapatalk
Such an annoying issue.
Even with pinned music it won't always play
Funny thing I'm noticing is that - especially with pinned music - if a song crashes the player, it's highly likely that it'll crash the player again at the same point in the song. I have several songs that I can predict the exact places where the song will quit. It's not consistent from play to play though.
Sent from my LG-D800 using Tapatalk
Hey so I decided to come here and take a look, what exactly is the problem you guys are having with Google play music app, is it only while streaming with Bluetooth or on both WiFi and Bluetooth, are songs bought from the play store or from you computer? Any details will be appreciated
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
Hey so I decided to come here and take a look, what exactly is the problem you guys are having with Google play music app, is it only while streaming with Bluetooth or on both WiFi and Bluetooth, are songs bought from the play store or from you computer? Any details will be appreciated
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
On G2 where every MB is precious(16GB) no way I gonna put on it music. For me it's the streams. I am feeling lucky radio to be precise. And problems I get sometimes as the good ppl have described. (Finally joined the KK ranks with all its faults... woohoo)
Sent from my LG-D802 using Tapatalk
Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls.
A HTC spokesperson confirmed the problem to TechRadar, with a recent HTC Service Pack downloaded from the Google Play Store the presumed (but unconfirmed) culprit.
The firm says resolving the problem, which could also be affecting One M8 users, is its number one priority and has told customers to expect the roll out in the coming days.
The statement says: “We are aware that some HTC One M7 (and possibly some M8) users have recently been experiencing audio issues making network calls on their devices.
“WiFi calling does not seem to be impacted at this time. We're working around the clock with our technical teams and partners to resolve the issue as a number one priority.
“We will provide further updates as soon as we can. For anyone experiencing this issue with your HTC One (M7 or M8), you may want to try WiFi calling, and we ask that you please contact your local Customer Care: www.htc.com/support."
Speculation suggests the Service Pack may have caused the instability, but HTC isn’t offering up that information at this stage. As the original report points out, if you haven’t downloaded the update yet, it may be wise not to do so.
jkolner said:
Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls..
Click to expand...
Click to collapse
This might explain the issues I have been experiencing since the 5.01 OTA. Call recording has failed with every SW I have tried. Sound quality during calls has crackling and is very poor.
This makes a lot of sense, in the last couple of days mine has had the same problem as was told by HTC that it was a hardware issue, but if this is the case may just hold back and wait for an update.
I've had mine recently producing no audio at either end when answering a call, a reboot seems to sort it out for a while. Hopefully this is all it is and they can sort it out fairly soon, I'm in the middle of buying my first home and trying to talk to lawyers and stuff gets a bit embarrassing when this happens.
Oh my a God.
Thought was mine only!
Sent from my HTC One using XDA Free mobile app
I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.
Pavlova said:
I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.
Click to expand...
Click to collapse
On M8 Original GPE, HTC service pack was installed with 5.01 OTA update. No choice on whether to install or not - it appeared on the list of updated apps.
Apart from sound issues (which I suspect come from HTC/Google disabling features at the Kernel level), I am now experiencing delayed touch response.
Yes, but as I remeber, it was updated also after initial startup. Last update of the Service Pack (on Sense) in Play Store was from 11th December. Anyway, on T-Mo firmware 3.29.118.9 call quality is much better. Also ringtones and notifications are more clear.
Just got a service pack update.
for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching
Andrew149 said:
Just got a service pack update.
Click to expand...
Click to collapse
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
RedBlackPellet said:
for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching
Click to expand...
Click to collapse
Can you pls give a little more details as to what specifically you uninstalled. Thanks.
Roadrunner100 said:
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
Can you pls give a little more details as to what specifically you uninstalled. Thanks.
Click to expand...
Click to collapse
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related
RedBlackPellet said:
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related
Click to expand...
Click to collapse
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1
Roadrunner100 said:
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1
Click to expand...
Click to collapse
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution
RedBlackPellet said:
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution
Click to expand...
Click to collapse
Like you I'm trying to find out what's going on. I can confirm issues with the proximity sensor. I have further issues like skype not gaining access to camera, voice call issues like loud speaker switching on by itself during a call.. etc. What's clear at the moment is that this GPE release is screwed up big time. Like you I've reset the device a few times, but noting changes. Same problems reappear.
I think that finding out more is difficult since there are no specific Forums or threads dedicated to non converted stock GPE's. So finding out more about issues specific to this version is very hard... I have two other colleagues with Original GPE's (mine is a very early device, their's purchased recently) that have the exact same issues, so I can only assume that this is not HW related, but due to Google disabling certain features and getting it badly wrong or HTC's service Pack at fault. In the office there are three other Sense M8's, which don't have any of these issues, but none of them are on Lollipop yet, so I cannot compare until they get HTC's update.
I have a OEM gpe m8, running mrjaydee82's lollipop gpe ROM. I've seen no weirdness besides memory leak.
Using "Netflix for Android TV 2.2 build 636" from the Sony TV APKs on my nexus player
Keep getting the error
"It looks like Netflix has been deactivated on this device"
have to re-login very frequently
Any ideas on how to solve this?
2.2.1 build 643 is on the Play Store, I've only had one forced reactivation with it so far.
But yeah Netflix for Android TV is quite buggy - a lazy port by the looks of it.
I got this Bs twice tonight.. like seriously? wtf is going on
Sent from my Samsung Galaxy Note 4 using Tapatalk.
Just got off the phone with netflix
had this happening, literally after every episode tonight. after troubleshooting everything at my house, thoroughly, I spent about an hour going through things with netflix support. apparently this is a known issue and for now there was no resolution. he said give it some time and check back if not resolved after having been escalated to tier 3 support.
Yeah it was quite bad, I noticed it seemed to be triggered consistently just after autoplaying a new episode - always within the first 30 seconds - but not after manually picking the next ep.
yup same here. honestly, I bought my dad a fire TV and myself a nexus and this nexus is garbage compared to the fire TV.. especially since I'm a prime member. I might just buy a fire TV and sell this pos.
Sent from my Samsung Galaxy Note 4 using Tapatalk.
Keep getting it too.
Really annoying.
Thought it was because I'm using it through a VPN / UnoTelly DNS but seems like it's just their terrible, terrible app being terrible.
clanbartok said:
Using "Netflix for Android TV 2.2 build 636" from the Sony TV APKs on my nexus player
Keep getting the error
"It looks like Netflix has been deactivated on this device"
have to re-login very frequently
Any ideas on how to solve this?
Click to expand...
Click to collapse
I have a Nexus Player and started getting this about 48 hours ago. It's annoying. Thanks for the workaround... I'll have to try that! I'm sick and tired of having to login after ever darn episode!!!
I do have the same problem, but i use dns4me.
on the help center (for xbox), it says that you should put dns settings on automatic.
Same issue here. Could it be related to IPv6 DNS? I have IPv6 6to4 turned on in my router and the IPv6 DNS is visible in the settings but no IPv6 adress is assigned for the device in the settings. Also in contact with the Netflix support here in Sweden, they called to US and they will investigate an call back in a few days. What ROM do you others guys use? Stock? I installed CM to be able to mount USB for Kodi.
This just started happening to me last night as well and now I have to keep logging in after every show. Time to hit them up....
I'm in the same boat guys.
I guess the bright side is I finally got around to installing cyanogenmod which of course didn't fix the issue.
I'm having this issues since a week or two. It must be a problem on the apps side only. More and more Playstore reviews and forum posts are coming up about this.
In a netflix support chat, they said that they are already working on a fix for this ... I hope so, because that's really lame.
Just came by to say the same thing is happening to me. Spent an hour on the phone with Netflix tech support, tried everything on my end, still having the same problem. Hope enough people call tech support so they know this is an issue.
i dont watch netflix often on the player, but i have this build and just fired it up and ran a few random videos. i had no errors or forced reactivations. it recognized me from the last time i ran it so it went right to the last played video i just played on my htpc...
stock and never rooted.
ghtop said:
2.2.1 build 643 is on the Play Store, I've only had one forced reactivation with it so far.
Click to expand...
Click to collapse
marctronixx said:
i dont watch netflix often on the player, but i have this build and just fired it up and ran a few random videos. i had no errors or forced reactivations. it recognized me from the last time i ran it so it went right to the last played video i just played on my htpc...
stock and never rooted.
Click to expand...
Click to collapse
The bug is triggered when autoplaying episodes, not when manually selecting them.
Edit: may be related to Settings > Help > Device, UI Build: release-20150707_170-zircon.
Same thing, asus nexus player
Got the exact same thing with my Asus Nexus Player.. 2.2.1 Build 643 of netflix app..
Need to reactivate every time it autoplays i to the next episode.. Manual select seems to br the workaround atm, tho quite annoying
I also have this problem, latest netflix on nexus plater stock rom
Me too. Netflix support just ask to sign out of app, power down the nexus player for a minute, power it back up, sign back in. Seemed to fix it, but then it was doing it again as soon as I actually watched an episode rather than just fast forwarding to the last 30 seconds.
Tried a clearing of the app data, didn't help. Tried a factory reset, that didn't help either.
longer explanation...
ok besides the fact the original episodes of mission impossible and knight rider are no longer on the site (expired licenses), i played one full episode of star trek, the original series (these shows are great background flicks whilst one is doing other things) and i was not forced out or required to sign off/on.
a bit of an aside, i have an ipad i have on my elliptical that i view whilst exercising, and when i would switch from that to the htpc i would sometimes have to re-log back in on the htpc. the error would say something to the effect of i cant be logged onto two different places at the same time, even though both devices (the htpc and ipad) are on the same network and subnet. i just figured the apple app has a different way of signing in. this error just started happening a couple weeks ago (i was using the ipad for months prior), so now i just turn on the television that the htpc is on and just view that whilst working on the machine and not had to re-log into the htpc (which is just the website netflix.com).
I have an Australian bought Pixel 4, build: QQ1B.200205.002, Security patch level 5 Feb 2020, stock factory firmware, not rooted. Bought it on the first week of release, so had it for a while now.
Since about a week ago my phone stopped responding to the "ok-google" hotword in sleep and locked modes. Restarting the phone temporarily fixes it, but it stops again after a while. Especially if I don’t use the phone for an hour or so.
It used to work quite reliably before. Voice match is enabled, also retrained the voice model but that didn’t help. Haven’t installed any new apps recently, nor recall changing any settings. I only have a handful of very popular 3rd party apps like Waze, Tunein, Skype, Outlook, Viber, Whatsapp a couple of banking apps etc., but no games or optimiser apps of any sort.
Any ideas?
Thanks.
I had similar issue. I had to disable battery optimisation for the Google app. Seems to have cure it
Thanks for the reply, I tried changing battery optimizer settings for Google app, failing that I even did a factory reset. Still nothing. Looks like I’m not alone with this particular problem: https://support.google.com/pixelphone/thread/27204195?hl=en
Check your case, small cutouts affected my microphones on my Galaxy Note8 two years ago.
Received the march update, but the problem still exists.
vonDubenshire said:
Check your case, small cutouts affected my microphones on my Galaxy Note8 two years ago.
Click to expand...
Click to collapse
Pretty sure the case has nothing to do with it, because it used to work fine with the same case till a month ago, it works for a while soon after the phone is restarted, and there are many others experiencing the same problem as noted in the above google community thread.
[SOLVED]
Hi All,
i have read the other posts about similar problems and although they are probably one and the same problems,
i'm slightly new to terminologies and was hoping for a slightly tailored discussion.
That being said i'm going to jump straight in with the story from the beginning,
Around 2 Months ago i bought this Head unit for my car.
Seicane - 9 Inch OEM Android 9.0 Radio 2004-2011 Ford FOCUS EXI MT 2 3 Mk2/Mk3 Manual air condition GPS Navigation system Bluetooth Touch Screen TPMS DVR OBD II Rear camera AUX 3G WiFi HD 1080P Video
I have recently received this and installed it just yesterday.
Now the problems i'm having is that when ever i use anything internet based via a WiFi dongle or hot spot on my phone then the whole system crashes out on me and i have to turn off the ignition.
Also Google is unable to grab my information, It recognizes me and goes through the 2 step verification but gets stuck after accepting agreement, the Gathering Information shows up on screen and then it just loads indefinitely until either the system or the app crashes.
now i'm not sure if these are one and the same issue but do seem very similar, Like once it has an internet connection it is trying to do a background connection to google to pull data but its getting stuck and crashing out again.
So the only way i'm able to use the system is to put it in airplane mode otherwise it crashes and makes the stereo unusable altogether.
So i have contacted Seicane in regards to this issue and awaiting a reply but figure i may have more luck talking with a community of people that know what they are on about.
So i'm going to say i probably need some kind of system update from google and firmware for the system, but cant log into google without the firmware update.
The problem i'm having is i don't know what stereo it is as such..... if someone could help me with this then i may have more luck
I assume its a MTCD board, but is it a PX6 -5 -4 or 104? i have no idea. i don't know if its even a PX...?
any help on that would be GREAT as i may then be able to download the right updates for it and maybe solve this issue that i'm having.
That being said if anyone can take some time to try and help me i would greatly appreciate it.
I look forward to hearing from you.
MANY many thanks,
Frederus
My initial thought on this is that it is probably caused by a hardware fault in the unit, rather than being a software fault. My reason for saying this is that Seicane are a reasonably popular (ie used by many people) brand, and connecting to the internet is a fundamental function of these head units. If it were a software fault, I would expect to see many more users reporting this issue since the software is in fairly widespread use. Since this seems to be (on the surface at least) only happening to your unit, I suspect it is a hardware fault. It would be interesting to see what the manufacturer has to say when they get back to you. Good Luck!
Update
So i have an update for everyone with some Progress.
So after talking with Seicane they sent me a firmware update it was about six months out of date.
After installing this it seems to have helped with the continues crashing issue i was having.
that being said i then lost a few apps like
Netflix, Spotify and my DAB+ app
They also sent me some APK's for Google services and login services, [This didn't make any difference to my login hanging issue]
So i got back to Seicane and informed them of what had transpired along with a short video of what was happening so that they could see this first hand
They got back to me by the morning and sent me the link for the DAB+ apk so i could reinstall and also forward me another set of apk's
Google Services
Login Services
Google Play Store.
i have given these a go this morning,
DAB+ is back and working
Google Services - No difference
Login Services - No difference
Google Play Store. - No difference
I have just sent them another email saying that this hasn't made any difference and await there reply.
After doing some searching i noticed a lot of people have this issue of google getting stuck on "gathering Info" on there smart phones
which is usually a Cache issue, so i will try this once i'm in my car again.
I would attach the link to the firmware update that they sent me for others who may have the same issue, but i am unable to at this moment in time due to forum limitations for new users.
Ill keep everyone informed as and when i have more information.
Update [Solved]
So its been a week or so,
Quick update after going backwards and forwards with tech support at Seicane it turns out it was a combination of the outdated APK and the fact that google was stuck due to an error with the cache, from what i can tell at least,
So in the end i removed all of the google services from the head unit and deleted the caches as well. then forced it to restart and reinstalled Google login services.
This seems to have worked and i'm not having this issue any longer.
That being said i do have an issue where it doesn't want to turn on very occasionally, but this is on a very rare basis and isn't really a problem usually just have to power down the car and reset ignition. except once where i had to hit the reset button, but 99% of the time it is now working fine.
I hope this helps someone who has the same or similar issue.
Fred.