Trusted Execution Environment - OnePlus 3 Questions & Answers

Hello,
Does the OnePlus 3T have a Trusted Execution Environment (TEE) installed that I can develop on?
If so, is it a Trustonic module by any chance?
Thanks

Related

Trusted Face for x86 devices

Hi guys,
I installed the latest version of the Lineage OS (14.1 for Zenfone 2 ZE551ML) and I also flashed the super gapps, but when I go in the smart lock section I do not see the face detection option.
I have an x86 processor.
Thanks in advance
I'm in same situation, does anyone a solution?
Hi, I'm trying to compile and make usable the app "Trusted Faces" on my Zenfone. The biggest problem is the facenet.so library, which I can't get on x86 platform.
I hope I get to a conclusion soon.

Project Treble Support?

Hi, just recently purchased this device through T-Mobile. Figured it was a great deal on a device with an actual unlockable bootloader from a carrier. Updated to 8.0 and noticed there's no Treble support. Does anyone know why this is? It's odd since this is one of the few devices that already utilizes the A/B slots for updates. I'm guessing Moto doesn't use a vendor partition? Is there any other reason why they wouldn't implement Treble support? And is there anything we can do on our end to try and encourage or enable support (doubting enabling since I don't think there's a vendor partition)? Just looking for more info on the situation.
Thanks

OxygenOS 10 Dynamic Software Update support

Hi everyone,
On the Android website I've read about the Dynamic Software Update. A feature that comes with Android 10 and lets anyone run a GSI based image without flashing on their Treble compatible phone.
The requirements also state that the phone has dynamic partition activated.
Now that we've got Android 10 on our OP5T is this feature enabled?
I've tried running all the commands, the DSU application starts but there is no install of the GSI image.
Is something that I need to do?
Thanks,
SYA

What is the relation between legacy GSI *_ab build targets and A/B seamless system updates?

In the Android documentation we can read about legacy GSIs:
The following legacy GSI build targets are for devices upgrading from Android 8.0 or 8.1 to Android 10. Legacy GSI names include the suffix _ab to distinguish them from Android 10 GSI names.
Click to expand...
Click to collapse
It also says the following:
The legacy GSI build target named aosp_$arch_a had been phased out. For the devices upgraded from Android 8 or 8.1 to Android 10 with ramdisk and non-system-as-root, use the legacy GSI aosp_$arch_ab
Click to expand...
Click to collapse
So apparently the *_ab suffix indicates among other things (older VNDK binaries) a build target that has no system-as-root. So this probably has nothing to do with A/B seamless system updates. Can anyone explain then why these legacy build targets are called as they are ("_ab")? It seems they have no relation with -ab- and -aonly- community GSI builds such as this one, right?

Question Is it possible to enable pKVM support for the Poco F3 manually using root, or does it require custom kernels to be made by ROM developers?

The title pretty much, the pixel 6 and 7 support pKVM, which allows us to boot Windows 11 ARM or ARM64 Linux images in a virtual machine.
I saw somewhere that it either requires root to enable, or it must be enabled when the kernel is compiled, is it possible for this to work on the F3?
Interesting question.
I think we won't get pKVM-support, unless someone gets GKIs (Generic Kernel Images) working on Alioth (or perhaps more accurately, on the Snapdragon 870 sm8250).
Our device's 4.19 Kernel is too old, and doesn't have Rust-support, which I think is needed to run the crosvm VM Manager. It's part of Android 13's Virtualisation-Module, under the package-name "com.android.virt"
The Pixel 6 and 7 are running a much newer kernel, and it's GKI.
I don't know about pKVM-Support of other GKI devices. There could be more requirements for pKVM-support (besides arm64, GKI-based Kernel and Android 13).
Here are some articles I checked out:
How the Android 13 Virtualization module uses pKVM to boot virtual machines
Android virtual machines are changing in Android 13, here is everything you need to know about VMs in the newest version.
blog.esper.io
How to run a Linux VM on Android 13
Android 13 adds a virtualization feature. Here's how to use it to run Linux in a VM.
blog.esper.io
Android 13 DP1 allows Google Pixel 6 to run full-fledged Windows 11 as a VM
The Android 13 DP1 unlocks the full KVM functionality on the Google Pixel 6 and 6 Pro. You can now boot Windows 11 and Linux VMs on these phones.
www.xda-developers.com
Getting started with Protected Virtual Machines
https://twitter.com/i/web/status/1492754683445669893

Categories

Resources