Open rmktrcyp opened 4 months ago
not intentional, but the app may simply not be compatible with newer android or with the lineage changes
but why would it work then with other versions or even custom roms based on Android 13? Also, both Automate and Macrodroid are pretty consistently updated...
I don't know and I don't have a rooted device to debug this usecase.
Please also note there is a 12hr strong auth timeout compared to the typical aosp 72hr, where it'll prompt regardless.
With Shizuku is the same issue, so far..
Okay, good to know, but I don't think this will be an issue for my use-case.
Is there any reason why setting the timeout for the lock screen through apps like Macrodriod or Automate, using root permissions and so on, should not work? Like, the logs show that the setting is being changed without errors, but then when I have a look at the setting it is not changed at all and it actually also doesn't work... somebody also mentioned this issue being possibly an intentional feature of DivestOS? I wonder is there any alternative way to accomplish this with DivestOS?
Thanks!