|
Post by Si6776 on Jun 7, 2021 14:05:46 GMT -5
Hi, I've noticed that my Unlocker has crashed several times recently, not seemingly connected to any other events, but more often than not happens on reboots. I have to Force Stop the app to close it. Any reason for this or solutions? Samsung Galaxy S10+, fully updated.
|
|
|
Post by GoneMAD on Jun 7, 2021 17:35:03 GMT -5
Force close what app? If it crashed then there is nothing to force close.
I can look into it but at a quick look at the bug reports there are only 2.. neither of which are something i can fix or give enough information to indicate what needs to be fixed
|
|
|
Post by Si6776 on Jun 7, 2021 18:07:18 GMT -5
What I'm saying is, when the Unlocker crashes, which it does when it's checking the registration, the top bar notification cannot be removed until I go to Apps > GoneMAD Music Player Unlocker and Force Stop the app. In Device Care > Care Report, the app is listed as having crashed on several occasions, as per the screenshot I posted above. I know I can turn off the notification but that presumably won't stop the Unlocker from crashing - I just won't know about it and it could potentially drain the battery.
Sorry if I wasn't clear before.
|
|
|
Post by GoneMAD on Jun 7, 2021 19:31:23 GMT -5
Ah okay forgot about the notification. You can safely hide the notification with no performance impact. The unlocker service starts, checks status with google play (99% of the time the result is cached so the response is instant), and then shuts down. It shouldnt run longer than a second (and most of that time is spent waiting for the response from google play services).
The notification isnt removable due to the crash. Looking at the crash reports and it appears to only be android 9 and 10.. so at least it looks like google finally fixed the bug that causes this in android 11. The gist of the issue is when a foreground service is started, the service must make a call to say they are running in the foreground. the unlocker does this right when the service starts up.. however the android OS doesnt wait long enough (or thinks it wasnt called) and crashes. Its super annoying
edit: nevermind i still see reports from android 11
|
|
|
Post by Si6776 on Jun 8, 2021 3:24:05 GMT -5
Yes, I am using Android 11. I can't say whether it was happening with previous versions as I didn't have GMMP then.
So just to clarify, you're acknowledging this is an issue and that it will be fixed at some point? I'm fine with hiding the notification, but obviously that doesn't actually fix the problem of the Unlocker crashing.
Thanks.
|
|
|
Post by GoneMAD on Jun 8, 2021 9:06:28 GMT -5
im acknowledging its an issue however i do not know if its fixable. The crash is a flaw in the android OS that google refuses to fix (working as intended according to them) issuetracker.google.com/issues/76112072?pli=1#comment56I did slowly roll out a potential "fix" but i dont know if it will fix the crash 100% of the time. The service calls startForeground immediately when it starts but a lot of times thats still not quick enough according to the OS. The rollout is at 20% currently and i'll bump that up if no additional issues get reported
|
|
|
Post by Si6776 on Jun 8, 2021 15:21:54 GMT -5
OK, thank you. 🙂
|
|
|
Post by GoneMAD on Jun 17, 2021 23:29:10 GMT -5
fyi i did push an unlocker update that might fix the issue. Actually had it at a 20% rollout for like 10 days and forgot about it. Upped it to 100% rollout 2 nights ago
|
|
|
Post by Si6776 on Jun 18, 2021 18:29:21 GMT -5
Thanks, I've received the update, but sadly the issue remains, and the Unlocker is still crashing on phone restart.
|
|
|
Post by GoneMAD on Jun 18, 2021 20:39:34 GMT -5
ah. dont think its fixable then. sorry
|
|
|
Post by GoneMAD on Jun 18, 2021 20:51:45 GMT -5
also according to the google play console there is only a single crash listed (old version had a lot of crashes and ANRs), so the update is at least helping some people
|
|
|
Post by Si6776 on Jun 19, 2021 3:57:52 GMT -5
It's a shame, because it doesn't happen with Unlockers for other apps.
Thanks for trying.
|
|
|
Post by GoneMAD on Jun 19, 2021 10:05:39 GMT -5
other unlockers were most likely not forced to update to the newer api levels which put the requirement for foreground service (foreground services are what is bugged in android) or dont do google play validation. I was forced to update the unlocker to support 3.0 and classic split, previously it was not updated for like 7-8 years
Just because another app can/doesnt do something means nothing in relation to a different app. Software is not that simple
If the crashing bothers you that much you can email me a receipt / proof of purchase and i can send an offline unlocker which will not have the same issue
|
|
|
Post by Si6776 on Jun 19, 2021 12:02:47 GMT -5
Thanks for the offer. Honestly, not nit-picking, but this sort of thing does bug me, as it clearly shouldn't be occuring.
As it happens, I just rebooted again to see if Device Care > Optimise would kill the process and it didn't crash this time, so I'll see how it goes.
|
|
|
Post by GoneMAD on Jun 19, 2021 20:36:18 GMT -5
yup hundreds of android developers agree and google will do nothing about it. its insanely frustrating.
|
|