• 0 Posts
  • 19 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle



  • If google restricts access to its os, like they have already started, all you’ll have is pixel up to 10/11 still supported 10 years from now. They’ve already started by no longer providing device trees in aosp for their phones, so graphene has to work harder to obtain them now. Whereas if you work on lineage, you potentially have a greater number of vendors and potentially new ones ready to open up to draw in new userbase.



  • I’ve worked with Qualcomm SoCs a long time ago and, from my experience, the binary blobs ARE the biggest hurdle to the true Foss phone. Google is the most to blame, IMO, but also the rest of traditional OEMS of SoCs. They basically found the way to circumvent the OSS nature of Linux, which is why even though android is based on linux, the actual product and ecosystem looks nothing like regular Linux. What Google allowed with Android architecture, particularly with their HAL subsystem is force a layer in between native Linux device interface and Android system, so OEMs use that to implement whatever proprietary peripheral (device, sensor, etc) purely in userspace, rather that just as a kernel module. The kernel module is then just a userspace/kernelspace adapter, and everything is handled in the user space. This then means you dont have to have an open source driver, as it is not a part of kernel, and you just lock your driver into a binary blob. And in case of Qualcomm and I assume other oems, everything is just a binary blob. All sensors, microphone, GPS, modem, EVERYTHING. Yes, you can boot a basic Linux kernel, but no other functionality will work. If you had access to the blob source, you’d be able to fix, update and use a newer kernel versions eventually. HAL is technically not the cause of the problem, but it’s certainly an inspiration and almost a blueprint for how to lock down your hardware.








  • From my small experience with Qualcomm in the past, I’m not too hopeful. In a company I used to work for, we wanted to use one of their SoC with Linux, which they claimed they supported. It was many years ago. But was full of closed binary blobs which even when signing NDAs, we couldn’t get the source for. We’re talking user-space drivers, sensors offloaded to a separate core with closed source firmware etc. It’s Linux, but it’s not Linux in spirit, it feels so closed and proprietary and secretive. They’re coming from Android, which google architecturally enabled vendors to close their drivers by utilizing HAL. It’s the single most significant blow to Linux by any corporation so far. It enabled thousands of vendors to close their shitty driver in user-space and not maintain it for newer kernels (kernel driver is just an IO proxy for user-space drivers). I get that without it, there wouldn’t be Android phones we have today, but I expected them to slowly open up. 10+ years later, almost nothing changed, in fact - things seem worse to me.



  • If it works for you, don’t touch it, great. Manjaro mostly just works, but occasional headaches I kept getting, like packages being broken for days at a time, no easy place to look for solution (their repo being different to arch’s makes 99%of the difficulty) made me switch to arch/endeavorOs. Eventually, they may get stable enough to be acceptable, but I don’t think their way is the right way to do it and they may even harm or slow down arch development and community in the process. Just looks like arch with extra steps, so I always recommend endeavorOs, Garuda or plain Arch, before Manjaro. But that doesn’t mean Manjaro is trash and in some cases, it may even be the best solution.


  • Yes, that’s exactly it. You could try out and see what you prefer. I tried everything, but also tastes change over time. I used to use KDE cause it felt more like windows (we’re talking XP era), later I tried Gnome, Unity, xfce, fluxbox, but then I tried i3 and it is really minimal and tiling and I don’t need anything more. Not for beginners, but after some time, it might become your jam.



  • Well, I think it’s a valid comment. I’m a big fan of her work and I watched a few streams, but the voice seems like it’s heavily processed, and to me it’s barely intelligible, which makes me concentrate really hard to try and understand what she’s saying. I ended up not listening to her streams. I now prefer to read blogs and other people’s articles about her and Asahi linux in general.