Yes

I think the correct tool for my purpose would be something like Popup window, if you care about that part.

SSB is still around, but also not what I was looking for. I just wanted a frameless window (and no other pwa functionality).
Fullscreen I disabled using my window manager. Under Linux you can commonly use alt+F3 to bring up the “right click on titlebar” menu, then disable fullscreen there. Generally ever window manager can disable fullscreen for windows, in a more or less accessible way (cough ms windows dll calls cough).

As mentioned below, This is recovery. I could ban kiosk mode to a separate profile, but unless you invent a time machine this won’t undo having opened kiosk mode in an in-use profile.

Yes, this is more of a recovery operation. Whatever the fix may be, modifying the browser itself to open a window without decorations would be easier.

There are some usecases in which you really don’t want to restart your browser.
The easiest way to update your kernel is to restart your pc, yet there is a market for live-patch kernels.
If someone accidentally infects their instance with kiosk, it may occasionally be preferable for them to follow a complex procedure to recover the instance, rather than doing the “simple” thing of restarting it.

Restarting may solve many problems, but there is a more difficult but less invasive solution almost every time.
Much like reinstalling may solve even more problems, but you can see that doing a reinstallation is not usually the right course of action.

Kiosk mode doesn’t just force fullscreen, it disables right click, the tab and title bar, …
Basically the browser is close to unusable until kiosk mode is ended, which I currently only know how to do via restarting Firefox.
And F11 is also disabled by kiosk mode. Interestingly, on the windows that were started before kiosk mode, it puts them into proper kiosk mode (after which F11 stops working of course).

I guess adb backup was before my time. I did use adb to transfer my apps when I last restored a twrp backup. In perhaps a similar manner to what that did, going by the name. But I did use adb root for that.

Otherwise, I use it to set a lot of otherwise inaccessible settings, like making the back gesture a lot thinner than intended because my touchscreen can handle it, or forcing 120Hz everywhere. I can also set my dpi there without anoying apps.

And ofc I use it to uninstall system apps I don’t need.

After initial setup I do all of that in a root bash session in termux admittedly, but if I hadn’t rooted my device I would still want to do most of that using an adb shell, as most of it doesn’t require root (besides maybe the restoring backups part).

I also use shell environment to semi-automatically transfer media files for certain processes, though I’ll probably move that over to syncrhing at some point.

The main remaining advantage is the ability to automate things on my phone from my pc, I don’t see a lot of those as replacable unless my rom installs kde connect as a system app and they add an immense amount of functionality

thx and wtf.
How can people even use android without adb shell?

I cannot open that, it shows a login page. Could you post a screenshot of what this is supposed to contain?

Shame they lost the display, that was the main benefit of the Xperia line for me.
Regular ~400 dpi screens look terrible and pixelated after being used to 650 dpi.

Guess I’ll have to hope another high dpi phone with headphone jack releases before mine dies.

Nice

This really seemed like a good simplification until you threw in that d’Alembert operator at the end

Does it let you severely reduce padding and let you wrap around home screens?

I’ve had similar problems with kde apps on fdroid. I think they are rebuilding very often and that somehow gives a decent chance they are chaning the file you are downloading. So the store is correctly identifying the apk is not matching the info of the repo, because the repo is outdated compared to the file.
I suspect droidify had outdated repo info while fdroid did not. A refresh would have probably made it work on droidify too.

You can use Simple Play Integrity Checker on IzzyOnDroid (fdroid repo) or the play store. It also checks safetynet.
If gpaywallet works that would indicate 2/3 play integrity if your android is recent I think, so it might be unrelated to the api. 3/3 isn’t enforceable yet afaik, too many legitimate devices can’t pass it.

Apps can still bring their own root checks, but magiskhide should allow you to pass those.
Unless the app is quite nasty and checks for the mere presence of apps that don’t do much without root or xposed, in which case there are also modules that allow you to limit what apps other apps can see being installed (really seeing installed apps should be a permission, but sadly it isn’t on most roms yet)

Indeed. I have found an article which I hope I can simply keep bookmarked to make it a simple task following whatever the next method may be.

But I have also found things calm down considerably over time, google seems to concentrate their resources on recent android versions. Once a15 or a16 are out for a bit, I probably won’t even have to update the module anymore.

All my older rooted phones have access to everything, even after years of not caring at all.

Been paying a bunch on my rooted custom a13 rom in the past 2 months. 1 single magisk module (Play Integrity Fix by chiteroman) was all it took, simpler than it has been in a long time. I have full safetynet or 2/3 play integrity reliably, which to my understanding is all google can reasonably enforce on modern devices and android versions for a while to come.

So with sadness I must say I can’t use google pay at all … cause they killed it. But google wallet (formerly google pay, formerly android pay, formerly google wallet, formerly google checkout), works just fine

How about phones sold preinstalled with a custom rom?

Not like you can from the inside either. You’re just a murder trolley driver, you don’t even have the break keys.

OpenSUSE 42.3 standing tall

Yes, I just updated the post, you can see the process in my various comments.
It seems to be caused by uBlock origin, though I haven’t yet investigated deeper. It might be the combination of the firefox version and the ubo version, and it may be dependent on a specific setting within ubo, I don’t know yet.