BadgerOS image becomes unresponsive after first app launch, but works OK with MicroPython one

[Synchro]

I just received my Badger2040 W. I read the getting started guide and found out how to the latest OS, and I've got that process working fine. However, once installed, things are not quite so smooth.

If I wipe it with flash_nuke.uf2, and then install MicroPython from pimoroni-badger2040w-v0.0.3-micropython.uf2, it resets, flashes the screen a couple of times (but the Badger OS screen still comes up, but buttons are unresponsive – I'm assuming this is some leftover image in the screen's own memory?). In this mode, I can interrupt it with Thonny and python works, but obviously none of the Badger OS apps are there.

If I wipe it again, and then install the BadgerOS image from pimoroni-badger2040w-v0.0.3-micropython-with-badger-os.uf2, the OS screen comes up again, but I can't interrupt it from Thonny, and also the buttons are unresponsive, and I can't launch any of the apps.

In both situations, the white LED in bottom left comes on and stays on.

I'm not using a battery, only USB power, but power-cycling it makes no difference.

When I first powered it on I was able to launch the apps, and I noticed that it showed 23% space used. After doing the 0.0.3 update (from blank, as above), it's using 40%, so I'm assuming that this means that it was running an older (and smaller) version of Badger OS that worked, but the newer version does not. After installing 0.0.2, I see that the usage graph has remained the same?

On further testing with both 0.0.2 and 0.0.3, they both act the same way - after installing a fresh OS image, I can launch any of the apps, then return to the launch screen, but after that everything is unresponsive, and I can no longer launch apps, even after a power cycle or reset. To clarify, after a clean install I can launch one app, exit it, and then the badger is seemingly dead.

I've not seen anything that suggests the two buttons on the right work – If I press one of them after a clean install, nothing happens, but I can't launch any apps either, and I have to wipe it again.

FWIW I'm on macOS running Thonny 4.1.2. I've also tried all this without Thonny running, so it's not interrupting anything.

Is this expected behaviour, or have I missed something?