I came here to basically say this. It’s especially bad when you aren’t even sure if you want to keep the service and are just testing it out. If I already have to go through a huge setup/troubleshooting process just to test the app, then I’m not feeling very good about it.

Oh I see. When I read your first comment I understood ‘functional’ to mean more like “it works but not very well”. I did see in the github issues that they are working on SSO and Android Auto so when that comes I’ll give it a try.

It seems to be missing SSO login support and Android Auto. The official app does so I feel like that makes it more functional than Lissen. At least for me.

Is this better in some way than the one developed by the audiobookshelf team?

Correct. If I remove the save then the ROM will take me to the tutorial and everything. I hadn’t done an md5 check but your first question had me try something else: i removed the save, started a new game on my phone and saved it the first moment I could. Closed retroarch and restarted it on my phone again, and I got the error again, even though the sage was created by that exact retroarch instance. Then i tried the mew save on the deck and it loaded fine. Seems like I just have an issue with retro arch on my other devices but not the save itself.

From the ROM. I’ve actually not tried a state because I usually don’t use them.

This is an interesting point. One of my other devices is my android, so flash, but another is a laptop with an HDD.

Lol, yeah, why are you working on my stream deck but my other devices?

I’m still waiting for an ice blue shell.

Could it be a lid and the hole is for steam to escape?