I just unlocked the bootloader and flashed my first G7 Custom ROM the other day and something that I tried doing was play DRM content on YouTube and Peacock (NBC's new streaming service).
When I do this, my device plays it for a couple of seconds, but then crashes and reboots.
I have already looked around in a few places, such as the official LineageOS subreddit and the G7 telegram group as well, and someone suggested using the liboemcrypto disabler Magisk module. My phone wasn't rooted, so I installed Magisk and installed this module as well. Unfortunately, this only helped a little bit because the device played the content for longer than before, but after about 15 seconds, or when I switch to full-screen, the device still crashes.
I looked on the LOS subreddit, but that came inconclusive because I found a topic saying that there was the same issue on the G7 Play (i don't remember, it was maybe G7 power, but the point is that it was a G7 series phone). Anyway, there was never a solved issue there.
So, I'm kind of stuck.
I will appreciate any suggestions, and if none is available, then I guess I just have to live without playing movies and TV on my phone, which I actually think is good for my own wellbeing!
Just wanted to update this thread, so far after using LOS 18.1 for a little while today, I have yet to notice any DRM crashes after using the liboemcrypto Disabler Magisk Module, which I was using before, but it seems like it works now! I will update this thread with any updates that appear.
Related
First of all, a video streaming app is an app that requires constant Internet connection to play a video. Some examples are YouTube, Facebook or Vessel.
This post was meant for people who has a problem where our device just randomly gives an error when trying to watch a video. It affects all apps at one time. Only way to fix it is to reboot the device. Until today. It seems like the Sony Marshmallow Beta (not the concept) released for our device has fixed this. But I am not a 100% sure. I haven't been getting any of those error ever since I've used the Beta software since it was released.
Please take this really short survey. Click here for the survey
Thanks
Personally, I've only experienced this issue when I'm on any rom with an unlocked bootloader. If I used any rom with a locked bootloader, I don't have this issue. I'm currently using the MM beta and I have rooted it with a locked bootloader and have not experienced any issues with video playback. I used to have this issue on Cyanogenmod, the MM concept, etc. with the bootloader unlocked. I've been trying to figure out what causes it but I haven't had any luck
ash123456678 said:
Personally, I've only experienced this issue when I'm on any rom with an unlocked bootloader. If I used any rom with a locked bootloader, I don't have this issue. I'm currently using the MM beta and I have rooted it with a locked bootloader and have not experienced any issues with video playback. I used to have this issue on Cyanogenmod, the MM concept, etc. with the bootloader unlocked. I've been trying to figure out what causes it but I haven't had any luck
Click to expand...
Click to collapse
Have you tried the Beta with your bootloader unlocked? Because mine is and I don't seem to have that problem anymore.
I haven't used the phone with locked bootloader so I can only tell my experience with unlocked bootloader.
On both Lollipop (23.4.A.1.264) and MM Concept (3536) [both with the DRM bypass mod), I've experienced multiple occurrences where HW decoded video playback (Facebook, YouTube, Album, etc.) fails. Not just playback however, video recording is also broken once that happens. Currently the only way to restore the functionality is to do a reboot. This is particularly annoying when you are binge watching a playlist on YouTube.
tl;dr
- I'm on unlocked bootloader.
- Video playback breaks randomly.
- Video recording is affected too.
- Only way to "fix" is to reboot.
I started having this issue when I installed the Concept ROM along with the unlocked bootloader. Since then, even if I lock it again it still happens.
I was able to solve it when I installed the Beta ROM, but I didn't like it so I came back to Concept and I still have this issue. It's annoying, but the only way to fix it is by rebooting the device.
I installed the beta rom and it seems that they fixed the issue.
I'm experiencing this on my Z3C as well (MM Concept 3555, UL and rooted with DRM fix). It's a nuisance having to restart my phone everyday so if MM Beta does fix this issue, I'd consider using it, but losing adoptable storage will suck. Hopefully someone comes up with a mod for MM Beta/Official that will allow us to utilize our SD cards as internal like Concept does.
Sent from my D5803 using Tapatalk
Hello all. So I cannot stream or download movies on my Verizon S5 - I'm on 5.0 (baseband: BOG5) and I am rooted. I've never had issues with this app up until a few months ago. I've tried researching it over this time, but nothing has worked. Now after being unable to download movies for a trip this past week - I'm starting to get annoyed....so I need your help.
Things of note:
-I've tried wiping/uninstalling the app
-I've tried wiping my phone
-The app loads just fine - I click on a movie to either play or download and it fails
Are there any known issues about this Android version and Vudu? I've researched, but I have yet to find a solution or just even an answer.
If any other information is needed, I'm happy to provide it.
Thanks!
beckamgop said:
Hello all. So I cannot stream or download movies on my Verizon S5 - I'm on 5.0 (baseband: BOG5) and I am rooted. I've never had issues with this app up until a few months ago. I've tried researching it over this time, but nothing has worked. Now after being unable to download movies for a trip this past week - I'm starting to get annoyed....so I need your help.
Things of note:
-I've tried wiping/uninstalling the app
-I've tried wiping my phone
-The app loads just fine - I click on a movie to either play or download and it fails
Are there any known issues about this Android version and Vudu? I've researched, but I have yet to find a solution or just even an answer.
If any other information is needed, I'm happy to provide it.
Thanks!
Click to expand...
Click to collapse
This VUDU thread explains it all. It may not address your issue directly, but it gets you closer to understanding what's happening.
https://forum.vudu.com/showthread.php?948535-No-HDX-support
The key response being this one from the VUDU engineering dept:
"First of all, sorry to hear that you cannot play it in HD/HDX. This is something beyond our power, let me try to explain why.
The DRM technology that we use is called Widevine (it was the name of the company that Google acquired). Widevine certifies each device into three levels, level 1 is the most secure and level 3 is the least secure. Briefly speaking, level 1 devices are capable of decoding the content at hardware level and level 2 and 3 devices can only decode it at software level.
Our contract with the studios mandates that we restrict the playback of HD/HDX playback to devices with hardware decryption(or widevine level 1), this is the reason why you can only play in SD.
How to know widevine level of your device?
- If you open our app, go the about screen. The last digit after the last underscore of the version is the widevine level of your device.
At last but not at least, once you root you device (or somehow change the signature of the bootloader), widevine will automatically downgrade your level from 1 to 3."
Since the last dev preview up to the final release, I've been having some major issues getting Viper4Android to work properly with Spotify and Google Play Music. For whatever reason, it works for a few minutes after the initial Nougat setup, then stops working whenever I'm steaming music. When I look at the driver status, it says "processing: no."
However, on Pocket Casts things are running normally - which is less than ideal since I turn it off when listening to podcasts.
I've forced permissive mode at boot, removed MusicFX, the audio effects file in the root folder, yet I still can't get it to work properly. I've even flashed various "fixes" and versions of Viper4Android, still, nothing changes.
This is exactly what kept me from staying on the dev previews, and I'm bummed to see nothing has changed since the final release.
I'm on the verge of pulling my hair out! Has anyone successfully gotten Viper4Android to work properly on Nougat, and if so, how?
It is entirely possible that viper needs to be updated due to changes in the coding. This would be something you may want to ask about over at the actual viper forum
To start, the only real reason I rooted my H918 in the first place was so that I could fix the screen retention problem. After I opened that box, I started play around with the phone and eventually installed LOS. I'm currently running LOS 15.1 on my H918 that's rooted with Magisk.
I'm having some weird issues and there are two apps that driving me to ask my question: Pokemon Go and Super Mario Run. I have Magisk hidden from both of the apps. In this state, Mario works fine, but PoGo has frequent issues logging in and usually the only way to fix it is to reboot. I'll usually be able to log in the first time, but if I close the app and go back to it later it usually doesn't log in and I need to reboot. Not to mention I get the frequent "Not Compatible with this version" screen, although usually just swiping it away and reloading it resolves that.
Knowing that LOS has the ability to adjust color values without root, I decided to uninstall Magisk. That appears to fix the issues with PoGo, but then I can't seem to get Mario to play. It just loads the red splash screen and then crashes back to my home screen. As an experiment, I even tried wiping my phone and doing a clean install. Mario would still not run. Looked online and it appeared to be a common issue for LOS users and Super Mario Run. For some reason, rooting and then hiding the root makes Mario play well with LOS. WTF??
So, this is where I'm at. I could likely fix all my problems with both games if I just went back to stock. I don't really need to be rooted for anything I do with this phone... except for screen retention. So I believe I need to be rooted with a custom kernel for KCAL to adjust the colors.... which leads me to issues with PoGo. Its driving me crazy and this is really making me want to get a new phone.
So, that brings me back to my thread title. Is there any way to adjust the color values to eliminate screen retention without being rooted on Stock Oreo (H918)? Perhaps flashing something with TWRP? A non-root app? Anything?
runningslow said:
To start, the only real reason I rooted my H918 in the first place was so that I could fix the screen retention problem. After I opened that box, I started play around with the phone and eventually installed LOS. I'm currently running LOS 15.1 on my H918 that's rooted with Magisk.
I'm having some weird issues and there are two apps that driving me to ask my question: Pokemon Go and Super Mario Run. I have Magisk hidden from both of the apps. In this state, Mario works fine, but PoGo has frequent issues logging in and usually the only way to fix it is to reboot. I'll usually be able to log in the first time, but if I close the app and go back to it later it usually doesn't log in and I need to reboot. Not to mention I get the frequent "Not Compatible with this version" screen, although usually just swiping it away and reloading it resolves that.
Knowing that LOS has the ability to adjust color values without root, I decided to uninstall Magisk. That appears to fix the issues with PoGo, but then I can't seem to get Mario to play. It just loads the red splash screen and then crashes back to my home screen. As an experiment, I even tried wiping my phone and doing a clean install. Mario would still not run. Looked online and it appeared to be a common issue for LOS users and Super Mario Run. For some reason, rooting and then hiding the root makes Mario play well with LOS. WTF??
So, this is where I'm at. I could likely fix all my problems with both games if I just went back to stock. I don't really need to be rooted for anything I do with this phone... except for screen retention. So I believe I need to be rooted with a custom kernel for KCAL to adjust the colors.... which leads me to issues with PoGo. Its driving me crazy and this is really making me want to get a new phone.
So, that brings me back to my thread title. Is there any way to adjust the color values to eliminate screen retention without being rooted on Stock Oreo (H918)? Perhaps flashing something with TWRP? A non-root app? Anything?
Click to expand...
Click to collapse
A stock rooted rom with magisk hide should allow you to play the games you mentioned and allow you to adjust the color.
Sent from my PH-1 using Tapatalk
clsA said:
A stock rooted rom with magisk hide should allow you to play the games you mentioned and allow you to adjust the color.
Click to expand...
Click to collapse
When I first rooted my H918 on stock, I was having the same issues with PoGo that I'm having now with LOS and Magisk. That's one of the reasons I tried LOS. It was working okay at first, but I'm starting to have issues again and it possibly coincides with the recent updates to the game.
Edit: To add a little more information, it appears will fail SafetyNet after a little while. The only root app currently installed on the phone is Kernel Adiutor.
On a fresh boot, I can log into PoGo just fine. I can open Magisk Manager and run the SafetyNet Checker and it passes. Fast forward a few hours and PoGo will not log in. I'll then go check Magisk Manager and test SafetyNet: "ctsProfile: false" and "basicIntegroty: false"
What's changing in that time?
I'm seriously ready to just buy a new phone. Eh, maybe I'll just unroot and live with the screen retention for awhile and see how bad it gets.
So I've had this problem for a couple/few years already where an update from either android or netflix caused the Widevine certification to read as L1 for Netflix specifically. It says version 15.0.. L3 as opposed to the L1 it's supposed to have, DRM INFO says i have L1 ver 14.0...
I previously worked around this issue with a modded Netflix install that half works but even then sometimes the quality will still drop even though the connection can more than handle the stream. I was hoping that after so much time has passed this issue had been resolved by either party (mainly because at one point, another update had left me without netflix on my phone for almost a year and this was before the L1/L3 fiasco) but no such luck.
In the past I've steered clear of rooting the phone, mainly because everytime i try to get into the spirit of things I either have a hard time finding the files needed or the guides I'm pointed towards seem like details to build a nuke.
I'm hoping i can fix this, and I'm willing to bite the bullet and try to root this phone if needed. Any help would be appreciated.