**** BEGIN LOGGING AT Tue Sep 07 02:59:57 2010 Sep 07 09:48:29 victory! finally, I have a f3507gw! Hmm, but it might sim locked. grr Sep 07 09:53:11 That is bad luck. Sep 07 09:57:29 how do I know if it's sim locked? after enabling I see the different interfaces (SimManager, SimToolkit, CellBroadcast, ...) Sep 07 09:58:24 Check with CPIN? manually. Sep 07 09:59:09 Or check the OFONO_AT_DEBUG=1 logs for it. Sep 07 09:59:21 If you get CellBroadcast, then it is not locked. Sep 07 09:59:33 ah cool Sep 07 09:59:35 You can't get to that stage on a locked device. Sep 07 10:03:22 I think I'm hitting the API incompatiblity we have right now between ofono and connman Sep 07 10:03:39 connman head should work with ofono 0.26, right? Sep 07 10:04:19 I assume so. Sep 07 10:04:25 wagi: yes Sep 07 10:04:51 ofono-0.27 is just building right now. And then we go from there fixing up ConnMan. Sep 07 10:05:57 I hope that by the end of the week we are back to normal life. Sep 07 10:06:38 Method "SetProperty" with signature "sv" on interface "org.ofono.DataConnectionManager" doesn't exist Sep 07 10:06:47 hmm, I'm pretty sure I have 0.26 Sep 07 10:07:22 Check list-modems and that the interface is present. Sep 07 10:07:48 it's there: [ org.ofono.DataConnectionManager ] Sep 07 10:08:01 let me rebuild all, and restart Sep 07 10:11:24 the missing interface message is from shutdown sequence (stopping ofono, connman runs on) Sep 07 10:13:24 That is a known issue inside ConnMan. It is verbose there. Sep 07 10:13:29 And it should not. Sep 07 10:14:17 lunch time bbl Sep 07 10:16:03 denkenz: Around? Sep 07 12:24:30 I can connect the t-mobile sim with my option hso, but still no success using this sim together with the f3706g Sep 07 12:24:53 connman sees the device Sep 07 12:25:55 but no service Sep 07 12:26:35 "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." looks bad Sep 07 12:27:22 but that might be another false positive Sep 07 12:29:27 Check manually with activate-context, deactivate-context, list-contexts. Sep 07 12:31:56 active-context gives me: "Error activating /3563970301509080/primarycontext1: org.ofono.Error.NotAttached: GPRS is not attached" Sep 07 12:32:23 and no log activies from ofono Sep 07 12:32:30 Check the traces if CGATT actually succeeded. Sep 07 12:33:22 Try with ofono-0.27 if you happen to get a Dell card. Seems these had some issues. Sep 07 12:33:39 I'http://pastebin.com/kkLcwW8D Sep 07 12:33:46 http://pastebin.com/kkLcwW8D Sep 07 12:33:55 okay, I'll try 0.27 Sep 07 12:35:10 still not sure if the SIM lock is the problem Sep 07 12:35:20 Are you actually booked into a network. Sep 07 12:35:37 don't think so Sep 07 12:35:39 Doesn't look like it. What does list-modems say for NetworkRegistration part. Sep 07 12:36:08 http://pastebin.com/0v7hitdk Sep 07 12:36:48 I guess 'Status: unknown' in NetworkRegistration is the source of the problem Sep 07 12:36:49 # Sep 07 12:36:50 [ org.ofono.NetworkRegistration ] Sep 07 12:36:50 # Sep 07 12:36:50 Status = unknown Sep 07 12:36:50 # Sep 07 12:36:50 Mode = auto Sep 07 12:36:52 # Sep 07 12:36:54 Name = Sep 07 12:36:56 This is a problem. Sep 07 12:38:52 I found something in the booklet which came along with the modem: "In Deutschland können Sie den Dienst online aktivieren. Zu Aktivierung Ihres Dienstes sollten Sie die IMEI und ICCID_nummern der Dell Mobile Broadband-Karte parat haben." Sep 07 12:39:11 IMEI -> modem, ICCID -> SIM Sep 07 12:42:20 CardIdentifier = 89490200000453780277 ==> ICCID. Sep 07 12:43:06 Serial = 356397030150908 ==> IMEI (in case of MBM at least). Sep 07 12:43:26 But yes, ICCID is a SIM specific number. Sep 07 12:43:48 But this is stupid. That is as insane as what Apple does with the iPhone. Sep 07 13:04:55 looks like Sep 07 13:05:58 and the best thing is that I got a vodafon SIM card with the modem, but this one is PIN locked and I haven't thought the PIN in booklet so far... Sep 07 13:22:22 I have phoned with vodafon and they even don't know this vodafon-dell sim-modem bundle. I guess this card is just net locked Sep 07 13:58:15 holtmann: I am now Sep 07 14:59:07 denkenz: Got busy now. Sep 07 15:02:52 denkenz: But I wanted to talk about adding the PCM audio details to the call object. Sep 07 15:03:00 Like we do for IP settings in the context object. Sep 07 15:03:23 what kind of details? Sep 07 15:04:54 if there is traffic channel or not? Sep 07 15:04:57 Like /dev/ttyUSB1, 8000HZ, 20period. Sep 07 15:06:44 See, I think you're assuming we know this info Sep 07 15:07:07 And on something like the Freerunner there is no PCM routing Sep 07 15:07:57 The MAL could fake these, or we just read it like for Huawei. Sep 07 15:08:03 It is just an idea. Sep 07 15:08:20 If we don't have that info or the PCM is hardwired, then this is empty. Sep 07 15:11:20 This would only work for Huawei Sep 07 15:11:40 I think everything else passes the raw gsm/umts frames Sep 07 15:11:54 That is fine, then we have a type = pcm or gsm. Sep 07 15:12:09 Just some dict that can be filled with data. Sep 07 15:12:24 If it is there, great, if not also not a big deal. Sep 07 15:12:28 Except you need a driver function for it Sep 07 15:12:36 So you need to know the possible details Sep 07 15:12:43 Or a notify function callback. Sep 07 15:13:06 or that, but still, without the possible details its hard to design this Sep 07 15:13:29 I was going for something simple like device name + PCM settings for now. Sep 07 15:13:50 But we already mentioned, only Huawei is doing PCM Sep 07 15:14:09 As of now. Sep 07 15:14:24 Shrug, do you know of any other platform doing it? Sep 07 15:14:38 For things like ISI, I would just include Device = /dev/... and Type/Codec = gsm. Sep 07 15:15:15 And codec could change of course. Sep 07 15:15:40 Dunno, my feeling is we can do it as a dedicated custom interface Sep 07 15:15:47 Then again, initially I would hardcode these in the audio client. Sep 07 15:16:27 Since there are many details that could be needed, e.g. wideband vs narrowband, amr/gsm codec, timing info Sep 07 15:16:30 Just guessing here Sep 07 15:26:42 Anyway I'm not an expert, brief look into Wikipedia shows there are like 3 GSM codecs and 3 AMR codecs Sep 07 15:27:12 E.g. GSM-HR, GSM-FR, GSM-EFR, AMR, AMR-WB, AMR-WB+ Sep 07 15:27:37 The rate on all those is 8K Hz, 20ms timing Sep 07 15:27:47 So perhaps you can get away with simple device / codec notify Sep 07 15:28:52 holtmann: So I'm fine if you add those and label them experimental Sep 07 16:12:57 denkenz: Let me play with it. Sep 08 00:00:22 denkenz: ping Sep 08 00:06:27 padovan: pong Sep 08 00:08:51 denkenz: I'm having some success with DUN here, ofono_gprs_set_cid_range() solves the segfaults I had, but cid 1 doesn't work. with 2 I got this: Sep 08 00:08:55 ofonod[18526]: > AT+CGDCONT=2,"IP",""\r Sep 08 00:08:57 ofonod[18526]: < AT+CGDCONT=2,"IP",""\r Sep 08 00:09:00 ofonod[18526]: < \r\nOK\r\n Sep 08 00:09:02 ofonod[18526]: > AT+CGDATA="PPP",2\r Sep 08 00:09:05 ofonod[18526]: < AT+CGDATA="PPP",2\r Sep 08 00:09:07 ofonod[18526]: < \r\nCONNECT\r\n Sep 08 00:09:21 and then it stops Sep 08 00:09:54 denkenz: any idea on how to debug this? Sep 08 00:10:34 it has gone into PPP mode Sep 08 00:10:50 see whether PPP is reporting any debug info Sep 08 00:13:48 denkenz: do u have time to look at my stk ui? Sep 08 00:14:17 denkenz: do I have to enable ppp debug? Sep 08 00:14:36 or it is enabled by default? Sep 08 00:15:30 padovan: u need to dump log to a file and open it in wireshark Sep 08 00:16:36 see gsmdial g_at_ppp_set_recording() Sep 08 00:17:28 zhenhua: Can't promise today, maybe tomorrow Sep 08 00:17:47 padovan: Have no idea, I know gsmdial sets it, but not sure if gprs-context does Sep 08 00:31:31 denkenz: sure, no probs, we don't have icon support yet. do i need to implement that one? Sep 08 01:09:26 not yet **** ENDING LOGGING AT Wed Sep 08 02:59:59 2010