**** BEGIN LOGGING AT Thu Mar 18 02:59:56 2010 Mar 18 05:31:00 holtmann, denkenz I meet below error when starting ofonod. "symbol lookup error: ofonod: undefined symbol: g_malloc0_n" I think it should come from the old version of glibc. My glibc version is 2.11.90. Can you point to me which version of glibc or other lib I need to upgrade? Thx Mar 18 05:36:33 holtmann, denkenz, BTW I have install the latest glibc and glib2 in MeeGo Mar 18 09:45:50 holtmann, denkenz it should be the MeeGo image issue, after I install the latest image. The issue gone. ;-) Mar 18 09:59:23 holtmann, denkenz, it seems that MobileNetworkCodeLength is not implemented by hso driver that broke the HSO 3G feature of ConnMan. Could you have a look at it? THX Mar 18 11:07:54 martin_lab: The HSO thing is weird. It is an entry on the SIM card. Mar 18 11:08:04 Can you send OFONO_AT_DEBUG=1 logs for that. Mar 18 14:38:15 holtmann, martin_lab: HSO doesn't support SIM card reading actually Mar 18 14:41:30 denkenz: Can we fix it, or is this a real hardware limitation. Mar 18 14:43:09 AFAIK it simply doesn't implement CRSM properly Mar 18 14:43:57 Let me play with it again, but that is what I remember Mar 18 14:45:05 Then we need to figure out some magic for IMSI to MCC/MNC conversion :( Mar 18 14:58:25 There's no real magic except to get country code database into oFono Mar 18 14:58:36 And by the way, there are other modems that screw this up Mar 18 14:58:50 Namely Freerunner's CRSM implementation is completely broken Mar 18 15:06:49 The other alternative is to have UI ask the user when ImsiLength is not found Mar 18 15:09:32 Yes. That is best properly. Mar 18 19:47:08 denkenz: ping Mar 18 19:51:15 jprvita: pong Mar 18 19:55:10 now i've tested with a gsm chip and sms works, but i've got the same message 3 times Mar 18 19:55:19 denkenz: http://pastebin.ca/1844937 Mar 18 19:55:41 the log says Sending failed, retry in X secs Mar 18 19:55:59 and I've got an incoming SMS too :) Mar 18 19:59:08 Sometimes the SMS fails to send, are you saying it actually got received 3 times? Mar 18 19:59:27 yes, i've received the same message 3 times in a row Mar 18 19:59:49 Can you test it again using OFONO_AT_DEBUG Mar 18 19:59:51 jprvita: Welcome to the world of broken basestations and GSM modem firmware. Mar 18 19:59:58 I want to see what the modem tells us Mar 18 20:00:03 Wait until you receive a SMS 120 times. Mar 18 20:00:10 holtmann: hahaha Mar 18 20:00:14 This works fine elsewhere ;) Mar 18 20:00:25 denkenz: i'll redo the test Mar 18 20:01:07 denkenz: It is something weird when modem sends SMS and basestations are switched etc. The network gets confused. I have seen that. Mar 18 20:01:23 It could be also oFono's fault, but the network can be screwed up, too. Mar 18 20:02:09 Well we rely on the modem here Mar 18 20:02:25 So it could be our fault, but if the modem says ERROR, then we have to respect that Mar 18 20:05:08 hum, from what I can read from the logs the modem says OK Mar 18 20:05:12 will pastebin Mar 18 20:05:50 http://pastebin.ca/1844950 Mar 18 20:07:20 eww Mar 18 20:07:50 I've got it 4x this time Mar 18 20:08:05 so the driver is getting confused Mar 18 20:08:09 I guess I'm on the way to 120 :/ Mar 18 20:08:35 And that's because the modem is fucking stupid Mar 18 20:08:54 huahua, ok, i can tell him ;) Mar 18 20:09:00 Are you using the V1 parser or the permissive one? Mar 18 20:09:13 hum, how do I know that? Mar 18 20:09:41 which driver are you using to connect? Mar 18 20:09:41 everything was autodetected Mar 18 20:10:12 huawei I guess, from the logs and object path Mar 18 20:11:09 ok, change huawei's plugin to use g_at_syntax_new_permissive instead of g_at_syntax_new_gsmv1 Mar 18 20:11:11 Then retry Mar 18 20:11:17 plugins/huawei.c Mar 18 20:12:33 ok Mar 18 20:15:31 fg Mar 18 20:19:14 And I need to look into why gatchat actually returns with an error there, it should stall... Mar 18 20:20:41 now the sms interface is not registered and I got several AT erros on the log: http://pastebin.ca/1844959 Mar 18 20:21:27 this is what was changed: Mar 18 20:21:27 - syntax = g_at_syntax_new_gsmv1(); Mar 18 20:21:27 + syntax = g_at_syntax_new_gsm_permissive(); Mar 18 20:21:59 sweet Mar 18 20:22:02 reset your phone Mar 18 20:22:22 un-plug / re-plug? Mar 18 20:22:32 it's a usb modem Mar 18 20:22:39 Yeah Mar 18 20:22:48 It sounds like we need to let it settle after CFUN=1 Mar 18 20:26:10 hum, now I'm getting some RSSI and BOOT messages and list-modems fails like if ofonod wasn't running Mar 18 20:26:34 after powering the modem Mar 18 20:28:37 err, sounds like wrong firmware Mar 18 20:28:42 http://pastebin.ca/1844976 Mar 18 20:29:14 Actually it looks fine Mar 18 20:29:52 RSSI is probably some proprietary signal strength stuff Mar 18 20:29:57 No idea what BOOT is Mar 18 20:30:38 hum, this modem doesn't report nothing through the strength property Mar 18 20:30:57 the property doesn't exist under NetworkRegistration Mar 18 20:31:05 The driver needs to be updated Mar 18 20:31:19 The huawei modems aren't properly supported, that is the reason Mar 18 20:31:25 Mostly because I don't have one :) Mar 18 20:31:33 hehe Mar 18 20:32:04 hum, weird, org.ofono doesn't show on the system bus.. Mar 18 20:32:35 valgrind, maybe we did something stupid Mar 18 20:33:44 ok, an ofono restart solved this problem.. no idea what happened tho Mar 18 20:34:04 and now I have SmsManager interface! will test Mar 18 20:37:00 denkenz: nice, problem seems solved: http://pastebin.ca/1844987 Mar 18 20:37:29 good, feel free to submit that patch Mar 18 20:37:42 I still need to figure out why we're returning false there, sigh :P Mar 18 20:38:06 In theory the parser should just stall and the invalid modem response should be quickly spotted Mar 18 20:38:07 denkenz: ok, will send it now Mar 18 20:38:15 Instead of being charged for 7 SMSes ;) Mar 18 20:38:52 hehe, don't worry, I've just got a sim card at work for these tests :) **** BEGIN LOGGING AT Thu Mar 18 22:39:53 2010 **** ENDING LOGGING AT Fri Mar 19 02:59:56 2010