Database Develop

Device Requiring Pattern to Boot

After experiencing some Bluetooth issues on the January 12th build of CM13 which were supposedly fixed a long time ago but never were for me(Bluetooth Share crashing constantly and disconnecting my watch) I figured it may be caused by updating over old nightlies, so I decided to a clean install of the latest nightly from January 18th.
I installed and set it all up including my pattern lock and I made sure that I had it checked off that I do not want to have to require my pattern to start the phone. Later when I went to do a reboot it asked me for my pattern to turn my device on. I assumed it was a new bug, disabled my pattern, reboot, it didn't ask so I enabled it again, this time tapping that I did want to require it and then tapping that I didn't to make sure it was set. Same thing, it asked for a pattern on startup.
So I wiped my whole device again and flashed my TWRP backup of the January 12th nightly and now it too asks for a pattern to start... I've tried wiping the internal storage, assuming it had something to do with encrypt but that didn't fix the issue. Anyone know how to disable this? I hate entering my pattern to start the phone.

Have you tried to turn on an Accessibility Service? In my case this always disables the pattern on boot

cOmrade93 said:
Have you tried to turn on an Accessibility Service? In my case this always disables the pattern on boot
Click to expand...
Click to collapse
Thank you, it worked. I would like to know how someone would disable this if they didn't have an accessibility service? The only one I had was for my Pebble.

admiralspeedy said:
Thank you, it worked. I would like to know how someone would disable this if they didn't have an accessibility service? The only one I had was for my Pebble.
Click to expand...
Click to collapse
thats a good question. I think this whole "pattern on boot" has serious problems. In theory unchecking "require pattern to start" should disable the pattern. But it only works some time...

Note SM-N920C No notifications until I wake screen. Tried Heartbeat fix. Doesn't fix!

This has been happening randomly for a few months. I can go days when notifications are fine and they come through on my phone immediately. Then, for no reason, there are days when no notification show at all until I wake my phone.
They're clearly being blocked and my phone only attempts to pull them in when I wake it. Like a doze setting
It all started around the time Marshmallow 6.01 landed on the phone.
All battery saving optimisation settings are off.
All notifications are set to on.
I have tried EVERY app that I can find to set the Google heartbeat interval to a lower time. None solve the issue.
Factory reset doesn't fix it.
I have (always on) fiber internet so idle timeout settings on the router cannot be to blame for killing the Google heartbeat check.
I have tried it on mobile data only and it is the same
Other people online have had the same issues on other Samsung devices but I can't find anyone suffering from this on the Note 5.
Could it be an issue (somehow) with my Google account, since all notifications have to be pushed through this?
Worried that if I get a new phone I'll still have the same issue.
Any help would be appreciated.

are u using greenify??? what android u have 6.0.1 ??? did u try on smart manager / battery / to not optimize app u want get notification????
N920c/64g/cc n7 port v3/ arise sound/ doulby /xposed greenify+powernap+amplify

Not got Greenify.
Not enabled any power saving at all.
All apps are set to notify
Either the phone is blocking notifications randomly, or my Google account is.

S Pen Unlock menu bug.

Hello,
So I noticed this issue and the local live chat support failed to help me and the only thing suggested was a factory reset.
The Unlock with S Pen Remote" option on the Note 9 is a bit buggy. First, whenever it's on, your phone can be unlocked bypassing every security you've set up.
Having this issue since the day I own it and it's not fixed via the November update. Also it's not related to the Google's Smart Lock.
The second thing about this is the menu which can't seem to be able to save the chosen option. Here is a video of what I am talking about.
https://imgur.com/a/jT82AF9
For long time I was looking for a way to disable it and after one reboot I finally did it and now I cannot turn it back on. Apparently there is almost invisible "OK" button
Trying to figure out if anyone is having the same issues.

Nokia 7 Plus frequently locks up, not in Safe Mode

