**** BEGIN LOGGING AT Wed Apr 07 02:59:57 2010
Apr 07 05:55:29 <Psi> hm.. how do you shutdown the phone with this new shr gui layout
Apr 07 06:30:48 <Psi> nevermind, gsm doesnt work so ill go back to previous version anyway
Apr 07 08:45:49 <badcloud> how can I diagnose the sim card? shr-t is not registering with the network (because sim card is not present??)
Apr 07 08:45:57 <badcloud> just flashed the latest
Apr 07 15:17:18 <Gabrys> PaulFertser: hello, I'm back here, to debug the BT thing :-)
Apr 07 16:11:19 <Gabrys> can someone share /etc/init.d/bluetooth script?
Apr 07 16:11:27 <Gabrys> because I miss one
Apr 07 16:33:14 <PaulFertser> Gabrys: hey
Apr 07 16:33:57 <Gabrys> so far I discovered, that doing this thing manually by calling from FreeRunner fail ;-)
Apr 07 16:34:17 <PaulFertser> ?
Apr 07 16:36:04 <PaulFertser> Gabrys: probably bluetoothd should be started by means of dbus activation nowadays.
Apr 07 16:36:13 <Gabrys> maybe
Apr 07 16:39:37 <PaulFertser> Gabrys: it's also interesting that the latest fso does request bluetooth resource on its own, so no need to do it manually.
Apr 07 16:39:57 <Gabrys> theoretically ;-)
Apr 07 16:40:01 <Gabrys> in practise it FAILS :D
Apr 07 16:41:36 <PaulFertser> Gabrys: and bt-headset-enabled is no longer used at all
Apr 07 16:41:45 <Gabrys> wow, nice :P
Apr 07 16:41:52 <Gabrys> so in theory 
Apr 07 16:42:05 <Gabrys> we just put bt headset about the phone and it magically works :D
Apr 07 16:42:47 <PaulFertser> Gabrys: no, bt-headset-address should be set in relevant config file
Apr 07 16:43:06 <Gabrys> so instead of two options it's now one?
Apr 07 16:45:00 <PaulFertser> Gabrys: yes, and you can even alter it runtime
Apr 07 16:45:29 <PaulFertser> Gabrys: through org.freesmartphone.Preferences.Service
Apr 07 16:45:56 <PaulFertser> And if you set it to "null", it will stop using the headset. And if you set the address, it'll start again.
Apr 07 16:46:06 <PaulFertser> Runtime, no frameworkd restart needed at all.
Apr 07 16:47:22 <Gabrys> nice :-)
Apr 07 16:47:38 <Gabrys> so how do I "start" bt at all?
Apr 07 16:47:42 <PaulFertser> Gabrys: it's you who knows python, not me, why is that i'm telling you that stuff?
Apr 07 16:47:55 <Gabrys> I mean do I have to /etc/init.d/bluetooth start or bluetoothd anymore?
Apr 07 16:48:12 <Gabrys> if not, what starts it 
Apr 07 16:48:20 <PaulFertser> Gabrys: do you know about dbus activation?
Apr 07 16:48:36 <Gabrys> not much
Apr 07 16:49:00 <Gabrys> would something like fsoraw "enable" bluetooth?
Apr 07 16:50:18 <Gabrys> fsoraw -r Bluetooth sleep 999 &
Apr 07 16:50:21 <PaulFertser> Gabrys: dbus activation will start bluetoothd on any org.bluez access i think.
Apr 07 16:50:28 <Gabrys> I'll try then
Apr 07 16:51:06 <Gabrys> root@om-gta02 ~ $ BTADAPTER=`dbus-send --system --dest=org.bluez --print-reply /
Apr 07 16:51:06 <Gabrys>  org.bluez.Manager.DefaultAdapter | tail -1 | sed 's/^.*"\(.*\)".*$/\1/'`
Apr 07 16:51:06 <Gabrys> Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files
Apr 07 16:51:25 <PaulFertser> Ok, let me check
Apr 07 16:52:43 <PaulFertser> Gabrys: probably i'm mistaken about bluetoothd dbus activation
Apr 07 16:54:19 <Gabrys> well
Apr 07 16:54:33 <Gabrys> though there's something like udev activation for bluetoothd
Apr 07 16:55:00 <Gabrys> bluetoothd --udev Run from udev mode of operation
Apr 07 16:56:24 <Gabrys> after manually powering on bluetooth, hciconfig works 
Apr 07 16:56:29 <Gabrys> but dbus calls fails
Apr 07 16:56:30 <Gabrys> the same way
Apr 07 16:56:45 <Gabrys> so it's not triggered by powered the bluetooth (with echo 1 > /sys/b...)
Apr 07 16:57:22 <PaulFertser> Gabrys: ok, it's udev
Apr 07 16:57:44 <PaulFertser> Gabrys: i just found that out, independently of you ;)
Apr 07 16:59:15 <PaulFertser> Gabrys: well, bluetooth chip is connected via usb, so upon powering udev should trigger. And http://git.kernel.org/?p=bluetooth/bluez.git;a=blob;f=scripts/bluetooth.rules.in;h=6809e9d737abf61b3ae3b88893b9796e6b6b7e68;hb=HEAD says it should start bluetoothd
Apr 07 16:59:41 <PaulFertser> Gabrys: do you by any chance can use "udevadm monitor" to try to find what happens and why the rule doesn't fire?
Apr 07 16:59:53 <Gabrys> nope, I'll try this
Apr 07 17:00:14 <PaulFertser> Gabrys: or try to start /sbin/bluetoothd --udev manually, see if it misteriously exits :)
Apr 07 17:00:55 <Gabrys> I got events 
Apr 07 17:01:15 <Gabrys> but I don't get commands executed in output of udevadm monitor
Apr 07 17:02:44 <Gabrys> hm
Apr 07 17:02:48 <PBeck> hi
Apr 07 17:02:50 <Gabrys> I don't have bluetooth.rules
Apr 07 17:03:02 <Gabrys> in my /etc/udev/rules.d
Apr 07 17:03:49 <PaulFertser> Gabrys: what rules you do have then?
Apr 07 17:04:35 <Gabrys> PaulFertser: http://pastebin.com/thAjqBTJ
Apr 07 17:05:24 <PaulFertser> Gabrys: it should be 97-bluetooth.rules...
Apr 07 17:05:47 <Gabrys> It must have gone recently 
Apr 07 17:05:52 <Gabrys> as the /etc/init.d/bluetooth script 
Apr 07 17:06:25 <Gabrys> I reinstalled bluez4 and task-base-bluetooth just to make sure it's there
Apr 07 17:06:28 <PaulFertser> Gabrys: apparently it's just omitted by mistake from bluez recipe
Apr 07 17:06:33 <Gabrys> probably 
Apr 07 17:06:36 <Gabrys> or udev's one 
Apr 07 17:06:41 <Gabrys> could you share that one for me?
Apr 07 17:07:09 <PaulFertser> Gabrys: the rules file? Just grab it from the link i gave to kernel.org
Apr 07 17:07:23 <Gabrys> remove @prefix@ from it?
Apr 07 17:07:27 <PaulFertser> Nope, the rules should be in bluez recipe
Apr 07 17:07:29 <Gabrys> it seems a template 
Apr 07 17:07:29 <PaulFertser> Gabrys: sure
Apr 07 17:07:33 <Gabrys> ok
Apr 07 17:07:51 <badcloud> hey people
Apr 07 17:08:15 <Gabrys> ok, restarting udev
Apr 07 17:08:40 <Gabrys> seems it cannot restart, I reboot my phone then
Apr 07 17:08:46 <badcloud> is anyone here pisi/python-smart?
Apr 07 17:09:56 <badcloud> I'm trying to import SIM contacts to opmid, but am getting "More items found in D-Bus signature than in Python arguments" at 10%. ideas?
Apr 07 17:10:37 <PaulFertser> Gabrys: udevadm control --reload-rules
Apr 07 17:10:45 <badcloud> if I select "yes" to continue, it stops at 40% and says it's finished but I don't see any contacts
Apr 07 17:10:55 <Gabrys> PaulFertser: I just got it rebooted ;-)
Apr 07 17:12:19 <PaulFertser> badcloud: sorry, but i'm not sure you'll find anyone here that wants/can debug it right now. Why do not you try yourself? And you most probably using an old version, i've read at community that those bugs are fixed.
Apr 07 17:21:16 <badcloud> PaulFertser: thanks. I wish I knew the debug command... I ran pisi in the terminal hoping it would load the gui + debug in the term
Apr 07 17:21:31 <badcloud> but no such luck (it's got a cli client as well)
Apr 07 17:22:08 <badcloud> PaulFertser: hold the phone, I should have looked harder :P
Apr 07 17:22:15 <badcloud> pisi, pisi*gui*
Apr 07 17:24:41 <PaulFertser> Gabrys: i'm not sure how it could happen the rule file is not there, i took a look at the OE recipe...
Apr 07 17:34:33 <Gabrys> hm
Apr 07 17:34:51 <Gabrys> PaulFertser: should bluetoothd be running after it's manually enabled from shr settings?
Apr 07 17:35:04 <Gabrys> udevadm displays proper "add" messages
Apr 07 17:35:28 <Gabrys> but I guess the command was not run :/
Apr 07 17:36:55 <PaulFertser> Gabrys: hm, udev has enough debugging means, try to check everything...
Apr 07 17:37:34 <Gabrys> ah, OK
Apr 07 17:37:38 <Gabrys> I had wrong path 
Apr 07 17:37:41 <Gabrys> to bluetoothd
Apr 07 17:37:44 <Gabrys> it works now
Apr 07 17:37:49 <PaulFertser> Heh
Apr 07 17:37:52 <Gabrys> I mean bluetoothd starts automatically 
Apr 07 17:38:01 <Gabrys> (I removed that %prefix% and it should be /usr)
Apr 07 17:38:15 <Gabrys> ok, so I have bluetoothd running 
Apr 07 17:38:19 <PaulFertser> Gabrys: so you basically claim that SHR bluez package is for some reason not installing bluetoothd rules file, right?
Apr 07 17:38:21 <Gabrys> let's see what's next :-)
Apr 07 17:38:28 <Gabrys> PaulFertser: yes
Apr 07 17:38:53 <PaulFertser> Gabrys: you might want to attract attention of any of shr devs to it, probably JaMa knows enough of bitbake-foo to sort that out in a matter of minute.
Apr 07 17:41:25 <Gabrys> also shouldn't default /etc/bluetooth/audio.conf have the route to HCI already set ?
Apr 07 17:41:29 <Gabrys> to PCM sorry 
Apr 07 17:44:11 <badcloud> is there any way to prevent the lock screen from appearing when the device is charging?
Apr 07 17:44:18 <badcloud> *only* when it's charging
Apr 07 17:44:20 <badcloud> in shr-t
Apr 07 17:48:04 <Gabrys> PaulFertser: I seriously think it would be much more elegant if we have the sound routing done in software :-)
Apr 07 17:52:08 <PaulFertser> Gabrys: it should have that option set to PCM, yes. That option is useless anyway and Play() method is deprecated. bluez developers already told me how to do it another, more proper way.
Apr 07 17:52:33 <Gabrys> what's the way?
Apr 07 17:53:53 <PaulFertser> Gabrys: i do not remember it already, some ioctl on unix socket or something like that.
Apr 07 17:54:06 <Gabrys> ok
Apr 07 18:24:40 <Gabrys> PaulFertser: I've just broken some rules or something 
Apr 07 18:25:33 <Gabrys> when I call to the FR (without even starting bluetooth) there's no audio either way, volume slider is left (but moving it right does not help), speaker switch also doesn't change anything 
Apr 07 18:31:23 <Gabrys> and I have no ring on incomming call :(
Apr 07 18:35:38 <badcloud> anyone know how to use installed graphic kbds? they don't show up...
Apr 07 18:35:41 <badcloud> shr-t
Apr 07 18:36:06 <Gabrys> PaulFertser: it seems frameworkd now don't switch scenarios :(
Apr 07 18:36:27 <badcloud> (always feels like a radio commercial ad when I do that- can't do this or this... *shr-t*)
Apr 07 18:36:33 <badcloud> though I mean nothing by it
Apr 07 18:38:37 <PaulFertser> Gabrys: restart framework, it also has bugs...
Apr 07 18:38:44 <Gabrys> ok
Apr 07 18:39:05 <PaulFertser> badcloud: tried sliding up? They should be there...
Apr 07 18:46:33 <badcloud> PaulFertser: slided, not there :(
Apr 07 18:47:53 <badcloud> http://pastebin.com/YbaUWuAr
Apr 07 18:50:41 <Gabrys> damn, it just stopped changing scenarios :/
Apr 07 18:50:46 <Gabrys> even after reboot :/
Apr 07 18:50:46 <brolin_empey> Since there appears to be no fsck.jffs2, how can I unbork my JFFS2 QtMoko v19 rootfs on NAND? :/
Apr 07 18:51:22 <Gabrys> PaulFertser: no ERROR in logs 
Apr 07 18:51:54 <brolin_empey> Let me guess:  I have to back up the files I want to keep and reformat Yet Again. :(
Apr 07 18:53:41 * brolin_empey thought he could boot QtMoko from SD, then fsck his borked rootfs on NAND, then he discovered there is no fsck.jffs2 before he replaced U-Boot with Qi so he could boot QtMoko from SD.
Apr 07 18:57:01 <brolin_empey> Is it possible the new microSDHC cards (HP, 8 GB Class 4) I am using caused the JFFS2 corruption?
Apr 07 19:05:30 <brolin_empey> Now I do not even get any graphics when QtEI is supposed to start during the QtMoko boot process:  I just get a blinking text cursor in the top left.  It blinks for a second or 2, then disappears, then the cycle restarts in an infinite loop. :(
Apr 07 19:18:56 <Gabrys> brolin_empey: JFFS2 images are not to be used on uSD cards
Apr 07 19:19:00 <Gabrys> they are for NAND
Apr 07 19:19:15 <Gabrys> on SD use tar.gz (unpack to ext3 partition on SD card)
Apr 07 19:19:30 <Gabrys> but with qtmoko v18 you need to use custom kernel, to boot into this
Apr 07 19:19:42 <Gabrys> so use v19 or v18 with custom (or -debug) kernel
Apr 07 19:19:49 <Gabrys> but -debug one is slower
Apr 07 19:22:32 <brolin_empey> Gabrys: I am using QtMoko v19 because v18 is unusable for me:  no USB mode control nor RNDIS support.
Apr 07 19:22:57 <Gabrys> brolin_empey: I don't even know what it is
Apr 07 19:23:12 <Gabrys> but you don't normally put jffs2 files onto a SD card 
Apr 07 19:23:35 <Gabrys> I don't think Qi can boot that 
Apr 07 19:23:43 <brolin_empey> Gabrys: I know.  I was not going to use a JFFS2 image on SD. :P
Apr 08 02:35:11 <Slaxxed> watsup with the planet--no updates lately?
**** ENDING LOGGING AT Thu Apr 08 02:59:56 2010