From Openmoko

Jump to: navigation, search

Hi, sorry, i have problem with phonelog. When i start it in the terminal i get the error

Traceback (most recent call last):
 File "/usr/bin/phonelog", line 471, in <module>
   populateList(incomingList, "incoming", last_time)
 File "/usr/bin/phonelog", line 250, in populateList
   calls = getPhonekitCallsList(type)
 File "/usr/bin/phonelog", line 141, in getPhonekitCallsList
   calls = database.execute("SELECT %s FROM calls WHERE direction = ? AND activeTime IS NOT NULL ORDER BY startTime DESC" % (get_fields, ), (CALL_STATUS_INCOMING, )).fetchall()
sqlite3.OperationalError: no such table: calls

I dont know what to set, to get logging on in ophonekitd. I use a SHR-image from 9.12.08. Do i need to use the daemon? The daemon doesn't seem to run:

Traceback (most recent call last):
 File "/usr/bin/phonelog", line 468, in <module>
   contacts = contactsObject.RetrievePhonebook("contacts")
 File "/usr/lib/python2.5/site-packages/dbus/", line 68, in __call__
   return self._proxy_method(*args, **keywords)
 File "/usr/lib/python2.5/site-packages/dbus/", line 140, in __call__
 File "/usr/lib/python2.5/site-packages/dbus/", line 622, in call_blocking
   message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

What can i do? g0m3z

For the moment, including with SHR, we should install the daemon. try to reboot he phone if the daemon doesn't work at first try.

Also note that for the moment, there's a little bug that prevents populating the list. A workaround is, line 255 in phonelog : (take care of tabulating, it's python!)

   return False

--Zupert 11:16, 13 December 2008 (UTC)

Hey G0m3z, thanks for the bug report, the issue you are referring to is known and is not from my part, but it's in SHR's daemon. I'm using a newer beta shr phonelogging daemon that is a bit different, and your version of the daemon is deprecated. Before using it with the shr daemon wait for the official release (or at least wait till they commit the changes I'm talking about). I'm in active contact with the SHR daemon's developer, don't you worry.

As for Zupert, I got a bug report concerning this issue a couple of hours ago, I'm aware of this bug and it will be solved soon, thanks for the correction as well. Anyhow, You are right about using the daemon even with SHR, I even changed the wiki to state that.

If you have any more questions, feel free to contact me. Thanks.

--Tom Hacohen 13:09, 13 December 2008 (UTC)

Ok, please check out version 0.14.0 I think it solves both of your problems, I added Zupert's check and I added a config file to choose whether to use the legacy daemon or not. --Tom Hacohen 14:09, 13 December 2008 (UTC)

Personal tools