Database Users

Modifying the flight mode facility

I currently use a QTEK s110 mainly for sat nav purposes. i dont use it as a phone at all. i am using tom tom5 with a globalsat bt-338 bluetooth reciever. with the bluetooth running it runs the pda battery down in about 2-3 hours if i forgot to lift the car charger from the other car. also it is a pin to start up as i have switch flight mode off and then wait fo rth phone to boot up before activating the tt software. so here are my questions.
is there anyway i can just get the tom tom to switch the flight mode off when i activate the tom tom software?
or is there anyway i can switch the pda off when not in flightmode rather than put it in standby as this just wastes the battery?
Can a shortcut button be created for the flight mode facility?
is there a fix for running the bluetooth with the flight mode on?
at present i have to switch off flight mode which becomes a pain when i have to switch it back on.
i have looked in to using the Globalsat sd-502 but it has compatibility issues.
i appreciate any help on this
Teb

"is there a fix for running the bluetooth with the flight mode on? "
tebs,
I know how you feel. This seems to be a problem with certain firmwares of the Qtec S110.
My manual states that holding down the power button turns the phone part off but not on my phone.
I'm currently testing Phone Alarm. It allows you to set up profiles. I've set one up which switches the radio (i.e. phone) off and bluetooth on. With it you don't have to go anywhere near flight mode. In fact, if you do, it'll get a bit confused. It's two presses on the today page to change modes. You can configure it to automatically put your phone pin in when switching the phone on. It's one press to toggle bluetooth on or off.
It takes some configuring but may do the job and its quite cheap (30 day trial)

Hi Borg,
i have also been using phone alarm for the last 3 weeks or so and its workin quite well. look as if i`ll have to purchase the software as my 30 day trial period is about to expire.

Yes, it's a pain that we have to buy software just to do what should be standard i.e. have bluetooth on without the phone on, but there you go. I contacted Qtek about this and they were pretty useless. Eventually I convinced them that it wasn't a faulty device but a faulty firmware and the only firmware that they offered me was the one I already had which is when I turned to PhoneAlarm.
Maybe one day HTC will put two physical switches on their devices to turn off phone and bluetooth - much better than software flight mode.
On a related note: I use sat nav whilst walking. I would like my bluetooth to actually turn off when I turn the device off so as to save PDA battery power. I'm sure the manual says it does turn off when you turn off the device but again it doesn't with my firmware - does yours?

borgs said:
Maybe one day HTC will put two physical switches on their devices to turn off phone and bluetooth - much better than software flight mode.
Click to expand...
Click to collapse
I've been saying that for ages! But honestly I dont even need physical buttons. If they would at least make the communications module togging (ie flight mode plus other radio functions) accessible from an on screen area bigger than a pinhead, that would be enough for a start. Its impossible to do it one handed. I'd love to know who the bonehead is at MS product development that okayed such awful ergonomics on a critical funciton...

Borg, my one is the same i cannot switch it off with the bluetooth running. need to switch it off first before switching the pda off otherwise the screen goes blank for a second then comes back up again!
skagen i totally agree with your comments.
its a pity the globalsat sd-502 doesnt work with it either that way you`d save loads of power not using the bluetooth at all. unfortunately once again the qtek has let us done on that one too as it doesnt detect the memory card!

Try
1. radiooff.exe
2. Turn on Blutooth
3. Tomtom -> GPS -> Configure -> Other NMEA GPS (4800,COM5 )

tebs said:
is there a fix for running the bluetooth with the flight mode on?
Click to expand...
Click to collapse
Try this:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\FlightMode]
"IsFMCheckEnable"=dword:00000000
"WarningMsg"="Please turn Flight Mode off first"
Change "IsFMCheckEnable"=dword:00000001 to "IsFMCheckEnable"=dword:00000000
Works for me...
Bye

it doesnt exist on my registry

Re:
Krisu said:
Try
1. radiooff.exe
2. Turn on Blutooth
3. Tomtom -> GPS -> Configure -> Other NMEA GPS (4800,COM5 )
Click to expand...
Click to collapse
radiooff.exe sounds interesting but I couldn't find it on my pocketPC. I looked in the windows directory and then I did a find. Is it a third party product?
Please ignore, I wasn't logged in when I read that message and so it didn't show me the download. Thanks

