Librem5 issueshttps://source.puri.sm/groups/Librem5/-/issues2020-07-05T11:22:09Zhttps://source.puri.sm/Librem5/OS-issues/-/issues/124Headphone output defaults to barely audible2020-07-05T11:22:09ZBob HamHeadphone output defaults to barely audibleAs Kyle [noted](https://source.puri.sm/Librem5/OS-issues/issues/50#note_80765):
> currently the audio output of the headphones defaults to be barely audibleAs Kyle [noted](https://source.puri.sm/Librem5/OS-issues/issues/50#note_80765):
> currently the audio output of the headphones defaults to be barely audiblehttps://source.puri.sm/Librem5/debs/plymouth/-/issues/1Shutdown fade doesn't go all the way to black2020-01-29T10:27:29ZTobias BernardShutdown fade doesn't go all the way to blackWhen shutting down the screen fades and becomes darker, but then freezes at some point and maintains that same brightness value for a few seconds, and then suddenly going black.
I'd be nicer if this fade went all the way to black withou...When shutting down the screen fades and becomes darker, but then freezes at some point and maintains that same brightness value for a few seconds, and then suddenly going black.
I'd be nicer if this fade went all the way to black without stopping inbetween.
![shutdown-fade](/uploads/d8075bce5f14f70ee01be587d333c6a7/shutdown-fade.mp4)https://source.puri.sm/Librem5/gnome-control-center/-/issues/109Mobile panel navigation: Use back buttons in more places2020-02-26T11:43:40ZTobias BernardMobile panel navigation: Use back buttons in more placesInside the Mobile panel we have 5 sub-views, some of which use cancel/apply, others a back button.
- **Network Mode** has cancel/apply, but should have a back button instead
- **Network** has cancel/apply, but should have a back button ...Inside the Mobile panel we have 5 sub-views, some of which use cancel/apply, others a back button.
- **Network Mode** has cancel/apply, but should have a back button instead
- **Network** has cancel/apply, but should have a back button instead
- **APNs** has a back button, which is appropriate
- **SIM Lock** has cancel/apply, but should probably back button (but needs a more general overhaul so I'd keep it as is for now)
- **Modem Details** has a back button, which is appropriate
These are immediately actionable:
- [ ] **Network Mode**: change to a back button
- [ ] **Network**: change to a back buttonhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/55blessed-builds: report success although no artifacts are produced2020-02-26T17:00:16ZGuido Guntherblessed-builds: report success although no artifacts are produced@arno.bauernoppel one more thing i noticed with your current pipeline logic:
if a job does not produce any debs the pipeline is marked as succesfull although it stops, see:
http://localhost:8080/job/Builds/job/debs/job/deb-folks-amber-...@arno.bauernoppel one more thing i noticed with your current pipeline logic:
if a job does not produce any debs the pipeline is marked as succesfull although it stops, see:
http://localhost:8080/job/Builds/job/debs/job/deb-folks-amber-phone-staging-aarch64/
(folks sets export-dir so the debs end up somehwere else but the pipeline must never report success then).Arno BauernoppelArno Bauernoppelhttps://source.puri.sm/Librem5/OS-issues/-/issues/123Feature (for consideration), a global setting for 'delete/purge' after n days2020-01-28T08:10:36ZTodd WeaverFeature (for consideration), a global setting for 'delete/purge' after n daysSeeing call recent https://source.puri.sm/Librem5/calls/issues/28 get closed and verified, and seeing delete recent https://source.puri.sm/Librem5/calls/issues/98 appear as a desire, while also seeing browser history delete options. It m...Seeing call recent https://source.puri.sm/Librem5/calls/issues/28 get closed and verified, and seeing delete recent https://source.puri.sm/Librem5/calls/issues/98 appear as a desire, while also seeing browser history delete options. It may be a feature to consider (I would use it) to purge all usage after n days (I would set it to a week).
Things I could see desiring to clear (for those that don't want an ever growing permanent record on their device):
1. Recent Calls
2. Recent Browsing (History and Cookies)
3. Recent Chats
4. Recent Map Addresses
5. Recent Files Accessed
I could see a "Purge Data" option of [Never, Monthly, Weekly, Daily, Hourly, Immediate]
This should not impact stored bookmarks, pictures, music, nor files (to name a few).
Another thing to consider would be a persona/profile switch to a fully temporary phosh instance for the user where this setting is 'Immediate' for everything.https://source.puri.sm/Librem5/OS-issues/-/issues/122Librem 5 system: locale(s) not generated automatically2020-12-26T10:41:19ZNils SiebelLibrem 5 system: locale(s) not generated automatically
# What problem did you encounter
## What is the actual behaviour?
Selected language in the user interface (gnome-settings-*): en_GB.UTF-8
THEN in Terminal:
```
# perl --version
perl: warning: Setting locale failed.
perl: warning: Pl...
# What problem did you encounter
## What is the actual behaviour?
Selected language in the user interface (gnome-settings-*): en_GB.UTF-8
THEN in Terminal:
```
# perl --version
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_MONETARY = "en_GB.UTF-8",
LC_PAPER = "en_GB.UTF-8",
LC_MEASUREMENT = "en_GB.UTF-8",
LC_TIME = "en_GB.UTF-8",
LC_NUMERIC = "en_GB.UTF-8",
LANG = "en_GB.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
This is perl 5, version 28, subversion 1 (v5.28.1) built for aarch64-linux-gnu-thread-multi
(with 61 registered patches, see perl -V for more detail)
(...)
```
This can actually cause trouble for some background processes as the output of perl scripts aren't parsable.
## What is the expected behaviour?
Locales will be generated as needed so that programs like `perl` run without issue.
## How to reproduce
Please provide steps to reproduce the issue. If it's a graphical issue please
attach screenshots.
# What hardware are you running on?
- [ ] amd64 qemu image
- [ ] Librem5 devkit
- [X] other (please elaborate)
Librem 5 Birch
# Relevant OS information
## Which kernel are you using?
Please paste the output of ``uname -a`` below.
`Linux pureos 5.3.0-librem5-h1 #1 SMP PREEMPT Tue Jan 7 10:16:00 CET 2020 aarch64 GNU/Linux`
## Which OS are you using?
Please paste the output of ``cat /etc/os-release`` below.
```
ID=pureos
NAME=PureOS
PRETTY_NAME=PureOS
VERSION_ID=9.0
VERSION_CODENAME=amber
HOME_URL="https://pureos.net/"
SUPPORT_URL="https://puri.sm/faq/#faq-WherecanIfindoutmoreaboutPureOS"
BUG_REPORT_URL="https://tracker.pureos.net/"
LOGO=pureos-logo-icon
```
https://source.puri.sm/Librem5/gnome-control-center/-/issues/108Date setting month flows off top of page2020-01-26T14:06:43ZTodd WeaverDate setting month flows off top of pageReproduction (yes, this user-flow did occur for me)
1. Settings
2. Details
3. Date & Time
4. Turn off Automatic Date & Time
5. edit Date & Time
6. Click Month, select 'December' (this flips the drop down to render to top on next click)
7...Reproduction (yes, this user-flow did occur for me)
1. Settings
2. Details
3. Date & Time
4. Turn off Automatic Date & Time
5. edit Date & Time
6. Click Month, select 'December' (this flips the drop down to render to top on next click)
7. Click Month
8. Witness overflow off the top
![2061-12-27-1840](/uploads/a1ccb061cc68c74f51d8bb2ec67ca5d7/2061-12-27-1840.png)
```
purism@librem-5-birch:~$ uname -a
Linux librem-5-birch 5.3.0-librem5-h1 #1 SMP PREEMPT Sat Jan 25 09:55:23 CET 2020 aarch64 GNU/Linux
purism@librem-5-birch:~$ dpkg -s phosh | grep Version
Version: 0.1.7
purism@librem-5-birch:~$ dpkg -s phoc | grep Version
Version: 0.1.5pureos1
purism@librem-5-birch:~$ dpkg -s gnome-control-center | grep Version
Version: 1:3.34.0.1+19975+gitf7dfd564f-1pureos0
purism@librem-5-birch:~$ uptime
06:06:15 up 13:17, 2 users, load average: 0.39, 0.47, 0.35
purism@librem-5-birch:~$ date
Sun 26 Jan 2020 06:06:20 AM PST
purism@librem-5-birch:~$
```https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/19Timer should repeat (like alarm) or be loud and longer2020-01-26T13:51:44ZTodd WeaverTimer should repeat (like alarm) or be loud and longerThe timer 'ding' is very quiet and very short
Reproduction
1. Clocks - Timer
2. Set to 1 second
3. Start
4. Hear tiny ding through earpiece
(now imagine your cookies burning from the other room because you missed this sound)
I could s...The timer 'ding' is very quiet and very short
Reproduction
1. Clocks - Timer
2. Set to 1 second
3. Start
4. Hear tiny ding through earpiece
(now imagine your cookies burning from the other room because you missed this sound)
I could see this either being like the alarm (continuous), or being much louder (through speaker) and much longer (at least 15 seconds). This probably needs @design to chime in :)
```
purism@librem-5-birch:~$ uname -a
Linux librem-5-birch 5.3.0-librem5-h1 #1 SMP PREEMPT Sat Jan 25 09:55:23 CET 2020 aarch64 GNU/Linux
purism@librem-5-birch:~$ dpkg -s phosh | grep Version
Version: 0.1.7
purism@librem-5-birch:~$ dpkg -s phoc | grep Version
Version: 0.1.5pureos1
purism@librem-5-birch:~$ dpkg -s gnome-clocks | grep Version
Version: 3.32.0+1911+git9afed36-1pureos0
purism@librem-5-birch:~$
```https://source.puri.sm/Librem5/debs/gnome-clocks/-/issues/18Alarm sound extremely quiet2020-02-19T17:29:00ZTodd WeaverAlarm sound extremely quietThe alarm plays quietly through the earpiece, and should be louder through the speaker.
Reproduction:
1. Clocks - Alarm
2. '+' create new alarm; for 1 minute from now
3. Wait
4. Hear alarm quietly playing through earpiece
```
purism@li...The alarm plays quietly through the earpiece, and should be louder through the speaker.
Reproduction:
1. Clocks - Alarm
2. '+' create new alarm; for 1 minute from now
3. Wait
4. Hear alarm quietly playing through earpiece
```
purism@librem-5-birch:~$ uname -a
Linux librem-5-birch 5.3.0-librem5-h1 #1 SMP PREEMPT Sat Jan 25 09:55:23 CET 2020 aarch64 GNU/Linux
purism@librem-5-birch:~$ dpkg -s phosh | grep Version
Version: 0.1.7
purism@librem-5-birch:~$ dpkg -s phoc | grep Version
Version: 0.1.5pureos1
purism@librem-5-birch:~$ dpkg -s gnome-clocks | grep Version
Version: 3.32.0+1911+git9afed36-1pureos0
purism@librem-5-birch:~$
```https://source.puri.sm/Librem5/debs/mesa/-/issues/4don't require ETNA_MESA_DEBUG=no_supertile for running phoc2021-08-05T09:17:30ZGuido Guntherdon't require ETNA_MESA_DEBUG=no_supertile for running phocneed to investigate why this is required and fix itneed to investigate why this is required and fix ithttps://source.puri.sm/Librem5/linux/-/issues/153OTG_CONFIG=1 When It Shouldn't Be2021-09-14T11:33:11ZEric KuzmenkoOTG_CONFIG=1 When It Shouldn't BeThe BQ25895's OTG_CONFIG bit is not being set to 1 on the basis of the TPS65982's VconnEnabled, DataRole, PortRole, ConnState, and PlugPresent bits. It seems to always be set to 1, which means if the OTG pin is set to 1 then we will wast...The BQ25895's OTG_CONFIG bit is not being set to 1 on the basis of the TPS65982's VconnEnabled, DataRole, PortRole, ConnState, and PlugPresent bits. It seems to always be set to 1, which means if the OTG pin is set to 1 then we will waste energy (less battery life).
From what I tested, we can use the TPS65982's 0x1A status register to determine when the BQ25895's boost mode should be enabled (when OTG_CONFIG=1 and/or when the OTG pin is set HIGH). The least significant byte in the status register tells us if the phone needs to supply VBUS and has negotiated to be a PD source:
![image](/uploads/db22a54667c45510948165cbc106bb6d/image.png)
Here is what you would get if the phone is a PD sink, connected to a host that is supplying VBUS:
```
purism@pureos:~$ sudo i2ctransfer -f -y 0 w1@0x3f 0x1a r5
0x04 0x0d 0x0c 0x94 0x01
```
0x0d here tells us VconnEnabled=0, DataRole=0, PortRole=0, ConnState=110, and PlugPresent=1. This allows us to know that we are connected to a USB PD source and do not need to put the BQ25895 into its OTG boost mode.
Here is what you would get if the phone is a PD source, connected to a device that needs VBUS to be supplied to it:
```
purism@pureos:~$ sudo i2ctransfer -f -y 0 w1@0x3f 0x1a r5
0x04 0x7d 0x00 0x14 0x01
```
In this case, 0x7d tell us connEnabled=1, DataRole=1, PortRole=1, ConnState=110, and PlugPresent=1. This allows us to know that we are connected to a USB PD _sink_. However, 0x00 shows us that PP_5V0 switch is disabled because the BQ25895 is not in its boost mode. When we find that we're connected to a USB PD sink we can put the BQ25895 into its OTG mode to supply VBUS, this is how that could happen:
```
purism@pureos:~$ sudo i2ctransfer -f -y 0 w1@0x3f 0x1a r5
0x04 0x7d 0x00 0x14 0x01
purism@pureos:~$ echo 255 | sudo tee /sys/class/leds/chg_otg_en/brightness
255
purism@pureos:~$ sudo i2ctransfer -f -y 0 w1@0x3f 0x1a r5
0x04 0x7d 0x02 0x14 0x01
```
As you can see, the 0x00 become 0x02, showing us that PP_5V0 is enabled and the phone is supplying 5V to VBUS (as was shown by my USB-C meter dongle thing during my test). We could use OTG_CONFIG instead of the OTG GPIO to accomplish the same thing, but we need to make sure we leave OTG_CONFIG=0 in all other conditions.
When nothing is connected to the USB-C port it is quite obvious that nothing is there and we should not put the BQ25895 into its boost mode. We can determine this simply by seeing if the least significant bit (PlugPresent) of the TPS65982's 0x1A register is 0 or 1.
Here's what I get when nothing is inserted:
```
purism@pureos:~$ sudo i2ctransfer -f -y 0 w1@0x3f 0x1a r5
0x04 0x60 0x00 0x14 0x01
```
I've also gotten this:
```
purism@pureos:~$ sudo i2ctransfer -f -y 0 w1@0x3f 0x1a r5
0x04 0x40 0x00 0x14 0x01
```
Which shows that the DataRole and PortRole bits are meaningless when there is nothing inserted, but the PlugPresent bit tells us whether or not something is actually connected.https://source.puri.sm/Librem5/linux/-/issues/152Turn lcd into an multi function device2023-10-03T16:17:47ZGuido GuntherTurn lcd into an multi function deviceTouch and lcd-panel probe/shutdown/suspend/resume need to be coordinated since they depend on the same regulators and reset lines. This is possible with a mfd driver for which i have a PoC.Touch and lcd-panel probe/shutdown/suspend/resume need to be coordinated since they depend on the same regulators and reset lines. This is possible with a mfd driver for which i have a PoC.https://source.puri.sm/Librem5/deb-build-jobs/-/issues/54blessed-builds: don't try to upload failed builds2021-11-11T09:16:38ZGuido Guntherblessed-builds: don't try to upload failed buildssee e.g. http://localhost:8080/job/Builds/job/debs/job/deb-mozjs60-amber-phone-staging-aarch64/2/console
when a build fails like
```
I: unmounting dev/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: Cleanin...see e.g. http://localhost:8080/job/Builds/job/debs/job/deb-mozjs60-amber-phone-staging-aarch64/2/console
when a build fails like
```
I: unmounting dev/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: Cleaning COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.15260
gbp:error: 'git-pbuilder --jobs=auto -nc --build=full -sa' failed: it exited with 1
[Pipeline] echo
Script returned 1. Aborting build.
```
but then the upload step tries to pick up the pieces:
```
Running on Jenkins in /var/lib/jenkins/workspace/Builds/debs/deb-mozjs60-amber-phone-staging-aarch64@2
[Pipeline] {
[Pipeline] sh
...
+ + echo ./*.changes
wc -w
+ [ 1 -ne 1 ]
+ ls ./*.changes
ls: cannot access './*.changes': No such file or directory
+ changes_file=
[Pipeline] echo
Script returned 2. Aborting build.
```
and only this makes the pipeline stop. The pipeline should have stopped after the first build failure.https://source.puri.sm/Librem5/OS-issues/-/issues/121OSK for SIM PIN should only offer number entry2022-01-21T08:05:45ZBob HamOSK for SIM PIN should only offer number entryWhen the SIM needs to be unlocked I get presented with a dialog box with an entry for the PIN, along with a QWERTY OSK. The OSK should be a number-only keyboard.
I'm not sure which component displays the SIM PIN entry. Regardless, ass...When the SIM needs to be unlocked I get presented with a dialog box with an entry for the PIN, along with a QWERTY OSK. The OSK should be a number-only keyboard.
I'm not sure which component displays the SIM PIN entry. Regardless, assuming it's a GtkEntry, calling [`gtk_entry_set_input_purpose`](https://developer.gnome.org/gtk3/stable/GtkEntry.html#gtk-entry-set-input-purpose) with `GTK_INPUT_PURPOSE_DIGITS` should make the OSK number-only.
/cc @mohammed.sadiq @dorota.czaplejewicz @guido.gunther @sebastian.krzyszkowiakhttps://source.puri.sm/Librem5/uboot-imx/-/issues/18remove 2 seconds boot delay2021-02-17T19:10:52ZMartin Kepplingerremove 2 seconds boot delayI guess keeping a button pressed on the console during boot would reliably drop to the u-boot console when we don't wait the 2 seconds we do now. And speeding up startup by 2 seconds is a lot!I guess keeping a button pressed on the console during boot would reliably drop to the u-boot console when we don't wait the 2 seconds we do now. And speeding up startup by 2 seconds is a lot!https://source.puri.sm/Librem5/l5-schematic/-/issues/2Make x-rays from documentation available on gitlabCE instance schematics folder2020-01-24T00:38:49Z. ¦3<RELATIVISMMake x-rays from documentation available on gitlabCE instance schematics folderschematics are available on documentation: https://developer.puri.sm/Librem5/Hardware_Reference/Birch.html. But are not available next to the schematics on this gitlab instance. So Im requesting for those images to be uploaded here as we...schematics are available on documentation: https://developer.puri.sm/Librem5/Hardware_Reference/Birch.html. But are not available next to the schematics on this gitlab instance. So Im requesting for those images to be uploaded here as well, on : https://source.puri.sm/Librem5/l5-schematic. Cheers, Alexishttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/53blessed-builds: switch build machine to virtio2020-02-07T19:14:41ZGuido Guntherblessed-builds: switch build machine to virtio(filing it here since we don't have a dedicated visible repo for hw stuff):
The vm uses scsi emulation instead of virtio which is way more cpu intensive on I/O. We should switch to virtio.(filing it here since we don't have a dedicated visible repo for hw stuff):
The vm uses scsi emulation instead of virtio which is way more cpu intensive on I/O. We should switch to virtio.https://source.puri.sm/Librem5/deb-build-jobs/-/issues/52blessed-builds: autopkgtests rebuild the source tree2020-12-07T09:23:37ZGuido Guntherblessed-builds: autopkgtests rebuild the source treethis is usually not necessary when you pass the `.changes` file to autopkgtst (and copy the other build artifacts into the container too) . This saves lots of time when performing the test step and also makes sure you test the just built...this is usually not necessary when you pass the `.changes` file to autopkgtst (and copy the other build artifacts into the container too) . This saves lots of time when performing the test step and also makes sure you test the just built binaries.https://source.puri.sm/Librem5/deb-build-jobs/-/issues/51blessed-builds: 'test package' step should be more clever when no tests are ...2020-12-07T09:23:31ZGuido Guntherblessed-builds: 'test package' step should be more clever when no tests are presentThe current machinery fires of even if the package does not contain any autopktests, in this case i'd be better to skip all the work since most of the time is spent installing dependencies.The current machinery fires of even if the package does not contain any autopktests, in this case i'd be better to skip all the work since most of the time is spent installing dependencies.Arno BauernoppelArno Bauernoppelhttps://source.puri.sm/Librem5/deb-build-jobs/-/issues/50blessed-builds: tests not being run on succesuful uploads2020-12-14T10:45:30ZGuido Guntherblessed-builds: tests not being run on succesuful uploadsNote that for all builds passing the 'Upload Debian Packages' stage with success (instead of unstable) the test stage is then not being run, this is due to
https://source.puri.sm/Librem5/deb-build-jobs/blob/master/blessed_build_auto.gro...Note that for all builds passing the 'Upload Debian Packages' stage with success (instead of unstable) the test stage is then not being run, this is due to
https://source.puri.sm/Librem5/deb-build-jobs/blob/master/blessed_build_auto.groovy#L252
checking for `.SUCCESS` but that is not set in the 'Upload Debian Packages' stage (and no other stage before that afaik.
/cc @arno.bauernoppelArno BauernoppelArno Bauernoppel