05-03-2021, 08:40 PM
(This post was last modified: 05-03-2021, 08:43 PM by TheOldPresbyope.
Edit Reason: ETA
)
Thanks @pmartin
I can confirm your procedure for installing and starting firefox in place of chromium to render the moOdeUI on either local DSI or local HDMI display.
I am not in a position to test long-term behavior [1] but the procedure is easy and reversible so you few who are experiencing variations of the reported issue can simply try out this alternative for yourselves.
The following are not criticisms, just observations:
1) this installation consumes an additional ca 200MB of storage (180MB for firefox and only 20MB---wow!---for the awesome window manager). This is trivial and could be mitigated by uninstalling chromium-browser which consumes ca 300MB.
2) the awesome/firefox combo appears to be using somewhat more system memory---something between 50MB and 100MB more during normal operation. I doubt this would be an issue unless, perhaps, when running on an RPiZero W.
3) startup of the local display takes about 20s (I counted in my head, so not precise!). This with an RPi3B+.
4) of this time, the first 5s the screen displays a blue screen while the Xserver initializes. The next 5s it displays the "awesome" awesome splash screen. During the next 10s it displays first blank screen and then various elements of the moOdeUI showing up.
Compare the chromium browser: 5s blue screen; then 5s or so with first blank screen and then various elements of the moOdeUI showing up. Net result: it takes the awesome/firefox combo about twice as long to settle.
ETA: very nice writeup by the way.
Regards,
Kent
[1] I'm not supposed to be doing any dev/testing work during the next 2 months while I fix up my house and prepare to move. My secret pleasure is scanning moOde forum posts when I take a coffee break. Couldn't help myself trying out firefox. I know it's wrong but I'm weak.
I can confirm your procedure for installing and starting firefox in place of chromium to render the moOdeUI on either local DSI or local HDMI display.
I am not in a position to test long-term behavior [1] but the procedure is easy and reversible so you few who are experiencing variations of the reported issue can simply try out this alternative for yourselves.
The following are not criticisms, just observations:
1) this installation consumes an additional ca 200MB of storage (180MB for firefox and only 20MB---wow!---for the awesome window manager). This is trivial and could be mitigated by uninstalling chromium-browser which consumes ca 300MB.
2) the awesome/firefox combo appears to be using somewhat more system memory---something between 50MB and 100MB more during normal operation. I doubt this would be an issue unless, perhaps, when running on an RPiZero W.
3) startup of the local display takes about 20s (I counted in my head, so not precise!). This with an RPi3B+.
4) of this time, the first 5s the screen displays a blue screen while the Xserver initializes. The next 5s it displays the "awesome" awesome splash screen. During the next 10s it displays first blank screen and then various elements of the moOdeUI showing up.
Compare the chromium browser: 5s blue screen; then 5s or so with first blank screen and then various elements of the moOdeUI showing up. Net result: it takes the awesome/firefox combo about twice as long to settle.
ETA: very nice writeup by the way.
Regards,
Kent
[1] I'm not supposed to be doing any dev/testing work during the next 2 months while I fix up my house and prepare to move. My secret pleasure is scanning moOde forum posts when I take a coffee break. Couldn't help myself trying out firefox. I know it's wrong but I'm weak.
