rigacci.org

User Tools

Site Tools

Trace:
doc:appunti:android:osmand_remote_controller

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
doc:appunti:android:osmand_remote_controller [2020/02/04 10:45] – [Other remote controllers] niccolodoc:appunti:android:osmand_remote_controller [2020/02/24 16:15] – [Remapping the controller keys (root required)] niccolo
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's instructions say to simply create a file with the name **Vendor_ffff_Product_0000.kl** (see the vendor and product read from the ''/proc/bus/input/devices'' pseudofile). Unfortunately this does not work, may be because ffff and 0000 are not valid ID values. In theory - to remap the functions of our controller - it should be possible to provide a **specific keylayout file** for just this controller: Android's instructions say to simply create a file with the name **Vendor_ffff_Product_0000.kl** (see the vendor and product read from the ''/proc/bus/input/devices'' pseudofile). Unfortunately this does not work, may be because ffff and 0000 are not valid ID values.
  
-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 **/system/usr/keylayout/Generic.kl** file, redefining some ScanCodes and axis (the rest of the file must remain untouched):
  
 <file> <file>
doc/appunti/android/osmand_remote_controller.txt · Last modified: 2020/02/24 16:35 by niccolo