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.
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
dmesgwill just tell you what files it cannot load because they are missing. Just find those, write the config, rundroid-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
I know C and I have a pixel 3a. I could probably help out with the kernel patches if you want. I’m not totally clear what work needs to be done. You just need someone to help get those patches merged against the mobian upstream kernel?
Cool! Well, it’s just a merge conflict. I don’t knoe how to combine the patches. Should be pretty easy for someone that does not need to google for every line of C.
I can give you notes* later on what to do to get to the conflict, then maybe you can resolve it and push the result to some repo? :)
*Just 3 or 4 commands, I think, including the Debian gbp command
Yeah sure. I’ll pull it all down and reproduce and try to get the conflicts sorted out and push the repo up somewhere. I’ve never built a Debian kernel before but I’m sure I can figure it out!
deleted by creator
deleted by creator