erebion/sargo-temp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

update project status and cleanup docs

Browse source
This commit is contained in:
erebion 2024-08-23 01:04:11 +02:00
parent 48c612cc53
commit 0e028947ea
2 changed files with 22 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
IMAGE.md
View file

@ -25,15 +25,12 @@ DEB_HOST_ARCH=arm64 dpkg-buildpackage -a arm64 -us -uc -rfakeroot -b -Pcross,noc
## Building the Image
First `cd` to the Mobian repo.
Copy the kernel deb to `devices/qcom/packages`, so that it gets installed onta the image we are about to build.
Temporary workarounds:
- Comment `loupe` in `include/packages-phosh.yaml` as that is currently not available in the repo. The image viewer can be installed later.
- Comment `mobian-phosh` because of a broken dependency and insert `phosh-core`, the metapackage just installs things like an XMPP client and nothing important we couldn't install later.
- First `cd` to the Mobian repo
- Copy the kernel deb to `devices/qcom/packages`, so that it gets installed onta the image we are about to build.
- Add your SSH authorized keys file to `overlays/ssh/authorized_keys`, important so you can log in later
- Make sure the internet connection is stable, as the build fails if it cannot download all packages successfully.
Now build the image:
```bash
./build.sh -t qcom -s -u mobian | tee mobian-build.log # -s for SSH, which we need later
@ -41,15 +38,16 @@ Temporary workarounds:
(If you replace `mobian` with your own username, you will have to use that one for SSH later, of course)
Wait. It takes a while. Make sure the internet connection is stable, as the build fails if it cannot download all packages successfully.
Wait. It takes a while.
Note: Your SSH Host Keys currently get generated while building the image, please don't give your image to anyone else.
Note: Your SSH Host Keys seemingly get generated while building the image, please don't give your image to anyone else.
To Do: Verify whether those keys really end up in the image.
## Flash to device:
```
fastboot --set-active --slot a
fastboot flash boot_a mobian-qcom-phosh-20240614.boot-bonito-sdc.img
fastboot flash boot_a mobian-qcom-phosh-20240614.boot-sargo.img
fastboot flash userdata mobian-qcom-phosh-20240614.rootfs.img
fastboot erase dtbo
```
@ -58,4 +56,4 @@ Boot up the device. Connect it via USB.
## Temporary manual changes
Documented in README.md in this repo.
The steps are documented in `README.md` in this repo.

26
README.md
View file

@ -18,6 +18,8 @@ Connect via SSH: `ssh mobian@10.66.0.1`
Accept the host key.
Note: If you built the image with a different username, you will have to set that in `ansible/ansible.cfg`.
### Roll out workarounds using Ansible
You have to have `ansible-playbook` installed.
@ -40,7 +42,8 @@ Roll out audio workarounds: `./audio.sh`
- Make installer images work on this device
- Have droid-juicer run on installer images
- Make an ITP for tinyalsa and q6voiced and get that done (use the workarounds from this repo to get call audio working for now)
- Make sure my `q6voiced` package no longer includes a hard-coded config for this device
- Create an ITP for `tinyalsa` and `q6voiced` and get both into the repos (use the workarounds from this repo to get working call audio for now)
- Combine SDM670 kernel patches with those in the Mobian qcom kernel
- Patches are already being upstreamed by the sdm670-linux project, maybe that's already done before I start working on it xD
@ -48,7 +51,7 @@ Roll out audio workarounds: `./audio.sh`
- Remove hard-coded value in the `droid-juicer` systemd unit (needs someone who knows Rust, **help wanted**)
- https://gitlab.com/mobian1/droid-juicer/-/issues/4
- Combining SDM670 kernel patches with the Mobian qcom kernel (To Do List entry above)
- Combining SDM670 kernel patches with the Mobian qcom kernel (To Do List entry above, **help wanted**)
Done:
@ -69,8 +72,8 @@ For those I will remove the workarounds once the changes are in the Mobian repo
- add udev rule for the vibration motor to the right package
- fix udev rule for the Bluetooth workaround in this repo
- add script that brings up Bluetooth & then package it
- for now this repo contains a simple script specific to this device and a udev rule, but something is wrong with the udev rule. Run "/opt/bluetooth-mac.bash" to get Bluetooth working, repeat after reboots
- create/find script/tool that brings up Bluetooth & then package it
- for now this repo contains a simple script specific to this device and a udev rule, but something is wrong with the udev rule. Run `/opt/bluetooth-mac.bash` to get Bluetooth working, repeat after reboots
### This Works
@ -90,24 +93,19 @@ For those I will remove the workarounds once the changes are in the Mobian repo
- eSIM
- SMS (only receiving has been tested, but I don’t have reason to believe sending wouldn’t work)
- audio (ALSA config not packaged, but can be manually added using the playbook in this repo)
- full disk encryption (works, need to get some MRs merged and will document that soon)
- camera (both are still WIP, front camera buggy, back camera works but patches not in git yet)
- GPS (needs some improvements for better accuracy)
- full disk encryption (works, will document that soon)
- camera (patches not pushed to my device-specific kernel)
### This Has An Unknown Status
- Fingerprint Sensor
- NFC (no idea what software I could use for testing, but should work, does so on pmOS)
- GPS (needs some improvements for better accuracy)
- NFC (should work, does so on pmOS)
### This Does Not Work Yet (Soon™)
- USB host mode (no Kernel support yet, but apparently this is being worked on)
### 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
@ -119,7 +117,7 @@ For those I will remove the workarounds once the changes are in the Mobian repo
- My efforts of packaging a device-specific kernel: https://salsa.debian.org/erebion/sdm-670-linux (which can be used for now as patches are not yet in upstream Linux)
- `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
- `droid-juicer`, which retrieves some important files, such as firmware, from some partitions: https://gitlab.com/mobian1/droid-juicer
- postmarketOS wiki: https://wiki.postmarketos.org (lovely folks, thanks for sharing everything you found out the hard way :D)
### Thanks For All The Fish