OK, Here goes...as we all know, multiple bluetooth audio devices aren't automatically switching from one to another and devices are unchecked by default. This is completely opposite of how multiple bluetooth audio devices connected with the i730. After much exploring I've found the following in the registry:
The above path is for my WEP200...It's difficult to say if you'll see the same path of these settings since each device has a separate listing with all those #s. I have "enabled" each checkbox for handsfree by changing each devices' value from 0 to 1....but....THIS DOES NOT ENABLE AUTO SWITCHING....it goes right back to unchecking the boxes. I have also verified that the same registry values are in the i730 and are "enabled" (value 1) by default.......I'm no registry expert...this is just what I have found.
Hopefully some of you can use these values in Mort for a temporary fix...(I have no experience with Mort....yet)
What we really need is a permanent fix from Samsung!
I know I'm not adding anything new to this thread and for that I apologize to all of the folks that know what they're doing and are really trying to post some fixes or tips.
I did want to post so that if Samsung is monitoring (fat chance but it's worth a try). - I have been having so many accidental hang ups due to the button locations that I really need to be able to easily use a BT headset to avoid this. However, I also use the handsfree BT system in my car. Not having an easy way to have the phone re-connect is a very serious issue for me now.
Again, if anyone from Samsung IS monitoring here, this is enough to make me not purchase another Samsung phone if this is a purposeful direction the company is taking regarding functionality.
Again, sorry for the rant but I've about had it with the accidental hang ups. I know there is a thread for that but my main goal is to be able to use a BT headset and then switch over to my car without problems - like in the good ol days.The hangups are due to having to hold the phone awkwardly while trying to do other things (like write client's information for example). that's what one of the main draws of a handsfree system should be.
cheers!
Jay
__________________
If it ain't broke. . . break it!!
If I go to the following in my registry:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Bluetooth/Device/002c72cbbbd/Services/0000111e-0000-1000-8000-00805f9b34fb
Then I can set the "Enabled" property to "1" which checks my device.
I think the large numbers of the registry address will be different for everyone. So, we would need a script that each person could customize. Then, we could simply have the script change that registry entry to "1" and map it to a button or something.
If I go to the following in my registry:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Bluetooth/Device/002c72cbbbd/Services/0000111e-0000-1000-8000-00805f9b34fb
Then I can set the "Enabled" property to "1" which checks my device.
I think the large numbers of the registry address will be different for everyone. So, we would need a script that each person could customize. Then, we could simply have the script change that registry entry to "1" and map it to a button or something.
And that makes that device active? if so, we can make that a MortScript at least, which can be made to a one-button function with AEB. Hardly ideal, but an improvement.
To the previous poster, I think we have a 2- or 3-button approach now. Not perfect, but better than nothing.
Attached is a LINK file that works for me. Drop it anywhere in your menu and it'll take you directly to the Bluetooth Headset selection screen of the Control Panel.
To make it less buttons - or one-hand-able - consider replacing the left soft key with it or a menu system that points to it.
I use WisBar, so I use the left soft key as their "User Menu" then make that the top selection. This means I can hit left-soft-key, enter and I'm on the screen. Then it's either right-tap / connect or D-pad arrow / D-pad center hold / connect.
I also use AEButton, so I can assign a single button directly to it. If we get the registry thing going, it is possible to make a button (soft-key or whatever) do double-press for one headset and triple-press for another.
Yes, this checks the "Handsfree" box for my BT device. I've never used Mortscript. Can it write to the registry? Is there some documentation and examples on how to use it? If so, I'll take a stab at a script to do this.
Looking at the Mortscript examples, I think you would only need a script similar to the following, except where you put in the registry value for your specific BT device. I will try this during the weekend. If anyone else is brave enough, please give it a try. I wish I knew about Mortscript sooner. It's very powerful.
Next, in notepad, create a file with the above command and rename it to have a mscr extension. Open your registry editor and go to SOFTWARE\Microsoft\Bluetooth\Device, then change the numbers in the above command to match what's in your registry since your BT device will differ from mine.
Finally, run the script on your phone. This changes the registry value.
I also created a shortcut, placed the shortcut in the windows start menu, then assigned the shortcut to a button. Now I can hold down the OK button to turn on my headset. In theory you could map multiple buttons for different BT devices.
Glad to finally have a more reasonable solution to the problem. A total fix is best, but this is the next best thing.
Last edited by Evil_Attorney : 01-04-2008 at 04:48 PM.
So... pull the appropriate line from the registry and make a separate script for each and assign them to shortcuts or buttons. Not an all-bad approach!
I would love to add the ability to turn on and off the Bluetooth radio to the script. That way, you could press a button to turn on BT and handsfree would be checked. Anyone aware of a way to toggle BT by some command or registry change?
I got the i760 a couple months ago after having the Treo 700W for a couple years. I tried the 750wx but it was slower than the 700 so opted for the i760.
H500 bluetooth worked great with the Treo. I can't get it to set up with i760 though.
I power BT on so blue light stays on, hold it near pda and go thru steps. i760 eventually recognizes it but then it asks me to put in a phrase or password. Whatever I type in it doesn't work.
Can't figure out how to get past this part or reset phrase (if thats possible).
Looked thru Threads and can't find anyone with similar problem.
Checked Motorola and Samsung websites with no luck but do have question inot Motorolas site.
Wondering if I have to delete the H500 from the Treo.
Any help would be appreciated.
Thanks
Evil_Attorney: After lots of experience with HTC devices, I am still happiest with PhoneAlarm for a Today screen solution for turning BT on and off. I know, however, that certain of the rlToday screens incorporate that function, and many of the user/developers there are very familiar with MortScript. Check at that forum if you want to incorporate a BT switch into yours.
So, the best answer so far is a MortScript switch based upon the registry address of the respective BT device?
That is cool, but, ummm, sort of sucks in terms of difficulty.
SAMSUNG, where are you??!!
-Richard
__________________ I'm at Dr. Johnson's office for a dental appointment.
Next, in notepad, create a file with the above command and rename it to have a mscr extension. Open your registry editor and go to SOFTWARE\Microsoft\Bluetooth\Device, then change the numbers in the above command to match what's in your registry since your BT device will differ from mine.
Finally, run the script on your phone. This changes the registry value.
I also created a shortcut, placed the shortcut in the windows start menu, then assigned the shortcut to a button. Now I can hold down the OK button to turn on my headset. In theory you could map multiple buttons for different BT devices.
Glad to finally have a more reasonable solution to the problem. A total fix is best, but this is the next best thing.
Anway to make it so it turns on two bluetooth devices at once? I use a bluetooth car headunit that has handsfree/headset profile and A2DP and would love to turn both on with one push of a button.
I was thinking the same thing. If all of them are marked headset any device can connect. I assume when you connect the other devices will have headset disconnected but the one connected should work.
Quote:
Originally Posted by Indiglow99
Anway to make it so it turns on two bluetooth devices at once? I use a bluetooth car headunit that has handsfree/headset profile and A2DP and would love to turn both on with one push of a button.
Has anyone else tried the mortscript option? While it checks the hands free box for me, my BT device has trouble connecting if I simply change the registry entry. It's not clear if my BT device is picky (it's the speaker phone in my Prius) or if only a certain order of events works (e.g., check, then turn on BT, then turn on BT device).