No, it's just that when you use a mainline kernel, you're just not reusing all the Android (often user-space) drivers that make cameras work on Android and due to that stuff, starting from drivers for the SoC camera interface to the camera sensor have to be re-implemented. Whether you are on glibc (e.g., on Debian/Mobian) or musl/Alpine does not really matter.
Also, Camera APIs and the whole "desktop Linux" camera stack (think of things like debayering, white-balance) is nowhere near as developed as what Android has (and that, IUC, Ubuntu Touch can reuse on Halium by plumbing things together).
A Pixel 3a may be a good choice. It's older, but not huge—and it's very well-supported in Ubuntu Touch (and Droidian, both use Halium/libhybris to re-use the Android kernel drivers), and also in postmarketOS (mainline Linux 6.9.3 as of this message).
On postmarketOS, camera support is not fully there—the front camera is somewhat supported. Also, Wi-Fi is still a bit annoying, calls only work with headset on postmarketOS, so I would say: Use Ubuntu Touch or Droidian for now, and maybe move on to postmarketOS once it's a bit more solid.
It should be. With zram, I can use similar software even on a 2 GB RAM device somewhat comfortably, unless I open too many tabs in Firefox.
It's somewhat SoC dependent, but the actual feature support depends on auxiliary chips. Of the well-supported phones, only the Shift6mq supports it in hardware - software support on mainline is not there yet though. The Fairphones 4 and 5 also have the feature. I have the 5, and display out works with postmarketOS, but audio support is still lacking, and USB peripherals (e.g., keyboard, mouse) are not supported.
Here's a list of more devices: https://www.uperfectmonitor.com/pages/list-of-smartphones-with-displayport-alt-mode
That said, there are other ways like DisplayLink and or GUD that may enable you to connect a display to a OnePlus 6 or PocoF1 anyway, some people have done it (and left video evidence on social media or YouTube. It definitely requires a customized kernel, and unfortunately, AFAIK the efforts have not been documented/shared (kernel config and necessary packages).
I don't think reporting the USB ID thing to Plasma is useful and will go far - for 99% of users (that use some kind of Android/AOSP) the modus operandi is fine and helpful. With many Android devices and OSes requiring you to do something on the device after plugging it in, testing does not seem to be feasible to me.
There's no need to add the edge repo, as the latest release of mobile-config-firefox should be in v23.12 by now (it's been updated there since my last post). The command I posted does not add the repo, but only uses it for the one package without adding the repo permanently.
I recommend trying to use KDE Connect (or scp, rsync ... another network based way) to send the screenshot from the phone to your other computer instead.
MTP/other file transfer protocols do not (yet?) work with mobile Linux, so this failure is to be expected. It only shows up for connection, because if your device ran Android, it would be an option — AFAIK, Plasma acts this way because of the USB ID of the device.
Also, regarding your main issue: While you can report this to Mozilla, please be aware that Firefox is being "patched" to better work on mobile by https://gitlab.com/postmarketOS/mobile-config-firefox. I suggest you to install the latest, not yet in postmarketOS 23.12 mobile-config-firefox package from edge first by running:
sudo apk del mobile-config-firefox
sudo apk add mobile-config-firefox --repository http://mirror.postmarketos.org/postmarketos/master
While it may not fix every issue possible, it should improve the experience.
I've been told that PinePhone 2 is not happening this year. (If AllWinner will continue to supply A64 SoCs, it might take even longer.)
Regarding SoC, the likely/obvious candidate is RK3566 - but we'll have to wait and see for the when and how. (I, personally, would love to see a PinePhone V - think PineTab V, but as a phone).
PineTime: It has nice companion apps on Mobile Linux, but I went back to my Pebble Time Steel - the always on display matters to me.
Yeah man, I think the article I initially read about PP Mobian situation was this one here just for reference if I am even remembering right – https://blog.mobian-project.org/posts/2023/09/30/paperweight-dilemma/
Someone stepped up (see https://blog.mobian.org/posts/2024/01/08/highlights-of-2023/ and afaik a-wai also mentioned this at fosdem (https://fosdem.org/2024/schedule/event/fosdem-2024-3290-towards-a-bright-future-with-mobian-/), also long standing issues like the out-of-tree-WiFi/BT driver are being worked on currently.
Regarding Beepy: I really tried, but ... compared to that, PinePhone was easy to get to a somewhat works state in mid 2020. See https://linmob.net/enter-beepy-esc/#flaws
Depends, guessing from this conversation I'd assume there's currently nothing to thank for.
And because of that: If you like Phosh, consider giving back:
- https://liberapay.com/Phosh/ and
- https://honk.sigxcpu.org/piki/donations/ are simple ways to do so :-)
Ubuntu Touch suggests that this will use Halium most likely, which is good for features, but ... it's not mainline.
Although: Thanks to Chromebooks, there are now a few Mediatek SoCs with okay mainline support. But while the Helio G99 seems quite similar to the Kompanio 520 at first glance, they are quite different, sadly.
This sounds a lot like the Flattr model - a service that had its moment in 2010/2011, but ultimately failed: https://en.wikipedia.org/wiki/Flattr
Payments are a challenge, with processing fees and taxes in an international context, small sums don't work out well - there's a reason why services like Liberapay push you to do bigger amounts at one time instead of small amounts at multiple points in time.
This may seem odd, but from a person that has a two-digit amount of phones: You know that it's possible two own more than one phone at a time, e.g., a Linux Phone and a Game Phone? ;-)
Very much not. GNOME Shell Mobile was funded by the German Prototype Fund in 2022 IIRC, way later than Phosh was created (funded by Purism for their Librem 5). GNOME Shell Mobile will eventually be part of GNOME proper (meaning it's Mutter, and GNOME Shell, patched to work on small devices), currently it's a patch set on top of multiple GNOME components that's packaged in postmarketOS and the AUR (if you consider AUR stuff packaged).
Phosh was created on based on wlroots (which is also used in Sway and other wayland-native window managers) and GTK3, as a Mobile Shell. Ironically, this way was pursued because Purism developers where told by the GNOME Shell people that an adaptation of GNOME Shell for Mobile would not be feasible.
Both rely on designs created by (at least then) Purism-employed designer Tobias Bernard IIRC, and thus may seem quite similar despite being based on a different tech stack, and both are hosted on GNOME's Gitlab, using all the same apps.
A blog post about FOSDEM 2024's 'The Linux Phone Apps Ecosystem' talk
Honestly - using Sxmo on a PinePhone Pro is about as hard-core as you can go beyong building your own thing from scratch.
Ubuntu Touch on Pixel 3a, or Sailfish X on a supported device or a Librem 5 with PureOS even is a lot less geeky and more approachable thing.
Officially, yes, but there's also https://elagost.com/flatpak/ Also (shameless self plug): https://linuxphoneapps.org/apps/org.signal.signal/
I wonder how much additional work would be necessary to actually support A64, too.
But for now this is definitely good news to PineCube hackers/users ;-)
The Pixel 3a? As stated on https://devices.ubuntu-touch.io/ it's the best port out there (and my previous experience with a OG Volla/GS 290 confirms this). Now is Ubuntu Touch perfect? No, and everything depends on your use-case (and because of no VoLTE support, the region you are in also matters). You can also try Droidian (https://droidian.org/) with a Pixel 3a, so given likely availability of a working, used device for less than USD/EUR 100 you can't go wrong with it, IMHO.
Just look at https://devices.ubuntu-touch.io/
I have a Pixel 3a and it's a really great port.
Writing this on my Librem 5 as a happy Librem 5 user, I struggle to find a good answer - maybe the Shift 6mq is an alternative (see the discussion on that in the equivalent to this thread in c/linux), as Shift have actively supported mainline development. The PinePhone is slower than the Librem 5, and the PinePhone Pro ... I could not daily drive it, too many bugs and too short active use battery life. If you just don't want to rely Purism shipping soon, you can always try a second hand Librem 5. Also: While I am quite happy, I am an enthusiast - YMMV.
We're back with another overdue update, marking our five year anniversary as well as the official Chimaera release. Apart from the upgrade to Chimeara / Bullseye (from Beowulf / Buster), here are...
Congrats to the project, this is great progress!
Three years and one day ago, the first Weekly Update on GNU-like mobile Linux, then dubbed LinBits, was published. A lot has happened since, and this celebratory blog post is an attempt to summarize highlights on a per-months basis. I'd like to thank Blort for the idea and contributing so much to th...
I figured this might be worth sharing :)
An App Directory for PinePhone, Librem 5 and other mainline Linux phones.
This post lists the apps we added to the app list/LinuxPhoneApps.org in the first three months. If you want to follow along as apps are being added and use a feed reader, https://linuxphoneapps.org/apps/atom.xml is your friend.