OS-issues issueshttps://source.puri.sm/Librem5/OS-issues/-/issues2022-07-08T18:20:04Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/245squeekboard opens on phosh overview when not needed2022-07-08T18:20:04ZMartin Kepplingersqueekboard opens on phosh overview when not neededSince squeekboard 1.15.0-1pureos1 it opens very briefly when opening the phosh overview. It's like a very short glitch - it opens and closes again - at least most of the time. It happened 2 or 3 times to me that it would not close anymor...Since squeekboard 1.15.0-1pureos1 it opens very briefly when opening the phosh overview. It's like a very short glitch - it opens and closes again - at least most of the time. It happened 2 or 3 times to me that it would not close anymore. I captured one here. I only opened the phosh overview:
![2022-01-03-212806](/uploads/4cb9960529942424cb9fc12dd398cc73/2022-01-03-212806.png)https://source.puri.sm/Librem5/OS-issues/-/issues/244Phonecalls sometimes fail due to modem not responding to AT commands, is some...2021-12-29T22:38:07ZElias RudbergPhonecalls sometimes fail due to modem not responding to AT commands, is some other process hijacking the AT port?This regards Librem 5 with PureOS Byzantium.
Making phonecalls works most of the time, but sometimes I cannot make a call. This is kind of reproducible but not every time, if I reboot e.g. 10 times and each time try to make a call, the ...This regards Librem 5 with PureOS Byzantium.
Making phonecalls works most of the time, but sometimes I cannot make a call. This is kind of reproducible but not every time, if I reboot e.g. 10 times and each time try to make a call, the problem usually happens at least once in those 10 attempts. When the problem appears, it seems like all following call attempts fail, and then any incoming calls also fail. A reboot is needed to make things work again.
Having added the ModemManager --debug option (`ExecStart=/usr/sbin/ModemManager --debug` in the `/lib/systemd/system/ModemManager.service` file) and compared logs for cases when making phonecalls work and not, now I think it looks like the problem is that the modem sometimes stops responding to AT commands.
For a successful case, part of the log related to [modem0/ttyUSB1/at] looks like this:
```
<debug> [1640639307.692391] [modem0/ttyUSB1/at] --> 'AT+CCWA=1<CR>'
<debug> [1640639307.703945] [modem0/ttyUSB1/at] <-- '<CR><LF>OK<CR><LF>'
<debug> [1640639307.704293] [modem0/ttyUSB1/at] device open count is 1 (close)
<debug> [1640639313.155180] [modem0/ttyUSB1/at] device open count is 2 (open)
<debug> [1640639313.155742] [modem0/ttyUSB1/at] --> 'AT+CCLK?<CR>'
<debug> [1640639313.168020] [modem0/ttyUSB1/at] <-- '<CR><LF>+CCLK: "21/12/27,21:08:32+04"<CR><LF><CR><LF>OK<CR><LF>'
<debug> [1640639313.168825] [modem0/ttyUSB1/at] device open count is 1 (close)
<debug> [1640639333.490220] [modem0/ttyUSB1/at] device open count is 2 (open)
<debug> [1640639333.490682] [modem0/ttyUSB1/at] device open count is 3 (open)
<debug> [1640639333.490880] [modem0/ttyUSB1/at] --> 'ATD90510;<CR>'
<debug> [1640639333.534638] [modem0/ttyUSB1/at] <-- '<CR><LF>OK<CR><LF>'
```
If I understand correctly, each "-->" line indicates an AT command sent to the modem, and each time there is a corresponding "<--" line that shows the response from the modem. That looks fine above, where each "-->" line is followed by a "<--" line.
Below is the corresponding part of the log for a case when I could not make phonecalls:
```
<debug> [1640636606.219473] [modem0/ttyUSB1/at] --> 'AT+CCWA=1<CR>'
<debug> [1640636606.230312] [modem0/ttyUSB1/at] <-- '<CR><LF>OK<CR><LF>'
<debug> [1640636606.230674] [modem0/ttyUSB1/at] device open count is 1 (close)
<debug> [1640636611.155941] [modem0/ttyUSB1/at] device open count is 2 (open)
<debug> [1640636611.156211] [modem0/ttyUSB1/at] --> 'AT+CCLK?<CR>'
<debug> [1640636614.159204] [modem0/ttyUSB1/at] device open count is 1 (close)
<debug> [1640636660.623905] [modem0/ttyUSB1/at] device open count is 2 (open)
<debug> [1640636660.624328] [modem0/ttyUSB1/at] device open count is 3 (open)
<debug> [1640636660.624529] [modem0/ttyUSB1/at] --> 'ATD90510;<CR>'
<debug> [1640636662.656478] [modem0/ttyUSB1/at] device open count is 4 (open)
```
In that case the modem responds to the "AT+CCWA" command, but for the "AT+CCLK" and the "ATD" commands there is no response from the modem.
There are also messages about timeouts, like this:
<debug> [1640636614.158768] [modem0] couldn't load network timezone: Serial command timed out
<warn> [1640636750.659447] [modem0/call0] couldn't start call: Serial command timed out
I asked about this on the ModemManager-devel mailing list and got the following reply from Aleksander Morgado there (see https://lists.freedesktop.org/archives/modemmanager-devel/2021-December/009049.html):
> There are 2 main explanations for that behavior:
> 1) some other process is trying to talk to the AT port, so "hijacking" the reading part from ModemManager.
> 2) the AT command handler inside the modem firmware, or some AT command processing got stuck in the modem firmware.
>
> When this happens, MM would count up to 10 consecutive AT timeouts, and when that happens it flags the modem as invalid, and it's reprobed. When reprobing, if the QMI port still works, MM will use exclusively that one. If the QMI also doesn't work, the modem will be unusable.
>
> I would try to ask whether case 1) is possible in the Librem5, and if it isn't, then you're facing a modem firmware issue very likely.
So now I would like to find out if it is case 1 above, that is, is some other process "hijacking" the AT port?
The port "ttyUSB1" seems related to a /sys/devices/ path according to the following:
<debug> [1640815008.566228] [base-manager] adding port ttyUSB1 at sysfs path: /sys/devices/platform/soc@0/38200000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.2/1-1.2:1.1/ttyUSB1/tty/ttyUSB1
Is there a way to log all access to that port, that could be used to detect if some other process is using it?
Other ideas about what to do here?https://source.puri.sm/Librem5/OS-issues/-/issues/242Attempt to select text in chatty leads to state where some touch events are i...2021-12-27T16:25:46ZElias RudbergAttempt to select text in chatty leads to state where some touch events are ignored, problem persists until next rebootI have noticed several times before that the phone gets into a state where the first touch event in each view gets ignored, but until now I have not had any way to reproduce it, it just seemed to happen randomly. Now I found a way to the...I have noticed several times before that the phone gets into a state where the first touch event in each view gets ignored, but until now I have not had any way to reproduce it, it just seemed to happen randomly. Now I found a way to the problem, as follows:
- open Chatty
- go inside a chat that has some previous messages
- drag inside the message text so that some part of the text is selected
- long-press on the selected text for a few seconds (which I was hoping would bring up a menu letting me copy the selected text)
- while still holding the long-press, drag it right a bit (then a shadow image of the selected text appears)
- release the long-press
- now the phone is in a state where the first touch in each view in Chatty gets ignored, so for example when tapping the back button that takes 2 attempts, and selecting another chat in the list takes 2 attempts, and so on.
It is easy to reproduce the problem in this way, I tried it several times and it behaves like this every time.
If someone can suggest ways to debug, like how to log information about touch events to see why some touches get ignored, that would be interesting to try.
Video:
![chatty25dec2](/uploads/e9e76f688e217885dd262a827931736a/chatty25dec2.mp4)
The problem persists after restarting Chatty, it only goes away after reboot.
Filing this issue in "OS-Issues" because I have a feeling the problem is not only in Chatty itself but something more general with how touch events are processed. Please move to Chatty if you think it belongs there.
This is on a Librem 5 running PureOS Byzantium.https://source.puri.sm/Librem5/OS-issues/-/issues/240Sort out do-not-disturb2021-12-20T10:46:23ZGuido GuntherSort out do-not-disturbWe need a good story regarding "do-not-disturb" and "feedback levels". While we have 3 feedback levels triggered by events:
- full (roughly mapping to haptic/led/sound)
- quiet (roughly mapping to haptic/led)
- silent (roughly mapping...We need a good story regarding "do-not-disturb" and "feedback levels". While we have 3 feedback levels triggered by events:
- full (roughly mapping to haptic/led/sound)
- quiet (roughly mapping to haptic/led)
- silent (roughly mapping to led only)
we don't have a do-not-disturb mode that e.g. affects
- whether notifications are shown as banners or on the lock screen
- whether notifications trigger feedback (see above)
- whether the phone lights up the screen on events
- the above feedback level
@francois.techene @tobias.bernard are there any (non-UI) designs regarding this yet? I think open questions are:
- is that a binary toggle?
- what exactly does it affect?
- where is this set in the UI? (see e.g. https://gitlab.gnome.org/World/Phosh/phosh/-/issues/8)
/cc @kop316 since it's related to https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/318https://source.puri.sm/Librem5/OS-issues/-/issues/238ModemManager connect fails due to multiple-connection-to-same-pdn-not-allowed2021-12-13T01:45:37ZElias RudbergModemManager connect fails due to multiple-connection-to-same-pdn-not-allowedMy L5 often gets into a state where ModemManager makes many failed connection attempts, it tries the same thing again and again and fails in the same way each time.
Example output from `sudo journalctl -u ModemManager`:
```
dec 12 15:2...My L5 often gets into a state where ModemManager makes many failed connection attempts, it tries the same thing again and again and fails in the same way each time.
Example output from `sudo journalctl -u ModemManager`:
```
dec 12 15:22:11 pureos ModemManager[578]: <info> [modem5] simple connect started...
dec 12 15:22:11 pureos ModemManager[578]: <info> [modem5] simple connect state (4/8): wait to get fully enabled
dec 12 15:22:11 pureos ModemManager[578]: <info> [modem5] simple connect state (5/8): register
dec 12 15:22:11 pureos ModemManager[578]: <info> [modem5] simple connect state (6/8): bearer
dec 12 15:22:11 pureos ModemManager[578]: <info> [modem5] simple connect state (7/8): connect
dec 12 15:22:11 pureos ModemManager[578]: <info> [modem5] state changed (registered -> connecting)
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer238] couldn't start network: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer238] call end reason (1): generic-unspecified
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer238] verbose call end reason (6,55): [3gpp] multiple-connection-to-same-pdn-not-allowed
dec 12 15:22:12 pureos ModemManager[578]: <warn> [modem5/bearer238] connection attempt #1 failed: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] state changed (connecting -> registered)
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer238] connection #1 finished: duration 0s, tx: 0 bytes, rx :0 bytes
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect started...
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (4/8): wait to get fully enabled
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (5/8): register
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (6/8): bearer
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (7/8): connect
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] state changed (registered -> connecting)
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer239] couldn't start network: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer239] call end reason (1): generic-unspecified
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer239] verbose call end reason (6,55): [3gpp] multiple-connection-to-same-pdn-not-allowed
dec 12 15:22:12 pureos ModemManager[578]: <warn> [modem5/bearer239] connection attempt #1 failed: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] state changed (connecting -> registered)
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer239] connection #1 finished: duration 0s, tx: 0 bytes, rx :0 bytes
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect started...
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (4/8): wait to get fully enabled
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (5/8): register
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (6/8): bearer
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (7/8): connect
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] state changed (registered -> connecting)
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer240] couldn't start network: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer240] call end reason (1): generic-unspecified
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer240] verbose call end reason (6,55): [3gpp] multiple-connection-to-same-pdn-not-allowed
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer240] couldn't start network: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer240] call end reason (1): generic-unspecified
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer240] verbose call end reason (6,55): [3gpp] multiple-connection-to-same-pdn-not-allowed
dec 12 15:22:12 pureos ModemManager[578]: <warn> [modem5/bearer240] connection attempt #1 failed: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] state changed (connecting -> registered)
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer240] connection #1 finished: duration 0s, tx: 0 bytes, rx :0 bytes
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect started...
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (4/8): wait to get fully enabled
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (5/8): register
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (6/8): bearer
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] simple connect state (7/8): connect
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] state changed (registered -> connecting)
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer241] couldn't start network: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer241] call end reason (1): generic-unspecified
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer241] verbose call end reason (6,55): [3gpp] multiple-connection-to-same-pdn-not-allowed
dec 12 15:22:12 pureos ModemManager[578]: <warn> [modem5/bearer241] connection attempt #1 failed: QMI protocol error (14): 'CallFailed'
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5] state changed (connecting -> registered)
dec 12 15:22:12 pureos ModemManager[578]: <info> [modem5/bearer241] connection #1 finished: duration 0s, tx: 0 bytes, rx :0 bytes
```
So, each time it says "verbose call end reason (6,55): [3gpp] multiple-connection-to-same-pdn-not-allowed".
It goes on with failed attempts like that for several hours, with hundreds of such failed connection attempts.
I suspect it is the mobile data connection that fails, because I can make voice calls in spite of those failed connection attempts.
What does this mean? How to troubleshoot this further?
The "multiple-connection-to-same-pdn-not-allowed" makes it sound as if there is some existing connection, could I check that somehow? If there is an existing connection, why is ModemManager trying (and failing) to make a new connection?https://source.puri.sm/Librem5/OS-issues/-/issues/237create and implement a policy for system suspend to RAM2023-11-15T19:31:19ZMartin Kepplingercreate and implement a policy for system suspend to RAMOur goal in the kernel is to support suspend to RAM and incoming (cellular) phone calls and SMS waking up the system. Exactly that. Currently we can't sensibly wake up the system based on any data packets.
But the above could be enough ...Our goal in the kernel is to support suspend to RAM and incoming (cellular) phone calls and SMS waking up the system. Exactly that. Currently we can't sensibly wake up the system based on any data packets.
But the above could be enough to not only let users manually suspend the system, but implement a policy that does not change UX (much) and saves power.
Something like suspend on "no internet connection", "no activity (whatever that means)" AND "display off for X seconds" is what comes to my mind.https://source.puri.sm/Librem5/OS-issues/-/issues/234during phone call the other side hears an echo of herself when the L5 side is...2021-12-07T08:34:41ZMartin Kepplingerduring phone call the other side hears an echo of herself when the L5 side is talking simultaniously (when "interrupting")you could argue the L5 highlight bad habits and enforces a conversation exercise to listen to your partner until she finishes, but noises can still happen by accident while the other party is talking :)
and exactly in this case, the oth...you could argue the L5 highlight bad habits and enforces a conversation exercise to listen to your partner until she finishes, but noises can still happen by accident while the other party is talking :)
and exactly in this case, the other party suddenly starts to hear an echo of herself. It ends again when the other party is talking alone again.
So that indicates that our echo cancellation works but shows hour tricky that can become. When the signal on the mic is not obviously similar to what is received, echo cancellation currently fails.https://source.puri.sm/Librem5/OS-issues/-/issues/233new message audio notification too loud during a phone call2021-12-07T08:28:00ZMartin Kepplingernew message audio notification too loud during a phone callwhen receiving a message in chatty while talking on the phone, the notification can be disturbingly loud for the ear.when receiving a message in chatty while talking on the phone, the notification can be disturbingly loud for the ear.https://source.puri.sm/Librem5/OS-issues/-/issues/232Swipe gesture not detected if started by tiny motion in other direction. Make...2021-11-29T10:49:05ZElias RudbergSwipe gesture not detected if started by tiny motion in other direction. Make swipe detection more robust?Looking at the swipe-up for the lockscreen as an example, but I think this is a general thing with how a swipe gesture is identified, it is not specific to the lockscreen and perhaps also not specific to phosh.
It easily happens that a ...Looking at the swipe-up for the lockscreen as an example, but I think this is a general thing with how a swipe gesture is identified, it is not specific to the lockscreen and perhaps also not specific to phosh.
It easily happens that a touch gesture that the user intended to be a swipe in a certain direction, like a swipe up to unlock the lockscreen, is ignore. Here is what it can look like:
![output2](/uploads/a747b29790ae40f17cf2457507325491/output2.mp4)
In that video each swipe is started with a small movement in a "wrong" direction, a direction that is not up, followed by a large motion upwards. I think what happens is that the software processing the touch events is looking at the direction of the swipe for the very first part of the motion and at that point decides the possible swipe direction. If the motion then changes direction, that is not treated as a swipe but is instead ignored.
Someone might argue that the user should learn to swipe properly, but I think this is an important accessibility issue: if you give a phone or tablet to a child, or an old person, or a person with slightly shaky hands due to whatever reason, then they will have trouble using the device because of this. For the user, it is very confusing that the device does not react when you as a user think you made a clear swipe.
Example: the finger first touches a point near the center of the screen. From there it moves down very slightly, perhaps as little as one or two pixels, and then it starts moving upwards a much longer distance. That should, I think, be interpreted as a swipe up even if the first few pixels of movement had another direction.
Another way of looking at it is to say that swipe detection should be robust to small disturbances; if there is a small random "noise" in the touch movement superimposed on a larger consistent movement, then the small noise should not destroy the touch gesture, the gesture should be detected anyway based on the larger movement that is very likely what the user intended.
I don't know where in the software stack this happens, but probably somewhere there is an algorithm that processes touch events to decide what gets interpreted as a swipe, then I think that algorithm would need tweaking to make it more robust.https://source.puri.sm/Librem5/OS-issues/-/issues/230Byzantium: Wifi needs HKS toggle off/on to come up2023-01-11T18:45:52ZMatthias ApitzByzantium: Wifi needs HKS toggle off/on to come upSince one of the last system updates my Wifi does not come up alone. No Wifi and no Bluetooth symbols are shown in this situation, also not after entering the PIN. I have only the HKS for cam and micro in off position, the others in on.
...Since one of the last system updates my Wifi does not come up alone. No Wifi and no Bluetooth symbols are shown in this situation, also not after entering the PIN. I have only the HKS for cam and micro in off position, the others in on.
After entering the SIM PIN this time I waited 5 minutes, then I toggled the HKS for Wifi/BT once. One minute later the L5 was connected to the AP. I have from this boot the `dmesg` and `/var/log/syslog` and will attach them also here.
The problem is not always reproducible.https://source.puri.sm/Librem5/OS-issues/-/issues/229squeekboard does not show in terminal Spanish chars2021-11-04T15:29:12ZMatthias Apitzsqueekboard does not show in terminal Spanish charsI added an additional Spanish language to the input methods and now the keyboard in the terminal does not have anymore this key labeled with áÁ (the 2nd key counted from the left in the lowest row of key) which serves to add a Spanish ti...I added an additional Spanish language to the input methods and now the keyboard in the terminal does not have anymore this key labeled with áÁ (the 2nd key counted from the left in the lowest row of key) which serves to add a Spanish tilded character. It is there when the keyboard works, for example, for the browser, but not for the terminal.
How one could get this key back again in the terminal?
![keyboard](/uploads/ec665ed0fc4358e5920149e679274043/keyboard.png)
Btw: In this Spanish keyboard at least the following chars are missing: `ñ Ñ ¿`https://source.puri.sm/Librem5/OS-issues/-/issues/228upowerd: did not recognise USB path [...], please report2021-11-02T08:55:35ZElias Rudbergupowerd: did not recognise USB path [...], please reportOn Librem 5 running PureOS byzantium, each time it boots there are the following messages:
```
purism@pureos:~$ sudo journalctl -b | grep "did not recognise"
Oct 31 16:19:02 pureos upowerd[739]: did not recognise USB path /sys/devices/p...On Librem 5 running PureOS byzantium, each time it boots there are the following messages:
```
purism@pureos:~$ sudo journalctl -b | grep "did not recognise"
Oct 31 16:19:02 pureos upowerd[739]: did not recognise USB path /sys/devices/platform/soc@0/30800000.bus/30a20000.i2c/i2c-0/0-003f/power_supply/tps6598x-source-psy-0-003f, please report
Oct 31 16:19:02 pureos upowerd[739]: did not recognise USB path /sys/devices/platform/soc@0/30800000.bus/30a50000.i2c/i2c-3/3-006a/power_supply/bq25890-charger, please report
```
It says "please report", so I am trying to report it by creating this issue. But I'm not sure where the report should go.
Apparently upowerd expects to recognise such pats and it does not recognise those two for the Librem 5. Is there a list somewhere, where those paths could be added so that upowerd could recognise them?https://source.puri.sm/Librem5/OS-issues/-/issues/227Need newer alsa-ucm-conf 1.2.5.12021-11-22T15:59:31ZGuido GuntherNeed newer alsa-ucm-conf 1.2.5.1Filing seprately to not clutter https://source.puri.sm/Librem5/librem5-base/-/merge_requests/277
@carsten.schoenert This is not super urgent, just in case you're bored: if you want to give backporting the 1.2.5.1-1 from Debian a try tha...Filing seprately to not clutter https://source.puri.sm/Librem5/librem5-base/-/merge_requests/277
@carsten.schoenert This is not super urgent, just in case you're bored: if you want to give backporting the 1.2.5.1-1 from Debian a try that would help a lot. I can test the resulting configuration before uploading.
On top we need https://github.com/alsa-project/alsa-ucm-conf/pull/102https://source.puri.sm/Librem5/OS-issues/-/issues/226Screen will not wake bug2022-06-13T15:27:29ZSteve StevensScreen will not wake bug# What problem did you encounter
The phone will not wake back up up. Screen stays black and the phone needs to be power cycled to get back in use. (hold the power button down for some time twice to shut it off and boot it back up). I've ...# What problem did you encounter
The phone will not wake back up up. Screen stays black and the phone needs to be power cycled to get back in use. (hold the power button down for some time twice to shut it off and boot it back up). I've waited hours to see if it would eventually come back on it's own, but it never does.
## What is the expected behaviour?
Phone will wake up (screen comes on and shows screensaver/lockscreen).
## How to reproduce
Steps to reproduce(follow EXACTLY this order):
1. Phone must have a sim card and have cell data turned on
2. Set the kill switches to the following:
* with Modem, and Wifi/Bluetooth hardware switched on.
* Mic/Camera hardware switch doesn't matter, though this has been tested most with it off.
3. Press the power button to turn off the phone’s screen.
4. Switch off the Wifi/bluetooth (hardware switch)
5. Switch off the Cell Modem (hardware switch, both the wifi/bluetooth and modem switches should be off now)
6. Wait 5 seconds
7. Press the power button again to try to turn the screen back on.
# What hardware are you running on?
Librem5 Evergreen Model
# Relevant OS information
Running Latest PureOS Byzantium
## Which kernel are you using?
Linux librem 5.13.0-1-librem5 #1 SMP PREEMPT Thu Oct 7 02:47:51 PDT 2021 aarch64 GNU/Linux
## Which OS are you using?
```
root@librem:/# cat /etc/os-release
ID=pureos
NAME=PureOS
PRETTY_NAME=PureOS
VERSION_ID=10.0
VERSION_CODENAME=byzantium
HOME_URL="https://pureos.net/"
SUPPORT_URL="https://puri.sm/faq/#faq-WherecanIfindoutmoreaboutPureOS"
BUG_REPORT_URL="https://tracker.pureos.net/"
LOGO=pureos-logo-icon
```
## Any other information that may be helpful?
Issue happens with 100% of my tests when following the above reproducer. It is not in any way itermittent.
Current Workarounds:
* Turn off modem switch before the wifi switch and this issue will not occur.
* Keep the screen on when turning off the wifi/bluetooth and modem
Forums post: https://forums.puri.sm/t/librem-5-wont-wake-bug/15014
This is particularly annoying as switching all of the switches off is a common use case for me, particularly wanting to switch the wifi off first.https://source.puri.sm/Librem5/OS-issues/-/issues/224Apps with missing icons in activity switcher2021-10-27T09:05:08ZSebastian KrzyszkowiakApps with missing icons in activity switcherBecause of how GTK3 handles app-ids, some applications have their icons in the activity switcher missing. Those that we forked should get fixed in the package, while for others it may not be a bad idea to have some compatibility mapping ...Because of how GTK3 handles app-ids, some applications have their icons in the activity switcher missing. Those that we forked should get fixed in the package, while for others it may not be a bad idea to have some compatibility mapping in phosh at some point (in addition to getting them fixed upstream).
Here's the list of packages where I noticed missing icons:
- [ ] gnome-2048
- [ ] gnome-authenticator
- [ ] cawbird
- [ ] gnome-disk-utility
- [ ] eog
- [ ] lightsoff
- [ ] iagno
- [ ] gnome-sound-recorder
- [ ] stream (lacks window title too)
- [ ] gedit
- [ ] tootle
- [ ] pinhole (lacks window title too)
- [ ] dconf-editor
- [ ] seahorse
- [ ] gnome-power-manager
- [ ] sysprofhttps://source.puri.sm/Librem5/OS-issues/-/issues/223Now debian package for redpine firmare2021-09-27T18:45:21ZGuido GuntherNow debian package for redpine firmareLooking at https://source.puri.sm/Librem5/linux-next/-/issues/290#note_150429 it seems there's no deb of the redpine firmware, we should have that for easy installation/deisntallation for testing (as with other firmwares).
/cc @angus.ai...Looking at https://source.puri.sm/Librem5/linux-next/-/issues/290#note_150429 it seems there's no deb of the redpine firmware, we should have that for easy installation/deisntallation for testing (as with other firmwares).
/cc @angus.ainsliehttps://source.puri.sm/Librem5/OS-issues/-/issues/218Add usb-gadget to initramfs2021-09-07T10:40:47ZGuido GuntherAdd usb-gadget to initramfsIt would be useful for unbreaking devices if one had the serial device from the usb-gadget in the initramfs already (not as useful as a serial console right in uboot but still very useful).
There's no systemd so just invoking the script...It would be useful for unbreaking devices if one had the serial device from the usb-gadget in the initramfs already (not as useful as a serial console right in uboot but still very useful).
There's no systemd so just invoking the script from https://source.puri.sm/Librem5/librem5-base/-/merge_requests/255 and adding the kernel modules needed should already do the trick.
/cc @dorota.czaplejewiczhttps://source.puri.sm/Librem5/OS-issues/-/issues/215amber-phone -> byzantium upgrade path2021-08-12T07:24:26ZGuido Guntheramber-phone -> byzantium upgrade pathWe don't have an issue tracking the manual upgrade path. Although reflashing is recommended due to encryption we might want to document the needed steps.
- [ ] documentation of the needed changes (`/apt/sources.list`, steps to perform)
...We don't have an issue tracking the manual upgrade path. Although reflashing is recommended due to encryption we might want to document the needed steps.
- [ ] documentation of the needed changes (`/apt/sources.list`, steps to perform)
- [ ] fix pending issueshttps://source.puri.sm/Librem5/OS-issues/-/issues/214Bring libadwaita to PureOS Byzantium2021-12-07T09:18:57ZGuido GuntherBring libadwaita to PureOS Byzantium@adrien.plazas since there's a nice post out what Purism does we should also ship it downstream https://puri.sm/posts/making-a-platform-adaptive-for-everyone/@adrien.plazas since there's a nice post out what Purism does we should also ship it downstream https://puri.sm/posts/making-a-platform-adaptive-for-everyone/https://source.puri.sm/Librem5/OS-issues/-/issues/213Bring gtk4 to PureOS Byzantium2021-06-12T11:36:03ZGuido GuntherBring gtk4 to PureOS ByzantiumAt least megapixels wants it and i expect more apps want to use that.
@adrien.plazas @alexander.mikhaylenko could you put that somewhere on your list? There's upstream Debian packaging to base this on.At least megapixels wants it and i expect more apps want to use that.
@adrien.plazas @alexander.mikhaylenko could you put that somewhere on your list? There's upstream Debian packaging to base this on.