yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] ansh1996:
Are you sure this was caused by maxlock, as you said you dont reboot often. If you're not completely sure just try disabling all the modules except maxlock and recreate the situation.

On second thoughts, though, i also keep having soft reboots usually due to ram overload. But now, after updating to 5.3, these soft reboots turn into bootloops and i have to wipe dalvik and cache to get back.

I'll roll back to 5.1.1 now as 5.3 is not working for me anyway.

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] wifestealer:
Well if he installed maxlock last module and then he didn't install any other module then it's rom problem because I never had bootloops because of maxlock and it works here very good.
[Xposed Framework Modules] ansh1996:
What android version are you running? because i think the latest version causing problems only on devices running lollipop 5.1

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] sherazi21st:
Thanks for v5.3. Hide from launcher not working in Lenovo P70 (KK), rest is fine.
[Xposed Framework Modules] wifestealer:
I'm on 5.1.1
[Xposed Framework Modules] ansh1996:
Oh, okay. I guess then there might be some problem with my rom settings. Are you using 5.3? Is knock code etc working fine for you on LP?

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] wifestealer:
I also think it's your rom problem and I am only using knock code. It works fine bro
[Xposed Framework Modules] hassony2008:
Thanxx Man , its very Nice Design , ;)
[Xposed Framework Modules] wifestealer:
Well I found a bug. It works fine but if I reboot sometimes then it gives bootloops even I uninstall all another modules except max lock
[Xposed Framework Modules] radz_:
Same thing for me... if i reboot the phone it gives bootloop but its intermittent.... i have to press and hold the power button again to shut down the phone and boot it up again....

I can live with it as long as my phone is still booting up..

Hoping for fake die to fix first...then improvements is next...
[Xposed Framework Modules] Maxr1998:
Experienced that as well already..

I'm not sure what I can still do, there isn't even a pattern..

I mostly seems like referencing classes from own package which aren't loaded by Xposed causes the issue, but then again it should throw a ClassNotFoundException, and should never work..

Fake die is already fixed, but not pushed yet [emoji14]

I will still have to fix that lockscreen loop bug..

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] sansnil:
Can you push the Fake die fix? For those of us not having the loop issue. :fingers-crossed:
[Xposed Framework Modules] ansh1996:
After using 5.3 after a clean install for a week or so, here's my review of it. I have not fully tested it but only the features i mostly used.

1. Firstly, locking is not working for me. The problem of back button unlocking is there for me as was in 5.3 beta. I can actually kill the lockscreen activity by using long back press. Maxr i can provide any log you want me to.

2. In app chooser. If i tap 'backup list' option it send the device into soft reboot.

3. haven't tested FakeDie.

4. Intika mod reset after screen off is actually working, as opposed to my previous response. You just have to give it a second or two to get reset.

5. Fullscreen lockscreen/ hide status bar is also working in 5.3. (it wasnt working for me in 5.3beta)

6. the fluidity of intika is awesome now as compared to 5.1.1

So thats all i have tested. As of now the app is unusable for me, but i'll still keep it installed in case [MENTION=5222551]Maxr1998[/MENTION] requires any logs etc. Max, i know you have a life outside xda and you can take as much time as you can. But please do fix the problems above, as i love this mod too much to let it go. i really wish i could help you fixing these things if i knew much about android development.

Thanks in advance. :)
[Xposed Framework Modules] zerosp12:
Still can't lock Tumblr by first time on 5.3 version ... :(

FB works fine, Whatsapp works fine.

Excellent work! :D
[Xposed Framework Modules] vsr625:
Even I have that bootloop problem....as someone mentioned before it's not permanent.. .. . It happens only some times.....
[Xposed Framework Modules] Maxr1998:
Yeah, maybe later or tomorrow..

1. Cannot reproduce.. Even when I kill the app, lockscreen immediately reappears..

2. Will test in a few minutes, but not while writing this post ?

3. Isn't working, but will push soon as said above.

4. I actually said this inb4. Anyway, that's great :)

5.-6. Nice!

Hm, ok, could you send me your Xposed logs?

