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

Compare commits

base: erebion:5318c6cfec44ffa952a0b3570709feef18250020
Branches Tags
erebion:main
..
compare: erebion:271559a29bc57b6265da623784472c85f53ac4df
Branches Tags
erebion:main

2 commits
5318c6cfec ... 271559a29b

Author SHA1 Message Date
erebion
271559a29b link to some issues on Debian Salsa 2024-08-31 13:25:02 +02:00
erebion
fd99ffaff3 add info that some SIMs are not detected correctly 2024-08-31 13:10:33 +02:00
1 changed files with 8 additions and 0 deletions
Show stats Expand all files Collapse all files

8
README.md
View file

@ -54,6 +54,7 @@ Note:
- Have droid-juicer run on installer images - Have droid-juicer run on installer images
- Make sure my `q6voiced` package no longer includes a hard-coded config for this device - 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) - 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)
- https://salsa.debian.org/Mobian-team/devices/kernels/qcom-linux/-/issues/2
- Combine SDM670 kernel patches with those in the Mobian qcom kernel - 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 - Patches are already being upstreamed by the sdm670-linux project, maybe that's already done before I start working on it xD
@ -74,16 +75,23 @@ For those I will remove the workarounds once the changes are in the Mobian repo
#### Misc Issues #### Misc Issues
- some physical SIMs are not detected correctly, current theory is a race condition in ModemManager (needs further investigation)
- https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/889
- ALSA config for the device has not been upstreamed yet (can be added using the Playbook in this repo) - ALSA config for the device has not been upstreamed yet (can be added using the Playbook in this repo)
- Bug in Pipewire that causes issues with the camera: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4227 - Bug in Pipewire that causes issues with the camera: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4227
- Some people have issues connecting to 5 GHz wifi and/or dual 2.4 GHz/5 GHz wifi, while for others this works perfectly fine
- https://salsa.debian.org/Mobian-team/devices/kernels/qcom-linux/-/issues/6
- 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
(This is a non-exhaustive list) (This is a non-exhaustive list)
#### Low Priority #### Low Priority
- add udev rule for the vibration motor to the right package - add udev rule for the vibration motor to the right package
- https://salsa.debian.org/Mobian-team/devices/kernels/qcom-linux/-/issues/3
- fix udev rule for the Bluetooth workaround in this repo - fix udev rule for the Bluetooth workaround in this repo
- create/find script/tool that brings up Bluetooth & then package it - create/find script/tool that brings up Bluetooth & then package it
- https://salsa.debian.org/Mobian-team/devices/kernels/qcom-linux/-/issues/5
- 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 - 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 ### This Works