**** BEGIN LOGGING AT Wed Jun 24 02:59:58 2015 Jun 24 05:59:13 morning Jun 24 06:46:31 I'm working with Ubuntu 13.04 for a while now, without any issue Jun 24 06:46:40 (and in a chroot) Jun 24 07:18:48 morning Jun 24 07:51:16 JaMa: ping Jun 24 08:39:09 Herrie|Veer: should bluetooth work on touchpad out of the box, or maybe need some module? hciconfig shows nothing to me. Jun 24 08:47:52 nizovn: I'm not sure. I haven't tried TP, only tried N4 Jun 24 08:48:04 I think it might need a tweak here or there on TP still Jun 24 08:48:17 I know the dev who did some work did it with N4 Jun 24 08:49:45 ok; how do you scan for bt devices on n4? maybe i do something wrong Jun 24 08:50:11 nizovn: I need to do a connmanctl enable bluetooth Jun 24 08:50:32 On N4 it will then appear powered in connmanctl technologies Jun 24 08:50:53 on touchpad too, but hciconfig is empty Jun 24 08:51:22 On N4 I get command not found :P Jun 24 08:51:29 Let me search through logs Jun 24 08:53:57 maybe "dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.ListAdapters" shows anything? Jun 24 08:54:36 nizovn: Check log for 20150429 Jun 24 08:54:42 There's quite some bits there Jun 24 08:55:24 thanks Jun 24 08:55:26 mdbus2 -s org.bluez Jun 24 08:56:06 Gives me org/bluez/680 also 680/hci0 and 680/any Jun 24 08:57:21 i don't have hci0 Jun 24 08:58:02 only /org/bluez/2139/ and 2139/any Jun 24 09:00:44 Hmmz morphis might know more for that Jun 24 09:00:57 I'm not too familiar with the whole BT stack stuff Jun 24 09:07:51 But seems we need hci0 for sure from what I read Jun 24 09:08:05 I guess we need to enable something in kernel for it Jun 24 09:14:09 NewbyJE has good sources on his github for TP kernel. It's used for the TP4G Android build. See http://github.com/newbyje/ Jun 24 14:30:38 Tofe: PR waiting for your review :) Working on Hebrew and other languages as well now :% Jun 24 14:30:39 :) Jun 24 14:53:31 Herrie|Veer: fine for me, merged Jun 24 14:53:56 Herrie|Veer: what's preventing from merging the touch PR ? Jun 24 15:03:32 Tofe: Thnx, I thought you still had a few points for the touch PR you were working on? Jun 24 15:10:15 Herrie|Veer: there will always be some Jun 24 15:10:32 But as such, all the functionalities we had are there Jun 24 15:16:18 Ah OK I'll merge it tonight :) Jun 24 17:31:42 Herrie: bluetooth on TP looks like a bit more work Jun 24 17:31:50 nizovn: if you want details, tell me Jun 24 17:32:12 morphis: i'm trying to get it now Jun 24 17:36:59 basically as we use bluez there are multiple steps Jun 24 17:37:45 nizovn: CONFIG_BLUETOOTH needs to be enabled next to some other options Jun 24 17:38:09 see https://github.com/webOS-ports/meta-webos-ports/blob/master/meta-luneos/scripts/verify_kernel_config#L158 Jun 24 17:38:46 after that we need to attach the tty from /dev to the bluetooth management layer in the kernel Jun 24 17:39:45 nizovn: https://github.com/willcast/hp-touchpad-ubuntu has some details about that Jun 24 17:40:39 morphis: i'm trying based on http://forum.xda-developers.com/showpost.php?p=23571015&postcount=443 Jun 24 17:40:55 seems it's the same :) Jun 24 17:41:07 yeah Jun 24 17:41:11 nizovn: does that work? Jun 24 17:41:44 i now think how to build bcattach Jun 24 17:42:09 https://github.com/CyanogenMod/android_device_hp_tenderloin/tree/jellybean/bcattach Jun 24 17:42:30 morphis: I know Android doesn't use BlueZ but other stuff could be taken from NewbyJE kernel right? Jun 24 17:43:38 Herrie: the difference between bluez and the Android BT stack is mainly that bluez puts the lower end (HCI,..) into the kernel and just has upper layer things in userland (bluetoothd) where Android has everything in one binary in userland Jun 24 17:43:54 keeps it independent of a kernel version (not 100% true) Jun 24 17:44:11 however our kernel should have CONFIG_BT=y set so we're fine Jun 24 17:44:59 you can check that with zcat /proc/config.gz | grep CONFIG_BT Jun 24 17:45:15 yes, it has Jun 24 17:45:21 good Jun 24 17:46:04 nizovn: to try you could simply apt-get install gcc-4.9-arm-linux-gnueabi Jun 24 17:46:36 then arm-linux-gnueabi-gcc-4.9 ... according to https://github.com/CyanogenMod/android_device_hp_tenderloin/blob/jellybean/bcattach/Android.mk Jun 24 17:46:49 should normally work Jun 24 17:47:00 or you use the toolchain from your tmp-glibc Jun 24 17:48:19 i just compiled gentoo crossdev toolchain (for uImage with more bt configs) Jun 24 17:48:49 ok Jun 24 18:35:26 morphis: bluetooth works! Jun 24 18:37:44 nizovn: Good stuff! Jun 24 18:57:39 nizovn: great! Jun 24 18:57:46 nizovn: now we just have to integrate it Jun 24 18:57:57 you can look how we did it for n4 in meta-smartphone/meta-lg Jun 24 19:06:03 morphis: bt extension should be based on dbus, or libbluez-qt? Jun 24 19:35:21 nizovn: I think morphis wanted to go more in the direction of the web bluetooth api Jun 24 19:35:34 Seems Tizen already did the necessary bits in combination with BlueZ ;) Jun 24 19:35:38 So that might be useful? Jun 24 19:36:18 yes Jun 24 19:37:06 You seen the link? Jun 24 19:42:31 tizen link? yes, seems very useful, thanks a lot :) Jun 24 19:43:25 This one: https://github.com/crosswalk-project/tizen-extensions-crosswalk/tree/master/src/bluetooth Jun 24 19:43:41 I'm not sure to what extend that's compatible with the Mozilla API Jun 24 19:44:56 But basic functionality should be similar Jun 24 19:45:10 And adding a 2nd API shouldn't be too much work when all the back end stuff is already there Jun 24 20:33:37 nizovn: for the bt API you can take the NetworkManager API as example Jun 24 20:33:49 https://github.com/webOS-ports/luna-webappmanager/tree/master/src/extensions Jun 24 20:33:57 sorry meant WiFiManager Jun 24 20:34:47 ok Jun 24 20:36:54 nizovn: and libbluez-qt is a good thing Jun 24 20:37:00 otherwise you could use qtconnectivity Jun 24 20:37:34 nizovn: http://doc.qt.io/qt-5/qtbluetooth-overview.html Jun 24 20:38:34 however I am not sure to which degree that support pairing **** ENDING LOGGING AT Thu Jun 25 02:59:59 2015