Was just changing my settings when I realized my version had changed.
Haven't noticed any front facing changes thus far but only got to look at it for a couple of seconds.
I've had it on mine for almost two weeks. I don't know what has changed.
I have had it too for a while, not really noticed any difference, except maybe Screen Mirroring MIGHT (though it is completely possible it is placebo) be less laggy.
Dan
Sent from my Nexus 7 using XDA Free mobile app
From the looks of it there are some WiFi driver changes in the kernel, as well as some changes to how eureka_shell loads its whitelist (it no longer has many apps pre-assigned in the /apps.conf file, and now seems to be mainly web driven)
ddggttff3 said:
From the looks of it there are some WiFi driver changes in the kernel, as well as some changes to how eureka_shell loads its whitelist (it no longer has many apps pre-assigned in the /apps.conf file, and now seems to be mainly web driven)
Click to expand...
Click to collapse
Does that mess with Eureka in any significant way?
Asphyx said:
Does that mess with Eureka in any significant way?
Click to expand...
Click to collapse
nope
ddggttff3 said:
nope
Click to expand...
Click to collapse
Will there be an update to Eureka or an updated stock with updates disabled ? I can not cast the BBC sports app with version 17250 on my 2 rooted Chromecast. Works fine on my none rooted 17977
revoxs said:
Will there be an update to Eureka or an updated stock with updates disabled ? I can not cast the BBC sports app with version 17250 on my 2 rooted Chromecast. Works fine on my none rooted 17977
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2638103
I hope to have 17977 posted there, and a Eureka ROM version soon. Still working on testing the ROM ATM.
Related
Through a lot of searching, trial and error, I finally got Netflix working on my Droid original version. I installed the netflix apk with device checking disabled (you can find it on this forum) and then made just 2 changes to my build.prop file. I set ro.product.model=Droid
and
ro.product.manufacturer=Motorola.
Success!!! So, wondering if I could do the same on my Gtab with Vegan-Tab. Installed the apk, changed the build.prop file and gave it a go.
Almost Success!!! The streaming actually works. I have tried all the other methods and never got the movie to stream. With this one it does.....problem is that it is running way to fast. The audio sounds like it must be 10 times faster than normal.
Another step.....sooner or later I'll find the secret.
If you used the version of the Neflix apk with the device check disabled you shouldn't have had to modify your build prop at all.
I installed it on my Droid X and it ran beautifully without any mods at all.
The device check only gets you as far as allowing the Netflix app to actually load completely. There is further wizardry involved to actually get streaming to occur. I can attest to the fact that I have tried at least 8 modifications of the build.prop file, with the only one allowing streaming to occur being the one that matches my Droid. Honest to goodness and cross my heart.
With disregard for the Netflix apk entirely, does Netflix allow streaming of their media directly from their website? Another words can you simply login to your web based account & access the media there?
I've never used Netflix & have no plans to join, but I figured if I could get the web version of Crackle to work when the Crackle.apk didn't then the same might hold true for Netflix. Of course it doesn't resolve the current problem but at the very least allows one to enjoy streaming until the issue is fixed.
droid x
Took the information posted earlier and, what do you know netflix on the droid x combinded with real hdmi lets make it a movie night.
BIG THANKS
EL TEJANO said:
With disregard for the Netflix apk entirely, does Netflix allow streaming of their media directly from their website? Another words can you simply login to your web based account & access the media there?
I've never used Netflix & have no plans to join, but I figured if I could get the web version of Crackle to work when the Crackle.apk didn't then the same might hold true for Netflix. Of course it doesn't resolve the current problem but at the very least allows one to enjoy streaming until the issue is fixed.
Click to expand...
Click to collapse
When I try to use it through the web browser, it wants me to install the Microsoft Silverlight plugin. No go.
Joeb2751 said:
When I try to use it through the web browser, it wants me to install the Microsoft Silverlight plugin. No go.
Click to expand...
Click to collapse
Hmmm..well that may change in the future then & hopefully it does:
http://thedroidguy.com/2011/04/microsoft-silverlight-coming-to-android-via-moonlight-dev-crew/
chipmunks
Finally got a movie to stream using your settings. Thanks! Same result though, sound is way too fast. After reading this thread http://forum.xda-developers.com/archive/index.php/t-954843.html
Thought about changing ro.board.platform= from tegra to whatever it is for the Droid. Do you know what is listed in the build.prop? Anyway thought it might be worth a try.
Im seeing the sped up video and sound as well here. Using the pre-packaged netflix apk on CM7 nightly 85.
maybe it's just me but when I went into the market today it said that there were updates available for netflix. I downloaded them and now when I run netflix it takes me to the "login" page instead of saying this device is not compatible.
fosser2 said:
maybe it's just me but when I went into the market today it said that there were updates available for netflix. I downloaded them and now when I run netflix it takes me to the "login" page instead of saying this device is not compatible.
Click to expand...
Click to collapse
They released an official update in the Market that doesn't do the device check. I don't know if that means it's wide open now for all android devices or not though for folks that have a Netflix account.
sjmoreno said:
They released an official update in the Market that doesn't do the device check. I don't know if that means it's wide open now for all android devices or not though for folks that have a Netflix account.
Click to expand...
Click to collapse
I saw that too and I got all excited. I do have an acct and could get to it. I can see my que but I can not still stream from there. It goes to the red loading screen but then dumps back out to the que. I have tried it several times. Still no. Close.. it seems.
glinraen said:
I saw that too and I got all excited. I do have an acct and could get to it. I can see my que but I can not still stream from there. It goes to the red loading screen but then dumps back out to the que. I have tried it several times. Still no. Close.. it seems.
Click to expand...
Click to collapse
Not working on Vegan 5.1.1
gTablet Vegan 5.1.1 with Pershoot's 2632.41 kernel
achernez said:
Not working on Vegan 5.1.1
gTablet Vegan 5.1.1 with Pershoot's 2632.41 kernel
Click to expand...
Click to collapse
Yea, I run Vegan v1 b511
sjmoreno said:
They released an official update in the Market that doesn't do the device check. I don't know if that means it's wide open now for all android devices or not though for folks that have a Netflix account.
Click to expand...
Click to collapse
It only added about 3 more phones to the list of approved devices. Install CM7 and all will be good.
glinraen said:
I saw that too and I got all excited. I do have an acct and could get to it. I can see my que but I can not still stream from there. It goes to the red loading screen but then dumps back out to the que. I have tried it several times. Still no. Close.. it seems.
Click to expand...
Click to collapse
Yep, same behavior for me after editing the build prop, running on Vegan 7 RC1, including after the market posted update to the apk.
drbomb said:
Finally got a movie to stream using your settings. Thanks! Same result though, sound is way too fast. After reading this thread http://forum.xda-developers.com/archive/index.php/t-954843.html
Thought about changing ro.board.platform= from tegra to whatever it is for the Droid. Do you know what is listed in the build.prop? Anyway thought it might be worth a try.
Click to expand...
Click to collapse
Sorry for the delay, have been on vacation. I will try that this evening and let you know the results.
Joe
tgruendler said:
It only added about 3 more phones to the list of approved devices. Install CM7 and all will be good.
Click to expand...
Click to collapse
My netflix running on CM7 about 2 days ago was working and now its not apparently because there is a new Netflix Update on the market.
Is there a reason why I can't search the Official Netflix App on the market using my GTAB? My build.prop is already modified to Nexus S. Maybe someone can post the Netflix APK since it is probably detecting my device as not supported.
Same here, using the new app, starts loading, flashes briefly, then back to the queue. Just installed flash 10.3 ,still no go.
On the gtab, ocd
Sent from my UPC300-2.2 using XDA Premium App
samlot said:
My netflix running on CM7 about 2 days ago was working and now its not apparently because there is a new Netflix Update on the market.
Is there a reason why I can't search the Official Netflix App on the market using my GTAB? My build.prop is already modified to Nexus S. Maybe someone can post the Netflix APK since it is probably detecting my device as not supported.
Click to expand...
Click to collapse
Droid-life had a link to the app. I grabbed the one off my phone I grabbed from the market. It didn't work on CM7.02 but I updated to CM7.03 and it works fine. No build.prop edits or anything needed.
Sent from my Viewsonic 10" GTab...CM7 style...
Just tried to cast the whole screen today from chrome dev version and it doesn't work. It used to work some time ago. Tried lots of thing and then figured that this feature is not working on beta or dev versions of chrome. Anyone else having this issue?
Thanks.
d3xt3rlab said:
Just tried to cast the whole screen today from chrome dev version and it doesn't work. It used to work some time ago. Tried lots of thing and then figured that this feature is not working on beta or dev versions of chrome. Anyone else having this issue?
Thanks.
Click to expand...
Click to collapse
I've this problem too
Same problem here on my Sammy ARM Chromebook...(Beta not Dev)
d3xt3rlab said:
Just tried to cast the whole screen today from chrome dev version and it doesn't work. It used to work some time ago. Tried lots of thing and then figured that this feature is not working on beta or dev versions of chrome. Anyone else having this issue?
Thanks.
Click to expand...
Click to collapse
Yeah... I have the same issue.
Hi all, chromecast is on build 17977 eureka , keep coming up with
Oops, we are having issues updating your chromecast to the latest
version. Some features may not work. Visit chromecast.com/update
to get help.
How do i resolve this problem? ,currently no longer able to
Cast screen.
Your Ever Faithful Servant!!
Grassden
P.S. Did a reboot from eureka setting page, it show chromecast background
then came up the Oops message , impresume from google?
grassden32 said:
Hi all, chromecast is on build 17977 eureka , keep coming up with
Oops, we are having issues updating your chromecast to the latest
version. Some features may not work. Visit chromecast.com/update
to get help.
How do i resolve this problem? ,currently no longer able to
Cast screen.
Your Ever Faithful Servant!!
Grassden
P.S. Did a reboot from eureka setting page, it show chromecast background
then came up the Oops message , impresume from google?
Click to expand...
Click to collapse
im able to use everything fine,
can cast from PC, and mobile etc ..
i have 4 chromecasts, 3 on the new hubcap exploit and one on the older exploit all doing the same thing for the last 2 days
one is a developer registered device and 3 are just normal and all 4 of them keep showing the "opps issues updating screen"
i have tried different whitelist sources and disabled/enabled updates on the team eureka web panel and nothing stops them from getting this message
the chromecasts still work and allow me to cast apps and mp4's and stuff to them, it seems its just the google/chromecast homescreen that drops out and shows this message
More info
Hi all, thanks for replys, here my info on my chromecast,
Eureka 17977.001 (24/07/2014)
Internet: Available
Serial: 342101ZLXGX
Settings page is eureeka rom and all enable , whitelist is eureka
Question 1. Would a force check update in debug page solve the issue ? (Reason i asked is basically iv not got the
Knowledge to know if that would help!) Chuckles
2. Cast screen on my samsung s4 (i9505 model) stop working after oops message appears.
Your Ever Pathetic Servant
Grassden
I experience the same problem.
For anyone else also dealing with this, please note that the Chromecast does work, it's simply the homescreen that displays this instead of the usual photos.
Solved!?
Hi all, hmm did a restart on my i9505 phone , did a cast screen and it eorking!!
But still we still have to understand where,how to resolve the oops message on starting chrmecast.
Yours Ever Pathetic Servant
Grassden
My CC imported from Amazon US during the short sales glitch window, rooted since day 1, OTA turned off in Eureka settings, now sowing oops screen instead of images?
I have the same issue.
Running the latest build from Eureka with OTA turned on.
heres a question, are those slideshow pics it normally displayed, local? or actually from google themselfs !?
if so surely it via that... detects not on correct firmware so send that screen instead ?
miniminus said:
heres a question, are those slideshow pics it normally displayed, local? or actually from google themselfs !?
if so surely it via that... detects not on correct firmware so send that screen instead ?
Click to expand...
Click to collapse
I have not yet seen this message on my unit but it does suggest that something about the default screen (which DOES load it's pictures rom Google Servers) Is doing some Version checking and reporting that your version is not up to date with what Google has as the latest ROM...
As long as the unit continues to work it shouldn't be a problem.
And once Team Eureka does a full EOD of the latest update and sends it to us this problem and message will probably go away.
EDIT: I'm not up to date, clearly. Thanks, minimus.
simonklit said:
Been looking a bit around. It seems that if you disable Team Eureka OTA Updates in the web-panel, then the message disappears, and the old photos are back.
Click to expand...
Click to collapse
then you missed the msg from the devs, saying just reboot the CC several times, and it will sort it self out ...
(which in effect happerned when you adjust the setting as you did.. the CC rebooted etc ..making it appear tthat ytou have to do that to fix it,
whenl all you needed to do was just a reboot !)
miniminus said:
then you missed the msg from the devs, saying just reboot the CC several times, and it will sort it self out ...
(which in effect happerned when you adjust the setting as you did.. the CC rebooted etc ..making it appear tthat ytou have to do that to fix it,
whenl all you needed to do was just a reboot !)
Click to expand...
Click to collapse
Definitely missed that one. Thanks!
Same here!
simonklit said:
Definitely missed that one. Thanks!
Click to expand...
Click to collapse
Hi all , Chuckles i second that thought! Never saw any news about the issue on feedly. (It just collects android news in general.) Which is usually where i get on my bit and pieces of knowledge on android basically, so curious as to how many chromecasts were affected by the issue?
Your ever pathetic servant
Grassden
grassden32 said:
Hi all , Chuckles i second that thought! Never saw any news about the issue on feedly. (It just collects android news in general.) Which is usually where i get on my bit and pieces of knowledge on android basically, so curious as to how many chromecasts were affected by the issue?
Your ever pathetic servant
Grassden
Click to expand...
Click to collapse
It was only happening on rooted devices running Eureka Rom which is why you probably didn't hear much about it other than here
This may be a known issue, but up until yesterday I thought it was only me.
Screen casting on any cyanogen ROM ends immediately after connection. Seems to happen regardless of cm ROM (cm12, cm11, resurrection, liquid) or device (moto x, bionic, kindle fire).
Is there a workaround?
metaljr81 said:
This may be a known issue, but up until yesterday I thought it was only me.
Screen casting on any cyanogen ROM ends immediately after connection. Seems to happen regardless of cm ROM (cm12, cm11, resurrection, liquid) or device (moto x, bionic, kindle fire).
Is there a workaround?
Click to expand...
Click to collapse
Might be your device? I'm running cm11 and broadcast to my chromecast just fine.
93Akkord said:
Might be your device? I'm running cm11 and broadcast to my chromecast just fine.
Click to expand...
Click to collapse
He is refering to the Cast Screen feature.
It is not working on any CM roms.
crashtheface,
Thank you! This has been driving me nuts the last few days.
I have a Sprint SGS3 (SPH-L710) running CM11 (cm-11-20141008-SNAPSHOT-M11-d2lte).
This one did not work for me:
http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193
I just got this one to work, but it is very laggy. It take 6 to 7 seconds to refresh the screen each time I switch apps.
https://play.google.com/store/apps/details?id=com.mobzapp.screenstream
I am really surprised that CM11 does not have screen mirroring to ChromeCast already built in.
I suspect is may be hardware related.
Thx...
crashtheface said:
He is refering to the Cast Screen feature.
It is not working on any CM roms.
Click to expand...
Click to collapse
Yup, cast screen worked for me just fine as well. No issues. Guess I'm lucky then
JM-PDA said:
crashtheface,
Thank you! This has been driving me nuts the last few days.
I have a Sprint SGS3 (SPH-L710) running CM11 (cm-11-20141008-SNAPSHOT-M11-d2lte).
This one did not work for me:
http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193
I just got this one to work, but it is very laggy. It take 6 to 7 seconds to refresh the screen each time I switch apps.
https://play.google.com/store/apps/details?id=com.mobzapp.screenstream
I am really surprised that CM11 does not have screen mirroring to ChromeCast already built in.
I suspect is may be hardware related.
Thx...
Click to expand...
Click to collapse
It doesn't seem to currently be hardware related.
All my devices run cast screen fine with AOSP stock 4.4.2 and 4.4.4 roms. However when going to say SlimKat, CM, or other 3rd party roms it fails.
#MirrorEnabler – CM11 KK 4.4 fix! (Well this worked for me)
On my nook HD plus running PacRom RC3 cm11 4.4.4
With root access (I used X-plorer)
Step 1:
Go to "/data/app-lib/com.r3pwn.mirrorenabler-1/"
Copy the 2 files
"libaudiopolicyconf.so" and "libhackyworkaround.so" to this directory "/data/data/com.r3.pwn.mirrorenabler/"
Step 2:
Go to "/data/app-lib/" and copy "com.google.android.apps.chromcast.app-1" into "/data/data/com.google.android.apps.chromecast.app/"
step 3: apply mirrorenabler settings and reboot....
krypticn said:
#MirrorEnabler – CM11 KK 4.4 fix! (Well this worked for me)
On my nook HD plus running PacRom RC3 cm11 4.4.4
With root access (I used X-plorer)
Step 1:
Go to "/data/app-lib/com.r3pwn.mirrorenabler-1/"
Copy the 2 files
"libaudiopolicyconf.so" and "libhackyworkaround.so" to this directory "/data/data/com.r3.pwn.mirrorenabler/"
Step 2:
Go to "/data/app-lib/" and copy "com.google.android.apps.chromcast.app-1" into "/data/data/com.google.android.apps.chromecast.app/"
step 3: apply mirrorenabler settings and reboot....
Click to expand...
Click to collapse
You don't need it anymore. Google updated chromecast app. Any devices running 4.4.2 should have mirroring enabled by default. I didn't try it on my nook yet, but I think it'll work without this app.
I could only cast for about half a sec. than it would immediately disconnect on both 4.3 and 4.4 PAC-Rom but by doing the above I was able get screen cast to work.
Sent from my BN NookHD+ using XDA Free mobile app
Based on my recent experience, it wasn't working for me on CloudyG3 1.2 (didn't try 2.0 yet - it was connecting and immediately disconnecting, with few tries results into dark screen on Chromecast), however on Darkobas PSD (ParanoidSabreDroid) Lollipop ROM (AOSPA rom) working without any issue and really very fast. (http://forum.xda-developers.com/lg-g3/development/rom-darkobass-psd-rom-dark-material-t2978382) (sorry, al LG G3 - D855 ROMs)
crashtheface said:
He is refering to the Cast Screen feature.
It is not working on any CM roms.
Click to expand...
Click to collapse
Works fine for me on CM12 !! Works flawlessly like a charm !!
tharmor said:
Works fine for me on CM12 !! Works flawlessly like a charm !!
Click to expand...
Click to collapse
hmm I'm wondering if the devs working on your motoG CM12 branch implemented it? I have yet to hear of any other CM builds where this has been successfully implemented.
crashtheface said:
hmm I'm wondering if the devs working on your motoG CM12 branch implemented it? I have yet to hear of any other CM builds where this has been successfully implemented.
Click to expand...
Click to collapse
It works on stock as well on Moto G !!! So should work on CM 12 !! Mine is galaxy grand duos and moto G and it works fine for me !!
tharmor said:
It works on stock as well on Moto G !!! So should work on CM 12 !! Mine is galaxy grand duos and moto G and it works fine for me !!
Click to expand...
Click to collapse
Are you sure you aren't refering to basic cast from App?
I'm talking about Cast Screen, the beta feature which DIRECTLY MIRRORS YOUR HANDSET SCREEN to your chromecast.
You may be confused as there are literally no reports or success stories of CAST SCREEN and not Google Cast.
They are two completely different things we are discussing screen mirroring in this thread.
crashtheface said:
Are you sure you aren't refering to basic cast from App?
I'm talking about Cast Screen, the beta feature which DIRECTLY MIRRORS YOUR HANDSET SCREEN to your chromecast.
You may be confused as there are literally no reports or success stories of CAST SCREEN and not Google Cast.
They are two completely different things we are discussing screen mirroring in this thread.
Click to expand...
Click to collapse
Watching your mobile screen on Chromecast !! Hope this is clear to you now !! Yes i am talking about screen mirroring dude !!
CM12 is on my Galaxy grand and not moto G yet !!
tharmor said:
Watching your mobile screen on Chromecast !! Hope this is clear to you now !! Yes i am talking about screen mirroring dude !!
Show some respect !!
Click to expand...
Click to collapse
just making sure friend. there has been confusing from time to time
what exactly was your method? I see two cast icons in your notifications area.
Also can you link me to your rom page on xda? I would like to contact the devs who did the build to see if they had manually changed anything to allow for cast screen.
I'm excited to go back to CM if I can get Cast screen working on my devices with Cyanogenmod.
crashtheface said:
just making sure friend. there has been confusing from time to time
what exactly was your method? I see two cast icons in your notifications area.
Also can you link me to your rom page on xda? I would like to contact the devs who did the build to see if they had manually changed anything to allow for cast screen.
I'm excited to go back to CM if I can get Cast screen working on my devices with Cyanogenmod.
Click to expand...
Click to collapse
Check with @pawitp here on xda .... He is a legend for our phone !!
Second notification was from dailymotion which I did not close when i started screen cast !!
tharmor said:
Check with @pawitp here on xda .... He is a legend for our phone !!
Second notification was from dailymotion which I did not close when i started screen cast !!
Click to expand...
Click to collapse
ah he does not accept private messages. can you link me to the thread pertaining to your rom?
crashtheface said:
ah he does not accept private messages. can you link me to the thread pertaining to your rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2942255
tharmor said:
http://forum.xda-developers.com/showthread.php?t=2942255
Click to expand...
Click to collapse
cheers!
Hi all, someone had problems with mirroring phone with chromecast? App like youtube are ok, but total mirroring disconnects instantly.
With one plus 3 (not T) all was ok.
Ty
Simone365 said:
Hi all, someone had problems with mirroring phone with chromecast? App like youtube are ok, but total mirroring disconnects instantly.
With one plus 3 (not T) all was ok.
Ty
Click to expand...
Click to collapse
I will have to try this when I get home and I will let you know
Seems to be a bug from SO. Many people is complaining about this in the official OnePlus community.
mikeazores said:
Seems to be a bug from SO. Many people is complaining about this in the official OnePlus community.
Click to expand...
Click to collapse
ah nice, i didn't find anything. Thank you for the info.
I have the same problem... I don't know what to do...
same problem here - 1+3t see my chromecast device , attempts to connect and... thats all
I've not screwed around with this problem much since I don't "cast screen" aside from netflix which works (as said here). I did some screen casting from CM in the past, But::
I've experience the identical symptoms of this problem on CM13, CM14, etc, with their built in cast command. I don't know if it'll be identical or of any help, but I had to get rid of all of the /system partition based "cast" (whatever it's called in this version), from /system/apps ./priv-apps and other /system-like places..
When you are sure you've got it all gone, using root explorer or adb or whatever you prefer (of course, you have to be rooted) , then reboot, then install Google Home(chromecast) from the play store. That worked fine in the CM's. I'll see if I can dig up the correct file names & folders that apply to this version and get back to this thread if I do.
I'll be happy to be the guinea pig, so don't do this unless you want to take a chance on screwing up your phone, until I report back.
Edit 1: Of course, the 3t does it differently. They're using all /data spaces for the cast, and since I've installed "google home" I have to get rid of it first to figure out which files remain. Here is what there is right now, not that there is anything worth doing with it unless I've uninstalled Google Cast via play store:
/data/data/com.google.android.gms/cache/cast_mirroring_raw_events.log.gz
/data/data/com.google.android.gms/shared_prefs/google_cast.xml
/data/data/com.google.android.gms/shared_prefs/PREF_CAST_SENDER_ID.xml
/data/data/com.google.android.gms/shared_prefs/CastDeviceCache.xml
/data/data/com.google.android.gms/shared_prefs/CAST_ACTIVE_NETWORK_MAP.xml
/data/data/com.google.android.gms/shared_prefs/googlecast-setting-prefs.xml
/data/data/com.google.android.gms/shared_prefs/PREF_CAST_SENDER_NONCE.xml
/data/data/com.google.android.gms/app_sslcache/cast.google.com.443
/data/data/com.google.android.apps.chromecast.app
/data/data/com.google.android.apps.chromecast.app/shared_prefs/com.google.android.apps.chromecast.app_preferences.xml
/data/app/com.google.android.gms-1/lib/arm64/libgcastv2_base.so
/data/app/com.google.android.gms-1/lib/arm64/libgcastv2_support.so
/data/app/com.google.android.gms-1/lib/arm64/libjgcastservice.so
/data/app/com.google.android.apps.chromecast.app-1
/data/dalvik-cache/profiles/com.google.android.apps.chromecast.app
Click to expand...
Click to collapse
And a log of cast from settings:
same problem but I am happy that Netflix and Spotify works.