After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 312127 - Support for Series 60 phones using GNAPPLET
Support for Series 60 phones using GNAPPLET
Status: RESOLVED FIXED
Product: gnome-phone-manager
Classification: Other
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: none
none
Depends on:
Blocks:
 
 
Reported: 2005-07-31 11:01 UTC by Matt Kay
Modified: 2007-11-19 12:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matt Kay 2005-07-31 11:01:07 UTC
Feature request:
  gnome-phone-manager support for Series 60 phones using the gnokii
interface to gnapplet, the gnokii application which runs on the phone
side.

Affected phones include 7650, 3650, 3600, 6600, 6620, 7610, 6670, 6630, 6680,
6681, 6682, N70, N90, N91.
Comment 1 Dag Stenstad 2005-11-30 09:15:36 UTC
Enabling the functonality in gnokii just consists of setting "model = series60"
in /etc/gnokiirc.
Comment 2 Bastien Nocera 2005-11-30 09:18:54 UTC
But it needs to be done automatically, and the gnapplet to be uploaded onto the
phone, that's the trouble.
Comment 3 Bastien Nocera 2007-07-10 17:32:05 UTC
(In reply to comment #1)
> Enabling the functonality in gnokii just consists of setting "model = series60"
> in /etc/gnokiirc.

It's actually "model = gnapplet", "model = series60" will use the nk6510 driver, not the gnapplet one.

It's possible to detect whether gnapplet is running/installed on the device using SDP discovery, and checking for the applet's presence. If it's not there, or not running, we could warn the user about it. It's a start.
Comment 4 Bastien Nocera 2007-11-02 16:55:46 UTC
(In reply to comment #3)
<snip>
> It's possible to detect whether gnapplet is running/installed on the device
> using SDP discovery, and checking for the applet's presence. If it's not there,
> or not running, we could warn the user about it. It's a start.

Actually, we can't, as gnapplet doesn't advertise its channel via SDP.

I guess we could still do this hardcoded for now though.
Comment 5 Bastien Nocera 2007-11-19 00:36:10 UTC
Bozo added a proper SDP record for gnapplet in the CVS version of gnapplet:
http://thread.gmane.org/gmane.linux.drivers.gnokii/9338/focus=9408

I just need a binary to be able to test this now.
Comment 6 Bastien Nocera 2007-11-19 12:55:09 UTC
2007-11-19  Bastien Nocera  <hadess@hadess.net>

        * libgsm/phonemgr-utils.c: (get_rfcomm_channel),
        (find_service_channel), (phonemgr_utils_get_serial_channel),
        (phonemgr_utils_get_gnapplet_channel),
        (phonemgr_utils_write_config), (phonemgr_utils_free),
        (phonemgr_utils_tell_driver), (phonemgr_utils_write_gnokii_config):
        * libgsm/phonemgr-utils.h: Add phonemgr_utils_get_gnapplet_channel
        to detect the channel used by gnapplet running on remote phones

        * libgsm/phonemgr-listener.c: (phonemgr_listener_connect),
        (phonemgr_listener_call_status):
        Add support for gnapplet, detect if gnapplet is running, and
        connect to the right channel if it's running, error out
        if it's not running (Closes: #312127)

You'll need an updated gnokii (CVS) and gnapplet (http://thread.gmane.org/gmane.linux.drivers.gnokii/9338/focus=9413), obviously.