5 ms·

> We need nerds who care about this to stop typing on hackernews and go start a phone hardware company. We need nerds who care about this to stop complaining a

> We need nerds who care about this to stop typing on hackernews and go start a phone hardware company. We need nerds who care about this to stop complaining about minor things in existing GNU/Linux phones and other similar devices on the market and go buy them. These hardware companies have been there for years already. It's hard to build a profitable and sustainable business only basing on the minority that doesn't mind it being "too thick", "too slow", "not high-res enough" or "unable to run modern PC games" (all of these are real things I heard from people here, no kidding). And I assure you that if you really care, you'll easily find a way to live with a (swappable) battery that lasts 20 hours.

tyami94 1y ago
I own one of these devices (pinephone) and it is legitimately not good enough for day-to-day use (despite the incredible efforts of the people who are working on it's software). I only use my phone for locally-stored music, text-only web browsing and calls/SMS. The Pinephone cannot perform any of these tasks competently. The thing it does best is playing music, but this drains the battery. It will not reliably place/recieve calls/texts (and 911 doesn't work IIRC). It can barely handle basic web browsing. KDE on this device literally pegs both CPU cores to 100% all of the time. Phosh is better but still dog-slow. This is the case even with the many years of improvements the community has been making to these devices. It used to be significantly worse, and the software is monumentally better than it ever has been. I love this device, and it deeply saddens me that it has such major flaws. All of the current Linux phones have major showstopper issues, and saying we're complaining about them being "unable to run modern PC games" is a strawman. The simple fact of the matter is there are no decent mobile Linux options available. The most endemic problem right now is "Linux" phones that use crummy forked vendor kernels and Halium. For all intents and purposes, these devices are trapped in time and can't meaningfully get software updates for major system components. The 2 decent Halium-free options, the Pinephone and the Librem 5, both still use downstream kernels, and the Pinephone's kernel is maintained by 1 person in their spare time. I think it's apparent that this is not sustainable, and one can't reasonably expect megi to maintain this device forever. As sad as it makes me feel to say this, I don't foresee these problems improving for a long time. As of now, I remain stuck with a Moto E6 from 2019 (Android 9.0) as it seems to be the final device ever produced with a replaceable battery, headphone jack, SD card slot, and screws instead of glue.
- oneshtein 1y ago
  > Pinephone's kernel is maintained by 1 person in their spare time Most open source projects, except few popular ones, are maintained by 1 person in their spare time.
  - harvey9 1y ago
    But most open source projects are not the kernel beneath your bank app.
- Klonoar 1y ago
  Halium is fine. If you wait around to be purist on this issue all day, nothing will ever change. Something like e.g FuriLabs is good for growing the ecosystem and getting people actually exposed to something other than iOS/Android.
  - tyami94 1y ago
    Halium is a hack around crummy vendors doing sub-par work. It is technically impressive but it doesn't resolve the underlying issue that the crummy vendor kernel will never be updated. Saying that Halium is not a good enough solution in the long-term does not make one a purist, it's a simple fact. Devices that rely on Halium are dead-on-arrival.
    - Klonoar 1y ago
      Devices that rely on Halium actually work. I’ll take that over your perceived “dead on arrival” status right now - especially since by the time anything in that ecosystem changes I’ll be ready to swap devices again anyway.
      - seba_dos1 1y ago
        Except they don't, not really at least. You can't even run a Wayland compositor unless it's hacked up to support Halium, and that's just the tip of the iceberg. It makes sense when you want to run some better userspace on an existing Android device where having a proper hardware support is absolutely hopeless, but in the end it's not that much better than running your stuff in Termux or WSL and you'll find yourself limited as soon as you actually try to do something unorthodox with it. I'm typing this on a device that doesn't rely on Halium and which actually actually works, without being confined to what distro maintainers happened to manage to hack up or reimplement, so it's not like there are no alternatives.

tyami94 1y ago

I own one of these devices (pinephone) and it is legitimately not good enough for day-to-day use (despite the incredible efforts of the people who are working on it's software). I only use my phone for locally-stored music, text-only web browsing and calls/SMS. The Pinephone cannot perform any of these tasks competently. The thing it does best is playing music, but this drains the battery. It will not reliably place/recieve calls/texts (and 911 doesn't work IIRC). It can barely handle basic web browsing. KDE on this device literally pegs both CPU cores to 100% all of the time. Phosh is better but still dog-slow. This is the case even with the many years of improvements the community has been making to these devices. It used to be significantly worse, and the software is monumentally better than it ever has been. I love this device, and it deeply saddens me that it has such major flaws. All of the current Linux phones have major showstopper issues, and saying we're complaining about them being "unable to run modern PC games" is a strawman. The simple fact of the matter is there are no decent mobile Linux options available. The most endemic problem right now is "Linux" phones that use crummy forked vendor kernels and Halium. For all intents and purposes, these devices are trapped in time and can't meaningfully get software updates for major system components. The 2 decent Halium-free options, the Pinephone and the Librem 5, both still use downstream kernels, and the Pinephone's kernel is maintained by 1 person in their spare time. I think it's apparent that this is not sustainable, and one can't reasonably expect megi to maintain this device forever. As sad as it makes me feel to say this, I don't foresee these problems improving for a long time. As of now, I remain stuck with a Moto E6 from 2019 (Android 9.0) as it seems to be the final device ever produced with a replaceable battery, headphone jack, SD card slot, and screws instead of glue.

oneshtein 1y ago
> Pinephone's kernel is maintained by 1 person in their spare time Most open source projects, except few popular ones, are maintained by 1 person in their spare time.
- harvey9 1y ago
  But most open source projects are not the kernel beneath your bank app.
Klonoar 1y ago
Halium is fine. If you wait around to be purist on this issue all day, nothing will ever change. Something like e.g FuriLabs is good for growing the ecosystem and getting people actually exposed to something other than iOS/Android.
- tyami94 1y ago
  Halium is a hack around crummy vendors doing sub-par work. It is technically impressive but it doesn't resolve the underlying issue that the crummy vendor kernel will never be updated. Saying that Halium is not a good enough solution in the long-term does not make one a purist, it's a simple fact. Devices that rely on Halium are dead-on-arrival.
  - Klonoar 1y ago
    Devices that rely on Halium actually work. I’ll take that over your perceived “dead on arrival” status right now - especially since by the time anything in that ecosystem changes I’ll be ready to swap devices again anyway.
    - seba_dos1 1y ago
      Except they don't, not really at least. You can't even run a Wayland compositor unless it's hacked up to support Halium, and that's just the tip of the iceberg. It makes sense when you want to run some better userspace on an existing Android device where having a proper hardware support is absolutely hopeless, but in the end it's not that much better than running your stuff in Termux or WSL and you'll find yourself limited as soon as you actually try to do something unorthodox with it. I'm typing this on a device that doesn't rely on Halium and which actually actually works, without being confined to what distro maintainers happened to manage to hack up or reimplement, so it's not like there are no alternatives.