Alistair authored 1 year ago and Sebastian Krzyszkowiak committed 1 year ago

ID_PATH doesn't correctly apply the quirks when using pmOS. Let's use
DEVPATH instead of ID_PATH to allow the udev quirks to work in pmOS as
well as PureOS.

Signed-off-by: Alistair Francis <alistair@alistair23.me>

Some systems power off after executing "halt". Users with a habit
of "halt" usage may end up surprised when the Librem 5 appears
completely off after using it, but actually is not - after halting,
the SoC remains on, consumes about 1W of power and does not respond
to any input (including low battery level!) until the power button
is held for ~5 seconds or power is cut.

There's little reason to ever halt a mobile phone without powering
it off, so don't let the users shoot themselves in their foot
(especially given that this can easily end up with battery's
undercharge protection circuit being involved) and force poweroff
whenever halt is invoked.

We need a recent enough kernel that keeps USB link active during
suspend and recent enough ModemManager that can handle incoming
messages arriving during suspend.

I did a simple test with a USB power meter to see the power draw over
5 minutes since running gnome-software in service mode using both
`powersave` and `simple_ondemand` governor with screen off.

With `powersave`, packagekitd was keeping one CPU busy at 100% for
slightly above 4 minutes. At the end of the 5 minutes period the power
meter reading was 125mWh.

With `simple_ondemand`, packagekitd was done after slightly above one
minute already, so the phone was idling rest of the time. Power meter
reading was 109mWh (it was at about 45mWh at the moment when packagekitd
finished its work).

I've also recorded two minutes of idling (nothing but kgx running):
the result was the same for both governors - 28mWh; and two minutes of
keeping all CPU cores busy with compressing random data: 61mWh for
`powersave` and 99mWh for `simple_ondemand`.

This is consistent with my anecdata - `simple_ondemand` appears to save
battery and makes the phone cooler. It also makes the UX much better when
using the phone over ssh. The one case where it makes things
worse - a rogue process constantly consuming 100% CPU in
the background - is already a pathological case with poor results on both
governors. When the process actually does some sensible and finite work,
it's going to finish it *much faster* with simple_ondemand, saving plenty
of power. Therefore, I'm going to merge this.

To go back to previous behavior, users can always use this udev rule:
```
SUBSYSTEM=="devfreq", TEST=="governor", ATTR{governor}="powersave"
```

Thus should work for the 7906G and the 7912G

Signed-off-by: Angus Ainslie <angus@akkea.ca>

Some deivces use the EM7565 modem instead on the BM818

Signed-off-by: Angus Ainslie <angus@akkea.ca>

Angus Ainslie authored 1 year ago and Sebastian Krzyszkowiak committed 1 year ago

Signed-off-by: Angus Ainslie <angus@akkea.ca>

The PMICs power button handling generates an event on long press which
confuses userspace as it already sees event from SVNS. Let's make
libinput ignore it.

This helps Phosh's power-button menu on long press as otherwise pressing
the button for too long will trigger the PMICs power button events
which will then blank/lock the device.

It's the defaults package that actually has requirements on
kernel version, so move the relation there.

Fixes #67

Guido Gunther authored 1 year ago and Sebastian Krzyszkowiak committed 1 year ago

It's where we collect the PureOS / Librem5 specific scripts.

Guido Gunther authored 1 year ago and Sebastian Krzyszkowiak committed 1 year ago

None is really needed so make it easy to remove them.

The new PM settings aren't compatible with kernels that don't
handle USB_PORT_QUIRK_NO_SUSPEND.

Set autosuspend delay to 500ms to improve battery life and disable
persist, since we don't gain anything from it as QMI state gets reset
with reenumeration.

PartOf= does not ensure ordering and ssh connections weren't
dropped before stopping this service. Before= does the thing.

Fixes #69

Some people reported that the new settings made the modem less
reliable on their phones. Since a better workaround is coming,
revert back to the old settings to not regress meanwhile.

