Database Develop

[Q] Lockscreen security toggle?

I'd like to turn the lockscreen security off in areas where I feel secure doing so. When i'm out taking public transportation or any other areas with any risk, i'd like the ability to easily turn security on.
Right now i'm using Xposed Framework with GravityBox 2.6.1. I'd prefer there to be a quick settings toggle that enabled/disabled the lockscreen security but didn't see that option in GravityBox (would request it in the thread for it but it looks like I can't until I post more here?).
Does anyone else have a setup similar to what i'm trying to achieve?
"No Lock Screen" app doesn't seem to work. Currently using "Toggle Lock" which does work as a widget but the size of it is so small at 1x1 (have to resize to enlarge but ends up taking too much space). Also the problem with toggle lock is if you close the Toggle Lock app in the multi-tasking in seems to break this setup.
EDIT: Toggle Lock has issues too after awhile it still asks for unlock randomly when launching apps/notifications

I used Tasker combined with Secure Settings (both on play store) to achieve something similar. When I'm connected to my home wifi, my password is disabled. When I'm connected to no wifi or any other wifi, my password is enabled.
I know this isn't the same as having a single press to toggle the password on and off, but since you can create a tasker task to do this, I imagine it can't be that hard to use Tasker App Factory to make an app that toggles the password on and off. Then just put that app on your home screen and you should be good to go.

Thanks! I'll look into that. The toggle lock app seems to have problems.

This works for me https://play.google.com/store/apps/details?id=org.jraf.android.nolock
Sent on my Moto X

flashallthetime said:
This works for me https://play.google.com/store/apps/details?id=org.jraf.android.nolock
Sent on my Moto X
Click to expand...
Click to collapse
Thanks! I tried and it seemed to work great at first (no issues with closing the app by mistake). Then i noticed later on how the phone would be unlocked yet accessing text messages from the notification bar would request the password.
What I ended up doing was setting a shortcut for Nova launcher 'Activities' > 'Settings' > 'Unlock selection' ChooseLockGeneric. This allows me to get to that settings page quickly and directly but I have to manually set up the password each time. Works though!

Is there a way to toggle a secure lock screen?

Benzo Rom for the Nexus 6 running 5.1.1 Lollipop allows the ability to toggle a secure lock screen from the quick settings in the notification drawer. For example, from the launcher, I can pull down the notification drawer to access the quick settings panel and tap the lock screen option and it will automatically engage the lock screen even if there was a password/pattern/gesture/pin, etc. previously setup. If I tap it again, it will remove the secure lock screen.
My concern is that this feature was built into the custom ROM itself and I don't know an alternate solution to this. Is there any solution to achieve this?

MiuKing said:
Benzo Rom for the Nexus 6 running 5.1.1 Lollipop allows the ability to toggle a secure lock screen from the quick settings in the notification drawer. For example, from the launcher, I can pull down the notification drawer to access the quick settings panel and tap the lock screen option and it will automatically engage the lock screen even if there was a password/pattern/gesture/pin, etc. previously setup. If I tap it again, it will remove the secure lock screen.
My concern is that this feature was built into the custom ROM itself and I don't know an alternate solution to this. Is there any solution to achieve this?
Click to expand...
Click to collapse
I think starting in MM (6.0), Google locked down this feature in favor of the smart lock function. You can set a trusted place, trusted device (bluetooth or NFC), trusted face or unlock until it detects it's been set down (on body). More information
I think, because the intents/secure action has been removed, it's not going to be something offered as a quick tile. I'm not aware of a work around.
That said, it's possible a ROM like lineage might offer this type of functionality.

ktmom said:
I think starting in MM (6.0), Google locked down this feature in favor of the smart lock function. You can set a trusted place, trusted device (bluetooth or NFC), trusted face or unlock until it detects it's been set down (on body). More information
I think, because the intents/secure action has been removed, it's not going to be something offered as a quick tile. I'm not aware of a work around.
That said, it's possible a ROM like lineage might offer this type of functionality.
Click to expand...
Click to collapse
I am currently running Pure Nexus Android 7.1.2 and have done some extensive digging to realize that a lot of keyguard and lockscreen solutions for Nougat and Marshmallow aren't working at all.
Taskers keyguard toggle option as well as Secure Settings keyguard toggle and lock screen features are broken and not working.
Secure settings is pretty old and outdated as it's been well over 2 years since it's been updated. The only options left are Taskers AutoInput looks really painful and the only other option is SecureTasks. The thing with SecureTasks is that it's relatively new and hasn't been tested long term and the method to gain device ownership looks really sketchy.

Lollipop & Gravity Box - Two Quick Setting Tiles not being removed

