All my buttons stopped working on AmberELEC out of nowhere
By simply putting the RG351V on sleep mode, the built-in buttons (OSH Controller) stopped working entirely, and didn't come back by shutting down/resetting the OS. OTG Controllers also didn't work. By doing a fresh AmberELEC install, it all went back to normal.
Not sure if this is a specific Sanshiro Tower bug or if my hardware is prone to failure.
Is ArkOS a more stable option in that regard?
EDIT: A day later, it just got worse. Left it charging for a couple hours to check if the culprit was the battery. At first everything worked great but then the controls died on me again (at 100% battery indicator). This time, they won't come back even after multiple reboots, changing SD cards etc.
Posted Jul 8, 2022, 11:24 AM UTC · edited
913
This is a known hardware issue that affects the RG351p, RG351m, and RG351v. This issue is not present on the RG351MP. The issue is observable on all FWs that can be run on the three affected devices. There's no workaround for it, apart from the general advice that the sleep mode on the RG351p/m/v handhelds can cause this issue.
Unlike other RK3326 handhelds, The RG351p/m/v (notably however, not the MP ) models use USB input for the controls. There is no way to change this, because this is how the PCB was designed. USB controls use a touch more power than the GPIO inputs used by other RK3326 devices. As a result and upon wakeup from sleep the power delivery to the control module sometimes fails and causes the device to not register inputs until it has been restarted (or in some cases, until some time passes.)
I don't know with any greater depth why this is the case - but it can be mitigated (though not eliminated) by keeping the battery charge higher. The only thing you can really do about it is to just be mindful that you may need to hard restart after wakeup if the controls aren't responsive.
(Note that this may not be 100% accurate, and is based on memory and current understanding, which may be outdated or recalled poorly. Someone more familiar with these devices hardware may be able to provide a more accurate summation)
Woah, it sucks. I wish I knew that before jumping in. What's curious is the absence of such problems in stock firmware as far as I have noticed, since the only workaround I've found was swapping SD cards.
Good comment!