Related
I am sending back my Jabra BT800 because it has a 9 second delay before it answers the phone! :evil:
I also can not get the caller ID to work. :evil:
I have the Asia WME2003 SE from here.
What BT head set, that has a caller ID screen that works with the XDAII, is best in your opinion?
Bump
Anyone?
Same is here
Akono series from Sony Ericsson do the trick. However they handle the id in erratic ways, sometime the number is shown, sometimes the name, sometimes nothing. Looks like they also behave different when the number is in the SIM card of the phone.
:?:
THANK YOU
Thank you, thank you, THANK YOU.
Are you sure???
Looking Glass:
Which Akono headset have you tried? The one available to me is the HBH-660, but before I plop down a lot of money, I wanted to be sure you got it working with the iMATE PPC (XDA II).
I had tried the Jabra BT800, and although it worked fine as a "basic" bluetooth headset, like everyone else, I could not get the caller ID function to work. I will admit that it had MUCH LESS static/crackle than my Jabra BT200.
So let me know which Akono you have tried, and confirm that you got it to work with the XDA II (not IIs, JAM, Mini, III, etc... just the "old" XDA II/iMATE Pocket PC).
Thanks!
-Kevin.
I will reconfirm in a few days.
I too experienced the same with the BT800. Great quality sound but the Caller ID will not work and it can take up to 9 seconds to answer a phone after I pushed the button.
I just bought the hbh-200 for $60 http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&category=20347&item=5756190707&rd=1
I will reconfirm this in a day or two.
They have a new HBH-662 that will have a power display and display how long the phone call was as well as caller ID like the HBH-660. Talk time is the same.
I went with the HBH-200 because I could just look at the part that is clipped to my shirt to see who is calling and leave the ear piece in. I am hoping I can make calls based upon the caller ID list as well. I am still worried I will break the wire though.
Dewild,
Please keep us updated on your results. If the model you have receives Caller ID on an XDA II/Imate PPC, I would assume the HBH-660 would work also.
Anxiously awaiting your test results...
Thx.
-Kevin.
Dewild1,
Forgot to ask in my previous post...
Are you currently running Pocket Bluetooth Tools, if so, what version 1100 or 1012?
Thanks.
-Kevin.
BT HS
I actually canceled that order... I did more research and it seems that 2.02 and 2.06, even Sin's version, does not support BT hands free.. Hands free mode is needed for the caller ID functions and other functions.
Yes, Sin's ROM does have a sort of hands free but in my opinion, there is NO BT head sets or any other device that is truly hands free that works with 2.02 or 2.06 or any mix or anything else.
Now the problem with that is,,, only the speaker works on the BT head set or any other device.. (I have only tested it on Jabra BT800 and ANYCOM HS-880, and I have read of others having the same experience)
NO Mic on the BT device. The Mic and phone on the XDAII are still going at the same time as well and if you keep your XDAII tucked away or in a pouch, you could here them but they can not hear you.. Or you could put the XDAII in front of you and talk into it and have your BT head set on.... Then you would be looking REAL COOL! :shock: :lol: 8)
Benefits of Sin's reg addition for Hands free are, the caller ID DOES work and when I push the button on the BT800, it answers almost instantly.. Not with the 9 sec delay while in HeadSet mode.
When you add the reg Key under, Hkey_localmachine, Software, Microsoft, Bluetooth and, (if your using Resco), highlight Bluetooth, Click on it and add just a plain Key of exactly "HandsfreeProfileOn", it is the same as adding Sin's hands free cab.
Now I would love to here from someone who has a BT SD card and see how it works.. I am tempted to buy a backpack to make this work and use a CF BT card if it works.. (There is no BT-Mem card combo,,, only WiFi-Mem combo cards that I know of)
I STRONGLY think this is a hardware driver issue!!!
Use 2.20.. IT WORKS
2.20 did the trick.. Seems ok..
No SD problems or other BS I read about
Hi Dewild1,
Excuse my ignorance, but I lost you on your last post regarding Sin's ROM, etc... what is SIN's rom? I did a global search and couldn't find anything on that. Am I missing something?
Thanks.
-Kevin.
Ignore previous post ... if you're referring to Sin's Wm2003SE merge. For my purposes, that's too much work and risk just to get caller ID on the headset. <sigh>.
-Kevin.
ROM
The only way to get caller ID to work and get Hands Free profile to work was to go to ROM version 2.20 of the translated to English from Chinese..
It seems stable, I have no SD card problems and the speed is good.
http://forum.xda-developers.com/viewtopic.php?t=13714&start=0
I used the extended ROM from the Dr.s
http://forum.xda-developers.com/viewtopic.php?t=16880&start=0
You can use http://spritesoftware.crmdesk.com/answer.aspx?id=63&back=browse.aspx#p17 to simplify the upgrade process. Make sure you have nothing paired in the BT manager first.
The God, mamaich, said that I should stay with 2.06 for it is more stable but I already updated to 2.20 and all is well... I hope it stays that way. :shock: :roll:
I just wish these DAM manufacturers and fricken resellers like HTC and O fricken 2 would support their dam products.. It should not be so [email protected]^@^ing difficult to get features that most FREE or almost free, cheap little phones have.. I mean we have the most complex, "advanced", powerful phone in the world right? But the free phones with BT that they give you with a one year contract, actually WORK, have BT voice dial, HAVE NO BUGS OR PROBLEMS! That is just not right. We pay a lot of money for a phone that needs to be hacked to make it work right...
It takes us, a combined group of people, to try and make the dam phones work right.. It is their job and they suck!
With that said, I would like to spend some time to say;
FU#* YOU O2, IPAC, and all the rest....
And a DOUBLE F#$K YOU TO HTC, Broadcom-Widcomm and Microsoft!!!!
I have spent a lot of time making things work right. If they would support their products, I could of spent my time on other things... They raped me!
Hu Guys,
I have an HTC TyTN and I cannot get the A2DP to work properly with with Jabra BT620s headset.
My ROM versions and other details are listed below in the sig.
If all others who are having problems with A2DP on their Hermes device please post below with their ROM details. I will then pass the info onto HTC when I speak with them.
Hey Syphon
I have been tracking this problem all over the intenret
Its the major deciding factor for me in purchasing this device
Its not just your device. Other people are reporting similar problems. Connection problems, bad quality, jumpy sound
I noticed in another forum you said you where in contact with HTC over this
If the HTC uses the BT A2DP stack from Microsoft then we are f#!ked then i dont think there is much HTC will do about it
Anyway Please be sure to keep us informed on how that goes
cam05 said:
Hey Syphon
I have been tracking this problem all over the intenret
Its the major deciding factor for me in purchasing this device
Its not just your device. Other people are reporting similar problems. Connection problems, bad quality, jumpy sound
I noticed in another forum you said you where in contact with HTC over this
If the HTC uses the BT A2DP stack from Microsoft then we are f#!ked then i dont think there is much HTC will do about it
Anyway Please be sure to keep us informed on how that goes
Click to expand...
Click to collapse
Well, this is my worry too. The WIDCOM (?) stack is supposedly MUCH better and MS have apparently really dropped the ball with theirs. The question is why would HTC switch? If you have a perfectly good stack already where is the need to switch? From what I understand the new MS one doesnt do anything that the WIDCOM one doesnt nor does it do anything better!!
do you know which implementation is in the Hermes?
cam05 said:
do you know which implementation is in the Hermes?
Click to expand...
Click to collapse
I thought it was the WIDCOM version, but it seems I may well be wrong.
I hope it is! Then atleast HTC might do something about it
If its the MS stack they'll just push it over to MS and say we have to wait for them like o2
Have you heard anything back from HTC Support yet?
not as yet.
confirmed the Hermes has the highly incapable Microsoft BT A2DP stack HTC you f'ing idiots
Complete f'ing idiots
I am going to put a jihad on HTC bunch of f'ing idiots
Why NOW? What possible reason would they have to revert to the MICROSOFT STACK ?
cam05 said:
confirmed the Hermes has the highly incapable Microsoft BT A2DP stack HTC you f'ing idiots
Complete f'ing idiots
I am to put a jihad on HTC bunch of f'ing idiots
Why NOW? What possible reason would they have to revert to the MICROSOFT STACK ?
Click to expand...
Click to collapse
How did you find this out? If it's true then I guess we are stuffed, unless MS and HTC sort their act out and fix this.
I reported this issue a week ago: please check my findings.
http://forum.xda-developers.com/viewtopic.php?t=57504&start=0&postdays=0&postorder=asc&highlight=
just read your thread. I see someone said their pantronics works fine...I also heard somewhere else that the tytn is kind of picky about what it works with. I may order up a plantronics to see if I can get it to work as mt bt620s is just not working at the moment.
i used to have an O2 XDA Atom before... A2DP sucked big time on it... crackling noise.. skipping... what not :lol:
now i'm using Dopod 838 Pro (HTC Hermes for south asia) and it works nicely for me... no skipping...(unless ur bt headset is low on battery) and no freaking crackling noise runs smooth. so far so good. i just pray that it doesnt go bad.
i'm using the i-Tech S38 Clip Stereo Headset (A2DP).
my rom, radio etc details found in my signature.
Is it me or does it seem the HERM100 models have newer ROMs on them?
Or are the variances due to the vendors applying their customisations etc?
I dont know but thats an interesting question!
I also encounter such problem. However, when I compare with my QTEK 9100 (AKU2.3 ROM), I found one of registry may cause the problem which shown as below:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Bluetooth/A2DP/Settings/UseJointStereo (Dword:1)
QTEK 9100 (AKU 2.3 ROM) don't have this registry but TyTH have. Now I know how to fix it:
Method 1:
Simple deleted it.
Method 2:
Change the Value to 0
Also you can add a new registry to improve the quality:
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings
Add : BitPool [Dword : 48] Maximum is 58
After the above mentioned change, bluetooth music work fine.
Hope it can help.
sas90850 said:
I also encounter such problem. However, when I compare with my QTEK 9100 (AKU2.3 ROM), I found one of registry may cause the problem which shown as below:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Bluetooth/A2DP/Settings/UseJointStereo (Dword:1)
QTEK 9100 (AKU 2.3 ROM) don't have this registry but TyTH have. Now I know how to fix it:
Method 1:
Simple deleted it.
Method 2:
Change the Value to 0
Also you can add a new registry to improve the quality:
HKLM\Software\Microsoft\Bluetooth\A2DP\Settings
Add : BitPool [Dword : 48] Maximum is 58
After the above mentioned change, bluetooth music work fine.
Hope it can help.
Click to expand...
Click to collapse
Interesting, I do not have my headset with me at the moment but after work and the gym I will give this a go. You are a good man for posting that info
I will let you know how I get on with it. Cheers dude.
@sas90850:
hmmm... the UseJointStereo value has been linked to monophonic vs. true stereo output to bt stereo headsets on some HTC devices. However, on others (like my 8125) this key is ignored.
Do you still get true stereo when this value is set to zero?
The BitPool value is absolutely one to play with when addressing this issue on the TyTn though. I was able to crank up my 8125 to the point where extreme breakup occured.
Sleuth255 said:
@sas90850:
hmmm... the UseJointStereo value has been linked to monophonic vs. true stereo output to bt stereo headsets on some HTC devices. However, on others (like my 8125) this key is ignored.
Do you still get true stereo when this value is set to zero?
The BitPool value is absolutely one to play with when addressing this issue on the TyTn though. I was able to crank up my 8125 to the point where extreme breakup occured.
Click to expand...
Click to collapse
Yes. True Stereo Output. The quality is same as QTEK 9100. Please note that TyTH also use AKU 2.3 ROM.
after a major set back with Hermes this morning.... used the A2DP for almost an hour plus this evening.
this morning, since last nite, my dopod 838 pro (hermes) starting behaving weirdly. freeze every now and then.. none of the plugins or other software, not able to install/function properly. and finally, this morning on the way to work, was listening mp3 on A2DP and while i was in transit from one train to another... hermes automatically went on a soft reset. once it came back to life, i found that i'm not able to access my mp3 library on the microSD using WMP10. was able to access the microSD thru the file explorer though.
no clue what so ever even to the dopod customer support and service personnel. all they did is do soft-reset, do u hav enuff free memory, do hard-reset (the usual stupid SOP).
i gave up on taking help from dopod people and tried investigating on my own.... found that the microSD's FAT is having some probz. some lost file chains. did a format.. and vola... WMP10 able to read the mp3 on the microSD like a charm!. and from the past 3 hours the device very much alive and kicking without weird behaviour.
no clue.. on why the microSD got screwed up like that. :lol:
oopz.. sorri.. my posting went off the topic... a bit.... hmm quite a lot actually :lol: :lol:
@sas90850
Ok we are getting somewhere...The "UseJointStereo" setting has partially fixed it. I have listened to a few songs without any major glitching. Just a skip or two, but nowhere near the scale I was seeing before. I am going to see how it goes. If there are any more problems I will try out the BitPool setting.
You sir are a good man! This has definitely made things a lot better.
So I've made the leap from WM to Android with my shiney new HTC desire.
I've managed to pair and connect it to my Nokia CK-7W bluetooth car kit but the recipient complains of a terrible echo their end of their own voice. At my end it's fine.
I've tried adjusting the volume in the car with no effect. I'm guessing that their voice that's coming through my speakers is getting fed back into the microphone, causing the echo.
Anyone experienced anything similar or even better know of a solution??
It's worth noting that this was never a problem with my HTC Touch Diamond.
Thanks
Rob.
Sorry for not answering your question, but how did you manage to connect the desire to CK-7W, I've been trying but no joy .
Again help would be appreciated
It took a bit of fiddling and to be honest I can't remember exactly how I did it.
I definitely set it to discoverable, but it wouldn't find it at first. I believe I had to turn on or off FTP server in advanced settings.
To connect once paired you need to turn on BT on your HTC and press and hold the connect button on the ck-7w for at least a second.
If you get it working please test for echoing and report back
Cheers.
Rob.
same setup here, same echo..
Hi,
I have the same car kit, I have the same complaints. Terrible echo. It worked just fine with my previous phones (Kaiser lately).
Cheers,
A.
When I get chance I'll trawl the other android phone threads to see if anyone has come up with a solution.
Cheers for the reply rob, I'll hopefully get it 'paired' tomorrow & feedback regarding echo.
Rich
Same issue here. I have upgraded from a HTC TYTN II WM6.1 to the HTC Desire. After connecting via bluetooth to the Nokia car kit all of my calls suffer from bad echo at the other end. To combat this i have turned the speaker volume down as low as i can hear it which seems to help the other party. (My bluetooth pairing setup perfectly the first time)
I also recall that my TYTN II had exactly the same issue and i had to download a patch from HTC which fixed the issue fully. Maybe the Desire needs a patch from HTC.
Has this issue been submitted to them for consideration?
This has been a bad problem since view first came out. It seems to be worse on the windows devices but it can and does affect even Nokia phones and still not an upgrade from Nokia.
I ended up having to get new parrots for our company cars as the drivers gradually upgraded their mobiles.
-------------------------------------
Sent from my HTC Desire
I found this thread over on the Xperia X1 forum with a solution they found to work
(See post #4)
http://forum.xda-developers.com/showthread.php?t=478612
I must admit I did this exact tweek a few years ago on my old M700 to get it to stream music via bluetooth to my a2dp enabled car stereo and it worked a treat.
Basically the M700 identified itself as a "smartphone" which the stereo didn't like. So I changed the "Class of Device" (COD) to identify itself as a normal mobile phone which instantly solved the problem.
I don't know if an Android has a registry or if it is editable but if it is identifying itself as a smartphone and it could be changed to a normal mobile phone then it just may get rid of the echo.
Perhaps there is another place on here that this question is better suited?
neomagik said:
I found this thread over on the Xperia X1 forum with a solution they found to work
(See post #4)
hxxp://forum.xda-developers.com/showthread.php?t=478612
Click to expand...
Click to collapse
For those guys changing the device class from smartphone to phone helped. I'm not familiar with Android internals but in /system/etc/bluez/main.conf there's a section:
# Default device class. Only the major and minor device class bits are
# considered.
# Local device class
# 0x400000 - Service class: Telephony
# 0x000200 - Major class: Phone
# 0x00000C - Minor class: Smart phone
Class = 0x40020C
Click to expand...
Click to collapse
Would that help to to change it? I haven't rooted my desire (yet?). Would someone having the same problem and having a rooted device try changing the device class?
Hey aszeman,
What application did you use view the contents of that file? I can browse to it but can't open it.
If rooting is what it takes to change the value, I'll give it a try.
neomagik said:
Hey aszeman,
What application did you use view the contents of that file? I can browse to it but can't open it.
If rooting is what it takes to change the value, I'll give it a try.
Click to expand...
Click to collapse
I did not check it on the phone as I could not read the file, but I used a downloadable stock rom.
I run the RUU updater, checked with "filemon" where it temporarily extract content. From rom.zip I extracted system.img. From that with unyaffs I extracted the system content. Browsed that around, and found the bluez setting there. I'm still hesitating about the rooting as there I see some issues floating around bricking USB/BT/FM. If someone has already done the rooting he/she could give it a try to change CoD.
You're obviously more 'in the know' than I am about these things.
Am I right in saying that if my phone was rooted I could view and alter these files directly on the phone?
I'm guessing that there are not that many people who own an HTC Desire, CK-7W car kit and who have rooted their phone. I hope I'm proved wrong but if no-one comes forward soon we'll have to take the plunge.
neomagik said:
You're obviously more 'in the know' than I am about these things.
Am I right in saying that if my phone was rooted I could view and alter these files directly on the phone?
I'm guessing that there are not that many people who own an HTC Desire, CK-7W car kit and who have rooted their phone. I hope I'm proved wrong but if no-one comes forward soon we'll have to take the plunge.
Click to expand...
Click to collapse
This is my first Android phone. Zero experience. I'm just guessing and making assumptions, and I'd assume with root rights one can change that file.
So I've now rooted my phone and changed the Class = 0x40020C to Class = 0x000200 and guess what.....no change.
I also got in touch with some people in the HTC Hero forum who have a CK-7W and they confirmed that they have no echo.
I then requested if someone could post the contents of their bluez folder which is different to ours. I copied the files onto my device, rebooted and still no difference.
Then, just for a test, I deleted everything from the folder and rebooted. Again no difference but to be honest I was surprised that it still worked at all.
It must be using information from elsewhere but I'm damned if I know!
I have the same problem with the Nokia CK-7W carkit and an HTC Desire smartphone.
I've had the problem before with my Xperia X1 (like someone said earlier) but then the problem was fixable within the registry of the phone.
My HTC Magic is paired without any echos or other problems, but still the HTC Desire has an terrible echo for the other party.
The answer of HTC was "buy a newer carkit", but that is insane, the basics are the same and it is depending on the phone so...
Hello,
I have the same setup and guess what...the same problem. I've updated the SW today but still no change.
Good news, the DeFrost Froyo rom has completely eliminated the echo, at least for me anyway.
The problem still exists... And i don't want to root my phone and flash a new ROM on to it.
Me also !
neomagik said:
So I've made the leap from WM to Android with my shiney new HTC desire.
I've managed to pair and connect it to my Nokia CK-7W bluetooth car kit but the recipient complains of a terrible echo their end of their own voice. At my end it's fine.
I've tried adjusting the volume in the car with no effect. I'm guessing that their voice that's coming through my speakers is getting fed back into the microphone, causing the echo.
Anyone experienced anything similar or even better know of a solution??
It's worth noting that this was never a problem with my HTC Touch Diamond.
Thanks
Rob.
Click to expand...
Click to collapse
Incredible .. Ive also made the leap from WM tot Desire and have the same problem with my Nokia Carkit. !!
Can't find the solution anywhere !!
greeds Rob
Hi All,
I guess most family readers have this issue.
Mum or Dad get a new phone, 5yr old child wants old phone. Not a problem except child wants the phone to charge up and switch on resulting in the phone possibly making emergency calls.
I have searched high and low for how to stop this happening. Is it possible? Does anyone know how?
I did think about ripping out the aerial. Would this work? For example on a Sony Ericsson Walkman W910, does anyone know how I could do this?
Cheers
I wouldn't recommend ripping out any hardware radios, as that can destroy the phone. I don't think there's a way to fully disable a phone's core functionality without any custom development. All phones when deactivated can at least make emergency calls.
I'm sure there might be some mod that's out there that permanently disables the radio, but I haven't heard of any. This is Android?
Like the subject says.. I don't get the point of
1. Creating a rom that's broken out of the box. Total waste of time to me.
2. Using a rom that is broken out of the box. Important functionality is not there.
I use BT all the time in my car and my service provider like many many others, use VOLTE.
So you are left with a useless phone with broken functionality.. For what? Play games with a few MB more?
Different people have different requirements. No carrier here supports VoLTE, nor do they plan to since LTE coverage is quite poor. While I do use BT personally, older cars/aftermarket headunits don't have hands-free, so BT becomes less important. And the thing you gain with a custom, is usually battery life or smoother/faster day to day experience. Sometimes even both.
What's the point? Literally everything else.
FYI... Most people and carriers on the world do not use/support VoLTE. Most people do not use BT, either. I do, personally, but that's besides the point. If I wouldn't be using my headphones, it would be off all day everyday.
Also, maybe bring this up within the ROM thread, and they might be able to help you with your issues. But although I am aware of some ROMs not working with VoLTE, I'm not aware of any where Bluetooth is an issue anymore, unless you're using a really outdated one.
I assume you're talking about Roms in the original section based on Lineage. I find it works better than Samsung's antiquated roms and the benefits far outweigh the sacrifices. Bluetooth works fine except for calls i.e. music, navigation all work via bluetooth. VoLTE is a pita and I wish you could set calls to 3g like you can on the iPhone. Sometimes I can get calls to go through if I do the calling but am unsuccessful when receiving calls.
Edit: You can disable Wi-Fi calling but I haven't tested this extensively enough to say if it 100% works. I don't care much for VoLTE and I don't see it as a big dealbreaker.
In my country it is illegal to drive with phone in hand and I am most definitely not wearing some ear piece or headphones. Hands free is the only way. In fact my car audio system supports BT and my stock phone/OS. I could not possibly lose BT for that reason alone, if not for streaming my music to my deck. That is a MAJOR feature requirement and a show stopper if it's not there.
I should say I don't blame the ROM makers, not their fault that Samsung hasn't opened RIL. My next phone will not be Samsung, Samsung was great when ROMs could be made to support all the features, now it's like Samsung is pointless. Definitely when I get my next phone I will scope out XDA and see what ROM's offer complete feature support.
Trust me, I went the route of posting to a ROM thread about the lacking feature support. I got torn a new one so I won't be doing that again. "How dare you complain about the ROM, he did it on his own time" blah blah..