Onyx 3.2.1 release screwed with buttons

[Renate]

I just did the 3.2.1 update on my Poke3.
Those knuckleheads mucked with the buttons.

At a low level they made all PgDn to be VolDn and all PgUp to be VolUp
(This is not a keylayout issue.)

Even:

# input keyevent 92 => 24
# input keyevent 93 => 25

Ok, tomorrow I'll look at it.

Edit: Well, I was too impatient, I wanted to read my book and not be annoyed by dumb stuff.

So, there is probably a setting to disable this (but in any case, the setting changed with the update), but because it cobbles in long press it also delays a simple push until it's released.

It's all in /system/framework/framework-res.apk -> res/raw/keypad.json

    {
      "keySet": [
        "KEYCODE_PAGE_UP"
      ],
      "shortPressAction": "switchByConf",
      "longPressAction": "KEYCODE_MENU",
      "repeat": false
    },
    {
      "keySet": [
        "KEYCODE_PAGE_DOWN"
      ],
      "shortPressAction": "switchByConf",
      "longPressAction": "fullRefreshScreen",
      "repeat": false
    },

I mentioned elsewhere how to disable this. I'll follow up tomorrow. My book is calling.

[Renate]

I had previously disabled all this long press stuff and key mapping.
I ran into problems before when I just deleted res/raw/keypad.json and res/raw/bt_keypad.json from /system/framework/framework-res.apk
The least intrusive way to disable access to these two files is to rename the filenames in the .zip (.apk) in the local header.

These numbers are from the Poke3 but other models will have stuff in approximately the same place.

C:\>findtext framework-res.apk keypad.json
00B2BCBD  res/raw/bt_keypad.json // manifests
00B2BD91     res/raw/keypad.json
01539DDE  res/raw/bt_keypad.json // zip local headers
0153A5A1     res/raw/keypad.json
016A3844  res/raw/bt_keypad.json // zip global headers
016A39E5     res/raw/keypad.json
C:\>modfile framework-res.apk 1539DDE 7a // k -> z
C:\>modfile framework-res.apk 153A5A1 7a // k -> z

(Your tools are probably named something else, but you get the idea.)

Then you'll need to put the modified file in a Magisk module.
You should probably make a module just for yourself that you can throw in odds and ends.
Making a module like this is easier than a packaged module for distribution.
Just make your own directory:

# cd /data/adb/modules
# mkdir -p MyModule/system/framework

Then you'll need to make the MyModule/module.prop file. It's nothing critical, just give your module some names. It's all documented here: https://topjohnwu.github.io/Magisk/guides.html

[mergen3107]

Why don’t you just override long presses with “Do nothing” in, for example, Button Mapper?

[Renate]

Originally Posted by mergen3107

Why don’t you just override long presses with “Do nothing” in, for example, Button Mapper?

I don't object to the actions of a long press, I object that the system holds off 1/2 a second to determine whether something is a short or long press. Also, I have no need of Button Mapper.

[mergen3107]

This time delay is also configurable in Button Mapper

[Renate]

Not if the Onyx stuff has already delayed it. Have you checked?

[mergen3107]

Ah, ok! No, I haven’t

[daldred]

You're referring to Magisk modules and stuff here.

Is this update something to avoid if using a standard Poke3 (without Magisk or anything much else installed)?

[Renate]

Originally Posted by daldred

Is this update something to avoid if using a standard Poke3?

No, the update is fine. It just seems like they changed some things that have to do with buttons. If you don't use a wired or Bluetooth keyboard or Bluetooth remote or any case buttons then this change will not affect you.

Being an optimist, I always hope that updates will be to help stability and increase performance. Therefore, if there is something that comes in that doesn't suit you it's better to just attack that than to roll back to an older version.

[Djezpur]

Renate, how did you update your rooted Poke3?

Mine is rooted with Magisk and I have tempered a bit with the files in the system/media folder.

I have tried two ways to update to 3.2.1 - (1) by retrieving the OTA-file directly and (2) by placing the update.upx on the sdcard as described at the bottom of this page: https://blog.tho.ms/hacks/2021/03/27...-note-air.html

Both times the update was being processed and decrypted, but the device always reboots back to 3.2.
Do I need to flash the original boot.img first?

[Renate]

Right now it's not really a problem if you directly modified files in /system (or /vendor) as Onyx is still putting out unconditional updates. When they become incremental (i.e. much smaller than 1 GB) is when that will change. At some point you may need to restore /system and/or /vendor to do an update.

boot.img is monolithic, so it will either get replaced or not, same for recovery.

I've actually gotten away from Magisk, but that's irrelevent.

I've been doing updates using direct download, decrypting to zip and using a USB flash drive and a custom recovery (just because I can). I've disabled too much Onyx stuff already.

[Djezpur]

Thanks for your swift reply!

So reflashing boot.img will not have any effect and custom recovery is the only way to go?

(It's not that I'm eager to update to 3.2.1, but I would like to know what the correct procedure is.)

[Renate]

No, it's certainly not the only way to go.

In regular Onyx, you can park the (still encrypted) .upx in /scard
You can navigate to some dialog for "Start update", but I forget how to get there.
You can just:

$ am start -n com.onyx.android.onyxotaservice/.OtaInfoActivity

I think.

[Djezpur]

Originally Posted by Renate

In regular Onyx, you can park the (still encrypted) .upx in /scard
You can navigate to some dialog for "Start update".

That's what I've tried to do and the file does get recognized and decrypted but when the device automatically reboots to finish the update, I see my own boot animation again and I'm still on 3.2

[Renate]

Well, that's one reason why I do stuff the way I do. I like to watch.