Related
I have tried several AOSP roms and have not gotten Netflix to work on any of them. I have tried liquidsmooth and PacRom but I keep getting Error (-9). Does anyone know of a fix for this? Please help..Thanks.
jmayer846 said:
I have tried several AOSP roms and have not gotten Netflix to work on any of them. I have tried liquidsmooth and PacRom but I keep getting Error (-9). Does anyone know of a fix for this? Please help..Thanks.
Click to expand...
Click to collapse
Using SELinuxModeChanger app, you can set to permissive and give it a go, it sometimes work.
Another method is to delete a lib file within
/system/vendor/lib
Liboemcrypto.so, you can rename or simply delete, then reboot the device.
Spark91 said:
Using SELinuxModeChanger app, you can set to permissive and give it a go, it sometimes work.
Another method is to delete a lib file within
/system/vendor/lib
Liboemcrypto.so, you can rename or simply delete, then reboot the device.
Click to expand...
Click to collapse
I personally didn't have luck with the permissive change and couldn't find the liboemcrypto.so file you spoke of. Is that specific to the Galaxy Note 4?
No sir, most ROMs don't have the lib, and what ROM are you using ?
Using liquid smooth on a moto xt926. I've noticed this problem on various cm12 ROMs I've tried. They had Netflix running for a while then it kind of stopped for recently then I think the last one I tried that I worked on was bliss pop 3.2. Jump over to liquid smooth because. Was pretty laggy and causing me a little pain. Back to a loading screen. Never comes up. I will say I thought it was a host file or ad block problem because I could get it going on WiFi. Just not on cellular data.
Think pulling and using the apk from a nexus device would change anything?
Beats me, I think that it probably is not an issue with the apk itself.
My best guess is that it is ROM related. Didn't cm ROMs have some DRM related issues a year or so ago? Wouldn't surprise me if it's something along those lines.
BTW, forgot to mention that you can't even get to netflix.com and browser. just more thoughts as to why I don't think it's actual program related it something in the ROM.
It is ROM/Kernel related for the Note 4 before I think @Mod57 fixed it but all it was is to change a build.prop line. Try and see if this works for you as well.
persist.hwc.mdpcomp.enable=false
If the value is already there and it says True, change it to false.
Did this on a previous build (cm12 5-8-2015 I believe), seems to work although more testing is needed to determine consistency. Failed first time worked second.
Sure hope that's it....!
Has anyone had better luck finding a solution for this? I came from DU's latest and now on CM12.1 6/25 nightly, everything is working great except for Netflix. I was never able to get it to work in DU so I won't be terribly heartbroken if I can't get it fixed, but I do not have Lyboemcrypto.so file or that specific persist line in my build.prop. Any other suggestions? I was getting a -504 error when attempting to install a couple apps, turning flight mode on/off took care of that, so I tried that as well as wifi on and off both for Netflix but cannot get it to initialize, all I get is the constant red spinning circle of the first screen. Thanks
Workaround
Install the module xposed cm10.1 Netflix workaround under xposed framework. Works perfectly on t0lte.
Edit: working on cm12.1
Netflix fix
Deleted
Google App v6.9.36.21.arm64, Viper ROM v4.4.0 and v4.5.0 (both clean installs), S-Off, Bootloader unlocked, TWRP v3.0.3.0_Unofficial.
Anyone else having issues with "Ok Google" detection not working when "From any screen" is selected? Even from within the Google app open with the search bar that states " "Say OK Google" ", I can't get the phone to respond to the "Ok Google" voice command. In other words, it never brings up a voice activated search.
If I deselect "From any screen", then it works from within the app with the search bar, as expected. But the moment I select "From any screen", and no matter how many times I've tried retraining the voice model, it never responds to "Ok Google".
Microphone is verified working.
The strange thing is that it was working a week ago, and nothing had changed since that time. I was running Viper 4.4.0 (Full ROM, not Magisk version) up until today (it was yesterday while on v4.4.0 that I noticed it wasn't working anymore), and today the v4.5.0 update came out, so I opted for a completely clean install to rule out any bad settings I may have mucked up at any point. Still, on v4.5.0 Full ROM (non-Magisc version), I can't get it working. I also tried installing Google Now Launcher to see if it would work with a different launcher, and still no luck.
Google App has permissions to Microphone (have also tried clearing data from app, and resetting it up, completely uninstalling Google App and reinstalling/setting up - still no joy). I've removed Google App from battery optimization, no change. I just can't make heads or tails of it. My wife's phone (Samsung GS7) has the same version of the Google App installed, and hers works fine, so it can't be the app.
Anyone out there care to verify on their phone if "Ok Google" detection from any screen works for them? And what is your ROM, Root, Bootloader, and S-on/S-off situation? I'm just a little curious with all the "Feature blocking for rooted devices" that's been going on lately, if Google blocked the use of "Ok Google" voice detection from any screen for rooted and/or bootloader unlocked devices for some strange reason.
Thanks! Any hits/tips/tricks would be greatly appreciated.
Can anyone at least verify if "OK Google" detection from any screen is working on their HTC 10?
Sent from my HTC 10 using Tapatalk
It's working fine here . Try to delete ok Google detection sample from voice search settings in Google now .
hamud.q said:
It's working fine here . Try to delete ok Google detection sample from voice search settings in Google now .
Click to expand...
Click to collapse
Just so I'm clear, are you suggesting to delete, then retrain the voice model from the Google App? Just want to be sure I understand, since I've performed the voice model training countless times since the issue popped up.
For the record, I don't have the Google Now Launcher installed. I only installed it once after noticing OK Google detection wasn't working, and when I noticed it didn't change anything, I removed it.
Thanks, and if you don't mind sharing your phone's setup?
Boostjunky said:
Just so I'm clear, are you suggesting to delete, then retrain the voice model from the Google App? Just want to be sure I understand, since I've performed the voice model training countless times since the issue popped up.
For the record, I don't have the Google Now Launcher installed. I only installed it once after noticing OK Google detection wasn't working, and when I noticed it didn't change anything, I removed it.
Thanks, and if you don't mind sharing your phone's setup?
Click to expand...
Click to collapse
You don't need to delete it, just retrain it. I've had to do this myself a few weeks ago.
xunholyx said:
You don't need to delete it, just retrain it. I've had to do this myself a few weeks ago.
Click to expand...
Click to collapse
OK, well, I've done it both ways (simply retraining, as well as deleting, then retraining). Nothing seems to restore functionality.
Thank you for the input.
Yes exactly ! Retrain ok google . But if that doesn't solve the problem . don't know what to do next .
Well, as an informational update to this issue, I flashed a stock RUU for my variant (US Unlocked, 2.38.617.6), and everything functions as intended. So, there's something funky going on with the custom ROM I was running. Attempting the Magisk version next to see if it all works there.
Boostjunky said:
Well, as an informational update to this issue, I flashed a stock RUU for my variant (US Unlocked, 2.38.617.6), and everything functions as intended. So, there's something funky going on with the custom ROM I was running. Attempting the Magisk version next to see if it all works there.
Click to expand...
Click to collapse
I believe I'm on the same ROM as you, and am using the classic SuperSU version, and it is working for me. I wish I had an answer for you, but I don't.
I'll try and see if I can find one for you though.
Further testing shows that it works on the Magisk version, but then immediately flashing back to the classic version with PHH Superuser, it ceases to function. I'll try testing with the classic version of the ROM using SuperSU, instead.
One last update for the day. Installing Viper v4.5.0 with SuperSU insteaed of PHH seems to have solved the issue, as well. Seems something about PHH is interfering with Google App voice detection from any screen.
Thanks for the input, guys.
I have magisk / phh r2 installed and my "OK Google" detection from the Google now on tap screen works very poorly. I've been thinking I had to yell at it to detect my voice, but even that is hit or miss. When I enable OK Google detection from any screen, it works just fine.
Edit: running 2.38.617.6 with latest magisk, included root, magisk hide enabled, and systemless host enabled for AdAway 3.2.
adamjmacdonald said:
I have magisk / phh r2 installed and my "OK Google" detection from the Google now on tap screen works very poorly. I've been thinking I had to yell at it to detect my voice, but even that is hit or miss. When I enable OK Google detection from any screen, it works just fine.
Edit: running 2.38.617.6 with latest magisk, included root, magisk hide enabled, and systemless host enabled for AdAway 3.2.
Click to expand...
Click to collapse
Odd... Man, I've tried so many things to get it working on a fresh install of 4.5.0 with PHH, and could never get it to work.
I would even do a fresh, full wipe install, then I wouldn't install any apps, set up voice model for OK Google, and still couldn't get it to work.
Hi I've got a 5t I started on FreedomOS, which was fine, but was still running 7.1.
I wanted to use MicroG, so opted for OmniROM and it was working perfectly. Then I found that WIFI tethering wouldn't work, not matter what I did full reset, apn settings, nothing worked.
I then thought I'd try Resurrection Remix and had it all setup and working. Then went to enter a lock code and it worked, then when I went to enter a fingerprint settings crashed and each time I opened settings it crashed. I had setup from scratch multiple times and tried both the OnePlus 3 and 4 firmwares. I had MicroG working via the Xposed module, so Omni is definitely my preferred option.
I then tested LineageOS and settings crash also when going to setup fingerprint or go to security settings at all.
I have done about 5 full formats including storage. It's kind of like the settings haven't been removed.
All I want is a clean ROM with MicroG support and a few customizations such as battery, dark theme etc, but have had no success.
I love the amount of support and customizations available for the OnePlus and that's was the main reason I got it.
Does anyone have any idea or something else I could try?
davoidd said:
Does anyone have any idea or something else I could try?
Click to expand...
Click to collapse
Have you tried a different firmware yet? Sounds firmware related - need the right firmware for the right ROM. OmniRom has that in the OP. Also just did some quick research on MicroG and found https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 if magisk is more desirable to you.
Hi thanks for your reply. I'm not sure why it happened, but have partly resolved it. I just switched to lineageos with native microg support.
Seems like removing some of these files can help. As even a full wipe doesn't remove these settings.
By removing these seemed to fix it.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
/data/system/users/0/settings_fingerprint.xml
You may also delete the following file if it exists
/data/validity/template.db
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
fortillian said:
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
Click to expand...
Click to collapse
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
CyberpodS2 said:
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
Click to expand...
Click to collapse
Yea, I've been through that 106 page thread and a few others. Renamed folders, deleted folders, reinstalled apps, hid services in magisk hide. I was never a fan of NFC payment until I started using it lol.
Try safety patch module in Magisk to pass Safetynet
HueyT said:
Try safety patch module in Magisk to pass Safetynet
Click to expand...
Click to collapse
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
fortillian said:
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
Click to expand...
Click to collapse
I'm thinking the same
Another problem with Google Wallet.
After updating Google Wallet, this app again tells me that the phone is rooted.
It has worked without problems until now.
Root - magisk and other supporting actions are already done from the previous editing.
Thanks in advance for your help
had this issue yesterday and didnt manage to fix without flashing another rom but here's a post with the latest fixes for it.
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
forum.xda-developers.com
Do you remember me? I also had that problem. I'm now using Evolution X ROM based on Android 13. Everything is working. Magisk + Zygisk + SafetyNet Fix Module
So
I tried clearing data from google play services, play store and completely uninstalling google wallet.
Next, I disabled MagiskHide Props Config for a while.
I downloaded USNF (safetynet-fix-v2.3.1-MOD.zip) and flashed it over the old USNF.
I restarted the mobile phone, installed Google Wallet, registered a bank card and so far everything is fine - the device meets the security requirements.
In magisk, I haven't added Google Wallet to the denylist yet.
We'll see how long it lasts.
Cleared cache and data of wallet, rebooted, and it works again. Very very strange.
sanguinesaintly said:
Cleared cache and data of wallet, rebooted, and it works again. Very very strange.
Click to expand...
Click to collapse
I wrote the procedure a little more extensive. I did many more actions and differently than you write!
jkmaxfli said:
I wrote the procedure a little more extensive. I did many more actions and differently than you write!
Click to expand...
Click to collapse
Google has made some backend changes by the looks of things. All working now without root or Magisk.