yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Farshid-Iran:
Good Job...

But have a problem , for relock app's must pulldown status bar and touch notification of your app till lock apps...

pls add options for relouck app when close app,..
[Xposed Framework Modules] chw9999:
Great app :)

Even though it might compromise security, could you add an option to disable locking while in home Wi-Fi net (or BT etc)? Or add a Tasker shortcut to do so?

Thanks a lot!
[Xposed Framework Modules] defim:
I think Tasker Support is better, so could many events beused. What about that: PA accept a broadcast, it contains

1) "mode" extra: protect apps, unlock forever and maybe unlock apps for the duration set in settings

2) "password" extra: In the settings could be a password defined and tasker has to add it to the broadcast. So not every app could send a broadcast.

Can you attach a logcat and logfile of Xposed?

That's not so easy, android does not "closes" apps, it "pauses" them. Eg if you hit HOME button while an app is open it is paused. Therefore is in the menu of PA an "exit" item.

You could get ~~ what you want if you set the oservation method to "create" and the unlocked time to it's minimum (its 30 atm)
[Xposed Framework Modules] badkill:
Spanish translation is complete, thanks for another great module :good:
[Xposed Framework Modules] chw9999:
Wohoo, that would be cool [emoji1]

Right now i have a tasker event to lock apps when away from home, but it's not a really save option.your method should be more reliable.

Thanks again!
[Xposed Framework Modules] ravijani:
great work.

Was looking for the same.

Thank you dev. keep it up. tipped for portal.
[Xposed Framework Modules] soesie:
I also got bootloop with s5. Got by any change a fix without restoring backup or reinstall rom?

Tried wipe dalvik cache and cache but no luck
[Xposed Framework Modules] cramu:
Nice to hear that you're going to integrate with Tasker to control app protection.

Any plans to support app grouping so we can lock/unlock groups of certain apps depending on (Tasker-)context?
[Xposed Framework Modules] badkill:
Does not work on my Galaxy S4 I9505 with Android 4.4.2 when selected an application is not saved in the list of selected applications.
[Xposed Framework Modules] defim:
I'm not sure which way, have to thing about it. But at first some bugfixes. :)

You could disable whole xposed with pushing five times a hardware key during boot. After that you have to enable it again in installer! Can you get before that a logcat and attach?

Thanks, i'll atach a translated apk late. In case you forgot: The old unlocker should still work

Please check that the folder "files" was created in /data/data/de.defim.apk.protectedapps. There should be also "cache" and something with shared-preferences. There was with another app also the case the "files" was not created, this should be done by android while installing the app. If you create it by yourself, set the same user&permissions like "de.defim.apk.protectedapps" has
[Xposed Framework Modules] Kagoshema:
bugs/suggestions

If there is no lock screen set for the phone then protected apps are impossible to open. Further if there is no lock screen set for the phone then it is also impossible to set a different locking method for protected apps and different methods that were set when the phone did have a lock screen stop working when the lock screen is removed.

So suggestion would be to make a way for your app to work even if the user has screen lock set to "None".
[Xposed Framework Modules] defim:
Thanks for reporting, i had not considered that case... Should be fixed in attached file (dont forget to reboot, the app reminds only if version code changed)

[MENTION=3967831]badkill[/MENTION]: Also translation included
[Xposed Framework Modules] Kagoshema:
Nice quick fix. I'll give it a test.

Tested:

Looks good. Minor detail; in settings under "method to unlock apps" if "Don't change" is selected then the checkbox "Use a custom patter/PIN/password" does nothing. I'll probably play around more but you've got my donation.

Also: in settings what is the difference between the "time after which a new unlocking is requested"(self explanatory) and "minimal/maximal duration of unlocking"?
[Xposed Framework Modules] Lord_Flaya:
Really nice mod. Is it possible to evolve it so that you can have protection for selected operations on the device? Demand pin for deleting SMS or whatever the user choose to protect..?
[Xposed Framework Modules] t3chwizard:
What do you mean xposed framework subforum

---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------

Asking if this works if xposed is disabled on boot is a legitimate question. There's no point in downloading and installing it if so.
[Xposed Framework Modules] karl999999:
why dont you try what i have listed. picture sharing is working fine. please try with webpage sharing from browser, as i listed.

its not threema. this bug happens only when your app is used. you can use surespot, or skype instead of threema. same bug with your app!

