Could it be that there's still some timing issue with ophonekitd?
I have updated ophonekitd to
> r...@om-gta02 ~ $ opkg list_installed ophonekitd
> ophonekitd - 0.0.1+gitr577+7e705882c099f353cf6ce535c222b7fee56b48b8-
> r15 -
which seems to be latest as of right now.
However, depending on my location it seems that ophonekitd succeeds to
register with the network or not. It finally seems to be able to
connect to the network since the network is displayed in the top bar
of illume and I can make calls with the dialer. But reading the SIM's
contacts and phone log failed and the contact list is empty and the
phone log app tends to crash.
In my apartment I seem to have a weak GSM signal and then ophonekitd
has the trouble described above.
In the office I have better reception and there ophonekitd behaves
nicely and I've got a working phone (including phonebook, etc.)
Here's the log of ophonekitd when it's failing:
> ** (process:1788): DEBUG: request_resource_callback()
> ** (process:1788): DEBUG: call ogsmd_device_set_antenna_power()
> ** (process:1788): DEBUG: sim_ready_status_callback(status=0)
> ** (process:1788): DEBUG: ophonekitd_sim_ready_status_handler()
> ** (process:1788): DEBUG: ophonekitd_sim_auth_status_handler()
> ** (process:1788): DEBUG: sim auth ready
> ** (process:1788): DEBUG: power_up_antenna_callback()
> ** (process:1788): DEBUG: register_to_network_callback()
> ** (process:1788): DEBUG: Registering to network failed: TODO
> org.freesmartphone.GSM.Device -2
> ** (process:1788): DEBUG: ophonekitd_sim_ready_status_handler()
> ** (process:1788): DEBUG: sim ready
> ** (process:1788): DEBUG: get_messagebook_info_callback()
> ** (process:1788): DEBUG: MessageBookInfo failed: 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. dbus -2
Is it normal that it tries to register with the network and *then*
reports "sim ready"?
At the same time (I think just before the message "Registering to
network failed") I get the following errors in frameworkd.log:
> 2009.02.24 00:16:05 ogsmd.channel DEBUG
> : got 12 bytes from: '\r\n
> +CREG: 2\r\n'
> 2009.02.24 00:16:10 ogsmd.channel DEBUG
> : sending 11 bytes: 'AT
> +CSMS=1\r\n'
> 2009.02.24 00:16:10 ogsmd.channel DEBUG
> : got 19 bytes from: '\r\n
> +CMS ERROR: 314\r\n'
> 2009.02.24 00:16:10 ogsmd.channel DEBUG
> : COMPLETED 'AT+CSMS=1'
> => ['+CMS ERROR: 314']
> 2009.02.24 00:16:10 ogsmd.channel DEBUG
> : sending 19 bytes: 'AT
> +CNMI=2,1,2,1,1\r\n'
> 2009.02.24 00:16:10 ogsmd.channel DEBUG
> : got 19 bytes from: '\r\n
> +CMS ERROR: 314\r\n'
> 2009.02.24 00:16:10 ogsmd.channel DEBUG
> : COMPLETED 'AT
> +CNMI=2,1,2,1,1' => ['+CMS ERROR: 314']
> 2009.02.24 00:16:14 ogsmd.channel DEBUG
> : got 16 bytes from:
> '%CSTAT: PHB, 0\r\n'
(I left out the lines with "_readyToRead: watch timeout = None" on
purpose for better readability)
The modem firmware should still be
gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0.
> * The Digital Pioneer [090223 19:11]:
>> I thought it was ophonekitd's job to do stuff like that. What do I
>> run? And
>> why on earth would I have to manually enable GSM on a phone? Heheheh
> you don't... its exactly what ophonekitd does. We fixed some stuff in
> the startup sequence of ophonekitd lately... you might want to try to
> update & upgrade.
>
> mrmoku
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
