Linux Phones
pine64.org
A new community update! New hardware to announced and previous hardware to return!
This is a follow-up to my earlier posts: https://lemmy.sdf.org/post/12809764 https://lemmy.sdf.org/post/19600671 ## We're Getting Closer. It's just small stuff left that needs a bit of piecing together, though I've now been daily driving my port for the past two weeks already. ### This Works - booting - display - touch - modem <- You might have to switch to the other slot if it does not work: `mmcli -m 0 --set-primary-sim-slot=1`, options are `1` or `2`. Note that the modem could also be a different number, maybe try `-m 1` if it is not found as the command will reboot the modem and then it changes. - plymouth - battery/charging - mobile data - wifi - torch - suspend - call audio - vibration - Bluetooth™ - full disk encryption - eSIM (I'm working on the packaging for the tool you need to provision it) - SMS - audio (ALSA config not packaged, but can be added manually) - camera (have taken a few photos, but the kernel driver is still work in progress and sometimes it just does not work) ### This Has An Unknown Status - Fingerprint Sensor - NFC (should work, does so on pmOS) ### This Does Not Work Yet (Soon™) - GPS - USB host mode (no Kernel support yet, but apparently this is being worked on) - Verified Boot (first need to do research whether this is actually feasible) ### This Is Missing And Will Come Later - accelerometer - magnetometer - ambient light sensor - barometer ### Project Status #### To Do List - Make installer images work on this device - Have droid-juicer run on installer images - Get into the repos: `tinyalsa` and `q6voiced` (I've already packaged both) - ITP for Tinyalsa: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079473 - ITP for q6voiced: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080483 - Combine SDM670 kernel patches with those in the Mobian qcom kernel ##### Done List - New release of qcom-phone-utils required so that my patches are available from the repo - https://salsa.debian.org/DebianOnMobile-team/qcom-phone-utils/-/commit/4f77281197c6ba1cfc1a82596157d00e8a7e014b (firmware folders) - https://salsa.debian.org/DebianOnMobile-team/qcom-phone-utils/-/commit/9aa29a1d0bd2327e9c74317d516a8aeecf820304 (fixes bootimg generation with LUKS) - https://salsa.debian.org/DebianOnMobile-team/qcom-phone-utils/-/commit/3ddb192b5c78b444065f23647b373ad66ce3617d (fixes on-screen keyboard for LUKS passphrase) - Remove hard-coded value in the `droid-juicer` systemd unit - https://gitlab.com/mobian1/droid-juicer/-/issues/4 - Make sure my `q6voiced` package no longer includes a hard-coded config for this device (known solution, need to implement) - add udev rule for the vibration motor to the right package - https://salsa.debian.org/Mobian-team/devices/kernels/qcom-linux/-/issues/3 - upstream: https://source.puri.sm/Librem5/feedbackd/-/merge_requests/139 #### Misc Issues - ALSA config for the device has not been upstreamed yet - Issues with 5 GHz wifi - Can be worked around by forcing the phone to only use the 2.4 GHz band, for example using `nmtui`, the network settings of GNOME/Phosh are bit too simplistic for that - No idea how to get the call audio on Bluetooth, meaning you will have to hold the phone or use a cable, for now (This is a non-exhaustive list) #### Low Priority - create/find script/tool that brings up Bluetooth & then package it - https://salsa.debian.org/Mobian-team/devices/kernels/qcom-linux/-/issues/5 Other than that... Everything should be there. It's definitely usable already. Just a few smaller quirks to iron out and two packages to get into the repo. ## The Sources (Use The Source, Luke) - My efforts of packaging a device-specific kernel: https://salsa.debian.org/erebion/sdm-670-linux (which will be used until all patches are part of upstream Linux and we can finally use a regular mainline kernel) - mobian-recipes, which is used to build images: https://salsa.debian.org/Mobian-team/mobian-recipes - droid-juicer, which retrieves some important files from some partitions: https://gitlab.com/mobian1/droid-juicer - https://wiki.postmarketos.org (lovely folks, thanks for sharing everything you found out the hard way :D) Thanks For All The Fish Huge thanks to be sdm670-linux project and flamingradian who runs the project (just one person!) to make sure the Kernel works on those devices! :) I don’t know how Kernel development works, so I would have never started porting without this project. Find that here: https://gitlab.com/sdm670-mainline/linux ## Questions Accepted / Ask Me Anything About The Project I will gladly answer all questions, I hope that more people will start porting if it becomes clear that this is not arcane magic. It’s mostly just arcane. And a community of friendly people that try to be helpful.#
DeltaTouch is a DeltaChat client for UbuntuTouch.
Hey there, I installed Kasts from KDE on Phosh, all the icons are missing and it therefore is difficiult to use. How can this be fixed? Do I have to install some sort of icon package? Maybe someone even knows the exact Debian package that's missing. :D
I was gonna buy a pinephone, but i want to know if this is really the best choice. I'm a real fan of the hardware switches. Any recommendations?
Hello internet, what is the current state of re-locking bootloaders on devices that previously ran Android? Any implementations? How does that work?
It looks like ubuntu touch on the fairphone 4 is nearly perfect, and the features that don't work I won't miss. I'm very tempted to buy a second hand fairphone 4, but I can't really find much on the experience of ubuntu touch. How do you install apps? Are there repo's that I can look at? And is it just branded ubuntu touch, or will any ubuntu apps made for arm work on ubuntu touch? If anybody has some links or personal experiences they could share, that would be greatly appreciated. Thanks a lot in advance!
I want to buy a mobile phone that would be great for linux mobile (ubuntu touch or postmarket os), fairphone 4 would be almost ideal if it wasn't so big (i'm currently using pixel 8 + GrapheneOS). What do you recommend for my desire to use a compact mobile for linux + a solid camera? Thanks for the answers.
As Google Chrome warns uBlock Origin may soon be disabled in the future. They’re going to eventually ban adblockers for chromium. We need to quickly respond with alternatives to android, we must end this market consolidation.
This is a follow-up to my earlier post: https://lemmy.sdf.org/post/12809764 (I re-used the photo as it was quicker and because the UI still looks the same, anyway, five months later.) Time for an update on where I got with the Pixel 3a / 3a XL so far: ## I Am Getting There. There isn't that much missing anymore. Will probably soon try this out as my daily driver, just did not yet have the time to configure all the applications I need. :) ### This Works - booting - display - touch - modem - plymouth - battery/charging - mobile data - wifi - torch - suspend - SMS (only receiving was tested, but I don't have reason to believe sending wouldn't work) - vibration (udev rule needs to be added to the corresponding package) - audio (ALSA config not packaged, but I'll get to that...) - Bluetooth™ (mac address has to be set after each boot, one single command, should probably package a script, still thinking about the right path) - eSIM (supported, but needs a bit more testing) - camera (front camera buggy, back camera works but patches not in git yet) - GPS (needs some improvements to accuracy) ### This Does Not Work (Soon) - USB host mode - call audio (requires packaging `q6voiced` to get audio from the modem, but of course VoIP would already work) - full disk encryption (no installer images yet, once the other stuff is done this will magically be there) ### This Has An Unknown Status - Fingerprint Sensor - NFC (no idea what software I could use for testing, but should work, does so on pmOS) ### This Is Missing And Will Come Later - accelerometer - magnetometer - ambient light sensor - barometer ## The Main Issues That Prevail - A systemd unit with a hard-coded value, that has to be manually edited for now - ALSA config not yet packaged, has to be manually copied for now - few things to do for kernel packaging and then submitting that to Mobian - no call audio yet, as the daemon (q6voiced) is not yet packaged, but can be manually added for now (I'm considering just using VoIP until I can get to that :D) - simple script that brings up Bluetooth has to be added somewhere Other than that, I cannot think of anything else that would be missing. ## The Sources (Use The Source, Luke) - My efforts of packaging a device-specific kernel: https://salsa.debian.org/erebion/sdm-670-linux (which will be used until all patches are part of upstream Linux and we can finally use a regular mainline kernel) - `mobian-recipes`, which is used to build images: https://salsa.debian.org/Mobian-team/mobian-recipes - `droid-juicer`, which retrieves some important files from some partitions: https://gitlab.com/mobian1/droid-juicer - https://wiki.postmarketos.org (lovely folks, thanks for sharing everything you found out the hard way :D) # Thanks For All The Fish Huge thanks to be sdm670-linux project and flamingradian who runs the project (just one person!) to make sure the Kernel works on those devices! :) I don't know how Kernel development works, so I would have never started porting without this project. Find that here: https://gitlab.com/sdm670-mainline/linux # Questions Accepted / Ask Me Anything About The Project I will gladly answer all questions, I hope that more people will start porting if it becomes clear that this is not arcane magic. It's mostly just arcane. And a community of friendly people that try to be helpful.#
I personally don't use it, but I often see people complaining that they cannot use it on their Linux phone and that might help. I stumbled across a project which implements the client connection, like the app does, for WhatsApp: https://github.com/WhiskeySockets/Baileys That would allow building a third-party WhatsApp client. That should also be relatively simple to integrate into a Matrix bridge such as mautrix-whatsapp. Apparently it uses the same API as the app, but it authenticates as a web client. If someone were to implement the authentication of the app, people could start using WhatsApp without the app and also comfortably bridged to Matrix. You can still link the bridge to the app currently, but the app needs to be online or the bridge will get disconnected after a few days. And if you don't want to have a phone constantly running, you probably want a VM for the app and then that all gets fiddly. Also, I recently found a blog post on how to build Matrix bridges, so that should be feasibe if anyone wants to implement that as part of the existing bridge: https://mau.fi/blog/megabridge-twilio/
I don't care how repetitive i am :( I've waiting for a similar experience since the jornada 720. y'all just don't know how good you have it (not to say there aren't glaring improvements that could be made) [https://0x0.st/XBT5.png](https://0x0.st/XBT5.png) [\#pinephone](https://mastodon.social/tags/pinephone) [#pine64](https://mastodon.social/tags/pine64) [@linuxphones](https://lemmy.ml/c/linuxphones) [@linux](https://lemmy.world/c/linux) [#jlime](https://mastodon.social/tags/jlime) [#jornada](https://mastodon.social/tags/jornada) [#arch](https://mastodon.social/tags/arch) [#sway](https://mastodon.social/tags/sway) [#swayisbae](https://mastodon.social/tags/swayisbae)
[Via linmob](https://linmob.net/weekly-update-23-2024/). Apparently the OS it uses is a fork of Droidan (meaning it uses Android kernels with Halium).
cross-posted from: https://lemmy.ml/post/16868638 > I was thinking about using graphene OS, but I've read some lemmy users dislike this OS due to perceived misleading advertising and the pixel 7a you're supposed to install graphene on because it's from google (an advertising company). > > Another option would be lineage OS, but there is so much false information about this OS, namely compatible phones that simply don't work with this OS and no support. > > what works for you? I want a phone with no google, that doesn't force me to use the manufacturer's ecosystem and that won't show the apps I don't want or need (on an asus I own you cannot neither get rid nor hide bloatware)
me seeing the [#pinephone](https://mastodon.social/tags/pinephone) haters as a former [#openmoko](https://mastodon.social/tags/openmoko) owner. [\#pine64](https://mastodon.social/tags/pine64) [#pinephonepro](https://mastodon.social/tags/pinephonepro) [#sxmo](https://mastodon.social/tags/sxmo) [#waybar](https://mastodon.social/tags/waybar) [@linuxphones](https://lemmy.ml/c/linuxphones) !linux@lemmy.ml [#spotify](https://mastodon.social/tags/spotify)