Wish Meitu could come back from the death (being acquired by Xiaomi) and bring us the abomination comparable to fingerprint sensor in bottom notch. You know what I mean. That would be something...
😐2
https://news.1rj.ru/str/MishaalAndroidNews/2780
No new vendor for y'all Snapdragon 870, 778 people, I guess
No new vendor for y'all Snapdragon 870, 778 people, I guess
Telegram
Mishaal's Android News Feed
The supported Linux kernel versions for Android 16 have been revealed. They include:
Upgrades:
- android11-5.4
- android12-5.4
- android12-5.10
- android13-5.10
- android13-5.15
- android14-5.15
- android14-6.1
- android15-6.6
- android16-6.12
New launches…
Upgrades:
- android11-5.4
- android12-5.4
- android12-5.10
- android13-5.10
- android13-5.15
- android14-5.15
- android14-6.1
- android15-6.6
- android16-6.12
New launches…
😐1
(nvm, 870 is at kernel 4.19 on mainstream devices, so stuck with A15 unless something extraordinary happens)
😐2
Tadi Channel
Update: It doesn't look like it! I'm afraid that we're seeing something more nefarious – a check for custom ROMs specifically. I had no issue in orange state (even "riskier" than yellow, stands for unlocked bootloader) while on stock ROM. PIA was at basic…
Oh... https://grapheneos.social/@GrapheneOS/113887419695660943
Not all oranges are custom ROM (plenty of innocent people with imported Chinese units running global stock), but all yellows are 😏
Not all oranges are custom ROM (plenty of innocent people with imported Chinese units running global stock), but all yellows are 😏
GrapheneOS Mastodon
GrapheneOS (@GrapheneOS@grapheneos.social)
Revolut insecurely checks the ro.boot.verifiedbootstate property and forbids it being yellow, which means a locked device with an aftermarket OS that's being cryptographically verified by the firmware. They permit it being orange, which means an unlocked…
😐3
I want to address a common misconception.
Raws (DNGs at least) are never meant to be dull. No, I don't mean that they should be punchy, but they shouldn't look purged of color. Whenever that happens, it means the metadata provided by your cam stack is incorrect.
Yes, a raw will usually need you to try bringing highlights down or do something to contrast or exposure, but whenever it looks really bad, blame your OEM for incorrect metadata, basic sensor mode, lack of stacking, or worse: forced post processing. Proper raw looks just fine.
Raws (DNGs at least) are never meant to be dull. No, I don't mean that they should be punchy, but they shouldn't look purged of color. Whenever that happens, it means the metadata provided by your cam stack is incorrect.
Yes, a raw will usually need you to try bringing highlights down or do something to contrast or exposure, but whenever it looks really bad, blame your OEM for incorrect metadata, basic sensor mode, lack of stacking, or worse: forced post processing. Proper raw looks just fine.
👍11🤯3❤1😐1
What if the key to render faces realistically is to not do anything special with them and avoid overcooking the image itself?
Naaaah, impossible...
Naaaah, impossible...
🤯9👏3😐3❤2
Tadi Channel
I wrote a post during a cold, so it could be foggier than it needs to, but regardless of that, you may want to read it. What Google has against custom ROMs and root? There's a lot of cheap takes one could have about it, but they're basically: "No one likes…
Better tldr:
PIA enforces device/OS discrimination using hands of app developers. This discrimination forces a device/OS vendor to either ship GMS and sabotage user capabilities (as what you're allowed to do with AOSP must match with Google's interest) or resign from support of apps an average person wants to use. To convince the app vendors to support you regardless, you need to be big enough, and to be big enough, you need very serious money, creating a barrier of entry to the market, consolidating it in result and causing a GMS contract to be mandatory for every sub-9-digit company that attempts to obtain market share between typical users.
PIA enforces device/OS discrimination using hands of app developers. This discrimination forces a device/OS vendor to either ship GMS and sabotage user capabilities (as what you're allowed to do with AOSP must match with Google's interest) or resign from support of apps an average person wants to use. To convince the app vendors to support you regardless, you need to be big enough, and to be big enough, you need very serious money, creating a barrier of entry to the market, consolidating it in result and causing a GMS contract to be mandatory for every sub-9-digit company that attempts to obtain market share between typical users.
👏13😐3👍1
Tadi Channel
Better tldr: PIA enforces device/OS discrimination using hands of app developers. This discrimination forces a device/OS vendor to either ship GMS and sabotage user capabilities (as what you're allowed to do with AOSP must match with Google's interest) or…
That's how it needs to be phrased to lawmakers, "custom ROMs" make it sound like solely a matter of hobby among bored people
❤11
Tadi Channel
https://social.treehouse.systems/@marcan/113914172433692339 Finally something technical!
https://android.googlesource.com/kernel/msm/+log/c6d66c401d23a399a453b64824bb74945e4708d3
https://www.androidauthority.com/pixel-4a-battery-update-explained-3522417/
https://www.androidauthority.com/pixel-4a-battery-update-explained-3522417/
Android Authority
There is even more to the Google Pixel 4a's horrific battery update than we thought
The Google Pixel 4a battery update, which made many devices unusable, hides even more than we thought — and we know everything.
🤯6😐3