search

FunkyMuse / Vigilante

🛡️ Android security (camera/microphone dots indicators) app using Hilt, Animations, Coroutines, Material, StateFlow, Jetpack (Room, ViewModel, Paging, Security, Biometrics, Start-up) based on MVVM architecture.
GNU General Public License v3.0
775 stars 64 forks source link

Service crashes on device unlock #81

Closed solarelf closed 3 years ago

solarelf commented 3 years ago

Hi,

I noticed that often, if not always, I got a Vigilante service crash just after unlocking my device with biometrics (Iris scanner plus camera, so camera is initialized), or when waking from standby, on home screen.

It seems to restart the service later though and it is working. So question: if this service is starting in User profile, or I can add some permissions to let it run on lock screen (why should I want to do that?), or maybe you give users option to set the startup delay in seconds?

FunkyMuse commented 3 years ago

If it crashes go into crash logs and tap on the issue you'll be redirected with the crash information and just paste it

FunkyMuse commented 3 years ago

Screenshot_20210116-123825

solarelf commented 3 years ago

Hi,

Well, it keeps on crashing (not every time, but ~ 20%) when waking device from standby and unlocking with biometrics (Iris + camera). Not a single time the "bug" feature was able to catch the exception and log it. It just says "No issues were detected!". Maybe this is because the glitch occurs before service (and the logger) starts?

See the attached screenshot. Translation from Russian is: "The app Vigilante is not responding", and the options are: "close" and "wait".

Screenshot_20210117-220732_YouTube

FunkyMuse commented 3 years ago

Oh well as I can see you're using DEX and that there is an issue and I've no idea how DEX implemented Samsung's device statuses and I don't wanna find out for now since they barely even provide any documentation at all.

Does this happen if you don't use DEX?

Well, it keeps on crashing (not every time, but ~ 20%) when waking device from standby and unlocking with biometrics (Iris + camera). Not a single time the "bug" feature was able to catch the exception and log it. It just says "No issues were detected!". Maybe this is because the glitch occurs before service (and the logger) starts?

The logger starts on application start up and it's there till the moment you kill the application.

solarelf commented 3 years ago

Does this happen if you don't use DEX?

I will check that and report

solarelf commented 3 years ago

The logger starts on application start up and it's there till the moment you kill the application.

That means that it cannot detect the glitch which occurs when it is not running. To catch this sort of glitches, it us good to set "finished gracefully" flag TRUE just when the service is about to gracefully end itself, and add it to log. The flag is reset to FALSE on service start, obviously. If there is no flag set to TRUE on service start then you know it crashed.

FunkyMuse commented 3 years ago

Does this happen if you don't use DEX?

I will check that and report

What's the status?

The logger starts on application start up and it's there till the moment you kill the application.

That means that it cannot detect the glitch which occurs when it is not running. To catch this sort of glitches, it us good to set "finished gracefully" flag TRUE just when the service is about to gracefully end itself, and add it to log. The flag is reset to FALSE on service start, obviously. If there is no flag set to TRUE on service start then you know it crashed.

That's not how things work. Also Samsung's DEX is the problem here I think

FunkyMuse commented 3 years ago

Closing due to inactivity