Leaderboard

New to me too. 🙂 Let us tag @Elysia to see if she can find a way to make stuff like this more visible. If no smarter solution found, a pinned post with links to stuff like this might do the trick. Maybe the general header on https://www.fxtec.com/ could be added to the community too? Perhaps even with something smart like the 'Stars' in the community, to indicate if the other 'tabs' have content the logged in user have not (yet) seen?

I've done OTA update yesterday, no problems at all.

I agree that it sounds like a software priority issue. But rather than lack of priority I would guess something else having too high priority thus interfering with the keyboard operation, as not everyone reports it. But could still be a system isssue, where some other system stuff gets activated by some actions or apps not all use or use the same way. Starting with the ones power consumption points at as posssible culprits, I would try to stop (or even deactive/uninstall) stuff and see if whatever triggers the phenomenon can be narrowed down. Ultimately trying a factory reset, and t

Fixed it! Thanks @_DW_ for pointing to Google's USB driver. It needs to be installed, however you also need to modify the driver INF file so that it lists Pro1 as compatible. Since you modify the INF you also need to have Windows setup in test mode so that you can install unsigned driver. Thankfully I had that enabled already as I've been working on some Windows driver implementation lately. You need to add the following lines to the INF file [Google.NTamd64] section (assuming you are running Windows 64 bits): ;F(x)tec Pro1 %SingleAdbInterface% = USB_Install, USB\VI