Sxmo/Pixel 3a
SXMO works on Pixel 3A.
Sound
It seems to work better with pulse at the moment.
To force the use of pulse, select sxmo-utils-audio-pulseaudio
as extra package in pmbootstrap.
With Pipewire, I get the same kind of problems I had with the op6 (for some things you need to have the mixer opened (placing calls) but for others (recorder) it blocks if mixer is opened.
Placing Calls
That is what a phone is for (no ?).
Current UCM profiles do not work (callaudio won't swich), so you'll have to use the ones that are worked on at this address [1] and place it in /usr/share/alsa/ucm2/Google/sargo/
.
For the moment, there are issues with the internal mic (it works using gnome-calls) ... started to talk about it in the UCM MR ...
Sensors
Proximity, light and accelerometer all work using iio-sensor-proxy
. Once running it can be queried using monitor-sensor
.
You can to do the same as with Oneplus6. Here is the sxmo_proximitylock.sh
script I currently use [2].
If you don't want monitor-sensor
to be run as root, you can use this polkit rule (it should be placed in /etc/polkit-1/rules.d/
) :
polkit.addRule(function(action, subject) { if (action.id == "net.hadess.SensorProxy.claim-sensor" && subject.isInGroup("plugdev")) { return polkit.Result.YES; } });
Working around the notch
Just kiddin', there is no notch on this phone !!!
But if you're upset by the rounded corners, you can always add some gaps on the status bar :
bar { gaps 0 20 0 20 height 20 ...
Issues
Most of them are minor, should be fixed quickly ;)
- GPS not working (not really optimistic about this one)
- Internal mic mute with sxmo dialer (works with gnome-calls)
- Headset headphones not working (but mic does)
- No deviceprofile yet
- HW buttons not working for navigating in the menus (I really should take care of the deviceprofile ;))