Not sure if this is a regression or not. I do not remember observing this previously, but I might have avoided this exact usecase.
On Android, if you use the onscreen keyboard then while the keyboard is open, `text` is set to an empty string and triggers the corresponding event/bindings.
In Android emulator, if you use hardware keyboard (there are those on Android), the text is set to gibberish, i.e. to the part of the text that was currently entered. Also, the in the text input the text entered from the hardware keyboard is inserted into a wrong position.
This affects both QtQuick TextField and QtQuick.Controls 2 TextInput.
Desktop works fine, iOS works fine.