it seems you just dont want to see it :(
[Xposed Framework Modules] defim:
[MENTION=762956]klau1[/MENTION]:

I have no device with TouchWiz to try. You are using to unlock the android keyguard method or custom?

The current state of device-unlock is watched by some protected-(system)-bordcasts. So maybe the TouchWiz doesnt sent it? It is also possible that your device was not completely started and it was delayed a bit

>Observe the switch between protected apps and relock.

Something similar could be achieve by setting these options: observer "create" only. Then set the duration of unlock to a low value. Now for the 1st start of any app you have to enter key

Please describe it with other words, maybe its just an translation problem. You could also enable logging in the app and attach. And please add links to Play Store to the apps you wrote about so i could try.
[Xposed Framework Modules] Denebola79:
Hi i realy want to try this module but when i active and reboot the phone stay on the samsung logo without boot... The phone is a note 3. Can u explain me how to get a log

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Xposed Framework Modules] defim:
This was reported by some, and so I added the checkbox in the settings "Disable keyguard hooks". Have you tried with this set? There was not yet a report about it

If it still crashes with it set: Enable ADB on the device and connect to a PC where you run "logcat", so you could see all messages until it crashes and hopefully shows what crashes. But this way to log is a little advanced...
[Xposed Framework Modules] Denebola79:
I just tried but fail. My steps are, install protectedapps, checkbox hooks then activate and reeboot. Nothing still stuck at samsung logo ?. When i came back home i will try with adb

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Xposed Framework Modules] Droidphilev:
You would help me too. Exact the same problem but no pc :(

Thanks in advance!

It seems you are using a tablet? same here.
[Xposed Framework Modules] Denebola79:
no its the note 3
[Xposed Framework Modules] defim:
It seems Samung/TouchWitz related
[Xposed Framework Modules] stickiestring:
null
[Xposed Framework Modules] karl999999:
what is so hard to understand??

open browser and share webpage link. it does not work with protected apps.

(skype is protected by protectedapps and threema is also protected)

share webpage from browser to -> skype

share webpage from browser to -> threema
[Xposed Framework Modules] defim:
I dont use Skype, so I opened my brwoser visited some site, hit share the link and select Threema. Then PA pops up, I entered key, then I selected a contact - and my 2nd device ringed because of recieved message.

As you can see it works for me. I can only fix errors if i know why they occur
[Xposed Framework Modules] w0rinal:
pin modifier option request

hey defim,

good module but i have a request for pin modifier:

pin modifier always uses 24h format, so the pin needed to be entered when it's 1:30 pm is 1330 and 0331 when reversed.

can you add an option to choose which format (12h or 24h) to be used?

regards

w0rinal
[Xposed Framework Modules] karl999999:
this is very strange. what android version do you use? i use 4.2.2 (not 4.4.x)

i have this error on 3 different devices with different browsers and different messenger apps

:( :( :(
[Xposed Framework Modules] defim:
As I want to keep settings small, I've added that time based PINs use 12h format if the device uses 12h format. Attached a file to test. To init it, open in the settings the modificator settings and check if it shows the correct pin. and dont forget to reboot, non-release version dont show a popup

See my signature. The S4 active with 4.2 is my main device where I use Threma etc, with the 4.4. device I develop apps. But the problem are the (sometimes small) modifications by vendors
[Xposed Framework Modules] w0rinal:
yep, it's working

you obviously need to restart the app to apply when time format has been changed but you don't do that very often i assume

the example always shows 24h format though but it doesn't affect the function

btw you forgot an R in "show search field" in your apps' settings activity

thanks
[Xposed Framework Modules] defim:
Thanks, this is not the only app missing the "r"!

As if you want enable time based pins you have to go to settings, it should be okay. The problem is, to get the used time format, a "context" is needed wich is not always available with Xposed. So its easier to save it.

The example should also show 12h, but it's now 9am and i have to wait a little to test...

EDIT: Oh, the time in the example is always 24h, but the examples itself are 12h, right? Will be fixed
[Xposed Framework Modules] Droidphilev:
Hi again,

Were you able to create a log?
[Xposed Framework Modules] klau1:
Opps delete
[Xposed Framework Modules] klau1:
Looks like this app really doesn't mix with Note 3 stock 4.3

Two major issues:

1. app thinks The system Is Still starting up After 15 minutes When everything Is clearly completely loaded. SORRY, It thinks device is locked when it is not currently locked. I know because it tries to lock the locked app If "Deny start of protected app" is selected on "while device is locked"

2. Custom Lock Pattern fails to display For The user to enter The password.

When This happens, The locked program simply opens and closes immediately without Any chance to enter a password pattern.

going to need a refund

---------- Post added at 04:56 PM ---------- Previous post was at 04:31 PM ----------

It seems ProtectedApps can not properly detect when the Lock Screen is On or Off.

If the device is set to a lockscreen delay when the screen autoshutoff, then when the user turns on the display before the Android Keyguard activates (due to delay countdown) then ProtectedApps will think the Keyguard is ON and basically let every protected app run.

The user would have to manually turn off the screen (which activates the Android Keyguard immediately) and turn it back on and pass the keyguard, before ProtectedApps can detect that the keyguard is OFF, and hence lock the protected apps.
[Xposed Framework Modules] defim:
[MENTION=762956]klau1[/MENTION]

It runs with Note 3? There where reports it causes loops, but this was maybe with current Android 4.4 :confused:

1) sounds like you have installed something preventing a broadcast sent when user logged in. Which other modules are you using? It was discussed above about "lockscreen disabler"

2) I think some other app causes this. What "special" have you installed?

>going to need a refund

You could request refund for all you apps here: https://play.google.com/store/account Btw, the only limitation is the count of apps...

3) There is no event "device locked" but "screen off", so this could happen. In the next version should be a workaround for that
[Xposed Framework Modules] klau1:
Yes, I'm using 4.3. It works without boot loop.

I don't have any lockscreen disabler xposed modules. The closes thing is:

Samsung Multiple Widgets on lock screen enabler. (Xposed)

Gear manager (regular app)
[Xposed Framework Modules] defim:
A quick look to multi widgets module: It changes also isSecure(unlock method), so it "could" cause problems, Please test without it.

If I have soon some days time, i'll get a TouchWiz device (but with 4.4) to do some tests..
[Xposed Framework Modules] Droidphilev:
Ah, hopefully.... :)
[Xposed Framework Modules] haoyangw:
Just a feature request, can you add support to maybe capture a selfie of the person who enter the wrong PIN/pattern a configurable number of times? This way it can really be of help when a device is stolen! Thanks for this awesome module! :)
[Xposed Framework Modules] chrootz:
I tested on my Verizon sm-n900v note 3, got same as your problem stuck Samsung logo and I had to format /system and reinstalled.

