Implementation of Gyro mouse for Android app

[Albert Vaca Cintora]

It seems like a good idea to me. It robably feels more natural to use than
the emulated touchpad we have. And we do something like that already in the
Presenter plugin
<https://invent.kde.org/network/kdeconnect-android/-/blob/master/src/org/kde/kdeconnect/Plugins/PresenterPlugin/PresenterActivity.java#L46-56>
.

One obvious challenge is the precision. I haven't tested the linked
implementations but one does say in the description it is wobbly. Desktop
UIs have small elements.

Another challenge is knowing where the origin/zero is. On the Presenter
plugin we solved it by resetting the origin every time the cursor is shown
(since there we hide the cursor when not in use). Maybe something like this
would work for the Remote Input plugin? Although showing/resetting the
cursor when tapping the screen conflicts with clicking when tapping which
is probably what one wants in the Remote Input plugin.

On Mon, Dec 12, 2022 at 11:02 PM Philip Cohn-Cort <cliabhach at gmail.com>
wrote:

> Hi all,
>
> I noticed that we have three open MRs ([229], [285], [302]) to address
> the same new feature: the ability to use the Gyroscope and
> Accelerometer of an Android device as a remote input method.
>
> It would be great to get this feature added to the codebase, so I
> wanted to start a discussion here about the best approach, and to
> decide on the implementation details.
>
> ~Philip Cohn-Cort
>
> 229:
> https://invent.kde.org/network/kdeconnect-android/-/merge_requests/229
> 285:
> https://invent.kde.org/network/kdeconnect-android/-/merge_requests/285
> 302:
> https://invent.kde.org/network/kdeconnect-android/-/merge_requests/302
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20221213/d43947a5/attachment.htm>