[samsung-serranovelte] Phosh: "wake up" approx. 2 mins after login

Describe your issue

On samsung-serranovelte with Phosh installed, when logging in after boot and thereafter locking the screen, it wakes up again approx. 2 mins later, but goes dark again after a few seconds.

When the wake up happens, there is a sound of the UI like indicating that something has been connected.

Also, in these first approx. 2 mins after boot, the battery icon shows a question mark (the battery percentage is reported, though). After the 2 mins, the battery icon becomes "normal" as expected.

The screen wake up and the "connecting" sound seem related to the battery icon thing. Actually it's the battery icon thing triggering the two other symptoms.

What's the expected behaviour?

• When logging in after boot and thereafter locking screen, remain in that state
• Usual battery icon when reaching graphical environment

What's the current behaviour?

• Lockscreen wakes up after 2 mins, goes black again after a few seconds
• Battery icon with question mark for 2 mins

How to reproduce your issue?

pmbootstrap init & install, flash device, boot. After the device reached the graphical environment, login and then lock the screen.

What device are you using?

samsung-serranovelte

On what postmarketOS version did you encounter the issue?

• edge (master branch)
• v21.03
• v20.05

On what environment did you encounter the issue?

Phone environments

• Phosh
• Plasma Mobile
• Sxmo

Other

• No environment
• GNOME
• KDE Plasma
• Kodi
• MATE
• Shelli
• Sway
• Weston
• Xfce4
• fbkeyboard
• i3wm

How did you get postmarketOS image?

• from https://images.postmarketos.org
• I built it using pmbootstrap
• It was preinstalled on my device

Additional information

I could work around this by refreshing the rt5033 battery information in UPower before reaching the graphical environment. This was done by a oneshot dbus command during boot. To have this command executed before reaching graphical environment, I manually set up an OpenRC service to do this. I think there are other possibilities, too, but I didn't further investigate this yet.

# mkdir /opt/startup-scripts (you can also choose another location)

# nano /opt/startup-scripts/update-upower (new file)

#!/bin/sh

dbus-send --print-reply --system --dest=org.freedesktop.UPower /org/freedesktop/UPower/devices/battery_rt5033_battery org.freedesktop.UPower.Device.Refresh

# chmod +x /opt/startup-scripts/update-upower

# nano /etc/init.d/update-upower (new file)

#!/sbin/openrc-run

command="/opt/startup-scripts/update-upower"

# chmod +x /etc/init.d/update-upower

# rc-update add update-upower default

# reboot

[phew, how can I insert a whole code block?]

However, it should be solved in a way that the issue doesn't show up at all after flashing the device.

In order to know in what direction a solution should go, I'd like place following questions:

• Are there other devices showing this issue in Phosh as well?
• Is this issue also existent in other UI's? It may not be as noticable as in Phosh, e.g. other symptoms.