Techlore Surveillance Report

Android 16's Dark Side Threatens Every Custom ROM

10 snips
Jun 16, 2025
In this discussion, the hosts delve into how Android 16 could complicate custom ROM development after Google omitted key Pixel device trees. They also explore the implications of a massive data leak from China and an alarming TikTok dataset allegedly for sale. In a surprising twist, a new dating app matches users based on their browser history, sparking privacy debates. Additionally, they touch on passkey portability advancements and the troubling rollback of cybersecurity measures by the Trump administration.
Ask episode
AI Snips
Chapters
Transcript
Episode notes
INSIGHT

AOSP Reference Moves Off Pixel

  • Google shifts AOSP reference from Pixel to Cuttlefish, removing Pixel device trees and full kernel history from Android 16 source.
  • This makes building custom Pixel ROMs harder and forces developers to reverse-engineer binaries or rebuild device trees.
INSIGHT

Pixels Lose Their Special Treatment

  • Google's move levels Pixels with other Android devices by removing special device-tree support developers previously enjoyed.
  • Expect increased upfront work each Pixel release and potential collaboration across ROM projects to share device-tree effort.
ADVICE

Back Custom ROMs Financially

  • Support or donate to custom ROM projects if you value device choice and privacy alternatives to stock Android.
  • Contribute financially or with testing to reduce risk these volunteer projects drop support for Pixel devices.
Get the Snipd Podcast app to discover more snips from this episode
Get the app