Does anyone have any clue on how I can add Widevine Security Level 1 (I only have L3) on my Zuk z2 Plus AOSP Extended v4.5 Official, so that I can watch Netflix @1080P, rather than 480p??? I CANT find any working solution on the web. Please, is there anyone polite enough to reply me, because this is my last hope? I need someone who knows thoroughly all the steps to do this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can stream in 1080p and I do also have the same thing you're talking about, so, maybe that's not the issue?
Its's definitely the issue. If your ROM has Widevine L3, its surely limited at 480p. You may be tricked that its HD, because of the high bitrate (good quality) , but its actually Standard Definition. Please read this as a proof:
“If your device is only L3 compliant, you’re capped at sub-HD resolutions. Only L1 secure devices with processing taking place entirely in the TEE can play back HD or higher quality content from Widevine secured services„
Source:
https://www.androidauthority.com/widevine-explained-821935/amp/
Can't really capture screenshot in Netflix otherwise I would show you.
Here’s what you need to know about Widevine and how it works.
How does Widevine work?
Widevine implements a selection of industry standards to protect content as it’s transferred over the internet and played back on devices. For a quick overview, it makes use of a combination of CENC encryption, licensing key exchange, and adaptive streaming quality to manage and send video to users. The idea is to simplify the amount of work on the service provider’s end, by supporting multiple levels of streaming quality based on the security capabilities of the receiving device.
To achieve this, Widevine protects content across three levels of security, simply named L3, L2, and L1. Your device will need to be certified to meet the full L1 specification if you want to stream HD content from services like Netflix.
ARM TrustZone technology within Cortex-A based application processors is commonly used to run trusted boot and a trusted OS to create a Trusted Execution Environment (TEE), which separates DRM and other processes from potentially exploitable applications.
To meet security Level 1, all content processing, cryptography, and control must be performed within the Trusted Execution Environment (TEE) of the device’s processor, to prevent external tampering and copying of the media file. All ARM Cortex-A processors implement TrustZone technology, creating a hardware separation that allows a trusted OS (such as Android) to create a TEE for DRM, and other secure applications.
Security Level 2 only requires that cryptography but not video processing be carried out inside the TEE. L3 applies either when the device doesn’t have a TEE or when processing is done outside of it. However, appropriate measures must still be taken to protect cryptography within the host operating system.
How Widevine is implemented
Android devices support either L1 or L3 security levels, depending on hardware and software implementations, as does Chrome OS. Chrome on desktops will only ever support L3 at maximum. If your device is only L3 compliant, you’re capped at sub-HD resolutions. Only L1 secure devices with processing taking place entirely in the TEE can play back HD or higher quality content from Widevine secured services.
SOURCE:
https://www.androidauthority.com/widevine-explained-821935/amp/
Related
Found this app via a lifehacker write up, developed by Microsoft ironically.
Basically lets you setup automations on your phone like sending a text to your wife that you're on your way home automatically when you leave work.
There's a collection of recipes you can pick from their site but you can also code any automation you'd like.
I'll let you guys read the article which explains it in more detail. It's currently in beta in the play store.
http://lifehacker.com/5916841/supercharge-and-automate-your-android-phone-with-onx
Here's a screenshot of some recipes on the web interface.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I already use Tasker to manage these things. This is only interesting for the functionality it provides by being location-aware, and able to detect the difference between walking, driving, or being at rest. However, usually that kind of detection translates to a massive drain on your battery life.
How often is it scanning for your location? What's the context it uses to trigger a location scan? What are the parameters for the accelerometer to determine walking, driving, etc?
Such an app is useless if I can't set my own parameters for how often/aggressively the app is scanning for a context.
haven't used tasker...does it allow you to actually code the tasks like on{x} does?
I think what you're asking is all dependent on what you decide in the code. I'll post two examples: first one is text my wife when I'm going home and second is play music while walking
lazaro17 said:
haven't used tasker...does it allow you to actually code the tasks like on{x} does?
I think what you're asking is all dependent on what you decide in the code. I'll post two examples: first one is text my wife when I'm going home and second is play music while walking
Click to expand...
Click to collapse
You can essentially write code for Tasker as well, it's just not presented in any recognizable language to the user, it's more like a simplified approach to coding. You start with a context and write a task for that context. Tasks are written as a series of actions, and you can input if/then/else statements to check for conditions before executing actions. For more complex tasks, you can set variables for several different contexts and have the tasks check against all of them.
Tasker is fully aware of location, wifi, Bluetooth, proximity sensors, screen settings, sound settings, headset plugs, accelerometer orientation, or just about anything the phone is capable of sensing, and also allows third party plugins to add more functionality in terms of contexts available and additional actions that the tasks can execute.
The difference with on{x} is that it has additional preset contexts for when you are moving and where you are located. It's not difficult to write something similar for Tasker, but you're going to run down the battery because the phone is constantly scanning for your location and running operations to translate accelerometer readings to either the walking, driving, or rest states. Whether or not this is actually the case with on{x} remains to be seen, but unfortunately they haven't made public what kind of algorithm they're using to set the phone into these various states.
Pretty interesting app, can't wait to really dig into it
What are some of the best tasks so far you goes have found?
On a side note, I just told my girlfriend I found it weird this is only on Android and she said "How come? Microsoft doesn't have a phone platform" and I thought she was joking, but she genuinely forgot about WP7
Sent from my Galaxy Nexus using xda premium
Problem is, how much will this app affect the battery life?
There are a large number of web sites that place restrictions on who can access them by filtering IP addresses. If you have an IP address from a particular country, you will not be able to view many foreign web sites, particularly those related to streaming media, videos and other such content. On your computer it is fairly easy to set up a VPN to get around these restrictions, and Hideman VPN is a free app that brings this option to Android.
Download from here
The app works by routing your web traffic through one of its servers located in twelve countries around the world. In this way it is possible to trick web sites into believing that you are located somewhere different and thereby access content that would not otherwise be available to you. There is no complicated configuration – all you need to do is click the flag of the country you would like to pretend you are in.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The app can also be used as a security tool thanks to the fact that it will hide your real IP address. This makes it much harder for your online activities to be traced and any traffic you generate is protected using 256-bit AERS encryption. It is a simple system but it works very well and you can be up and running in a matter of moments, regardless of whether you have worked with VPNs in the past or not.
Download from here
.
Thanks for sharing could be useful
will test and report :good:
m_gamal` said:
There are a large number of web sites that place restrictions on who can access them by filtering IP addresses. If you have an IP address from a particular country, you will not be able to view many foreign web sites, particularly those related to streaming media, videos and other such content. On your computer it is fairly easy to set up a VPN to get around these restrictions, and Hideman VPN is a free app that brings this option to Android.
Download from here
The app works by routing your web traffic through one of its servers located in twelve countries around the world. In this way it is possible to trick web sites into believing that you are located somewhere different and thereby access content that would not otherwise be available to you. There is no complicated configuration – all you need to do is click the flag of the country you would like to pretend you are in.
The app can also be used as a security tool thanks to the fact that it will hide your real IP address. This makes it much harder for your online activities to be traced and any traffic you generate is protected using 256-bit AERS encryption. It is a simple system but it works very well and you can be up and running in a matter of moments, regardless of whether you have worked with VPNs in the past or not.
Download from here
.
Click to expand...
Click to collapse
So if i do this, does this apply only for browsers or can i access apps that are not availible in my country on Google Play too for example?
No need to download it's already in play store
Sent from my GT-I9300 using xda premium
thank you guys.....
..............................10/10......................
good luck all............
(I'm going to be cheeky and cut-and-paste this (with some edits) from an earlier post on the Gemini Planet Facebook page, so some people may recognise it if you spend time there.)
Since upgrading my Gemini from Android 7.1.1 to 8.1 I've hit a snag with the Amiga emulator UAE4ARM and other emulation apps that use the SDL library for handling video.
It looks as though the new OS may not be providing the correct screen width to whatever function the SDL libraries is using for their fullscreen display. Whether or not the Gemini's navigation bar is hidden, I lose 10% or so of the screen on the right hand side (or the left, if the navigation bar has been moved) when running these apps fullscreen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All of the apps I've seen this happen to are emulators (UAE4ARM, Vice64 and Unreal Speccy Portable) and while I'm not certain whether Unreal Speccy uses SDL the other two definitely do, which leads me to suspect it as the common factor. The DOS emulator Magic DOSbox uses a different display methodology and works perfectly in fullscreen landscape.
I've tried all available methods for hiding the navigation buttons; Gemini's new settings, UAE4ARM/SDL's built-in Immersive Mode and the Granular Immersive Mode app. All methods exhibit this truncated screen effect. It's interesting to note that in terms of raw pixels, the truncation appears at the same horizontal position that the navigation bar would appear if it were visible. This also coincides with the right side of the titlebar clock, and is only a few pixels to the right of where Planet's own App Bar cuts off, whether or not the navigation buttons are visible.
Everything points to the OS reporting the wrong screen width to certain apps and libraries when the navigation bar is hidden. None of these apps exhibited this behaviour under 7.1.1, but it's unclear to me whether this is a change in Android functionality or a result of something Planet have specifically tweaked for the Gemini firmware (perhaps related to the new built-in ability to hide the navigation buttons?)
I've tried the obvious Google searches but with fairly generic parameters such as "Oreo" "8.1" "width" "SDL" etc. I'm getting a lot of false positives and nothing of actual use.
Does anyone know what might be causing this, and whether there's a workaround to change whatever value the OS is reporting to SDL? I'm pretty sure I've exhausted all of the tweaks available under Developer Options but I don't mind using tools such as ADB to apply tweaks if necessary. I'm even prepared to root the Gemini if that's what's needed, although I'd rather avoid that if possible. I'm really hoping for the equivalent of an .ini or .plist file (you can tell I'm not an Android developer!) that I can tweak.
My next stop will be to contact Planet and let them know, in the perhaps vain hope that this is a simple bug/oversight that they can fix with a later update. The problem with Planet is that their e-mail based support system has no proper feedback channel, so you often don't even know whether your issue has been acknowledged let alone investigated. So I figured I'd run it past the folks in here first, in case I'm missing something obvious.
TIA for any assistance.
We all know that op7t doesn't shoot HDR videos but its does take decent quality [email protected] fps although only unto 5 minutes even after android 11. Theoretically new android os supports writing files more than 4gb but I don't know why still the restriction.
Anyways more than HDR I am always fascinated with wide color gamut which comes with Rec.2020 as the videos look more vibrant and exciting. May be I like to remember places I have visited with this vivid look. So while fiddling with ffmpeg to reduce video size when hevc recording was not supported, I came across a strange behavior of my videos shot with OnePlus 7t. This has been same on official oxygen os android 10 and now 11.
This somehow doesn't apply to [email protected] fps as they still have 1-1-1 Rec. 709 (HD) color profile. But if you notice when you shoot [email protected] the resulting videos have 5-1-6 PAL SD color profile. With a simple command in ffmpeg I was able to change these videos to a richer color profile 9-1-9: Rec. 2020 SDR and I simply love the results.
Before we go any further, for those of you who d like to experiment here is the command to run with ffmpeg. Its independent of phone so If your video is shot from other devices it may work as long as the video has enough data to provide such colors. As I found Rec.709 HD didn't have.
Code:
ffmpeg -i input.mp4 -c copy -color_primaries bt2020 -color_trc bt709 -colorspace bt2020_ncl -color_range pc -bsf:v h264_metadata=video_full_range_flag=1:colour_primaries=9:transfer_characteristics=1:matrix_coefficients=9 output.mp4
As you can notice that these parameters are for videos shot without HEVC selected in the new settings. Advanced users can figure out similar command for hevc videos to experiment.
I have attached a screenshot for reference in which I paused the two video files at same point. The above part is 5-1-6 PAL SD and bottom is 9-1-9 Rec.2020 SDR.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let me know how your experiment goes and what's your take on this. Do you like the videos as they were or with this is new color definition.
This is really cool, thanks for sharing! I've updated your post to enclose the command in a code block
since I have been using the new hevc option in oos11 on my OnePlus 7t, I searched online for a simple solution as above to change color profile of videos.
here it is for use in ffmpeg with hevc videos
Code:
ffmpeg -i INPUT.mp4 -codec copy -bsf:v hevc_metadata=colour_primaries=9:transfer_characteristics=1:matrix_coefficients=9 OUTPUT.mp4
Hello, Recently I decided to get tablet for my car, and I come up with Google pixel C tablet, Which I'd like to use for many reason, to listen music and watch, for camera instead of mirrors, for GPS navigation. I like the size and every specs it has, read everything about it, but There is no GPS? Google pixel c doesn' come with built in gps? Is it true, why did they do so good tablet without gps? it's something like iphone 12 without camera.
I just can't beleive that any modern tablet without GPS, and plus google would have include gps staff in their devices. My question is is it true or did I read something wrong?
commander1874 said:
Hello, Recently I decided to get tablet for my car, and I come up with Google pixel C tablet, Which I'd like to use for many reason, to listen music and watch, for camera instead of mirrors, for GPS navigation. I like the size and every specs it has, read everything about it, but There is no GPS? Google pixel c doesn' come with built in gps? Is it true, why did they do so good tablet without gps? it's something like iphone 12 without camera.
I just can't beleive that any modern tablet without GPS, and plus google would have include gps staff in their devices. My question is is it true or did I read something wrong?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is true.
The Pixel C was supposed to be a Chrome OS tablet. So, because they weren't building the hardware for Android they omitted many standard Android features from the time:
- No GPS.
- No vibration
- Touch screen cannot estimate finger pressure
- No NFC
- A surprising number of hardware components cannot be directly configured even with root because they live in the Chrome OS bootloader
There are also just weird choices or mistakes like:
- Poor WiFi signal
- Catastrophic Bluetooth signal
- 3 GB RAM when the chip supports 4 GB and it was supposed to run desktop Chrome? WAT
- Others. It's a long list really.
But I still love it even though it really should have been allowed a couple of generations for improvements to reach it's potential.