I have a Librem 5 that I bought off of eBay. I have the most recent updates installed, and I had a question about the Camera app. I know it has “(dev preview)” in the title, so I’m assuming it is not in its final form, but all of the sliders appear to change settings except for the “focus” slider. Does this match other people’s experience with the Camera app in its current form?
No, this should be working. Do you have Amber or Byzantium on the phone?
I am 99% sure it is Byzantium. Running “uname -a” tells me the kernel is “5.15.0-1-librem5”. Also it has disk encryption that I have to unlock at bootup, which I believe was introduced in Byzantium.
Then I would update the system first, and then provide the logs from Millipixels.
When I run “sudo apt update,” it tells me that all packages are up to date.
How do I get the logs from Millipixels?
just run millipixels in the terminal, move the slider around, and exit it. The logs will be in the terminal.
2 Likes
$ millipixels
Found config file at /usr/share/millipixels/config/purism,librem5r4.ini
Adding camera big from config
matched GRBG8 to GRBG8 3
matched GRBG8 to GRBG8 3
Adding camera selfie from config
matched GBRG16 to GBRG16 14
matched GBRG16 to GBRG16 14
Found postprocessor script at /usr/share/millipixels/postprocess.sh
mp_device_list_find_remove imx7-csi s5k3l6xx 3-002d
18: there’s csi, looking for s5k3l6xx 3-002d
18: there’s csi capture, looking for s5k3l6xx 3-002d
18: there’s imx8mq-mipi-csi2 30a70000.csi, looking for s5k3l6xx 3-002d
18: there’s hi846 2-0020, looking for s5k3l6xx 3-002d
17: there’s csi, looking for s5k3l6xx 3-002d
17: there’s csi capture, looking for s5k3l6xx 3-002d
17: there’s imx8mq-mipi-csi2 30b60000.csi, looking for s5k3l6xx 3-002d
17: there’s s5k3l6xx 3-002d, looking for s5k3l6xx 3-002d
found!
devname /dev/video2
17: there’s csi, looking for s5k3l6xx 3-002d
17: there’s csi capture, looking for s5k3l6xx 3-002d
17: there’s imx8mq-mipi-csi2 30b60000.csi, looking for s5k3l6xx 3-002d
17: there’s s5k3l6xx 3-002d, looking for s5k3l6xx 3-002d
found!
linking flags 0 source 15:0 sink 10:0
MPDevice: MEDIA_IOC_SETUP_LINK error 22, Invalid argument
mp_device_list_find_remove imx7-csi hi846 2-0020
18: there’s csi, looking for hi846 2-0020
18: there’s csi capture, looking for hi846 2-0020
18: there’s imx8mq-mipi-csi2 30a70000.csi, looking for hi846 2-0020
18: there’s hi846 2-0020, looking for hi846 2-0020
found!
devname /dev/video0
18: there’s csi, looking for hi846 2-0020
18: there’s csi capture, looking for hi846 2-0020
18: there’s imx8mq-mipi-csi2 30a70000.csi, looking for hi846 2-0020
18: there’s hi846 2-0020, looking for hi846 2-0020
found!
linking flags 0 source 15:0 sink 10:0
MPDevice: MEDIA_IOC_SETUP_LINK error 22, Invalid argument
linking flags 1 source 15:0 sink 10:0
MPDevice: MEDIA_IOC_SETUP_LINK error 22, Invalid argument
Setting mode 1052 780
[7:26:14.726252334] [11697] INFO Camera camera_manager.cpp:293 libcamera v0.0.0
[7:26:14.747986249] [11698] WARN CameraSensorProperties camera_sensor_properties.cpp:141 No static properties available for ‘s5k3l6xx’
[7:26:14.748210180] [11698] WARN CameraSensorProperties camera_sensor_properties.cpp:143 Please consider updating the camera sensor properties database
[7:26:14.754071990] [11697] INFO Camera camera.cpp:937 configuring streams: (0) 1052x780-SGRBG8
[7:26:14.756192615] [11698] ERROR DeviceEnumerator device_enumerator.cpp:166 Removing media device /dev/media2 while still in use
ok
[sudo] password for purism: MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
NOTE: the above lines repeated a LOT more
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
MPCamera: VIDIOC_DQBUF error 22, Invalid argument
purism@librem5:~$
That what I got when I opened Millipixels from the terminal and just tried changing the focus slider a couple of times.
There you go: this means that you don’t have the permissions to set the focus. This could only happen when some packages are at older versions. Could you paste the output of this command?
find /etc/sudoers.d
1 Like
~$ find /etc/sudoers.d
/etc/sudoers.d
/etc/sudoers.d/README
purism@librem5:~$
Can you do:
sudo apt-get update
sudo apt-get dist-upgrade
~$ sudo apt-get update
[sudo] password for purism:
Get:1 https://repo.pureos.net/pureos byzantium InRelease [5851 B]
Get:2 https://repo.pureos.net/pureos byzantium-updates InRelease [4580 B]
Get:3 https://repo.pureos.net/pureos byzantium-security InRelease [4581 B]
Get:4 https://repo.pureos.net/pureos octarine InRelease [4666 B]
Fetched 19.7 kB in 2s (8192 B/s)
Reading package lists… Done
purism@librem5:~$ sudo apt-get dist-upgrade
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
purism@librem5:~$
That looks wrong, but I’ll get back to you tomorrow.
1 Like
I would say by definition that you should have reflashed this phone from scratch - because obviously otherwise you have no idea of the state of the phone. I mean forget about trust, there are just reliability issues. The previous owner could have been ‘tinkering’. That is after all half the fun of the Librem 5. 
2 Likes
You have the “octarine” repository in the sources, meaning that the previous owner was experimenting with the phone. As such, it makes no sense to try to debug it if you don’t know which customizations were performed. I advise reflashing.
1 Like
I added the octarine repository to be able to install a newer version of Dino that was going to be formatted to the screen of the Librem 5. That said, I didn’t reflash it when I received it, so I suppose that is a decent step. Seems a little overkill, though.
In short, you’re missing this change: https://source.puri.sm/Librem5/millipixels/-/merge_requests/49/diffs
But it’s included in the newest Millipixels, so something more unusual went wrong, and unless it appears in a new install, I don’t think it’s worth spending the time debugging.
2 Likes
Not in my opinion, for a phone where one of the selling points is privacy and security. If you buy a phone from a random on the internet, you won’t know whether the seller has intentionally left compromised software on the phone.
When a phone (any phone) is sold privately I would expect both seller and buyer to nuke the phone. The seller is ensuring that any confidential info has been securely erased. The buyer is ensuring that any malware has been removed.
1 Like