Yes, I've done hard resets. It doesn't do anything except make me start all over.
BS on the 2 Samsung devices. Bluetooth is supposed to be a standard so you aren't tied to a company's proprietary devices. If they did not follow the standard that's their problem and they need to address it.
$.02
+1
I have done a hard reset also and it doesn't do anything.
I agree bluetooth 2.0 is a universal standard thats like saying have to buy only linksys 802.11g wifi equipment.
I have a Plantronics 520. It is supposed to connect with more than one device. If I have it connected to my Thinkpad I can't use it with the i760. As soon as I break the connection with my Thinkpad it works with the i760. I read where someone had it working with laptop and i760. Is this true or is my problem part of the Samsung problem.
I'm going to skip the complaining about this... since it ain't helping.
Seems I recall that MortScript was not WM6 ready last I looked... but it doesn't say that now. Could we use a MortScript to manually change between devices without having to drill down at least?
If that works, we can use whatever other app to launch them - AEButtonPlus / cLaunch / WisBar / PhoneAlarm / etc - including by time / function if necessary.
I've got a BT phone system at home, a Plantronics headset, and an S9 set - and even an old Moto BT speakerphone - that are all a pain to switch between now. I'd be pleased with a button to push right now.
Has anyone found a way to do this at least?
Edit: Here's a shortcut at least.
Make a text file with the following content:
23#ctlpnl cplmain.cpl,23,6?\Windows\cplmain.cpl,-23
then save that as something like "BT Headset.LNK" and you can launch that to get you to the tab that lets you select headset device in a couple taps or button pushes.
... and I tested it: couple of taps to switch between my S9 and my P320 for headset. Could be worse.
I still think MortScript is a better answer, but I don't know how to use it yet.
Oh... makes sense... I bet things like "COM Ports" don't appear unless enabled or whatever. Good to know.
I also poked around the registry a bit last night (okay... a lot... but I'm not that bright, so let's just pretend it was only a bit) and was able to manipulate which headset was "active" by manually changing ONEs to ZEROs and vice-versa; but it didn't work well enough that I expected to be able to make a MortScript out of it. Seems like a MortScript could be done, though, that would present choices and / or allow button-presses to make them work.
Thanks for the help. I made my test file with notebook and found a way to link it with AEB+ so that I have only 1 button to push to get to the headset devices page. This will help for the moment, hopefully a proper fix will be coming soon.
Just a thought, is there anyway someone could move the bluetooth stack from another Samsung unit to the i760? That might fix our problem.
This sounds like something right up SuperDave's alley, if he doesn't mind my throwing his name out there.
Haven't seen much of him in the i760 forums though, I wonder if he got his yet?
__________________
The more complex the mind, the greater the need for the simplicity of play.
Just a thought, is there anyway someone could move the bluetooth stack from another Samsung unit to the i760? That might fix our problem.
That might work. But from what I have seen some ports in the registry such as the aGPS on GPD0, changes back on soft reset.
Unless you hack the registry and dlls and overwrite them all... their could be a chance.
(Note: I tried moving the aGPS from GDP0 to GPD1 for google maps and hard setting it in the settings to see if the my location worked... still was able to see the agps device but of course no data)
__________________
Touch Pro 2 - Stock ROM - Verizon Wireless
Samsung is a dead end because like I said earlier in this thread, it is an issue with the immaturity of VoiceCommand as a Bluetooth Audio Gateway. Samsung isn't going to train their support people to publicly state that Microsoft screwed up VC 1.6 BTAG support.
Stack replacement is the ideal option. The problem is, the people here who would typically mess with replacing stacks are being swallowed by their day jobs.
Is there a way to easily merge a registry entry with the WM registry, like using a shortcut file? If we can do that, then we can simply turn on the headset option by modifying a registry entry. I can do this manually now with a registry editor.
Samsung is a dead end because like I said earlier in this thread, it is an issue with the immaturity of VoiceCommand as a Bluetooth Audio Gateway. Samsung isn't going to train their support people to publicly state that Microsoft screwed up VC 1.6 BTAG support.
So how do we go about deleting MS voice command? I don't use it all, so I wouldn't miss it.
It's not Voice Command's fault. You can switch out the dlls that get loaded by editing the registry and the phone will still uncheck the not active device.
Is there a way to easily merge a registry entry with the WM registry, like using a shortcut file? If we can do that, then we can simply turn on the headset option by modifying a registry entry. I can do this manually now with a registry editor.
E_A, can you explain your thinking a bit?
I might be able to get somebody at XDA-dev to write a script that could do that (if I understand what you mean).
While not ideal, I would guess that most users would be OK with tapping an icon to change devices.
-Richard
__________________ I'm at Dr. Johnson's office for a dental appointment.
Is there a way to easily merge a registry entry with the WM registry, like using a shortcut file? If we can do that, then we can simply turn on the headset option by modifying a registry entry. I can do this manually now with a registry editor.
If you can tell me what registry entries you're modifying to make it toggle between devices, I may be able to figure out how to make them do it with a MortScript.
I haven't put more energy to MortScript because I haven't found the entries to do the toggling.
If you can nail these down, we can have a single app pop up and ask which device (theoretically) OR just assign direct menu items or buttons to each BT device.
Login
Panel
