I have done searches here and in AT&T HTC One forum, did not see anybody had the same issue, which is sad (well, for me :silly
When trying to play any purchased or free movies or TV show episode, getting "There was a problem while playing [31]. Touch to retry" error message. After few consequent retries movie could start, but if paused, will not play again, also if rewound or fast forwarded, will not restart.
I cleared memory from Google Play, Google Play Movies, Google Play Services, restarted the phone (in long mode too), nothing helps.
Google Play support is useless, their answer is ridiculous: "Please restart the device, if after restart it still won't play, this device is incompatible with Google Play Movies at this time. Thanks, Martin, Google Play support". These guys are just have a robot replying with copypasted text without even knowing what device is in question. Should I tell HTC their flagship device is "incompatible with Google Play Movies at this time"?
If anybody saw this issue before and knows how to fix, please, help!
Sorry, if it was already discussed, I made several searches and read this forum to page 30, till got tired
Nobody else has this issue? That's really sucks
EugeneR said:
Nobody else has this issue? That's really sucks
Click to expand...
Click to collapse
I'm right there with you. I've been playing with my new HTC One Developers Edition for a few days and have the exact same issue as you've described. I fired up my Nexus 4 and couldn't get it to error out even once.
I may just give up on the movies from Google play until HTC can fix this.
I have this same problem. Although, I'm using a tmobile One.
Sent from my HTC One using xda premium
Same issue in the UK on sim free 32gb
Same issue here. AT&T 32 gig.
Ok, at least I see some others having same issue with non-US, ATT. TMO phones in both 64 GB and 32. Means the problem is not isolated to one modification or one operator.
Assuming the issue is with HTC firmware. Maybe (just a wild guess) related to the issue HTC can't recognize (can't see) some files downloaded from network with some tools e.g. ES File Explorer, somehow when the video is being cached the Google Play Movies application can't see it. Need to try something. So far I have one direction.
Since the problem exists even for files I make available offline from Google Play Movies, I am going to download one movie, then find it in temp directory it cached, connect my phone to the PC, and transfer it to the PC and back with USB. Then retry. Will report.
BTW, did anybody try HTC Support? Are they same level useless as Google Support?
[UPDATE] It did not work. Same error even though I checked the movie file is there (\Android\data\com.google.android.videos\files\Movies)
I've heard this is a problem caused by rooting the phone. Anyone here have their HTC One unrooted and on stock that can say they are or aren't experiencing this problem?
Sent from my HTC One using xda premium
sensationfan623 said:
I've heard this is a problem caused by rooting the phone. Anyone here have their HTC One unrooted and on stock that can say they are or aren't experiencing this problem?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I'm stock on my 64gb developer edition and mine Google play works fine.
Sent from my HTC One using xda app-developers app
ahernandez4110 said:
I'm stock on my 64gb developer edition and mine Google play works fine.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
So it probably has to do with being rooted.
Sent from my HTC One using xda premium
sensationfan623 said:
So it probably has to do with being rooted.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
This is not related to root. My HTC One Developer Edition unlocked, 100% stock not rooted or changed in any way (stock recovery too). Had this issue from day 1.
EugeneR said:
This is not related to root. My HTC One Developer Edition unlocked, 100% stock not rooted or changed in any way (stock recovery too). Had this issue from day 1.
Click to expand...
Click to collapse
This is unfortunately one of the side effects of using the Dev Edition. It also won't play movies and ther content purchased from HTC store. This is related to DRM security. I doubt it can be fixed. See below disclaimer to the Dev Edition from HTC website.
"Special note about the unlocked bootloader: With an unlocked bootloader, some content on your device may also be invalidated and cannot be accessed anymore because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC."
I have both the Dev Ed and AT&T version and the latter has no issues playing Google Play and HTC content.
jarek0423 said:
This is unfortunately one of the side effects of using the Dev Edition. It also won't play movies and ther content purchased from HTC store. This is related to DRM security. I doubt it can be fixed. See below disclaimer to the Dev Edition from HTC website.
"Special note about the unlocked bootloader: With an unlocked bootloader, some content on your device may also be invalidated and cannot be accessed anymore because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC."
I have both the Dev Ed and AT&T version and the latter has no issues playing Google Play and HTC content.
Click to expand...
Click to collapse
I can play a movie if it starts from the beginning (not always but it will work). If I try and stop the movie and restart from the stopped position I get the error 31. Also I had the Nexus 4 with unlocked boot-loader with root and I did not have this issue.
Also as of July of 2012 Google started allowing Play-movies on rooted device.
jdh10475 said:
I can play a movie if it starts from the beginning (not always but it will work). If I try and stop the movie and restart from the stopped position I get the error 31. Also I had the Nexus 4 with unlocked boot-loader with root and I did not have this issue.
Also as of July of 2012 Google started allowing Play-movies on rooted device.
Click to expand...
Click to collapse
Mine behaves the same way. It's definitely specific to the Dev Edition as my AT&T model works fine and it IS caused by unlocked bootloader on this specific model, as stated by HTC. The fact that your Nexus 4 doesnt exhibit the same bahavious is irrelevant. Obviously Google would not cripple their own device by making it incompatibile with Play store.
jarek0423 said:
Mine behaves the same way. It's definitely specific to the Dev Edition as my AT&T model works fine and it IS caused by unlocked bootloader on this specific model, as stated by HTC. The fact that your Nexus 4 doesnt exhibit the same bahavious is irrelevant. Obviously Google would not cripple their own device by making it incompatibile with Play store.
Click to expand...
Click to collapse
BUT I can play movies I just have a problem starting the movie again once I have stopped watching it. I'm on AT&T unlocked with root. I can download the movie I can stream the movie. As long as I start watching the movie and don't stop I am fine. But if I want to watch 30 minutes and then a few hours later try to watch the move again I have to start all over. YouTube is fine Netflix is fine.
jdh10475 said:
BUT I can play movies I just have a problem starting the movie again once I have stopped watching it. I'm on AT&T unlocked with root. I can download the movie I can stream the movie. As long as I start watching the movie and don't stop I am fine. But if I want to watch 30 minutes and then a few hours later try to watch the move again I have to start all over. YouTube is fine Netflix is fine.
Click to expand...
Click to collapse
Yep, mine exhibits the exact same behavior...
jarek0423 said:
This is unfortunately one of the side effects of using the Dev Edition. It also won't play movies and ther content purchased from HTC store. This is related to DRM security. I doubt it can be fixed. See below disclaimer to the Dev Edition from HTC website.
"Special note about the unlocked bootloader: With an unlocked bootloader, some content on your device may also be invalidated and cannot be accessed anymore because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC."
I have both the Dev Ed and AT&T version and the latter has no issues playing Google Play and HTC content.
Click to expand...
Click to collapse
Some content on your device. I do not have this content on my device. It is being streamed. Besides, if it was due to invalid DRM security keys, it would be not playing. Period. But it is inconsistently playing after several retries, or even from the first time. But does not renew the play after pausing. I am not convinced this is something caused by invalidity of DRM keys. I would rather think something in HTC firmware.
Nope, problem shows up intermittently on stock
sensationfan623 said:
So it probably has to do with being rooted.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I've got a 32gb AT&T HTC One which is completely stock and I've run into this problem (network error, try again later), both when I try to stream a HD movie AND with a downloaded HD movie (I haven't tried SD). The odd thing is when I tried it just now the downloaded HD movie played just fine; very snappy in fact and almost instantaneous seeking within the movie. I then purchased another HD movie as a test; that one streamed just fine. Although seeking wasn't quite as quick (which isn't unexpected) playback was fine.
Not sure if this helps or just confuses the issue, but that's my experience. I'll chime in again if anything changes (like it goes back to displaying network errors).
PS: the first time I tried this, the phone was connected to the HD Media Link I got w/ preorder. The problem persisted after I disconnected from the media link, but I wonder if the media link is the cause. I'll try hooking up to the media link after my wife gets done watching her shows to see if it works there.
I have the same issue on a 100% stock Developer Edition. After reading the posts in this thread, it seems like, collectively, the posters here have enough information to definitively answer two questions, but not all the information has been posted, so the answers are still unclear:
Several people in the thread have reported this issue on non-Developer Edition phones, but none of them explicitly state whether the phone is rooted or bootloader unlocked (except for the last poster, but he's reporting different error: "network error", not "There was a problem ... [31]"). If we can get confirmation that the error happens consistently on stock, locked, unrooted phones, that would rule out the "invalid drm keys" theory.
At least one poster claimed that Google Play Movies worked for them on the Developer Edition, but did not say whether they could stop and restart playback. Since the problem does not manifest unless playback is stopped and restarted, this is not clear evidence that movies play properly on some Dev Edition phones. In my case, I can pause and resume as long as Google Play Movies was the foreground app. If I switched to another app and then came back, I am unable to restart playback, and get the error 31. Anybody out there able to stop playback, switch apps, then switch back and resume playback on a Developer Edition phone?
Data point: Most or all of the HTC One reviews of the Google Play Movies app are 1 star, reporting that movies don't play back. Maybe this is widespread across HTC One models?
Assuming it really is an issue with DRM keys, does anybody know:
Will relocking the bootloader will restore the DRM keys?
What DRM keys are we talking about, and how are they generated, stored, and managed? The android DRM framework is plugin-based, but there's no way I know of (short of writing an app) to figure out what plugins are present; and even if we knew the set of plugins we wouldn't know what "type" Google Play is trying to use. It would really help to know, e.g., if there's a single set of keys that's mated to the phone somehow, and once they're gone they're gone, or whether you can generate a new set of keys that would at least work for newly purchased content, if not existing content. Are DRM keys invalidated when the bootloader is unlocked because they're erased, or because they're marked invalid somehow? Is the DRM key management fully or partially hardware based, or all done in software? Etc.
There's a notable lack of documentation for android.drm; it doesn't seem like it would really be useable without having documentation for the plugins on any given platform, and that doc doesn't seem to be available for HTC.
/dev/random said:
I have the same issue on a 100% stock Developer Edition. After reading the posts in this thread, it seems like, collectively, the posters here have enough information to definitively answer two questions, but not all the information has been posted, so the answers are still unclear:
Several people in the thread have reported this issue on non-Developer Edition phones, but none of them explicitly state whether the phone is rooted or bootloader unlocked (except for the last poster, but he's reporting different error: "network error", not "There was a problem ... [31]"). If we can get confirmation that the error happens consistently on stock, locked, unrooted phones, that would rule out the "invalid drm keys" theory.
At least one poster claimed that Google Play Movies worked for them on the Developer Edition, but did not say whether they could stop and restart playback. Since the problem does not manifest unless playback is stopped and restarted, this is not clear evidence that movies play properly on some Dev Edition phones. In my case, I can pause and resume as long as Google Play Movies was the foreground app. If I switched to another app and then came back, I am unable to restart playback, and get the error 31. Anybody out there able to stop playback, switch apps, then switch back and resume playback on a Developer Edition phone?
Data point: Most or all of the HTC One reviews of the Google Play Movies app are 1 star, reporting that movies don't play back. Maybe this is widespread across HTC One models?
Assuming it really is an issue with DRM keys, does anybody know:
Will relocking the bootloader will restore the DRM keys?
What DRM keys are we talking about, and how are they generated, stored, and managed? The android DRM framework is plugin-based, but there's no way I know of (short of writing an app) to figure out what plugins are present; and even if we knew the set of plugins we wouldn't know what "type" Google Play is trying to use. It would really help to know, e.g., if there's a single set of keys that's mated to the phone somehow, and once they're gone they're gone, or whether you can generate a new set of keys that would at least work for newly purchased content, if not existing content. Are DRM keys invalidated when the bootloader is unlocked because they're erased, or because they're marked invalid somehow? Is the DRM key management fully or partially hardware based, or all done in software? Etc.
There's a notable lack of documentation for android.drm; it doesn't seem like it would really be useable without having documentation for the plugins on any given platform, and that doc doesn't seem to be available for HTC.
Click to expand...
Click to collapse
Those are good questions. Hope users will be able to answer. So far it looks like there are not much Google Play Movies users on HTC One Dev Edition, so, the problem is not annoying enough people to blow up.
I was not able to get any support on the issue from Google Play neither from HTC. HTC blames Google, Google, naturally, blames HTC (I posted their answer earlier). No help, ho clue, no hope. How expectable from Google and HTC. I have never had good support from either of them.
Related
I was just playing around with the Movies app and noticed I can't seem to watch/download the licensed movies.
It's concerning the five free ones we received with the phone (they're the only ones I've tried at the moment). I redeemed them when I got the phone and at that time they downloaded and played just fine. Now though, when I tried to play one it said could not play video.
I deleted the file and thought I'd re-download to see if that helped but it now keeps saying 'Unable to get license' and won't download.
Just wondering if anyone else has had or seen a similar issue before?
i have a different problem, i can't remove video unlimited completely. even after uninstalling it, the movies app still loads video unlimited stuff.
DeaflyBlind said:
I was just playing around with the Movies app and noticed I can't seem to watch/download the licensed movies.
It's concerning the five free ones we received with the phone (they're the only ones I've tried at the moment). I redeemed them when I got the phone and at that time they downloaded and played just fine. Now though, when I tried to play one it said could not play video.
I deleted the file and thought I'd re-download to see if that helped but it now keeps saying 'Unable to get license' and won't download.
Just wondering if anyone else has had or seen a similar issue before?
Click to expand...
Click to collapse
sitting in the same boat as you. :crying:
xAjCx said:
sitting in the same boat as you. :crying:
Click to expand...
Click to collapse
Mine's all good again.
I'm not sure what exactly fixed the problem. Before noticing it was fixed I know I did both a factory reset and re-flashed a stock FTF file (for other purposes - I gave up on the license issue).
Maybe try one (or both) of those options and see if that helps (or maybe even running the repair through PC Companion)?
I've seen this with vGet, then Web Video Caster and now with the latest Netflix.
I'd seen this before with some apps, usually I switched to Netflix to get control and then disconnected from there.
The dev for Web Video Caster says he's using a Google library for the function and will contact Google after he checks further.
Latest Netflix - pause a show, disconnect, the show remains on the TV.
I wondered if this is widespread or not so I'm asking if others are seeing this.
I'm on the latest Chromecast version, stock.
i'm watching netflix right now on stock chromecast.
I have always had this problem since buying the chromecast in December, I have to cast YouTube to get out of netflix on both my htc one and my ipad. Are you by any chance using a dns service like unblock us? I am and Netflix said that could be the cause.
pandarock32 said:
I have always had this problem since buying the chromecast in December, I have to cast YouTube to get out of netflix on both my htc one and my ipad. Are you by any chance using a dns service like unblock us? I am and Netflix said that could be the cause.
Click to expand...
Click to collapse
Nope, I'm as vanilla stock, out of the box as you can get.
This just cropped up for me, been using Chromecast since August.
@gianptune - thanks, but doesn't answer the question.
Today (July 9th) Google has released the anticipated latest Chromecast app that would allow us to screen cast our phones to a TV. It's only available for a limited amount of phone, which our Note3s are supposed to be supported.
However, the Play Store only shows v1.5.5.
Can someone verify this?
Try this apk. It's version 1.7.4
http://www.mediafire.com/download/wqhdjkt4zdrnrk7/com.google.android.apps.chromecast.app-1.7.4.apk
I only have android 4.3 and it requires 4.4.1 or higher so I can't test it fully. It installs for me but no screencast feature found.
After my first post, and after searching the interwebs I finally found this 1.7.4 version.
After install, it does exactly what they advertised. It screen casts everything to the TV. To test, I played a video in full screen mode from my PGA Tour app, and it looked beautiful! Especially in full screen!
*Update* the Chromecast in the play store still only shows v1.5.5. Which is says it's been updated on July 9th (today), so I can only assume our wonderful Note3s will not get this updated version through the normal "official" channels.
I hope I'm wrong.
I saw that too. I went online though, and found a 1.7.4, but it's not casting. It doesn't even show my Chromecast on the device when I try to cast. It just shows "My Device". It does show up in the Chromecast app though.
Sent from where the wind begins....
Kamau54 said:
I saw that too. I went online though, and found a 1.7.4, but it's not casting. It doesn't even show my Chromecast on the device when I try to cast. It just shows "My Device". It does show up in the Chromecast app though.
Sent from where the wind begins....
Click to expand...
Click to collapse
Here is a link that might help:
https://support.google.com/chromecast/answer/6059461
lawalty said:
Here is a link that might help:
https://support.google.com/chromecast/answer/6059461
Click to expand...
Click to collapse
I searched that forum, and posted the problem, but with no answer. I have found though a couple others with the same issue, but they got no response to their questions either.
Sent from where the wind begins....
Just got a reply over in the Chromecast Help forums suggesting that my issue may be to being rooted, even though I'm still running the stock rom with a few bloatware frozen. They suggest unrooting my phone.
Just putting the solution out here for others. Personally, I'm not giving up my room just to Screencast.
Sent from where the wind begins....
Finally got the update notification from the play store a few hours ago. I'm currently rooted running DynamicKat 4.0
Says it version 1.7.4
Up until the most recent update, I have been able to share my screen to my Chromecast and then open NFL Mobile.
Now, it displays a message on my TV stating to disconnect my device in order to use it.
Is there a way to prevent this check.
Thought would be to root, and allow the screen cast service to work without the phone reporting this is being done.
Any help would be greatly appreciated.
Am I the only one that this affects?
Or do some people in this community use a custom Rom that avoids this issue. Any response would be greatly appreciated.
Yeah this sucks, hopefully someone will figure out a work around.
Sent from my SCH-I545 using XDA Free mobile app
kirbnite said:
Up until the most recent update, I have been able to share my screen to my Chromecast and then open NFL Mobile.
Now, it displays a message on my TV stating to disconnect my device in order to use it.
Is there a way to prevent this check.
Thought would be to root, and allow the screen cast service to work without the phone reporting this is being done.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Also having this issue and I am pretty pissed off about it. This was the only way for me to watch my beloved Denver Broncos out of network without paying over $100/month for tv I dont need or want.
kirbnite said:
Am I the only one that this affects?
Or do some people in this community use a custom Rom that avoids this issue. Any response would be greatly appreciated.
Click to expand...
Click to collapse
It's affecting everyone - /r/Chromecast/comments/2isxbo/nfl_mobile_no_longer_casts_video/ (I can't post links?)
The change appears to have gone into affect at least yesterday.
It went into affect the moment I updated the NFL Mobile app on 10/6/2014. I am thinking, something could be done. If ruining a custom ROM, couldn't there be a way to ensure what ever flagged is engaged when the Cast Screen sevice is used to always show as off, so nfl mobile does not know it is being used.
This also affects the Samsung Allshare media cast device. (Mirror mode on my Note 3).
kirbnite said:
It went into affect the moment I updated the NFL Mobile app on 10/6/2014. I am thinking, something could be done. If ruining a custom ROM, couldn't there be a way to ensure what ever flagged is engaged when the Cast Screen sevice is used to always show as off, so nfl mobile does not know it is being used.
This also affects the Samsung Allshare media cast device. (Mirror mode on my Note 3).
Click to expand...
Click to collapse
Makes sense. I did try the factory reset but the app says a new update is required...so I'm guessing rolling it back to the pre-10/6 version wouldn't work.
I believe a similar workaround was developed into custom ROMs for hiding HDMI connections but after searching online I can't find anything that references a similar cloak for the screen cast service.
Now, I am not opposed to rooting my phone and using some hdmi adapter. Anyone confirm if there is a ROM that allows the NFL Mobile to stream to the TV in any means necessary.
kirbnite said:
Now, I am not opposed to rooting my phone and using some hdmi adapter. Anyone confirm if there is a ROM that allows the NFL Mobile to stream to the TV in any means necessary.
Click to expand...
Click to collapse
Supposedly the play store app no longer has rooted phone detection, but that update was about a year ago - http://forum.xda-developers.com/showpost.php?p=45088481&postcount=244
kirbnite said:
Up until the most recent update, I have been able to share my screen to my Chromecast and then open NFL Mobile.
Now, it displays a message on my TV stating to disconnect my device in order to use it.
Is there a way to prevent this check.
Thought would be to root, and allow the screen cast service to work without the phone reporting this is being done.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm far from an expert on this matter, but it seems to me it has something to do with the permissions enabled by the NFL Mobile app. With screen cast/mirroring, you connect these devices wirelessly and you may need to cloak this connection in order to throw off the NFL app? In any event, I'm having the same issue and was hoping someone could help.
A work around includes an app called screen stream mirror. NowI don't have the link to it, but it requires root. It can be used with a chrome cast to allow you to watch video which you normally wouldn't be able to. Cost is $5.00.
What's this teensie I've read about? Hacking your chrome cast, anyone heard about it?
Thank You. I will be making some modifications
Re:
NFL mobile app now checks to see if the phone has been rooted and/or has the developer options turned on. In either case it will not allow streaming to a bigger screen. Back in August 2014 they banned rooted phones altogether from watching preseason games, then because of an outcry, they have allowed them back in partially to watch from the phone but not project onto a big screen. They also have put a DRM protection in so you cannot set up a mock location with a gps spoofer app.
No audio with the "Screen stream mirror" app.
Sent from my SCH-I545 using XDA Free mobile app
Bradleyd444 said:
No audio with this app
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
It works. If you are rooted, it stands the audio. If not, microphone. Either way, Just enable it in the settings.
kirbnite said:
It works. If you are rooted, it stands the audio. If not, microphone. Either way, Just enable it in the settings.
Click to expand...
Click to collapse
I am rooted, I did enable system sounds but it does not work.
Sent from my SCH-I545 using XDA Free mobile app
Email the developer. They will work with you.
If your audio does not work, I would assume 1 of 2 things.
1. Your media volume on your phone is turned all the way down.
2. Running a custom ROM that is interfering with how the application works.
Does the audio fall to transmit with every application you open on your phone?
Galaxy S4 Google Play Edition, audio plays on the phone but does not cast with the video, have not tried other apps.
Sent from my SCH-I545 using XDA Free mobile app
no sound
I have a Verizon Galaxy S4 and had the same problem. The recommendation that worked for me was rebooting the Chromecast - just unplug then reconnect the power to the Chromecast unit, wait for it to cycle back up and try again.
Seems like a stupid question, but yes I bought a 2213 EU version, unlocked the bootloader, rooted it the right way, did everything to pass safety net, device is play protect registered, getprop ro.boot.verifiedbootstate returns green, Google Pay works fine after root, DRM Info shows Widevine L1
Netflix won't install (not compatible with device)
HBOMax won't play
Peacock won't install
Hulu won't install
Is this possibly a OnePLus bug on the new NE2213_11_A.15 build, some new rooting thing with Android 12, bad luck, or is there some solution that I need to install?
I may be haded right back to the trusty OnePlus 8 Pro....which has none of these issues and has the Macro Camera which I actually miss....
Thanks in advance for any suggestions....
Also, if anyone in the US needs dual SIM, the EU versions supports all the US bands (and more), is dual SIM, and works flawlessly with T-Mobile...5G, VoWiFi, everything.
Same thing for me, i live in Sweden and we have Cmore & Discovery here that refuse to play after bootloader unlock and root, no magisk hide solution have worked for me. Maybe bootloader unlock with no root works, but cant try because my OP10 is bricked. My old OP9 was working perfect with all the streaming, i now have Xiaomi 12 Pro and was afraid the same thing would happend with this phone, only unlocked bootloader on this phone but no root and everything works 100%, streaming apps, gpay.
It just seems there is something wrong here in the way that OnePlus certified this device. Other Android 12 devices can be rooted without all these issue, right?
Can people US or Chinese / Indian versions get rooted and have access to the Streaming services?
MetroWestMA said:
It just seems there is something wrong here in the way that OnePlus certified this device. Other Android 12 devices can be rooted without all these issue, right?
Can people US or Chinese / Indian versions get rooted and have access to the Streaming services?
Click to expand...
Click to collapse
I have Hulu Disney plus and Netflix working but only play when streamed to my Chromecast. On device play doesn't work and only plays L3 even though device reads L1. Believe it's to deal with bootloader unlock and not root. But others posted that it was a OnePlus issue and was supposed to be resolved but hasn't been.
toolhas4degrees said:
I have Hulu Disney plus and Netflix working but only play when streamed to my Chromecast. On device play doesn't work and only plays L3 even though device reads L1. Believe it's to deal with bootloader unlock and not root. But others posted that it was a OnePlus issue and was supposed to be resolved but hasn't been.
Click to expand...
Click to collapse
It's a issue with this particular Snapdragon chip. The Samsung Galaxy Tab S8 uses the same processor and has the exact same problem.
g96818 said:
It's a issue with this particular Snapdragon chip. The Samsung Galaxy Tab S8 uses the same processor and has the exact same problem.
Click to expand...
Click to collapse
How can it be the chip. It could be the kernel associated didn't have correct commits from snapdragon. But still the drm is in the secure partition on our device that can't be altered also.
toolhas4degrees said:
How can it be the chip. It could be the kernel associated didn't have correct commits from snapdragon. But still the drm is in the secure partition on our device that can't be altered also.
Click to expand...
Click to collapse
Not sure, but that's the only common link between both devices from different manufacturers. They're basically using the same work around we are. I'll be testing it out shortly also since my S8 was just delivered.
It is just fundamentally blocking anything having to do with DRM. You can't even spoof the user agent and watch any streaming service through a browser -- it ask if the browser can play secure content (you say yes) and then gives an error. I am not even that much of a TV / Movie guy, but to be 100% blocked from any streaming just for rooting a device you own????
Pretty F&*^in extreme if you asked me....
The only question is do I wait for someone to hack it (if that's even possible), or do I just go back to my trusty OP 8 Pro and sell this...?
Are there any Android 12 rootable phones that don't have this issue...or is it all Android 12 phones?
MetroWestMA said:
It is just fundamentally blocking anything having to do with DRM. You can't even spoof the user agent and watch any streaming service through a browser -- it ask if the browser can play secure content (you say yes) and then gives an error. I am not even that much of a TV / Movie guy, but to be 100% blocked from any streaming just for rooting a device you own????
Pretty F&*^in extreme if you asked me....
The only question is do I wait for someone to hack it (if that's even possible), or do I just go back to my trusty OP 8 Pro and sell this...?
Are there any Android 12 rootable phones that don't have this issue...or is it all Android 12 phones?
Click to expand...
Click to collapse
i think it's a snapdragon issue rather than software issue.
MetroWestMA said:
Seems like a stupid question, but yes I bought a 2213 EU version, unlocked the bootloader, rooted it the right way, did everything to pass safety net, device is play protect registered, getprop ro.boot.verifiedbootstate returns green, Google Pay works fine after root, DRM Info shows Widevine L1
Netflix won't install (not compatible with device)
HBOMax won't play
Peacock won't install
Hulu won't install
Is this possibly a OnePLus bug on the new NE2213_11_A.15 build, some new rooting thing with Android 12, bad luck, or is there some solution that I need to install?
I may be haded right back to the trusty OnePlus 8 Pro....which has none of these issues and has the Macro Camera which I actually miss....
Thanks in advance for any suggestions....
Also, if anyone in the US needs dual SIM, the EU versions supports all the US bands (and more), is dual SIM, and works flawlessly with T-Mobile...5G, VoWiFi, everything.
Click to expand...
Click to collapse
How did you get widevine L1 after bootloader unlock?
devtherockstar said:
How did you get widevine L1 after bootloader unlock?
Click to expand...
Click to collapse
That's what DRM Info showed.
But for me it's all moot at this point. Yesterday, Google Pay stopped working (some new detection thing I presume), so I attempted to relock the bootloader with
./fastboot flashing lock
at which point the device started going into an infinite power cycle instant reboot no way to get into FASTBOOT, or Recovery or turn off the phone. So I just returning the phone and going back to OnePLus 8 / Android 11 where you can be fully rooted and everything just works.
What a disappointment and waste of time.
Thanks for everyone who offerred suggestions...I'll try back in 6 months or so and see if any of this gets sorted out.
It's not "issues with the chip". Google upped their ante with root detection, which breaks everything from netflix to google pay. See this thread.
I was the OP and had to return my bricked OP10Pro under the 30 day return period.
Anyway, I bought a Google 512GB Pixel 6 Pro used, rooted it, and did the basic stuff I have done since the OP8Pro -- and everything works -- GPay, Netflix, no DRM issues and no hassles.
So maybe it is the chip, but if google had "upped their game" I would think it would be with their own phones especially since the Tensor SOC (co developed with Samsung) has a trusted security module.
As far as the phones go, the Pixel Pro is heavier and the battery charges slower, but you get dual SIM and it works on all USA/Worldside 5G networks and bands. And the cameras are top notch. So kind of a tossup I guess.