Points of note.
–Millipixels always works after a reboot and does so for a while. I can’t find a repeatable pattern to when it stops working.
–Very rarely it will start working again but only until I close the ap and open it again. Then back to the swirling thing.
–When its working properly the camera preview continues to update even while swirling icon shows processing. When its not the image stops updating and the swirling icon continues to swirl for ever.
–If you don’t close millipixels the battery will drain quickly. Not sure if this relates to this issue.
Any tips on what may cause this and how I can resolve it?
How about pointing me to a process or service I can kill to recover camera functionality without needing a reboot? Closing and reopening millipixels doesn’t work.
For the future, please explicitly write that you are using unreleased versions of packages when asking for help or submitting issues. In this case the screenshot quickly gave it away, but it could have been a headscratcher otherwise. The latest version of Millipixels available in Byzantium is 0.20.0-1pureos1.
root@pureos:/usr/local/bin# dpkg -s millipixels
Status: deinstall ok config-files
Maintainer: Dorota Czaplejewicz <email@example.com>
Depends: libbsd0 (>= 0.0), libc6 (>= 2.18), libcairo2 (>= 1.2.4), libcamera0 (>= 0~git20220628+27cc0a6b), libgcc-s1 (>= 4.2), libglib2.0-0 (>= 2.65.1), libgtk-3-0 (>= 3.16.2), libstdc++6 (>= 5.2), libtiff5 (>= 4.0.3), libzbar0 (>= 0.10), libraw-bin, v4l-utils
Recommends: dcraw, graphicsmagick-imagemagick-compat | imagemagick, libimage-exiftool-perl
Breaks: linux-image-librem5 (<< 5.16.18pureos2)
Description: GTK3 camera app for mobile using the V4L2 media request API
Millipixels is a GTK3 camera application that knows how to deal with the V4L2
media request API.
I then did apt remove millipixels, which said it removed it but… …it still launched.
I then did ‘which millipixels’ and found it at /usr/loca/bin I renamed it to millipixels_old
Now it doesn’t launch.
I then did ‘apt install millipixels’ and my camera ap is back with what looks like manual controls and no video record options. It is working fine. I will continue to try and reproduce my issue and report back.
I’m guessing you somehow installed millipixels (from source?) into /usr/local/bin. I normally recommend installing into a prefix in the home directory instead, where it’s harder to mess up the entire OS.
Nothing out of the ordinary running I can think of. The phone gives notifications from text messages, calls, Geary, Nheko. I have a script watching for new messages in Nheko. I have used firefox, VLC, Feeds and ??.
My script watching for messages from Nheko can be found here but I don’t think its anything important.
2/3 down, the code sniplet.
How long is it usually from the time you write a kernel patch until I may see it on my phone? How can I monitor for when this patch gets applied to my device?