I am using Ubuntu Touch 24.04-1.0 (Release candidate channel) on my Fairphone 5 (Android 13 kernel as recommended) and video decoding stops working after the device has been powered on for multiple hours.
Once that happens, no app that uses hardware decoding is able to play videos (e.g. Media Player, Morph Browser and even Android apps in Waydroid).
Trying to play a video in Media Player results in an "Error playing video" popup with the message "Failure connecting with playback backend." and the following journal messages:
Oct 06 17:03:20 ubuntu-phablet lomiri-mediaplayer-app[182490]: library "eglSubDriverAndroid.so" not found
Oct 06 17:03:20 ubuntu-phablet lomiri-mediaplayer-app[182490]: file offset for the library "/vendor/lib64/hw/gralloc.default.so" >= file size: 0 >= 0
Oct 06 17:03:20 ubuntu-phablet lomiri-mediaplayer-app[182490]: Creating a QMirClientScreen now
Oct 06 17:03:21 ubuntu-phablet lomiri-mediaplayer-app[182490]: virtual QMediaService* AalServicePlugin::create(const QString&) "org.qt-project.qt.mediaplayer"
Oct 06 17:03:21 ubuntu-phablet lomiri-mediaplayer-app[182490]: Failed to start a new media-hub player session: Failed to create session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Oct 06 17:03:21 ubuntu-phablet lomiri-mediaplayer-app[182490]: Failed to create a new media player backend. Video playback will not function.
Oct 06 17:03:21 ubuntu-phablet lomiri-mediaplayer-app[182490]: Could not finish contructing new AalMediaPlayerService instance since m_hubPlayerSession is NULL
Oct 06 17:03:22 ubuntu-phablet lomiri-mediaplayer-app[182490]: bool QDeclarativeVideoOutput::createBackend(QMediaService*) Media service has neither renderer nor window control available.
Oct 06 17:03:22 ubuntu-phablet lomiri-mediaplayer-app[182490]: libpng warning: iCCP: known incorrect sRGB profile
Oct 06 17:03:22 ubuntu-phablet lomiri-mediaplayer-app[182490]: file:///usr/share/lomiri-mediaplayer-app/qml/player/ToolBar.qml:71:9: QML Item: Binding loop detected for property "height"
Oct 06 17:03:22 ubuntu-phablet lomiri-mediaplayer-app[182490]: qml: AbstractPlayer: 5:The QMediaPlayer object does not have a valid service
Oct 06 17:03:22 ubuntu-phablet lomiri-mediaplayer-app[182490]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/Lomiri/Components/Popups/1.2/Dialog.qml:154:5: QML StyledItem: Mixing of Lomiri.Components module versions 1.2 and 1.3 detected!
Oct 06 17:03:22 ubuntu-phablet lomiri-mediaplayer-app[182490]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/Lomiri/Components/Popups/1.2/PopupBase.qml:193: TypeError: Cannot read property 'activeFocusItem' of null
Oct 06 17:03:22 ubuntu-phablet lomiri-mediaplayer-app[182490]: file:///usr/share/lomiri-mediaplayer-app/qml/player/ToolBar.qml:71:9: QML Item: Binding loop detected for property "height"
Oct 06 17:03:22 ubuntu-phablet lomiri-mediaplayer-app[182490]: ** Application is now activ
In dmesg I see the following lines:
[84592.596338] [haptic_hv][1874]seq_store: seq0=0x00
[84592.598427] [haptic_hv][1874]seq_store: seq0=0x01
[84592.598668] [haptic_hv][1907]loop_store: seq0 loop=0x00
[84592.599780] [haptic_hv][1673]duration_store: duration=10
[84592.599810] [haptic_hv][1612]brightness_set: enter
[84592.600828] [haptic_hv][0279]aw8692x_wait_enter_standby: entered standby!
[84592.601030] [haptic_hv][0417]aw8692x_upload_lra: write f0_cali_data to trim_lra = 0x00
[84592.601808] [haptic_hv][0451]ram_vbat_comp: ram vbat comp close
[84592.601813] [haptic_hv][0324]aw8692x_play_mode: enter ram mode
[84592.602291] [haptic_hv][0293]aw8692x_bst_mode_config: haptic bst mode = bst
[84592.603508] [haptic_hv][0260]aw8692x_play_go: enter, flag = 1
[84592.672236] init: sys_prop: invalid command 2
[84593.026014] init: Control message: Could not find 'vendor.qti.hardware.cacert@1.0::IService/default' for ctl.interface_start from pid: 135 (/system/bin/hwservicemanager)
Rebooting the phone fixes the issue; however, it is quite annoying having to reboot so frequently.
Has anyone else experienced similar issues or knows how to fix this without a full reboot?
