| 01:13.23 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |
| 01:33.45 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |
| 02:50.02 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |
| 06:27.58 | *** join/#openezx gDD (~gDD@unaffiliated/gdd) |
| 07:27.24 | *** join/#openezx ao2 (~ao2@cl-35.trn-01.it.sixxs.net) |
| 07:49.07 | *** join/#openezx file (~file@asterisk/developer-and-muffin-lover/file) |
| 07:50.14 | *** join/#openezx florian (~fuchs@port-217-146-132-69.static.qsc.de) |
| 07:50.15 | *** join/#openezx florian (~fuchs@Maemo/community/contributor/florian) |
| 08:39.59 | *** join/#openezx gDD (~gDD@unaffiliated/gdd) |
| 09:59.46 | ao2 | mickey|bbl, after your last change: [CRITICAL] FreescaleNeptuneModem <4C>: Requested AT command CUSTOM unknown |
| 10:00.54 | ao2 | and fsogsmd terminates (which halts a1200, but that's a kernel problem) |
| 10:05.11 | ao2 | I am now try adding the "CUSTOM" command handler back |
| 10:13.23 | ao2 | ok, that seems to prevent fsogsmd to terminate, but initialization is still not ok, I get this when launching the script: |
| 10:13.25 | ao2 | dbus.exceptions.DBusException: org.freesmartphone.Unavailable: This function is not available while modem is in state FSO_GSM_MODEM_STATUS_INITIALIZING |
| 10:15.22 | ao2 | btw the patch to prevent fsogsmd to halt is this: http://pastebin.com/1BXKyZbW |
| 10:15.49 | ao2 | s/to halt/from halting/ |
| 11:12.04 | *** join/#openezx gDD (~gDD@unaffiliated/gdd) |
| 11:17.36 | mickey|bbl | ao2: FSO_GSM_MODEM_STATUS_INITIALIZING this is what i would expect |
| 11:18.04 | mickey|bbl | to prevent you from sending commands while the modem is not ready |
| 11:18.18 | mickey|bbl | btw., most other apps do this by waiting for the proper modem state to arrive via signal |
| 11:19.28 | mickey|bbl | like i said, we can work about 'RequestResource' only coming back after the modem is in the proper state |
| 11:19.35 | mickey|bbl | (eventually) |
| 11:43.57 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |
| 12:17.26 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |
| 12:19.20 | *** join/#openezx lclaudio (~lclaudio@201.86.10.12.dynamic.adsl.gvt.net.br) |
| 12:42.09 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |
| 12:51.37 | ao2 | mickey|bbl, so my app should either retry or listen for the "available" signal? |
| 12:51.48 | mickey|bbl | yes |
| 12:52.11 | mickey|bbl | the problem with delaying the ResourceRequest answer so long is that many people have ridicolously configured (default) dbus timeouts |
| 12:54.39 | ao2 | mickey|bbl, I am ok with any behavior as long as it is documented. Will the spec tell that RequestResource may return even if the resource is not actually "ready" yet? |
| 12:56.24 | mickey|bbl | ao2: yes, i will add to the spec that there are resource-specific subtypes of "readyness" which means resource access will lead to domain specific errors even though the resource has been successfully requested |
| 12:56.33 | mickey|bbl | s/will/could/ |
| 12:56.37 | mickey|bbl | err |
| 12:56.41 | mickey|bbl | ~lart purl |
| 12:56.41 | purl | whips mickey|bbl with a wet and grimy noodle just because |
| 12:56.56 | ao2 | feudian... |
| 12:57.09 | ao2 | s/feudian/freudian/ |
| 12:57.27 | ao2 | :) |
| 12:59.30 | mickey|bbl | hehe |
| 16:12.17 | *** join/#openezx toi (~toi@d54C2AA76.access.telenet.be) |
| 16:54.38 | *** join/#openezx florian (~fuchs@Maemo/community/contributor/florian) |
| 21:47.41 | *** join/#openezx mickey|bbl (~mickey@80.81.242.146) |
| 23:55.49 | *** join/#openezx EuroTrash (~rtrsh@82-169-3-152.ip.telfort.nl) |