I could not work out why my Sony headphones were giving me a ding sound and then my listening was interrupted with ambient noises. I assumed Bluetooth connection requests at first, but for me it was the “speak to chat” feature that can be disabled.
This is the answer, much of what makes bazzite good is it’s mostly just fedora, and they can be set up near identically, sans immutability.
Replying from an Xperia 5 IV which is my first 21:9 display. I sympathise that they fixed the ratio but made the whole phone larger! They would also need to restore the compact line or make those slight reductions to restore it back to a more friendly size.
They added the double tap home to scroll the top of the screen down so you can reach it, and if they think that’s a necessary feature I’d argue the design is wrong!
Thanks for letting me know about the new ratio, not quite 16:9 but not as bad as 21:9.
I really wish they would ditch the elongated display ratio. It’s wasted space in landscape 99% of the time, makes the top of the display inaccessible with one hand and the phone unnecessarily large in your pocket. The premium on these could be justified when all the features hit that mark but this is poor human ux.
I tried bazzite, which is very close to kinoite, as Fedora itself had a great out of box experience, even on laptops.
Whilst there was a way to get most setups, apps and configs working it was clear I would eventually run into a piece of software that the effort to get it working was not worth it. Some software and development tools are not (yet) designed and maintained to easily work in an immutable environment.
My biggest gripe was that any interaction with os-tree meant that updates now started to take a really long time building the image with high CPU/power usage. I wasn’t ditching Windows to go back to a world of unnecessarily long updates.
For some, I can see the immutable can work well if they want an Android like experience and can accept the software catalog available. It wasn’t the right model for me, as I expected my machine to do more than point and click app install. I would be curious how your typical arch user would find it.
There’s only so much that can be done on the hardware/ firmware side, but his for me is the real gap that Linux can improve upon. Hibernate, disk encryption and secure boot/tpm unlock together have just worked for a long time on Mac and Windows.
The kernel decisions seem hostile and hard code a big assumption that it’s always unsecure to restore from hibernate automatically. What’s more insecure is having to disable disk encryption entirely. Secure boot is often misunderstood, but for all its flaws it is better than nothing, and your average user does not want to manually enter a decryption key on top of their user login all the time.
Because of this I feel a lot of software is not written and tested with hibernate in mind, so you also roll the dice on what works and what doesn’t when restoring today.
Sleep for 1 hour and then auto hibernate after, in a working setup, meant this problem was solved - always enough battery to resume doing work, no user decision required, quick wake up if resuming a recent session.
I’d love to see multi-user switch selectively suspending user processes and writing them to disk, so you can quickly restore state between users, and if one user left a browser or game running it’s not draining the battery on what are now known background tasks. No OS does this one well today.