Yes, had it as well 3 times by now, I just cannot find a pattern.. :?

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] Maxr1998:
Pushed 5.3.1 which fixes ANR in backup app list and fake die. Enjoy!

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] huckky:
Just for the info, bootloop on reboot issue is still there for me but it might be rom related too. Other than that, it's working quite fine
[Xposed Framework Modules] radz_:
[MENTION=5222551]Maxr1998[/MENTION]

Sorry for the stupid question....

I just installed 5.3.1, it seems like everything works fine...

But how does Fake Die works? I'm thinking when you click on report, i have to type in "start" to open the app...

Right now, when i click on report, i saw my screen saver, then i have to put may Knock Code password...
[Xposed Framework Modules] bigbighill:
[MENTION=5222551]Maxr1998[/MENTION]

1、Maxlock 5.3.1 still can't unlock google Authenticator

2、menu "Rest Imod on screen truned off" not be translated into chinese

sorry pool english

HM NOTE 1S

MIUI 6.5.4
[Xposed Framework Modules] Maxr1998:
Exactly, fake die was never meant to be a lockscreen replacement.

You could enable min fake die to show lockscreen directly when pressing report..

Yes, I didn't fix it by now. Else, I'd have put it to changelog. It's much more difficult to fix than one may think, sadly :/

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] radz_:
Thanks for your reply,..

So its normal to see that when i press "report".. i see my home screen wallpaper, then i need to enter the passcode i use?

For me i use Knock code.. so when i press "report", i have to enter Knock Code to unlock the app...

Whats the use of "start" in Fake Die menu?

Sorry.. I'm very satisfied with this version right now..

I'm just curious, and i might use it in a wrong way...

A demo video would be nice, to see all features and how the way it works..
[Xposed Framework Modules] ansh1996:
See let me tell you. When you bave fake die enabled, you open the locked app it'll crash and ask you to report it. You press report, enter the phrase of your choice in the textbox (default : start), and it will show you your lockscreen.

If you enable mini fake die, it will show you the lockscreen directly after you press report, that means no need to enter a phrase first ans then press ok. There is no way that fake die will directly open the app, its just an added security feature, not an alternative.

Although, max, a micro fake die would be a good idea if it opens the app directly after entering the phrase, no ?

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] radz_:
Hi mate,

I'm almost there, but still confused..

To me it works in diff way, first what do you mean by "mini fake die"?

I have this settings..

Locking type: Knock Code

Fake Die: Enabled...

Lock app: Viber = Fake die is checked..

When i press: Viber.. i see Fake die function.. if press "report"

My "homescreen" wallpaper appears... not "lockscreen"..

Then i enter Knock Code to unlock the app.... not the usual to type in "start"

Your statement above is when i press report i should type in "start" to unlock the app? Thats my expectation too...

But it didn't take me there....
[Xposed Framework Modules] ansh1996:
See in the attachment below, actually the formal name is 'fake die direct unlock'. As written in the description, it goes directly to the lock screen after pressing report button. It only unlocks fake die directly, not the app itself. It just ships entering the phrase that you can set with the option directly below it.

The default phrase in there is 'start'.

And about my statement, i was just suggesting the Dev that this might also be an option where you unlock the app just by using the fake die. There is no such option in maxlock as of now.

I hope all your doubts are sorted out now :)

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] radz_:
Yup i undestood... but on mine it works diff..

When i press.. report.. it goes to my wallpaper.. not lockscreen..

And i have no option to type in "start" to unlock the app...

What it does, when i press report, my wallpaper appears.. then i type my Knock code.. then apps unlock..

Not lockscreen or type start....

Never mind mate.. i can live with it..lol

Thanks for all your help..
[Xposed Framework Modules] KOHO:
app unable to lock

First of all, it is by far the best app lock I've ever used!

Two thumbs up!!

I face an issue on the 5.3.1 which there's an app I'm just failing to lock that was locking fine in 5.1.1. I've enabled the fake die with knock code option, but everytime I click on this particular locked app, it just jump straight into the main screen of app. Will it be fixed in the new version?

Thanks Maxr for your great app~ I'm just loving this app too much!
[Xposed Framework Modules] ansh1996:
by lockscreen i dont mean your phone's lockscreen/keyguard. i meant maxlock lockscreen. Are you trying to say that you enter the knock code on the homescreen wallpaper? if yes, then you probably have disabled all the ui elements in the maxlock settings (namely title bar, input bar, dividers etc). If thats the case its fine and everything is working as it should.

I think you need to name the app that you're facing issues with. Also you might have to wait some time for a fix as the dev says fixing non-locking apps is difficult than it seems.

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] visky642:
One more thing

When usb is mounted ie mass storage on computer you cannot unlock anything at all
[Xposed Framework Modules] Maxr1998:
Just coming home from school and seeing [MENTION=4912187]ansh1996[/MENTION] already helped out on all problems, thank you very much :)

Oh yes, as the temporary file is saved on you external storage!

I think I really need to find another place to put the file now [emoji16]

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] Maxr1998:
Hey guys, so today I rewrote the MaxLock core code once again, and I fixed the following issues:

Lockscreen looping for some apps [MENTION=2433856]bigbighill[/MENTION]

MaxLock not working when having mounted mass storage to PC [MENTION=4670518]visky642[/MENTION]

bootstucks (hopefully?)
[Xposed Framework Modules] Atharkhan101:
Can't trust

I cannot trust this app for locking.

Still it wont lock few apps like pocket. Sometime it asks password multiple times for unlocking example app Evolve sms. I'm going back to app lock app in the Playstore. Till then good luck if you are making maxlock better.
[Xposed Framework Modules] visky642:
Lockscreen is still looping.

I'll test the usb mount soon
[Xposed Framework Modules] KOHO:
Thanks for the information!

Much appreciate your answer~~~

The APP which fails to lock for example is LINE. I found out that when I start-up the LINE app after reboot of phone, the lock screen will be shown. But after that, when I run the APP, it will never be locked anymore. It is very random…… I thought of the I Mod (Grace Period) may be causing to fail to lock even after screen off or long delay, but no matter which settings I try or do on MaxLock, LINE remains unlocked. And I didn't even enable any function under I Mod.

Really hope Maxr can help on this soon but no pressure!
[Xposed Framework Modules] radz_:
Rebooted my phone 3 times.. everything seems to be OK..

no more bootloop so far....

Thanks for the effort Max!
[Xposed Framework Modules] Maxr1998:
I'm sorry to hear.. I hope I can fix everything you mentioned one time, maybe you will come back again then.

Which apps do loop? Could you send me your Xposed apps?

Did you reboot after disabling Imod settings (if enabled before)?

Could you send me your Xposed logs?

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] visky642:
heres my logs i'm using instagram+ for eg

MLaC|com.instagram.android.activity.MainTabActivity|-|1437024367084

MLaC|com.instagram.android.activity.ActivityInTab|-|1437024367848

MLiN|com.instagram.android.activity.MainTabActivity|de.Maxr1998.xposed.maxlock.ui.LockActivity|1437024367991

MLiN|com.instagram.android.activity.MainTabActivity|de.Maxr1998.xposed.maxlock.ui.LockActivity|1437024368243

MLaC|com.instagram.android.activity.MainTabActivity|-|1437024376883

MLiN|com.instagram.android.activity.MainTabActivity|de.Maxr1998.xposed.maxlock.ui.LockActivity|1437024377022

MLiN|com.instagram.android.activity.MainTabActivity|de.Maxr1998.xposed.maxlock.ui.LockActivity|1437024377110

MLaC|com.instagram.android.activity.MainTabActivity|-|1437024379669

MLaC|de.robv.android.xposed.installer.WelcomeActivity|-|1437024387912

MLiN|de.robv.android.xposed.installer.WelcomeActivity|de.Maxr1998.xposed.maxlock.ui.LockActivity|1437024388073

MLiU|de.robv.android.xposed.installer.WelcomeActivity|de.robv.android.xposed.installer.XposedInstallerActivity|1437024392516

MLaC|de.robv.android.xposed.installer.XposedInstallerActivity|-|1437024392559
[Xposed Framework Modules] vsr625:
Hey Dev, Finally the bootloop problem is GONE...

Thanks for your work...

Just one more thing...

Why was it happening and what did you do to fix it....Just Curious...
[Xposed Framework Modules] Maxr1998:
Well, you could look at my git, but basically, I tried to remove as many MaxLock non-xposed class references as possible.. (import de.Maxr1998.xposed.maxlock.*)

I also now use one loader class which calls static methods from specialized classes, I oriented a bit on GravityBox sources from [MENTION=5008415]C3C076[/MENTION] ;)
[Xposed Framework Modules] ansh1996:
Hey [MENTION=5222551]Maxr1998[/MENTION]

Tried your latest beta.

No bootloops so far, so i guess the bootloop problem has been fixed for good.

But unfortunately, the locking bug has still not been fixed for me. All my apps still unlock if i press the back button, but it does keep asking for it on every activity until i dont put the code in.

I will send any xposed logs, logcat anything you need as i still have it installed.

I have still not lost hope that you will be able to fix my problem one day.

Thanks in advance :)
[Xposed Framework Modules] Maxr1998:
The problem is, I cannot reproduce, and the logs that you already sent me don't help me in any way.. And I believe there isn't anybody else having that problem, is it?

In /data/data/de.Maxr1998.xposed.maxlock/files/temps.json, is there any package name with "_close"?

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] ansh1996:
Yeah i guess no one else is having this problem. And if i remember correctly i havent sent you any logs before.

And here's what the temps.json file in the specified directory contains.

{"TheAnswer":"42","nextapp.fx_tmp":1437069197285,"nextapp.fx_imod":1437068941124,"IMoDGlobalDelayTimer":1437068941124}

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] Maxr1998:
Hm, so there is a bigger problem it seems. Do you use any IM where I can reach you? Telegram e.g.?

Sent using my nexus7 running stock Lollipop LMY47V ?
[Xposed Framework Modules] ansh1996:
Do you have kik messenger, if yes then my username is aroransh96.

If not, i'm installing telegram and i'll be on it with the same username.

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] Maxr1998:
Nope, I only use Telegram, Hangouts and WhatsApp. I can really recommend Telegram :)

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] ansh1996:
Okay give me your telegram username :)

Hit thanks if i helped ! :)

Sent from a blisspopped I9300 with the power of xposed.
[Xposed Framework Modules] Maxr1998:
Same as XDA ;)

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] appleline777:
"Reset Imod on screen turned off" uner INTIKA I.MOD setting doesn't work at all but manually reset it using Tasker works!

Is it a bug or did I miss something? Any suggestions? (version 5.3.1)
[Xposed Framework Modules] bigbighill:
1、Unstable, sometimes locked and sometimes not,

2、If QQ Security Center ( https # :// #play.google.com/store/apps/details?id=com.tencent.token) to open gesture password, can't lock this app.

3、can't unlock Quckpic （]https #:// #play.google.com/store/apps/details?id=com.alensw.PicFolder）

4、"Reset imod on screen turned off " not work

Xposed log:
[Xposed Framework Modules] Maxr1998:
In fact it works, but after applying the setting, you need to reboot atm, as I forgot to call reload() to reread the current settings from storage. I will fix that this weekend.

1. For which apps exactly?

2.&3. I will test them later today, and hopefully fix.

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] SyCoREAPER:
http://xdaforums.com/showpost.php?p=61888936&postcount=13

Think this will resolve the bootloops?
[Xposed Framework Modules] sathishcoumar:
Thanks Max .
[Xposed Framework Modules] Maxr1998:
It may. But it seems MaxLock itself was an independent source for bootloops/-stucks, but my last rewrite really seems to have fixed it.

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] bigbighill:
1,3 maybe becuse "reset Imod screen on turned off "…
[Xposed Framework Modules] the-blind-bandit:
This app is great!

It's missing a few things like smart lock/unlock when connected to a certain WiFi.

Id also like to be able to customize the color and thickness of the pattern unlock but apart from that, this app is pretty awsome.
[Xposed Framework Modules] TechnoSparks:
MaxLock was only meant to lock apps, and does not intercept notifications.

By the way, do regular battery-hogging applocks in Play Store intercept notifications? If they do, I guess it is time for a new #featurerequest :D
[Xposed Framework Modules] Fuzark:
No no. U don't understand me.

When i block WhatsApp with maxlock and receive an audio notification and play direct from Notification, i can hear the audio. If the intentions of app are block for privacy, so need tô block it too.
[Xposed Framework Modules] TechnoSparks:
I have already said that MaxLock is an app locker. It locks app, it doesn't offer shiny privacy-protection at the moment.

Notifications are flexible too; with many apps come different ways of how the notifications work for their respective apps. MaxLock locks an app by inspecting a main app's activity. In your case however, it does not involve launching a new activity, therefore unable to prevent anyone from hearing the audio.

If you wish, you can coin this as a feature request :)

As a workaround, you can use a secure lockscreen to prevent anyone from reading or interacting with your notification drawer.
[Xposed Framework Modules] Fuzark:
I already request it here and maxr1998 say that its possible for maxlock do that but he need do something that i don't remember. I'm Just asking if him already did it.
[Xposed Framework Modules] Maxr1998:
No, I didn't start on that feature yet. I still have much other stuff to fix and improve.

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] wifestealer:
Thanks man for new updates. It doesn't give problem about bootloops anymore. I'm on 5.0.2 now and it works perfectly fine.
[Xposed Framework Modules] kathense:
I got the similar problem when I tried Maxlock v5.3.1 (also v5.3 and v5.2.1) on Note2 (Android 4.3, Touchwiz) with xposed framework 2.7.

once i got an incoming call, the incoming call interface will be blocked and automatically came into settings with lock pattern appeared, after unlock it come into settings interface.
[Xposed Framework Modules] folusmile:
Your new update always force close on note 3..Pls fix
[Xposed Framework Modules] wifestealer:
What ROM are you using ? Because touchwiz roms aren't compatible with modules and xposed. Please use cm ROM
[Xposed Framework Modules] Maxr1998:
That sounds strange. I never faced that issue when having settings locked.. Maybe it's problem with your ROM? Maybe you could try to switch to a newer Android version..
[Xposed Framework Modules] sansnil:
Does the Fake Die feature work for anyone using a pattern lock? I've never been able to get it to work from 5.1.1 thru the latest version 5.3.2.
[Xposed Framework Modules] Sebi673:
Not sure if it's already reported since I'm away from computer and can't really check all thread but maxlock is the only app which isn't automatically relocking.

I click the lock toggle, go on home screen, lock phone, unlock it, go to recents, to maxlock and voila, it's unlocked and I can also click the lock toggle to terminate apps lock. Intika mod wasn't activated since I noticed that with the mod activated phone.apk and stock messaging apk won't lock.

If I clear recents, obviously maxlock will ask for pswd. The automator im using does that by default withing the lock-down profile so it's not really a problem for me.

A suggestion would be to have password on maxlock unlock toggle, just to be safe.
[Xposed Framework Modules] bigbighill:
5.3.2 "Reset Imod after screen turned off " maybe not work .

"Reset Imod after screen turned off " maybe not work .

When I run the locked app after reboot of phone, the lock screen will be shown. But after that, when I turn off the screen,wait some Minutes(within 10 Mins) , I turn on the screen and run the app it will not be locked.
[Xposed Framework Modules] Maxr1998:
Working fine here. What is "not working" in your case? Which apps?

That behaviour is normal and has been like this for ages. MaxLock itself doesn't use the lock algorithm, it only uses the fragment that shows the lockscreen..

I don't want to have to unlock always when I relaunch, I would have to handle the current position from dev side, and it sucks from usage side. Just close from recents when you don't need it anymore.

Works here.

It is not instant, but 5-10s was the time it needed to relock. You could open your file explorer, navigate to /data/data/de.Maxr1998.xposed.maxlock/files/ and watch the size of temps.json (open a few locked apps before), then turn of screen, wait 10s, turn on again, reload file explore, file size should have highly decreased.

If not after trying multiple times, send me your Xposed logs.

Sent using my nexus⁴ running Euphoria 1.1 with Xposed and hells-Core B80

Hit thanks if I helped!
[Xposed Framework Modules] visky642:
Lock loops still there :( using 4.1.2 tw xposed 2.7
[Xposed Framework Modules] bigbighill:
I try multiple times, I run a few locked apps, the file 's size have increased (”temps.json “),then I turn off screen ,wait 1 minutes,turn off screen ,the file size have no decreased.