GNOME Bugzilla – Bug 475795
Support of Nokia 5500
Last modified: 2007-11-02 11:25:23 UTC
Hi, is it possibile to support Nokia 5500? the output of --identify is: gnome-phone-manager --identify 00:18:0F:9F:F6:30 model: 'Nokia' http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441627 thanks. francesco
I don't see it as being supported by gnokii in the sources, and I don't know why it wouldn't output a problem model name. Could you please get the output of: gnokii --identify with the following ~/.gnokiirc: [global] port = 00:18:0F:9F:F6:30 model = AT connection = bluetooth [logging] debug = on That line also sounds pretty bad: (gnome-phone-manager:4392): GConf-CRITICAL **: gconf_engine_set_string: assertion `g_utf8_validate (val, -1, NULL)' failed Could you get the output of: hcitool info 00:18:0F:9F:F6:30 Please make sure you redirect the output for both commands and attach them in a tarball, so that the text isn't changed by bugzilla/e-mail/whatever. I'll ask Pawel about the 5500 support.
Created attachment 97659 [details] gnokii --identify
Created attachment 97660 [details] hcitool info 00:18:0F:9F:F6:30
Here they are. I'll make a tarball if you're not satisfied.
This message probably came from another device, rather than your phone: (gnome-phone-manager:4392): GConf-CRITICAL **: gconf_engine_set_string: assertion `g_utf8_validate (val, -1, NULL)' failed Could you please attach the output of "hcitool scan" (redirected directly to a file)? There should be a device with non-UTF8 characters in the name. As for the 5500, it is unsupported by gnokii in gnapplet, and the AT mode won't do SMS on that phone. Could you attach the output of "sdptool browse 00:18:0F:9F:F6:30"? Hopefully, it will show if we can detect this phone with something other than the AT connection.
Created attachment 98336 [details] hcitool scan It looks like it's really my phone. Only plain ASCII chars (but there's a space).
Created attachment 98337 [details] sdptool browse 00:18:0F:9F:F6:30
(In reply to comment #6) > Created an attachment (id=98336) [edit] > hcitool scan > > It looks like it's really my phone. Only plain ASCII chars (but there's a > space). I have international characters and spaces in mine, and it still works fine. Could you please get a backtrace running gnome-phone-manager with "--g-fatal-warnings" as an option? (that's for the original reporter. Do you see that as well Xavier?) What's the full output of gnome-phone-manager starting up on that machine? Please try to use the latest SVN version, I just fixed a bug related to your phone (there's no Dial-Up or Serial Ports listed in the sdptool output).
I *am* the original reporter, but I reported the problem to the Debian BTS, and Francesco "escalated" it upstream (i.e. to you). Anyway, here's the backtrace. I think there'll be too many holes in there, which debug packages do you want me to install ? gdb --args gnome-phone-manager "--g-fatal-warnings" GNU gdb 6.6.90.20070912-debian Copyright (C) 2007 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (gdb) r Starting program: /usr/bin/gnome-phone-manager --g-fatal-warnings (no debugging symbols found) warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4 (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xf69676b0 (LWP 9860)] [New Thread 0xf647eb90 (LWP 9868)] [New Thread 0xf5c7db90 (LWP 9871)] ** Message: bdaddr 00:18:0F:9F:F6:30 ** Message: New connection device is 00:18:0F:9F:F6:30 (changed) [New Thread 0xf5c3cb90 (LWP 9873)] ** Message: New connection device is 00:18:0F:9F:F6:30 (not changed) ** Message: Connecting... ** Message: Status 1 ** Message: Making serial port connection conn_complete: status 0x00 GConf-CRITICAL **: gconf_engine_set_string: assertion `g_utf8_validate (val, -1, NULL)' failed aborting... Program received signal SIGABRT, Aborted.
+ Trace 174556
Thread 4137055920 (LWP 9860)
Sorry, I'm pretty sure I got confused once already, and getting confused again ;) gnome-bluetooth's debug packages should do. Thanks.
For the connection problems, we need to find which channel is being used for the AT interface, if it's still there. That's the ~/.gnokiirc: [global] port = 00:18:0F:9F:F6:30 model = AT connection = bluetooth rfcomm_channel = XXXX [logging] debug = on Try a new rfcomm_channel (from 1 to 16), and see whether "gnokii --identify" works.
2007-11-02 Bastien Nocera <hadess@hadess.net> * libgsm/phones.xml: Add the Nokia 5500 as an AT phone, until we can get something better (Closes: #475795) I'm waiting for the backtrace for the search warning.
Apparently, the warning isn't reproduceable either. Closing.