**** BEGIN LOGGING AT Fri May 15 02:59:58 2009
May 15 03:00:04 <astrocub> i'm going to get a phone that supports omoko sometime, probably around october when my plan expires
May 15 03:01:09 <astrocub> in the meantime, i'll go ahead and grab the chdk enabled camera
May 15 03:01:23 <astrocub> need a camera more than anything atm
May 15 03:03:09 <astrocub> isn't it possible for an enthusiast such as myself to build the freerunner?
May 15 03:06:25 <astrocub> http://wiki.openmoko.org/wiki/Wishlist:Camera
May 15 03:10:41 <SpeedEvil> build the?
May 15 03:27:05 <DocScrutinizer> hmm, puzzling
May 15 03:38:52 <slaxxer> wassa doc
May 15 03:39:10 <slaxxer> anybody hear from Dave?
May 15 03:45:46 <Toaster`> Arg... contacts is crashing
May 15 04:01:52 <slaxxer> opkg upgraded testing-shr     recon the shutdown menu works?
May 15 04:06:10 <slaxxer> still dont work
May 15 04:24:54 <slaxxer> dave
May 15 04:25:08 <slaxxer>      D                                        a                                          v                                   e
May 15 07:53:54 <Hopscotch> good morning
May 15 08:54:41 <Psi_> http angstrom-dist feed down for anyone else?
May 15 09:28:24 <Psi_> does anyone have a dosbox binary for the neo?
May 15 09:29:07 <lindi-> Psi_: apt-get install dosbox
May 15 09:29:28 <Psi_> how that going to work
May 15 09:30:21 <Psi_> opkg list | grep dosbox has nothing
May 15 09:34:47 <lindi-> Psi_: with apt-get
May 15 09:34:57 <Psi_> there is no apt-get
May 15 09:35:01 <Psi_> atleast, not on shr
May 15 09:39:06 <Zorkman> Psi_: you can request a package on the shr trac
May 15 09:40:55 <Psi_> Zorkman: thanks
May 15 09:41:23 <Zorkman> np
May 15 09:43:56 <badcloud1> Psi_, you can boot debian/hackable and install it
May 15 11:48:56 <rhkfin> Anyone have an idea of the crashing stuff in frameworkd.log (has several tracebacks) http://pastebin.com/m4645706f
May 15 12:58:56 <CIA-53> openmoko: 03werner * r4988 10/trunk/gta02-core/gta02-core.pro: 
May 15 12:58:56 <CIA-53> openmoko: Changed relative paths from components/... to ./components/..., for
May 15 12:58:56 <CIA-53> openmoko: better compatibility with older versions of KiCad.
May 15 12:58:56 <CIA-53> openmoko: Reported by Dave Ball <openmoko@underhand.org>
May 15 13:03:46 <CIA-53> openmoko: 03werner * r4989 10/trunk/gta02-core/expanded/gta02-core-expanded.pro: 
May 15 13:03:46 <CIA-53> openmoko: This wasn't actually the file I was using and it had the default libraries,
May 15 13:03:46 <CIA-53> openmoko: i.e., all wrong.
May 15 13:11:15 <PBeck> hallo
May 15 13:13:13 <rhkfin> hallo"
May 15 13:13:14 <Zorkman> llo
May 15 13:19:45 <CIA-53> freesmartphone.org: 03mickey 07cornucopia * rda54a121b23d 10/fsodeviced/src/ (4 files in 2 dirs): fsodevice: kernel_input: fix dbus marshalling problem
May 15 13:19:46 <CIA-53> freesmartphone.org: 03mickey 07cornucopia * rf878e9965de2 10/libfsoframework/ (3 files in 2 dirs): fsoframework: remove stuff from PosixExtra and create proper patches on top of vala master
May 15 14:08:01 <CIA-53> freesmartphone.org: 03seba.dos1 07framework * r409578e04178 10/framework/subsystems/opimd/ (4 files): opimd: implement adding new fields when updating existing contact
May 15 14:10:05 <CIA-53> freesmartphone.org: 03mickey 07cornucopia * rddba791589a4 10/ (5 files in 3 dirs): all: catch up with new patchset against posix.vapi
May 15 14:11:57 <CIA-53> freesmartphone.org: 03mickey 07cornucopia * r8546f3ff83c2 10/libfsoframework/vapi/posixextra.vapi: vapi: remove functions sent to patchset
May 15 14:27:55 <CIA-53> freesmartphone.org: 03mickey 07libgsm0710mux * re90f15e51657 10/ (4 files in 3 dirs): catch up with new vala posix patchset
May 15 14:29:41 <CIA-53> freesmartphone.org: 03mickey 07fso-abyss * r8ce3c6e40c48 10/ (configure.ac vapi/posix.vapi vapi/posixextra.vapi): catch up with new vala posix patchset
May 15 14:29:50 <CIA-53> freesmartphone.org: 03seba.dos1 07framework * red9619d31b75 10/framework/subsystems/opimd/pimd_messages.py: opimd: Messages: fix inconsistences with Contacts backend
May 15 15:28:31 <CIA-53> openmoko: 03daveb * r4990 10/trunk/gta02-core/components/ (5 files): revert to nNAME labelling for inverted signals, fix a couple of pintypes.
May 15 16:50:50 <thrashold> Is that glamo thing the reason that during SD I/O, the whole GUI is unresponsive on GTA02? :(
May 15 16:51:59 <wurp2|working> thrashold: yes
May 15 16:52:26 <wurp2|working> The same bus is shared between mrmory, video, and sdio
May 15 16:52:26 <max_posedon> not always
May 15 16:52:48 <max_posedon> thrashold, many distros for some crazy reason mount it sync
May 15 16:52:54 <max_posedon> remount it in async
May 15 16:54:41 <thrashold> Shouldn't ext3 default to async? I think it is async here
May 15 16:55:02 <max_posedon> thrashold, mount will answer you
May 15 16:55:19 <thrashold> It has neither, so I assume it is async (as it is in defaults)
May 15 16:55:34 <thrashold> rootfs on / type ext3 (rw,noatime,errors=remount-ro)
May 15 16:56:39 <max_posedon> hm... in this case you have other problem
May 15 16:57:46 <thrashold> I moved the SD card from Neo 1973 to Neo Freerunner (this is a Debian installation), put 2.6.29 kernel for GTA02, and now I have this problem (among others)
May 15 16:59:27 <wurp2|working> thrashold: You didn't change to the rootfs for the FR?  Don't you need to?
May 15 16:59:47 <thrashold> wurp2|working: No.
May 15 17:00:18 <thrashold> wurp2|working: I changed only one GTA01-specific package to get my sound and FSO framework running.
May 15 17:00:45 <thrashold> And video driver...
May 15 17:01:02 <wurp2|working> Wow, I thought there were more rootfs changes than that.  I know the advertised alsa controls are different, but I thought some of the other hw changes bled through
May 15 17:02:51 <thrashold> At least not on Debian. I guess it depends on the distro. OM2008.X didn't work for me on GTA01, even after compiling it myself for it...
May 15 17:03:08 <thrashold> Didn't work as in E was segfaulting
May 15 17:06:12 <thrashold> But I have problems, and I suspect the kernel. No battery status, for example.
May 15 17:10:57 <thrashold> Unresponsive means that I clicked on the screen and the click was registered after the backlight got turned off...
May 15 17:43:39 <thrashold> Is there USB host support in the framework, or I should use the old method? :)
May 15 17:46:30 <dos1> thrashold: there is, even shr-settings has toggle to set USB host mode
May 15 17:46:57 <thrashold> I couldn't find the method anywhere in the wiki, and I still haven't compiled shr-settings. :)
May 15 17:48:20 <dos1> thrashold: shr-settings is python, no need to compile :P
May 15 17:55:09 <PaulFertser> Digital_Pioneer: are you there?
May 15 17:55:28 <Digital_Pioneer> PaulFertser: Yo
May 15 17:57:05 <PaulFertser> Digital_Pioneer: i just tried to follow wiki instructionns for bluetooth headset. It works. (except that with this bluetooth i get amplifier noise instead of sound, but that's expected).
May 15 17:57:21 <PaulFertser> Digital_Pioneer: i can show you excerpts from frameworkd log.
May 15 17:59:21 <Digital_Pioneer> PaulFertser: Sounds good.
May 15 17:59:54 <Digital_Pioneer> All I ever see is crap about enabling and disabling the rules that used to be in the YAML file. It says those regardless of whether I'm trying to use bluetooth or not.
May 15 18:01:09 <PaulFertser> Digital_Pioneer:  ophoned              INFO     BT-Headset: ConnectionStatus = True
May 15 18:01:26 <PaulFertser> Digital_Pioneer: i get this after i turn on the headset.
May 15 18:01:31 <Digital_Pioneer> I've never seen a line like that. :(
May 15 18:02:09 <PaulFertser> Digital_Pioneer: then triggers oeventsd.trigger     DEBUG    trigger BTHeadsetIsConnected()
May 15 18:03:14 <Digital_Pioneer> Nope, nothing of the sort. So what am I not doing?...
May 15 18:03:22 <PaulFertser> Digital_Pioneer: either you have bluetoothd not running or you haven't enabled bluetooth via requesting resource.
May 15 18:04:10 <PaulFertser> Digital_Pioneer: i did fsoraw-armel -r Bluetooth -- sleep 1000 to request it. But i guess it'll be the same with SHR Settings.
May 15 18:04:53 <Digital_Pioneer> fsoraw doesn't work for me.
May 15 18:06:20 <PaulFertser> Digital_Pioneer: how come?
May 15 18:06:56 <Digital_Pioneer> IDK, but when I tried using it for mokomaze, the screen blanked anyways.
May 15 18:08:09 <PaulFertser> Digital_Pioneer: i guess you did something wrong
May 15 18:09:01 <Digital_Pioneer> :D No surprise there.
May 15 18:10:35 <CIA-53> freesmartphone.org: 03seba.dos1 07framework * rf7442ac4c4ca 10/framework/subsystems/opimd/pimd_contacts.py: opimd: Contacts: use lower TRESHOLD to have better contact name resolving
May 15 18:11:07 <PaulFertser> Digital_Pioneer: i can't fully test it here but it surely loaded the proper scenario and activated the headset (because it beeped on start and end of the call).
May 15 18:12:10 <Digital_Pioneer> PaulFertser: Well is there no cleaner way to request the resource than to use fsoraw to claim it for 1000 seconds?
May 15 18:12:57 <PaulFertser> Digital_Pioneer: i don't use shr so i don't know a better way.
May 15 18:13:22 <Digital_Pioneer> Yeah...
May 15 18:26:11 <Digital_Pioneer> PaulFertser: OK, so from the start, how do you tell frameworkd to use bluetooth? You need the two parameters in your profile, right?
May 15 18:28:03 <PaulFertser> Digital_Pioneer: yes, i have "bt-headset-enabled: True" and "bt-headset-address: 00:15:BE:27:CC:F9" in my opreferences/conf/phone/default.yaml. And i restarted frameworkd after adding those.
May 15 18:28:07 <Digital_Pioneer> bt-headset-address: XX:XX:XX:XX:XX:XX and bt-headset-enabled: 1 in /etc/freesmartphone/opreferences/conf/phone/default.yaml
May 15 18:29:24 <Digital_Pioneer> Now, for convenience sake when I can't use bluetooth, I went ahead and created a separate profile for it, so it's not in default.yaml, but I can load the new one from the GUI just the same (after editing a couple other .yaml's)
May 15 18:31:24 <Digital_Pioneer> PaulFertser: OK, so after loading the bluetooth-enabled profile, what then?
May 15 18:32:36 <PaulFertser> Digital_Pioneer: ensure you're running bluetoothd.
May 15 18:32:48 <PaulFertser> Digital_Pioneer: then request Bluetooth resource.
May 15 18:33:02 <Digital_Pioneer> root      3561  0.0  1.2   3228  1516 ?        SNs  May14   0:04 /usr/sbin/bluetoothd
May 15 18:33:07 <Digital_Pioneer> Methinks it's running.
May 15 18:33:28 <Digital_Pioneer> PaulFertser: Is there any DBUS call to make for that?
May 15 18:34:19 <PaulFertser> Digital_Pioneer: there's some interface in ophonekitd but i don't know it.
May 15 18:34:23 <astrocub> [22:09] <SpeedEvil> build the?
May 15 18:34:25 <astrocub> [22:25] <DocScrutinizer> hmm, puzzling
May 15 18:34:41 <astrocub> yes, i thought you could assemble the parts kind of like what you do with an arduino
May 15 18:34:44 <Digital_Pioneer> OK, we'll fool with that later. I just used your fsoraw command, hopefully that will do it.
May 15 18:34:51 <SpeedEvil> astrocub: oh
May 15 18:34:53 <astrocub> was hoping someone could clarify this for me
May 15 18:34:55 <SpeedEvil> astrocub: yes, you can
May 15 18:35:00 <astrocub> :D
May 15 18:35:02 <astrocub> great
May 15 18:35:06 <astrocub> that makes me happy
May 15 18:35:12 <astrocub> good news all around today
May 15 18:35:13 <SpeedEvil> astrocub: but, expect to spend $10-20K getting the first one working
May 15 18:35:18 <astrocub> o.O
May 15 18:35:22 <astrocub> no way
May 15 18:35:35 <astrocub> why?
May 15 18:35:38 <Digital_Pioneer> PaulFertser: After that?
May 15 18:36:04 <SpeedEvil> astrocub: because you've got to make a PCB, and design the circuit, and integrate it, and debug it
May 15 18:36:23 <SpeedEvil> astrocub: if by that you mean design a phone equivalent to FR
May 15 18:36:24 <DocScrutinizer> astrocub: SpeedEvil is kidding on you. Nope you can't
May 15 18:36:30 <PaulFertser> Digital_Pioneer: after that i'd press a key on headset to turn it on.
May 15 18:36:42 <Digital_Pioneer> PaulFertser: OK, I see in the frameworkd.log lines about bluetooth going to enabling to enabled.
May 15 18:36:46 <SpeedEvil> assuming you can get the parts.
May 15 18:36:47 <astrocub> oh, i understand now.
May 15 18:36:51 <Digital_Pioneer> PaulFertser: It's on.
May 15 18:37:06 <astrocub> i just thought the blueprints were available 
May 15 18:37:14 <astrocub> and that it was common to build it
May 15 18:37:46 <SpeedEvil> astrocub: you can't get the parts for the FR in small quantities.
May 15 18:38:12 <PaulFertser> Digital_Pioneer: Ok, what about BT-Headset: ConnectionStatus = True
May 15 18:38:13 <SpeedEvil> astrocub: in principle, if you could, and nothing went wrong, you could probably make one for $1000 or so.
May 15 18:38:34 <SpeedEvil> astrocub: due to assorted one-off charges biting you really hard
May 15 18:38:44 <Digital_Pioneer> PaulFertser: Nope.
May 15 18:39:10 <PaulFertser> Digital_Pioneer: Try to press some key on the headset...
May 15 18:39:23 <PaulFertser> Digital_Pioneer: try to toggle power of it.
May 15 18:39:51 <Digital_Pioneer> PaulFertser: Does the fsoraw command just turn the BT chip on?
May 15 18:39:59 <PaulFertser> Digital_Pioneer: if you start bluetoothd with "-nd" switches you'll see what's happening.
May 15 18:40:12 <PaulFertser> Digital_Pioneer: no, fsoraw requests the resource.
May 15 18:41:00 <Digital_Pioneer> PaulFertser: The purpose of which being?... I'm just wondering if enabling bluetooth from the settings GUI is doing the same thing.
May 15 18:41:51 <PaulFertser> Digital_Pioneer: dos1 says it is.
May 15 18:42:00 <Digital_Pioneer> OK
May 15 18:42:03 <dos1> let me check
May 15 18:42:42 <dos1> PaulFertser: no, it isn't
May 15 18:42:53 <dos1> it's using odeviced
May 15 18:43:00 <dos1> but it needs to be changed...
May 15 18:43:11 <Digital_Pioneer> OK, bluetooth is enabled, I connected to the headset with simple-agent, and I've got the bluetooth profile running.
May 15 18:43:24 <Digital_Pioneer> s/running/loaded/
May 15 18:43:24 <apt> Digital_Pioneer meant: OK, bluetooth is enabled, I connected to the headset with simple-agent, and I've got the bluetooth profile loaded.
May 15 18:43:33 <PaulFertser> dos1: ah, that might explain it.
May 15 18:43:41 <PaulFertser> Digital_Pioneer: use fsoraw then.
May 15 18:43:55 <Digital_Pioneer> Disable BT in GUI?
May 15 18:44:00 <Digital_Pioneer> Then use fsoraw?
May 15 18:44:47 <dos1> Digital_Pioneer: no, just use fsoraw
May 15 18:45:22 <Digital_Pioneer> dos1: So enable it in GUI then use fsoraw?
May 15 18:45:41 <dos1> Digital_Pioneer: you don't have to touch GUI. just use fsoraw
May 15 18:46:51 <Digital_Pioneer> Well, it's either enabled or disabled in GUI, I'd rather know which way it should be from there so that nothing is conflicting or whatever. I don't know the internals here, I don't know what might cause problems...
May 15 18:47:53 <Digital_Pioneer> Looks like using fsoraw makes the GUI report it as enabled anyways, so whatever.
May 15 18:48:03 <Digital_Pioneer> I've got the fsoraw command running.
May 15 18:48:09 <Digital_Pioneer> (sleeping really)
May 15 18:49:08 <Digital_Pioneer> OK, profile is loaded, headset is connected, headset is on, fsoraw has requested the resource. What else?... :\
May 15 18:49:54 <dos1> Digital_Pioneer: i know internals, that's why i suggested you to use just fsoraw ;)
May 15 18:50:13 <Digital_Pioneer> dos1: So I gathered. :)
May 15 18:50:40 <Digital_Pioneer> There's still nothing about ConnectionStatus in frameworkd.log
May 15 18:51:07 <dos1> ofc my knowing about internals isn't so much, but it's enough to distinguish ousaged and odeviced role in bt thing ;)
May 15 18:52:44 <Digital_Pioneer> Well, either way I do it, I think, ousaged says it enabled bluetooth in 0.2 seconds or so, and odeviced says power control for Bluetooth changed to True.
May 15 18:54:23 <Digital_Pioneer> And there's STILL nothing from ophoned about the headset being connected.
May 15 18:54:32 <Digital_Pioneer> Is there no way to give it a little prod? :P
May 15 18:54:52 <Digital_Pioneer> Does it only say that when a call in in progress?
May 15 18:56:05 <Digital_Pioneer> Call still goes through normal handset stuff.
May 15 18:56:54 <PaulFertser> Digital_Pioneer: no, it does it when bluetoothd sees the headset.
May 15 18:59:25 <Digital_Pioneer> PaulFertser: And there's nothing more to making that happen than bonding the two, right?
May 15 19:00:19 <PaulFertser> Digital_Pioneer: start bluetoothd with -nd and you'll see.
May 15 19:06:24 <Digital_Pioneer> PaulFertser: bluetoothd isn't saying anything that concerns me. It looks like it's acting exactly as it should.
May 15 19:07:38 <Digital_Pioneer> I even manually connected the headset (with a dbus call) and bluetoothd acts like everything's perfect, says it got connected, the headset beeped, and frameworkd.log is completely devoid of anything interesting.
May 15 19:10:06 <Digital_Pioneer> I just disconnected it with a dbus call (bonding still exists) and the headset beeped accordingly, bluetoothd output looks perfect. I have to think it's frameworkd not doing its job.
May 15 19:12:47 <Digital_Pioneer> any ideas? :(
May 15 19:13:05 <PaulFertser> Digital_Pioneer: it worked for me without any additional tweaks...
May 15 19:13:41 <Digital_Pioneer> :|
May 15 19:13:58 <Digital_Pioneer> Stupid frameworkd
May 15 19:15:43 <PaulFertser> Digital_Pioneer: i saw something like link_key_request (sba=00:06:6E:17:27:E0, dba=00:15:BE:27:CC:F9) in bluetoothd output
May 15 19:15:53 <PaulFertser> Digital_Pioneer: and then frameworkd saw it.
May 15 19:17:01 <CIA-53> openmoko: 03werner * r4991 10/trunk/gta02-core/kicad-patches/ (. eeschema-plot-only-mode.patch): 
May 15 19:17:01 <CIA-53> openmoko: A patch to add batch-mode plotting to eeschema:
May 15 19:17:01 <CIA-53> openmoko: eeschema --plot file.sch
May 15 19:19:02 <fale> I connected my moko to my pc throught the usb, but my moko is not able to connect to the web. What can I do to fix it
May 15 19:20:30 <Digital_Pioneer> PaulFertser: bluetoothd[8837]: link_key_request (sba=00:06:6E:17:2B:67, dba=00:19:7F:A1:C1:05)
May 15 19:20:59 <Digital_Pioneer> The dba address is my headset.
May 15 19:28:11 <Digital_Pioneer> fale: See wiki
May 15 19:28:44 <fale> Digital_Pioneer: I have tried this page: http://wiki.openmoko.org/wiki/USB_Networking but without any luck
May 15 19:30:22 <Digital_Pioneer> fale: Well, I stuck this in a script and run it every time I connect my FR: http://pastebin.com/m2ada1662
May 15 19:32:19 <fale> Digital_Pioneer: thankyou very much :)
May 15 19:33:01 <Digital_Pioneer> fale: Did that work for you?
May 15 19:33:30 <fale> Digital_Pioneer: yes :)
May 15 19:33:36 <Digital_Pioneer> Excellent. :)
May 15 19:49:55 <CIA-53> openmoko: 03werner * r4992 10/trunk/gta02-core/ (4 files in 2 dirs): 
May 15 19:49:55 <CIA-53> openmoko: Updated scripts to use new eeschema --plot to automatically generate
May 15 19:49:55 <CIA-53> openmoko: the schematics with expanded pin types.
May 15 22:15:55 <CIA-53> freesmartphone.org: 03mickey 07framework * race2ab827183 10/framework/subsystems/ogsmd/ (gsm/channel.py modems/abstract/calling.py): ogsmd: repair damage done by 9c746079d020f483257c64200cd0e18ca8586f13. should fix #404
May 15 23:13:55 <CIA-53> freesmartphone.org: 03dos 07framework * r504f93b72247 10/framework/subsystems/opimd/pimb_sim_messages_fso.py: opimd: SIM_Messages_FSO: some initial work
May 15 23:16:31 <Think-Free> Hi guys ! I'm looking for a librairy to make a keyboard for Xorg ... any ideas ( I 'm looking for a low level one )
May 15 23:34:54 <Prodego> mickey|zzZZzz: poke
May 16 00:09:06 <DocScrutinizer> Prodego: too late for mickey|zzZZzz :-)
May 16 00:10:41 <DocScrutinizer> ~seen mickey|zzZZzz 
May 16 00:10:46 <apt> mickey|zzzzzz is currently on #htc-linux #openmoko #openezx. Has said a total of 20 messages. Is idling for 13h 33m 30s, last said: 'rap100: fb works, SD works, GSM works, USB works. no audio, no gprs, no wifi, no bluetooth'.
May 16 00:15:59 <Prodego> he is actually idle 1:21:26
May 16 00:19:05 <DocScrutinizer> Prodego: see #openmoko-cdevel :-)
May 16 00:19:38 <Prodego> DocMobilizer: you can also get it authoritiarively from /whois mickey|zzZZzz mickey|zzZZzz 
May 16 00:19:38 <DocScrutinizer> Prodego: btw: WTF? 23k wiki-edits?! o.O
May 16 00:19:50 <Prodego> you should meet j.delanoy
May 16 00:20:22 <Prodego> he has more than 10 times that
May 16 00:20:31 <DocScrutinizer> errrrr
May 16 00:20:36 <DocScrutinizer> :-o
**** ENDING LOGGING AT Sat May 16 02:59:57 2009