[kdeconnect] [Bug 387396] Feature request: allow KDE Connect to keep phone unlocked

[mirh]

https://bugs.kde.org/show_bug.cgi?id=387396

mirh  changed:

   What|Removed |Added

 Resolution|UPSTREAM|---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #4 from mirh  ---
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*.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 387396] Feature request: allow KDE Connect to keep phone unlocked

[mirh]

https://bugs.kde.org/show_bug.cgi?id=387396

--- Comment #3 from mirh  ---
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*

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 387396] Feature request: allow KDE Connect to keep phone unlocked

[Nicolas Fella]

https://bugs.kde.org/show_bug.cgi?id=387396

Nicolas Fella  changed:

   What|Removed |Added

 CC||nicolas.fe...@gmx.de
 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Nicolas Fella  ---
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

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 387396] Feature request: allow KDE Connect to keep phone unlocked

[mirh]

https://bugs.kde.org/show_bug.cgi?id=387396

mirh  changed:

   What|Removed |Added

 CC||m...@protonmail.ch

--- Comment #1 from mirh  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.