keymapperorg
Crashing After UI7 Update
Developer TODO (don't remove)
- [ ] update documentation
Been getting this error message continually after updating to UI7 with latest update of Key Mapper. No idea why this is happening.
Needless to say that clearing the cache doesn't help.
S22 Ultra. Definitely a brand new issue since the the phone updated last week to UI7 and Key Mapper updated just the other day to 3.1.2. Massive crashing, accessibility keeps turning off even as I turn it back on each time. Something's definitely up. Also never saw this system dialog in all my previous testing ever.
I would also just add that for 90% of Galaxy users other than the latest model, the UI7 update has really just started to roll out, which might explain why others haven't yet reported anything, I'm thinking.
Also to be clear, it's not just UI7 but also Android 15 that got pushed to the phone for everyone last week as well.
I'm getting this error dialog every 10-15 minutes, as if it's trying to recover and then repeatedly fails.
It would help us if you could get a logcat using ADB. Do you know how to set up Android Debug Bridge on a PC?
One more factoid. These error messages are coming even with the app paused.
Sorry, super late here in UK. I'll be back online tomorrow if you're available then.
I imagine you'll find the issue easily because the app is literally freaking out like never before.
Starting with plugging in the phone and opening Mac Terminal.
If everything is set up, you should be able to type 'adb devices' and see that your device is connected. If it says 'unauthorised' you will need to open your phone and accept the debugging prompt.
Once you are connected please can you enter adb logcat | grep -i keymapper into the terminal and then open the app. Once the app crashes you can copy the log from the mac terminal and paste it here.
Do I need to keep the phone plugged in and Terminal running until it crashes next?
Also, overnight the phone performed an "optimizing apps" routine on its own and I haven't seen it crash yet today. Wonder if that fixed it?
Yes, please use the app until it crashes after running the command in the terminal.
Alas, this issue has not gone away but was masked by another less obvious symptom that I did not realize until now due to being busy on other things. Before, the problem was a nearly constant error dialog telling me Key Mapper crashed after updating to UI7 and then 3.1.2.
Then, the messages went away after clicking Clear Cache in the error dialog and it optimized the apps.
But, unbeknownst to me until now, what's been consistently happening after that is that app's accessibility keeps shutting itself off (not working) which forces me to manually turn it back on, when it works for a while, and then shuts back off. No idea why this is happening, and it's not practical for me to be tethered to ADB over long stretches of time, so not sure how to best help you debug this. Also never see this behavior before.
Now that the app is able to run for a while, could you turn on 'extra logging' in the settings and leave it on for a couple days. Once you notice the accessibility service crashing could you send over the log?
Actually noticed now that accessibility had turned off, so I turned on extra logging and reset the accessibility and will check back and send the log in a couple of days.
Ok good because the entire app is in a constant state of crashing at this point. Kind of surprised nobody else is having this issue.