If possible, could you report what happens when:

• GBoard is installed from Aptoide Store? (You can rollback to TV version by uninstalling updates and then reinstall latest version from playstore)

As far as I know there are two, possibly three very different apps called Gboard.

(White-color) Gboard - the Google Keyboard - Minimum version Android 6.0+
(Black-color) Gboard - the Google Keyboard - Minimum version Android 8.1+
(?-color) Gboard - the Google Keyboard (Android TV) - no experience with this one...

Now, here's where it gets interesting:

D-Pad mode can NOT enter the keys or click the microphone button on the white keyboard. Only mouse mode can do that. This is true for both hardware and software mouse toggle.

The black keyboard works exactly the opposite way!

Mouse mode can NOT enter the keys or click the microphone button on the black keyboard. Only D-Pad mode can do that. Again, this is true for both hardware and software mouse toggle.

It doesn't matter which version of the white or black keyboard is installed, and it doesn't matter where you get it from (Aptoide, APKPure, APKMirror, Playstore, etc.). The result is always the same. You need a mouse pointer to use the white one. You need a D-Pad to use the black one. The black one is definitely preferable since it allows the microphone on a Mecool ATV3 IR/BT Remote to voice search within apps, but since the black one requires Android 8.1+, it doesn't help M8S Pro owners with Android 7.1 or 7.2. M8S Pro owners have to use the white Gboard and they need either an aftermarket remote with hardware mouse toggle or the bundled RemoterATV3 with mouse-toggle software in order to click that all-important microphone button.

Now, regarding the white keyboard, MATVT accuracy is way OFF on M8SPro series TV boxes with Android 7.x, but spot ON (as far as I remember) on the Tanix TX6-p with Android 9. The Fluxii app couldn't click anything with accuracy on the TX6-p.

• Is Fluxii mouse toggle able to move over the status bar? If so, I can be certain that it's possible to do with software without root privileges and try to investigate more on this.

Neither MATVT nor Fluxii could click the Status Bar on the Tanix TX6-p. MATVT's pointer slid underneath. Fluxii's pointer stopped at border. Fluxii's pointer could not enter it.

• Does the Fluxii mouse pointer also face issues with drawing over overlays? If not, I believe there's some hope to improve this behavior as well.

It varies. When testing on the H96Max RK3318 TV Box with Android 9, neither Fluxii v1.05, nor MATVT v1.03 could click the activation buttons of either of the two screen recorders installed.

But when testing on the Tanix TX6-p TV box, also with Android 9, MATVT had no problem clicking the activation buttons with perfect pointer accuracy. I don't remember whether Fluxii could click also them on that box. Fluxii's pointer accuracy was so far OFF that it was very frustrating to use (same frustrating experience as when using MATVT on Mecool boxes with Android 7.x).

• Do you also face issues in clicking on overlays on any of your devices? In the first video I couldn't understand if the overlay clicks were not registering.

That's because of the pointer accuracy problem occurring on the Mecool M8S Pro. In that video I would be clicking (repeatedly) right on top of a key located on the upper row of the keyboard but instead of registering on the key, the clicks registered 3/4" up and to the left, into the black area above the keyboard - so nothing happened. Might have been more obvious if I'd thought to turn on pointer location in developer options...

Uh oh!

MATVT v1.0.3 issues #8

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions