BTW, think of it as a litmus test for every "reputable" """keybox extractor""" wannabe (I'm speaking of all keybox sellers who claim to extract them from devices rather than OEM leaks) who won't manage to do anything despite the writeup. Since it couldn't be reliably sold (keyboxes are mostly model/batch-specific, not unit-specific, duh, you're probably lied to by an incentivized person if you're told otherwise), it'd be excellent for promotion of a monetized venture. And yet you likely won't see it for the first time from any such a place. At best, you'll see some AI slop gibberish on why publishing it would be irresponsible, while irl it's just skill issue at dealing with EL3 pwn-ed hw.

BTW, if anyone knows how many keyboxes were ever provisioned in total to RN11S, lemme know, comparing the output from https://github.com/vvb2060/KeyAttestation across different manufacturing date and regions will suffice.

Phrasing it like this makes you quite complicit. It's mandatory age verification for adults through privacy invasive means.

But, does anyone really have to be on THESE social media anymore? Really?

Well, we're going into 2026, and I'm actually not pessimistic, I'm seeing more and more people who notice that governments and corporations worldwide work contrary to individual's interest. The enshittification of everything is an eye opener that does unironically bring people from the opposite political spectrums to actually shared goals. Keep going.

https://youtu.be/u7Uz1YZ5hQA

Since you probably want to hear about it even if you're not the target audience.

Also:
https://clicksphone.com/en/communicator

A standalone phone with 4-inch square-ish screen.



Battery
4,000 mAh silicon-carbon

Display
4.03” AMOLED

Connectivity
Bluetooth, NFC
Wi-Fi: 802.11 a/b/g/n/ac/ax

Cameras
Rear: 50MP OIS
Front: 24MP

Charging
Qi2 wireless charging + USB-C

SIM cards
NanoSIM + eSIM

Wired audio
3.5mm

Storage
256GB on-board + expandable MicroSD card storage up to 2TB

Bands supported
5G, 4G LTE, 3G/2G (unlocked)

Operating system
Android 16

Secure storage
Android Strongbox ready

Size & weight
130.5mm × 78.63mm × 12mm
170g

It's bl unlockable.

Real?!

https://boingboing.net/2026/01/05/everyone-hates-onedrive-microsofts-cloud-app-that-steals-then-deletes-all-your-files.html

Just don't login into OS vendor's online accounts, anywhere.

https://nuxx.net/blog/2026/01/09/oled-not-for-me/

When I noticed significant fringing on an S20+, I thought it's a phone specific skill issue, because the supply chains are longer and responsibility gets diffused. Turns out that a 2025 OLED monitor is the same. It's quite plausible that the controller does support the needed corrections for subpixel rendering (SPR), and yet a monitor company failed the only job they had.

Here's the S20+. It's not a limitation of the subpixel array. In case of one, the colors would be switching sequentially like on a thin cable shot far away with a Bayer sensor. Here, the individual colors are evidently "centered" with a bias to the expected center of the pixel. This allows them to reliably drift in their own direction.

And pretty much yes, I believe that some of the people who thought PWM irritates them, may actually dislike misconfigured subpixel rendering. While fringing is one thing, some of the SPR configurations can result in blur. It's a fairly straightforward topic that probably isn't going away just yet.

Knowing the limits of your hardware before taking photos ❌
Getting a variable aperture ❌
Repainting unfocused faces ✅

Yeah...

https://youtube.com/watch?v=oP7xzAdCYQU

I wonder if they even paid him for using his personal brand, considering he's not in the video even for a moment. Too cheap to collab with a streamer?!

To be clear, Keymint remote key provisioning changes this to a really massive degree.

https://android.googleapis.com/attestation/status

This json will either disappear at some point, get redefined or grow to megabytes, since device-wide (all units running the same build during a given time frame) public listing of revocations would no longer be practical – the banned "serials" would supposedly have to be per each unique app installation. Yes, I'm still trying to comprehend it. No, collecting unit-unique public keys at the factory and uploading them to Google isn't the whole story.

Tldr: if whoever decides to play by Google's rules, attestation/PIA/screen proxying from a device you personally own may actually let you live in peace, but for all it's worth, it really seems that Google won't have to choose between revoking a whole device (bad for PIA adoption) and letting non-compliers in.

To benefit from the new level of control, Google will likely just break the promise of:
"Additionally, Google backend servers are segmented such that the server which verifies the device’s public key does not see the attached attestation keys. This means it is not possible for Google to correlate attestation keys back to a particular device that requested them."

If they won't, why all this effort?

https://linuxiac.com/linux-snap-users-warned-as-attackers-push-malware-through-old-trusted-apps/

Looks like Snaps don't have to be signed before uploading them and then are only signed by the store. A quite bad design.

As a matter of fact, I do wish someone would test this Google's promise, there's nothing to lose because the architecture for granular revocation is now in place and changing it would only be a change of policy, not of client side implementation.