**** BEGIN LOGGING AT Fri Aug 06 02:59:58 2010 Aug 06 03:26:26 any N900 oFono devs alive yet? Aug 06 04:04:37 cool, the Calypso handles Send Short Message and the like for us, and just lets us know using %SATN Aug 06 04:05:08 it also sends the End Session very reliably like the MBM Aug 06 04:31:27 morning Aug 06 04:59:10 … Aug 06 05:36:51 luke-jr: I saw pessi here a couple of days ago **** ENDING LOGGING AT Fri Aug 06 05:44:27 2010 **** BEGIN LOGGING AT Fri Aug 06 08:30:14 2010 **** ENDING LOGGING AT Fri Aug 06 08:30:21 2010 **** BEGIN LOGGING AT Fri Aug 06 08:32:14 2010 Aug 06 12:51:31 kvalo: Do the Huawei changes work fine for you? Aug 06 12:52:43 holtmann: yeah, no regressions. I sent mail earlier today Aug 06 12:52:55 Haven't read emails yet. Aug 06 12:53:15 holtmann: still issues with pin lock, but that has been broken for huawei since I broke it (I think) Aug 06 12:53:23 kvalo: I just saw your email, strange that it worked fine for me with pin locked sims Aug 06 12:53:48 Can you fix it? Aug 06 12:53:54 jprvita: firmwares can work differently Aug 06 12:54:11 at least I could start ofono with a pin-locked sim on my modem, use enter-pin to unlock it and have all the interfaces shown Aug 06 12:54:29 jprvita: definitely your patch improved things, but something is still wrong Aug 06 12:54:38 kvalo: yes, the hell of different firmwares :( Aug 06 12:55:26 I will leave in ~1h for the weekend, so I can't look at more about ofono this week Aug 06 12:59:30 kvalo: from what you said, after restarting ofono you could use your data connection from connman.. Aug 06 13:00:04 doesn't it seem more related to the pin unlock notifications than to the huawei plugin itself? Aug 06 13:01:21 jprvita: can't say Aug 06 13:01:22 btw, I haven't tested with connman (not using it ATM), just saw ofono reported the pin as unlocked on SimManager interface properties and all other atoms were successfully added Aug 06 13:01:37 what about ./list-context? Aug 06 13:02:21 IIRC that was empty for me after I entered the pin Aug 06 13:02:49 this for data-only right? I've been testing with voice-only sims most of the time Aug 06 13:02:54 I can check this, tho Aug 06 13:03:00 just a minute Aug 06 13:07:11 jprvita: the pin locked elisa sim support both voice and data, but I'm sure my huawei modem only supports data Aug 06 13:08:32 * jprvita trying to figure out the default PIN for "Oi" operator, brazil :/ Aug 06 13:20:07 kvalo: couldn't figure what my PIN is, but anyway, no contexts get automatically created even for unlocked-sims Aug 06 13:20:33 I'm testing this with huawei E156C Aug 06 13:24:45 I guess connman would do this part and manage the context, right? Aug 06 14:41:17 jprvita,kvalo: Interesting that the E1552 reports 255 as the sim state, e.g. not present Aug 06 14:41:54 yes, I've noticed that on kvalo's 1st attempt Aug 06 14:42:16 but on the 2nd it reports 0 (sim locked), when ofono prompts for PIN Aug 06 14:47:00 Yeah, this is cold-boot Aug 06 14:47:11 Probably his firmware doesn't update the state Aug 06 14:48:02 It might be worth it to re-run the SYSINFO query about 1-2 seconds later if the modem reports sim state of 255 Aug 06 14:48:21 Perhaps oFono is simply too fast ;) Aug 06 14:57:39 jprvita: ConnMan will auto-create a context right now. This needs changing of course, but in theory the context should show up. Aug 06 14:58:32 holtmann: if I had connman running ;) Aug 06 14:59:01 Yes. Aug 06 14:59:24 If we end up having a better provider database, then oFono can do that hopefully at some point by itself. Aug 06 14:59:34 We will see. It is bit tricker than one would think. Aug 06 15:00:37 does it make sense? who would handle the data connection then? I guess you don't want to add all of this to ofono Aug 06 15:13:19 Provisioning the context data is different than handling data Aug 06 16:54:54 hello, devs Aug 06 17:01:23 pessi, q. about isimodem-driver... isimodem.c:mtc_state_cb intended to be called once? if so, when callback for ofono core is actually called if cause is MTC_OK? Aug 06 17:24:57 my sim card is sending a DisplayText "Do you agree to send an SMS to 7575?" and waits for an Ok or a Go back Aug 06 17:25:18 so i think the DisplayText request does need the fourth parameter Aug 06 17:28:48 I'm thinking that the UI should always provide an OK button Aug 06 17:30:05 And really the SIM application is being stupid, it should use GetInkey for this Aug 06 17:39:22 Hi, I have a question re: patch submission process. If there's a feature change that spans the whole architecture - is it ok to submit it as a single patch or do you prefer to have it split up into several patches in some way, e.g. as per directory structure? Aug 06 17:41:05 daradoyle: If you're changing the oFono driver API, then it gets a bit more complicated Aug 06 17:41:39 In general we prefer the build not to break with any commit to make git bisect work Aug 06 17:41:49 However, if the changes are extensive, then multiple patches are still preferred Aug 06 17:42:33 ok great, thank you Aug 06 17:58:07 patches? why not just a pull request? Aug 06 17:58:41 pessi: ping **** ENDING LOGGING AT Sat Aug 07 02:59:57 2010