**** BEGIN LOGGING AT Tue Dec 08 02:59:56 2009 Dec 08 03:01:16 hfp_template("AT+CHUP", vc, generic_cb, 0x3f, cb, data); Dec 08 03:01:26 if you want to use hfp_hangup to release a call, Dec 08 03:01:36 then we should not pass 0x3f to hfp_template Dec 08 03:02:07 denkenz: we should pass 1 instead Dec 08 03:02:13 correct Dec 08 03:02:28 then i will make the change. Dec 08 06:20:47 denkenz: Still up? I had to go to sleep at some point. Dec 08 06:29:50 heh Dec 08 06:29:56 about to Dec 08 06:48:26 balrog-kun: Did your Option 401 come with an external antenna? Dec 08 08:52:45 ofonod[7614]: App:< \r\n_OSIGQ: 21,0\r\n Dec 08 08:52:45 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 08 08:52:45 ofonod[7614]: App:< \r\n_OSIGQ: 21,0\r\n Dec 08 08:52:45 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 08 08:52:45 ofonod[7614]: App:< \r\n_OCTI: 0\r\n Dec 08 08:52:46 ofonod[7614]: OCTI mode: 0 Dec 08 08:52:48 ofonod[7614]: App:< \r\n+CREG: 1,"5620","5EEF"\r\n\r\n+CGREG: 1,"5620","5EEF"\r\n Dec 08 08:52:50 ofonod[7614]: App:> AT+COPS=3,2\r Dec 08 08:52:52 ofonod[7614]: App:< \r\n_OSSYSI: 2\r\n Dec 08 08:52:56 ofonod[7614]: OSSYSI mode: 2 Dec 08 08:52:58 ofonod[7614]: App:< \r\nOK\r\n Dec 08 08:53:00 ofonod[7614]: App:> AT+COPS?\r Dec 08 08:53:02 ofonod[7614]: App:< \r\n+COPS: 0,2,"26201",2\r\n\r\nOK\r\n Dec 08 08:53:04 ofonod[7614]: App:> AT+COPS=3,0\r Dec 08 08:53:06 ofonod[7614]: App:< \r\nOK\r\n Dec 08 08:53:08 ofonod[7614]: App:> AT+COPS?\r Dec 08 08:53:10 ofonod[7614]: App:< \r\n+COPS: 0,0,"T-Mobile D",2\r\n\r\nOK\r\n Dec 08 08:53:14 ofonod[7614]: App:< \r\n_OSIGQ: 5,0\r\n Dec 08 16:30:40 ofonod[7614]: App:< \r\n_OSIGQ: 21,0\r\n Dec 08 16:30:40 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 08 16:30:40 ofonod[7614]: App:< \r\n_OSIGQ: 21,0\r\n Dec 08 16:30:40 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 08 16:30:40 ofonod[7614]: App:< \r\n_OCTI: 0\r\n Dec 08 16:30:40 ofonod[7614]: OCTI mode: 0 Dec 08 16:30:42 ofonod[7614]: App:< \r\n+CREG: 1,"5620","5EEF"\r\n\r\n+CGREG: 1,"5620","5EEF"\r\n Dec 08 16:30:44 ofonod[7614]: App:> AT+COPS=3,2\r Dec 08 16:30:46 ofonod[7614]: App:< \r\n_OSSYSI: 2\r\n Dec 08 16:30:48 ofonod[7614]: OSSYSI mode: 2 Dec 08 16:30:50 ofonod[7614]: App:< \r\nOK\r\n Dec 08 16:30:54 ofonod[7614]: App:> AT+COPS?\r Dec 08 16:30:56 ofonod[7614]: App:< \r\n+COPS: 0,2,"26201",2\r\n\r\nOK\r\n Dec 08 16:30:58 ofonod[7614]: App:> AT+COPS=3,0\r Dec 08 16:31:00 ofonod[7614]: App:< \r\nOK\r\n Dec 08 16:31:02 ofonod[7614]: App:> AT+COPS?\r Dec 08 16:31:04 ofonod[7614]: App:< \r\n+COPS: 0,0,"T-Mobile D",2\r\n\r\nOK\r\n Dec 08 16:31:06 ofonod[7614]: App:< \r\n_OSIGQ: 5,0\r\n Dec 08 16:31:08 Similar to the one from yesterday. Dec 08 16:31:10 ofonod[7614]: App:< \r\n_OSIGQ: 6,0\r\n Dec 08 16:31:12 ofonod[7614]: App:< \r\n_OSIGQ: 4,0\r\n Dec 08 16:31:14 ofonod[7614]: App:< \r\n_OCTI: 3\r\n Dec 08 16:31:16 ofonod[7614]: OCTI mode: 3 Dec 08 16:31:18 ofonod[7614]: App:< \r\n_OSIGQ: 18,0\r\n Dec 08 16:31:20 ofonod[7614]: App:< \r\n_OSSYSI: 0\r\n Dec 08 16:31:24 ofonod[7614]: OSSYSI mode: 0 Dec 08 16:31:26 ofonod[7614]: App:< \r\n_OSIGQ: 4,0\r\n Dec 08 16:31:28 ofonod[7614]: App:< \r\n_OSIGQ: 17,0\r\n Dec 08 16:31:30 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 08 16:31:32 ofonod[7614]: App:< \r\n_OCTI: 0\r\n Dec 08 16:31:34 ofonod[7614]: OCTI mode: 0 Dec 08 16:31:36 ofonod[7614]: App:< \r\n_OSSYSI: 2\r\n Dec 08 16:31:38 ofonod[7614]: OSSYSI mode: 2 Dec 08 16:31:41 ofonod[7614]: App:< \r\n_OSIGQ: 5,0\r\n Dec 08 16:31:42 That happened a few hours ago. Dec 08 16:31:44 ofonod[7614]: App:< \r\n_OSIGQ: 4,0\r\n Dec 08 16:31:46 ofonod[7614]: App:< \r\n_OSSYSI: 0\r\n Dec 08 16:31:48 ofonod[7614]: OSSYSI mode: 0 Dec 08 16:31:50 ofonod[7614]: App:< \r\n_OCTI: 3\r\n Dec 08 16:31:54 ofonod[7614]: OCTI mode: 3 Dec 08 16:31:56 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 08 16:31:58 ofonod[7614]: App:< \r\n_OSIGQ: 18,0\r\n Dec 08 16:32:00 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 08 16:32:02 And another one. Dec 08 16:32:04 denkenz: Anything else you need? Dec 08 16:32:27 Ooh interesting, you got a tech change without CREG in between? Dec 08 20:37:39 ofonod[7614]: App:< \r\n_OSIGQ: 18,0\r\n Dec 08 20:37:41 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 08 20:37:43 ofonod[7614]: App:< \r\n_OCTI: 0\r\n Dec 08 20:37:45 ofonod[7614]: OCTI mode: 0 Dec 08 20:37:47 ofonod[7614]: App:< \r\n_OSSYSI: 2\r\n Dec 08 20:37:51 ofonod[7614]: OSSYSI mode: 2 Dec 08 20:37:53 ofonod[7614]: App:< \r\n_OSIGQ: 5,0\r\n Dec 08 20:37:55 And another one. Dec 08 20:38:29 Btw, I'm actually at a loss of how to integrate this info into the core Dec 08 20:38:53 OSSYSI refers to GSM or UMTS access Dec 08 20:38:59 same as COPS? return Dec 08 20:39:43 When OCTI 0 seems to indicate 3G mode on your card Dec 08 20:39:55 On mine, OCTI goes to 0 when I lose signal :P **** BEGIN LOGGING AT Tue Dec 08 21:26:51 2009 Dec 08 21:33:24 booklet: RFCOMM Protocol TDI Dec 08 21:33:45 0X0A12&0001 Dec 08 21:33:58 is that part of the modem? Dec 08 21:34:59 tdibth.inf Dec 08 21:36:33 there's also a composite device 0x0c45 0x6409 mi 00 Dec 08 21:37:33 it's windows starter I can't find anything Dec 09 00:05:13 holtmann: So lets suppose network forced a detach, what's our strategy? Dec 09 00:05:27 Try to wait 10 seconds, reattach and if fails set powered=false? Dec 09 00:06:12 Sounds good to me. Dec 09 00:08:26 or do you want some sort of increasing retry-time? Dec 09 00:08:58 Also, theoretically we might fail to attach the first time too Dec 09 00:09:14 In which case what do we do, set powered off? Dec 09 00:12:20 tmzt: Do you have the Nokia booklet? Dec 09 00:12:54 denkenz: Try one approach and if it fails, we try a different one. I have no real preferences here. Dec 09 00:13:17 Nod, was just wondering whether you thought of something yet Dec 09 00:13:50 Anyway, we try that first, single retry if we're forcefully detached, otherwise go back to powered=false Dec 09 00:18:32 denkenz: so i think you have received my mail about poll_clcc in mpty call. what do u think? Dec 09 00:19:10 I didn't totally get what you were saying actually Dec 09 00:20:17 Especially this option 2 thing Dec 09 00:20:32 If we have an mpty with 2 calls, how do we know when 1 is dropped? Dec 09 00:20:34 it's simple. Dec 09 00:20:50 if 1 is dropped, then it's not a mpty call anymore Dec 09 00:21:11 Sure, but there's no indicator that is sent Dec 09 00:21:11 and ciev call_held should change. Dec 09 00:21:15 Not according to the spec Dec 09 00:21:28 call_held is still going to be 0 Dec 09 00:21:44 hmm... Dec 09 00:22:10 ok. so I think you're right. we have to choose option 1. Dec 09 00:22:27 and we don't need to poll after release_specific_cb. is that ok? Dec 09 00:22:39 because we poll it every 2 seconds Dec 09 00:23:05 So you want release specific to only be used on an mpty call Dec 09 00:23:09 Am I correct? Dec 09 00:23:18 no Dec 09 00:23:36 if ag support chld=1x, we just use it Dec 09 00:23:41 So if we haven't started a poll, should release_specific do so? Dec 09 00:24:10 Remember, release_specific has weird behavior Dec 09 00:24:20 It specifies that the held call must be accepted according to the spec Dec 09 00:24:28 Which I bet half the devices don't do Dec 09 00:25:08 don't understand why 'held call must be accepted' Dec 09 00:25:42 Recheck 4.32.1 Dec 09 00:25:54 if we are not in mpty call, we should get callsetup=0 if we release a call. shall we? Dec 09 00:26:48 The spec isn't clear Dec 09 00:27:20 If the released call was an active call and a call is currently held, the AG shall retrieve the held call. Dec 09 00:27:21 ? In the event that there are multiple held calls the AG shall retrieve the call associated with the lowest call index. Dec 09 00:27:23 ? The AG shall report the change in call status. Dec 09 00:27:46 How it reports the change is an excercise left to the reader ;) Dec 09 00:27:49 i tested on iphone. if only 1 active and 1 held, and held will become active Dec 09 00:27:55 hehe Dec 09 00:28:24 So here I don't have clear guidance Dec 09 00:28:34 Lets see if we can get away relying on the callheld indicator Dec 09 00:28:41 If not worst case we have to poll once Dec 09 00:28:46 anyway, if (!vd->clcc_source), then we schedule a poll after release_specific Dec 09 00:28:52 is that ok for u? Dec 09 00:29:04 Lets try without polling first Dec 09 00:29:10 But if it doesn't work, then yes Dec 09 00:29:21 ok Dec 09 00:31:05 and i will start thinking about modem emulator after mpty call. talk to u later once i have some ideas Dec 09 00:32:12 ok good Dec 09 01:17:23 holtmann: no, just looking at it in the store Dec 09 01:17:44 they said the software is not installed but seem to think the chipset is gobe Dec 09 01:17:52 I thought it was nokia/isi Dec 09 02:17:40 It is not Nokia ISI and I don't think it is a GOBI. Dec 09 02:17:51 I think it is a Novatel card. Dec 09 02:18:10 I am more interested if the graphics card works with Linux on it. Going to get one of these. Dec 09 02:18:30 denkenz: i just send mpty patches to ML. Let me know if any problems. Dec 09 02:22:54 ofonod[7614]: App:< \r\n_OSIGQ: 6,0\r\n Dec 09 02:22:55 ofonod[7614]: App:< \r\n_OSIGQ: 4,0\r\n Dec 09 02:22:55 ofonod[7614]: App:< \r\n_OSSYSI: 0\r\n Dec 09 02:22:55 ofonod[7614]: OSSYSI mode: 0 Dec 09 02:22:55 ofonod[7614]: App:< \r\n_OCTI: 3\r\n Dec 09 02:22:55 ofonod[7614]: OCTI mode: 3 Dec 09 02:22:57 ofonod[7614]: App:< \r\n_OSIGQ: 20,0\r\n Dec 09 02:22:59 ofonod[7614]: App:< \r\n_OSIGQ: 18,0\r\n Dec 09 02:23:01 ofonod[7614]: App:< \r\n_OSIGQ: 19,0\r\n Dec 09 02:23:03 ofonod[7614]: App:< \r\n_OCTI: 0\r\n Dec 09 02:23:05 ofonod[7614]: OCTI mode: 0 Dec 09 02:23:08 ofonod[7614]: App:< \r\n_OSSYSI: 2\r\n Dec 09 02:23:09 ofonod[7614]: OSSYSI mode: 2 Dec 09 02:23:11 ofonod[7614]: App:< \r\n_OSIGQ: 5,0\r\n Dec 09 02:23:15 Not sure how many more samples do you need. Dec 09 02:29:52 hot: it's 500 so it's still binary until the vmware/gallium driver is done Dec 09 02:30:24 holtmann: can you decdode those usb strings? vendor/product Dec 09 02:30:31 that's the baseband Dec 09 02:30:42 the usb composite device Dec 09 02:31:04 I would only get one if linux was an option Dec 09 02:31:12 and it was affordable unlocked Dec 09 02:31:30 The US one is 599 USD or so. The EU model is 799 EUR. Dec 09 02:31:56 okay cool Dec 09 02:32:12 Meaning Europe is paying double for it with the current exchange rate. Dec 09 02:32:14 it was 349 with a 2 year 60usd plan Dec 09 02:32:19 yeah Dec 09 02:32:21 sorry Dec 09 02:33:33 The composite device might be just some sort of Windows magic. Dec 09 02:34:00 We need to get someone install Linux on it to get it going. Dec 09 02:34:20 there's also a composite device 0x0c45 0x6409 mi 00 Dec 09 02:34:30 I just want lsusb -v -v Dec 09 02:34:46 I want /proc/bus/usb/devices actually. Dec 09 02:34:53 I don't have one though Dec 09 02:34:54 ok Dec 09 02:35:45 http://savago.wordpress.com/2009/11/12/nokia-booklet-3g-linux-considerations/ Dec 09 02:36:42 Maybe the modem is just some sort of Option HSO modem. Dec 09 02:36:55 Then oFono would already support it, I guess. Dec 09 02:37:01 what's the vend? Dec 09 02:37:06 0x0c45 Dec 09 02:37:31 I thought nokia was working with intel on an integrated chipset Dec 09 02:37:40 and this was the first product Dec 09 02:37:47 that's why it was interesting Dec 09 02:41:01 You are not getting me to comment on this at all, but you should know that already ;) Dec 09 02:41:46 WiFi is Atheros, Bluetooth is Broadcom and 3G seems to be Option or Novatel. CPU and graphics is Intel. Dec 09 02:42:16 I had one in my hands at the Maemo summit in Amsterdam a few month back. Really nice netbook. Dec 09 02:42:44 And the US prices are fair. The EU pricing is just stupid. For that money I get a real laptop. Dec 09 02:46:07 right Dec 09 02:46:27 cpu is intel 500, meaning powervr pci bridge Dec 09 02:46:33 no open driver Dec 09 02:46:36 gpu Dec 09 02:57:20 Yeah. That is the only sucky part. **** ENDING LOGGING AT Wed Dec 09 02:59:57 2009