**** BEGIN LOGGING AT Wed Dec 22 02:59:57 2010
Dec 22 17:34:02 <padovan> denkenz: holtmann: will Emulator have a DBus API?
Dec 22 17:44:07 <denkenz> padovan: I don't think so
Dec 22 17:48:42 <padovan> Yeah, I'm seeing no point on have that as well.
Dec 22 17:54:17 <padovan> denkenz: so, Ill start with DUN PTY implementation as Marcel said to me. And when I finish all the Emulator stuff and integration with PPP and AT Server we can go to BT and USB DUN
Dec 22 17:59:21 <padovan> denkenz: and if we are not going to have an API how the user can cancel a DUN link from the Server side in oFono?
Dec 22 17:59:38 <denkenz> bluez authorization?
Dec 22 18:01:16 <padovan> Yeah, that works, I forgot.
Dec 22 18:23:22 <hbragge> '
Dec 22 18:29:40 <denkenz> padovan: Ok fair enough, can you check the g_dbus_watch logic in stkagent.c, are we fine in there?
Dec 22 18:29:53 <denkenz> padovan: One other small booboo in your patch:
Dec 22 18:29:55 <denkenz> +	DBusConnection *conn =ofono_dbus_get_connection();
Dec 22 18:37:14 <padovan> denkenz: ok, I'll look into stk too.
Dec 22 18:50:17 <padovan> denkenz: src/stkagent.c is fine.
Dec 22 18:53:04 <padovan> denkenz: where in doc/features can I add an entry about modem reset? A new Modem category?
Dec 22 18:56:53 <denkenz> that sounds fine for now
Dec 22 20:05:40 <denkenz> padovan: can you pull and look at commit 3daf20216f3e16c65cc5142405477a141f64c9c3?
Dec 22 20:05:47 <denkenz> I want a second pair of eyes on that one
Dec 22 20:06:45 <padovan> Seems that kernel.org have not synced oFono repo yet.
Dec 22 20:06:55 <denkenz> nod, no hurry
Dec 22 20:22:14 <denkenz> holtmann: btw I'm mostly fine with Rafael's GPS patches
Dec 22 20:22:36 <denkenz> holtmann: Do you want to fight over naming now or ?
Dec 22 20:23:20 <holtmann> The naming should not be GPS.
Dec 22 20:23:42 <holtmann> It should more like LocationSettings or LocationControl or LocationManager or something alike.
Dec 22 20:24:04 <denkenz> We already have LocationServices
Dec 22 20:24:29 <denkenz> Or was that renamed to something else in the latest STE proposal?
Dec 22 20:25:21 <holtmann> What about LocationSettings?
Dec 22 20:26:30 <denkenz> so the main purpose behind the API is the powered on/off setting
Dec 22 20:26:47 <denkenz> And the dev node to open
Dec 22 20:27:06 <denkenz> (which is missing in the current proposal)
Dec 22 20:27:45 <denkenz> So I'd almost say like NmeaDevice
Dec 22 20:28:01 <holtmann> I does not have to be NMEA actually.
Dec 22 20:28:17 <holtmann> LocationDevice?
Dec 22 20:28:41 <denkenz> LocationReporting? LocationDevice...
Dec 22 20:29:16 <holtmann> I like LocationDevice actually.
Dec 22 20:30:10 <padovan> I agree with Marcel in LocationDevice
Dec 22 20:30:20 <denkenz> personally I like LocationReporting more
Dec 22 20:30:45 <denkenz> LocationReportingDevice? lol
Dec 22 20:31:18 <holtmann> That one is too long ;)
Dec 22 20:31:46 <denkenz> After SupplementaryServices nothing is too long
Dec 22 20:31:53 <holtmann> LocationReporting is fine with me as well, but LocationDevice seems reasonable since essentially we are talking about a GPS device.
Dec 22 20:32:04 <holtmann> The SS one is crazy, blame 3GPP.
Dec 22 20:32:52 <denkenz> dunno, LocationDevice doesn't convey the same meaning to me, but then LocationReporting can also be confused with certain network location requests
Dec 22 20:33:12 <denkenz> so I'm fine either way
Dec 22 20:34:13 <denkenz> we'll change it in a month anyway ;)
Dec 22 20:35:18 <holtmann> Could be.
Dec 22 20:42:03 <denkenz> Ok, so unless someone has better ideas I'm going with LocationReporting
Dec 22 20:42:23 <denkenz> we also need to add at least string Device and string Type
Dec 22 20:42:28 <denkenz> to properties
Dec 22 20:46:00 <padovan> Does Device need NMEA to be retrivied? If we are talking about a NMEA device
Dec 22 20:48:32 <denkenz> sorry, not following?
Dec 22 20:50:58 <padovan> I'm asking about the Device property. How is it value retrived from the GPS device?
Dec 22 20:51:27 <denkenz> its the tty where the NMEA stream is being piped
Dec 22 20:51:37 <denkenz> so in the case of mbm it might be /dev/ttyACM2
Dec 22 20:52:35 <padovan> That answers, thanks.
Dec 22 20:55:27 <denkenz> the other thing that mbm supports is setting the update frequency in seconds
Dec 23 01:16:50 <padovan> +       case MODEM_STATE_PRE_SIM:
Dec 23 01:16:50 <padovan> +               modem->driver->set_online(modem, 1, NULL, NULL);
Dec 23 01:16:52 <padovan> +               break;
Dec 23 01:17:10 <padovan> denkenz: I didn't get this part of your patch
Dec 23 01:17:40 <denkenz> Basically if we go online and the user removes the SIM
Dec 23 01:17:44 <denkenz> we should go offline
Dec 23 01:17:49 <denkenz> But I actually screwed this up
Dec 23 01:17:54 <denkenz> should be 0 not 1 :P
Dec 23 01:17:59 <sabotage> is there a way to dump the IMEI# for the modem?
Dec 23 01:19:00 <denkenz> sabotage: see Modem Serial property
Dec 23 01:19:44 <sabotage> ok, thought so, but didn't have one already known for this new device to be sure
Dec 23 01:21:48 <padovan> denkenz: Okay, for the Set(powered, false) and Set(Lockdown, true) a under reset flag could work to fix the race condition. But that doesn't cover the remove sim action.
Dec 23 01:21:57 <padovan> So your patch is godd, fix all cases
Dec 23 01:22:01 <padovan> :)
Dec 23 01:22:56 <denkenz> except for screwing up the offline bit :P
Dec 23 01:23:05 <sabotage> denkenz: ok, next question... trying to online the modem, I'm getting:
Dec 23 01:23:07 <sabotage> org.ofono.Error.NotAvailable: Operation currently not available
Dec 23 01:23:18 <sabotage> what could be preventing this?
Dec 23 01:23:24 <padovan> sabotage: first power it up
Dec 23 01:23:24 <sabotage> worked last boot ;)
Dec 23 01:23:27 <sabotage> it is
Dec 23 01:23:34 <sabotage> Powered = 1
Dec 23 01:23:39 <denkenz> You cannot go online until the sim initialization is complete
Dec 23 01:23:53 <denkenz> so either the pin is locked or you're too fast
Dec 23 01:24:10 <sabotage> no pin lock on the SIM
Dec 23 01:24:18 <sabotage> been powered up for a while now
Dec 23 01:24:22 <sabotage> 7-10 min
Dec 23 01:24:42 <padovan> and kernel.org is really slow today... :(
Dec 23 01:25:26 <sabotage> only diff is this boot, I have ofonod running backgrounded with -n -d * and OFONO_*_DEBUG set... all logging to a /tmp file
Dec 23 01:25:43 <sabotage> so could be buffer blocked?!?!
Dec 23 01:29:15 <denkenz> doubtful
Dec 23 01:29:37 <denkenz> what does list-modems say?
Dec 23 01:29:41 <sabotage> ok, well running it w/out all that, and the modem powers up and onlines at boot
Dec 23 01:30:06 <sabotage> fav pastebin server?
Dec 23 01:30:13 <denkenz> pick one
Dec 23 01:31:54 <sabotage> 1) http://pastebin.ca/2026790
Dec 23 01:31:56 <sabotage> 2) http://pastebin.ca/2026792
Dec 23 01:32:29 <sabotage> 1) was while running ofonod -n -d '*' > /tmp/log 2>&1 from rc.sysinit
Dec 23 01:32:47 <sabotage> 2) was normal, ie just ofonod, from sysinit
Dec 23 01:34:46 <denkenz> go figure, somehow the modem failed to init in the first log
Dec 23 01:34:58 <sabotage> meh :/
Dec 23 01:35:00 <denkenz> the at log might tell why
Dec 23 01:35:11 <sabotage> my luck... crappy HW
Dec 23 01:35:28 <sabotage> I have that too... what would I look for?
Dec 23 01:35:34 <denkenz> maybe a command stalled our parser?
Dec 23 01:37:44 <sabotage> I haven't the foggiest what I'm looking for in the log... so, not sure what to tell ya
Dec 23 01:38:12 <sabotage> I did note that buffering to the log seemed to stop as soon as I tried testing a voicecall
Dec 23 01:40:31 <denkenz> generally parser stalls if the modem sends something whacky
Dec 23 01:40:38 <denkenz> like an invalid number of crlfs or something
Dec 23 01:48:29 * sabotage kicks POS device and it's flakey and inconsistently working i2c/touch/kboot/etc...
Dec 23 02:04:31 <sabotage> denkenz: so from what I can see, I'm getting a remote disconnect immediately after dialing
Dec 23 02:05:21 <sabotage> and calling my sim #, I never get signaling in ofono, and after the noreply timeout, get sent to voicemail
Dec 23 02:05:52 <sabotage> so I'm actually wondering if my sim/IMEI is being barred by the carrier (or network?)
Dec 23 02:06:25 <denkenz> doubtful
Dec 23 02:06:29 <denkenz> probably your signal sucks
Dec 23 02:06:32 <sabotage> I've got another sim I can borrow tomorrow that was confirmed to work yesterday, but that person is out until the morning
Dec 23 02:06:48 <sabotage> so I'll swap sims and try again tomorrow
Dec 23 02:07:17 <sabotage> ofono-monitor tells me the signal is ranging between 4-6
Dec 23 02:07:33 <denkenz> 4-6 percent?
Dec 23 02:07:42 <denkenz> that's pretty crap ;)
Dec 23 02:08:00 <sabotage> whatever "Strength" means when it says 6
Dec 23 02:08:14 <denkenz> yeah, percent
Dec 23 02:08:28 <sabotage> oh, I thought it was between 1-10 /// oops ;)
Dec 23 02:08:49 <sabotage> ofono-monitor says: {VoiceCall} [/ifx0/voicecall01] DisconnectReason remote
Dec 23 02:09:08 <sabotage> upon placing a dial request (which did return success)
Dec 23 02:09:20 <denkenz> I'd need the at log
Dec 23 02:09:41 <denkenz> maybe the network is overloaded, or maybe you have no credit
Dec 23 02:09:42 <denkenz> no idea
Dec 23 02:10:33 <sabotage> nod
Dec 23 02:11:15 <sabotage> sim is unlimited voice/data plan... but, well like you said... hard to be sure
Dec 23 02:11:44 <denkenz> does seem strange that it times out though
Dec 23 02:11:58 <denkenz> however, its been known to happen in low signal conditions
Dec 23 02:12:20 <denkenz> my iPhone sometimes takes ~20 seconds to tell me the call failed
Dec 23 02:12:32 <sabotage> sure... yet another problem with pre-prodcution HW... poor antenna placement
Dec 23 02:13:21 <sabotage> I'm going to try on previous version of the HW, same sim/OS, and see what happend
Dec 23 02:13:26 <sabotage> happens
Dec 23 02:14:10 <denkenz> nod
Dec 23 02:28:58 <sabotage> ok denkenz, no matter how I try running ofonod -n -d '*' from root ssh session, it always seems to hang at:
Dec 23 02:29:00 <sabotage> Timeout with multiplexer setup
Dec 23 02:29:15 <sabotage> and the modem can't be powered
Dec 23 02:29:28 <sabotage> both versions of the HW
Dec 23 02:30:07 <sabotage> oh, and my test failed again... same behavior, remote disconnect on outgoing calls, never any incoming signaling
Dec 23 02:30:12 <denkenz> holtmann might know that one, he wrote that driver
Dec 23 02:30:23 <holtmann> Which one?
Dec 23 02:30:32 <sabotage> IFX
Dec 23 02:31:15 <holtmann> That one needs a modem reset since the IFX kernel driver for the TTY is stupid. It shits itself when you call close() on /dev/ttyIFX0.
Dec 23 02:31:24 <sabotage> this used to work on the EB2, but now getting immediate remote disconnects
Dec 23 02:31:31 <holtmann> There is a script somewhere to toggle the GPIOs.
Dec 23 02:31:39 <sabotage> I'm getting this on two devices
Dec 23 02:31:50 <holtmann> Still on EB2?
Dec 23 02:31:54 <sabotage> ok, hints where to find it?
Dec 23 02:32:00 <sabotage> and EB3
Dec 23 02:32:15 <holtmann> Don't have an EB3.
Dec 23 02:32:41 <sabotage> fair enough, but behavior is consistent between the two
Dec 23 02:33:23 <holtmann> EB3 is still a 6260 and you have initial modem firmware programmed in? Our EB2 came with no modem firmware. And then nothing works.
Dec 23 02:34:26 <holtmann> If your EB3 is modem firmware less, you are in for a treat. I have no idea on how to fix this. Fred did it for us.
Dec 23 02:35:16 <chenmin> sabotage: what problem you met? I also met some problem about SIM card.
Dec 23 02:37:53 <sabotage> holtmann: yeah, I had the "fun" of initial modem flashing with EB2
Dec 23 02:38:13 <sabotage> EB3 appears to come preloaded and with IMEI programmed too
Dec 23 02:38:31 <holtmann> Nice. At least something.
Dec 23 02:41:52 <sabotage> chenmin: still trying to determine if it's the SIM, the FW/Driver or just signal issues
Dec 23 02:46:21 <denkenz> if you get past the point of having an IMSI, then it isn't a sim issue
Dec 23 02:46:26 <chenmin> sabotage: Ok, I haven't follow IRC these days, but I have met a problem that a series of SIM card doesn't work in N900 both in Maemo and Meego OS
Dec 23 02:47:04 <chenmin> signal can be found. but call cannot be made, is it similar to your issue?
Dec 23 02:47:37 <chenmin> sabotage: BTW, what HW do you use?
Dec 23 02:47:42 <sabotage> meh... mine *could* just be this: Strength = 1 on the network :/
Dec 23 02:49:05 <chenmin> what about registor to network?
Dec 23 02:49:19 <sabotage> denkenz: not clear on what "having an IMSI" means... 
Dec 23 02:49:40 <sabotage> yeah, registration seems fine
Dec 23 02:50:00 <sabotage>     [ org.ofono.NetworkRegistration ]
Dec 23 02:50:03 <sabotage>         Status = registered
Dec 23 02:50:05 <sabotage>         Strength = 1
Dec 23 02:50:07 <sabotage>         Name = AT&T
Dec 23 02:50:08 <denkenz> lets put it this way, if you're receiving signal strength, then the problem isn't the SIM ;)
Dec 23 02:50:09 <sabotage>         LocationAreaCode = 33998
Dec 23 02:50:11 <sabotage>         Mode = auto
Dec 23 02:50:13 <sabotage>         MobileCountryCode = 310
Dec 23 02:50:15 <sabotage>         Technology = hspa
Dec 23 02:50:17 <sabotage>         CellId = 13765841
Dec 23 02:50:18 <sabotage> ok ;)
Dec 23 02:50:46 <sabotage> w00t! "Strength = 0"
Dec 23 02:51:02 * sabotage needs longer wires, an antenna or both
Dec 23 02:51:28 <sabotage> having none, calling it a night and trying again in the morning
Dec 23 02:54:11 <denkenz> balrog-k1n: Where's my DisplayActionInfo patch? ;)
**** ENDING LOGGING AT Thu Dec 23 02:59:58 2010