Revision history [back]
 | 1 | initial version | posted 2020-04-18 03:47:38 +0200  |
Where is alien_wayland_keyboard?
Hi sailors!
I want to get my bluetooth keyboard working with AlienDalvik with the german layout (and any other layout!).
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are.
Please help!
| | 2 | No.2 Revision |
Where is alien_wayland_keyboard?
Hi sailors!
I want to get my bluetooth keyboard working with AlienDalvik with the german layout (and any other layout!).
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are.
Please help!
| | 3 | No.3 Revision |
Where is alien_wayland_keyboard?
Hi sailors!
I want to get my bluetooth keyboard working with AlienDalvik with the german layout (and any other layout!).
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are.
They seem to be in /opt/alien/system.img. How can I extract the image? I have tried:
simg2img, unyaffs and unpackbootimg. No success...
Please help!
| | 4 | No.4 Revision |
Where is alien_wayland_keyboard?
Hi sailors!
I want to get my bluetooth keyboard working with AlienDalvik with the german layout (and any other layout!).layout!). Perhaps some of you know, that the physical keyboard is stuck with US keymap for Android apps.
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are.
They seem to be somewhere in /opt/alien/system.img. How can I extract the image? I have tried:
simg2img, unyaffs and unpackbootimg. No success...
Please help!
| | 5 | No.5 Revision |
Where is alien_wayland_keyboard?
Hi sailors!
I want to get my bluetooth keyboard working with AlienDalvik with the german layout (and any other layout!). Perhaps some of you know, that the physical keyboard is stuck with US keymap for Android apps.
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are.
They 
AD menu Languages & Input devices. You can see the topic Physische Tastatur, which is the hardware keyboard.
AD menu Hardware keyboard. You see, that I have added IBM keyboards with an Android app and changed it to German (IBM), but my bluetooth keyboard still writes with US keymap
The configuration files and stuff seem to be somewhere in /opt/alien/system.img. How can I extract the image? I have tried:
tried: simg2img, unyaffs and unpackbootimg. No success...
Please help!
Next step forward: sudo unsquashfs system.img extracts the file.
Searching for alien_wayland_keyboard within these files didn't bring up any.
I can see, that there is a generic keymap within system.img in the file /system/usr/keylayout/Generic.kl and qwerty.kl. There are no keymaps in /usr/share/X11/xkb. This leads to my assumption, that AlienDalvik goes back to the generic keyboard for compatibility reasons.
So, what's the next step?
Where is this alien_wayland_keyboard? Is it some SFOS piece, that I can't find, not something from AlienDalvik?
| | 6 | No.6 Revision |
Where is alien_wayland_keyboard?
Hi sailors!
I want to get my bluetooth keyboard working with AlienDalvik with the german layout (and any other layout!). Perhaps some of you know, that the physical keyboard is stuck with US keymap for Android apps.
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are.
AD menu Languages & Input devices. You can see the topic Physische Tastatur, which is the hardware keyboard.
AD menu Hardware keyboard. You see, that I have added IBM keyboards with an Android app and changed it to German (IBM), but my bluetooth keyboard still writes with US keymap
The configuration files and stuff seem to be somewhere in /opt/alien/system.img. How can I extract the image? I have tried: simg2img, unyaffs and unpackbootimg. No success...
Next step forward: sudo unsquashfs system.img extracts the file.
Searching for alien_wayland_keyboard within these files didn't bring up any.
I can see, that there is a generic keymap within system.img in the file /system/usr/keylayout/Generic.kl and qwerty.kl. There are no keymaps in /usr/share/X11/xkb. This leads to my assumption, that AlienDalvik goes back to the generic keyboard for compatibility reasons.
So, what's the next step?
Where is this alien_wayland_keyboard? Is it some SFOS piece, that I can't find, not something from AlienDalvik?
In the meantime, I have realized, that the same behavior is happening with flatpak within the Angelfish browser. So this might be something outside of AlienDalvik, right? I am open for hints, where to follow the lead.
| | 7 | No.7 Revision |
Where is alien_wayland_keyboard?Trying to get physical keyboards to work with AlienDalvik and Flatpak
Hi sailors!
My bluetooth keyboard works perfectly with SaiflishOS, but: I want to get my physical bluetooth keyboard working to work with AlienDalvik apps and Flatpak apps with the german layout (and any other layout!). layout!) . Perhaps some of you know, that the physical keyboard is stuck with US keymap for Android apps.apps and Flatpak.
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are.are. I believe that this is the crossing, where things come together. Here are two screenshots on my way to try to find out, what is happening.
AD menu Languages & Input devices. You can see the topic Physische Tastatur, "Physische Tastatur", which is the hardware keyboard.
AD menu Hardware keyboard. You see, that I have added IBM keyboards with an Android app and changed it to German (IBM), but my bluetooth keyboard still writes with US keymap
/opt/alien/system.img. How can I extract the image? I have tried: simg2img, unyaffs and unpackbootimg. No success...
Next step forward: sudo unsquashfs system.img extracts the file.
Searching for alien_wayland_keyboard alien_wayland_keyboard within these files didn't bring up any.
I can see, that there is a generic keymap within system.img in the file /system/usr/keylayout/Generic.kl and qwerty.kl. There are no keymaps in /usr/share/X11/xkb. This leads to my assumption, that AlienDalvik goes back to the generic keyboard for compatibility reasons.
So, what's the next step?
Where is this alien_wayland_keyboard? Is it some SFOS piece, that I can't find, not something from AlienDalvik?
In the meantime, I have realized, that the same behavior is happening with flatpak within the Angelfish browser. So this might be something outside of AlienDalvik, right? Somewhere, there might be an interface to pass the information from the SFOS physical keyboard to other systems like AlienDalvik or Flatpak.
I am open for hints, where to follow the lead.
| | 8 | No.8 Revision |
Trying to get physical keyboards to work with AlienDalvik and Flatpak
Hi sailors!
My bluetooth keyboard works perfectly with SaiflishOS, but: I want to get my physical bluetooth keyboard to work with AlienDalvik apps and Flatpak apps with the german layout (and any other layout!) . Perhaps some of you know, that the physical keyboard is stuck with US keymap for Android apps and Flatpak.
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are. I believe that this is the crossing, where things come together. Here are two screenshots on my way to try to find out, what is happening.
AD menu Languages & Input devices. You can see the topic "Physische Tastatur", which is the hardware keyboard.
AD menu Hardware keyboard. You see, that I have added IBM keyboards with an Android app and changed it to German (IBM), but my bluetooth keyboard still writes with US keymap
The configuration files and stuff for AlienDalvik seem to be somewhere in /opt/alien/system.img. How can I extract the image? I have tried: simg2img, unyaffs and unpackbootimg. No success...
Next step forward: sudo unsquashfs system.img extracts the file.
Searching for alien_wayland_keyboard within these files didn't bring up any.
I can see, that there is a generic keymap within system.img in the file /system/usr/keylayout/Generic.kl and qwerty.kl. There are no keymaps in /usr/share/X11/xkb. This leads to my assumption, that AlienDalvik goes back to the generic keyboard for compatibility reasons.
So, what's the next step?
Where is this alien_wayland_keyboard? Is it some SFOS piece, that I can't find, not something from AlienDalvik?
In the meantime, I have realized, that the same behavior is happening with flatpak within the Angelfish browser. So this might be something outside of AlienDalvik, right? Somewhere, there might be an interface to pass the information from the SFOS physical keyboard to other systems like AlienDalvik or Flatpak.
Edit: 2020-04-18
https://jolla.zendesk.com/hc/en-us/articles/201440697-What-Bluetooth-profiles-does-SailfishOS-support-
HID 1.0 (Human Interface Device Profile): Allows use of HIDs with Jolla, for example keyboards and mice. SailfishOS supports the American keypad layout only.
I am open for hints, where to follow the lead.
| | 9 | No.9 Revision |
Trying to get physical keyboards to work with AlienDalvik and Flatpak
Hi sailors!
My bluetooth keyboard works perfectly with SaiflishOS, but: I want to get my physical bluetooth keyboard to work with AlienDalvik apps and Flatpak apps with the german layout (and any other layout!) . Perhaps some of you know, that the physical keyboard is stuck with US keymap for Android apps and Flatpak.
I am stuck with searching for the alien_wayland_keyboard and where its configuration files are. I believe that this is the crossing, where things come together. Here are two screenshots on my way to try to find out, what is happening.
AD menu Languages & Input devices. You can see the topic "Physische Tastatur", which is the hardware keyboard.
AD menu Hardware keyboard. You see, that I have added IBM keyboards with an Android app and changed it to German (IBM), but my bluetooth keyboard still writes with US keymap
The configuration files and stuff for AlienDalvik seem to be somewhere in /opt/alien/system.img. How can I extract the image? I have tried: simg2img, unyaffs and unpackbootimg. No success...
Next step forward: sudo unsquashfs system.img extracts the file.
Searching for alien_wayland_keyboard within these files didn't bring up any.
I can see, that there is a generic keymap within system.img in the file /system/usr/keylayout/Generic.kl and qwerty.kl. There are no keymaps in /usr/share/X11/xkb. This leads to my assumption, that AlienDalvik goes back to the generic keyboard for compatibility reasons.
So, what's the next step?
Where is this alien_wayland_keyboard? Is it some SFOS piece, that I can't find, not something from AlienDalvik?
In the meantime, I have realized, that the same behavior is happening with flatpak within the Angelfish browser. So this might be something outside of AlienDalvik, right? Somewhere, there might be an interface to pass the information from the SFOS physical keyboard to other systems like AlienDalvik or Flatpak.
Edit: 2020-04-18
https://jolla.zendesk.com/hc/en-us/articles/201440697-What-Bluetooth-profiles-does-SailfishOS-support-
HID 1.0 (Human Interface Device Profile): Allows use of HIDs with Jolla, for example keyboards and mice. SailfishOS supports the American keypad layout only.
Today, the USB Foundation standard is: HID 1.12. So, there is a lot of work to get done, my friends!
bluez is open source, so we could do some really serious work. :-) I am just a user, who digs a bit underneath. I would need some serious people to help.
I am open for hints, where to follow the lead.