I don’t know. If by usability you mean a better user experience, I don’t think so. I haven’t noticed many improvements in this area for years. That’s why many wine wrappers exist, and I’m fine with that. Personally, I value it more when the wine team focuses on improving the common virus library APIs for better application compatibility.
No, it has never happened to me. I think the software somehow detected when the phone was in a hand. But when I ran while holding the phone, it sometimes turned on.
Holding the power button when the screen is off works pretty great and won’t ever activate on accident. It is also a default Android feature I believe.
It seems okay.
It’s a Motorola gesture. I don’t have a Motorola anymore, but I think shaking is the best gesture for turning on the flashlight.
deleted by creator
Why is the microphone running after launching the app? I built the flatpak from the instructions.
Haha, that’s true.
Wine imitates Windows, so applications behave just like they would on real Windows — basically, one prefix is like one Windows installation. And in many cases, users even replace Wine’s built‑in DLLs with native ones from Windows, so those files can’t really be hidden because applications expect to see them.
I like Steam’s approach where game files are stored separately together with the prefix settings, and when you launch a game it just runs inside its own Wine prefix. Still, I can easily imagine cases where this setup doesn’t really make sense — for example when you need several programs working together in the same prefix, like some mod installers that expect the main game to be there as well.
If you’re interested in Steam’s approach, you should also check out UMU launcher and more here bottles UMU integration
PS: Wine itself is a general‑purpose engine, while the frontends are meant for regular users. Even though I compile it regularly, I haven’t really used plain Wine directly in a long time.