Hi
Is there any xposed module, which would let me modify the list that is being shown upon long clicking the tasks in Recents screen? By default, those are:
1) Remove from list
2) App info
I'd like to remove the #1, but most importantly add to it "Uninstall" option and also "Clear data" option, that are available from "App info" screen of an app.
Anybody willing to help me out and point me to a module which allows it (if there is none, and someone searched for it, I'd appriciate info like that also)
Lucas
If anyone knows of any way to achieve it, please respond.
Lucas
Hallo everyone,
i have looked over all the threads here but did not find any solution.
My question is: Since SecureSettings (plugin) seems to be not developed anymore i need a new way to completely disable keyguard with Takser and ofc. reset to keyguard it was before.
Example: currenty i have a pattern to unlock. What i want to do: Profil "App X starting" -> Start-Task: completely disable keyguard (no "swipe to unlock", no pattern, no pin, nothing: tapping on power button => screen on with current running app); -> Exit-Task: restore pattern (with the pattern i was using before ofc)
Does any1 know any way how to do this? Currently i am running CM13 Snapshot (Android 6.0.1) on my GT-I9505.
thanks for any helpful answer
You can do that with Secure Settings, or the new AutoTools plugin
CrashOverride93 said:
You can do that with Secure Settings, or the new AutoTools plugin
Click to expand...
Click to collapse
SecureSettings disableing does not work on Android 6 (not only on my device). Thats why i started this thread. But thanks for the hint with AutoTools, i will try
did it work with autotools?
if it did, can u share the howto?
ty
liatgme said:
did it work with autotools?
if it did, can u share the howto?
ty
Click to expand...
Click to collapse
No, it did not (at least not for me), i did not even find the "disable keyguard" option like the SecureSettings Pluig-in had it
Still looking for a way to completely disable keyguard on Android 6 (CM13). Not even with my Smartwatch and "Smart Lock" i can REALY disable keyguard, i still have to swipe the Lock-Icon after reaktivating my phone
you can use secure settings on Lollipop and also on MM
try this with Terminal emulator:
https://dammit.nl/p/962
alegend1979 said:
you can use secure settings on Lollipop and also on MM
try this with Terminal emulator:
https://dammit.nl/p/962
Click to expand...
Click to collapse
Thanks, but i already knew this. The problem is not, secure settings does not find su binary. The problem is, secure settings -> disable keyguard is not working on LP&MM.
I am running Android 6.0.1... I use the Tasker plugin TouchTask (in Google Play) to disable the keyguard. It works perfect for me.
---------- Post added at 10:32 PM ---------- Previous post was at 09:58 PM ----------
I use a tasker plug in called TouchTask from Google Play. It works perfect for me on Marshmallow. I used the plugin to temporary disable the keyguard in order to allow voice commands when driving.
135Shadowsoul said:
Thanks, but i already knew this. The problem is not, secure settings does not find su binary. The problem is, secure settings -> disable keyguard is not working on LP&MM.
Click to expand...
Click to collapse
hi, this is weird!
Maybe I misunderstood something here, but I'm running MM, and Secure setting's disable keyguard runs fine here. I use it to turn off pin keyguard when at home, and turn it back on, with preset pin, when I'm out.
I'm running Tasker with Secure setting on 6.0.1. Also, Secure setting is enabled in Xposed, if it matters.
I don't see any problem so far...
p.s. I just saw another plugin from the same developer, it is called SecureTask, it claims to be able to clear/set pin, password too. Maybe a good solution to finally replace the dated Secure setting?
alienyd said:
hi, this is weird!
Maybe I misunderstood something here, but I'm running MM, and Secure setting's disable keyguard runs fine here. I use it to turn off pin keyguard when at home, and turn it back on, with preset pin, when I'm out.
I'm running Tasker with Secure setting on 6.0.1. Also, Secure setting is enabled in Xposed, if it matters.
I don't see any problem so far...
p.s. I just saw another plugin from the same developer, it is called SecureTask, it claims to be able to clear/set pin, password too. Maybe a good solution to finally replace the dated Secure setting?
Click to expand...
Click to collapse
Can you provide a link to this Secure Task plugin? Thanks
GrippingSphere said:
Can you provide a link to this Secure Task plugin? Thanks
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.balda.securetask
there you go, but I haven't tried this out, just saw that it claims to be able to do the job.
trukero said:
I am running Android 6.0.1... I use the Tasker plugin TouchTask (in Google Play) to disable the keyguard. It works perfect for me.
---------- Post added at 10:32 PM ---------- Previous post was at 09:58 PM ----------
I use a tasker plug in called TouchTask from Google Play. It works perfect for me on Marshmallow. I used the plugin to temporary disable the keyguard in order to allow voice commands when driving.
Click to expand...
Click to collapse
Can you share how you did this?
thanks for all the reply. Unfortunately nothing did work for me the way i need it
135Shadowsoul said:
thanks for all the reply. Unfortunately nothing did work for me the way i need it
Click to expand...
Click to collapse
how exactly do you want it to work?
alienyd said:
how exactly do you want it to work?
Click to expand...
Click to collapse
Like mentioned in my OP (and how it worked on 4.4.4 (CM11):
Profil "App X" => start task: disable keyguard => end task: enable keyguard
i am using unlock pattern usually. what i want is, while "App X" is active/running, keyguard will be set to nothing (not even swipe to unlock!). pressing power (or home button) on my Samsung Galaxy S4 (GT-I9505), wich has no fingerprint reader, returns me from black screen (screen off) to the running "App X", i was before pressing power button to screen off. If i stop "App X" the keyguard should be re-set to the unlock pattern.
The SecureSettings plugin did this job on android 4.4.4, but not on 6.0.1 for me
135Shadowsoul said:
Like mentioned in my OP (and how it worked on 4.4.4 (CM11):
Profil "App X" => start task: disable keyguard => end task: enable keyguard
i am using unlock pattern usually. what i want is, while "App X" is active/running, keyguard will be set to nothing (not even swipe to unlock!). pressing power (or home button) on my Samsung Galaxy S4 (GT-I9505), wich has no fingerprint reader, returns me from black screen (screen off) to the running "App X", i was before pressing power button to screen off. If i stop "App X" the keyguard should be re-set to the unlock pattern.
The SecureSettings plugin did this job on android 4.4.4, but not on 6.0.1 for me
Click to expand...
Click to collapse
I would recommend Xposed module App Settings, allow your app to show on lockscreen.
alienyd said:
I would recommend Xposed module App Settings, allow your app to show on lockscreen.
Click to expand...
Click to collapse
but xposed sometimes hard to hide with suhide or rootswitch
135Shadowsoul said:
but xposed sometimes hard to hide with suhide or rootswitch
Click to expand...
Click to collapse
there are, again, some modules just to do the hiding:laugh:
dorsetqpr said:
Can you share how you did this?
Click to expand...
Click to collapse
The task I use is the follwoing:
A1 Secure Settings, "screen & keyboard Lights on 4 s"
A2 Screen Unlock "Using the Plug I have mentioned"
A3, what ever else you want to do with Tasker
Please keep in mind that previously, I have disable the PIN using Tasker and Secure Settings when my cell phone is connected to my car's bluetooth
Keyguard is disabled/not an option in Secure Setting even I enabled legacy features. Did anyone figure it out how to disable keyguard on Marshmallow?
I'm not real keen on rooting my Note8 just yet but the only way I know how to change the IME with the Spen is with tasker, Secure settings and root access. Is there a way to get around needing root access to set the IME with secure settings? Orban alternative method? Thanks
So I finally figured out how to do this. It requires AutoTools (you also need to give it permission to write secure settings via adb). I'm sure you can configure this in Tasker but since I use Macrodroid, that's what I used.
Configure it to trigger based on an intent, com.samsung.pen.INSERT to be exact. Now in Macrodroid I set this up as 2 macros. For the removal I had it trigger on that intent with the extra of penInsert and a value of false. That means the pen was removed, the the reverse for when it was inserted.
It's the same intent, com.samsung.pen.INSERT and extra of penInsert but with a value of true. Then for each macro I used the AutoTools Secure Settings option then under services it lists input method.
You can then select an input method for each macro, one for when the pen is removed (like Google handwriting) and then when it's reinserted have it swap back to a normal keyboard.
[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.