Revision history [back]

In Android messaging apps (for example Signal or Conversations), the Sailfish keyboard overlays the field for text input. This only appears in portrait-orientation. The input field doesn't swipe up with the keyboard like in landscape-oriantation. Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

In Android messaging apps (for example Signal or Conversations), the Sailfish keyboard overlays the field for text input. This only appears in portrait-orientation. The input field doesn't swipe up with the keyboard like in landscape-oriantation. Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Description
In Android apps with a text input field at the bottom (for example messaging apps (for example like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays the field for text input. This only appears happens in portrait-orientation. portrait orientation. The input field doesn't swipe up with move up, when it is selected and the keyboard like vKBD appears, in landscape-oriantation. contrast landscape oriantation.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays the field for text input. This only happens in portrait orientation. The input field doesn't move up, when it is selected and the vKBD appears, in contrast landscape oriantation.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to an Android app shall always exclude the screen area occupied by the vKBD when it is active, as it is already the case i in landscape orientation.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays the field for text input. This only happens in portrait orientation. The input field doesn't move up, when it is selected and the vKBD appears, in contrast landscape oriantation.hence one cannot see the resultnof one's own typing.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to an Android app shall always exclude the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays the field for text input. This only happens in portrait orientation. The input field doesn't move up, when it is selected and the vKBD appears, hence one cannot see the resultnof result of one's own typing.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to an Android app shall always exclude the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays the this field for text input. This only happens in portrait orientation. The input field doesn't move up, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to an Android app shall always exclude the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field doesn't move up, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to an Android app shall always exclude the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field doesn't move up, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to an Android app shall always exclude the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Workaround
Use the affected Android apps in landscape orientation until this issue is fixed.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field doesn't move up, is not moved up far enough, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to an Android app shall always exclude the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Workaround
Use the affected Android apps in landscape orientation until this issue is fixed.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field is not moved up far enough, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to an Android app shall always completely exclude the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Workaround
Use the affected Android apps in landscape orientation until this issue is fixed.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field is not moved up far enough, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.typing.
Side note: The affected Android apps appear to reposition their (bottom) input field when the vKBD comes, but at incorrect coordinates when in portrait orientation.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
The screen area provided to A (bottom) text input field of an Android app shall always completely exclude visible on top of the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Workaround
Use the affected Android apps in landscape orientation until this issue is fixed.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field is not moved up far enough, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.
typing.

Side note: The affected Android apps appear to reposition their (bottom) input field when the vKBD comes, but at incorrect coordinates when in portrait orientation.

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
A (bottom) text input field of an Android app shall always be completely visible on top of the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Workaround
Use the affected Android apps in landscape orientation until this issue is fixed.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field is not moved up far enough, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Side note: The affected Android apps appear to reposition their (bottom) input field when the vKBD comes, comes up, but at incorrect coordinates when in portrait orientation.orientation (maybe AlienDalvik provides incorrect coordinates to them?).

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1

Expected behaviour
A (bottom) text input field of an Android app shall always be completely visible on top of the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Workaround
Use the affected Android apps in landscape orientation until this issue is fixed.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field is not moved up far enough, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Side note: The affected Android apps appear to reposition their (bottom) input field when the vKBD comes up, but at incorrect coordinates when in portrait orientation (maybe AlienDalvik provides incorrect coordinates to them?).

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.13.2.1
Edit: ... and AlienDalvik Control 9.1.3.

Expected behaviour
A (bottom) text input field of an Android app shall always be completely visible on top of the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

WorkaroundWorkarounds
* Use the affected Android apps in landscape orientation until this issue is fixed.fixed. * Tap on Settings -> AlienDalvik Control -> Navigation bar: Show and live with the navigation bar for now.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field is not moved up far enough, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Side note: The affected Android apps appear to reposition their (bottom) input field when the vKBD comes up, but at incorrect coordinates when in portrait orientation (maybe AlienDalvik provides incorrect coordinates to them?).

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1 (i.e., the current AOSP8- and AOSP4.4-based AlienDalvik versions).
Edit: ... and AlienDalvik Control 9.1.3.

Expected behaviour
A (bottom) text input field of an Android app shall always be completely visible on top of the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Workarounds
* Use the affected Android apps in landscape orientation until this issue is fixed. * Tap on Settings -> AlienDalvik Control -> Navigation bar: Show and live with the navigation bar for now.

Description
In Android apps with a text input field at the bottom (for example messaging apps like Signal or Conversations), the Sailfish virtual keyboard (vKBD) overlays this field for text input. This only happens in portrait orientation. The input field is not moved up far enough, when it is selected and the vKBD appears, hence one cannot see the result of one's own typing.

Side note: The affected Android apps appear to reposition their (bottom) input field when the vKBD comes up, but at incorrect coordinates when in portrait orientation (maybe AlienDalvik provides incorrect coordinates to them?).

Tested with an Xperia 10 and Xperia X, both @SFOS 3.2.1 (i.e., the current AOSP8- and AOSP4.4-based AlienDalvik versions).
Edit: ... and AlienDalvik Control 9.1.3.

Expected behaviour
A (bottom) text input field of an Android app shall always be completely visible on top of the screen area occupied by the vKBD when it is active, as it is already the case in landscape orientation.

Workarounds
*

• Use the affected Android apps in landscape orientation until this issue is fixed. * fixed.
• Tap on Settings -> AlienDalvik Control -> Navigation bar: Show and live with the navigation bar for now.

P.S.
So ultimately this seems to be an issue caused by AlienDalvik Control, not by AlienDalvik.