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.

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).

The AI slop's interpretation of lateral overflow integration capacitor 🥴

"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?

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.

1. Make a camera app
2. You need to sell a new device
3. Add a dedicated button unique to this new device as a sign of its freshness
4. Repeat
5. Your UI becomes full of buttons
6. Go on a detox and advertise a redesign
7. Do it all again

4pda iOS theme official

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.

Nvm, they want to close instead. That's not really 100% necessary, but well.

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.

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.

Say what you want, but local tonemapping be like this.

(But if you read my earlier posts, you'll know that buying a dedicated phone for that goal isn't necessary. You may even process raws in bulk if you really want to)

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.

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/

(real)