I was wondering if the above combination works, I believe that the HBH-200 needs the handset profile that is missing from the XDA II.
Has anyone came up with a patch to support this functionality.
I appreciate anyone help in providing a solution for this.
Thank you. :wink:
I have the same combination, it works, but sometimes has the bonding problem just like the jabra headset. the solution is to disable bluetooth in the bluetooth option menu, then enable bt headset mode on your today screen and then click on and ok.
you won't be able to see the phone numbers.
I've tried several of the SE roms floating aroung the forums with my I-mate and finally setteled with the translated 2.20.07CHS one.
This rom obviously has Hands-free profile implemented to some degree, I bond my Bluetrek-G2 with the phone, and a long keypress on the G2 properly invokes the "Last call redial" feature of Hands-free.
My question is: to what extent is the hands-free profile implemented? Specifically I'm interested to know whether the "Caller ID" feature is implemented, so that headsets with built-in LCD displays for caller ID (e.g. Sony-Ericsson HBH-660 and the upcoming Jabra BT800) can be put to full use.
Any experience regarding this issue?
I saw some review/post from people with caller ID bt Headset
saying that is working fine , with the caller ID with the 2.20 CHS ROM
Were those posts on any of the XDA-DEVELOPRS forums?
NO, I saw them @ some chinese forum
which few model of caller ID Bt , working fine
"peoples say"
Here is my experience with an XDAII and a SE HBH-660
With ROM 2.02.t1, can setup the HBH-660 as a handsfree device, caller id works great, but the mic on the headset does not work at all!
With ROM 2.06, can only setup the HBH-660 as handset device, so clearly caller id does not work here, but at least the mic on the headset works!
Haven't tried 2.20, got tired of reflashing and hard-resetting my device after trying every steps suggested in the forum, even merging the 2.02.t1 and 2.06, which still has the same problem as the 2.02.t1 ...
Currently sticking to ROM 2.06 and using Pocket Bluetooth Tools 1.10. At least I can redial from the HBH-660, answer calls and transfer calls back and forth between the HBH-660 and the XDAII ...
skuld said:
Here is my experience with an XDAII and a SE HBH-660
With ROM 2.02.t1, can setup the HBH-660 as a handsfree device, caller id works great, but the mic on the headset does not work at all!
With ROM 2.06, can only setup the HBH-660 as handset device, so clearly caller id does not work here, but at least the mic on the headset works!
Haven't tried 2.20, got tired of reflashing and hard-resetting my device after trying every steps suggested in the forum, even merging the 2.02.t1 and 2.06, which still has the same problem as the 2.02.t1 ...
Currently sticking to ROM 2.06 and using Pocket Bluetooth Tools 1.10. At least I can redial from the HBH-660, answer calls and transfer calls back and forth between the HBH-660 and the XDAII ...
Click to expand...
Click to collapse
You may have a look at this thread to see how to turn on the Handsfree on ROM 2.06
http://forum.xda-developers.com/viewtopic.php?t=14386
Tried that as well ... got even worse results, sometimes the headset works and sometimes it doesn't ... have embarassed myself in front of people by wearing the headset on my left ear and still putting the phone to my right ear ...
skuld, I suggest you try 2.20.07CHS, it is the most stable 2003SE out there, and Bluetooth works great for me using the Handsfree profile (sound only comes out of the headset and the headsets' mic is operational).
I intend to purchase the Jabra BT-800 as soon as it is released and hope toi take advantage of full Handsfree functionality with it finally.
If you do decide to upgrade to 2.20.07CHS, please let me know if caller id works for you with your HBH-660.
so?
So, basicallly, the non-chinese speakers, are stuck with non fully working BT profiles, since handsfree option identifies every headset as hansdfree, and then the problem with the "stereo" effect appears.
In my case, both (device and XDA) mics and both speakers work simultaneously either in SE HBH 35 headset or BT Carkit.
Can please confirm 2.20 version solves that totally?
Any idea on why it has not been released in WWE?
2.20 indeed solves this problem, I'm currently running 2.20 for several days with no problems, the translation to English provided by Buzz is impressive and comprehansive. I don't speak a work of Chinese yet have no problems using my device, I have yet to come up with a Chinese message-box/notification of any kind. Bluetooth works flawlessly with my Bluetrek G2 using Hands-free profile.
Ummm..
Will give it a chance.
Keep me informed should you find any other problem using this version.
:wink:
yes so far so good
2.2 is a offical OS ROM for dopod 696 , which the same hardware as xda2
so it is working fine with the caller ID & bt sound
Anyone can provide me the complete REG file of 2.20CHS?
darren_the said:
yes so far so good
2.2 is a offical OS ROM for dopod 696 , which the same hardware as xda2
so it is working fine with the caller ID & bt sound
Click to expand...
Click to collapse
I converted the reg file from default.fdf of the ROM, but it seems to be incomplete when I compare it against 2.02 and 2.06.
I understand that Kinglee uploaded the PHM reg backup file. Can someone give me a hint how I might convert that file to a text readable format?
Re: so?
Looking Glass said:
Can please confirm 2.20 version solves that totally?
Any idea on why it has not been released in WWE?
Click to expand...
Click to collapse
I can confirm that 2.20 uses different bluetooth DLLs than 2.02 or 2.06.
After configuring BT headset, the user is prompted with BTBond_UI.exe screen with checkbox for headset/handsfree enabled, and greyed out checkbox for ActiveSync, Dial-up Networking and Serial.
There is quite a number of differents in the registry settings as well.
I think I just about manage to port 2.20 BT over to 2.06 (or 2.02 for that matter).
However, I need you guys to give me pointers on a couple of things:
(a) for handsfree profile - can 2.20CHS users enable the handsfree profile and use only the headset microphone to speak to the recipient?
(b) what about current 2.02 users?
(c) What can 2.20 CHS users do with their current BT settings? Please describe what you are allowed to do.
- No merry christmas present...hopefully, there's one for happy new year, aye? :wink: -
can someone post the file BTBond_UI.exe i need to try it on 2.02t version
BTHFP
Ok here's the skinny.
On 2.06 got BT HandsFree profile to pickup and end calls via headset with stereo audio but headset mic still off (Xda II mic on).
Anyone got the headset mic to work?
Need 2.20 registry to understand how BTBond_UI.exe and other *.dll works.
I posted blue tooth mic not responding to voice input topic a couple of days ago, from responses I got ... I decided to upgrade from 2.02 to 2.20 CHS, (it's a good upgrade it's got WMP 10 but no letter recogniser or transcriber input ??).... but alas G2 BT would still not respond to voice.
Then I had an idea..... I went back to the the 1.72 ROM (radio 1.17) and guess what ? The G2 blue trek headet now works Not really what you'd call progress....... but a fix !!
I would like to upgrade back to WM2003SE, but I have no idea what combination of ROM software will deliver the latest features of the upgrade plus the full functionality for the bluetooth device ??
So anybody out there know what combination works ??
BTHFP
MJW said:
Then I had an idea..... I went back to the the 1.72 ROM (radio 1.17) and guess what ? The G2 blue trek headet now works Not really what you'd call progress....... but a fix !!
Click to expand...
Click to collapse
Are you saying under 1.72 your G2 is able to enable HandsFree profile perfectly? What BT driver did you use Bro?
Steady...... I am just a beginner at this !!!
What I am saying is that with the 1.72.00 WWE ROM the G2 now works i.e I can hear through it and when I speak into it I can be heard. Pressing the button on the headset picks the call up and ends the call. What it doesn't do with this level of software is last number redial.
As for the BT software I have no idea what I am running ? Is there a way of finding out ? The 1.72 update was from the 02 site.
I have downloaded the 3500 BT patch and was wondering about upgrading back to 2.20.07 CHS + the patch and see if that works. Thoughts ? But I need the letter/Transcriber input and I am not sure where you get those and how to add them to the XDA2.
BTHFP
I am running both the WM2003SE MSBT and BC/WC 3500 BT on my Xda II.
Probably you are referring to the HeadSet profile Bro. We're discussing about the HandsFree profile - correct me if I am wrong.
I am going mad -
before upgrading to WM2003 SE - my bluetrek G2 worked fantastically.
NOW
it sets it up as handsfree device - I hear people through the headset but people only hear me through the mike on the XDA - the bluetrek microphone seems to be "disabled" in handsfree mode.
ANY ideas how to enable the microphone on the bluetek headset so it is in HEADSET mode and not through the microphone input on the XDA ?
I have been looking for an aswer to same problem. Hopefully we can find something together. :idea:
Problem solved
When I upgraded to 2003 SE I had three main problems and spent hours trying to solve them:
1) Bluetooth handsfree automatically kicked in - when I needed headset mode - rendered my bluetrek headset useless.
2) e-mail attachments - enormous problems downloading and sending attachments
3) alarm clock - not ringing
I have solved all 3 problems by reinstalling the 2003 se rom using the rom of 2.06 instead of the "merged" rom which was causing me the above three problems - when upgrading be careful and beware of country code errors - I am no expert but I used the rom upgrade of Hery and reupgraded and am happy with the result. Every time upgrading is a dangerous excersise and if you like me just want a machine that works and not really technically minded - beware of upgrading. I was able to but was nervous the whole way through. They say version 2.06 hangs but its been OK for me. I do not have wizcom on my machine but the only bluetooth I use is the headset and for GPS which work with the microsoft bluetooth protocol.
Good luck
Hi folks,
Greetings from Italy.
First of all congratulations for this web site and thanks to all people who share their info's with others.
Problem: I use a Qtek 2020 with his original latest ROM 1.75.04ITA, radio 1.14.00, with a Logitech BT headset . This configuration works fine, and I can make/receive phone calls without any problem. I also have installed TT5 with a BT GPS Leadtek device and it works fine, BUT I can't hear TT5 vocal instructions in my BT headset! The voice from TT5 is only available on Qtek speaker.
If I receive a phone call during TT5 usage, the phone call is correctly diversed on my BT headset, on TT5 screen appears an icon showing 'Vocal instructions suspended' (but the graphic instructions are ok) and at the end of phone call the vocal instructions start again.
Note that using wired headset all works perfectly.
How can I hear these vocal instructions into my BT headset?
I know using Nokia 7710 with identical configuration it works fine, why using Qtek isn't?
Pls help me! It's is very important, because I'm an ambluance driver, and this function should be VERY useful for us in our job.
I'm availabe to all modifications: i.e. change ROM, change BT stack (but I'm not able..need instructions..), change WinMobile version... whatever you want if it can be the solution!
The only thing I don't want is to buy another device or a BT adapter.
Thanks,
Valerio
Hello,
I have a Qtek 8500 with WM6.1 5.2.19202 loaded and I am loving it. I am using this phone for listening to music via A2DP and make calls.
Is there any easy methode to switch BT A2DP ON or OFF? Because I have to navigate/click alot before A2DP is active. A2DPtoggle for ppc is what I am looking for, but isn't working for smartphone.
anyone??
nobody has got a nice workaroud or other app? Perhaps with Mortscript?
I think that you can use btaudio for this:
http://www.davidmays.com/BTAudio/
Actually no, my BTAudio program does not do anything with A2DP.