"You can force-kill and restart apps without leaving the system broken" is a core design principle of all modern operating systems. I believe that a system component which requires programs to perform "clean" shutdown to avoid broken system state (that cannot be recovered by an app restart) is extremely undesirable and seems like important to fix. SOAPBOX RANT □ (skip this blockquote you don't want to argue the subject) (OPEN QUESTION: What does happen on other platforms currently?) That means the device no longer shows up in discovery, and becomes an "orphan" unavailable for use until the device is restarted, the computer is restarted, bluetoothd is restarted, or some bluetoothctl incantations are made. My understanding: there is an issue (quirk?) with the bluez (Linux) implementation (and possibly other platforms?), where if an app is connected to a device and then terminates without disconnection, the device remains connected and the connection is kept alive by bluez. Please check my understanding of the situation and the possible solutions, corrections much appreciated. I'm happy to help if there's a good agreeable direction! I apologize profusely if I'm just stirring the pot uselessly. This seems to be the most promising thread (including some great positive suggestions by above).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |