| Summary: | Feature request: allow KDE Connect to keep phone unlocked | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | Daniel Duris <kdebugs> |
| Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | REOPENED --- | ||
| Severity: | wishlist | CC: | mirh, nicolas.fella |
| Priority: | NOR | ||
| Version First Reported In: | 1.5 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Daniel Duris
2017-11-28 12:39:19 UTC
AFAIK smart (un)lock is actually a GMS feature, which long story short means it's nothing available to outside programs. An idea could still be to present the user (both on the phone and desktop) with the systems respective interfaces to securely pair devices. And then you should be good to go with that. But of course it wouldn't work without gapps. We could rely on xposed, but I guess that kind of defeat the "easiness of access"... And I'm also told then, tasker + secure settings used to provide similar functions (via device administrator features?), but I dunno personally. Kdeconnect could even just offer a IsConnected intent for automation apps eventually. Hard to decide. As mirh said, we can't use the API for that. Unless Google changes it's policy regarding that we can't do it Sorry That's closed (invalid/wontfix) if any. OTOH, nothing of what I said means that this is infeasible. You could do through one of the (plenty of) alternatives I hinted. Even just sending an intent (whatever the right one is) to open the corresponding google-provided utility could be *something* Anddd.. Plot twist https://nelenkov.blogspot.com/2014/12/dissecting-lollipops-smart-lock.html The api to do so is undocumented, but there should be nothing preventing anybody from making their own *trust agent*. |