Love it, I would go even further to have an android interface to make it look more inconspicuous, even with fake google icons for certain apps. This would work further into the Fake OS part.
Someone with a J2 could add it to the Automagic community library, means the switch could practically do anything.
1 Like
That’s where the community library comes in. If one user figures it out he/she can share either just the trigger settings or the finished automation with every other Automagic user, making it trivial for others to set it up.
I can look into it as soon as I receive my J2 but that may take a few more weeks.
1 Like
Maybe I’m dumb, but where is that library?
I like the idea of using guest mode. How would that work? You click the button and all apps that are already running are now locked and switching to them starts them as guest account (until switch is reset and pin is entered).
This would require a global state of the window/session manager, apps starting as another user from your desktop
But what about people interested in your pin? Can they have like a secondary pin that makes use of the global state, and start as a secondary user / a decoy one. Hmm.
Other ideas
== Location ==
Disable location :mwahaha: not like our phones know where we are.
But could be used to trigger BeaconDB recording, because you have a strong GPS connection and you’re comfortably outside your home area.
== Bluetooth ==
Switch between appsupport and sailfish (the BLE scanning).
Same switch for NFC (why isn’t that already available for Appsupport??!)
== Recording ==
Really this is the thing that requires a button. Call recording, ambient recording..
If you can use the button and simply say “let me turn off notifications” that would be great.
Or directly start video recording. That would include sound, and if out of pocket, video too.
== Slide to lock ==
I wish this was a spring slider as on Nokia 808 and all Belle phones. It would be stateless, the actions being lock/unlock but if you hold it in tension for 3s it is flashlight. Can’t have this with a simple 2-state button…
== Ctrl-Alt_Fn ==
Just switch the instance of lipstick. Have 2 running all the time, with different apps. Maybe work vs nonwork, who knows.
Or instead of two lipsticks, just have one Terminal app open all the time, and be able to switch to it no matter the state of lipstick, crashed locked or not.
Sounds like the hold-your-finger could reverse the lock too, that could be a nice feature request that doesn’t need the button
Now this opens a whole different can of worms: “Switch Gestures”.
Have a, say, 5 second window in which switch toggling is recorded.
Toggle 3 times: flashlight
2 times: Silent Mode
5 times: factory reset, lock bootloader
…
2 Likes
Use Morse-code to tell the phone what you want 
3 Likes
what i would truly like it to do is absolutely prevent the phone from making noises.
not ‘silent’ mode, where media can still play or alarms can make the phone buzz.
like, safe for a funeral, no thought needed.
3 Likes
Because basically everything people would want to use it for depends on Google. No doubt it’s coming in the future because Jolla said that they could use a similar solution to the one they used for Bluetooth, but NFC on Android is used mostly for mobile payment, which is locked behind Google.
2 Likes
Not all needing NFC is behind apple/ Google.
I have Tapster keyring ( also rings etc. Available) ( uses fidesmo) .
Payment does not need phone, but startup , activating the thing to tapster and via that to bank. NFC is also needed from time to time to renew the activation. Like cards needing pincode from time to time after swiping enough. So it’s good to have a phone with NFC with..
2 Likes
This was also my first thought, even before I got the phone.
It should be possible to select one of these available switches as the action that’s triggered.
Technical details
These switches are defined in /usr/share/jolla-settings/entries/foo.json.
If a file in that folder has an entry with “type == custom” and params.type == "grid", then a toplevel switch is available.
I think these entries should be either re-used, or a new params.type == "privacyswitch" entry supported.
Then all the privacy switch daemon has to do is to somehow send the toggled() signal to the SettingsToggle QML type.
3 Likes
For being a switch for a toggle state I’m a bit disappointed that when I map it to VPN (which to be fair to Jolla, is “Enable default VPN connection” and not “Toggle VPN connection”) that upon switching the toggle to the off position, after having toggled it to on, it doesn’t then turn off the VPN. Also that I couldn’t then set it to only be allowed to turned off/on using the toggle (so no other function is able to manipulate it). Of course, it is easy enough to just remove the VPN from the top menu settings, but would have liked it to be more integrated throughout the stack.
Good start though, looking forward to seeing it improve!
5 Likes
Good catch. That is catastrophic, since it will render the Privacy switch state inconsistent with actual device state.
It should be somewhat easy to prevent in the simple case, where the switch controls a single toggle:
- Top menu toggles need an
Unavailablemode, to show the current state (on or off) in addition to making it clear that they controlled by the Privacy switch and can’t be changed. Until the visuals for theUnavailablemode are implemented, toggles could be made unresponsive to touch, leaving for the user to understand that they engaged the Privacy switch. - The internal state memory of toggles must be protected from all avenues of change, except the Privacy switch. That would include other places, e.g. Settings and DBus methods,
For the case where the Privacy switch selects an Ambiance, the Unavailable mode applies both to the set of toggles controlled by the ambiance and to any means of changing Ambiance, except for the Privacy switch.
Given Jolla’s ideas about TOH controlling the phone’s mode of operation, there is also a problem space to research, where Privacy switch actions interfere with TOH actions. My tentative suggestion:
- Let TOH define a suggested Ambiance for general use, and an enforced Ambiance when the Privacy switch is enabled.
- TOH could potentially store the definitions of these two Ambiances in its onboard memory, so that they are available only with TOH attached.
- This takes away some user freedom to define the precise meaning of the Privacy switch. Letting the user edit the settings of the suggested and enforced Ambiance would still let people have the final say.
(Edit: update my post above to reflect this.)
4 Likes
You likely will have to pass the return values into a output variable, like in the Media Status (Trigger) from the Media Player Monitor example.
Then the variable should be available in the flow and it can check/display/pass it’s value:
1 Like
One other use case for the Toggel as double tap to wake is back:
One mode (“home mode”) keeps the login valid for a long periode (no pin needed for e.g. smaller than 30 min between screen off and on), the other position enforces new pin entry after short period or after every time the screen is turned off.
6 Likes
I use the switch at the moment as VPN toggle. But to be honest at the moment I find it’s implementation a bir strange. If I can swith VPN on with the switch, I would expect that I can as well switch it of. But thar\ not the case.
Is there already a bug report about that?
privacy switch auto shutdown or auto reboot after inactivity no screen login, after 8, 16, 24 hours ?