The installation of UT on a Cosmo Communicator works for me and others after installing Gemian. Has anybody managed to avoid this extra burden? I am willing to try suggestions on another fresh Cosmo Communicator.
(Could somebody create a Planet subcategory and move my post and others there? That would help ...)
@melu9wuv Kaldi is a toolkit and far from an easy installation. If more people are interested, I can share a recipe, mabye including ASR models for EN and DE.
You can run Kaldi-based ASR on UBports. This solution needs no Internet and preserves privacy. I am using this for German and English. But this is not an app, only a tool for converting wav files to text.
The new devices page is really nice and helpful.
Small suggestion. I am happily running UT on a Cosmo Communicator (using this installation method https://github.com/gemian/gemian/wiki/UBPorts , but other methods exist) and wonder why this device is not mentioned on https://devices.ubuntu-touch.io/ ?
I can add some details. The LED is on and white. The device is getting warm, so in a sense it is hot spot 
@moncon said in ut-sysbench-qt-gui: Compare CPU performance of different devices:
Works on Cosmo Communicator, copes with landscape view as well.
Same device, OTA-19: the two lower buttons are not visible for me. How did you manage to see them?
@johndoe said in ut-sysbench-qt-gui: Compare CPU performance of different devices:
if some of you could share your device's name together with a screenshot of the result you get
A save (as plain text) button in the app would be great, so that people can post results for immediate processing via scripts or copy/paste.
A discussion on a similar topic was started 3 days ago https://forums.ubports.com/topic/6561/oneplus-6t-and-speech-to-text
Thanks for clarifying and good to hear that it worked. Which file did you use for downgrading to Android 9?
@moncon said in ut-sysbench-qt-gui: Compare CPU performance of different devices:
Works on Cosmo Communicator, copes with landscape view as well.
Same device, OTA-19: the two lower buttons are not visible for me. How did you manage to see them?
@johndoe said in ut-sysbench-qt-gui: Compare CPU performance of different devices:
if some of you could share your device's name together with a screenshot of the result you get
A save (as plain text) button in the app would be great, so that people can post results for immediate processing via scripts or copy/paste.
@portu51 The question from @rbhawk, me, and others is: How to install OxygenOS 9? I sent one device to OnePlus and they refused to downgrade ("not possible", haha).
@flohack I switched from stable to RC and the installed version is reported as 2021-W36 (not 2021-W27, OnePlus 3T). It broke the perfectly working HotSpot :-(, now I need several tries to turn it on.
@ada Most postmarketOS pages are quite up to date. The predecessors (OnePlus 6 and 6T) are in a much better pmOS state than this device; they are even promoted to "community device" status.
You can add upstart scripts in user space. Example: put into .config/upstart/local-init.conf:
description "run script local-init"
start on started unity8
exec /home/phablet/local/bin/local-init
and add your commands into the file given in the exec line.
@Mou-du-GNU The relevant section is labelled "French" in https://gitlab.com/ubports/community-ports/android9/planet-cosmocom/planet-cosmocom/-/blob/master/overlay/system/usr/share/X11/xkb/symbols/planet_vndr/cosmo
AE... is the top row of keys, AD the second etc. Compare to your physical keyboard.
@davedanger Can you share it here (at least its core)? Maybe someone can help you.
@mou-du-gnu There have been keyboard mapping problems (Russian, Dvorak, ...) that have been resolved quite quickly via an issue in gitlab. Please open a good one at https://gitlab.com/ubports/community-ports/android9/planet-cosmocom/planet-cosmocom/-/issues
Something related to this HotSpot issue. Some devices, like the OnePlus 3T, have a HotSpot that always works on this first attempt. For others, like the Cosmo Communicator, the HotSpot never works.