-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.6.3, 6.8.3, 6.9.0
-
None
-
- A TCL running Android TV OS 11
- A Hisense running Android TV OS 10
- A FireTV 4K (2nd gen) stick running FireOS 8 (based on Android 11)
Tested with 6.6.3, 6.8.3, 6.9.0. Android API lev 34
-
-
6de8ce2af (dev), eb3291f32 (6.9), 622bb6c65 (tqtc/lts-6.8), a0b53b5b5 (tqtc/lts-6.5)
-
2025wk16s1QtforAndroid, 2025wk18s1QtforAndroid, 2025wk20s1QtforAndroid, 2025wk22s1-2QtforAndroid
On Android TV with a remote, the system keyboard and the input field behave erratically and are not in sync, corrupting input. Using the following:
Window {
width: 640
height: 480
visible: true
Column {
width: 400
anchors.centerIn: parent
TextInput {
id: input
height: 40
width: 300
text: "Input field"
color: "black"
focus: true
}
Text {
text: "Value: " + input.text
font.bold: true
}
}
}
On all other platforms, including mobile with a pop-up keyboard, this responds as expected and the matching output field stays in sync. However on TVs, if you simply key in an 'x', then the input is corrupted with a copy of some of it's existing text appended. If you start hitting backspace, you can erase the 'extra' content and eventually it will again append some of the remaining text. Basically it's very broken.
Also, on all other platforms the display field matches the input field per-keystroke. The TV system keyboard events aren't processed per keystroke, and you don't know what you'll get until you finish.
Tested on Google TV Android 10 & 11. FireOS has a variant of this issue as well. Qt 6.6.3 also has this issue though with slightly different behavior.
- is required for
-
QTBUG-129315 Google TV support
-
- Open
-