GNOME Bugzilla – Bug 661413
Patch for improved Gnapplet support, enables Android Gnapplet
Last modified: 2018-08-17 18:49:47 UTC
Created attachment 198742 [details] [review] Patch for looking up Gnapplet by UUID and defaulting to Gnapplet when AT commands are unavailable The attached patch makes two changes needed to get an Android version[1] of Gnappet to connect with g-p-m. Many Android phones does not have a serial port that accepts AT commands, which is used by g-p-m to determine the phone type. This means that finding the driver for such phones will fail, so I've changed the code to default to Gnapplet driver when AT commands are unavailable. Android phones are also quite limited on how a Bluetooth service record can be configured, so even with the correct driver the existing code will fail because it tries to find the RFCOMM port by searching for a serial class port. I've changed the code to try to look up the port by using the Gnapplet UUID first, and then falling back to the old behaviour if it can't find the port by UUID. I believe that none of these changes will influence existing Gnapplet support. [1] The Android app is still in early development, but with this patch to g-p-m I'm able to use it to send SMS. No project page yet, but it will be posted to the Gnokii mailing list soon.
gnome-phone-manager is not under active development anymore since 2013. Its codebase has been archived: https://gitlab.gnome.org/Archive/phonemgr/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.