Does Vivo (and not just them) really think that people are buying compact devices in 2026 because they're cheaper and not because of size? X300 FE is missing both stacked and full res raws in its stock camera. Can X300 and X300 FE buyers really be convinced "I should buy an Ultra next time" because of few unadvertised differences?
🤯5😐2👍1👀1
https://github.com/x-spy/CVE-2026-43499-popsicle
https://github.com/Linuxoid-cn/Mi8E5-Unlocker-by-CVE-2026-43499
Freshly manufactured/updated Mi 17 series buyable again for a while.
https://github.com/Linuxoid-cn/Mi8E5-Unlocker-by-CVE-2026-43499
Freshly manufactured/updated Mi 17 series buyable again for a while.
GitHub
GitHub - x-spy/CVE-2026-43499-popsicle: CVE-2026-43499 Implementation for 6.12.23-android16-5-g75e9b1c7ae7c-abogki463945075-4k
CVE-2026-43499 Implementation for 6.12.23-android16-5-g75e9b1c7ae7c-abogki463945075-4k - x-spy/CVE-2026-43499-popsicle
🔥8😐2
Can't be arsed describing the lore, but Google designed an API for Android 13 vendors that's basically meant for torch power control outside of camera apps. Two versions later, they realized that something designed as a part of camera API should rather have something to do with it.
In short, OPlus adapted it, Xiaomi and Vivo did not.
https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.magnifier would be the only camera app taking advantage of this API that I'm aware of if you want to try it out.
Why did I look into this? For the sake of Aperture PoC that utilizes manual focus that works seamlessly through logical cameras and an intuitive flashlight power slider. The first is more straightforward to add because of the above.
In short, OPlus adapted it, Xiaomi and Vivo did not.
https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.magnifier would be the only camera app taking advantage of this API that I'm aware of if you want to try it out.
Why did I look into this? For the sake of Aperture PoC that utilizes manual focus that works seamlessly through logical cameras and an intuitive flashlight power slider. The first is more straightforward to add because of the above.
👀3😐2
https://9to5google.com/wp-content/uploads/sites/4/2026/07/Pixel-11-Glow-teaser.mp4
Here's your notification LED, on the back, likely unable to function as one on stock, but certainly pulsating in a cool way to the voice of Gemini.
Here's your notification LED, on the back, likely unable to function as one on stock, but certainly pulsating in a cool way to the voice of Gemini.
😁6😐5❤1
https://fxtwitter.com/NexToWeb/status/2078339101435072847
Ain't an animation if it doesn't make you automatically fall from a bike
Ain't an animation if it doesn't make you automatically fall from a bike
FxTwitter
Mohit Kharbanda (@NexToWeb)
The Capabilities of the HONOR Robot Phone is incredible
#HONOR #RobotPhone
#HONOR #RobotPhone
🤯13😁2😐1
Forwarded from ColorOS System Apps Updates
OnePlus unlocking policy in the China market has been updated.
https://bbs.oneplus.com/thread/2175833961601695750
https://bbs.oneplus.com/thread/2175833961601695750
一加社区
一加手机官方论坛。一加手机开箱体验、测评报告、玩机技巧、手游攻略。与你分享美图及摄影技巧,众多大神教你轻松刷机,并由丰富手机资源任由下载。百万加油大家庭,交流更随心,一加社区官方论坛
😐2👍1
ColorOS System Apps Updates
OnePlus unlocking policy in the China market has been updated. https://bbs.oneplus.com/thread/2175833961601695750
OPlus is killing OP's global market presence with so much dedication that they're going out of their way to presumably prevent even the import of Chinese units. They want it gone off the global market, you must all buy Oppo now in their mind.
😐10👍2😁1
Tadi Channel
To run an untouched (just kidding, the toggle in question and GP signing cause your app to be far from "untouched") original app enrolled into this unnecessary restriction, use: pm disable com.your.app/com.pairip.licensecheck.LicenseContentProvider
Update:
This shouldn't need to be repeated, but:
PairIP doesn't protect your app against modification and redistribution. The extent of needed binary modifications can't be high if a single command beats it. It only serves as Google's sneaky anti-competitive measure that aims to force users to always be logged into a Google account to use your app, even after installing an untouched, legitimate version through Aurora Store or APKmirror or from a backup they've made themselves.
PS: in dev console it's called "automatic protection".
pm disable com.your.app/com.pairip.licensecheck.LicenseActivityThis shouldn't need to be repeated, but:
PairIP doesn't protect your app against modification and redistribution. The extent of needed binary modifications can't be high if a single command beats it. It only serves as Google's sneaky anti-competitive measure that aims to force users to always be logged into a Google account to use your app, even after installing an untouched, legitimate version through Aurora Store or APKmirror or from a backup they've made themselves.
PS: in dev console it's called "automatic protection".
👍4😐2😁1
Tadi Channel
Update: pm disable com.your.app/com.pairip.licensecheck.LicenseActivity This shouldn't need to be repeated, but: PairIP doesn't protect your app against modification and redistribution. The extent of needed binary modifications can't be high if a single command…
FYI: it looks like you'll still need to have PlayStore/FakeStore (com.android.vending) installed after disabling the activity, otherwise the PairIP-infected (yes, it's quite a valid word, considering most developers don't know the full implications, while being enrolled by default for all new apps) apps will crash in ~2 seconds.
😐1
Tadi Channel
I need these questions answered on public record by a googler: Will a developer who wants to publish solely on F-droid still have to provide personal details to Google? Will Shizuku be broken? Would a victim change the system clock to bypass the 24h wait?…
https://kitsumed.github.io/blog/posts/android-may-soon-restrict-on-device-adb/
Oops, looks like wireless ADB is somehow too convenient to access and your granny will use it to bypass the 24h cooldown and install malware 🤯
Oops, looks like wireless ADB is somehow too convenient to access and your granny will use it to bypass the 24h cooldown and install malware 🤯
Kitsumed Blog
Android May Soon Restrict On-Device ADB, Affecting Shizuku, libadb and Developers
Changes proposed for ADB could kill an entire ecosystem of open-source power-user apps, mobile developer setups, and rootless privacy tools based on Shizuku.
😐3👀1