1
There's Saldo: https://flathub.org/apps/org.tabos.saldo
No idea, but you could of course install Waydroid on Mobian. I hope Android Translation Layer (https://gitlab.com/android_translation_layer) will at some point get to a state where it is usable as the superior Waydroid alternative for many people.
No idea, but you could of course install Waydroid on Mobian. I hope Android Translation Layer (https://gitlab.com/android_translation_layer) will at some point get to a state where it is usable as the superior Waydroid alternative for many people.
Also, I keep some notes up to date over on my Forgejo instance: https://git.erebion.eu/forgejo/erebion/sargo-temp
129
Follow-up Two: Mobian on the Pixel 3a / 3a XL
(lemmy.sdf.org)
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 are1or2. Note that the modem could also be a different number, maybe try-m 1if 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:
tinyalsaandq6voiced(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-juicersystemd unit - Make sure my
q6voicedpackage 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
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
- Can be worked around by forcing the phone to only use the 2.4 GHz band, for example using
- 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
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.#
I'm working on porting Mobian to the Pixel 3a, pretty much everything works, even eSIM. The kernel dev is already working on upstreaming the patches, some are already in the next Linux release.
I've recently posted about the progress: https://lemmy.sdf.org/post/19600671
Updates to that post would be that eSIM does work and that the internal microphone will work very soon once the already existing patches are pushed to the git repo.
Much better than my Pinephone, lol
I cannot complain. I have not used it for a whole day yet as I am mostly fiddling with the kernel packaging and I want to get call audio working before I use it as my daily driver, but I have no reason to believe it would not last the whole day. No issues here. Probably longer battery life than with Android. It does not constantly talk to Google, after all. xD
74
Follow-up: Mobian on the Pixel 3a / 3a XL (getting close)
(lemmy.sdf.org)
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
q6voicedto 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-recipesdroid-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.#
Only if you have a different use-case or if you are a fundamentalist. Most software is not inherently bad, it just might not be what you want.
Not having systemd was always the only reason I did not seriously consider using it, now I will have to re-consider.
Those are impossible to hard brick in my experience, you would need to break both bootloaders and recoveries. See if this helps:
https://flash.android.com/welcome
Also, Pixel 3 has different hardware, but is supported by pmOS and I've spotted some commits in Mobian, so there might be people working on it there.
Same, my Pinephone does that within an hour maybe xD
Oh, I don't mind questions. :)
Help: A lot via the Mobian Ports ( #mobian-ports:matrix.org ) Matrix room and the postmarketOS offtopic ( #offtopic:postmarketos.org ) Matrix room.
Sources: Not much there yet. As soon as there are official builds for the Pixel 3a, I will start writing docs. I already have a lot of notes on what I had to do. But first I need to have someone merge the Kernel patches, as I don't know C, which makes resolving merge conflicts really hard, it turns out. Once that is done, there are just a few smaller merge requests left and builds will appear magically.
The whole process is not that difficult if there are already Kernel patches available. In the case of the Pixel 3a, I only had to clone the sdm670-mainline repo ( https://gitlab.com/sdm670-mainline/linux-patches ) , compile the kernel (two commands) and get a .deb, which I used with mobian-recipes ( https://salsa.debian.org/Mobian-team/mobian-recipes/ ) to build an image. I then wrote a config file for droid-juicer ( https://gitlab.com/mobian1/droid-juicer/-/merge_requests/4 ) which tells it what files on the vendor and modem partitions it should get, then those are copied to /usr/lib/firmware/updates/.
That was easy as dmesg will just tell you what files it cannot load because they are missing. Just find those, write the config, run droid-juicer, reboot... boom. Display, Wifi, LTE and so on working.
Then smaller stuff like udev rules for vibration and an initramfs hook ( https://salsa.debian.org/DebianOnMobile-team/qcom-phone-utils/-/blob/debian/latest/initramfs-tools/hooks/qcom-firmware?ref_type=heads ) so that firmware files get integrated into initramfs and components start to work early during boot.
The most difficult part would be merging the Kernel patches with other patches and resoving the merge conflicts... At least to me, as I don't know C.
If there are no mainlining efforts for a phone yet, then I don't know what to do, as that requires a Kernel dev.
For the Pixel 4a you mentioned, there is a postmarketOS port. So this should be doable. ( https://wiki.postmarketos.org/wiki/Google_Pixel_4a_(google-sunfish) )
That's all not that hard, my main difficulty was finding out what to do. Everything I did so far would be an afternoon of work, if I had just found the necessary information much quicker. Instead I spent two weeks, of which 95 % was finding info, lol.
Just join the Mobian Matrix room, we should be able to help you, even though I know far less than the others there...so far. :p
I do hope that's helpful and I'll happily try to answer more questions. :)
Kernel mainlining effort for the SoC in thr Pixel 4a: https://github.com/sm7150-mainline/linux
163
Got Mobian (almost) ported to Pixel 3a / 3a XL
(lemmy.sdf.org)
Most parts work, still not sure why Bluetooth gives me errors in dmesg, audio out works, microphone input not yet... I'm getting there.
But graphics, charging, low standby power consumption, LTE, wifi... those all work already.
The fact that postmarketOS has support and also that there are people working on mainline support, makes this a task that is not as difficult as I thought, as most work was already done for another distro.
Otherwise it runs more fluid than Android ever did on it and it has a great standby time (forgot to turn it off at around 80 % and a few days later it was at 58 %).
For now stuck on merging the Kernel patches from the sdm670-mainline project with those from Mobian, not really something I can do without knowing C. I just hope someone with the right skills does it at some point.
Then I just need to make some smaller merge requests, like one to add a udev rule for vibration support and so on.
Not much missing before I can finally use it as a daily driver.
view more: next ›
erebion
0 post score0 comment score
joined 1 year ago
Did you consider talking to the RFC's author? Maybe they are planning a new RFC that will update that, this could then be included.