Mediatek has been making phone SoCs since forever now, they have two lines - Helios and Dimensity. They’re used in many phones, usually on the lower end. Even Samsung uses them. Both lines have abysmal custom rom support compared to Snapdragon phones, so I don’t think you can hope for much there.
deleted by creator
You realise that if that were to be “fixed”, you wouldn’t end up paying the low price, Brazil would end up paying the high price? One they can’t afford because they make as much in a month as you do in a week, or worse.
A few months ago I needed to install Google home for something Chromecast related, so I quickly searched the play store and installed it. Loaded it up and I see an ad, what the hell. App opens and I realise it isn’t Google Home, it’s something made to trick me into thinking it was when I wasn’t paying attention.
Google is letting their ads steal their own users from them.
Have you tried running xiaomi.eu ROMs?
Not sure what you’re on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify or debsums to verify the files, arch has paccheck, I’m sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won’t boot.
Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.
The message that we approve of the removal of the headphone jack done in order to peddle wireless headphones…
I really like gnome the software, but I’ve started considering moving away from it after a decade simply because of how toxic and difficult gnome the project can be.
If this was done by multiple people, I’m sure the person that designed this delivery mechanism is really annoyed with the person that made the sloppy payload, since that made it all get detected right away.
TIL there are Linux people that don’t use OpenWRT. I always assumed everyone in the Linux community used it. It’s great.
Works great with mt7621 based routers if anyone ends up looking for something compatible.
I use gnome for the most part. I have been checking out kde recently to see how the newer versions stack up (gave up on it during the 4.0 days). As you mention kde supports dpms changes on wayland because they have their own protocol extension for that.
That’s actually my biggest gripe with wayland - the huge amount of fragmentation it has caused. I’m pretty confident that almost all the missing features I talked about are possible on one or two of the compositors, but not all of them. And definitely not on the one I use. I’m sure once some pragmatism takes hold that all the issues will be ironed out, but my plan for now is to stick to X11 until that happens.
For me it’s a million little details that just don’t work. Stuff like positioning windows, removing decorations from a window, remapping buttons on a trackball, setting a graphics output to tvrgb, disabling a display via ssh and enabling it again, etc.
It’s not just about hardware compatibility. It has to be compatible with existing workflows, and it’s currently very limiting.
set -euo pipefail at the top of every script makes stuff a lot safer. Explanation here.
I love how the complaint makes even less sense when you look at the KDE mega announcement from yesterday. The third thing listed is a new wallpaper.
Love KDE, but they have some really annoying users.
Xfreerdp and gnome work really well together for me. Extremely reliable and very quick. My only complaint is lack of multi monitor support.
I remember having this realisation about Mir, but only after we collectively ran it off the cliff wall. The main reason everyone piled on Mir was that it was thought that Canonical would be priming Linux desktop for fragmentation with two competing standards.
But in fact, Mir was providing a solution to the fragmentation Wayland was bringing. Now we have 3, 4, 5 Mir-s, all with slight incompatibilities. Want a feature? Better hope all of them decide to implement the extension after someone proposes it. We know how well that worked in the past.
This is also ironic because the detractors of Xorg constantly talked about the issues with Xorg extensions and how many of them there were. But I never really had to look up which extensions Xorg supported, while I have had to do that with Wayland compositors.
I remember some 10-15 years ago when I’d look at the y windows website every couple of months hoping for some news of progress, simply because I was sick of x11 being so crappy. I hated it, it was so fiddly, it didn’t work right, I just wanted something that worked.
So you can imagine how happy I was when Wayland started taking off. Here was the promise of something better, something that just worked, it sounded amazing. And yet, today I’m still running xorg and I will be for the foreseeable future.
The reason is simply that in the time passed xorg just became usable, I don’t have to think about it, it works reliability, it has all the features I need and I hardly ever have to touch it. Meanwhile, I log into my Wayland session and instantly 3 or 4 of the applications I use daily either don’t work or act weird. I go and try and fix the issues and I’m told to just accept it, or that I actually don’t exist because Wayland works perfectly for everyone. And I’m not even using an Nvidia card, just plain Radeon.
So I quit and go back to what works. Maybe in a couple of years, until then: no thanks.
If you need this frequently, I really suggest you look into GPU forwarding. I have a Windows VM setup with a second card and it works perfectly, I use it for games and CAD all the time. Figure out your iommu groups, pop a second card in your computer (and optionally a second nvme drive if you want max performance), and use virt-manager and the arch wiki to set it up.
For accessing the machine you can use a second monitor input, or you can get a window to the machine with looking glass or moonlight. I use moonlight as it lets me play games from my laptop on the couch, and looking glass was causing windows to crash sometimes.
It’s a bit of work to set it all up but when you’re done it should just be one XML file and maybe one modprobe.d config file.
I think I’ve been using this for over a year now and the single pain point I encountered in all that time was maybe that usb input hotplug isn’t supported, though there’s ways to fix that, but I haven’t bothered.
A DE has little to do with this, it’s a driver, it gets loaded when you plug in a compatible device, there’s no interaction. This should have been disabled 2 years ago when the gaping security holes were found, and actually Greg had attempted to have it disabled in 2022 but it kept getting pushed back.