Lollipop 5.10
Wiko Highwar Star (phone)
Hi guys, hope you can please steer me in the right direction. Am late to the Lollipop party (just upgraded my phone finally to LP 5.10 from KK 4.4.4), and I immediately noticed that my phone has a very bad Quick Settings tiles (the ones that display pulling down up top on the Notification Bar). By bad I mean no flashlight tile and a whole bunch of other tiles that serve me no purpose.
So I rooted the phone, installed custom bootloader, installed Xposed, all for the purpose of installing Gravity Box so to hopefully tailor my Quick Settings to my needs. But unfortunately it seems I am only half successful because I still have two tiles displaying (Smart Standby & W Mode - don't even know what they do) that I can't make disappear using Gravity Box because they are not listed under its settings for Quick Settings Tiles so to uncheck them to make them disappear. I had thought that Gravity Box would only display those tiles that I have checked in its options, but that does not seem to be the case as I have those last two system stock tiles still displaying. So help please... is there a way that I haven't figured out yet in Gravity Box to make these last two tiles disappear even though their names are not in its options to uncheck?
If not, is there a way to make all my Quick Settings Tiles disappear and then use some other Xposed module (or app) to add only the ones I want back in?
Oh I guess I should mention that this phone has no stock option, none whatsover, to alter the Quick Settings Tiles which is why I was resorted to installing Xposed.. Even tapping or long pressing the main Settings button didn't bring up any way to alter the quick settings tiles.
Cheers guys for some guidance

@andyxo, could you specify the Lollipop ROM you're using. GravityBox is designed for mostly vanilla/plain AOSP ROMs. Depending on your ROM GB may or may not be able to do all that you want as stated in the module's various threads.
Maybe copy and paste your post in the GravityBox Lollipop thread. Don't forget to mention your ROM.
http://forum.xda-developers.com/showthread.php?t=3037566
ZTE Axon 7 A2017U, Project New World 8.1.0, Multiboot, XDA Legacy

marcdw said:
@andyxo, could you specify the Lollipop ROM you're using. GravityBox is designed for mostly vanilla/plain AOSP ROMs. Depending on your ROM GB may or may not be able to do all that you want as stated in the module's various threads.
Maybe copy and paste your post in the GravityBox Lollipop thread. Don't forget to mention your ROM.
http://forum.xda-developers.com/showthread.php?t=3037566
Click to expand...
Click to collapse
Hi, thanks for your post... the ROM is the one that came with my phone (Wiko Highway Star). Ya, I figured that Gravity Box has that limitation but am hoping someone could provide an alternate solution (besides Gravity Box) to getting rid of those last two pesky stock Quick Setting tiles. Such as a different module to totally remove all Lollipop Quick Setting tiles (I don't see such an option in Gravity Box, darn!) , then I could just find an app to add in the ones I want. Or some other solution, one that I haven't thought of yet

So haven't had any luck yet in totally removing all Quick Settings from Lollipop 5.10. I found a 5.0 version of SystemUI Tuner but that didn't do it. Tried various Xposed modules for other phones with the hopes of making it work but nope....
So Lollipop has been around for a long time... am really surprised that there is no Xposed module (or at least one that I have found) that can actually remove all Quick Settings what with all the coders and modders populating the world. If even just for a plain jane Lollipop android that I could try. What am I missing here?
Edit: So it seems I solved my first world problem using an app called Custom Quick Settings. For some reason this app had exactly the two pesky stock toggles I needed to remove from my Quick Settings tiles: Slip cover removed W mode and Smartstandby removed Smart Standby (go figure). For some reason (got lucky) Custom Quick Settings had these toggles turn-off-able while Grav Box doesn't. So am using both apps at the same time because Grav Box has more options relating to Quick Settings while just using Custom Quick Settings to remove those two peskies. So far they are playing well together.... posting this just in case may help someone

Nice find @andyxo. ?
I'll keep that app in mind if I ever come across some stubborn tiles that GravityBox can't handle.
ZTE Axon 7 A2017U, Candy7 v5.2 ROM, Google free - no microG, MultiROM, XDA Legacy

How to activate/deactivate a qs tile upon screen off/on?

In android 10,a new feature called as TURN ALL SENSORS OFF is available in developer settings. It also has a qs tile.
Is there a way to automatically enable this feature upon screen off and then disable upon screen on?

The obvious answer is absolutely yes using AutoInput to emulate the touches. That can also be done with more effort using just built in Tasker actions.
However, it's possible (likely?) That there is a secure setting that controls this action. You can sort that out by comparing the secure settings before and after toggling the tile. The AutoTools secure settings action has an assistant that may help you sort this out.

ktmom said:
The obvious answer is absolutely yes using AutoInput to emulate the touches. That can also be done with more effort using just built in Tasker actions.
However, it's possible (likely?) That there is a secure setting that controls this action. You can sort that out by comparing the secure settings before and after toggling the tile. The AutoTools secure settings action has an assistant that may help you sort this out.
Click to expand...
Click to collapse
1) In android 10,there is an option to disable all sensors in developer options. So i turned it on last night, and battery drain was less than 2 % in 4 hrs, compared to 1% per hour usually, with volte and 4g data on. I would get more accurate stats later on.
There's a qs tile available to activate it.
What I want to ask is, is there a way to automatically enable it every time the screen goes off, and then disable it when screen goes on, without any user input?Either as a shortcut or as a qs tile.
2) I am afraid i don't have enough knowledge to exactly understand the steps you are telling. Do you know of a pre made recipe to execute this. I tried to search but in vain. Or if you are on android 10,maybe you can try doing what i need.
Thank you.

