The Following User Says Thank You to ajalkane For This Useful Post: | ||
|
2012-09-20
, 17:04
|
Moderator |
Posts: 5,320 |
Thanked: 4,464 times |
Joined on Oct 2009
|
#102
|
I have no personal need for this (no Bluetooth devices) so I'm unsure what is needed and what not. My intent was to do a condition like the existing WLAN/NFC where you could collect Bluetooth devices, so that the condition would trigger when the device is paired.
But I've ran into trouble implementing even that, as I can't seem to get the information about when Bluetooth devices are paired with phone:
http://talk.maemo.org/showthread.php?t=86870
So I'm currently unsure if I can implement this to ProfileMatic or not.
I think it continues just the same even if connected, but I'm going by memory here so I can be wrong.
The Following User Says Thank You to jalyst For This Useful Post: | ||
|
2012-09-21
, 06:10
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#103
|
Bummer, I was hoping we could set conditions based on the BT profile being used...
Maybe they all are to some extent? In which case it'd be more prudent to set conditions based on whether BT is: "off", "on" or "on & visible".
I think condition based on whether device is paired or not is way too generic, you usually only need to pair a BT device once :-/
The Following User Says Thank You to ajalkane For This Useful Post: | ||
|
2012-09-21
, 08:03
|
Posts: 277 |
Thanked: 319 times |
Joined on Jan 2010
|
#104
|
|
2012-09-21
, 19:06
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#105
|
ajalkane, if you want, I could donate an old Nokia BH-111 bluetooth receiver (without the headphones). I have no use for it and since I assume we both live in Finland it would cost me nothing to send it to you. Let me know if you think that might help. No strings attached.
|
2012-09-22
, 16:26
|
Moderator |
Posts: 5,320 |
Thanked: 4,464 times |
Joined on Oct 2009
|
#106
|
I know really badly about Bt use cases so I gladly listen to ideas to see what's possible. Of course at the same time I'd like to make as generic condition as possible, so that it would be flexible for different use cases.
Maybe I'm wrong, but I thought having a condition on defined Bluetooth device would be such flexible condition.
That one at least would be possible. But I would avoid such a condition if there are alternatives, since there is action for putting Bluetooth off/on/on&visible. Reason being it could cause unfortunate loops of re-evaluating the rules.
I see, thanks for that. Shows how little I know of using Bluetooth. I thought pairing is like connecting the devices.
Unfortunately I see nothing in the APIs to detect when a Bluetooth device is connected. I did see such message in D-Bus, but that won't help if I can't catch the D-Bus messages.
|
2012-09-22
, 20:53
|
Posts: 277 |
Thanked: 235 times |
Joined on Jan 2012
|
#107
|
|
2012-09-25
, 20:17
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#108
|
TBH I'm not sure of too many others either, I know there's many other uses/profiles, but I only use a tiny fraction of them regularly.
Perhaps if I dug-up some more info. on BT profiles that would help?
The Following User Says Thank You to ajalkane For This Useful Post: | ||
But I've ran into trouble implementing even that, as I can't seem to get the information about when Bluetooth devices are paired with phone:
http://talk.maemo.org/showthread.php?t=86870
So I'm currently unsure if I can implement this to ProfileMatic or not.
My N9/N950 projects: