developer.puri.sm issueshttps://source.puri.sm/Librem5/developer.puri.sm/-/issues2020-02-04T14:24:19Zhttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/126Add a diagnostic app to show and change the state of peripherals, switches, b...2020-02-04T14:24:19ZDavid BoddieAdd a diagnostic app to show and change the state of peripherals, switches, buttonsIt would be useful to have an app to allow basic testing of hardware functionality. This would allow a tester to quickly check the following pieces of hardware on a single screen:
* touchscreen (both display and input)
* volume buttons
*...It would be useful to have an app to allow basic testing of hardware functionality. This would allow a tester to quickly check the following pieces of hardware on a single screen:
* touchscreen (both display and input)
* volume buttons
* kill switches
* sound output (speaker and headphones)
* sound input (microphone)
* proximity and ambient light sensor
* Inertial Measurement Unit (IMU - gyro, accelerometer, magnetometer)
This might have to be running outside a flatpak sandbox to be able to access some of these resources.
A separate app could provide information about more complex peripherals:
* Global Navigation Satellite System (GNSS - GPS, etc.)
* modem and SIM card
* smart card
* camera
* wireless networking
* Bluetooth
* USBhttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/51Devkit board setup instructions2019-10-03T12:44:31ZHeather EllsworthDevkit board setup instructionsFor the users receiving a dev kit, they will want some guide to follow to set up the board from unboxing to ready for app development.
Items to describe:
- [x] serial console shell
- [x] SSH connection
- [x] [using the display](https:/...For the users receiving a dev kit, they will want some guide to follow to set up the board from unboxing to ready for app development.
Items to describe:
- [x] serial console shell
- [x] SSH connection
- [x] [using the display](https://source.puri.sm/Librem5/developer.puri.sm/merge_requests/189)
- [ ] cross-compilation
- [ ] application development
- [ ] using the device as a desktopDavid BoddieDavid Boddiehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/97Expand on display cable fix2019-07-06T17:12:23ZGuido GuntherExpand on display cable fixhttps://developer.puri.sm/Librem5/Development_Environment/Boards/Troubleshooting/LCD_Problems.html?highlight=cable#procedure already helps a lot but a recent case showed:
- [ ] a real picture of the misplaced and seated cable
- [ ] a re...https://developer.puri.sm/Librem5/Development_Environment/Boards/Troubleshooting/LCD_Problems.html?highlight=cable#procedure already helps a lot but a recent case showed:
- [ ] a real picture of the misplaced and seated cable
- [ ] a real picture showing where the connector is placed
- [ ] instructions how to reseat the cable
(basically you filp up the lever (e.g. using a tweezer) tilt the display and flip down the lever again.) This could also include a picture with the lever opened.
would help people to fix this on their own.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/73Map devices, access to resources to flatpak permissions and portals2019-04-01T14:51:43ZDavid BoddieMap devices, access to resources to flatpak permissions and portalsA table, for example, mapping a device like the camera to the lines required the manifest, would be useful.A table, for example, mapping a device like the camera to the lines required the manifest, would be useful.David BoddieDavid Boddiehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/81Document Plasma Mobile installation2019-03-08T22:09:21ZDavid BoddieDocument Plasma Mobile installationFrom [Matrix chat](https://matrix.to/#/!DuiySnjJDbuIaRRkhz:talk.puri.sm/$15510151131487jpZtp:kde.org):
1) Flash pureos
2) apt install gnupg2
3) apt-key adv --keyserver keyserver.ubuntu.com --recv-keys CF319275556E40EC
4) Add deb https:/...From [Matrix chat](https://matrix.to/#/!DuiySnjJDbuIaRRkhz:talk.puri.sm/$15510151131487jpZtp:kde.org):
1) Flash pureos
2) apt install gnupg2
3) apt-key adv --keyserver keyserver.ubuntu.com --recv-keys CF319275556E40EC
4) Add deb https://repo.kaidan.im/debpm/ buster main devkit debline in /etc/apt/sources.list
5) apt update
6) Disable phosh.service
7) Install kwin-wayland kwin-wayland-backend-drm plasma-phone-components plasma-settings plasma-phone-settings simplelogin (I also removed gnome packages to make space as I haven't figured out how to increase size of rootfs)
8) Add export ETNA_MESA_DEBUG=no_supertile to /etc/profile.d/etnaviv.sh
9) systemctl enable simplelogin and reboot
10) modify /lib/systemd/system/simplelogin.service to use purism user instead of phablet
Make sure kwin packages are from devkit component ^^ if they're from the debian/pureos it won't work.David BoddieDavid Boddiehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/75devkit: Need information on connecting Ethernet2019-02-21T16:01:22ZDorota Czaplejewiczdevkit: Need information on connecting EthernetCurretly, the only info is about the stock image. There should be some clear indication that this is not how to connect to the current images.Curretly, the only info is about the stock image. There should be some clear indication that this is not how to connect to the current images.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/67Add instructions for compiling devkit kernel2019-02-12T22:13:45ZBob HamAdd instructions for compiling devkit kernelFrom Matrix:
```
mdz0: I just compiled a kernel package using https://source.puri.sm/Librem5/linux-emcraft by adjusting the instructions here https://source.puri.sm/Librem5/image-builder/blob/master/build/kernel.txt
08:49
sudo apt-get i...From Matrix:
```
mdz0: I just compiled a kernel package using https://source.puri.sm/Librem5/linux-emcraft by adjusting the instructions here https://source.puri.sm/Librem5/image-builder/blob/master/build/kernel.txt
08:49
sudo apt-get install gcc-aarch64-linux-gnu build-essential crossbuild-essential-arm64
cp arch/arm64/configs/librem5-evk_defconfig .config
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- menuconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- deb-pkg
```David BoddieDavid Boddiehttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/68Add LED description2018-12-31T17:10:18ZDorota CzaplejewiczAdd LED descriptionThe programmable LED needs to be descibed in the docs:
It can be controlled with:
```
root@pureos:/# echo 200 > /sys/class/leds/LED\ 1/brightness
```
where 0 is "off", and any value between 1 and 255 is "on" with the default device tr...The programmable LED needs to be descibed in the docs:
It can be controlled with:
```
root@pureos:/# echo 200 > /sys/class/leds/LED\ 1/brightness
```
where 0 is "off", and any value between 1 and 255 is "on" with the default device tree. The LED is driven by a PWM shared with the haptic motor, so only one can be gradual at a time, decided by device tree.
* * *
Eric about the 3 charge controller LEDs without a battery plugged in:
> the two LEDs that were on are one that is on VBAT_REG (meaning VBAT_REG is likely being properly regulated), and PG# (Power Good). The third LED is attached to the charge controller's STAT pin, which would indicate whether or not a battery is being charged (can blink @ ~11Hz or be off if no battery is present, basically meaningless without a battery)
> if you are powering from a battery but are _not_ supplying VBUS, then you will just see the VBAT_REG LED on, the PG# and STAT ones will be off (unless you _are_ supplying VBUS)
VBUS is USB.
> for the LEDs, best thing to do is look at the schematic and charge controller's datasheet to know what it actually meanshttps://source.puri.sm/Librem5/developer.puri.sm/-/issues/17Need general introduction to the dev kit and phone2018-12-29T22:59:02ZBob HamNeed general introduction to the dev kit and phoneFor the phone, something along the lines of:
"The Librem 5 is an i.MX8 phone running PureOS, a Debian derivative. The kernel is [based on NXP's sources? latest mainline with patches? not sure]. For the graphical windowing system, it ...For the phone, something along the lines of:
"The Librem 5 is an i.MX8 phone running PureOS, a Debian derivative. The kernel is [based on NXP's sources? latest mainline with patches? not sure]. For the graphical windowing system, it makes use of Rootston, a Wayland compositor, together with a bespoke shell named phosh. The graphical environment is based on the GNOME platform with a variety of modifications. The telephony stack consists of [oFono/ModemManager/etc.]. ... "
And something similar will be needed for the dev kit.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/65Introduction points to almost empty page "Hardware Reference"2018-12-23T10:44:01ZGuido GuntherIntroduction points to almost empty page "Hardware Reference"We know the hardware of the Devkit so the first link [Hardware Reference](https://developer.puri.sm/Librem5/Hardware_Reference.html) on
https://developer.puri.sm/Librem5/Introduction.html
Should point to an appropriate page. This also ...We know the hardware of the Devkit so the first link [Hardware Reference](https://developer.puri.sm/Librem5/Hardware_Reference.html) on
https://developer.puri.sm/Librem5/Introduction.html
Should point to an appropriate page. This also relates to #18.
Having things like RAM, CPU Module, modem, wifi would be start we could then fill in more details via MRs. The page should provide two separate sections for the devkit and the phone.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/14Docs should be updated on commit2018-12-22T22:25:46ZGuido GuntherDocs should be updated on commitUpdating the docs is currently a manual task (AFAIK). It'd be great to publish them right after the Jenkins build.Updating the docs is currently a manual task (AFAIK). It'd be great to publish them right after the Jenkins build.https://source.puri.sm/Librem5/developer.puri.sm/-/issues/63Unify devkit and imx8 page2018-12-21T11:34:36ZGuido GuntherUnify devkit and imx8 pageThere's
https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html
https://developer.puri.sm/Librem5/Development_Environment/Boards/Dev-kit.html
while both refer to the devkit.There's
https://developer.puri.sm/Librem5/Development_Environment/Boards/imx8.html
https://developer.puri.sm/Librem5/Development_Environment/Boards/Dev-kit.html
while both refer to the devkit.David BoddieDavid Boddie