Android 13 flashlight brightness adjustment app for Pixel 6, 6 Pro and 6a. (and Galaxy S22 on One UI 5 beta)

Features:
• You can add a "Brightness control" tile to the quick settings for easy access;
• Support for dynamic colors and themed icon;
• Support for predictive back gesture;

• Demo;

You can't install this app on earlier Android versions.

Thanks to @polodarb for the build.

Google News | En

As media directly copied the imprecise claims of my friend on what staggered HDR actually is, let me correct it:
Typical sensor capture process works in a way that as long as your exposures are short, the integration (exposure start) of next frame won't happen any sooner than than the cycle of next frame, which basically starts when each of the sensor lines start integration, top to bottom. So for a sensor in 30 fps mode, it won't matter if your exposure time is 1/800s or 1/40s, you won't be able to capture more frames just because their exposure time is short.
Staggered HDR changes that. A sensor in such mode is able to have more than one ongoing integration start at a time, as long as a given line already stopped integration for the previous frame. This is better than bracketing typically is, as it lets the frames represent a narrower range of time. But it's really not a perfect timing match, the frames won't represent the same exact moment in time. To achieve that, you still need to rely on either dual...

/triple conversion gain merge or gain-based QHDR (or Nona, Hexa etc. equivalent of it). It's a good moment to remind of the Samsung presentation I linked here: https://news.1rj.ru/str/TadiBlog/111

A graph I made representing the non-staggered (typical) operation of a sensor. It's a bit idealized, as it skips the blanking time and other margins.

You may want to say "hey, but the sensor has limited clocks and same definitely goes for the output!". And well, you'll be correct. Staggered HDR isn't an on-sensor merge, meaning that it somehow has to output at basically the same rate as it captures. And that leads me to one simple guess: staggered operation is achieved by slowing down the scan to the levels comparable with slower frame rate modes, exchanging the minimal rolling shutter distortion for smaller "temporal gap", which is how Samsung calls the time not covered by any exposure.
And make no mistake, a sensor outputting 90 frames per second in staggered mode is able to do the same in normal operation mode.

Something more sleek for the very few:
https://f-droid.org/packages/com.cyb3rko.flashdim/

SafetyNet attestation in Telegram for Android

Beta version of Telegram for Android has begun performing a SafetyNet check before sending out the SMS authorization code. This was discovered by developers of the unofficial Nekogram modification.

Telegram Info found out custom ROM users don't need to worry.

SafetyNet API, developed by Google, is a tool that app developers can use to detect unofficial modifications within the app and on the system, such as mods, root access, and custom ROMs. This technology is used to protect against piracy and improve security by blocking the app or certain features on devices deemed unreliable by the developer.

Some users have expressed concern that Telegram's implementation of SafetyNet may indicate that the app will no longer allow SMS codes to be received from devices with unofficial ROMs or that the app will cease to function on these devices altogether.

However, a deeper analysis of the app's code reveals that Telegram is using SafetyNet to test a new method of delivering SMS authorization codes via Google's Firebase service, which requires the device attestation. The old method of sending codes will still be used in other cases, leading to the conclusion that Telegram does not intend to impose any sanctions on users of unofficial apps or mods.

The use of Firebase may be related to the high cost of sending SMS messages and calls for authentication. The delivery of codes accounts for a quarter of the messenger's expenses.

#Android

Heck, I forgot to mention the phone, obviously:
https://m.gsmarena.com/quick_camera_comparison__galaxy_s23_ultra_vs_galaxy_s22_ultra-news-57427.php

Samsung is expectedly non-compliant on S23 Ultra

https://www.xda-developers.com/poco-x5-series-launch/

A release of sm6375 and sm7325 device in February 2023.
If Google won't bend the GRF rules, these devices will only get one system update (UPDATE: or two, because they supposedly start with Android 12 as per @kacskrz). Aside from this fact alone, it's quite impressive that the VNDK these phones are running is two whole versions behind sm8550. I don't think a VNDK gap this big happened on freshly released devices very often in pre-GRF days.
Looks like Qualcomm really priced their S and T vendor SoCs too high.

Further cost cuts confirmed, third party clients won't be able to make Telegram send an SMS to you. You'll need an already logged in device to receive the OTP in Telegram service message if you want to add a session of a third party client.
https://news.1rj.ru/str/NekoUpdates/363

⚠️ Beware of seismic activity ⚠️
https://9to5mac.com/2023/02/16/exclusive-this-is-iphone-15-pro-thinner-bezels-thicker-curve-design-no-lightning-port-more/

The JUST DON'T LOGIN TO GOOGLE ACCOUNT FOR YOUR ENTIRE SYSTEM OR BROWSER thread:
https://twitter.com/MishaalRahman/status/1629315374679306240