[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Handling large numbers of SMS and other problems with Nokia 3500c

From: Krylov Ivan
Subject: Handling large numbers of SMS and other problems with Nokia 3500c
Date: Fri, 11 Jan 2013 22:54:13 +0400
User-agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.11) Gecko/20121123 Firefox/10.0.11 Iceape/2.7.11


I'm a user of Nokia 3500c. I usually write and receive lots of messages and tend not to delete them until phone's memory is full.

Some days ago I thought that slower phone startup can be caused by
unusually big number of messages being in the phone memory, so I wanted
to download them to my computer and delete them from phone.

First of all, 3500 classic doesn't allow SMS reading or writing through
AT-commands, so I set up priviledges for libusb:

# /etc/udev/rules.d/45-nokiadku2.rules

ACTION!="add", GOTO="nokiadku2_rules_end"
SUBSYSTEM=="usb", GOTO="nokiadku2_rules"
# This one is for the old kernels
SUBSYSTEM=="usb_device", GOTO="nokiadku2_rules"

ATTRS{manufacturer}=="Nokia", MODE="0660", GROUP="plugdev"


and enabled the dku2libusb method (I'm using a USB-miniUSB cable to
connect my phone to the computer; phone cannot be charged via miniUSB):

# ~/.config/gnokii/config

model = series40
port = 1
connection = dku2libusb

debug = on
xdebug = on

After running `gnokii --showsmsfolderstatus` program hanged for some time and returned an error: "command timed out". Enabling debug mode showed that command is not actually timing out, but the phone cannot list all messages in time before timeout reaches (file: gnokii.log.gz)

Tweaking NK6510_GETFILELIST_TIMEOUT on line 209 from 500 to 9500 in include/phones/nk6510.h of the latest git snapshot made me able to list the messages, but the program noted that values more than 1024 are very strange for it and asked to report a bug (file: gnokii.9500.log.gz).

What modifications should be done to make Gnokii handle large numbers of messages properly? I tried to move timeout setting deeper in the message handling loop (in the common/gsm-statemachine.c:__sm_block_timeout function), but that didn't help, so I had to tweak timeout instead. I guess that my C knowledge wouldn't help me with the "1024" warning either.

By the way, I have not been able to get the messages from my phone. The --get command usually returns "The given memory location is invalid" (log: gnokii.getsms.log.gz) despite messages actuallly being there; I was able to "get" the message once, but is was empty and sent and delivered in 2000 (sorry, did not save it and couldn't reproduce it later). I also received "an error in the device handling code" and "phone returned short message" a few times, and did not save these logs too, unfortunately.

Best regards,

Attachment: gnokii.9500.log.gz
Description: application/gzip

Attachment: gnokii.log.gz
Description: application/gzip

Attachment: gnokii.getsms.log.gz
Description: application/gzip

reply via email to

[Prev in Thread] Current Thread [Next in Thread]