Nemomobile in June 2022
There haven’t been any revolutions in June. We still have to fix compatibility with the new toolchain. Phone calls and the camera still don’t work. The call history and alarm handler have been reworked and the Gallery app improved. Translations of plurals caused some extra effort during the merge.
There were two conference talks: At the DevConf Mini conference and at the Installfest conference. The Installfest (CZ) will cut the stream into separate talks soon.
Manjaro has updated to a new toolchain. This caused some troubles with the rebuild of Nemo packages. Namely libdsm package and libconnman-qt package. The WebOS team is working on Qt6 support of it. Their code fixed partially the issue with GCC 12, but there was still some ambiguous use of namespace.
The libglacierapp now contains two new features. There is a function to wipe application data and to the set application language. The wipe function doesn’t remove data provided by libraries. For example, the contact list is stored in another location.
Presage packages were added to the nemo-packaging repository, so the working predictive keyboard is coming very soon.
Glacier UI on postmarketOS seems to be not working right now.
As was shown in the previous blog post phone calls are not working with audio. A phone call could be done after the profile switched manually:
pactl set-card-profile 0 "Voice Call"
After the phone call, it must be switched back to HiFi profile to be able to play a ringtone or any other music.
The call history page was reworked. The icon is distinguishing incoming, outgoing, and missed calls. By default, it dials the number, but it allows also writing a text message. The connection to the contact editor is not ready yet. The data itself is currently mocked up because records are not created after finishing of the phone call.
Meanwhile, UBports users are fighting with spam calls. It seems that the proposed solution could be used after small changes also in Nemo.
The camera is connected from hardware to application with video 4 linux device using media-ctl, gstreamer, and QtMultimedia. It seems the /dev/video2 needs to be created in a different way. After all, the colorimetry plugin reports an error when the glacier-camera application is started.
CameraBin error: "Device '/dev/video2' does not support 2:0:0:0 colorimetry"
There is currently some Google Summer of Code student working on the color space GStreamer plugin. So it will be hopefully fixed soon.
The MegaPixels application has its own processing pipeline, so it works there. It seems the following pipeline can grab some images:
gst-launch-1.0 v4l2src device=/dev/video2 ! 'video/x-bayer,format=bggr,width=1280,height=720,framerate=15/1,colorimetry=(string)1:1:0:0' ! bayer2rgb ! videorate \! video/x-raw,framerate=3/1 \! videoscale \! video/x-raw,width=320,height=240 \! videoconvert \! xvimagesink
In Nemo it should use
waylandsink instead, but it doesn’t work for some reason.
The libcamera should be able to provide some features into the GStreamer pipeline, such as control of focal point and so on.
In KVM, it is possible to redirect the USB camera into it and use it with the glacier-camera application. It turned out that there are a couple of bugs to fix. There are a couple of features missing. For example, it is not possible to take a photo and save it into a file. The reference implementation from Qt Multimedia works perfectly fine, so now it is just about finding the missing or incorrect method or parameters.
Glacier gallery got another improvement. Now it is possible to crop the image.
The alarm handler application was reworked. It can now show the calendar and alarm events.
Previously, the application was popping up repeatedly. It turned out that the timed daemon had the
WakeUp event in the list
of events. Now is possible to filter those events out of the list.
There was a little confusion caused by the number of plural forms in Transifex and in Qt Linguist. The first one showed two forms and the second one showed three forms of plurals:
As a consequence, Transifex considered the translation reimported from GitHub as incomplete and discarded it.
Moreover, Transifex recommends writing the translations directly within their user interface or using the import dialog in the same place. Merging of translations into GitHub and consequent import to Transifex is not recommended.