Still problem with protectedapps module and I think it has do with touchwiz. I couldn't connect with the adb logcat when the boot start processing.

Hope fix this problem soon.

Im on 4.4.2
[Xposed Framework Modules] defim:
I'v planned to flash soon on my "Google Edition" device a TouchWiz rom to get it work

[MENTION=5189434]haoyangw[/MENTION]: I try first to fix problems with some devices
[Xposed Framework Modules] falcontx:
Any update on this? I'm getting a stuck Verizon screen on my S5. Disabling ProtectedApps fixes it. If you tell me how to get the proper logs, I'd be happy to provide them.
[Xposed Framework Modules] defim:
Sorry, no time yet. I have to test this to reflash my main device with a complete differen rom..
[Xposed Framework Modules] Groverx77:
Is there a way to completely remove the program and locked functions I have had a lockout problem
[Xposed Framework Modules] Droidphilev:
By disabling xposed. I think you have to quickly start pressing (about 5 times or so) while booting till the device vibrates.
[Xposed Framework Modules] defim:
Or if you have still root access or adb with root, you could delete the content of the "files" directory of the app and reboot
[Xposed Framework Modules] Groverx77:
Hey thanks guys I'll figure it out today good looks
[Xposed Framework Modules] defim:
[MENTION=3932068]chrootz[/MENTION] [MENTION=6127237]falcontx[/MENTION] [MENTION=762956]klau1[/MENTION]