moghisi101 said:
tebs said:
is there a fix for running the bluetooth with the flight mode on?
Click to expand...
Click to collapse
Try this:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\FlightMode]
"IsFMCheckEnable"=dword:00000000
"WarningMsg"="Please turn Flight Mode off first"
Change "IsFMCheckEnable"=dword:00000001 to "IsFMCheckEnable"=dword:00000000
Works for me...
Bye
Click to expand...
Click to collapse
This also doesn't exist in my registry but the warningmsg part exists under OEM rather than HTC. But, if I add IsFMCheckEnable 0 it has no effect.
I think that this is probably a difference between the Qtek firmwares and the iMate firmwares. Qtek seem to have stuffed up in their current firmware.

Re:
Krisu said:
Try
1. radiooff.exe
2. Turn on Blutooth
3. Tomtom -> GPS -> Configure -> Other NMEA GPS (4800,COM5 )
Click to expand...
Click to collapse
Fantastic - thank you so much Krisu!
I have now uninstalled PhoneAlarm, done a soft reset and can now toggle the phone off and on using that app. If the bluetooth is currently running it leaves it running. No need to go near the flight mode button and should be able to assign it to one of the keys for fast turning off of the phone.
Thanks again!

borgs said:
moghisi101 said:
tebs said:
is there a fix for running the bluetooth with the flight mode on?
Click to expand...
Click to collapse
Try this:
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\FlightMode]
"IsFMCheckEnable"=dword:00000000
"WarningMsg"="Please turn Flight Mode off first"
Change "IsFMCheckEnable"=dword:00000001 to "IsFMCheckEnable"=dword:00000000
Works for me...
Bye
Click to expand...
Click to collapse
This also doesn't exist in my registry but the warningmsg part exists under OEM rather than HTC. But, if I add IsFMCheckEnable 0 it has no effect.
I think that this is probably a difference between the Qtek firmwares and the iMate firmwares. Qtek seem to have stuffed up in their current firmware.
Click to expand...
Click to collapse
LOL, yea I forgot to mention that my Qtek is running on an Imate ROM. That may be why...

moghisii101: No probs mate, I appreciate the info - if anything its shown me that the iMate rom flight mode is better implemented than the Qtek version.
tebs: check this thread out: http://forum.xda-developers.com/viewtopic.php?t=39281
You will find a bluetooth cycle program there (CicleBT). It seems to work ok with radiooff.exe but can get a bit confused if you download (from there) and use FlightMode. So I would suggest that you use radiooff.exe and CicleBT. I've assigned them to buttons. Phone Profiler also seems to have problems with our dodgy firmware. Again this is not the program's fault but what Qtek have done with their firmare.
And cheers for your thread as you've helped me solve my problems!

Check out SKScheMa at www.s-k-tools.com as it can turn WiFi BT and GSM on and off from a scripting language or from its scheduler.
Cheers cjb

I use the bluesoleil BT stack,and I can use tomtom with the phone off!

Bluetooth Manager.

There is this program here called Pocket Bluetooth:
http://www.bluetooth.jazztel.es/
Which is not working very well in my 9100, and actually stopped working entirely.
What it promises:
1. One click enabling and disabling bluetooth
2. Shutting down BT after 60secs of inactivity.
3. Setting the screen light permanently on i.e in the case of a GPS set.
...things very much needed.
Does anybody know of another program that does that?
Thanks

No one?

Cicle BT does one click enabling and disabling of BT
http://www.winmobileapps.com/Home.aspx
Its freeware too.
Works for me U can put it in the tray useing PHM traylaunch
Or map it to one of the hardware buttons 8)

meschle said:
Cicle BT does one click enabling and disabling of BT
http://www.winmobileapps.com/Home.aspx
Its freeware too.
Works for me U can put it in the tray useing PHM traylaunch
Or map it to one of the hardware buttons 8)
Click to expand...
Click to collapse
Thanks meschle,
It lacks though 2 main functions for me.
1. Disable BT after 60sec of inactivity and,
2. Screen light toggle, to permanent on, or normal when BT is active.
Regards

