MobileRead Forums - View Single Post - How to remap the 2 keys on the cover of the Nova Air with SDS100 Keymapper?

csdvrx · 10-30-2022, 11:33 AM

After reading your message, I tried:

BOOX:/ $ settings put system switch_key 1

It did nothing to help keymapper, so I reverted that with:

BOOX:/ $ settings put system switch_key null

However, the next one is more interesting:

BOOX:/ $ settings put global key_custom_side_key_short_press_enable 1

It stops the keys from doing volume, while still making them uncatchable by keymapper. So whatever it does, it seems to do it in the right place!

Would you know what it influences? I'd like to disable that.

You mention:

Here's a simplified diagram I just made of how keys work. Your side keys are lots more complicated because they are intercepted somewhere and they get turned into a string and get processed through res/raw/keypad.json (or res/raw/bt_keypad.json) in /system/framework/framework-res.apk. That causes your PgDn to work only when you release the button (instead of when pressing) because it has to wait to determine short/long press. I defeated that on my Poke3 because it drove me crazy.

Super interesting as it confirms my guess about something doing a weird interpretation.

You're going to have to change the keylayout. Me, I'd change the dtb too (because it's easy and just a single change to the boot.img that doesn't need to be a Magisk module).

Can you please tell me what you did and how to replicate your changes?

My goal is to have the side buttons each emit a key (any key!) that I can intercept with keymapper to map that to actions.

Ideally, I would do the same to the power button, since the Hall sensor is sufficient to wakeup the boox, and the timeout sufficient to put it to sleep.

If you need a copy of my Nova Air C boot.img, I think you already have one as it's found inside the 3.2.2 update.upx you posted before (boot.img md5 7abc9ae7af6c05ef73bf6c08854b4786)

I don't know how to do that by hand, but it mustn't be too hard since that's what Magisk patches:

10-30-2022, 11:33 AM	#3
csdvrx Enthusiast Posts: 25 Karma: 10 Join Date: May 2022 Device: kindle HD8 onyx	After reading your message, I tried: BOOX:/ $ settings put system switch_key 1 It did nothing to help keymapper, so I reverted that with: BOOX:/ $ settings put system switch_key null However, the next one is more interesting: BOOX:/ $ settings put global key_custom_side_key_short_press_enable 1 It stops the keys from doing volume, while still making them uncatchable by keymapper. So whatever it does, it seems to do it in the right place! Would you know what it influences? I'd like to disable that. You mention: Here's a simplified diagram I just made of how keys work. Your side keys are lots more complicated because they are intercepted somewhere and they get turned into a string and get processed through res/raw/keypad.json (or res/raw/bt_keypad.json) in /system/framework/framework-res.apk. That causes your PgDn to work only when you release the button (instead of when pressing) because it has to wait to determine short/long press. I defeated that on my Poke3 because it drove me crazy. Super interesting as it confirms my guess about something doing a weird interpretation. You're going to have to change the keylayout. Me, I'd change the dtb too (because it's easy and just a single change to the boot.img that doesn't need to be a Magisk module). Can you please tell me what you did and how to replicate your changes? My goal is to have the side buttons each emit a key (any key!) that I can intercept with keymapper to map that to actions. Ideally, I would do the same to the power button, since the Hall sensor is sufficient to wakeup the boox, and the timeout sufficient to put it to sleep. If you need a copy of my Nova Air C boot.img, I think you already have one as it's found inside the 3.2.2 update.upx you posted before (boot.img md5 7abc9ae7af6c05ef73bf6c08854b4786) I don't know how to do that by hand, but it mustn't be too hard since that's what Magisk patches: