yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] P€πtex4869:
Is it still possible to hide/lock the thumbnails of locked apps from the recent apps screen?
[Xposed Framework Modules] beeshyams:
Not on Pie+. Developer discusses this a few pages back in response to my related question
[Xposed Framework Modules] P€πtex4869:
Ah. I see. Thanks
[Xposed Framework Modules] beeshyams:
Works on Android 10 too, with the same limitations as on Pie but does create quite a few errors in EdXposed logs

I hope the developer is on track to release a non Xposed version soon enough

Thanks
[Xposed Framework Modules] Maxr1998:
On the current state of MaxLock

As you might have noticed, there wasn't a lot of activity on the app in the last 1-2 years. In fact, I didn't even look into the source apart from a small maintainance release back in June. That means, there was no progress on meaningful changes this year at all.

What are the reasons for that?

First of all, it's lack of motivation. The code in it's current form (with the new locking algorithm partly implemented) is a huge mess, and always when I tried to get into it again, it kinda drove me away again. Also, to put it bluntly, there were just more interesting projects to work on - I spent a lot of time this year contributing to Niagara Launcher, but I also had many other small projects that were more interesting to me. Additionally, University is taking a huge cut of my free time as well.

What next?

I still want to get into and work on MaxLock again, because I know the huge potential and usefulness it has, and I don't want to let you down. The thing is, I want to make my work as painless as possible - that my motivation doesn't get instantly killed again because of weird framework bugs and having to support exotic configurations.

That means:

Dropping support for Android 6 and below - that makes testing much easier and removes a lot of compatibility code

Completely remove all Xposed-related code, as the locking implementation will be replaced anyway - unfortunately, that also means the recents thumbnail hiding will be gone. It was way too complicated to support throughout the different Android versions and OEM skins, so it's probably for the best.

Slim down the UI customizations - I know some of you love customization, but I think that I've gone too far with MaxLock - it has way too many toggles, and the sheer amount of options was always intimidating to new/inexperienced users. After working a long time with [MENTION=9435783]8bitpit[/MENTION] on Niagara, I've learned that it's better to have less, but meaningful options, to result in an all-in-all better product.

On the other hand, I plan to add a lot of improvements to MaxLock:

First of all, the new locking implementation - only requires root (preferring Magisk, because that also supports startup scripts)

Redesigned lockscreen, supporting in-screen FP readers and other biometric authentication methods

A much less confusing configuration experience

Hopefully better support for multiwindow, I need to do some tests on that though

Potentially digital wellbeing features, if I find enough time

Performance improvements

So, what do you think? I'm looking forward to hearing your feedback on my thoughts, as well as other feature requests or ideas for improving the app-experience.

By the way, there is also a Telegram group that I created way back, if you want, you can join and discuss with me there: https://t.me/MaxLock
[Xposed Framework Modules] beeshyams:
Thanks for the update. I am subscribed to this thread though not using MaxLock any more because it's isn't supported though it works on 10. Right now I am using built in feature of Oxygen OS.

My thoughts (non developer). Putting it bluntly with no offense meant

1. The customization, toggles, these are unique and make MaxLock stand out. There are other plain and simple apps that lock too. I want to use MaxLock precisely for the customization it offers.

2. Dropping support below Marshmallow is OK provided module is available for others to use as is.

3. Dropping support for xposed is clear but why not use EdXposed? Fear that this may also get dumped or totally be free of X/EdXposed? That's fine but it won't have the power and like I said one may use any other locking app too

I think you have a niche module that is endearing because of it's customization and appeals to those who take the trouble to learn. Fantastic UI too (Big fan of those rolling cog wheels on choosing apps)

So you have to decide whether you want to target the savvy audience or create an app that would surely be good but one among many. I think you have chosen the latter. Our loss

All the best in your endeavors, irrespective of the choices and would appreciate updating thread too, telegram group aside
[Xposed Framework Modules] Maxr1998:
Thank you so much for your feedback! These are some very good points.

I think you may be right, killing too much of the customization could also hurt the experience, and drive people away who came for exactly that. My thought was mostly to make it more accessible to people who are not as tech-savvy - because that's what I also got a lot of feedback about. Additionally, I wanted to simplify the code a bit - every toggle is another "application state" I have to handle/keep in mind.

So, I didn't plan to kill all of the customization anyway (far from it), but I still want to streamline some of the options, to make them easier to use, and easier for me to support. Maybe an "advanced" tab for the tech-savvy users might be the right solution, I actually already thought about something like that this morning. Anyway, I don't know yet how everything will turn out, but I'll try to balance it between making MaxLock more accessible while also keeping the pro-appeal that others appreciate. Thanks again giving me a bit of contra, that's exactly what I needed to better think this all through :highfive:

I will obviously keep the old version around (and have it downloadable here or on XDA Labs/GitHub), so that people with MM or earlier can still re-download it when needed.

Xposed already was a bit of a hack (and obviously MaxLock as well), and EdExposed didn't change any of that - also afaik device compatibility and stability isn't perfect and doesn't get better with every new Android release, and I don't want to depend on a framework that might eventually die as well.

I think my custom system daemon implementation will be the better choice, the only thing we'll (very likely) loose is the thumbnail hiding, which is unfortunate, but as I already said, supporting that across custom roms and OEM skins was and will always be a pain (with (EdE)Xposed).

Regarding the UI: I just want to modernize it a bit, probably won't be thaaat obvious in the first few versions.

Btw, the cogwheels will always stay, I also really love them as well :D

The Telegram chat is mostly for additional/quick discussion, I will post any announcements here as well. And yikes, I need to be way more active on XDA again. Last login/post was a looong time ago.
[Xposed Framework Modules] beeshyams:
Glad you found merit in some points.

A suggestion--make the app simple but provide deep customization options a paid version with a trial period (it does take time to learn, if you haven't used it before). In the pro version you can bundle other things like automation support etc.

I wouldn't mind paying for it and would like to think same of others - if they value customization

Edit : Thumb mail hiding seems to be baked into lot of Chinese OEMs so people would probably expect that. If it can work with pure Android or skin's that aren't tweaked much it would be great

All the best and looking forward:svetius:
[Xposed Framework Modules] wannaskoo:
Hi, thanks for coming back to work on this project.

Here's some quick thoughts.

1) I agree on too many unneeded customization options. I don't personally use a lot of them (my lock screen is just plain black with the name of the locked app displayed).

2) Aaaaand also agree on switching from Xposed to Magisk. After all if you can achieve the same near-instant locking performance without all that heavy xposed hacking and support more devices and android skins, it shouldn't matter to the user.
[Xposed Framework Modules] Jquaidark:
Thanks

Thanks Man for your interesting

But please don't do that xposed is very necesary

without xposed it will consume a lot of memory, which differentiates it from any app in the play store, what I would like is that it had support for fingerprint scanner on the screen, why the current version does not support that
[Xposed Framework Modules] s1m0n:
[MENTION=5222551]Maxr1998[/MENTION],

thank you for the Wonderful app.

Sorry if that was answered before but i'm Looking for a lock app to lock the playstore access on my parents phone, as well as remove the delete feature on all the apps. My parents used to remove the apps they have "troubles" using and then reinstall scammy alternatives from the playstore. I installed MaxLock to test it out and i have 2 issues:

1. I put a lock on Instagram for test purposes. After a while lock wasn't showing and i could access the app until i rebooted. Then the lock appeared again.

2. If put a lock on playstore, i'm not sure if the apps are able to update. I Let's say, i have playstore locked and i don't know the PIN. I have the notification saying there are updates pending. Will apps be updated automatically when the phone is on WiFi and charging or do i need to unlock the playstore app for it to function?

Using the playstore version, not the xposed.

Cheers
[Xposed Framework Modules] Maxr1998:
Regarding 1: this is kinda weird, it seems the locking service is getting killed. What device are you on?

For 2: if you have auto-update enabled inside the Store, apps will update even if the app is locked. MaxLock only blocks access of the UI, it doesn't stop the app itself from working.
[Xposed Framework Modules] Maxr1998:
PSA: Google, for no apparent reason, removed MaxLock from the Play Store this morning, stating it has "high risk of abuse". Since there weren't any changes to the app or the Play Store page within the last months, I have no clue why this could have happened, especially with such a vague reason. I'll try to get the app back into the store, but I'm not optimistic I'll succeed, given Google's track history on this.

EDIT: Pushed a small update (7.0.6) which hopefully resolves this. Wish me luck, guys!

UPDATE: We're back! ?

You can download/update MaxLock normally from Google Play again.
[Xposed Framework Modules] s1m0n:
I'm on OnePlus 3T, latest stock firmware, Oxygen 9.0.6., non rooted.

Regarding the removal of your app from the play store, could you please attach the latest stable apk here? Herzlichen Dank!
[Xposed Framework Modules] Maxr1998:
Hm, that should have enough RAM to not be an issue, actually. Could you send a a feedback report from within the app? Maybe there's a crash somewhere.

Sure, that's a good idea. The update that I just pushed to Google Play (see my edit above) is also attached to this post.
[Xposed Framework Modules] oviung:
In the latest version (7.0.6), in case of password lock, once the lockscreen pops up it doesn't set focus on the input field so the keyboard would open without tapping on the field. Is there some option for this that I've missed?
[Xposed Framework Modules] Maxr1998:
Can reproduce, the keyboard doesn't open at all. I will fix that in the next version.

As I've stated some weeks ago, I plan to get into MaxLock again with full force, and finally finish the rewrite I started over a year ago. For now, I'm still busy with exams, but I will spend more time on MaxLock in March.
[Xposed Framework Modules] Kontex:
Yesterday I downloaded Version 7.0.6 in search of a good, slim Applocker without all this bloatware other applockers include and the hope that it is even better with Xposed support. Here is the Bug Report:

System:

Lineage OS 16 Android 9 with Magisk, EDXposed with YAHFA and the Riru core.

Bugs:

- The App locks other apps but it doesn't lock it self properly if you do not close the window in the recent menu. It doesn't ask for the unlock code when it is running in background window and reopened afterwards. Don't get me wrong the App Lock service is always active but the difference is the window entry in the recent menu.

- The App lock app itself doesn't mask the thumbnail in recent menu when it used in Xposed mode.

- had to deactivate the Xposed modul support as it didn't lock apps like "Settings" in this mode; it locks those apps well in the normal, nonxposed mode

Feature Wish:

- I unlock the apps with the finger print scanner and wish to have a lock screen where only a little symbole for the finger is drawn. The Pin or Password should only be visible if I tap the screen.

- Place the app itself in the list of lockable apps and set it locked as default. It is allways nice to have the full control over the system which includes the lock of the lock app.

- Option to force an other language

Comment:

- Thumbnail hidding is supported by other modules like https://repo.xposed.info/module/com.r3n3.xposed.securewindow very well so I see no reaseon for your app to support Xposed any more except for advertising.

Thank you for the App.
[Xposed Framework Modules] Peter1212:
Recently saw that one cannot set a lock screen security on xiaomi redmi note 7 while keeping encryption disabled. I was so much disappointed in the whole device and manufacturer, not the first time feeling that. I was looking if there was any way to secure my device with a lock perhaps with magisk/xposed but found nothing so far yet. This is the next best possible solution, unless it's possible to get some (pseudo) lock screen security via xposed. Maybe with this app if it's possible to do so in the future or some other app.
[Xposed Framework Modules] Maxr1998:
1. That's actually intended, but I might change that in a future version, with alle the comments I received about it. You don't have to remove it from recents though, pressing back from within the app should also work.

2. Yes, the feature is broken since Android Pie, and on some custom/OEM ROMs.

3. Might be a bug, not sure. Won't happen anymore with the new locking algorithm based on root only.

4. I also thought about adding a "biometric" lockscreen, and a show the other stuff only as a fallback. That way, I can also use the official biometric prompt from Android Pie, without bothering that it'd cover some part of the lockscreen.

5. Interesting idea, but not sure if that makes sense. Why lock other apps at all if the settings to disable the app aren't locked? Additionally, MaxLock uses another way to lock itself, and not the normal lockscreen.

6. Might add that sometime in the future. Not a high priority though.

7. FLAG_SECURE works across all Android versions, yes, but it also has the unpleasant side-effect to block screenshots for these apps. That's why I decided to build something different back then. But I'll very likely drop that feature if I don't find another way without Xposed.
[Xposed Framework Modules] jiraianam:
[MENTION=5222551]Maxr1998[/MENTION] thank you for your great app. I need an option xposed with your help, my bank app need I configure an PIN/password of the system. And I do not like do it, I just define an PIN in Android System to register fingerprints and later go in TWRP and flash the FIXER_Lockscreen.zip to remove the Android System PIN because I prefer use your APP with fingerprint. But google pay and other bank application require I configure an PIN of the system, have how you put an option to spoof Android System PIN to the banks applications think have an PIN configured in the system using the Xposed Resource? I am user of the you app even the 6.4.1

A second point is if you can you put bult-in module Lockscreen Disabler inside of your app updated to the Android 10 too?
[Xposed Framework Modules] jiraianam:
[MENTION=5222551]Maxr1998[/MENTION] is extremely important to me you put the Lockscreen Disabler module inside your app, can you make it please?

---------- Post added at 12:40 AM ---------- Previous post was at 12:40 AM ----------

[/COLOR [MENTION=5222551]Maxr1998[/MENTION] is extremely important to me you put the Lockscreen Disabler module inside your app, can you make it please?
[Xposed Framework Modules] mario0318:
Hey guys. I read through some of the previous posts regarding Maxlock with EdXposed hoping to find a clue on how to fix MaxLock not detecting the xposed/edxposed framework. Here's the deal...

Currently it works fine, I'm on magisk 20.4, Riru 19.8, Edxposed Sandhook 0.4.6.1, and EdX manager 4.5.7. Everything is working as is, maxlock detects xposed framework as normal even though it's edxposed. But only because I have the option enabled in EdXposed Manager to 'de-optimize boot image' which as stated on the option description can slow down the system as a whole, and it does so on my phone. With the option unselected, in other words allowing edxposed to optimize the boot image, the system is speedy but maxlock doesn't kick in and when going in the app's implementation settings it says it's unable to detect the xposed framework with only the accessibility method as the only working option, albeit extremely limited and almost as slow as having the boot image de-optimized. I know that option is to allow ed/xposed modules access to all framework hooks, but is there a workaround I'm missing entirely?

I've tried all sort of settings in edxposed manager, App List Mode, both as whitelist and blacklist, Force Hook Modules, Instant Module List, Disabled Resource Hooks, all to no avail. The only thing I haven't tried is enabling App List Mode and selecting all the apps I've got locks for, but this wouldn't resolve the issue of Maxlock not detecting the framework would it?

I'm on Lineage 15.1. I know I can run xposed just fine but I would like to keep the Riru/EdXposed management setup as they're under active development and given all the other modules from xposed work fine in edxposed, including GravityBox. Maxlock seems to be only module having issues hooking to the framework when boot image is not deoptimized.

Anyone know of a potential fix? Or guide me to a thread I may have missed? I've already posted this on the unofficial EdXposed thread here on xda and since this issue isn't apparent when using xposed, there isn't much i could find there regarding edxposed. Btw, Edxposed YAHFA causes bootloops so trying that framework as a potential solution unfortunately isn't possible.
[Xposed Framework Modules] Antho02:
hi, i encounter a problem since i updated to Android 10, not sure its related but...

so i use lo lock access to edxposed manager app with maxlock since years, but since yesterday, once i scanned my fingerprint, the edxposed manager app appears all black instead of show status (see screenshot)

then i open app menu / framework and it finally appears...

Xiaomi MiA2 Lite / Android 10 / Stock Rom

Magisk 20.4 / edXposed4.5.7(same with 4.5.0) / MaxLock7.0.6
[Xposed Framework Modules] rfurb:
E-Mail app locking issue

Hello all,

I am a new MaxLock user, and initially installed version 7.0.6, but it just crashes on my phone, Samsung SM-910F running stock Android 5.1.1 rooted with SuperSU.

Interestingly, trying an older version (7.0.2) it works perfectly. Has anybody seen this problem ?

Thanks in advance !
[Xposed Framework Modules] robneymcplum:
I've used maxlock for years, every phone, every rom. I've always had a tasker profile so that when any power lead (ac/USB) is inserted then maxlock is activated.

I've just upgraded to CRdroid android 10 and this is not working now. Having a gravity box quicksetting tile to activate maxlock works fine, and the app works fine everywhere else.

Phone is redmi note 6 Pro, edexposed sandhook latest, maxlock latest and Crdoid 6.6 android 10. I'll paste the error log here:

time: 1591718650667

msg: java.lang.SecurityException: Permission Denial: startForeground from pid=7734, uid=10251 requires android.permission.FOREGROUND_SERVICE

stacktrace: java.lang.SecurityException: Permission Denial: startForeground from pid=7734, uid=10251 requires android.permission.FOREGROUND_SERVICE

at android.os.Parcel.createException(Parcel.java:2071)

at android.os.Parcel.readException(Parcel.java:2039)

at android.os.Parcel.readException(Parcel.java:1987)

at android.app.IActivityManager$Stub$Proxy.setServiceForeground(IActivityManager.java:6178)

at android.app.Service.startForeground(Service.java:707)

at de.Maxr1998.xposed.maxlock.ui.actions.tasker.TaskerActionService.a(Unknown Source:21)

at c.e.a.a.a$b.run(Unknown Source:4)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)

at java.lang.Thread.run(Thread.java:919)

Thanks.
[Xposed Framework Modules] GOrMHATRe:
If I was to install this app today, woud I need Edxposed or magisk to access full functionality? I am on android pie.
[Xposed Framework Modules] DB126:
Yep
[Xposed Framework Modules] mario0318:
Anyone on Los 15.1 (Oreo 8.1) with latest edXposed get maxlock working and what was the process?
[Xposed Framework Modules] KnifeFed:
Did it get removed from Google Play again?
[Xposed Framework Modules] KnifeFed:
Is the project abandoned?
[Xposed Framework Modules] Maxr1998:
Nope, I removed it myself because I don't want to risk any strikes because I can't keep it updated. You can still find the latest release in this thread and on the Xposed repo.

Not completely, but at the same time I have to admit that the planned updates get more and more unlikely. It's just that I have too many other projects to work on, and I recently also started working on my bachelor's thesis. So I can't promise anything, but I also don't really want to fully abandon it yet.
[Xposed Framework Modules] George jg:
Maxlock latest version for lolipop
[Xposed Framework Modules] George jg:
Plzz sent a link
[Xposed Framework Modules] rfurb:
Here you go:

Download Maxlock 7.0.4

This is the one I actually use today in Android 5.1.1
[Xposed Framework Modules] hac9:
Hi. I have an issue with MaxLock 7.0.6 version on OnePlus 5T (latest DerpFest Android 11). If I enable MaxLock in EdXposed and simultaneously enable keyguard (by setting unlock password in settings) and then I reboot, the UI freezes. The launcher won't start - the screen is black. After long press on power button the power menu appears - shows an option to shutdown, restart and lock. The only way to restore it is to boot the device in safe mode which disables magisk modules and edxposed. I can use MaxLock with disabled keyguard or use keyguard with disabled MaxLock. I have attached log files on what happens during black screen. Do you have any suspicions on what causes this behavior?
[Xposed Framework Modules] darashikoh:
I am facing the same issue @hac9. Android 11. Hope someone can chime in on this.
[Xposed Framework Modules] Valiante:
Does not appear Android 11 is supported at this time
[Xposed Framework Modules] Valiante:
Will the module be adding support for LSPosed's scope requirements?
[Xposed Framework Modules] D!Ts2l:
Unlikely. Probably no support at all.

The developer said early last year that he would be supporting this module less and less.

I fear it may have already been abandoned.
[Xposed Framework Modules] DarkSJ1998:
Does anyone here have any app suggestions that work just like MaxLock? I've been using this module since years now & it seems I won't be if/when I upgrade to Android R/12.

Tried a couple of "app locks" from Play Store, none of them are as easy, effective & simple to use as MaxLock is, I don't need fancy stuff, the crash dialog imitation is fine for me. Thanks.
[Xposed Framework Modules] Lord Sithek:
Did u try Norton? The only Play Store alternative I've found useful
[Xposed Framework Modules] DarkSJ1998:
Alright, will give it a try, thanks!

I see there are some bad reviews regarding the latest version on the Play Store, are you using the latest one or any old one? Also, does it have the "app crash" imitation implementation in it?