Wouldn't be surprised if the cost of engineering a 0-click exploit for a mainline Linux smartphone running something that isn't Android is now much greater than engineering one for Android itself. You just need a prerelease access to patches for a very good hint of what you can exploit unbothered until Google catches up, upgrades the severity and makes the patch mandatory for next month and all your targeted devices finally receive it.

Posted disinfo again xD

Irl OEMs are given lots of free-hand and free SPL string updates with zero security patches as long as Google decides it's not critical enough.

We know that Samsung applied some of the optional patches, but no such statement came out of Xiaomi, they're now allowed to be much lazier than earlier.

I discussed it all.

https://youtu.be/bFuHNIRkJr8
If you ever wondered how staggered HDR looks like when participating frames get misaligned, here you go. The chance that it's anything else is very slim.

It's not a Samsung moment, fun stuff also occurred on certain Ace 3V serials. It's the internal confusion about the difference between OnePlus, Oppo and Realme. OnePlus bootloaders used to be a backdoor to unlocking the others. OPlus (the name of this 3 brand entity) caught up on it and implemented serial checks inside OnePlus bootloader images. To demise of the users, these checks seem to be fragmented. Once OP phones start going through the "deep testing", OnePlus bootloaders should stop pranking the device owners.

https://github.com/PkmX/lcamera/

If you recognize this app, you're a real one.

Google caused all these not really communicative entities to install modules from the deepest pits of hell. Now they're finally secure.

No, it's not a secret previous owner of your brand new Moto, they indeed perfume their boxes (or phones?) at least on the Edge 50 series.

What they didn't perfume tho is OTA installation experience. It's only incremental to this day. By refusing to use a desktop update tool, you're in for a whole day of updating, and their updates are often far from irrelevant. The things that change make the stock feel somewhat like a custom ROM, with the good and bad aspects of that. Even if you follow just the open source part of their codebase, you'll notice that device specific driver changes occur even long after device release.

Btw: if you take out a Moto from a sealed box, not give it a sim nor wifi, you get a good chance at being able to toggle the OEM unlock instantly.

Wanna hear a conspiracy theory on why the QPR1 source isn't public to this day?

Since QPRs are only ever used by "best partners" and undoubtedly Google thinks primarily of Pixels when developing them, it's very plausible that they feel free to implement the patches they deem secret and optional, in essence, the "patches from the future" GOS was talking about.

If this happens to be the case, the QPR source releases from now on could take up to 3 months, until all of the patches get released on the QPR0 branch. This can mean that A16 QPR1 will get released in December and the "in coming weeks" promise was a big understatement.

A common misconception is that uninstalling a preloaded app is significantly better than disabling it. This aside, Nothing now gets closer to Moto, surprisingly risking their Apple-ish brand image for something that would be more expected on the CMF lineups.

There are two wolves in you:
– "This user should never unlock in first place, he's clueless! He's about to install proprietary susware!"
– "How tragic of a situation it is that solely enabling an ability without even taking advantage of it gets you penalized."

I prefer not to be a rumour guy, but I've heard that bribery services (paid unlock of Chinese Xiaomis at 100$+) are now available again. Does that make Mi 17 more unlockable than S26? Is it morally acceptable to buy it over OP13T and the upcoming OP15T? Uh...

Turns out it's just a dude selling 100$+ global unlock, keep staying away from Xiaomi

Ever wanted to check battery capacity on a device that doesn't report it?
Install https://f-droid.org/packages/com.dijia1124.plusplusbattery, set your correct current multiplier/divider (so that wattage looks right), charge to 100%, disconnect and instantly open the app.

Edit: after hitting 100% and opening the app, turn the screen off for 5 seconds, then unlock again.

Keep rooting, use Aurora, use apkmirror, set your limits.

Thank you Google Play for serving users with apps that have their best interest in mind 🥰

I strongly believe that lots of OEMs can do it to you with a single click. This is a rare case where a third party is allowed to do so to a free market device.

So QPR1 source just got released alongside Pixel feature drop. It seems it was kept a secret not because of unreleased security patches, but unreleased Pixel features.