Related
Hi all,
I've had my LG Watch Sport since the beginning of the year and Android Pay worked fine in Android 7.x on this device. Since the update to Android 8 it is always disabled. I have manually re-enabled it and updated it which then it works for a short while, then it disables itself again.
I've used it fine and the bank I am with supports this, but it is starting to frustrate me that this function has now gone (well, not really, just have to re-enable the app every time I want to use it so not convenient) when I have gotten so used to it. I can use it on my phone fine.
The Android Wear version from the watch information is 2.7.0.1778645119 and there do not seem to be any other updates available at this time.
Someone on one of the Google threads has indicated that it is due to the region being locked on these devices - so if you are not in the US or UK, you cannot use Android Pay.
I am curious to know if you are experiencing this issue if you are located in the US or UK. There doesn't seem to be too much noise in the forums here about this, so I am guessing it is working fine for the US and UK folks where this is supported.
Also wondering if anyone knows how it determines its location - whether it is like the Microsoft Band 2 where you can set your phone up as US first, then change your time zone, etc to your location and keep using it, or if the new Android Wear and Android Pay do a GPS lookup on the watch before operating.
If this works fine for all our US and UK owners, maybe we can set the watch up thinking it is in a different location and see if it gets disabled? It would seem silly to have it disable once set up, as I would forsee travelling with this device and just being able to conveniently use this for both store cards and credit card without having to bring anything else.
I can not believe this, it do not want either.'
Any country that supports Android Pay the app should work
deswong said:
Hi all,
I've had my LG Watch Sport since the beginning of the year and Android Pay worked fine in Android 7.x on this device. Since the update to Android 8 it is always disabled. I have manually re-enabled it and updated it which then it works for a short while, then it disables itself again.
I've used it fine and the bank I am with supports this, but it is starting to frustrate me that this function has now gone (well, not really, just have to re-enable the app every time I want to use it so not convenient) when I have gotten so used to it. I can use it on my phone fine.
The Android Wear version from the watch information is 2.7.0.1778645119 and there do not seem to be any other updates available at this time.
Someone on one of the Google threads has indicated that it is due to the region being locked on these devices - so if you are not in the US or UK, you cannot use Android Pay.
I am curious to know if you are experiencing this issue if you are located in the US or UK. There doesn't seem to be too much noise in the forums here about this, so I am guessing it is working fine for the US and UK folks where this is supported.
Also wondering if anyone knows how it determines its location - whether it is like the Microsoft Band 2 where you can set your phone up as US first, then change your time zone, etc to your location and keep using it, or if the new Android Wear and Android Pay do a GPS lookup on the watch before operating.
If this works fine for all our US and UK owners, maybe we can set the watch up thinking it is in a different location and see if it gets disabled? It would seem silly to have it disable once set up, as I would forsee travelling with this device and just being able to conveniently use this for both store cards and credit card without having to bring anything else.
Click to expand...
Click to collapse
I have the same issue. I have had LG Watch Urbane 2nd before and there had been Android Pay working well. Now I have to enable it after approx. 1 hour.
I've got the watch one week ago, there was Android 7.1.1. I had to join beta testing, then I got Oreo.
My country is suported by Oreo and also Android Pay is supported (Czech republic)
Has anybody an idea how to fix this? Very annoying.
Android Wear 2.7.0.178645119
Andtoid OS 8.0.0
Services 11.9.51
1st October 2017
Build OWR1.170919.023
I've got the watch one week ago, there was Android 7.1.1. I had to join beta testing, then I got Oreo.
Android Wear Beta did disable Android Pay.
This is why I refused to sign up for the beta program.
But I got final Oreo, not beta.
I live in Spain LG Watch Sport with Oreo, and I have the same issue[emoji852]️
Enviado desde mi SM-G930F mediante Tapatalk
Seems like many people are seeing this, me I will refuse any update until I an sure Android Pay will work.
I purchased the watch because it has NFC and Android Pay support.
I live in Taiwan LG Watch Sport with Oreo, and I have the same issue️.
LG or Google should face & fix this problem.
It's a problem for all devices with Oreo, not only LG Watch Sport
Enviado desde mi SM-G930F mediante Tapatalk
Do you mean all devices or only all wearables? Should I stop upgrading to Oreo on my phone?
libb said:
Do you mean all devices or only all wearables? Should I stop upgrading to Oreo on my phone?
Click to expand...
Click to collapse
All wareables
Enviado desde mi SM-G930F mediante Tapatalk
Lots of good info here.
Having read this and upgraded both my smartphone and my watch to Oreo 8, I tried Pay today. And it did work with both the LG watch sport and my Oneplus 5 (rooted). Suprisingly, the Pay on the smartphone now worked in a shop where I could not pay with smartphone/smartwatch before.
.....
Keep in mind only Non-Americans seem to have issues
How to make a downgrade - Android 7.1.1 Nougat, I really need Android Pay. Does anyone have a factory image?
AstroDigital said:
I can not believe this, it do not want either.'
Any country that supports Android Pay the app should work
Click to expand...
Click to collapse
Android Pay on Android Wear supported only in US and UK
I'm Huawei Watch 2 user also probably soon affected by this. To work around this, I prepared a proxy app that takes only two more taps to enable and launch Android Pay. https://forum.xda-developers.com/android-wear/development/app-pay-enabler-android-pay-oreo-t3750815 Any thoughts/feedback?
Thank you. I appreciate it but we should pust to Google to enable it.
I tried the application and I like it.
One suggestion: is possible to check if Android Pay is enabled and if not, display the page for enabling, if yes, start AP? Then I could set hardware button to your application and it would start what is necessary.
EDIT: I checked source code and you alreadyd did it! Thanks, it works well!
moneytoo said:
I'm Huawei Watch 2 user also probably soon affected by this. To work around this, I prepared a proxy app that takes only two more taps to enable and launch Android Pay. https://forum.xda-developers.com/android-wear/development/app-pay-enabler-android-pay-oreo-t3750815 Any thoughts/feedback?
Click to expand...
Click to collapse
Thank you~
Your app helps us a lot~ :good:
Hello,
I have recently bought a Nokia 7 plus. I have Oreo 8.0 with February security patch. I have heard that Oreo 8.1 is available, but my phone does not found it. It is a Nokia TA-1046 dual SIM version and I am fronm Spain. I bought it via Amazon and it is unlocked. Any help is appreciated, thanks a lot,
Profree
Received 8.1 in the UK. Try using a VPN connection
awells845 said:
Received 8.1 in the UK. Try using a VPN connection
Click to expand...
Click to collapse
Thanks for your answer, how can I establish a VPN connection? I mean, in server direction what do I have to write?? Thanks a lot.
Profree99 said:
Thanks for your answer, how can I establish a VPN connection? I mean, in server direction what do I have to write?? Thanks a lot.
Click to expand...
Click to collapse
Download a VPN app from the play store
awells845 said:
Download a VPN app from the play store
Click to expand...
Click to collapse
Which location you set in the vpn?
awells845 said:
Download a VPN app from the play store
Click to expand...
Click to collapse
A recommended VPN app please?
VPN won't work.Its based on your provider more than anything
manus31 said:
VPN won't work.Its based on your provider more than anything
Click to expand...
Click to collapse
I have seen that some people have the update others not. I suppose it will appear in some days.
manus31 said:
VPN won't work.Its based on your provider more than anything
Click to expand...
Click to collapse
Usualy update rollouts are based on imei numbers afaik.
Profree99 said:
Hello,
I have recently bought a Nokia 7 plus. I have Oreo 8.0 with February security patch. I have heard that Oreo 8.1 is available, but my phone does not found it. It is a Nokia TA-1046 dual SIM version and I am fronm Spain. I bought it via Amazon and it is unlocked. Any help is appreciated, thanks a lot,
Profree
Click to expand...
Click to collapse
maybe it will be a good idea to keep this update issue in one thread - https://forum.xda-developers.com/nokia-7-plus/help/eu-7-dual-sim-ta-1046-model-stuck-t3780101
Anyway, this update saga becomes more interesting as someonefrom Spain, with same model, is reporting he got the update when he turned on the phone 1st time: https://forum.xda-developers.com/showpost.php?p=76296726&postcount=6
Hope it is not an issue with Amazon IMEI
Profree99 said:
A recommended VPN app please?
Click to expand...
Click to collapse
Something that seems to work for some people is to remove your sim card, disable the GPS, clear the cache and data of carrier services under the apps menu (you'll need to click on the three dots and show system apps first), clear the same for Google Services Framework, reboot, connect to the Belgium server using Psiphon Pro (a VPN app). Choose to tunnel whole device. You could also try other locations like Germany and Denmark in Psiphon Pro. Some people have found that if it doesn't work, a factory reset prior to connecting to the VPN has triggered the update, but that's pretty extreme. Let us know if it works, as I don't own the device and I'd be interested to hear if it's effective.
Pumpino said:
Something that seems to work for some people is to remove your sim card, disable the GPS, clear the cache and data of carrier services under the apps menu (you'll need to click on the three dots and show system apps first), clear the same for Google Services Framework, reboot, connect to the Belgium server using Psiphon Pro (a VPN app). Choose to tunnel whole device. You could also try other locations like Germany and Denmark in Psiphon Pro. Some people have found that if it doesn't work, a factory reset prior to connecting to the VPN has triggered the update, but that's pretty extreme. Let us know if it works, as I don't own the device and I'd be interested to hear if it's effective.
Click to expand...
Click to collapse
How can you connect to a VPN server through a VPN once the device has been factory reset without setting up the device and downloading the app and connecting to a server. You would be in the same predicament again. So then user has factory reset again and again......
If an update hasn't arrived for a particular device model number, nothing you can do will get you the update quicker. If we're talking about the 1055 model, that is.
awells845 said:
How can you connect to a VPN server through a VPN once the device has been factory reset without setting up the device and downloading the app and connecting to a server.
Click to expand...
Click to collapse
If you do have to factory reset, you configure your wifi and Google account, and download the app from the Play Store. Or, you download the APK from APK Mirror and simply install it. Not inserting the sim card or enabling the GPS would be the important steps if you're trying to get an update that's available but witheld in your region.
Pumpino said:
If you do have to factory reset, you configure your wifi and Google account, and download the app from the Play Store. Or, you download the APK from APK Mirror and simply install it. Not inserting the sim card or enabling the GPS would be the important steps if you're trying to get an update that's available but witheld in your region.
Click to expand...
Click to collapse
Though you don't have the device to prove this information is credible, have you got proof it worked for you?
awells845 said:
Though you don't have the device to prove this information is credible, have you got proof it worked for you?
Click to expand...
Click to collapse
I don't have the device and I don't have proof. However, I've been researching the issue of blocked updates by looking at three forums over the weekend and compiling a list of strategies that have worked for some people. The purpose of me doing it is to establish whether or not I want to purchase the phone. I'm happy to go to the trouble of using a VPN to get updates, but I'm not prepared to purchase the phone if it doesn't receive timely updates. That's why I want more people to report if it's a reliable strategy.
Pumpino said:
I don't have the device and I don't have proof. However, I've been researching the issue of blocked updates by looking at three forums over the weekend and compiling a list of strategies that have worked for some people. The purpose of me doing it is to establish whether or not I want to purchase the phone. I'm happy to go to the trouble of using a VPN to get updates, but I'm not prepared to purchase the phone if it doesn't receive timely updates. That's why I want more people to report if it's a reliable strategy.
Click to expand...
Click to collapse
Could you provide links to such forums and to where people have stated this approach works. A Vpn usually works for me on other devices, but a seems too many factors involved with getting the update here for example I don't think anyone has got an update on TA-1055,no matter what region. It may have shipped with 8.1 for some though
manus31 said:
Could you provide links to such forums and to where people have stated this approach works. A Vpn usually works for me on other devices, but a seems too many factors involved with getting the update here for example I don't think anyone has got an update on TA-1055,no matter what region. It may have shipped with 8.1 for some though
Click to expand...
Click to collapse
https://forums.whirlpool.net.au/forum-replies.cfm?r=56102186#r56102186
https://forums.whirlpool.net.au/forum-replies.cfm?t=2597417&p=59#r1172
https://forum.xda-developers.com/showpost.php?p=76425485&postcount=127
https://forum.xda-developers.com/showpost.php?p=76427295&postcount=129
Obviously, it's only got potential to work if the update is available. https://www.nokia.com/en_int/phones/security-updates
Pumpino said:
https://forums.whirlpool.net.au/forum-replies.cfm?r=56102186#r56102186
https://forums.whirlpool.net.au/forum-replies.cfm?t=2597417&p=59#r1172
https://forum.xda-developers.com/showpost.php?p=76425485&postcount=127
https://forum.xda-developers.com/showpost.php?p=76427295&postcount=129
Obviously, it's only got potential to work if the update is available. https://www.nokia.com/en_int/phones/security-updates
Click to expand...
Click to collapse
Thanks for providing the links, yea seems like something that would work OK, but I suspect they just haven't flipped the switch for my model yet so will hang on another while until I hear people have been getting updates
"]https://drive.google.com/open?id=1Ys1edGoDygewh40D5UHatb93HaNbW9bU[/IMG]https://drive.google.com/open?id=1Ys1edGoDygewh40D5UHatb93HaNbW9bU
Contacted Nokia Support again. They've confirmed something interesting that some Nokia 7 Plus models wont receive 8.1 just security patches. (Screenshot above for evidence.
awells845 said:
"]https://drive.google.com/open?id=1Ys1edGoDygewh40D5UHatb93HaNbW9bU[/IMG]https://drive.google.com/open?id=1Ys1edGoDygewh40D5UHatb93HaNbW9bU
Contacted Nokia Support again. They've confirmed something interesting that some Nokia 7 Plus models wont receive 8.1 just security patches. (Screenshot above for evidence.
Click to expand...
Click to collapse
Very interesting, but strange. Some people with in my region (spain) and with my model TA-1046 have received the update, but I don't. That means that I will never receive the update? Thanks for the information.
Anyone else experienced problem with Google Pay after update?
It worked extremely well for me up until the update, then all of the sudden it doesn't work any more.
I checked the settings inside Google Pay, but all seems well. Card is registered and everything.
When holding my phone up to the terminal there is no reaction from the phone at all.
What can I do to fix this?
I have exactly the same, but with my normal banking app. It can also do payments via NFC, but when I hold it up to a terminal nothing happens like you said.
I'm now factory resetting my phone to see if that helps, I'll let you know!
Gfhoihoi72 said:
I have exactly the same, but with my normal banking app. It can also do payments via NFC, but when I hold it up to a terminal nothing happens like you said.
I'm now factory resetting my phone to see if that helps, I'll let you know!
Click to expand...
Click to collapse
Thanks! Looking forward to your feedback if this works or not.
TordFuglstad said:
Thanks! Looking forward to your feedback if this works or not.
Click to expand...
Click to collapse
Nope... Unfortunately not. Maybe I'll just downgrade to Android 9 and wait until a new patch for Android 10 comes out where they fix this.
No problems here, working as before
EnormoDerClown said:
No problems here, working as before
Click to expand...
Click to collapse
What firmware version are you on?
I've downgraded to Android 9.1 and the mobile payment is working perfectly again, so it's definitely an issue with Android 10. So if you really want to use it, you can downgrade for now. Otherwise just wait for the next Android update and hope that it gets fixed.
Same here in France, Google Pay says Phone moved too fast.
Can pay with one other bank's app, but not the other one's. (both Georgian banks)
They did warn in changelog that some banking apps are not working due to their compatibility issues with Android 10, though
giosal said:
Same here in France, Google Pay says Phone moved too fast.
Can pay with one other bank's app, but not the other one's. (both Georgian banks)
They did warn in changelog that some banking apps are not working due to their compatibility issues with Android 10, though
Click to expand...
Click to collapse
True, that changed the way apps can use your IMEI and this was the way most banking apps verified your phone. But my banking app should be compatible with Android 10 and it is working for some people but not for others.
Gfhoihoi72 said:
What firmware version are you on?
I've downgraded to Android 9.1 and the mobile payment is working perfectly again, so it's definitely an issue with Android 10. So if you really want to use it, you can downgrade for now. Otherwise just wait for the next Android update and hope that it gets fixed.
Click to expand...
Click to collapse
10.0.0.168. "normal" update. Not a member of the beta or anything, just normal OTA. Working exactly as on Android 9. Also tested/used with different cards/institutes in google pay. Working like a charm
Same problem here, Google Pay worked perfectly in 9.1. Now, with 10.0.0.173 there's no response when near terminal. No error messages anywhere. NFC works fine, e.g. ReadID to read the NFC chip in my passport.
The same here, but I have a mate 20 pro. After the update to Android 10 I can no longer pay with Google pay.
From Germany
Updated yesterday and works fine for me in UK
So i better stop an update i am asked to update to 173 and stay on my 168 It is working for sure on 168 for me. Used it quite often
I solved the problem on my P30 Pro. I was using a "twin SIM" card from Ice (service provider). When I switched sim cards to my main SIM, Google pay works as before. The twin SIM worked fine with Android 9. I think the problem is that the twin SIM does not have the real phone number, but some long code that the phone system somehow recognizes, but causes issues in some scenarios e.g. iMessage on iPhone which cannot verify it. That's why I had the twin SIM in my P30 Pro.
EDIT: The iMessage problem is caused by the fact that only the main SIM receives "class 0" or flash SMSs, used for iMessage's verification.
I'm having the issue with my UK region VOG-L29 that's running .173. I rarely use Google pay, so I'm not sure if it was working before the upgrade. Google Pay works fine on my Fossil Wear OS watch that's tethered to the phone. NFC also seems to work fine when connecting my camera to the phone.
Have also the problem of nfc payments (with gpay and postfinance app) not working after updating to Android 10. Full reset didn't help currently on version 10.0. 0.173 and still not working.
Huawei support doesn't know anything about this and said I should wait for app updates and/or emui update.not very helpful...
Uninstalling gpay and deleting the cards linked to it and setup everything from scratch didn't help either. Nfc hardware seems to work as I can trigger my bt connection with my nfc enabled headset.
Hopefully Huawei sorts this out quickly as it is very annoying since I used nfc payment almost every day on emui 9.1
Any solution for this problem? I also used the ohone to pay and the point is that it is a big inconvenience that there is no solution
Waiting for Huawei to fix the damn bug in their next update (hopefully). Downgrading or resetting and so on is a pain when the affected phone is your daily driver.
Been using GPay already multiple times with 10.0.173.
No problems here in germany.
Regards
Same here!
Updated yesterday to EMUI 10 and realized today that I could'nt pay at the terminal. Bad situation without credit cards
Seems like NFC does not work at all. When I try to read my credit cards with NFC Tools, there is no reaction from phone as before.
I updated from 12.0.2 to 12.0.3 of MIUI recently and I now cannot pay by NFC with my banking app. My banking app doesn't use Google Pay and I don't have or want Google Pay so I can't try that.
I have checked that "Use HCE" wallet is set. Is there anythign I can do to get things working again?
Does no one have any suggestions on this at all?
@ludditefornow can you elaborate a bit what do you mean by "cannot pay by NFC" - what exactly happens when you place your phone near the terminal: is there any reaction (message) from the banking app or no reaction at all? Did you try to pay with the banking app open? Did you try disabling and re-enabling contactless payments in your banking app? In MIUI settings just below the option where you select "Use HCE" there's another option to select application for contactless payments - maybe the upgrade reset it to "Google Pay"?
I also have MIUI Global 12.0.3 (upgraded from 11.something) but didn't try paying by phone yet.
Thanks for the response. I have always paid with the banking app open. And have never had an issue.
Since 12.0.30 I have had two reactions from the 'pay wave' NFC payment terminals. Either they state that they can't read and throw up an error. or simply do nothing.
I have tried to disable and reenable contactless payments and no difference.
I have confirmed that Google Pay is not the default and that my banking app is. I have also confirmed that my banking app has NFC permissions.
I really have no idea. But I appreciate your reply.
For me (Global version) it's still working fine.
Never used my phone for contactless payments, so can't give specific advice, but a couple of simple questions to help troubleshoot.
Does NFC work at all? Can you communicate with other phones, e.g. can you send a photo to another phone using Nearby Share (or whatever name NFC sharing might be called on MIUI, if it's not the same)
How did you update MIUI? OTA or manually? If manually, did you flash the correct ROM? Because Indian MIUI versions don't have NFC functionality, as the physical device is missing on Indian phones.
Robbo.5000 said:
Never used my phone for contactless payments, so can't give specific advice, but a couple of simple questions to help troubleshoot.
Does NFC work at all? Can you communicate with other phones, e.g. can you send a photo to another phone using Nearby Share (or whatever name NFC sharing might be called on MIUI, if it's not the same)
How did you update MIUI? OTA or manually? If manually, did you flash the correct ROM? Because Indian MIUI versions don't have NFC functionality, as the physical device is missing on Indian phones.
Click to expand...
Click to collapse
Thanks,
three different NFC checking apps return positive to NFC and HCE. There is no Android Beam and as far as I recall there never has been.
Updates always OTA. And the current ROM is global as is my phone.
I've completely uninstalled the app and reinstalled it and then added the card again. I will check it today and see the result.
Thanks for the assistance all.
Yesterday I paid successfully with my phone (as I mentioned - MIUI Global 12.0.3 upgraded from 11.something).
Interesting outcome (for me anyway).
After removing the credit card from the app and then deleting the app, I then reinstalled the app and added the card. This led to the NFC HCE function again working.
Another symptom that appeared at the same time on the update was that I could turn on airplane mode at the icon on the pull down draw on the home screen. I couldn't turn off the airplane mode in the same way. To turn off airplane mode I needed to do so with the slider in settings.
After HCE function started working again, my airplane mode on / off functionality came back as well.
I am just writing this here in case someone at sometime gets something similar and may have another option to try to repair it.
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.