gnokii-users
[Top][All Lists]
Advanced

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

Nokia 5130c-2 given location is empty for writecalendar with one-note .i


From: gnokii
Subject: Nokia 5130c-2 given location is empty for writecalendar with one-note .ical files
Date: Mon, 24 Jan 2011 21:30:30 +0530

Hello  :-)

Trying to workaround the problem described in my previous mail with writing
an Orage export file to the phone, I tried uploading many .ical files
containing a single calendar note and found a different, possibly related
problem.

The .ical files had been written by custom VBA script run in Outlook 2003.
They had successfully been catted together into a single .ics file and
imported to Orage so are probably valid.  "Successfully" should be
qualified; I did not check all Orage Events created by the import but did
see that many had been created and a random sample looked sane.

Here's the script used to run gnokii on each .ical file:

=== script begins  ===
#!/bin/bash

# Configure script environment
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
export PATH=/usr/bin:/bin
set -o nounset
unalias -a

# Do it!
# ~~~~~~
i=0
for f in /home/c/d/tmp/Outlook/Appt-*.ical
do
    (( i++ ))
    ls -l $f
    gnokii --writecalendarnote $f $i 2>&1 | tee /tmp/gn_write.log
    sleep 1
    [[ $i -gt 20 ]] && exit
Done
=== script ends ===

The first gnokii --writecalendarnote command succeeded.  Every subsequent
one failed with "Failed to load vCalendar file: The given location is
empty."

Here's an excerpt from the script/gnokii output:

=== script/gnokii output excerpt begins ===
Found component at depth 0
Component found
BEGIN:VEVENT
ORGANIZER:MAILTO:address@hidden
DTSTART:20080721T143000Z
DTEND:20080721T171700Z
LOCATION:MMC
TRANSP:OPAQUE
SEQUENCE:0
UID:
 040000008200E00074C5B7101A82E00800000000106833EC06ECC801000000000000000010
 000000856A4F6FE829344F855DA8D78D7B7554
DTSTAMP:20110124T111348Z
SUMMARY:FILM: khuda ke liye (In the name of God)
PRIORITY:5
X-MICROSOFT-CDO-IMPORTANCE:1
CLASS:PUBLIC
END:VEVENT

WriteCalendarNote2
Message sent: 0x13 / 0x0005
00 01 00 95 00                                  |                 
Message received: 0x13 / 0x000e
01 52 00 96 00 00 00 00 0d 9a 00 00 00 00       |  R              
Received message type 13
First free position received: 13!
char_mblen(FILM: khuda ke liye (In the name of God)): 40
Message sent: 0x13 / 0x0086
00 01 00 65 00 00 00 00 00 0d 00 00 00 00 ff ff |    e            
ff ff 00 00 00 00 ff ff ff ff 02 00 07 d8 07 15 |                 
0e 1e 07 d8 07 15 0e 1e 00 00 ff ff 20 00 00 00 |                 
00 28 00 00 00 00 00 46 00 49 00 4c 00 4d 00 3a |  (     F I L M :
00 20 00 6b 00 68 00 75 00 64 00 61 00 20 00 6b |    k h u d a   k
00 65 00 20 00 6c 00 69 00 79 00 65 00 20 00 28 |  e   l i y e   (
00 49 00 6e 00 20 00 74 00 68 00 65 00 20 00 6e |  I n   t h e   n
00 61 00 6d 00 65 00 20 00 6f 00 66 00 20 00 47 |  a m e   o f   G
00 6f 00 64 00 29                               |  o d )          
Message received: 0x13 / 0x000e
01 52 00 66 00 00 00 00 00 0d 00 00 00 00       |  R f            
Received message type 13
Calendar note written at 13 location
Successfully written!
Serial device: closing device
-rw-r--r-- 1 c users 833 Jan 24 16:43 /home/c/d/tmp/Outlook/Appt-10.ical
GNOKII Version 0.6.30git
LOG: debug mask is 0x1
Config read from file /home/c/.config/gnokii/config.
phone instance config:
model = series40
port = C8:DF:7C:04:96:EA
connection = bluetooth
initlength = default
serial_baudrate = 19200
serial_write_usleep = -1
handshake = software
require_dcd = 0
smsc_timeout = 10
rfcomm_channel = 0
sm_retry = 0
Connecting
Forcing rfcomm_channel = 14 for FBUS connection
Serial device: opening device <MAC address removed>
Channel: 14
Channel: 14
Using channel: 14
Getting model...
Message sent: 0x1b / 0x0006
00 01 00 07 01 00                               |                 
Message received: 0x1b / 0x003e
01 39 00 08 00 01 58 38 00 31 56 20 30 37 2e 39 |  9    X8 1V 07.9
37 0a 31 33 2d 30 39 2d 31 30 0a 52 4d 2d 34 39 | 7 13-09-10 RM-49
35 0a 28 63 29 20 4e 6f 6b 69 61 20 20 20 20 20 | 5 (c) Nokia     
20 20 20 20 20 20 20 0a 4d 4b 00 00 00 00       |         MK      
Received message type 1b
model length: 6
Received model RM-495
Found model "RM-495"
No component found.
Failed to load vCalendar file: The given location is empty.
Serial device: closing device
=== gnokii output excerpt begins ===    

The ls -l command shows the file exists and is not empty.  One such file was
examined, its note/event identified and inspected in Orage where it looked
sane.

Assuming that gnokii was able to read and parse the .ical file, why would it
have a problem with the "location" -- presumably a
phone.calendaar.note.reminder slot -- being empty?  Shouldn't it be the
other way around -- that a non-empty slot would not be sutable for writing
to?

Here is the content of /home/c/d/tmp/Outlook/Appt-10.ical, the one that
gnokii was not able to write in the excerpt above:

=== Appt-10.ical begins ===  
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN
VERSION:2.0
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:Chennai, Kolkata, Mumbai, New Delhi
BEGIN:STANDARD
DTSTART:16010101T000000
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
TZNAME:Standard Time
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER:MAILTO:<email address removed>
DTSTART;VALUE=DATE:20060913
DTEND;VALUE=DATE:20060914
RRULE:FREQ=YEARLY;INTERVAL=1;BYMONTHDAY=13;BYMONTH=9;WKST=SU
TRANSP:TRANSPARENT
SEQUENCE:0
UID:040000008200E00074C5B7101A82E00800000000A0CE8D2AE6F0C8010000000000000000
100
 0000003C53E5187BB15438AAAA373BF4C21D8
DTSTAMP:20110124T111350Z
SUMMARY:<name removed> birthday
PRIORITY:5
X-MICROSOFT-CDO-IMPORTANCE:1
CLASS:PUBLIC
BEGIN:VALARM
TRIGGER:-PT10080M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
=== Appt-10.ical ends ===

Incidentally, before the sleep was introduced in the bash script, a gnokii
--writecalendarnote process hung and could not be killed, not even with a
kill -9 by root.  Switching Buetooth off on the phone did not help.  It was
cleared by rebooting the OS. 

Best

Charles




reply via email to

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