This should work on Jolla's Sailfish OS phones as they're running a legit Android in a sandbox. Unfortunately their hardware support is pretty abysmal if you want all features working - and since it's legit Android it's also not free (monetary) and Sailfish OS's UI toolkit is also not free (freedom).

edit: also, last time I checked, Bluetooth support for Android apps is terrible, basically only audio work(s|ed).

And then there's the installation options that look and behave exactly like a regularly themed Qt application (which it probably is). Wonderful!
Okay, I'm coming from Gentoo and Debian, cut me some slack, I'm easy to please regarding installers :-P

Maybe you should actually have read OP's post.

Unfortunately this is not a time lapse of random developers in pajamas sitting in front of their computers, typing in text, googling stuff on StackOverflow, occasionally scratching their heads and occasionally shouting "fucking Akonadi!!!".
Very disappointed!

/s in case it wasn't obvious

Or issue a DMCA takedown if they violate OP's copyright. Much cheaper, much faster.
But very much illegal if OP's copyrights aren't being violated.

Gentoo.
Everything just works and I can configure everything the way I want.

In the vast overwhelming amount of cases tooltips show additional information that you cannot see from clicking on something or provide an explanation to an option that isn't available without scrounging through a manual. None of those apply here.

In current versions of Firefox you hover your mouse over a non-active tab [...] to see (after a small delay) a tooltip containing the web page title.

Uh... what is the point of that? If I am looking for a specific tab then:

• I probably want to switch to the tab that I am looking for, so staying on the current one is not required
• if there are a few tabs from different pages from the same domain the difference might be hard to see on a thumbnail (similar page headings with logos)
• and most importantly: opening the tab is faster than waiting for the delay anyway

This sounds like a "cool" feature that's looking for an actual problem to solve.

dpkg-reconfigure sysvinit

I don't remember what I was trying to achieve, but it was a bad idea. I also didn't (and still don't) know how to fix the outcome of this, so - since my home was on a separate partition anyway - I just reinstalled Debian since that was much quicker anyway.

That something entirely different than the protocol being biased towards Linux. It's like complaining that TCP/IP is biased towards Linux because the Linux kernel's networking module can't be used in BSD kernels.

A crash in the window manager takes down all running applications: Yes, because the compositor IS the server, window manager AND compositor at the same time.

Maybe not anymore in the future: https://blog.davidedmundson.co.uk/blog/qt6_wayland_robustness/

Wayland is biased towards Linux and breaks BSD

FreeBSD already has working Wayland compositors by the way.

X11 and Wayland are just protocols. These protocols are used to abstract the window drawing from the actual hardware and runtime environment as much as reasonably possible - because nobody wants to maintain 3215 versions of their app for different runtime environments. So in order to be shown on the screen an app needs to implement either the X11 or the Wayland protocol (or both!).

The piece of software that is on the other side depends on whether the app is using X11 or Wayland. For the sake of simplicity let's assume that the app does only support one of those. If the app supports Wayland then it will try to connect to a Wayland compositor. The compositor implements every part of the protocol and makes sure that the window is rendered on the screen and that user input is forwarded to the app. If the app supports X11 then it will try to connect to a X server and take the role of an X client. This is (on Linux, essentially) always X.org*. X.org also implements every part of the protocol and makes sure that the window is rendered on the screen and that user input is forwarded to the app.

* Unless you're running a Wayland compositor, then it will connect to XWayland which passes through the window to your compositor.

Wayland compositors have full control over the apps while the abilities of apps are purposefully restricted.
A window manager is just another regular, boring, old X client connecting to the X server. It doesn't actually abstract anything. It can move windows because the X11 protocol allows it to, but any other X client could just as well move all other windows around, read all user input to all other windows and even move the mouse around as it pleases.

So, to be specific, there is no mouse pointer bug in Virtualbox while using Wayland. There is a mouse pointer bug affecting specific Wayland compositors, likely because they enforce GPU hardware acceleration that is lacking in either your VM or the Linux kernel because of missing drivers. Try using a different compositor, (re)installing Virtualbox Guest Additions with the correct version on the guest system and/or check whether hardware acceleration is enabled for the VM and has enough video memory.