2025-05-03, 03:57 AM
Latest commit on the lua-input branch should fix the crashing that happens when input.lua is missing.
There's no reason that specific button should behave differently than the others, assuming you have a mapping for it in input.lua. You could try replacing your input.lua with the script I use for hardware testing, and watching the debug console (idf.py monitor from your build environment); it'll print all the button states whenever they change.
If it's a hardware problem, you could try just... pushing the button really hard to nudge it back into working. I had to do that occasionally on my original prototype.
Quote:So, is there a way to tell the difference between if the bottom right/southeast button on my Tangarine is physically broken vs. if the firmware isn't working as intended? Right now, I can't use the SE button to go to the "Now Playing" menu.
There's no reason that specific button should behave differently than the others, assuming you have a mapping for it in input.lua. You could try replacing your input.lua with the script I use for hardware testing, and watching the debug console (idf.py monitor from your build environment); it'll print all the button states whenever they change.
If it's a hardware problem, you could try just... pushing the button really hard to nudge it back into working. I had to do that occasionally on my original prototype.
