12:40 <asdf28> when i turn off my android box using the remote, it enters a type of "suspend" state where the status light turns from blue to red, and it can be woken up again using the remote. is this possible on a generic linux system? or is this android specific?

12:43 <asdf28> i tried "systemctl suspend" but the remote wasn't able to wake it up

14:57 <narmstrong> asdf28: it’s feasible but not easy

14:58 <narmstrong> In short: the wakup sources are hard coded in the binary loaded at boot

15:23 <asdf28> could you make the remote act as a keyboard and use it that way as a wakeup source?

15:24 <asdf28> i'm still struggling to register the remote correctly

15:24 <asdf28> this is a lot harder than i thought

15:24 <asdf28> i got as far as making it register keypresses when i test it using "ir-keytable -t"

15:26 <asdf28> so it seems to register KEY_LEFT when i press left, but it won't move the cursor left in a text editor as i hoped

17:33 <chewitt> asdf28 the IR wake code is in bl301 which is part of the boot FIPs (early boot firmware)

17:34 <chewitt> most original "ROM" images should have this set correctly for the remote/box

17:35 <chewitt> but if you've been using non-original ROMs, it might boot but be set for some other IR hardware

17:35 <chewitt> and sometimes the box is a clone with another box's software

17:35 <chewitt> (the usual Android dice roll)

17:36 <chewitt> configuring ir-keytable stuff should be fairly simple

17:37 <chewitt> https://libreelec.wiki/configuration/ir-remotes might help

17:38 <chewitt> but when you 'suspend' everything falls back to the boot code, userspace cannot do anything

17:46 <asdf28> thanks chewitt

17:48 <chewitt> on x86 hardware you can often set a USB port so that keypress/mouse sends a wake signal, but there's nothing like this

17:50 <asdf28> so if i'm booting from an SD card image that relies on the android boot firmware, it could work?

17:50 <asdf28> this is confusing

17:52 <chewitt> if you're booting the original Android ROM on emmc, and that is correct for the box, it should work

17:52 <chewitt> original Android boot firmware (not ROM)

17:54 <chewitt> the only thing you'd need to do is create the IR keymap so that KEY_POWER sends the box into suspend

17:54 <asdf28> is "systemctl suspend" the same as suspend under android?

17:54 <asdf28> hardware wise?

17:55 <chewitt> it might depend on the kernel config (defconfig) but I'd expect it to be fairly simple to get into suspend/sleep mde

17:55 <chewitt> mode

17:56 <asdf28> i can suspend it using systemctl suspend, it just won't wake up anymore

17:57 <asdf28> how would you do that, use KEY_POWER to suspend it?

17:58 <asdf28> it does recognize the keycodes

17:58 <asdf28> when i use the test app

17:58 <asdf28> but i don't know how to make the keycodes actually do something

17:59 <chewitt> if it doesn't wake, the wrong IR code is hard-coded in the boot firmware

18:00 <chewitt> it happens :)

18:01 <asdf28> when the box is suspended on android, the LED turns red, but on generic linux, it stays blue

18:01 <asdf28> but the screen does turn off

18:01 <asdf28> i thought maybe that's two different kinds of suspend mode, who knows

18:02 <chewitt> probably doesn't have the right bits set in device-tree

18:02 <chewitt> to toggle the LED back to red

18:16 <asdf28> well that's interesting to know at least

18:16 <asdf28> that the remote wakeup code is in the firmware