Added a TouchWiz compat mode (enable it in the settings before reboot). Tested with stock TouchWiz Android 4.4.2 on S4 active
[Xposed Framework Modules] chrootz:
Hi, im going to be glad to test right now. I will report you in few minutes. :good:
[Xposed Framework Modules] falcontx:
You can't change any settings before reboot because you get the message "This app is not activated..." then the app closes immediately.
[Xposed Framework Modules] defim:
Serious? Sure, just touch outside the alert dialog or hit back key to not opene xposed. (Sorry for little annoying dialog, but to much mails some time ago because module was not enabled at all)
[Xposed Framework Modules] falcontx:
Okay. The back button worked and the compatibility mode also worked on the Galaxy S5. Thanks!
[Xposed Framework Modules] defim:
Great :D

Btw, if you want cancel an alert dialog by touching outside (as most other roms) you could try Xposed Module "HowTouchAlert"
[Xposed Framework Modules] Droidphilev:
Thanks for this tip! :)
[Xposed Framework Modules] W1nks:
I have a problem. Since the update Thursday it broke my protectedapps and I can't get into it. It asks for my code and I enter it and then it just goes back to home screen. I use protectedapps to lock xposed and protectedapps so I have no way to get back into it or disable it. How do I fix this? I also have it lock xprivacy which applies a default template to all apps so I can't really use any new apps that install. Thanks!
[Xposed Framework Modules] defim:
[MENTION=5732681]W1nks[/MENTION]: I think you missed a reboot after the update, so the communication xposed <> gui part does not work correctly. As the xposed part "protects" the apps, it does not know you unlocked :)
[Xposed Framework Modules] W1nks:
I have rebooted my phone since doing the update and I'm still unable to get into my apps that are locked by protectedapps. Or maybe I'm not understanding what you're saying. What exactly should I do to get into my apps?
[Xposed Framework Modules] defim:
Yes, reboot after the update. So if you now unlock, does the state changes from lock to unlock of the widget or notification? Maybe you have some sleep-for-battery app which does terminate ProtectedApps and it cant receiver broadcasts anymore?

Can you tell me some detailf how you configured PA?

If you have su acces by adb or a terminal app you could delete the "files" diretory content of PA and reboot to reset the configuration. Or if the android app drawer could be opened delete "data" of PA
[Xposed Framework Modules] W1nks:
I have rebooted and it still doesn't work. When I unlock through the lockscreen passcode it just back to the home android screen and then pops the protectedapps screen again saying I need to unlock it in an endless loop. I tried adding the widget for protectedapps and it goes through that loop too. Nothing should be terminating that app. In the app drawer I can only clear cache which doesn't fix it. Uninstall, force stop, and clear data are all grayed out. I don't have a terminal app. I do still have root access but I'm not sure what I need to do with that. Thanks again for the help!
[Xposed Framework Modules] Scorp123:
I am experiencing this lock looping as well. I have only my gallery pattern protected with PA and a Tasker profile to relock on screen off. When I click gallery the pattern unlock comes up as usual but once I enter the pattern and the gallery starts to open it will throw me back to the locked "draw your pattern" screen. And it just looks like that until I use the task switcher to close the gallery app
[Xposed Framework Modules] defim:
[MENTION=5732681]W1nks[/MENTION] [MENTION=4794703]Scorp123[/MENTION]

Are you using the android or custom pattern unlock?

Can you pleae enable all logging options in the app: In settings do 2x a long touch on the text in the last line, then exit settings and reopen to see all options

Then do again this unlock which is not working.

Btw, for another app was shorty also a problem reported which exists only in cracked versions. So please test it only with app downloaded by Play Store, Xposed Repo or my website...
[Xposed Framework Modules] Scorp123:
Here's my log https://www.dropbox.com/s/4hqtzd3cm1bhcuu/ProtectedApps.log?dl=0
[Xposed Framework Modules] defim:
Thanks! Bug found and fixed
[Xposed Framework Modules] Scorp123:
Works perfectly again. Great work
[Xposed Framework Modules] defim:
I forgot to comment out 1 test line -.-
[Xposed Framework Modules] CHEF-KOCH:
Shi* happens, anyway great work! ?
[Xposed Framework Modules] 22vlaja:
i've just buyed your application now testing it, just have one question, after locking for example 5 random apps via pin, entering pin on the one of them unlock all others? hope u get me, is there any chance to change that,
[Xposed Framework Modules] defim:
Yes, unlock for all. You could see this & lock again (if enabled) with notification & widget.

To get something like per app unlock, you could set the "method" to "create" and the duration of unlock to very low value.

