Database Users

every phone call activates Bluetooth

Does anybody have an idea, why every call I made automaticaly activates Bluetooth?
I do not use any headset.

amir77a said:
Does anybody have an idea, why every call I made automaticaly activates Bluetooth?
I do not use any headset.
Click to expand...
Click to collapse
Have you installed Bluetooth Tools?
Not sure if that's even necessary or not, but certainly that software by very nature, does this so that incoming calls can be passed to Bluetooth headsets.
This can be altered, if you are using Bluetooth Tools, by enabling this item on the today screen, and turning OFF timed bluetooth mode.
If you are not using this, then I am not sure...

Yes, I do use Bluetooth tools.
I use it mainly for my GPS BT Receiver.
I will play with its options, and see if this can solved this.

amir77a said:
Yes, I do use Bluetooth tools.
I use it mainly for my GPS BT Receiver.
I will play with its options, and see if this can solved this.
Click to expand...
Click to collapse
Not solve mate - it's the whole intention of the software you installed.
Simply enable the Bluetooth Tools plugin on your today screen.
Then you will see a little clock icon.
Tap on this so it goes grey.
This means you just turned OFF the timed bluetooth option.
But mate, it ISN'T a bug, and is the very purpose of Bluetooth Tools for most people.
To get it to activate Bluetooth ONLY when a call comes in, so as to enable the headset.
Instead of PERMANENTLY having to leave BT on, and thus flatten the battery.

i'm pretty sure mine does it when i make the clock grey aswell

Rudegar said:
i'm pretty sure mine does it when i make the clock grey aswell
Click to expand...
Click to collapse
Rudegar,
If you grey out the clock, you turn OFF the timed element of Bluetooth.
It will then depend on whether you have Bluetooth ON, or Bluetooth OFF as to what happens then...
All the clock does, AFAIK, is enable or disable timed bluetooth...?

Yep.. guess you right. It's working so good with the BT GPS receiver, I'll just sit and enjoy, and let it work for 60 seconds, each call I make.

Even when I turn the clock grey it still comes on !
OK I can live with the 60secs business, it'll save battery life.
But what is the purpose of the 2 battery indicators 1&2 ?? Can't seem to suss that out ?

ekko star said:
Even when I turn the clock grey it still comes on !
OK I can live with the 60secs business, it'll save battery life.
But what is the purpose of the 2 battery indicators 1&2 ?? Can't seem to suss that out ?
Click to expand...
Click to collapse
They are two different Profiles as it were.
It means you can configure settings as you prefer for one device/gps/headset, and then click icon 2 and set another lot, for a different device, then quickly change easily.
That info is from the Bluetooth Tools site, where it is all mentioned.
I don't wish to sound too rude, but it would be helpful if people seeking support would try reading the site where they download stuff from, or the original author's site, first...
http://bluetooth.i-networx.de/index_e.html

thanks for the help mate and thanks for telling me what it already says on that site.
My question is really how to configure those two settings ? I can't work out how I can set different settings for profile 2 nor how I can change 1 ?

ekko star said:
My question is really how to configure those two settings ? I can't work out how I can set different settings for profile 2 nor how I can change 1 ?
Click to expand...
Click to collapse
Well, it's dead simple (actually, was too simple for me to understand until someone pointed it out to me...): you tap on '1', so that it gets the little grey box around it. Then you use the normal settings dialogs of the PPC to configure things like backlight timeout, brightness etc. Then go back to the Today screen, tap on '2', and again configure your PPC. Now, each time you tap '1' or '2', the set of settings will be restored. Unfortunately, I couldn't find a list of which settings are actually subject to that toggle. I know that the backlight timing is, because that's what I use it for: while TomTom is running, I don't want the backlight to go out, so while '2' was actibe, I configured the backlight accordingly. Now '1' is my normal mode, and '2' is the "navigation" mode.
Cheers
Daniel

Android 2.0 - Bluetooth shame!!!

