[Nova Air] Anyway to remap the magnetic case page from vol up/down => page up/down?

[Renate]

Nah, it wasn't in KCB. It was in services.jar, also on my copy. It's in com.android.server.accessibility.MotionEventInject or

It looks like the buttons fake a gesture, which gets translated into VolUp/VolDn??? Go to your settings for Gestures and see if any of them are VolUp/VolDn. Change them to something and see if it makes a difference.

Uh-oh, I looked at mine, that could be it. It's sliding up and down the left edge.

[llinfeng]

In Gesture setting, I changed what sliding up/down at the left edge does. Still, the volume buttons on the cover ended up changing volumes when they are pressed.

[Renate]

Hmm...
Go to Android (stock) Settings > Accessibility:

$ am start -n com.android.settings/.Settings

What does the first line say, "Volume key shortcut"? Is it gray? Can you select something?

[llinfeng]

Under Accessibility, the first line reads:

Volume key shortcut
No service selected

Indeed, I can tap on it, which prompts me to turn on "Volume key shortcut". Here are a few screenshots:
1. Screenshot 1 - Is the color for "Volume key shortcut" gray? Well, not really?
2. Screenshot 2 - These are options I see after tapping on the "Volume key shortcut" entry.

[Renate]

OMG, you've got so much stuff going on there.
I still think that those buttons are coming through the accessibilty stuff that I mentioned.
It's just too complicated to troubleshoot by remote control.

Unless you can capture a logcat...

C:\>adb logcat

and see a direct correlation between pressing a button and something spitting out I don't know how I can do any more.

[llinfeng]

Thank you for all the detailed instructions up to this point. Here are two sets of logcat outputs, stored on Dropbox:

• Output where I pressed the top button for 5 times, and then the button at the bottom for 7 times or so
• Output where I toggled the "Finger touch" icon multiple times

Then, to talk about the patterns, I am not sure what to look for exactly. Solely by how often something is logged, here is my take:

1. After pressing the buttons on the magnetic cover for Nova Air, I shall see the following event:

   01-18 16:56:28.193  1286  2707 D MediaSessionService: dispatchVolumeKeyEvent, pkg=com.android.settings, opPkg=com.android.settings, pid=7509, uid=1000, asSystem=true, event=KeyEvent { action=ACTION_UP, keyCode=KEYCODE_VOLUME_UP, scanCode=0, metaState=0, flags=0x0, repeatCount=0, eventTime=2335593, downTime=2335593, deviceId=-2023406815, source=0x12345678, displayId=-1 }, stream=-2147483648, musicOnly=false

2. When I toggle the "Finger Touch" function, I found the following patterns:
   

   01-18 12:23:59.437  1436  1436 I TouchInteractionService: onReceive Intent { act=onyx.action.DO_NOT_INTERCEPT_GESTURE flg=0x1000010 }   flags 0
   
   01-18 16:54:08.631  1436  1436 W TouchInteractionService: Intercept gesture TP disable

How to make use of these things? As a bit of a sidenote, can I assign a dedicated key to disable/enable "Finger Touch" by editing /system/usr/keylayout?

[Renate]

I may have it (the side switches). Do this:

$ settings put system switch_key 1

[llinfeng]

Sorry, what to expect after running the following in abd shell?

NovaAir:/ $ settings put system switch_key 1
NovaAir:/ $

Both buttons on the cover are still working as volume rockers.

[Renate]

Hmm... That's interesting. That settings does affect a bit of code that decides whether "pageVolUp" gets mapped to PgUp or VolUp. I guess that it was already resolved or it doesn't go through there.

[pazos]

Originally Posted by llinfeng

[*] When I toggle the "Finger Touch" function, I found the following patterns:

01-18 12:23:59.437  1436  1436 I TouchInteractionService: onReceive Intent { act=onyx.action.DO_NOT_INTERCEPT_GESTURE flg=0x1000010 }   flags 0

01-18 16:54:08.631  1436  1436 W TouchInteractionService: Intercept gesture TP disable

can I assign a dedicated key to disable/enable "Finger Touch" by editing /system/usr/keylayout?

Nope.

When you click the "finger touch" quick pane an intent is generated, as you can see in logcat.

You can use an app that uses the accesibility framework, catches a defined key press and emits the same intent you see on your log. That's it "onyx.action.DO_NOT_INTERCEPT_GESTURE"

You need to know if the flags change based on current state (enabled/disabled) or they are the same on both and the service that catches the intent just flips current state. You can do that pressing the "finger touch" thingy a few times and watching at the log. Do you see the same flags?.

An example of an app that uses the accesibility framework to map keys to other things is https://github.com/sds100/KeyMapper. They have wonderful docs available following the links in the link

[llinfeng]

Hi pazos,

Thanks for taking a look at the previous posts and suggesting KeyMapper as a working demo. Frankly speaking, I don't even know what are "flags" per the logcat content

Just to clarify what to expect - at the end of the day, to map a DPAD key to flip the "Finger Touch" setting, I should write myself a standalone Android App. And, to do so, I can refer to the implementation for KeyMapper. [Upon quickly looking into KeyMapper, it said it cannot remap buttons on DPAD ...]

RE: the patterns - I did flip it multiple times in this logfile, and those two lines are showing up sequentially as I flip the setting. Though, there are many lines between those two text markers that I don't fully understand.

[pazos]

Certain keys cannot be remapped (ie: power button). For those that can be remapped you can use the suggested app directly. Writting your own app to do the same is a billion times harder than reading the manual from one that's already implemented, documented and in good shape.

I suggested the intent based on your previous log, but there're no traces on your full log that the intent was called more than once.

Sadly these kind of things require time and some knowledge. You can try to start the intent from adb with "am" and see it the setting flips it state. There're plenty of online tutorials of how to send intents using the shell.

[llinfeng]

Thanks a lot for the pointer.

[Renate]

Try this:

$ settings put global key_custom_side_key_short_press_enable 1

And if you don't like it, put it back to zero.

I believe it will make the buttons scroll, but possibly in a screwy manner and not working like normal PgUp/PgDn.

Edit: And if you're still not happy, give me a copy of your boot.img so I can check the dtb.

[llinfeng]

Thanks for the comment that I can undo the setting by setting the thing back to 0. Unfortunately, with the suggested setting, the two buttons are not doing anything. I have only tried OneNote and Kindle.

Though, getting boot.img seems to be a bit demanding, per this post.

RE: being happy - I'm glad to learn a lot about adb, especially getting to know the correct spelling And, I don't end using the magnetic cover too much anyways. I think the OP of this thread can take over from where we are now, well, if there is a burning need to remap the two keys on the magnetic cover.

Practically, for flipping pages, I use a Bluetooth clicker. (Logitech Spotlight feels good, but only have two functional buttons. And, Boox sells a black page-turner as well.)