Related
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
Apologies if this is an FAQ, but I've had a quick look and drawn a blank.
I've just got my first Windows mobile phone (Vario II) and one of the things I really miss compared to my old Nokia, is that when I connect my bluetooth headset, I'd like the phone to switch to 'auto answer' and for the volume to be set to max. When I disconnect the headset, I'd like the phone to refert to a 'normal' or 'general' profile.
I require this because I use it on a motorcycle in conjunction with an intercom system, and I need the phone to auto answer after say 2 rings.
Is this possible on a smartphone?
Regards,
Glenn
Join the club mate......
I've been using the Vario2 in combination with a Nolan N-102 with the N-comm BT kit on it.....
I've been #$^&# with it for weeks now and I've made some progression...
First you need a program that allows you to select profiles like Nokia used to have...
I use PocketzenPhone but maybe there are some other(better) programs to do that.....
So then u can swith to a bike profile I've made and enable auto answer....
I've run the cab file to redirect BT sounds to my helmet in stereo (floats somewhere on this forum)
The only thing I can't do at the moment is enable Voicedial from the helmet...
If I press the button designed to start it ........f%ck all happens....
Still working on that but I'm running out of ideas....so any help would be appreciated...
Danny.
Pdanny said:
Join the club mate......
I've been using the Vario2 in combination with a Nolan N-102 with the N-comm BT kit on it.....
I've been #$^&# with it for weeks now and I've made some progression...
First you need a program that allows you to select profiles like Nokia used to have...
I use PocketzenPhone but maybe there are some other(better) programs to do that.....
So then u can swith to a bike profile I've made and enable auto answer....
I've run the cab file to redirect BT sounds to my helmet in stereo (floats somewhere on this forum)
The only thing I can't do at the moment is enable Voicedial from the helmet...
If I press the button designed to start it ........f%ck all happens....
Still working on that but I'm running out of ideas....so any help would be appreciated...
Danny.
Click to expand...
Click to collapse
Hi, the reason you can't activate voice dialing from your headset might be to do with the BT Audio cab you have installed to redirect sound through your headset. If the cab you have installed is the most common one floating around then this actually disables the launch of voice dialing in favour of being able to toggle between sound in the headset and sound on the phone (pressing and holding down the call button for a few seconds on your headset normally).
If you look in the registry HKLM>software>OEM>voicecommand, if launchapenable has a value of 0 then it is disabled. You can enable it again by changing the value to 1 but this will mean that your headset button will now not work as an audio toggle feature because it will launch the voicedial software every time.
Not sure if this is the answer to your problem but it sounds like it might be, hope this helps
Am trying as we speak....thanks for the reply....see wat happens...
D.
Well.....Ive got good news and bad news....
The good news is that I can trigger voicecommand now......
The bad news is that MS voice command 1.6 is not reconizing my accent...(dutch)...
So out of 10 tries it never called the number i wanted.....
So I tried the build in SDdialer.....and that one is doing a better job....
However I can't make the sounds to stick in my helmet........
I mean...
With MSVC by pressing the button on the helmet I could redirect the sound to the helmet and get a voicecommand tone at the same time....
By symply not speaking or saying '"cancel" it would cancel the voicecommand but the sound stayed in the helmet.....
With SDdialer following the same steps as above the sounds does not stay in the helmet but goes back to the speaker......
Any ideas????
BTW is there a dutch version of MS voice command?
If you go back into the registry, in the same location as before, check the value that is in VoiceCmdDuration (This is the amount of time the voice prompt stays active for in seconds) .. the audio cab file usually sets this to 86400 (24 hrs in seconds), if yours is low eg. 10, 20, 30 etc.., set it to 86400 and that may sort out the problem.
Duration is set fort 24 hrs....already..
Funny thing is that MSVC is not cutting out and the sddialer is...
Regsetting stay the same.....
By pressing the button on helmet I just change the exe file.....
Only option is to try and get MsVC to work and get use to my voice....
D.
Hmmm booking slow process.....tryed to call with MsVC and now 2 out 2....
Ordered to play media from helmet......worked..
This is only sitting in the livingroom with helmet on.....looks absolutely silly but thats besides the point
P$ssing with rain here so hoping for better weather to go for a roadtest...
So thing needed for me to get it to work...
-MsVC 1.6
-Bluetooth stereo cab
-Regedit from the MsVC topic..
-PocketzenPhone for designing profiles.....however thinking on removing that...and see how that works.....
D.
I am glad that you are at least part way there to solving the problem
I don't have Voice Command on my phone. On the rare occasion I use voice dialling I use the standard SDdialer program but my sound diversion does not revert back to the handset like yours.
I must have changed something on it to get it working but I am afraid I don't know what because, when I was trying to get it working, I tried absolutely everything and it was quite a while ago now so I have forgotten what I did
It sounds like Voice Command is going to be okay for you though so that is good.
By the way, Phonealarm is also another good profile switching program.
Thanks for the replies guys, but I think I may have accidentally discovered my own solution.
On my T-mobile vario II, if I go to the Phone->Settings and select the 'more' tab (need to scroll along the last tab at the bottom of the screen) there is an option to 'Automatic pickup' which will auto answer a call after x number of rings.
I had always assumed this would kick-in even if no headset was present. However, I've just done some simple testing, and it looks like the auto answer only kicks-in if the phone is currently in comms with a headset (I used a bluetooth one but probably the same for the supplied 'hands free' kit).
So this functions exactly as I want it to.
Oh, and Pdanny, for background info I'm using a Nolan 101 (no bluetooth) with speakers and mic installed. These connect to my 'Starcom' intercom (via an old fasioned curly lead) which allows me to hear directions from my 'TomTom' and also take phone calls via the starcom/phone bluetooth partnership. Down side is that the wife can also talk at me .
As I never want to initiate a call while riding, this setup works just perfect for me. I don't need to remember to change the phone setup either before or after mounting the bike. As soon as the bike ignition is turned on, the intercom partners with the phone. Then if I receive a call, it auto answers and I can take the call. Once the ignition is switched off, the phone reverts to normal non-auto answer.
In my research for this issue I came across an app called 'phonealarm' (from pocketmax.net), it was the manual for this that made me try the above experiment. This looks like a neat app and I may still end up installing it as long as it does not hog the processor.
[edit]OOps sorry Nicky, just noticed you already mentioned phonealarm. I'd be interested in any comments you have about this app, good ot bad [/edit]
Once again, thanks for the replies, and I hope this thread helps someone in the future.
Regards,
Glenn
Phonealarm......give that a try thanks.....
Im also going to test with the buils in auto pick up.....
I knew it was there but i assumed that it would ALWAYS auto pick up...
It seems that that is not the case therefore making the Pocketzenphone and possibly phonealarm obsolete.....
I also get all the sounds over BT in my helmet....incl TT
Also... I don't have a wife .......sounds like a perfect world hey???
Keep you posted on the outcome of the xperiment....
Grtz
Danny
Hi knnelg, glad you managed to sort your problem. I always knew the option for autoanswer was in the settings but like you, I had assumed that it would autoanswer all calls regardless of whether a headset was connected so it is handy to know that it only applies when in headset mode.
You asked about opinions on Phonealarm, I think it is a great program. I have used it on my Vario II and my last phone, an XDA Mini S, and it is has always worked fine, no problems at all.
I really missed having phone profiles when I switched to PDA style phones so Phonealarm was one of the first 3rd party apps I ever bought and I wouldn't be without it now Also, Bruce, the developer of phonealarm, is very good at listening to users input and if enough people make a suggestion about an improvement or tweak to the program, he will implement it in future versions which is really nice.
One of the other programs Pocketmax does, Alarmtoday, is useful too.
Hi,
I am currently looking for a piece of software that will do a specific job, or possibly a better solution to what I am trying to do. Let me give you a little bit of background...
I have got an O2 XDA Mini S, and a Parrot hands-free kit that does not support the A2DP bluetooth profile (only the handsfree profile). I am currently using TomTom 6 on my XDA with a bluetooth GPS unit. Everything works really nicely together, except I cannot get instructions from TomTom through my parrot (which is ultimately my goal).
The only way I can see of getting the TT instructions through my Parrot is to make use of the programs floating about that allow you to turn on and off redirection of sound through bluetooth. The idea I had was that if there was a program about (or maybe even write something myself) that would be able to signal when the sound coming out of the XDA exceeded and then dropped back below a threshold level, and then somehow link that into the bluetooth redirection programs, I could basically have any sound that is produced go through the Parrot only when they occur (including obviously the TT instructions).
Does anybody have any ideas on this? Any help would be greatly appreciated.
Thanks.
Point UI, a UI wrapper, has a feature similar to what you're describing. It's used just to save battery power by turning on BT only when an incoming call is detected, and then killing BT after the call is ended. I don't know if it's open source, but you might want to head over to their forums and see if you can find out how they did it.
You probably also want to haunt any TomTom forum sites (if any even exist).
As a final option, look into Mortscripts. People have done amazing tricks with Mortscripts, and this might be just the ticket. Mort haunts these boards, and may pipe in with an "I can (or cannot) do that with Mortscript" too...
I have a question, though. What's wrong with using the Wizard's built-in speakers for getting directions?
Myrddin Wyllt said:
I have a question, though. What's wrong with using the Wizard's built-in speakers for getting directions?
Click to expand...
Click to collapse
To be honest, it's not too bad through the speakers although if I have my radio on which I usually do, sometimes it can be a little bit hard to hear, and it would be nice to just have the radio mute while it gives me the directions.
It's more of a "want" than a "need" really.
Thanks very much for the info
Myrddin Wyllt said:
Point UI, a UI wrapper, has a feature similar to what you're describing. It's used just to save battery power by turning on BT only when an incoming call is detected, and then killing BT after the call is ended. I don't know if it's open source, but you might want to head over to their forums and see if you can find out how they did it.
Click to expand...
Click to collapse
It is quite easy for programs to detect when you're in a call - MortScript, I presume, probably can detect that quite easily as it's an overall Windows feature and will probably have a readily available part in the API.
The problem is not with turning the bluetooth on and off, it's actually detecting when TomTom is giving an instruction. To be honest I think I'll look into MortScript and if that can't do it then I'll probably just give up.
Detecting phone calls isn't that easy, and it's especially not easy to make a check in a simple procedural script language like MortScript (up to WM5, there's no way to check whether a call is active, you have to monitor all the time if a call is accepted or hung up).
Detecting sound output of another application is entirely impossible - at least for most applications. If the app opens the output channel only during output (which most don't because it takes valuable time and causes ugly "click" noises on some devices), one could maybe query the number of free output channels - but that would need a CPU hog monitoring all the time, or half of the message would be over until it's detected.
And even if that would work, there's simply no way to redirect output to a BT headset (except with A2DP). At least on most devices. Once there was a simple way to do that (you just had to open a virtual port, and as long as it's open, everything was redirected similar to the A2DP way nowadays), but most manufacturers didn't implement it, and nowadays it seems like no modern device supports it anymore. (Had it for test purposes in a MortPlayer beta, no user reported it works...)
So, to put it short: Currently it's impossble. Maybe WM8 might change that... (Few hope for WM7, it's proposed to have the same kernel as WM5 and WM6.x)
I'm a Desktop .Net developer with NO bluetooth experience and only a bit of low-level networking experience so I'm speaking from limited knowledge, but not complete ignorance.
I use my phone as an A2DP source and AVRCP client for quite a few devices (Jabra JX20 Pura, Jabra BT3030, Windows Vista, various BT speaker systems) and Alpine BT300) around my house, garage, car, and on the go. They all work wonderfully (some have better range than others, some better sound), but using any of them presents a couple common issues.
Some devices (like my car), constantly seek out the last paired device until they connect, while most of the other require a connection to be initiated from the phone. The phone doesn't care which is around or has the best signal, just which one successfully connects first.
I'd like an app that could have profiles setup which would let me control certain variables OR at a more basic function (see below):
Bluetooth Profile
Device Priority
Minimum Strength (to be used when more than one device has the same priority)
That would be my ultimate goal, but in the meantime I'd be happy with something as simple as a command line app that could be bound to a key or shortcut which would try to connect to a predefined list of BT MACs for a given profile and stop when the first one connects successfully. Variations on this might allow a connection attempt to a specific device instead of a list. This way I could have StartMenu or Today shortcuts.
The point here is largely to have to avoid nagivigating all the menus needed to initiate an A2DP connection, but I'm sure there are MANY other uses people would find.
If someone could point me in the right direction (I'm researching already of course) to the namespace(s) and or class(es) in .Net 2 or newer which would allow me to enumerate and/or initiate connections, this may be something I could bring to the community (assuming it doesn't already exist, and I have asked MANY times).
I've created a poll also to see what kind of interest is out there for this software and how much support I might receive.
I've been knocking an app up to suit my own personal A2DP needs... and a lot of yours by the look of things ;-) Things it does:
Kinetic scrolling finger friendly list of A2DP devices known to your phone (tap to select then tap again to attempt connection).
Toolbar buttons indicating active A2DP connection status (tap to disconnect active connection).
Bluetooth devices applet shortcut.
Switch bluetooth on (a good few of my devices need the phone to be discoverable so the app forces the phone to be discoverable at all times *blush*).
Switch bluetooth off.
Shortcut to program launcher list (automatically displays this list when you initiate a connection to a selected device... and there's items to display in the list of course).
Command line access (via secondary exe) allowing you to attempt connection (to a named , the last connected or first found device) and disconnect an active A2DP connection. I've only really tested the named device connection but the other 2 modes *should* work
QVGA / VGA and orientation aware.
I've been wanting to work towards getting it up on XDA... but time constraints (and a baby on the way ) have gotten in the way and it's unlikely I'll have the time to do it for a good while. I'd be happy to pass on the code to someone willing to take it further if that's any use. It's written (very quickly!) in VB.net BTW.
It uses a few bits and bobs from other people though:
A2DPToggle's "a2dp.exe" to handle initiating a connection.
Icons from lord only knows where I found them.
The kinetic list code found on here (http://forum.xda-developers.com/showthread.php?t=333124&highlight=klist). IIRC, I used the gingercat updated version and tweaked it to my own needs. There's many a kludge I've put in to the code to get things working quick-smart (D-Pad navigation mainly).
InTheHand 32feet.NET libraries (http://inthehand.com/content/32feet.aspx). These work with MS Bluetooth stack only.
So permission from the respective folks above would be needed before releasing it into the wild I guess.
Here's a screeny
Hey great tool! When I click a device will it auto connect or only open the BT Explorer and will it work with Broadcom BT Stack? Thanks
Oops, meant to say it's been developed for the MS bluetooth stack only. Sorry about that.
When you attempt to connect to a device it first checks the device is reachable and only then attempts to initiate an A2DP connection.
Northernmost said:
I've been knocking an app up to suit my own personal A2DP needs... and a lot of yours by the look of things ;-) Things it does:
Click to expand...
Click to collapse
Absolutely. I can get around in VB.Net and C# just fine. If you don't want to publish the code publicly, PM me your email address and I'll invite you to my Sharepoint site (easiest way I know to share files and manage communique), otherwise attach here.
It sounds like you've already covered 99% of what I was looking for, but I'd be more than happy to do what I can to more the idea forward, even taking suggestions from others in this thread.
About the BT stack, I'm running a Vogue with a ROM cooked in PPCKitchen, how do I determine which stack I'm running and can that be changed?
rainabba said:
About the BT stack, I'm running a Vogue with a ROM cooked in PPCKitchen, how do I determine which stack I'm running and can that be changed?
Click to expand...
Click to collapse
I've no idea what stack Vogues come with but the MS stack device list looks like the attachment below. If yours looks the same it's the MS one. I guess the Vogue forum should have any info on swapping stacks if it's possible.
Sounds like I found the correct people to answer my question about BT. Is there a way / how can I: enable my Mogul 6800 phone to transmit the sound that would normally go through the speaker to my BT headset in order to listen to streaming audio from the net using Kinoma Play which goes out and picks up all sorts of "radio programs" , i.e. not using a direct URL. I am also not able to listen to audio files from the Audio Recorder through anything except the speaker, even not through a head phone. Do I need to download a program or set up my phone differently. I currently have Titan WM6.1 Build 20755 GPS kitchen from PPC Geeks. Thanks so much for your help.
jminor4326 said:
Sounds like I found the correct people to answer my question about BT. Is there a way / how can I: enable my Mogul 6800 phone to transmit the sound that would normally go through the speaker to my BT headset in order to listen to streaming audio from the net using Kinoma Play which goes out and picks up all sorts of "radio programs" , i.e. not using a direct URL. I am also not able to listen to audio files from the Audio Recorder through anything except the speaker, even not through a head phone. Do I need to download a program or set up my phone differently. I currently have Titan WM6.1 Build 20755 GPS kitchen from PPC Geeks. Thanks so much for your help.
Click to expand...
Click to collapse
You need an A2DP capable device (high quality), connected, THEN start your audio program OR use a program called Audio Gateway with a basic Bluetooth headset (low quality audio).
thank you very much.
Northernmost, how about that source code? If you want to pass it along less privately than a post here, PM me and I'll provide a solution (source control, WSS, etc.)
Sent you a PM the other day. Let's go the private way for now.
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