A slight correction, DGO doesn't seem to be equivalent to DCG.

https://web.archive.org/web/20211027145610/https://downloads.canon.com/cinemaeos/DGO-Sensor-White-Paper.pdf

Unless one of the two photosites always has a different gain than the other, DGO is prone to motion artifacts in form of gaps in motion or clipping below the white point. I couldn't observe this on DCG, while it's easy on QHDR despite the simultaneous exposures.

And example of what can happen to QHDR despite the simultaneous exposures. The sole fact that the shorter exposures don't cover the same length of time as the long results in missing information for highlights. This obviously also affects staggered HDR, but even more, as exposures become fully sequential.

You can fight against this artifact specifically, but you'll either have to guess the missing data or prefer shorter exposure data for areas with motion.

I don't think I said it here, but the only OEM to fit denoscription by GrapheneOS communications is Nothing.

If it won't be them, it'll be a bust. I can't imagine HMD or Sony cooperating with a hardening-oriented third party system maker sufficiently, while Motorola, Samsung, OPlus, Honor and Vivo are way too proud (and in business of earning from preloaded bloat) to consider such a collaboration.

If none of the above, then it simply won't be a major OEM as much as it was claimed.

https://www.androidheadlines.com/wp-content/uploads/2025/12/Motorola-Edge-70-Ultra-AH-exclusive-image-1.jpg

Noooooo... :(

From patterns embedded in spaghetti to this 😳. Prepare accordingly or something.

https://support.google.com/pixelcamera/answer/16507662?hl=en
For reference, as you can see, they're clearly not about individual's authorship, where the image author would be the one holding the signing key. It's attestation of "genuine device" embedded in the captured media.

Their design is so much non-private that they had to mention a "strict no-logging policy" on their servers.

Qualcomm has an error in the 7g3 brochure, this SoC doesn't support 4k60 encoding and you can verify it in every possible way (I did).

I've heard people are interested in reading more, this is one additional resource that describes completely authoritative use of content credentials that includes concepts like app whitelisting:
https://security.googleblog.com/2025/09/pixel-android-trusted-images-c2pa-content-credentials.html

I wanted to post this pic and say I miss Syncthing Lite, meanwhile it's resurrected and I didn't notice, wtf.

https://github.com/researchxxl/syncthing-lite/

Yes, we deserve file browsing over P2P without constantly running Tailscale that occupies your Android VPN slot. To get "normal people" off the cloud, you need syncing and browsing that works between their phone, tablet, wife and her husband, while the only laptop at home is sleeping.

The dev handling it is fresh and kinda odd, don't get your hopes up :( There's a mini-drama regarding that at https://github.com/researchxxl/syncthing-android/issues/16.

Want to clean up your storage, but have no idea where to even start? It's simple and psychologically effective and assumes you're already in a root shell of your terminal:
cd /data/
du -ma . -d 100 |sort -n

No, -d doesn't stand for deletion of your files, it's depth. You'll get a relatively quickly generated list of largest directories and files sorted by size in less than 20 seconds unless you check on a desktop with HDD.

https://www.reddit.com/r/NothingTech/comments/1peea5e/ive_found_one_source_of_40_battery_drain/

The worst thing about bloatware is system integration that doesn't make it possible to cut it off without consequences.

(It's something I gotta give to the straightforward uninstallation argument – there's a higher chance that the system won't insist to run an app that was intentionally removable)