I contacted the developer of the Pocket Bluetooth Tools, but got no reply for a week now, nobody knows anything?

No one ?

Can bluetooth headset trigger auto answer?

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.

Sounds...

On WM5.0 there used to be a sound that would play when the bluetooth connected. Not on WM6.1. Is there a way of turning on the sound for bluetooth connections? I know there's a notification for connection established but that appears to be for like a wifi connection.
Also, WM5.0 used to have a click sound for opening the Start menu and/or doing menu picks, etc. How can one turn that on?
Finally are there any good "sound collections". Cutesy sounds then you connect to wifi or or new email or SMS message are nice but then you need to do a translation in your mind of "Oh that cutesy sound means I got an SMS". I'd rather just a sound that says "You received and SMS message" or "You missed a phone call" etc.

defaria said:
Also, WM5.0 used to have a click sound for opening the Start menu and/or doing menu picks, etc. How can one turn that on?
Click to expand...
Click to collapse
TF3D Settings tab | Sound | Advanced: Check off the Screen Taps option.
(or Start | Settings | Personal | Sounds)
defaria said:
On WM5.0 there used to be a sound that would play when the bluetooth connected. Not on WM6.1. Is there a way of turning on the sound for bluetooth connections?
Click to expand...
Click to collapse
I've noticed that too ... I thought it was a problem with my headset, and I just live with it. I guess I'm not alone.

GeckoDev said:
TF3D Settings tab | Sound | Advanced: Check off the Screen Taps option.
(or Start | Settings | Personal | Sounds)
Click to expand...
Click to collapse
I wasn't really looking for all taps, just menu taps. For example, I didn't want (or I wasn't used to) having a sound come out just because I checked off a task, but I did remember a sound happening when I tapped on "Start" or when I then tapped on "Programs". IOW a menu pick, not each and every time the stylus/finger hits the screen. Plus you can't seem to set or change this one (though I didn't look into the registry).
I've noticed that too ... I thought it was a problem with my headset, and I just live with it. I guess I'm not alone.
Click to expand...
Click to collapse
I have lots of times when the bluetooth doesn't connect or I'm not sure it's connected. I was used to that reassuring sound that yes I am indeed connected properly.
Speaking of which, it would be nice to have an application that really indicates bluetooth status. IOW what's connected to what.
I have a Sony-Ericson bluetooth headset. It's stereo and AD2P, etc. I can listen to music and answer phone calls. I use it all the time, except when I get into my car. There I have a Motorola Rokr which takes the bluetooth and rebroadcasts it to FM. So I sometimes "pass the torch" between the two. Sometimes the BT "Wireless" gets passed byt the BT "Handsfree" does not. Or at least that's my suspicion. I'd like a program which can verify this for me by showing me "Hey the BT Wireless is currently connected or paired up with the Rokr but the BT Handsfree is associated with the Sony-Ericson". Of course a little functionality in this tool to tell it "Hey move that BT Handsfree association -> Rokr" would be excellent!
Oh, and I'm curious. Who designed bluetooth and why is it that the functionality/connections are so bad and badly designed? I mean it seems to me that BT Handsfree control multiple things. For example, it seems to control ARVCP as well as "Push to talk" at the same time. I think such functionality should be controllable separately.

defaria said:
I wasn't really looking for all taps, just menu taps.
Click to expand...
Click to collapse
I don't know of any other settings for that. This is my 4th or 5th WM device, and up until now they all did what you are describing. Maybe this is something that was removed in WM6.
defaria said:
Oh, and I'm curious. Who designed bluetooth and why is it that the functionality/connections are so bad and badly designed?
Click to expand...
Click to collapse
If I remember right, it was originally developed by Ericsson, and then a consortium of companies banded together to create a standards group. The standards group has done well developing specifications for compliance to each version, but the problem is that multiple Bluetooth stacks have been developed by just about everyone that manufactures BT devices or supports them.
The result is a lot of different BT implementations that technically conform to the specs, but a vary greatly in practical usage. What a shame...

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