[prjkt.io] simplepinoi177:
Very peculiar issue...

Hello all! I am hoping you guys can help me. I am having a very peculiar issue...

Some initial info: I am

very

new to Substratum.

I am using a Google Pixel 2 XL (taimen) on Pie/9 (flashed; not OTA), rooted with Magisk 16.7, custom recovery (TWRP 3.2.3-0), custom kernel (Flash kernel 3.2 beta). My ROM is stock. Substratum version 998 (ninety ninety eight). Following the guide from the OP, I used Matlog and I attached the text file to this post. Also, I normally employ a "Pattern + Fingerprint" screen lock (the importance of this is shown later on)...

Here is an explanation of my issue...

After flashing the Full Factory image of Android Pie/9 (taken from the developer's site), I proceed to root and install a custom recovery and kernel. Afterwards, I would confirm root, install busybox, and a few modules. I could/would restart multiple times, entering my screen lock pattern to decrypt after each reboot -- and successfully, I might add. At this point, everything would work well and without a hitch. After confirming this, I would install Substratum 998 (taken from APKMirror [given on XDA here]), and then install Abdulwahab Isam's (AL_IRAQI) Status Clock Tweaks for P. After setting it up that my "clock placement" would be on the "right side", I would "Build & Update", restart my device, after starting backup go to Manager, toggle the overlay, and "change overlay states". This would place and switch the clock to the right successfully. The problem is this: somehow doing this will cause my device to

NOT

recognize my pattern! It would say "Wrong Pattern" after the next reboot (when asked at first to decrypt) and a number of times (initial decrypt) after that!.

In the instance of the logcat I attached, I set my device up to not have any security or screenlock so when I have to restart to install and build the overlay, I wouldn't get stuck at the pattern not recognizing and so Substratum will have the overlay in the Manager after the 1st reboot (subsequent reboots after the 1st will show no overlays in Manager).

The only way I can get back into my device is to restart, input the pattern, and if it doesn't work (says "Wrong Pattern"), restart it again, and do this as many times as needed until the one instance it does work! (5+ times some times). There have been instances that it did not seem to ever work and I would have to re-flash my device to non-root stock to get back in.

Here is another peculiarity of this bug/issue: when using the pattern in my custom recovery (TWRP), the pattern works 100% every single time! So it's not that my pattern changes or removed!

Also, I should say that I have done things where I would set up my Fingerprint + Pattern immediately after flashing my phone, no issues come up, and only after installing Substratum and the Clock Tweak .apk does this occur. I also mention this to show the reasoning for removing it in the instance of my logcat; If I were to have a fingerprint and pattern screen lock, my device wouldn't recognize it on the subsequent reboot, and I would have to restart quite a number of times before I can get back into my device -- but the overlay would then not appear in the Manager.

One might say, "...why go through all this trouble?" I really absolutely hate the clock's placement in Pie currently -- especially considering that it is really only changed for that damned notch (a whole other rant altogether) and the supposed "symmetry" of it all. As such, this is the only way I could find that would put this back while still employing a stock "ROM" or "theme" -- I don't wish to use another ROM, theme, or launcher.

I appreciate you reading this far into this lengthy post (Anyone that knows me, knows I tend to be extremely descriptive). I acknowledge that it might be the Clock Tweak that may cause this and/or I should bring this issue up there, but I find that reasoning highly unlikely as well as I should get better support and explanations here this specific forum off the specific app that enables the tweak. I also have the thought that it might be more informative if I could include a logcat of the pattern not working, but I am unaware of how to enable either Matcat or another logcat app to continue/work past shutting down and re-enabling and logging during start up even to the point before a pattern is required. If a logcat of that is needed, please inform me on how that is accomplished and I would be more than happy to comply.

Again, I appreciate you, any and all of you, reading all of this and helping out in any way -- I know it might be a bit aggravating and/or a bit annoying the size and length of this post. I am simply just this way, and merely wish to be as thorough as can be as to not require any of you to inquire more than you have to.

Thanks again, and thanks in advanced...