I thought about "native" per app unlock, but it renders widget, notification etc useless...
[Xposed Framework Modules] smohanv:
I installed version 2.5.7 lastnight. I experience a bug here. If anyone experience the same issue (explained below), you can use adb command to clear data which resets this app.

I installed this app and started playing with settings.

A. Settings > Input,

we have options to choose from,

Keyguard of Android

Custom unlock screen

Disable hooks of keyguard etc..

B. Settings > Unlocking,

There is an option here "Disable slider if a second unlock method is set"

OP please note, this "Disable slider........" does not appear if the 2nd unlock method "Custom unlock screen" is set

If we select both "Keyguard of Android" and "Disable slider........." is checked, when we choose protected app, it opens Android slide and nothing happens by sliding to open.

In my case, unfortunately I protected "settings", "xposed", "this app" and also "package installer". Becuase of these core apps were protected I could not open xposed to remove this app or even this app itself to disable. I left with no option. I managed with the following adb command. Hope this may help to the users having similar issues as mine.

Solution to manage the situation mentioned above

Connect device to PC via USB

Open command prompt from the folder where adb files are located (attached here for convenience, just unzip in to a folder of your choice)

adb root

adb shell

To clear data:

cd data

cd data

rm -r de.defim*

exit

adb reboot

Job done. Now open this app and redo settings again.
[Xposed Framework Modules] defim:
Pleas first change "rm -r de.defim*" to "rm -r de.defim.apk.p*" so other apps get not cleaned

> OP please note, this "Disable slider........" does not appear if the 2nd unlock method "Custom unlock screen" is set

I think this is correct: If you use not the lockscreen to unlock, then before unlocking the slider+additional unlock method is not visible because of custom unlock dialog..

> If we select both "Keyguard of Android" and "Disable slider........." is checked, when we choose protected app, it opens Android slide and nothing happens by sliding to open.

The module was enabled + device rebootet? If not, maybe something is incompatible with your device/rom. Details?

> In my case, unfortunately I protected "settings", "xposed", "this app" and also "package installer". Becuase of these core apps were protected I could not open xposed to remove this app or even this app itself to disable.

Because of this, in the OP is a hint "WARNING: Please configure and check ProtectedApps with other apps before!" ;)

If you have not yet set a password, every input is accepted (like Android does it).

So i'm not sure what's the problem exactly. Can you please test it again, but only set some other app at first?
[Xposed Framework Modules] smohanv:
Thanks for your response on this. I am okay now as I have selected custom unlock screen.

I am reluctant to use this app because unlocking for any one of the protected app is unlocking all the protected apps until either timeout happens or screen off and switch back on.

Thanks again.
[Xposed Framework Modules] defim:
Meh, okay.

For "per app" see #234

Maybe a "per app" later, but not sure if reasonable as Play Store rating is about 3 stars
[Xposed Framework Modules] smohanv:
Yes. I have noticed that. Let me use the app in combination with tasker and let you know.
[Xposed Framework Modules] klau1:
What is the difference between Tasker modes: unlock and infinite ?

Is there a Tasker intent for Unlock for X seconds?
[Xposed Framework Modules] defim:
Like in notification or widget:

-unlock has timeout you set

-infinite ... is infinite unlock
[Xposed Framework Modules] klau1:
Which field inside Tasker is used to set the time out period for unlock?
[Xposed Framework Modules] defim:
Time could be set in the settings of ProtectedApps
[Xposed Framework Modules] klau1:
Thanks for fixing it to work with TouchWiz.

Just getting CPU drain and slowness until reboot issue once Protected App is unlocked (ie: pattern / password), but the program doesn't subsequently open

EDIT:

Please disregard my message, I am still investigating the cause, and new evidence suggest the cause may not be ProtectedApps.
[Xposed Framework Modules] defim:
Sry, I dont understand what you wrote. After unlock you CPU has heavy load? Which process is it? Maybe logcat tells more
[Xposed Framework Modules] klau1:
Please disregard my message, I am still investigating the cause, and new evidence suggest the cause may not be ProtectedApps.
[Xposed Framework Modules] fengfengchao:
I'm long for open source to learn more:p:p:p
[Xposed Framework Modules] defim:
Best to see whats goind on and find cause: Attach usb cable, enable adb on device and watch logcat in computer

[MENTION=4822080]fengfengchao[/MENTION]: I dint understand what you wrote