Jump to content

Sean McCreary

Members
  • Content Count

    82
  • Joined

  • Last visited

  • Days Won

    12

Sean McCreary last won the day on November 28 2021

Sean McCreary had the most liked content!

Community Reputation

210 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm hoping to improve the existing Settings app as part of the changes to support the Pro1X. An option to install a custom keymap from within Settings seems like a good idea, and I want to add support for a full custom keymap generator app in the driver. This would include a way to ask the driver what default keymaps are supported, and what keys are in each map (i.e. what is printed on each key). Since the default QWERTY map on the Pro1X will be different from the Pro1, the standard keyboard layout names aren't sufficient specify the correct 'default' keymap.
  2. After a very long delay, this feature has finally been merged in LineageOS 18.1. Beginning with tomorrow's build there will be a new option in Settings to make 'fn_r' (the right-hand diagonal yellow arrow key) send ralt/AltGr. This will enable full Windows-style task switching behavior, as well as assist entering accented characters when typing languages other than English. Enabling this feature will disable the use of this key to enter the yellow glyphs printed on each key, but all of them can be generated by chording with 'shift' instead, with the exception of '/' and '?'. Since these two ke
  3. We're really glad it helps :-)
  4. This has very obvious security implications, however. If you do this, you should be aware you are disabling some of the malware protection Google has built into Android. As an alternative, you might consider including gapps inside your custom OS image, like the OEMs do. For more details on how to do this, see: https://github.com/opengapps/aosp_build
  5. Yes, that is what I meant. FWIW, meta+A doesn't appear in the list shown by Trebuchet, so perhaps there is missing code somewhere in the framework.
  6. This list of shortcuts is scrollable, even though the UI doesn't indicate it. The full list has 14 entries by default. The app must register properly for the shortcut to work. For example, K9 never used to work with the meta+E shortcut, but after the recent UI redesign it now does.
  7. Right now you will need to use 'adb' to install the custom keymap, and there isn't any app to help you create the map 😕 @Slion made this nifty QWERTY keyboard image with each key labelled with the 'key number' in yellow: The manual process is to choose which key you want to remap, and to look up the keycode you want it to generate in this list: https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h You will need to convert the keycodes from decimal to hexadecimal if they don't begin with '0x'. The custom keymap is a file with lines contain
  8. For those of you who are self-building, I thought I should provide some info about where to find the monthly ASB patches. Google is currently backporting security patches to all releases since Oreo (Android 8.1), and there is a simple way to cherry-pick these patches from the AOSP source tree. You'll need to have synced the full tree first, following the instructions at https://source.android.com/setup/build/downloading tl;dr repo init -u https://android.googlesource.com/platform/manifest -b master repo sync Once you have the full tree, you can easily display the patches inclu
  9. Also, https://play.google.com/store/apps/details?id=flar2.homebutton says: That may trigger the keymap bug that Google introduced in Android 11
  10. Android uses 'meta' for the built-in keyboard shortcuts, such as meta+B for the web browser, meta+E for the email app, meta+enter to switch back to the launcher (i.e. 'HOME'), and meta+backspace for 'BACK'. This list of shortcuts is extensible, but I don't think the interface is currently exposed in any system app. By default, the 'F logo' key generates KEY_META in LineageOS, enabling these shortcuts. You can display a list of the currently defined shortcuts with meta+/, although this is unfortunately a three-key chord on the Pro1 which makes it rather difficult to type. 😕 However, pressing b
  11. Yes, there is still a problem to be solved, it just can't be solved by changing qwertz_fn_keys[] in the keyboard driver. @VaZso's summary is quite correct, that we will most likely need additional language-specific custom keymaps to make this work properly. We probably also need the ability to remap the six 'modifier' keys with dedicated GPIO lines (shift, ctrl, fn_l, F logo, alt, and fn_r), and this is not possible with the current custom keymap feature. However, we are making good progress towards adding support for that.
  12. "Oops". I have opened a change with this keymap fix at https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/315195 I think the problem is that none of us actually have a QWERTZ layout Pro1, so the keymap may not have been well tested 😞 I can revise that change with any other mapping errors you find. I have verified that each key generates the glyph matching the printed keycap for QWERTZ variant Pro1 devices, as long as in 'Settings -> System -> Languages & Input -> Physical keyboard' *both* 'Advanced settings -> Physical layout
  13. FYI, the DeviceSettings UI fixes will be in tonight's official build. If there is any problem applying the custom keymap, the user will see a 'toast' error notification and the custom keymap will be toggled back off again. This resolves the problem that there was no feedback when things go wrong. To test, you can use any keymap with a syntax error. I have been using this one for testing: 70:0000:0000 Since there's no key 70, this generates EINVAL which triggers the failure notification and modified UI behavior. I'm sorry this problem wasn't noticed before causing VaZso so much f
  14. Now that custom keymaps are working, you can remap the 'up arrow' key to '/', with Android handling shift+'/' -> '?' with the following: 04:0035:0067 I chose to remap Fn+'/' to 'up arrow' so you can still use that, but it overwrites the default keycode of 'page up'. That's the '0067' part in the string above, where 'page up' would be '0068'
  15. These two changes have been merged, and are in the 20210906 build for Pro1. If you have any trouble using a custom keymap, please open a new bug report following the instructions here: https://wiki.lineageos.org/how-to/bugreport
×
×
  • Create New...

Important Information

Terms