#14559 closed defect (fixed)
ANDROID: Crash when a bluetooth keyboard reconnects on Android 7 device
Reported by: | antoniou79 | Owned by: | antoniou79 |
---|---|---|---|
Priority: | normal | Component: | Port: Android |
Version: | Keywords: | crash, bluetooth, keyboard | |
Cc: | Game: |
Description
We have a report on Discord about this issue.
When a physical bluetooth keyboard reconnects to the device while ScummVM is running, it crashes to Desktop.
This was tested (by the reporter) on Android 7 and Android 10 only with ScummVM 2.7.1.
It crashes on Android 7, and does not crash on Android 10.
The reporter also tested with and older SDL based ScummVM Android port and the behavior is better (I think).
As of yet, I have not tested myself (I don't own a bluetooth keyboard).
The pertinent messages on Discord are around here:
https://discord.com/channels/581224060529148060/1135579923185139862/1135584296124559442
Change History (2)
comment:1 by , 12 days ago
Owner: | set to |
---|---|
Resolution: | → worksforme |
Status: | new → pending |
comment:2 by , 12 days ago
Owner: | changed from | to
---|---|
Resolution: | worksforme → fixed |
Status: | pending → closed |
It's been a while, but I believe I made this commit (and tested with a newly acquired physical bluetooth keyboard myself) to address this issue:
https://github.com/scummvm/scummvm/commit/a674b65c95e
That fix is part of ScummVM since official version 2.8.1.1 on the Play Store (and 2.8.1 which wasn't on the Play Store).
Edit: Indeed, I've made that commit for this specific issue. This is my relevant comment from Discord:
(...) so the issue with Bluetooth Keyboards causing our main activity to recreate itself (so it looked like ScummVM was crashing/returning to launcher) was because apparently some keyboards also notify "navigation" as configuration change when they're (dis/)connected. With the recent commit (...) issue should be resolved. I was able to test with my new Bluetooth keyboard
https://discord.com/channels/581224060529148060/1135579923185139862/1139978324760875098
I'm marking it as fixed.
There is not enough information about this crash to do anything and the user never provided such details.
I propose to close.