I just updated my 2025 Moto G Stylus 5G to Android 16 only to discover the only feature I updated for doesn't work on my device thanks to Qualcomm.
That was one of the "upside" of a samsung with an Exynos vs the Qualcomm ones
this post was submitted on 25 Mar 2026
22 points (100.0% liked)
Android
33704 readers
25 users here now
DROID DOES
Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
founded 2 years ago
MODERATORS
Yeah, my last phone was one of the Galaxy phones with the hardware locked bootloader. I should've looked a bit harder when choosing my current phone for one with a bit more open source support, but I think I'll be pretty happy once I can get Lineage running.
I don't think this is the fault of Qualcomm. For some reason I can't get behind, this feature requires some virtualization mode with lowered security features. The older Qcom chips only support regular secured VMs.
This article states the Snapdragon 8 Gen 5, the latest Snapdragon chip, does not support non-protected VMs. This doesn't seem to be a feature taking a while to be implemented, they've made the deliberate decision not to add support for this, just as other vendors have decided the opposite.