Madis

A fork of the open-source abandonware Yuzu Browser. Both have a highly customizable interface.

What difference would it make if CEO got a minimum wage if there is no stable income stream for the company regardless?

Well, if they steal ideas but not the implementation, why would they have to mention them? Either way I’d say upstreaming GrapheneOS features is a win-win for all, including GrapheneOS itself.

Man, that original three tab layout is exactly what I want.

https://f-droid.org/packages/com.looker.droidify/

…but it has a built-in option to do so nowadays. So while you won’t get in industry-wide change, you can still help your friends and relatives. Nowadays, any drawbacks are fairly small anyway, mostly to do with few broken site logins or not being able to use external comment forms (add an exception if you’d like).

Actually, that workaround is no longer required. Which doesn’t invalidate my point though.

Well, it was about compatibility years ago, too. But when they did the Fenix project, I remember initially only about 5 extensions were available to install, even if they could’ve allowed more with the APIs available back then. Then it took years again to get access to the full store of extensions.

Edit: also, where did themes go? It isn’t that hard to overlay a horizontal image on the toolbar like before.

And yet they introduced nonsense restrictions on them after overhauling the interface few years ago.

It is still possible to make 90% of that screen harder and keep only the crease as the weak point.

They used to be? When?

Play Store already does a weird thing to some niche apps where you have to have to click twice on an app to even see full details like screenshots. For example, look up the app “SecondScreen”.

Widget stacks and per-screen customization as well.

Another article blurring the lines of a skin and a launcher. I don’t care what your default launcher does, not gonna use it anyway. System-wide features, on the other hand…

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.

Probably Google Play Services, motion sensors, heuristics