Turns out that having the fragment size be larger than 22 ms
triggers a bug in Waydroid breaking it audio. Since this is
a balance between latency and possibility of underruns
occuring, let's reduce the recently bumped fragment size by
a tiny bit to make Waydroid happy, resulting in latency lowered
by 4 ms as a bonus.

Reencryption happens before resizing, so it only takes
about two minutes on the phone.

In order to use it, initial LUKS dump needs to be stored
on the rootfs:

    mkdir -p /var/lib/reencrypt
    LUKSDEV=$(cryptsetup status crypt_root | awk -F: '$1~/device/ {gsub(/^[ \t]+/, "", $2); print $2}')
    cryptsetup luksDump $LUKSDEV > /var/lib/reencrypt/dump

Citing Wikipedia [0]:

    Of these protocols [RNDIS, ECM, EEM and NCM] ECM could be classified
    the simplest - frames are simply sent and received without modification
    one at a time. This was a satisfactory strategy for USB 1.1 systems
    (current when the protocol was issued) with 64 byte packets but not for
    USB 2.0 systems which use 512 byte packets.

We're already using USB 3.0, so we should switch away from ECM.
Reasonable alternatives include EEM and NCM (RNDIS is a proprietary
Windows protocol, which - although supported by Linux - is considered
unsafe and may get removed [1]).

Bandwidth tests with iperf3 gave me these results:
 - ECM: 526 Mbits/sec
 - EEM: 761 Mbits/sec
 - NCM: 1.67 Gbits/sec

While NCM is newer, it's been supported in Linux since 2.6.37 already,
which is quite ancient by today's standards, so switching to it
should be safe for any kind of reasonably modern Linux host (plus we still
expose ACM serial that will be available even if NCM is not supported,
so basic communication with the device will still be possible).

It also has an added bonus of being supported in Windows 10 and
later, while ECM and EEM aren't supported there at all.

Therefore, switch the Ethernet gadget to use NCM.

[0] https://en.wikipedia.org/wiki/Ethernet_over_USB
[1] https://lore.kernel.org/lkml/20221123124620.1387499-1-gregkh@linuxfoundation.org/

This way it does not rely on the block device being named "sda".

This appears to reduce frequency of BM818's USB resets.

With 16ms the are occasional underruns happening when using
mpv with DRAM at 25MHz.

Signed-off-by: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>

No functional change; this only prevents user changes from being
overriden at each UCM profile switch.

Full ALSA state reset is already performed when updating from
the old incompatible profiles, so that's not a concern here.

hciattach isn't aware that the card gets reset at system suspend, requiring
full reinitialization, so it needs to be restarted. Unfortunately,
I haven't found a way to describe such relation using systemd unit
relations alone that wouldn't break things, so a system-sleep hook
is added to stop the service before going into suspend.

The service itself is also tweaked to better handle errors and to make
it restartable (previously it would require the card to be reset before
hciattach could work again).

Signed-off-by: Sebastian Krzyszkowiak <sebastian.krzyszkowiak@puri.sm>

Guido Gunther authored 2 years ago and Guido Gunther committed 2 years ago

squeekboard 1.20.0-2 from Debian will use update-alternatives to manage
the /u/s/a/sm.puri.OSK0.desktop finally allowing us to obsolete
osk-wayland here.

We do so by making sm.puri.OSK0-legacy.desktop use update-alternatives
too and giving it a lower priority than squeekboards.

As older squeekboard in PureOS Byzantium doesn't worry about
sm.puri.OSK0 at all so an update of librem5-base-defaults won't change
anything for the user.

We can drop sm.puri.OSK0-legacy and osk-wayland for Crimson

Guido Gunther authored 2 years ago and Guido Gunther committed 2 years ago

Don't rely on what a debhelper snippet does

Guido Gunther authored 2 years ago and Guido Gunther committed 2 years ago

Otherwise we won't have debhelper snippets inserted

Fixes 664324e4

Now that `sensors` outputs reasonable values as well we can safely have
people remove  it. gnome-usage has a separate Recommends: releationship
so it's can be dropped completely for crimson.