anisse / bepo-android Goto Github PK

Shortcuts stays mapped to qwerty.
Is there a way to make them work or are they tied to the keycodes?
They remap correctly using azerty for example, so I believe it's doable.

Thanks for the awesome work by the way!

This application is very easy to install and allows to use Bépo on Android.
Thanks for this !

It took me some time to understand the wrong behaviour for the key in the top left corner on my keyboard. This should provide "$" and "#" on a Bépo keyboard and provides "ê" in my case.

My understanding of the problem, after searching the web without finding a clear answer, is that Samsung remaps two keys of « small » keyboards that do not have the "<>" key. For such keyboards the bottom left and the top left keys are swapped. These are respectively "²" and "<>" keys. I imagine that the reason is to keep the most important key "<>" and to discard the less important one : "²".

Unfortunately this remapping of the keyboard makes the important key "#$" in Bépo unavailable, as it is replaced by "êÊ".

On most keyboards, the characters of this missing key are still available through Fn+ the neighbour keys, but this is not convenient, for example to type comments in programming languages.

As many small keyboards do not offer the "<>" key directly, I was wondering if it would make sense to provide a second keymap in the same app so that people experiencing the problem have a direct solution to fix it, that is select the second bépo option that would be labelled like "French (bépo alt.) to use when $# and ê are swapped."

Best regards.

Afin de faciliter la découverte, installation, mise à jour de cette application libre et open-source, elle devrait être disponible dans le magasin d'application f-droid (https://f-droid.org/).

Bonjour,
Depuis quelque temps de nombreuses combinaisons ne fonctionnent plus sur mon clavier externe.

Pour info, j'utilise un Samsung Galaxy A5 2016 (A510F), avec un clavier Logitech K480.

Voici ici un post où je parle du problème.

Je donnerai bien volontiers des infos si besoin.

I've been using bepo-android for a long time now.

In a device I recently owned though, it does not work. It is a redmi note 5 (whyred) with the last official lineage os 18 before it became unmaintained (taken from https://xdaforums.com/t/rom-r-official-lineageos-18-1-for-xiaomi-redmi-note-5-pro-whyred.4109253/page-63).

Actually, I think this is not an issue of bepo-android, because whatever content I put in /system/usr/keychars/Vendor_1e54_Product_2030.kcm (I have a TypeMatrix keyboard), the kcm content is not taken into account.

But, even though it is not an issue with bepo-android, I'm asking if you have an idea of how I could investigate this issue.

I'm sure the kcm is correctly read, because logcat tells me so

12-13 17:05:16.134 2217 2326 I EventHub: New device: id=43, fd=330, path='/dev/input/event10', name='TypeMatrix.com USB Keyboard', classes=0x80000121, configuration='', keyLayout='/system/usr/keylayout/Vendor_1e54_Product_2030.kl', keyCharacterMap='/system/usr/keychars/Vendor_1e54_Product_2030.kcm', builtinKeyboard=false,

I created the .kl and the .kcm files copying the Generic ones and tried to edit them afterwards.

I fell back adding some bindings in the .kl file, but, as you suggested a long time ago in your post (https://anisse.astier.eu/bepo-android.html), this is barely usable.

I wrote my notes in https://konubinix.eu/braindump/posts/4a6b0994-30f4-47d9-bb80-8dec73b4c0c2/?title=android_11_key_character_map_vs_keylayout_vs_whyred_to_use_bepo.