What I don’t understand is do any of the OEMs giving this feature also combine it with passthrough power? So besides not charging the phone at 80%, it would keep it working using the wire instead of the battery.

Perhaps you could report it to Google Play for that?

I’ve noticed that XDA still has the main threads and download links, even if more frequent communication happens elsewhere.

Having used custom ROMs for years, it can get tiring to fight with SafetyNet, find root backup apps that still work, dealing with bugs the developer may not be able to reproduce and, of course, even finding decent phones that have decent ROMs. I refuse to buy a Pixel until they have a decent SoC and price.

So for my next phone I’m currently considering an OEM that supports phones for long and has decent customization by default - Samsung. As I’ve never owned Samsung phones before, I don’t know whether I’ll like their OS, but so far it looks good enough.

So it took 4 major releases to make the quick settings reasonable again… I’m actually glad most other OEMs did not follow when Google did the change in 12.

every app wanted to have its own persistent notification

When? Which apps? I’ve been using Android since KitKat and I only remember persistent notifications by apps that needed them (to keep working, stay in memory).

That said, I agree that a permission would be nice, as I am skeptical of the use cases shown in the article mockups. I think it should stay an ongoing notification thing as anything else would indeed take more space.

But it would use less energy afterwards? At least that was claimed with the 4o model for example.

Yes, by default every Chromium browser is affected. It is just a matter of

• whether they want to extend it to the enterprise time (which Edge and Opera won’t do IIRC)
• whether they’d try to keep it working after enterprise time (maybe Brave and Vivaldi, but it could take a lot of effort)
• whether they even have an alternative place to download extensions from if CWS takes MV2 extensions down (Brave has some workaround for few extensions, not sure about others)

Maybe there will be some devs working on Ungoogled Chromium to keep the support, but they also have to think where users would even get the extensions from.

We will now [Oct 9] begin disabling installed extensions still using Manifest V2 in Chrome stable. This change will be slowly rolled out over the following weeks. Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension. For a short time, users will still be able to turn their Manifest V2 extensions back on. Enterprises using the ExtensionManifestV2Availability policy will be exempt from any browser changes until June 2025.

https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline#october_9th_2024_an_update_on_manifest_v2_phase-out

So there is no single date for normal users, but June 2025 is fixed for enterprise (and expected date for Brave, Vivaldi)

Probably Google Play Services, motion sensors, heuristics