You've seen many camera apps with a HDR mode, right? And you may consider them rightfully painful one way or another. But here's something I realized yesterday:
Despite not being based on stacking raw frames, Open Camera lets you obtain a bracketed HDR photo with reasonable distance from an LTM-overcooked look. Additionally, it manages to avoid catastrophic motion artifacts in shadows. Bracketing is an ancient technique that became forgotten way too much once EV0/underexposed ZSL stacking became viable. You may have certain preferences or alternatives that genuinely work better on your device, but this actually works everywhere. I knew of Open Camera's HDR mode since a long time, but only now I thought that maybe it can be configured better than default. And yes, it can.
All of the needed settings are on the screenshots, set manual expo however you want, but be aware that using it can be mandatory for EV0 frame to skip your device's LTM.
Despite not being based on stacking raw frames, Open Camera lets you obtain a bracketed HDR photo with reasonable distance from an LTM-overcooked look. Additionally, it manages to avoid catastrophic motion artifacts in shadows. Bracketing is an ancient technique that became forgotten way too much once EV0/underexposed ZSL stacking became viable. You may have certain preferences or alternatives that genuinely work better on your device, but this actually works everywhere. I knew of Open Camera's HDR mode since a long time, but only now I thought that maybe it can be configured better than default. And yes, it can.
All of the needed settings are on the screenshots, set manual expo however you want, but be aware that using it can be mandatory for EV0 frame to skip your device's LTM.
🤯5🥰2👍1😐1
This media is not supported in your browser
VIEW IN TELEGRAM
Sorry Sharp, but I'm afraid that shorter than usual duty cycle with lesser number of concurrent PWM pulses and a usual pixel rate don't make me buy that it's just like 240 Hz. Even if you managed to hit 50% duty cycle or less at max brightness, even if your pixel rate would be twice the current one, when people are thinking of a 240 Hz screen, they're thinking of one that displays 240 frames per second, not 120. Yes, it feels unique, but so many "news" sites ignore your asterisks and think it's a real deal.
😐2
Tadi Channel
Photo
Context: since the rolling shutter of phone cameras scans from the wider edge, by pointing it directly at another (portrait on portrait), the slow speed of your phone's rolling shutter lets you see how fast is the refresh on targeted display. Larger distortion -> faster. To capture this photo, I used a normal photo mode, to make sure that my sensor isn't operating at a higher speed, making it harder to see the display's pixel rate, as you can see on the (legitimate, not frame interpolated) 960 fps video above, where PWM bands look straighter (just as they are irl).
😐2
"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