Degradation since December update

[mrozentsvayg]

Last few months been running teslausb on OrangePi Zero 2W, everything worked as expected.
Up until ./bin/setup-teslausb upgrade in the end in December, then I started to have weird issues.
The issue manifests as zero-length for some files, which totally confuse tesla player (showing blank screen, no Sentry etc. folders), and occasionally teslausb viewer (eg Failed to fetch video detail Cannot destructure 'ye(...)(...)' as it is undefined.).
Tried another SD card with fresh armbian community build, ended up with the same in a couple days.

Is it only me or anyone else experiencing the same?
Not sure if there's a graceful rollback without forking a repo, unfortunately to [try to] isolate it in the code.
Assuming it's not hardware, but the armbian seems to be fine.

[marcone]

Do you know if the OrangePi and Armbian images you were running on the OrangePi Zero 2W were 32-bit or 64-bit images?
Also, have you tried rebooting the car?

[mrozentsvayg]

@marcone
in January i've tried a community minimal aarch64 image, downloaded from https://www.armbian.com/orange-pi-zero-2w/
currently updated to "25.2.0-trunk.419"
i've used self-compiled image before, but it's all the same since December - the system is rock solid, but hardly usable for the purpose - it's only randomly available for tesla to use, but more often is not or the car complains that the speed is too low..

it used to be pretty stable before December, but now i'm just using USB stick