Not rendering after service restart

[arpio23]

This might be a device specific issue?

After upgrading the shell, the service restarts and you see actually the last rendered frame from the last session and nothing works. Seems like its running on a dummy display.

Can also be reproduced by just restarting cutie-ui-io.service.

I encountered same issue when testing wayfire, its not really the cutie code. Its even possible to start apps by blindly swipe and touch but its not rendering on the screen.

Is it possible to prevent the service to restart after upgrade? Maybe just informing the user that a restart is needed?

Maybe it is the service file itself? Cause I just adapted the cutie one for wayfire.

[erikinkinen]

This is a device specific issue. I have a similar problem on sargo. Restarting the Android-side hwcomposer service does fix it on sargo. AFAIK, it is an issue in the proprietary hwcomposer vendor implementation. It also affects phosh.

You can try running systemctl restart android-service@hwcomposer.

[arpio23]

Thats what I was thinking also. If we going to target not only a couple of devices, is it possible to make other services restart if cutie restarts?

[erikinkinen]

Thats what I was thinking also. If we going to target not only a couple of devices, is it possible to make other services restart if cutie restarts?

I did not mean to make the service restart on upgrade, but it was the default setting. The phosh packaging explicitly disables this. So, I disabled in now on cutie-shell.

After all, the whole phone should preferable be rebooted after updating. When we have a graphical front-end for updates. It should reboot as well. Actually, I would prefer offline updates then (in the style of gnome-software or kde's discover).

[arpio23]

I'm happy with this solution. I would close this issue.

[erikinkinen]

I'm happy with this solution. I would close this issue.

Ok, then. It is resolved.