doc:appunti:android:osmand_remote_controller
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
doc:appunti:android:osmand_remote_controller [2020/02/04 10:38] – created niccolo | doc:appunti:android:osmand_remote_controller [2020/02/24 16:35] (current) – [Remapping the controller keys (root required)] niccolo | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Using OsmAnd with a Remote Controller ====== | ====== Using OsmAnd with a Remote Controller ====== | ||
- | [{{.:osmadn: | + | {{.:osmand: |
I'm an early joiner of the **[[https:// | I'm an early joiner of the **[[https:// | ||
Line 8: | Line 8: | ||
===== The Mocute Universal Wireless Remote Controller ===== | ===== The Mocute Universal Wireless Remote Controller ===== | ||
- | [{{ .:osmadn: | + | [{{ .:osmand: |
It is a low-cost (5-10 euros) **Bluetooth** device, sold under different brands. At present (Jan 2020) you can find it on **Amazon** or **Aliexpress.com** under the generic terms //Android gamepad Bluetooth controller// | It is a low-cost (5-10 euros) **Bluetooth** device, sold under different brands. At present (Jan 2020) you can find it on **Amazon** or **Aliexpress.com** under the generic terms //Android gamepad Bluetooth controller// | ||
Line 62: | Line 62: | ||
The Mocute-032 controller has a little slide switch with two positions: **GAME** and **KEY**. Each mode generates different **ScanCodes** for the four buttons. **The joystick operates differently**: | The Mocute-032 controller has a little slide switch with two positions: **GAME** and **KEY**. Each mode generates different **ScanCodes** for the four buttons. **The joystick operates differently**: | ||
- | [{{.:osmadn: | + | [{{.:osmand: |
==== The joystick in GAME mode ==== | ==== The joystick in GAME mode ==== | ||
Line 104: | Line 104: | ||
In theory - to remap the functions of our controller - it should be possible to provide a **specific keylayout file** for just this controller: Android' | In theory - to remap the functions of our controller - it should be possible to provide a **specific keylayout file** for just this controller: Android' | ||
- | So we have to change the **Generic.kl** file, redefining some ScanCodes and axis (the rest of the file must remain untouched): | + | So we have to change the **/ |
< | < | ||
- | key 305 MINUS | + | key 304 |
- | key 307 PLUS | + | key 305 |
+ | key 307 PLUS | ||
+ | key 308 PLUS | ||
axis 0x00 Y | axis 0x00 Y | ||
axis 0x01 invert X | axis 0x01 invert X | ||
</ | </ | ||
- | This change have the side effect to remap all the external | + | **NOTICE**: I have redefined scancodes **304** and **308** as **duplicates** of 305 and 307. This is because the default action for scancode 304 was **BUTTON_A**, |
+ | |||
+ | This change | ||
===== Key Mapping Test ===== | ===== Key Mapping Test ===== | ||
Line 124: | Line 128: | ||
===== Other remote controllers ===== | ===== Other remote controllers ===== | ||
- | * **[[https:// | + | * **[[https:// |
* **[[https:// | * **[[https:// | ||
doc/appunti/android/osmand_remote_controller.1580809086.txt.gz · Last modified: 2020/02/04 10:38 by niccolo