Hello folks,
in the new Android 2.0 there's a limit on Bluetooth: you can't enable DISCOVERABLE mode without passing through an Android dialogbox and only for a limited period of time (max 300 seconds): SHAME!!! This means that for DUN connections (or similar) the user should press YES every 300 secs (on Droid probably there's a bug, only 120 secs are allowed).
The problem could be found on the GIT at line 758: the application requires the WRITE_SECURE_SETTINGS permission to run the setScanMode method, unfortunately not available at user level.
Hope this could be fixed for homebrew roms.
Cheers

I thought it had always been that way Isn't the limit there as a security measure? Oh well, thanks for pointing out a solution, should be interesting to see if this is adopted in to new ROMs.

Paragnosta said:
Hello folks,
in the new Android 2.0 there's a limit on Bluetooth: you can't enable DISCOVERABLE mode without passing through an Android dialogbox and only for a limited period of time (max 300 seconds): SHAME!!!
Click to expand...
Click to collapse
That is an EXCELLENT feature. Prevents the user from accidentally leaving it on, and thus vulnerable.
This means that for DUN connections (or similar) the user should press YES every 300 secs (on Droid probably there's a bug, only 120 secs are allowed).
Click to expand...
Click to collapse
INCORRECT. The host only needs to be discoverable when the connection is established. The connection, once established, can remain open for an unlimited amount of time.

lbcoder said:
That is an EXCELLENT feature. Prevents the user from accidentally leaving it on, and thus vulnerable.
Click to expand...
Click to collapse
Sorry, but this is not so excellent as you can think. It's OK when user enable the discoverable mode from the Android settings, fine and good. But if you want to create a background service always listening for incoming connections, simply you can't!!!
You must use a system dialogbox each time you wanna be discoverable and it's not so cool
One example? If you want, you can't receive proximity marketing messages, unless you KNOW when and where enable the discoverable mode. And if you want a public DUN service always discoverable by anyone? You can't!!!
IMHO, this is a great limit for developers, that's why the Bluetooth is dying...
Cheers

Paragnosta said:
Sorry, but this is not so excellent as you can think. It's OK when user enable the discoverable mode from the Android settings, fine and good. But if you want to create a background service always listening for incoming connections, simply you can't!!!
You must use a system dialogbox each time you wanna be discoverable and it's not so cool
One example? If you want, you can't receive proximity marketing messages, unless you KNOW when and where enable the discoverable mode. And if you want a public DUN service always discoverable by anyone? You can't!!!
IMHO, this is a great limit for developers, that's why the Bluetooth is dying...
Cheers
Click to expand...
Click to collapse
I have yet to meet anyone who WANTs to receive proximity marketing messages.
That's like WANTING spam in your inbox...
Or WANTING junk mail...
Or LOVING commercials...

Paragnosta said:
Sorry, but this is not so excellent as you can think. It's OK when user enable the discoverable mode from the Android settings, fine and good. But if you want to create a background service always listening for incoming connections, simply you can't!!!
Click to expand...
Click to collapse
It is a PHONE, not a server. If you are using the phone, then it is in YOUR HAND, which means you can click the button. And the use-case for a phone is that you use the PHONE to connect to OTHER DEVICES -- not the other way around!
You must use a system dialogbox each time you wanna be discoverable and it's not so cool
Click to expand...
Click to collapse
So? If the thing is always discoverable, what's to stop someone from hacking in? This is a necessary feature, and it doesn't interfere with appropriate use.
One example? If you want, you can't receive proximity marketing messages, unless you KNOW when and where enable the discoverable mode.
Click to expand...
Click to collapse
Again, the devices need to be paired ANYWAYS. You can't just bluetooth crap for fun and have everything receive it. BAD IDEA, DANGEROUS.
And marketing messages? As in ADVERTISEMENTS? Seems like a good thing to BLOCK AT ALL COSTS.
And if you want a public DUN service always discoverable by anyone? You can't!!!
Click to expand...
Click to collapse
Huh?
Again, it is a ***PHONE***. Not a server! You *DO NOT WANT THAT*.
IMHO, this is a great limit for developers, that's why the Bluetooth is dying...
Click to expand...
Click to collapse
No it isn't. It just prevents developers from doing things that they shouldn't be doing or have no legitimate reason to be doing.

Well, anyway you look at it, its a limitation put in place to protect people that don't know what they're doing at the expense of those who do.
Example:
I wanted to use KBlueLock (Locks the screen when bluetooth device disapears and [optionally] unlocks when it appears). I can't because the device won't stay discoverable. As soon as the timeout runs out, the screen is locked.

stormlabs said:
Well, anyway you look at it, its a limitation put in place to protect people that don't know what they're doing at the expense of those who do.
Example:
I wanted to use KBlueLock (Locks the screen when bluetooth device disapears and [optionally] unlocks when it appears). I can't because the device won't stay discoverable. As soon as the timeout runs out, the screen is locked.
Click to expand...
Click to collapse
Your phone doesn't need to be discoverable for your headset to remain visible to it, so either your description is wrong, or the problem that you perceive is unrelated to your guess about the cause.

lbcoder said:
Your phone doesn't need to be discoverable for your headset to remain visible to it, so either your description is wrong, or the problem that you perceive is unrelated to your guess about the cause.
Click to expand...
Click to collapse
I'm not talking about a headset. KBlueLock is part of KDE's bluetooth framework in Linux. It locks the screen when a certain BT device is no longer present.
You're assuming a pairing is required when it isn't. The mere presence (or not) of that device in a scan is enough.

Paragnosta said:
Hello folks,
in the new Android 2.0 there's a limit on Bluetooth: you can't enable DISCOVERABLE mode without passing through an Android dialogbox and only for a limited period of time (max 300 seconds): SHAME!!! This means that for DUN connections (or similar) the user should press YES every 300 secs (on Droid probably there's a bug, only 120 secs are allowed). ..........
Cheers
Click to expand...
Click to collapse
I second that. My bluetooth in my car and laptop would not automatically pair unless I have discoverable mode active. Its a hassle to always have to go to your bluetooth settings to activate that field EVERYTIME, otherwise it would not pair. They should have an option to have it turned on all the time. The user should have the freedom to choose! and not restrict them due to security issues.. i had blackberry's, and nokias, and had no problem with people trying to "hack" into my phone or whatever since my bluetooth was on all the time (and is automatically discoverable)

So in order for the phone to be on discoverable mode for a longer time, this would require editing the code for bluetooth right? Would this mean that the application will be rooted to the android platform? I am working on creating an app that allows bluetooth to be on discoverable mode all the time so perhaps with what the Bluetooth Adapter available to me right now in API 2.0, will prevent me from achieving this goal... Does anyone have code suggestions that can help me pass this obstacle? Below is what I have to make bluetooth discoverable for 300 seconds max. The Bluetooth Adapter prevents me from going beyond that time and also does not let me proceed to make bluetooth discoverable without user permission.
Intent discoverableIntent = new Intent(BluetoothAdapter.ACTION_REQUEST_DISCOVERABLE);
discoverableIntent.putExtra(BluetoothAdapter.EXTRA_DISCOVERABLE_DURATION, 300);
startActivity(discoverableIntent);
Thank you for your help in advance.
Sincerely,
AndroidTeam5

opinions opinions.. one man telling another man what they want and others telling others what they do and do not need.
The BOTTOM LINE is we should always have the option.. for example you MAY THINK (your opinion) that proximity marketing is like spam but freaking OBVIOUSLY SOMEONE WANTS IT he JUST SAID IT WOULD BE A GOOD THING... so damn everyone needs to take their opinions and leave..
You only post in this thread if you think it is useful.. not if you dont..
anyway proximity marketing would be good for example you are walking around a new area and you are really interested in what there is to eat around you.. and what deals they may have.. well you are walking down the street and BLING it tells you what the specials are..
Its funny cause everyone hates on spam and advertisments because we are always getting shown them when we are doing something else.. so its annoying.. but proximity marketing means that you turn that **** on when you are walking around interested in what the hell is available to you...

Bluetooth
I looked up more on Bluetooth and discover that I could perhaps use the NDK to make use of the Bluetooth Stack. Has anyone use Android Bluetooth using NDK? Is this recommended?
Thank you
AndroidTeam5

Bluetooth does not connect automatically

I've been using the Belkin Bluetooth Car Hands-Free Kit for the last year with my Nexus 4.
http://www.amazon.com/Belkin-Bluetooth-Hands-Free-BlackBerry-Smartphones/dp/B004CLYJ2I
For the most part it has worked great. However, my new Note 3 will not connect automatically to the device, I always have to turn the screen on and select the bluetooth device to connect to it. My Nexus 4 would simply connect to it automatically if the bluetooth was switched on.
Any ideas?

hfuizo said:
I've been using the Belkin Bluetooth Car Hands-Free Kit for the last year with my Nexus 4.
http://www.amazon.com/Belkin-Bluetooth-Hands-Free-BlackBerry-Smartphones/dp/B004CLYJ2I
For the most part it has worked great. However, my new Note 3 will not connect automatically to the device, I always have to turn the screen on and select the bluetooth device to connect to it. My Nexus 4 would simply connect to it automatically if the bluetooth was switched on.
Any ideas?
Click to expand...
Click to collapse
I had similar issues with my bluetooth headset. When I would press the connect button on my bluetooth it wouldn't automatically connect, and the only solution I found was re-arranging my quick toggles in the notification bar so when I pull it down I can quickly access bluetooth settings and devices.

Yep am having problems with note 3 bluetooth. For a top of range phone, this bluetooth is crap. 2 headsets works when it wants and 6 works wagons only works in some! Am surprised no one else as commented on the bluetooth
Sent from my SM-N9005 using xda premium

I had the same issue that my N3 didn't connect automatically to my BT-devices. I stumbled over a thread where I found some one else having the same issue who recommended the app "Bluetooth auto connect". I downloaded the app and now it just works. If you have the BT-scan dialog enabled, you see how it switches between the different paired devices in the list until it locks on to the one that's in range.
If you don't like that dialog, you can disable it using wanam (I think). Hope this helps.

Mikegrmn said:
I had the same issue that my N3 didn't connect automatically to my BT-devices. I stumbled over a thread where I found some one else having the same issue who recommended the app "Bluetooth auto connect". I downloaded the app and now it just works. If you have the BT-scan dialog enabled, you see how it switches between the different paired devices in the list until it locks on to the one that's in range.
If you don't like that dialog, you can disable it using wanam (I think). Hope this helps.
Click to expand...
Click to collapse
Thanks for the suggestion, I'll give it a try. Does this app have any affect on your battery life?

hfuizo said:
Thanks for the suggestion, I'll give it a try. Does this app have any affect on your battery life?
Click to expand...
Click to collapse
Not for me. But I may not be the average user. I'm getting 3 days of battery life out of my N3. I only turn wireless (3g / wifi) on when I need it and do the same with BT. But I found it really inconvenient to have to select my connected BT device. For switching BT on and off, I use tasker. I have a setting that checks for the music app of my choice, and when I start it and have no headphones connected, tasker turns on BT.

[Q] Do something when phone removed from NFC Tag

Iv done some reading and am still a little confused as to if I can use something like Trigger or something like Trigger to turn off toggles etc. when my phone is removed from a NFC Tag. Currently I use Trigger to turn on BT and Turn off Wifi etc.. when I place my phone on a NFC tag when I get into my car and that works great. But when I get out of my car and remove my phone from said NFC Tag I would like to turn off BT etc.. Can this be done?
I have a Verizon Galaxy S5 running NE9.
Thanks,
~SomeGuy2008

It can be done but you'll have to set up another trigger to disable them. So one trigger is turning on BT/ off Wifi when you touch it the first time. The second trigger would be the opposite BT off/ wifi on but you can't just remove it from the NFC tag, you have to tap it again

Thanks for the idea. I found that I was over engineering the whole idea between Tasker and Trigger. After reading your reply I figured I would only use Trigger. I had to create 2 Tasks in Trigger. When I get into my car I put my phone into the phones car dock (which has a NFC Tag on it) . 1 triggers via NFC which turns on BT and connects to my Cars BT,disables wifi, enables Mobile Data and opens Waze or whatever navigation app I want. The other Task does the reverse when disconnecting from my Cars BT (aka getting out of my car and taking my phone with me). After various tests its about 99.99999% accurate. And I works with only 1 initial NFC tap.
Thanks again for the idea.
~SomeGuy2008

Bluetooth question

I am coming from a long history of HTC use and so I apologise if this question has an obvious answer.
Previously, if I wanted to connect to my bluetooth in the car (previously paired with), I would just hit the bluetooth button in quick settings to turn it on and that was it, just like connecting to wifi.
If I do this on my S7E, I then get another screen popping up that tells me my device is visible to others and lists previously paired devices for me to select from, and then I have push the back button to leave that screen?
Is there a simpler way as I used to do on my HTC?
cheers
C.
PS - I am sure this will be the first of a number of questions as I get used to TouchWiz and Marshmallow......Sorry.....

crazyC said:
Previously, if I wanted to connect to my bluetooth in the car (previously paired with), I would just hit the bluetooth button in quick settings to turn it on and that was it, just like connecting to wifi.
Click to expand...
Click to collapse
Have you ever *paired* your new phone with your car?
I've only had two cars with BT in them, but in both cases the car and phone had to be paired before they would work together.
Once that was done then it would work as you expect.
Specifics of getting your *car* into pairing mode I can't help with, but once you do that you should be able to select it while scanning from the phone (as you've seen already the phone will list devices it finds) and you can finish walking through the pairing.

C0derbear said:
Have you ever *paired* your new phone with your car?
I've only had two cars with BT in them, but in both cases the car and phone had to be paired before they would work together.
Once that was done then it would work as you expect.
Specifics of getting your *car* into pairing mode I can't help with, but once you do that you should be able to select it while scanning from the phone (as you've seen already the phone will list devices it finds) and you can finish walking through the pairing.
Click to expand...
Click to collapse
Oh yes, it was paired with the bluetooth fine (its actually a visor BT device, not the car itself), and when I turn on the BT it shows up on the list of previously paired devices)

Don't have to make it a trusted device for it to auto-pair?

Why turn Bluetooth off at all?
Just leave it on.
Regards,
Dave
Sent from my Nexus 6P using Tapatalk

neezy13 said:
Don't have to make it a trusted device for it to auto-pair?
Click to expand...
Click to collapse
Nope, just had to be paired.
Trusted Device brings in the Smart Lock stuff, which enables the option of having your phone NOT authenticate you (pattern/pin/finger/passwd) when connected.
For example, I have my car bluetooth set as a trusted device so that when I'm driving I don't get any identity challenge to use the phone (like for navigation), the screen will just come on as requested.

Smart lock is blocked by my exchange administrator as I get my work emails on my phone.
I turn the Bluetooth on the phone off because I don't turn the one in the car off and it's just outside the house and will stay connected.
Sent from my S7 Edge