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.
Related
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."
Having cut the cord in the middle of last year I've been running a Fire TV to for some time but haven't been completely satisfied. I am more involved with the Google ecosystem than the Amazon ecosystem using Google Play Music and the Play Store and the like.
My device will be hardwired like everything else in my entertainment center and had a few questions.
1. I root most everything that I buy Android but I did not on my Amazon Fire TV 2. Why would I want to root the shield Pro?
2. This will be my first Shield device, any suggestions or tricks that I should know? I am reading through this forum but I figured beginner's tips for a long time Android User might be helpful.
3. I haven't been able to find anything out about the Google Assistant update coming out yet. Has anyone heard an approximate date for it?
4. Same as number three but about the Samsung SmartThings dongle?
Thanks everybody.
Some threads I would recommend you read up on might be, (or cover).
SSD Migration. Not so much for replacing the SSHD with a SSD, but to make a backup of it! This will likely prove to be one of the smartest things you could do especially if you plan on rooting. In case you ever run into Problems.
Two rooting on the Shield is a kind of miss the only benefit I ever got from it was being able to add Unofficial Channels inside Plex. The biggest reason for me to want to root anything would be to use AdAway. Now I guessing it's the way AndroidTV is setup over normal Android. But, FWIW AdAway just does not do its job of blocking Ads on a sideloaded Chrome Browser at all.
Again depending on which side of the curve you are on with 4k UHD, you will have problems loading up TWRP on the Shield TV. At least this is the case with most reports here, and myself included.
Continuing you could just replace the stock recovery with TWRP, and that would work.. 'Till you get hit with an OTA Update where it's expecting to use the Stock Recovery, and will eventually loop itself without it. If you found yourself with a Shield in late January in that situation. You'd have noted that nVIDIA were lax to release a working v5.x Recovery Image. So you used the one from v3.3.0, and now your bricked!
This is why I suggest you really dig into the SSD Migration Thread(s), in Order to create a clone image of the local HDD first.
I would also add that you probably should ONLY ever fastboot boot recovery TWRP-*.img, and NEVER! fastboot flash recovery TWRP-*.img
But, unless you need Unofficial Channels on Plex, and theres nothing there that isn't already on Kodi. There doesn't seem to be any real compelling reason to root the Shield. And in all fairness I regret having done it now.
That's about 110% of what I was looking for. Thank you.
The new 5.1 release is fundamentally flawed and does not allow apps to set resolution or refresh rates, plus suffers from HDMI blanking/disconnects when set @ 4k resolutions. None of these problems are present in the previous 3.3 version, and I need to switch back. Unfortunately every time I have tried to go back to the previous official firmware from nvidia, I just get blank screen/no signal. So I am stuck on 5.1.
I suspect this has something to do with the partition sizes/layouts, or some other 1 way change which is preventing the older firmware from booting. Has anyone got any ideas how this downgrade can be achieved?
Thanks in advance
I don't think that is possible. Unless you want to brick your Device.
Well that's what happened when I tried it. Thankfully... (Or, not) I have the Pro version so finding a working SSHD backup image was simple enough. But, I don't think you'd be nearly so lucky with just a non-removable 16Gb eMMC Chip.
I also tried it, from Nougat 5.1 to Marshmallow 3.2 and to Marshmallow 3.3.
Unfortunately, this is not working. Fortunately, fastboot is still accessible and I can get it back to Nougat (I've done it several times, the only time I add a problem, it was because of a suddenly faulty USB OTG cable).
That's unfortunate, because now that I'm on Nougat, I can't managed to find a functionnal version of Skype with my Logitech C920 or C930e webcam (while I had it on Marshmallow, with StockRestyle by @zulu99). I tried both with the standard version and with full android (see this post for more details on Skype on the standard Nougat ROM).
Oh well. At least I know I'm not doing anything wrong when I try and downgrade. I'll just have to stick with 5.1 and hope they resolve the ability for apps to set refresh/resolution.
TBH I'm a little perplexed how it got passed testing @ nvidia. Changing refresh rates to match content source is common video playback functionality, and resolves many jerky playback issues.
Thanks for the input!
MintyTrebor said:
Oh well. At least I know I'm not doing anything wrong when I try and downgrade. I'll just have to stick with 5.1 and hope they resolve the ability for apps to set refresh/resolution.
TBH I'm a little perplexed how it got passed testing @ nvidia. Changing refresh rates to match content source is common video playback functionality, and resolves many jerky playback issues.
Thanks for the input!
Click to expand...
Click to collapse
Ah, I thought I was the only one with jerky video playback. Let's hope Nvidia resolves it in a future update soon!
Hi Guys
My Moto G4 Plus is unable to play any sounds at all. I'm pretty sure it's some software problem since there are rare moments where I can listen to some music/watch youtube videos, phone... but mostly these things just don't work. The music fast forwards through the tracks then stops and crashes, youtube doesn't show any videos, etc...
This seems to be a common issue with this device (far too common in my opinion) and I already tried the steps from the motorola forum, such as deleting cache. After even a hard reset didn't work they advised me to use my warranty to solve this software error. But the seller doesn't accept it because it has some cracks.
Meanwhile I unlocked the bootloader, installed TWRP, rooted the device and flashed the custom rom 'lineage' onto my device but still no sound at all.
What could I do further? Hope this is the right place to ask
LeGlitcheur said:
Hi Guys
My Moto G4 Plus is unable to play any sounds at all. I'm pretty sure it's some software problem since there are rare moments where I can listen to some music/watch youtube videos, phone... but mostly these things just don't work. The music fast forwards through the tracks then stops and crashes, youtube doesn't show any videos, etc...
This seems to be a common issue with this device (far too common in my opinion) and I already tried the steps from the motorola forum, such as deleting cache. After even a hard reset didn't work they advised me to use my warranty to solve this software error. But the seller doesn't accept it because it has some cracks.
Meanwhile I unlocked the bootloader, installed TWRP, rooted the device and flashed the custom rom 'lineage' onto my device but still no sound at all.
What could I do further? Hope this is the right place to ask
Click to expand...
Click to collapse
Reflash stock rom and if still doesn't work then may be hardware issue. You can use fastboot method or TWRP flashing with Revivor, CreamPie, or Totally Stock by DroidphilEV.
[SOLVED]
Hi All,
i have read the other posts about similar problems and although they are probably one and the same problems,
i'm slightly new to terminologies and was hoping for a slightly tailored discussion.
That being said i'm going to jump straight in with the story from the beginning,
Around 2 Months ago i bought this Head unit for my car.
Seicane - 9 Inch OEM Android 9.0 Radio 2004-2011 Ford FOCUS EXI MT 2 3 Mk2/Mk3 Manual air condition GPS Navigation system Bluetooth Touch Screen TPMS DVR OBD II Rear camera AUX 3G WiFi HD 1080P Video
I have recently received this and installed it just yesterday.
Now the problems i'm having is that when ever i use anything internet based via a WiFi dongle or hot spot on my phone then the whole system crashes out on me and i have to turn off the ignition.
Also Google is unable to grab my information, It recognizes me and goes through the 2 step verification but gets stuck after accepting agreement, the Gathering Information shows up on screen and then it just loads indefinitely until either the system or the app crashes.
now i'm not sure if these are one and the same issue but do seem very similar, Like once it has an internet connection it is trying to do a background connection to google to pull data but its getting stuck and crashing out again.
So the only way i'm able to use the system is to put it in airplane mode otherwise it crashes and makes the stereo unusable altogether.
So i have contacted Seicane in regards to this issue and awaiting a reply but figure i may have more luck talking with a community of people that know what they are on about.
So i'm going to say i probably need some kind of system update from google and firmware for the system, but cant log into google without the firmware update.
The problem i'm having is i don't know what stereo it is as such..... if someone could help me with this then i may have more luck
I assume its a MTCD board, but is it a PX6 -5 -4 or 104? i have no idea. i don't know if its even a PX...?
any help on that would be GREAT as i may then be able to download the right updates for it and maybe solve this issue that i'm having.
That being said if anyone can take some time to try and help me i would greatly appreciate it.
I look forward to hearing from you.
MANY many thanks,
Frederus
My initial thought on this is that it is probably caused by a hardware fault in the unit, rather than being a software fault. My reason for saying this is that Seicane are a reasonably popular (ie used by many people) brand, and connecting to the internet is a fundamental function of these head units. If it were a software fault, I would expect to see many more users reporting this issue since the software is in fairly widespread use. Since this seems to be (on the surface at least) only happening to your unit, I suspect it is a hardware fault. It would be interesting to see what the manufacturer has to say when they get back to you. Good Luck!
Update
So i have an update for everyone with some Progress.
So after talking with Seicane they sent me a firmware update it was about six months out of date.
After installing this it seems to have helped with the continues crashing issue i was having.
that being said i then lost a few apps like
Netflix, Spotify and my DAB+ app
They also sent me some APK's for Google services and login services, [This didn't make any difference to my login hanging issue]
So i got back to Seicane and informed them of what had transpired along with a short video of what was happening so that they could see this first hand
They got back to me by the morning and sent me the link for the DAB+ apk so i could reinstall and also forward me another set of apk's
Google Services
Login Services
Google Play Store.
i have given these a go this morning,
DAB+ is back and working
Google Services - No difference
Login Services - No difference
Google Play Store. - No difference
I have just sent them another email saying that this hasn't made any difference and await there reply.
After doing some searching i noticed a lot of people have this issue of google getting stuck on "gathering Info" on there smart phones
which is usually a Cache issue, so i will try this once i'm in my car again.
I would attach the link to the firmware update that they sent me for others who may have the same issue, but i am unable to at this moment in time due to forum limitations for new users.
Ill keep everyone informed as and when i have more information.
Update [Solved]
So its been a week or so,
Quick update after going backwards and forwards with tech support at Seicane it turns out it was a combination of the outdated APK and the fact that google was stuck due to an error with the cache, from what i can tell at least,
So in the end i removed all of the google services from the head unit and deleted the caches as well. then forced it to restart and reinstalled Google login services.
This seems to have worked and i'm not having this issue any longer.
That being said i do have an issue where it doesn't want to turn on very occasionally, but this is on a very rare basis and isn't really a problem usually just have to power down the car and reset ignition. except once where i had to hit the reset button, but 99% of the time it is now working fine.
I hope this helps someone who has the same or similar issue.
Fred.