So, I've got a fix. There's problems (unknown) round-tripping with ApkTool.
If you are using Magisk, this is safe and fairly easy. If you are modifying /system directly you might want to make a backup of that partition? I dunno. Just warning you.
Also! ADB starts late so you want to boot up normally so you have ADB. Then you can issue the command:
Which stops the Android subsystem, but you will still have ADB so you can fix whatever you screw up. When you want to try things, type "start".
As I said, the JSON files are in /system/framework/framework-res.apk
Grab a copy and pull it on your desktop.
My Poke3 has:
Code:
md5: 9b99400530a31ad55f29bc68fc417fc1
24,578,369 framework-res.apk
There's md5sum on the Onyx and whatever it's called on your desktop.
Use whatever desktop hex editor tools you have to find the ASCII string "keypad",
without unzipping the file. There should be
six eight occurences of it.
Leave the first two alone, change the last four strings. Change #5, #6, #7, #8 (I like changing the "keypad" to a "zeypad" so that I know what I've done.) That's your file. Put it in your Magisk module directory or else replace the original system/framework file.
I really like that now the page goes down when I press the button down, not when I release it. Right now, the auto-repeat is pretty fast. You can see it by holding down a letter in a text editor. If I do a typical "long press" on PgDn now I see that it goes off doing about 10 pages forward. I'll look into tempering that a bit. You could also handle that in your app to not go go on the auto-repeated DOWN but either timer or checking whether the page turning is backed up. Hmm, another project for me...*
Good luck. If you screw up, don't reboot! just stop, fix something, start.
*Edit: I added that idea to my reader. It goes fast, but stops after you let up the button (instead of staggering on for a second or two). I like it!