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.
Firstly, hopefully I receive a fix because this is annoying.
My issue is my edge plus reboots whenever I use Google Chrome its constant no change, if I open the app my phone reboots point blank. Also, at the same time this started my microphone died for no reason. I haven't done anything crazy software wise that I haven't had previously installed from week 1 of having this phone. There has not been any drops or any physical factors that could of triggered this. I have tried all the possible standard fixes cache,wipe, full wipe. My last try is unroot and go stock which means I can't use the phone so that try is pointless for me(928T unlocked for AT&T) no root = no unlock = expensive paperweight.
My phone is the T (tmobie variant) I rooted and unlocked it after buying it practically brand new second hand. This has ran with no issues for about 5 months until a few few days ago. Both of these issues occurred almost simultaneously but I can't see how they can be connected.
Venting .... Every android (Samsung) I have owned I have had to do surgery on. Note 2, Note 3, Note 4 all required new USB charging port replacement after a yr. Now this Edge Plus has issues and the build quality is nice but not inspiring for the novice phone surgeon I think I am. I hate to say it but if I can't find a fix I will have no choice but to convert to Apple.
Hi.
comming from Samsung galaxy s7 edge, bought a new LG G6 H870.
is there any down side for unlocking the bootloader/rooting the device?
on samsung we have the knox indicator and once you unlock the boot loader, the knox indicator is tripped and there is no way to reset that.
it affect allot of security features(banking apps fingerprint logging etc)
so, if i want to root the device to run certain apps, will i have to consider anything else being affected?
Rooting ain't what it used to be.
In the prehistoric Android days rooting was needed to get rid of the excessive crapware supplied by you mobile provider.
Buying an unlocked phone was nonexistent so drastic measures were needed by the device owners.
Today crapware still exists but is not quite so controlling of the device.
Unlocking the bootloader and rooting prevents updates from updating, some apps won't function such as Android pay, Netflix, Some banking apps.
The hassle of messing with a device and loss of some of the device features just isn't worth it.
On the LG G6 you will "earn" a warning boot screen and loose the garanty for errors related to the root/bootloader unlock/custom rom.
Apart from that the Gear S3 is no longer working, as the Gear App does not work. My Banking App (Banking 4A) and the fingerprint is working fine.
I do need root for some gaming tools.
Hey,
So the thing when the phone had stock rom and everything it worked perfectly until one moment when the device decided to present messages such as:
(the name of the app/service) stopped working. It was like this for a long time so I decided to change rom. SO basically I tried to put every single rom out there, none of them worked except resurrection one that eventually had problems too.
The phone was never dropped or something like that, and when the problem appeared I took the phone to the lab and that said they "fixed" it, they didn't.
So my question is, what is the possible problem for this annoying shutting down, deleting apps on its own and only one possible working rom?
Feel free to help
Do any apps utilise data from the micro SD card?
If that fails or failing can cause issues that your experiencing
Just a thought
Sent from Samsung S7 Edge [Oreo]
Hey there;
Sprint S10+, 128GB version. After every update, the Galaxy Store uninstalls itself. It becomes a com.sec.etc... item and only comes back up when I install a random build of Galaxy Apps over it, which in turn updates to Galaxy Store. Except the most recent update, which unfortunately landed me in an old Galaxy Apps version that will not update itself. Any idea what may cause this kind of behavior?
I haven't done much on the phone, so a factory reset wouldn't hurt my feelings terribly; I would love to avoid doing this, however. I did use SmartSwitch, though this didn't have the battery-killing side-effect that seemed to plague most Samsung users. Is this perhaps the culprit?
If it is, and a factory reset is needed.. Is there an easy / quick way to back up the important "stuff" without using SmartSwitch? I assume backup and restore from Google or Samsung Cloud is safe?
Thanks!