Related
I was wondering if Desire works OK with bluetooth hand-free devices. Someone who can tell us about it? I use it a lot on my car and it's a basic point for a mobile phone. I would really appreciate any feedback about this.
Thanks.
xmfreak said:
I was wondering if Desire works OK with bluetooth hand-free devices. Someone who can tell us about it? I use it a lot on my car and it's a basic point for a mobile phone. I would really appreciate any feedback about this.
Thanks.
Click to expand...
Click to collapse
It has full A2DP which means you can control the device using the stereo itself, something the iphone cannot do
Audio/Video Remote Control Profile (AVRCP) is what works properly on the Desire, the iphone does not have this support
The Desire supports the following Bluetooth Profiles
A2DP,AVRCP, GAP, GOEP, HFP, HSP, PBAP, SPP, Service Discovery Application Profile
This is a full list of all the bluetooth layers
Advanced Audio Distribution Profile (A2DP)
Audio/Video Remote Control Profile (AVRCP)
Basic Imaging Profile (BIP)
Basic Printing Profile (BPP)
Cordless Telephony Profile (CTP)
Device ID Profile (DID)
Dial-up Networking Profile (DUN)
Fax Profile (FAX)
File Transfer Profile (FTP)
General Audio/Video Distribution Profile (GAVDP)
Generic Access Profile (GAP)
Generic Object Exchange Profile (GOEP)
Human Interface Device Profile (HID)
Intercom Profile (ICP)
Object Push Profile (OPP)
Personal Area Networking Profile (PAN)
Phone Book Access Profile (PBAP)
Serial Port Profile (SPP)
Service Discovery Application Profile (SDAP)
SIM Access Profile (SAP,SIM)
Synchronisation Profile (synch)
Video Distribution Profile (vdp)
Wireless Application Protocol Bearer (WAPB)
Works well with my BT Parrot CK3300 kit.
Ive got a Pioneer 7100BT winging its way to me, that has A2DP, im hoping it will work well with my Desire. Will post results when i get it and install it tomorrow.
Seems to work ok with my Standard Motorola headset.
Hoping to be able to est it with a bluetooth stereo soon.
ronnyuk said:
It has full A2DP which means you can control the device using the stereo itself, something the iphone cannot do
Audio/Video Remote Control Profile (AVRCP) is what works properly on the Desire, the iphone does not have this support
The Desire supports the following Bluetooth Profiles
A2DP,AVRCP, GAP, GOEP, HFP, HSP, PBAP, SPP, Service Discovery Application Profile
This is a full list of all the bluetooth layers
Advanced Audio Distribution Profile (A2DP)
Audio/Video Remote Control Profile (AVRCP)
Basic Imaging Profile (BIP)
Basic Printing Profile (BPP)
Cordless Telephony Profile (CTP)
Device ID Profile (DID)
Dial-up Networking Profile (DUN)
Fax Profile (FAX)
File Transfer Profile (FTP)
General Audio/Video Distribution Profile (GAVDP)
Generic Access Profile (GAP)
Generic Object Exchange Profile (GOEP)
Human Interface Device Profile (HID)
Intercom Profile (ICP)
Object Push Profile (OPP)
Personal Area Networking Profile (PAN)
Phone Book Access Profile (PBAP)
Serial Port Profile (SPP)
Service Discovery Application Profile (SDAP)
SIM Access Profile (SAP,SIM)
Synchronisation Profile (synch)
Video Distribution Profile (vdp)
Wireless Application Protocol Bearer (WAPB)
Click to expand...
Click to collapse
Hope someone can figure this out:
I've had experience with 3 mobiles connecting to the built-in bluetooth in my car (HTC Tytn II, HTC Hero and Nokia e71) my concern is the following:
With the Nokia, when I get a call, I hear the phone ringtone through the car speakers. But with both HTCs I couldn't, I hear the default car ringtone, which is REALLY annoying.
The nokia e71 has the following bluetooth specs:
Bluetooth version 2.0 with Enhanced Data Rate
- Bluetooth profiles: DUN, OPP, FTP, HFP, GOEP, HSP, BIP, RSAP, GAVDP, AVRCP, A2DP
does anyone know if one of the these profiles is responsible for this? which one? I hope it would work with the Desire.
by the way, does making the phone visible before connecting make any difference? (just wondering)
Yet another HTC handset I can't get to work with my factory fit blue-tooth in my Skoda Superb (delete / install any VW Audi group car)
sh500 said:
Works well with my BT Parrot CK3300 kit.
Click to expand...
Click to collapse
Hi, I have the CK3200 LS-COLOR and I can't get the contacts to load on the parrot, did you have any teething troubles?
Pumpkin Lantern said:
Hi, I have the CK3200 LS-COLOR and I can't get the contacts to load on the parrot, did you have any teething troubles?
Click to expand...
Click to collapse
No problems at all. Just a standard pairing; it took less than a minute to auto sync the address book and I was ready to go.
I've never had problems with this kit; have sync'd numerous WinMo devices, Blackberrys (is that the plural?!) (still active for work) and now the Android device.
beaker656 said:
Yet another HTC handset I can't get to work with my factory fit blue-tooth in my Skoda Superb (delete / install any VW Audi group car)
Click to expand...
Click to collapse
VAG cars need phones that use the RSAP Bluetooth profile, it's a bit of a wierd profile and stands for Remote Sim Access Profile, now looking this up for you I can only see some blackberry and Nokia phones that have this profile.
Bluetooth phone prep is a bit of a waste of time at the moment as the company who writes the software are not fully integrating there systems with everyone else, they are also not following standard A2DP procedures, I would imagine this is due to a partnership thing with people like Nokia and company cars etc.
Next time save the 600 quid or so you pay to have bluetooth prep and get a decent stereo like I have in my Audi, unless you got satnav too then you are stuffed
I have enclosed a link on VAG group phone prep and HTC phones, make sure your SIM card is of the new Variety
http://audiforum.us/multimedia/11189-audi-bluetooth-rsap-adapter-htc-touch-pro.html
I've had mixed results.
In my car the Desire works perfectly with the Parrot CK3300. I get full bluetooth contact sync, voice dialling works fine (the CK3300 does the voice recognition as the Desire doesn't do it over bluetooth) and calls come through loud and clear.
The wife has the lower CK3000 Evo. This doesn't have a display, so you send contacts to the kit over bluetooth and then record voice tags against them so that the kit can do voice dialling. Unfortunately the Desire refuses to send contacts to it and claims that the kit doesn't support sending contacts over bluetooth. This unfortunately means the wife can use the kit for incoming calls, but has no voice dialling for outgoing calls when she also upgrades to the Desire on Saturday when her contract's up.
Dae.
But what about voice dialling over Bluetooth with any of those?
The Android OS doesn't support voice dialling over bluetooth yet.
That's why I use the Parrot CK3300 - it does it on behalf of the phone. It basically syncs the phonebook to the kit. You then record the voice tags into the kit and associate them with a contact. You can then voice dial, which the kit will match up to the contact and dial using the phone.
Even when I've had phones that do support voice dialling I've always found the Parrot more effective.
Dae
ronnyuk said:
VAG cars need phones that use the RSAP Bluetooth profile, it's a bit of a wierd profile and stands for Remote Sim Access Profile, now looking this up for you I can only see some blackberry and Nokia phones that have this profile.
Bluetooth phone prep is a bit of a waste of time at the moment as the company who writes the software are not fully integrating there systems with everyone else, they are also not following standard A2DP procedures, I would imagine this is due to a partnership thing with people like Nokia and company cars etc.
Next time save the 600 quid or so you pay to have bluetooth prep and get a decent stereo like I have in my Audi, unless you got satnav too then you are stuffed
I have enclosed a link on VAG group phone prep and HTC phones, make sure your SIM card is of the new Variety
http://audiforum.us/multimedia/11189-audi-bluetooth-rsap-adapter-htc-touch-pro.html
Click to expand...
Click to collapse
Thanks for the explanation. I happen to own a VAG car, A4 B8 with concert radio.
So SAP profile is different than RSAP profile? Could this be responsible for the phone ringtone not going through the car speakers? Because everything else works perfectly, it pairs and connects automatically, syncs contacts and make/receive calls, except for the ringtone issue! Which sounds like an ambulance siren.
What stereo system did you install?
daesimps said:
I've had mixed results.
In my car the Desire works perfectly with the Parrot CK3300. I get full bluetooth contact sync, voice dialling works fine (the CK3300 does the voice recognition as the Desire doesn't do it over bluetooth) and calls come through loud and clear.
The wife has the lower CK3000 Evo. This doesn't have a display, so you send contacts to the kit over bluetooth and then record voice tags against them so that the kit can do voice dialling. Unfortunately the Desire refuses to send contacts to it and claims that the kit doesn't support sending contacts over bluetooth. This unfortunately means the wife can use the kit for incoming calls, but has no voice dialling for outgoing calls when she also upgrades to the Desire on Saturday when her contract's up.
Dae.
Click to expand...
Click to collapse
That's not good to read at all if I remember correctly I think I have on my car the same parrot model as your wife. My parrot is working perfect with Omnia and Xperia but I was afraid it wouldn't work with Desire and it seems I was right to be afraid. That's a huge problem for me.
Works perfectly with my Motorola H500 Bluetooth Headset.
xmfreak said:
That's not good to read at all if I remember correctly I think I have on my car the same parrot model as your wife. My parrot is working perfect with Omnia and Xperia but I was afraid it wouldn't work with Desire and it seems I was right to be afraid. That's a huge problem for me.
Click to expand...
Click to collapse
It's a big deal for her too. I'm hoping that it'll be fixed in a future update. I'm glad we thought to check it before she upgraded to the Desire. She's going to hold off upgrading until this issue is resolved as she spends a lot of time in the car and it's not cheap to upgrade the handsfree kit. It's a deal breaker for her.
salahag said:
Thanks for the explanation. I happen to own a VAG car, A4 B8 with concert radio.
So SAP profile is different than RSAP profile? Could this be responsible for the phone ringtone not going through the car speakers? Because everything else works perfectly, it pairs and connects automatically, syncs contacts and make/receive calls, except for the ringtone issue! Which sounds like an ambulance siren.
What stereo system did you install?
Click to expand...
Click to collapse
I installed a Blaupunkt MP68 but would not recommend it as it's pretty old now, the good thing was in the day it matched the Audi Red dials perfect and was German so I stuck with it.
All the Pioneer new series of BT headunits have Parrot BT built in so I would recommend one of those.
hmmm ... where does one go to get at slightly more advanced settings for BT? The Settings>Wireless & Networks options are very basic. I'm hoping to be able to tweak something to make it start working with my Audi A5. I suppose I'm asking is there anything like Sim Access Profile or Jetware out there?
Anyone any ideas? I searched Marketplace but nothing relevant came up.
I have found that my motorola headset keeps connecting and disconnecting like it is going out of range.
Thing is, it can be in my pocket about a foot from my headset and still disconnect and reconnect several times a minute.
Tried connecting my Galaxy S to some A2DP speakers, found it would pair then fail to connect, constantly reporting "Paired but not connected".
After a bit of poking around, I found in /system/etc/bluez/audio.conf:
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Switch to master role for incoming connections (defaults to true)
#Master=true
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
Changed to:
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control,Headset,Gateway,Source
#Disable=
# Switch to master role for incoming connections (defaults to true)
#Master=true
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
Rebooted, and everything works like a charm. Probably only need to enable the additional profiles.
Here's the diff for those so inclined:
Code:
--- audio.conf.dist
+++ audio.conf
@@ -5,8 +5,8 @@
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
-Enable=Sink,Control
-Disable=Headset,Gateway,Source
+Enable=Sink,Control,Headset,Gateway,Source
+#Disable=
# Switch to master role for incoming connections (defaults to true)
#Master=true
@@ -19,7 +19,7 @@
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
-#AutoConnect=true
+AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
@@ -27,7 +27,7 @@
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
-#HFP=true
+HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
wiimote support
interesting to know that, thanx for sharing buddy
is it possible to get the sgs connected to a Wiimote? i think i had a similer problem when i tried to pair it with the wiimote, it seems to pair fine but it just wont connect, i appreciate your support
Will it work with car based handsfree?
kloodee said:
interesting to know that, thanx for sharing buddy
is it possible to get the sgs connected to a Wiimote? i think i had a similer problem when i tried to pair it with the wiimote, it seems to pair fine but it just wont connect, i appreciate your support
Click to expand...
Click to collapse
The Wiimote is a different beast - it's a HID device, and I don't know that the hidp module is included in the Galaxy kernel, or whether the proprietary bluetooth interface supports it.
ondoteam said:
Will it work with car based handsfree?
Click to expand...
Click to collapse
Yep, should do.
sorry, but how do i pull this file? i tried copying it with linda file manager to my sd but is doesn't copy.
aridoasis said:
sorry, but how do i pull this file? i tried copying it with linda file manager to my sd but is doesn't copy.
Click to expand...
Click to collapse
You'll need root - I just edited the file in place, but if you have a copy on your SD card, you could use Root Explorer to paste it over the existing one after making /system R/W.
hmm.. i'm getting 'error opening file'
Tell me what steps you're performing exactly, and I may be able to point you in the right direction.
i'm pretty sure i'm missing something...
i'm using linda explorer
i got to /system/etc/bluez/
click on audio.conf
so, i'm made to select what to open the file with
the only logical thing for me to use was dropbox text editor
is there a special file editor i need to use?
Your device needs to be rooted, and you need to use Root Explorer - you won't have permission to modify the file without root privileges.
lol. ok. my device is already rooted. thought i could do it without having to buy root explorer.
Any tool that will let you remount /system read-write, and write files as root will do - there may be others, but Root Explorer works particularly well, so that's the only one I'm aware of. I just did it from the command line, but you need a level of comfort with linux for that.
thanks spoidar. i was finally able to do it. just got super manager. not as great as root explorer, but it did the job.
Glad to hear you got it sorted
spoidar said:
The Wiimote is a different beast - it's a HID device, and I don't know that the hidp module is included in the Galaxy kernel, or whether the proprietary bluetooth interface supports it.
Yep, should do.
Click to expand...
Click to collapse
Thank you!! Working
Method works using root explorer for my e-blue airhifi bluetooth stereo receiver. Previously can only pair but cannot connect.
kaikee said:
Method works using root explorer for my e-blue airhifi bluetooth stereo receiver. Previously can only pair but cannot connect.
Click to expand...
Click to collapse
Good to hear - it astounds me that Samsung wouldn't get something so simple right.
BT Handsfree - not working
spoidar said:
Good to hear - it astounds me that Samsung wouldn't get something so simple right.
Click to expand...
Click to collapse
I edited and saved audio.conf on SMASUNG GALAXY S in root mode.
Then I rebooted - but no change.
I still get the same message "Paired but not connected"
ANy help ?
It works like a charm. Thank you very much man.
I am a android noob but i have figured out from rooting to editing the audio.conf
And now it connects to all my headset, helmet a2dp headset and to my car's bt system.
I have to say that ia had big prtoblems in the past with bt. Sometimes when a headset was connected an tried to call it frozed my phone to the point that i had to took out the battery to reset it. Right now, after the process, i used my phone for 3 days with intensive BT activitiy (from calls to music and to all headsets) and no freeze.
vrajitoru said:
It works like a charm. Thank you very much man.
I am a android noob but i have figured out from rooting to editing the audio.conf
And now it connects to all my headset, helmet a2dp headset and to my car's bt system.
I have to say that ia had big prtoblems in the past with bt. Sometimes when a headset was connected an tried to call it frozed my phone to the point that i had to took out the battery to reset it. Right now, after the process, i used my phone for 3 days with intensive BT activitiy (from calls to music and to all headsets) and no freeze.
Click to expand...
Click to collapse
Can I know after editing and saving audio.conf file - what are other steps to be performed in order to solve this problem?
Though I rebooted - the same problem continues.
Pl help?
i wanted to use the bluetooth headset profile of my htc wildfire to answer calls from a bluetooth enabled pc. how can i do that. when i search the services from pc side, the headset profile is not seen. but the htc official website has shown that wildfire has headset profile in their specs. what is true then.
the htc website shows that the wildfire bluetooth has following profiles.
• A2DP for wireless stereo headsets
• FTP and OPP (object push) for file transfer
• Other supported profiles: AVRCP, GAP, GOEP, HFP, HSP, PBAP, SPP, Service Discovery Application Profile
but i just used ftp, opp profiles. pdanet offers DUN which works only with certain pc bluetooth stacks. eventhough thanks to pdanet.
and what about using other above profiles. how to use them
try bluesoleil.. search it over google
I have a Tasker Profile which should be activated based on a Bluetooth state - i.e. when connected to my car Bluetooth system. When creating the Profile I used a search to locate the correct Bluetooth device from the list. The problem is that this profile is not being activated when the phone is connected to the car Bluetooth system - the Tasker notification just says that there is no active profile.
I've tried adding both the Bluetooth device name and address using the Search function, and I've also left both the name and address blank to see if the Profile can be triggered by connecting to any Bluetooth device, but the Profile never gets triggered. Has anyone else had any success triggering a Bluetooth Connected Profile on their G4?
I'm running Tasker 4.7m on a rooted LG G4 TWN model (Android 5.1).
The Tasker Profile definition is below:
Profile: In Honda (17)
State: BT Connected [ Name:JVC Unit Address:00:10:601:AC:20/00:10:601:AC:20 ]
Enter: Gmail Notifications Off (14)
A1: Secure Settings [ Configuration:Gmail Notifications Disabled Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
Exit: Gmail Notifications On (15)
A1: Secure Settings [ Configuration:Gmail Notifications Enabled Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
I use Tasker to open Waze when connected to the Bluetooth in my car and it works no problem. The exit task to close/kill Waze doesn't seem to work for some reason.
rick09 said:
I use Tasker to open Waze when connected to the Bluetooth in my car and it works no problem. The exit task to close/kill Waze doesn't seem to work for some reason.
Click to expand...
Click to collapse
Any chance that you could paste an export of your Profile definition here so that I can compare it with mine?
Profile: Waze (2)
State: BT Connected [ Name:CAR KIT Address:00:13:04:Blah:Blah ]
Enter: Waze (3)
A1: Launch App [ App:Waze Data: Exclude From Recent Appsff Always Start New Copyff ]
Exit: Close Waze (5)
A1: [X] Kill App [ App:Waze Use Rootff ]
A2: [X] Say [ Text:KILLING WAZE Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focusn Networkff Continue Task Immediatelyff ]
Is that what you're looking for?
rick09 said:
I use Tasker to open Waze when connected to the Bluetooth in my car and it works no problem. The exit task to close/kill Waze doesn't seem to work for some reason.
Click to expand...
Click to collapse
rick09 said:
Profile: Waze (2)
State: BT Connected [ Name:CAR KIT Address:00:13:04:Blah:Blah ]
Enter: Waze (3)
A1: Launch App [ App:Waze Data: Exclude From Recent Appsff Always Start New Copyff ]
Exit: Close Waze (5)
A1: [X] Kill App [ App:Waze Use Rootff ]
A2: [X] Say [ Text:KILLING WAZE Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focusn Networkff Continue Task Immediatelyff ]
Is that what you're looking for?
Click to expand...
Click to collapse
Yes - thanks. It looks like you're doing it exactly the same way that I am, except for some reason mine isn't responding to the bluetooth connected event. Must be something on my phone that's interfering with it
???
itm said:
I have a Tasker Profile which should be activated based on a Bluetooth state - i.e. when connected to my car Bluetooth system.
Click to expand...
Click to collapse
Bluetooth Near works for me on my profile. I've not tried Bluetooth Connected.
Be aware that there is a lag exiting the profile though, based on the display off monitor interval. For my purposes however, the lag isn't important.
soyelmango said:
Bluetooth Near works for me on my profile. I've not tried Bluetooth Connected.
Be aware that there is a lag exiting the profile though, based on the display off monitor interval. For my purposes however, the lag isn't important.
Click to expand...
Click to collapse
Bluetooth Near doesn't trigger anything for me either, and I've tried this with a Bluetooth headset as well as the car Bluetooth. The Tasker logs don't register thing for any Bluetooth-related events it seems :0(
itm said:
Bluetooth Near doesn't trigger anything for me either, and I've tried this with a Bluetooth headset as well as the car Bluetooth. The Tasker logs don't register thing for any Bluetooth-related events it seems :0(
Click to expand...
Click to collapse
A few things to try, in no particular order...
Bluetooth hardware address is optional, try it without.
Select the Bluetooth name using the magnifying glass, to avoid typing errors.
Is the JVC unit always discoverable? (ie: broadcasting its name for tasker to see).
Are you giving the profile enough time to fire, according to either the screen on or screen off monitor values?
According to Bluetooth Connected help page, tasker only detects the act of connection or disconnection, but not the state of being connected.
Let us know how you get on... Good luck!
soyelmango said:
A few things to try, in no particular order...
Bluetooth hardware address is optional, try it without.
Select the Bluetooth name using the magnifying glass, to avoid typing errors.
Is the JVC unit always discoverable? (ie: broadcasting its name for tasker to see).
Are you giving the profile enough time to fire, according to either the screen on or screen off monitor values?
According to Bluetooth Connected help page, tasker only detects the act of connection or disconnection, but not the state of being connected.
Click to expand...
Click to collapse
Thanks for the suggestions. I did use the Search function to populate both the device name and address. I also tried specifying name only, and even leaving both blank (to test for any bluetooth device being connected, but none of these options worked.
The JVC Unit does seem to be discoverable - i.e. it always shows up when I scan for bluetooth devices. This problem isn't limited to the one unit however - I also can't get the profile to activate with the Parrot unit in my wife's car, or with a Sony MW600 headphone adapter.
Re. giving the profile enough time to fire - could you please elaborate on where I need to specify the appropriate values for this? (or do you mean am I waiting long enough? - in which case the answer is yes, I've waited 30 minutes after watching the unit connect to the JVC unit in the car!)
I just tried a different test. I created a simple profile with a single context of "BT Status on". I then turned off Bluetooth on the phone, turned it back on, and waited a few minutes. My new profile never activated. It seems that Tasker is completely blind to changes of Bluetooth state on my phone
???
itm said:
Re. giving the profile enough time to fire - could you please elaborate on where I need to specify the appropriate values for this? (or do you mean am I waiting long enough? - in which case the answer is yes, I've waited 30 minutes after watching the unit connect to the JVC unit in the car!)
Click to expand...
Click to collapse
You're definitely waiting long enough! See tasker preferences > monitor > display on monitoring, and display off monitoring. Tasker's help file explains how the values work.
itm said:
I just tried a different test. I created a simple profile with a single context of "BT Status on". I then turned off Bluetooth on the phone, turned it back on, and waited a few minutes. My new profile never activated. It seems that Tasker is completely blind to changes of Bluetooth state on my phone
???
Click to expand...
Click to collapse
Other things to try:
Watch out for battery savers, task killers, memory cleaners, background service freezers, phone boosters unwittingly killing Tasker.
Way back, when I used Titanium Backup to restore my apps, it did Secure Settings first then Tasker… didn't work! Long shot: Reinstall Tasker, then Secure Settings.
What a mystery!
itm said:
I have a Tasker Profile which should be activated based on a Bluetooth state - i.e. when connected to my car Bluetooth system. When creating the Profile I used a search to locate the correct Bluetooth device from the list. The problem is that this profile is not being activated when the phone is connected to the car Bluetooth system - the Tasker notification just says that there is no active profile.
Click to expand...
Click to collapse
you mentioned the tasker notification, but do you have "Run in Foreground" checked within the preferences? if you do not, then most likely the bluetooth trigger will not work.
I did have both Clean Master and Greenify installed, but have now uninstalled both of them and I still get the same problem. At this point I'm monitoring only for "BT Status On", but Tasker is not triggering my profile when I turn on Bluetooth (and wait for a few minutes).
I do also have the "Run in foreground" option set.
itm said:
I did have both Clean Master and Greenify installed, but have now uninstalled both of them and I still get the same problem. At this point I'm monitoring only for "BT Status On", but Tasker is not triggering my profile when I turn on Bluetooth (and wait for a few minutes).
I do also have the "Run in foreground" option set.
Click to expand...
Click to collapse
Did you ever figure out what the problem is? I'm seeing the same behavior. I can't get my Profile to activate when I connect my bluetooth headset.
I tried forgetting my bluetooth and re-adding it, no luck.
I'm currently on Marshmallow 6.0.1 on a Nexus 6 and Tasker v4.8
It turns out that the version Tasker that I purchased from the Amazon app store was not legitimate. I got a refund from Amazon, repurchased it from the Play Store, and now I don't have the problem
itm said:
It turns out that the version Tasker that I purchased from the Amazon app store was not legitimate. I got a refund from Amazon, repurchased it from the Play Store, and now I don't have the problem
Click to expand...
Click to collapse
Thank you very much. I downloaded a "mod" version and it didn't work until I downloaded from Play Store
Hi!
I face a problem with LineageOS and connecting my sports watch (Suunto Ambit3) to the smartphone in order to receive push notifications on the watch. The watch has to be paired via the Suunto Movescount app. Afterwards, when being in bluetooth range pushed notifications should be transferred to the watch, automatically. In addition, trainings I logged with the watch can be transferred to the app, too. With my stock ROM (Motorola G LTE XT1039 "peregrine", Android 5.1.2) this worked.
However, with LineageOS I can pair the watch with the Movescount App initially but it cannot reconnect after being disconnected once. Lineage smart lock shows that the watch is connected (trusted devices) but no data is transferred between the phone and my watch.
Has anyone a clue which settings to modify in order to make the connection work? What else could I do? Is there an alternative app that could Transfer the push notifications to the watch (Botifiy doesn't work) Thanks in advance
default_user0815 said:
Hi!
I face a problem with LineageOS and connecting my sports watch (Suunto Ambit3) to the smartphone in order to receive push notifications on the watch...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3469103
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Already did that.
Thank you.
Sorry, me again.
I didn't get an answer to my question in the corresponding sub-forum. Anyway, my next question is more or less a general question.
I still have no real clue why the connection with my watch works under the stock ROM and doesn't work under lineage OS. But I identified some differences in the build.prop files of the two ROMs:
In lineage the building.prop files shows
Code:
[...]# Bluetooth
qcom.bluetooth.soc=smd
qcom.bt.le_dev_pwr_class=1
ro.qualcomm.bluetooth.opp=true
ro.qualcomm.bluetooth.hfp=true
ro.qualcomm.bluetooth.hsp=true
ro.qualcomm.bluetooth.pbap=true
ro.qualcomm.bluetooth.ftp=true
ro.qualcomm.bluetooth.nap=true
ro.qualcomm.bluetooth.map=true
ro.bluetooth.sap=true
ro.bluetooth.dun=true
ro.bluetooth.hfp.ver=1.6
ro.qualcomm.bt.hci_transport=smd[...]
whereas the building.prop of the stock ROM looks like this:
Code:
[...]# system property for Bluetooth hci transport
#
ro.qualcomm.bt.hci_transport=smd
#
# system property for Bluetooth HFP version
#
ro.bluetooth.hfp.ver=1.6
#
# system property for Bluetooth SAP support
# Motorola disabled SAP
#
ro.qualcomm.bluetooth.sap=false
# Bluetooth LE power class
qcom.bt.le_dev_pwr_class=1[...]
Would it be possible that my issues are related to the differences within these files? Could I play around with the Bluetooth settings there without risking to brick my phone (of course I know it is a delicate thing to modify the building.prop file, but maybe there is a chance that....)?