"Acer" (actually Indkal licensing their brand name) has a phone that claims to have the first 64MP LYTIA sensor. And yet, the specifications of two phones they released talk only about IMX882 (which is 50MP and has an assigned LYT-600 name) and IMX682 (a dated 64MP sensor that would be exceptional to ever get a theoretical LYT name). What's going on?
😐5👍1
Tadi Channel
"Acer" (actually Indkal licensing their brand name) has a phone that claims to have the first 64MP LYTIA sensor. And yet, the specifications of two phones they released talk only about IMX882 (which is 50MP and has an assigned LYT-600 name) and IMX682 (a dated…
For context, the phone in the pic comes with IMX682, so the 64MP part is valid, but there's nearly no way Sony would agree to have LYTIA written on this device.
😐3👍1
GrapheneOS guys WILL ABSOLUTELY release a REALLY MAD post for one certain thing that occurred. Google stopped releasing Pixel device trees.
GOS GKI and GOS GSI incoming. Or something.
Sadly I can't tell you how much it'll impact the fancy and obvious device features. Pixels aren't known from 100% perfect Treble compatibility, so a regression actually noticable by users can genuinely occur.
GOS GKI and GOS GSI incoming. Or something.
Sadly I can't tell you how much it'll impact the fancy and obvious device features. Pixels aren't known from 100% perfect Treble compatibility, so a regression actually noticable by users can genuinely occur.
😐16🤯3👍2😁1🎉1
Tadi Channel
GrapheneOS guys WILL ABSOLUTELY release a REALLY MAD post for one certain thing that occurred. Google stopped releasing Pixel device trees. GOS GKI and GOS GSI incoming. Or something. Sadly I can't tell you how much it'll impact the fancy and obvious device…
Nvm, they want to close instead. That's not really 100% necessary, but well.
😐14😁6👍3🤯3❤2🎉2
Tadi Channel
GrapheneOS guys WILL ABSOLUTELY release a REALLY MAD post for one certain thing that occurred. Google stopped releasing Pixel device trees. GOS GKI and GOS GSI incoming. Or something. Sadly I can't tell you how much it'll impact the fancy and obvious device…
I wish GOS stays with us, no matter the PR failures and potential technical regressions.
They were among the very few projects (and probably biggest among them) to call out how Play Integrity API causes market exclusion of Google-less OS and device vendors. If to think strategically, they need to create a requirement table to evaluate the state of the market and perhaps even ditch Pixels if a different OEM manages to be sufficiently trustworthy. The problem of half-baked security patch implementations is real, but at the very least, it's worth showing exactly why the other OEMs wouldn't qualify.
They were among the very few projects (and probably biggest among them) to call out how Play Integrity API causes market exclusion of Google-less OS and device vendors. If to think strategically, they need to create a requirement table to evaluate the state of the market and perhaps even ditch Pixels if a different OEM manages to be sufficiently trustworthy. The problem of half-baked security patch implementations is real, but at the very least, it's worth showing exactly why the other OEMs wouldn't qualify.
❤24😐2
Tadi Channel
FYI, all-competent HMD forgot to restrict bootloader unlock on HMD Fusion running build 00WW_2_430_SP01 (April 2025) or older, user security is at a great risk 😭 Remember to install the latest patch quickly to prevent yourself from abusing this dangerous vulnerability!
FixupX
Hikari Calyx (@Hikari_Calyx)
To unlock the bootloader for HMD Fusion series (including Barça Fusion, Xplora Fusion X1)
1. Enable OEM Unlocking in developer options.
2. fastboot oem unlock_factory
If that doesn't work, please report your current build version (00WW_X_XXX shown in about…
1. Enable OEM Unlocking in developer options.
2. fastboot oem unlock_factory
If that doesn't work, please report your current build version (00WW_X_XXX shown in about…
🔥4
Tadi Channel
It is a sleek, gold smartphone engineered for performance and proudly designed and built in the United States for customers who expect the best from their mobile carrier. I'm displeased to announce it's not fake.
No, it's not running Snapdragon 6g1. Laugh hard at me if it actually happens to be qcom. It being the same thing as REVVL 7 Pro 5G is impossible. The ODM behind it wouldn't allow it to look so stupid.
😐4😁1
Do you have a device abandoned by official LOS? Back in February, LineageOS for microG released LOS 18.1 builds for devices like LG G2 and Redmi Note 5 Pro. Whatever you do with them, that's pretty cool.
https://download.lineage.microg.org/
https://download.lineage.microg.org/
🤯5❤2🔥1😐1