There are loads of tutorials available to use the AutoInput plugin.
As far as issuing the native tasker custom setting action;
Create a new task
Add a Settings -> Custom Setting action
A developer settings action is probably a global setting but you may have to explore
When you are in the configuration for the Custom Setting action, use the magnifying glass and Find to identify the setting you want. A pop-up will appear directing you to ok out of the instructions then go to the setting you want to manage, activate the setting and return to Tasker. Then hit the magnifying glass again and if the setting was identified, it will display in the pop-up where you can select it.
No offence, even if I were on A10, this can be done with a basic understanding of Tasker so I wouldn't create a project for it. If you are still unsure what to do, please take the time to work through some basic tasker tutorials to gain familiarity with the app.

ktmom said:
There are loads of tutorials available to use the AutoInput plugin.
As far as issuing the native tasker custom setting action;
Create a new task
Add a Settings -> Custom Setting action
A developer settings action is probably a global setting but you may have to explore
When you are in the configuration for the Custom Setting action, use the magnifying glass and Find to identify the setting you want. A pop-up will appear directing you to ok out of the instructions then go to the setting you want to manage, activate the setting and return to Tasker. Then hit the magnifying glass again and if the setting was identified, it will display in the pop-up where you can select it.
No offence, even if I were on A10, this can be done with a basic understanding of Tasker so I wouldn't create a project for it. If you are still unsure what to do, please take the time to work through some basic tasker tutorials to gain familiarity with the app.
Click to expand...
Click to collapse
Will follow the steps. If I encounter any issues, will reply back here.
Big thanks.

[SOLVED] Why does my phone not unlock on 47.1.A.16.20 with Xposed?

[FOR REFERENCE ONLY]
Problem solved!
The confounding variable was NOT Xposed Framework, but conena's Gesture Control app that was set up to use Immersive Mode to hide the navigation bar. And according to this post that I landed on purely by chance, if you don't exempt the Lockscreen Settings app, it causes all these problems.
Note that this problem has nothing to do with the app, it's the Immersive Mode setting to blame, on which any setting change at all will cause these same problems (to be fair, conena's app does preemptively discourage this)
Solution
Use a Substratum overlay to hide the navbar instead; do NOT use GravityBox to do that by setting navbar height to 0, or qemu.hw.mainkeys=1 in build.prop (which doesn't work, BTW). Next, backup your gesture bar data and wipe the data of the app, then restore the bar data – just don't fiddle with that Immersive Mode setting again!
Well, some explanation is in order because it wouldn't make for a great thread title:
I am running the last stock Oreo build on this G8441, which is 47.1.A.12.20, for the primary reason of being able to use rovo89's Xposed Framework because the original XPrivacy module that's vitally important to me does not run on any of the EdXposeds or LSPoseds.
Using systemless Xposed with the latest Magisk version (and older ones too, nothing changes) I find that if I were to set a lockscreen to anything other than "None" and reboot, I will have times where I simply can't see the display when pressing the power button -- but weirdly enough the touchscreen still keeps taking touch input! The only way around is to remove the lockscreen, reboot, then set your locking method and try not to have it restart for any reason.
It's quite obvious that systemless Xposed is causing this problem (Xposed can't be installed normally on this firmware version) because this problem can be reproduced even without any modules active. But I'm at a complete loss as to what's actually causing this lockscreen interference, because I've tried taking system logs with and without Xposed and there's simply nothing at all different except it taking insanely long times for the display to activate upon unlock (but the touch input working just fine for some reason?) and there's a small, dim red LED near the proximity sensor that stays stuck as long as the display is.
Please help me, I'm absolutely out of ideas -- and no, I can't upgrade to Pie, I have to stay on Oreo for the sake of the XPrivacy module.

So it seems like 47.1.A.12.75 is the last problem-free Oreo version for normal Xposed Framework, and I wouldn't mind using that, if it weren't for the fact that there doesn't seem to be any VoLTE-activating SIN file for India for it below 47.1.A.12.270. There's a 2G phaseout in progress with the largest carrier and it's only a matter of time before there'll be no fallback network and I'll have to have VoLTE at any cost.