Jump to content

Sxmo/Pixel 3a: Difference between revisions

From postmarketOS Wiki
No edit summary
No edit summary
Line 32: Line 32:
});
});
</pre>
</pre>
=== Camera ===
Megapixel has a configuration for pixel3a, but it does only take into account the front camera and the program closes when changing camera or taking photo.
Gnome snapshot works but doesn't find a camera. A complex pipeline involving libcamera/pipewire/gstreamer must be set-up. Waiting for more input on this ;)
For the moment it seems to go further by installing <code>xdg-desktop-portal-gnome</code> ... but then it fails saying it can't connect to pipewire (if pipewire is manually launched, then it complains that an object does not exist while calling "org.freedesktop.portal.Camera:OpenPipeWireRemote".
Note that there is no <code>pipewire-plugin-libcamera</code> package ... it seems to exist in other distributions


=== Working around the notch ===
=== Working around the notch ===
Line 45: Line 55:
     ...
     ...
</pre>
</pre>
=== Device profile ===
Default values seems ok for this phone. So you can leave an empty device profile in <code>/usr/bin/sxmo_deviceprofile_google,b4s4-sdm670.ini</code>


=== Issues ===
=== Issues ===

Revision as of 06:49, 18 October 2024

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;
  }
});

Camera

Megapixel has a configuration for pixel3a, but it does only take into account the front camera and the program closes when changing camera or taking photo.

Gnome snapshot works but doesn't find a camera. A complex pipeline involving libcamera/pipewire/gstreamer must be set-up. Waiting for more input on this ;)

For the moment it seems to go further by installing xdg-desktop-portal-gnome ... but then it fails saying it can't connect to pipewire (if pipewire is manually launched, then it complains that an object does not exist while calling "org.freedesktop.portal.Camera:OpenPipeWireRemote".

Note that there is no pipewire-plugin-libcamera package ... it seems to exist in other distributions

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
    ...

Device profile

Default values seems ok for this phone. So you can leave an empty device profile in /usr/bin/sxmo_deviceprofile_google,b4s4-sdm670.ini

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 ;))