I have a Nokia 7 Plus, running Pie, unrooted. Generally a great phone, had the charging port fixed by Nokia a few years ago.
But every now and then the screen locks up, I can usually get control back by locking the screen and waiting a moment and unlocking.
I've factory wiped my phone a few times, I've removed of my apps but today it's been terrible and seeks to be locking up more than ever.
I put it into safe mode and used chrome, with Bluetooth and wifi and had no issues at all.
Any ideas how I can diagnose and fix the issue?

benji1304 said:
I have a Nokia 7 Plus, running Pie, unrooted. Generally a great phone, had the charging port fixed by Nokia a few years ago.
But every now and then the screen locks up, I can usually get control back by locking the screen and waiting a moment and unlocking.
I've factory wiped my phone a few times, I've removed of my apps but today it's been terrible and seeks to be locking up more than ever.
I put it into safe mode and used chrome, with Bluetooth and wifi and had no issues at all.
Any ideas how I can diagnose and fix the issue?
Click to expand...
Click to collapse
Any suggestions how to potentially fix this?

Maybe worth to try the following:
1) clear system UI cache
2) Android system force stop
3) reboot
and /or
1) activate developer settings
2) under -> debugging -> Game-Driver Settings activate "prerelease-driver* for all Apps. It will survive re-starts
3) enter recovery mode and perform the graphics test
4) reboot
This is working for me since 29 May 2021. To be confirmed....

chrhei said:
Maybe worth to try the following:
1) clear system UI cache
2) Android system force stop
3) reboot
and /or
1) activate developer settings
2) under -> debugging -> Game-Driver Settings activate "prerelease-driver* for all Apps. It will survive re-starts
3) enter recovery mode and perform the graphics test
4) reboot
This is working for me since 29 May 2021. To be confirmed....
Click to expand...
Click to collapse
Thanks @chrhei
Unfortunately the issue still persists with the first option.
I'll try the 2nd one - what does the Game Driver setting do?

benji1304 said:
Thanks @chrhei
Unfortunately the issue still persists with the first option.
I'll try the 2nd one - what does the Game Driver setting do?
Click to expand...
Click to collapse
To be honest: I've no idea what it does, but it's still working for me.

Sorry to all
After 5 days of usage it happened again.
Conclusion: No fix.
Sorry for being to optimistic.

Xiaomi Mi 5 freezes / restarts and can't see fingerprints

I put it in one thread as it may be connected. My Mi 5 behaves strangely for some time. It occasionally freezes, but not totally. I can, for instance, enable/disable WiFi, but an application gets stuck. After a while phone restarts by itself, but then very often freezes on LineageOS initial animation. I need to restart it manually by pressing the power button.
To make it more interesting, almost each time that results in a reset of some style settings (like icon style) and an inability to use existing fingerprints. They are still visible in the fingerprint settings, but apps that used them can't see them anymore (just inform that "you probably changed or deleted your fingerprints, activate it again"). I also cannot unlock my screen with fingerprints (after entering password once). The only way is to delete old fingerprints and add new ones.
I generated logcat files after such reboots, but they usually don't cover the time before a restart, as if the logs were cleared.
I have LineageOS 18.1-20220508-NIGHTLY-gemini.
I attach logcat examples:
Logcat_1 - sudden, partial freeze and auto-restart, which got stuck (12.05.2022 about 19:48). Fingerprints not lost. Surprisingly there are some logs from February which jump straight to the time after restart.
Logcat_2 - sudden auto-restart (15.04.2022, about 11:07) with fingerprints lost. (LOS 17.1). Again logs from a month before the restart just disappeared.
Do you think that may be a hardware issue? Similar strange things happend on LineageOS 17.1 just before an upgrade (about a month ago). Sometimes nothing happens for a week and sometimes I have a problem day after day.

Given that Lineage OS was flashed to your device, and if this issue did not happen before Lineage OS was flashed, I would suggest it a software issue.
To solve this issue, if you can still enter recovery
- format data - "yes";
- clean-flash a new rom.
I would suggest you flash a rom from lineage official website: https://lineageos.org/ if it was no so or a stock rom or a rom from XDA forum.