2016-02-11 20:46:31	@kido	I investigated the Gadgetbridge way for asteroid and one thing bothers me: it is just an implementation of the pebble protocol, which means that 1- it is not based on low energy 2- we reimplement a usualy closed protocol 3- there are many features that are totaly irelevant to asteroid (e.g: install pebble specific watchfaces, watchapps, firmware, languages, pebblekit etc...)
2016-02-11 20:48:19	@kido	I tried to see elsewhere if there was any standard for doing the things we need and the bluetooth group standardized the "Alert Notification Profile" https://developer.bluetooth.org/TechnologyOverview/Pages/ANP.aspx and "Alert Notification Service" https://developer.bluetooth.org/TechnologyOverview/Pages/ANS.aspx a part of it seems to be implemented in BlueZ5
2016-02-11 20:48:19	@kido	http://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/alert-api.txt
2016-02-11 20:48:56	@kido	of course apple did its own thing https://developer.apple.com/library/ios/documentation/CoreBluetooth/Reference/AppleNotificationCenterServiceSpecification/Introduction/Introduction.html
2016-02-11 20:49:55	locusf	hmm
2016-02-11 20:50:13	locusf	you could be the trailblazer now in this regard as well :)
2016-02-11 20:51:12	@kido	indeed, but for now I'm not informed enough on the subject to become a bluetooth-trailblazer :)
2016-02-11 20:52:09	locusf	if you know about protocols you know about profiles
2016-02-11 20:52:16	locusf	since they are quite similar
2016-02-11 20:52:28	@kido	sure
2016-02-11 20:52:34	locusf	GATT is apparently something that BLE does
2016-02-11 20:52:57	locusf	but don't take all from me :p
2016-02-11 20:53:13	locusf	my knowledge of bluetooth is from a course from 2005
2016-02-11 20:53:18	locusf	and then of course monotooth
2016-02-11 20:53:47	locusf	https://github.com/locusf/monotooth
2016-02-11 20:54:02	@kido	oh didn't know you did that
2016-02-11 20:54:03	locusf	9 years ...
2016-02-11 20:54:12	@kido	this is really cool
2016-02-11 20:54:17	locusf	yeah I had this knack on bluetooth back then
2016-02-11 20:54:24	locusf	still do but not in the same sense
2016-02-11 20:54:50	@kido	you might be of valuable help for me indeed
2016-02-11 20:54:57	locusf	took me two weeks to do a proper framework and send first bytes with the same code on windows + linux
2016-02-11 20:55:33	locusf	but my course instructor was right
2016-02-11 20:55:54	locusf	bluetooth has become de-facto small range wireless physical medium
2016-02-11 20:56:30	dr_gogeta86	hi locusf
2016-02-11 20:57:36	locusf	hi dr_gogeta86 :)
2016-02-11 20:57:56	dr_gogeta86	I've seen the mer-meeting ... and talk about pure hw-adaptation
2016-02-11 20:58:09	dr_gogeta86	you referring to freedreno HAL ?
2016-02-11 20:59:49	locusf	yes
2016-02-11 20:59:52	locusf	+ mainline kernel
2016-02-11 21:01:05	@kido	I'd be interested too...
2016-02-11 21:02:08	locusf	the crap thing is that bluetooth specs have been closed since 2007
2016-02-11 21:02:27	locusf	although it was getting quite ridiculous
2016-02-11 21:02:40	locusf	2.1 EDR spec was 3000 pages
2016-02-11 21:02:47	locusf	nothing compared to GSM specs but still
2016-02-11 21:03:10	locusf	had to read some parts of it in order to implement a baseband emulator over tcp
2016-02-11 21:04:23	@kido	:D
2016-02-11 21:05:28	dr_gogeta86	locusf, badass
2016-02-11 21:05:48	dr_gogeta86	locusf, better a crap protocoll rather then carplay or android auto
2016-02-11 21:05:54	dr_gogeta86	walled gardens ...
2016-02-11 21:06:03	dr_gogeta86	not to mentions mirrorlink .....
2016-02-11 21:07:03	locusf	yeah
2016-02-11 21:13:35	@kido	mhhh it seems I will have to get back to android to get started with bluetooth easily :/ if I stick with sailfish on my phone, it will only make things harder to do at the begining
2016-02-11 21:16:39	locusf	why so?
2016-02-11 21:16:52	locusf	use QtBluetooth
2016-02-11 21:17:07	locusf	you don't usually need to bother with bluez directly that way
2016-02-11 21:17:18	@kido	yes but qtbluetooth is not complete on BTLE, it seems I will have to use bluez's dbus api
2016-02-11 21:17:51	locusf	not yet :)
2016-02-11 21:18:13	locusf	you could pull in the ble branch as a patch collection
2016-02-11 21:19:03	@kido	I showed javier the latest commit of the devel branch of qtbluetooth and he said on linux it was not using bluez
2016-02-11 21:21:23	locusf	http://doc.qt.io/qt-5/qtbluetooth-le-overview.html
2016-02-11 21:21:28	locusf	ok
2016-02-11 21:22:32	@kido	https://twitter.com/javispedro/status/697393946448805889
2016-02-11 21:26:54	locusf	I see bluez headers ...
2016-02-11 21:28:33	locusf	1,477 src/bluetooth/qlowenergycontroller_bluez.cpp
2016-02-11 21:29:53	locusf	https://github.com/qtproject/qtconnectivity/blob/d55a7539175a07e0a0eb59a840c424231661195b/src/bluetooth/qlowenergycontroller_bluez.cpp
2016-02-11 21:35:07	locusf	but now sleep
2016-02-11 21:35:10	@kido	javier contributed to this file in 2016 so he is probably well aware of the current state, he said qtbluetooth's bluez backend was capable of setting up clients but no servers
2016-02-11 21:35:16	locusf	okay
2016-02-11 21:35:32	@kido	I will try to contact the other qtbluetooth devs
2016-02-11 21:37:08	locusf	yeah I recommend that
2016-02-11 21:37:14	locusf	using pure bluez api is painful
2016-02-11 21:37:33	locusf	if you get Qt to this it makes life much easier
2016-02-11 21:37:42	@kido	sure
2016-02-11 21:37:52	locusf	but still
2016-02-11 21:38:01	@kido	that was the original plan... I just hope it's possible
2016-02-11 21:38:02	locusf	parsing characteristics is also a bit meh