I have a recently purchased a Tmobile wing and wanted to be able to connect it to my stereo bluetooth A2DP device (Motorokr S9-HD). While the phone says it can support A2DP, I'm not able to connect. Some have said I should upgrade my bluetooth software on the windows mobile 6.0. Is there an individual program or ROM I can change to allow this to work and how can it be done?
what do you mean by can't?
you get an error?
Sorry, hit something wrong the last time. The mobile phone doesn't even recognize the headset. I spoke to a Tmobile representative who said the problem might be fixed by upgrading to Windows mobile 6.1, but that also could result in slowing down the phone. I just want the bluetooth to work enough so I can connect the 2 devices.
you have a pm
ares527 said:
Sorry, hit something wrong the last time. The mobile phone doesn't even recognize the headset. I spoke to a Tmobile representative who said the problem might be fixed by upgrading to Windows mobile 6.1, but that also could result in slowing down the phone. I just want the bluetooth to work enough so I can connect the 2 devices.
Click to expand...
Click to collapse
please read your pm i have sent you
bull**** about slowing down using WM6.1
go pick a good rom from the wing's section and flash it...
don't listen to representatives
Related
im facing problems when trying to connect to my home wifi router, the thing is tht my mda vario(unlocked and using it in Pakistan) just wont detect any wifi network. apart from the router ive tried it on my laptop and bro's jamin. im running nbd v7.4 with ipl/spl 2.6. is there any hardware failure in my device or is it because of some bug in the rom. pls advice guys, hoping to hear frm ya ppl soon. many thanks
irri said:
im facing problems when trying to connect to my home wifi router, the thing is tht my mda vario(unlocked and using it in Pakistan) just wont detect any wifi network. apart from the router ive tried it on my laptop and bro's jamin. im running nbd v7.4 with ipl/spl 2.6. is there any hardware failure in my device or is it because of some bug in the rom. pls advice guys, hoping to hear frm ya ppl soon. many thanks
Click to expand...
Click to collapse
What channels are your AP's using? ETSI compliant WiFi Radios support channels 1 thu 13, whereas American & Chinese ones only support channels 1 thru 11, Japan supports all channels 1 thru 14 and Israel only supports 3 thru 9.
List here on Cisco's website: http://www.cisco.com/en/US/docs/wir...os/configuration/guide/DosappB.html#wp1010830
I had this issue with a HP iPAQ I purchased that was originally from the Far East, my AP was configured for channel 12 and I could not see the SSID from the iPAQ.
HTH
Andy
it went straight over my head but atleast got some idea abt teh problem, im using channel 11, i'll see wht i can do. and pls tell me tht were u able to solve ur problem? is it possible to change this channel thingy. my bro's jamin's channel is 6, i guess if i somehow i change my channel to 6 the prob is solved. anyway dude, thanks
cant anyone of you listen to my problem ?? i asked in simple english that whether it is possible to change the valye of your channel in wifi settings through some registry settings? if not then wht am i supposed to do as my wifi channel is 11 while 6 works at my place...
any solutions guys??
Did it work with WM5 that came on the device? if not then its a hardware thing. You may want to have it checked out by HTC. maybe they can help you. But you will need to make sure you have the TMO 2.26 rom installed. Thats the only way they will support it.
Wohoo
irri said:
cant anyone of you listen to my problem ?? i asked in simple english that whether it is possible to change the valye of your channel in wifi settings through some registry settings?
Click to expand...
Click to collapse
Wow. Talk about an attitude problem. You will find that please and a little patience works better around here your majesty.
Have a weird problem and i think it can fixed by some registry.
the bluetooth will disconnect each time with my headsfree after hang up call. only either i press headsfree button to re-estabish or restart bluetooth to get it hook up again.
Does anyone has similar experience ?
Bluetooth disconnect
I've had this problem with my Sprint Touch Pro since I've had it...running stock ROM or Merdin's ROM. Very frustrating...using Motorola HF820 in the car and AT&T EP5632 (BT/Landline phone)...same thing.
I think there's a registry entry for bluetooth polling or something that can be set, but I've yet to find it. There was a post indicating that Diamond TF3D Config had a Bluetooth "tweak" that might solve the problem...but I get an error message when I run it.
JLPDA, Can you send me the tread that talk about this tweak, i wanna take a look see has anything we can do about.
Same problem: Touch Pro with Parrot MK6000 handsfree. I notice though that the phone reconnects after a minute or so. Previous Tytn did not have this problem.
Any news on this? I have the same problem with my Touch HD and Mk6000
Prehapes we have to generate alot of post to make people make attention to us .....
flippy_tv said:
Prehapes we have to generate alot of post to make people make attention to us .....
Click to expand...
Click to collapse
Maybe we should flood Parrot with requests for a fix... It should be easy for them.. my previous kit (MK3000) worked flawlessly...
just "copy and paste" from MK3000 parrot engineers!!!!
OTOH, my Jasjam (HTC Tytn) worked fine with my MK6000, while my current Touch Pro has this problem.
I was unable to find anything on the Parrot forums...
I wrote a message to the technical support page on Parrot's web site... let's see what happens...
Parrot's tech support told me that the HTC Touch HD is not currently suopported!!
superfuffo said:
Parrot's tech support told me that the HTC Touch HD is not currently suopported!!
Click to expand...
Click to collapse
Seems like nothing is supported on this POS. Out of six phones I have had the only ones that seemed to work with the MK6000 without problem was the Blackberry Storm which is the only good thing I have to say about that phone. It seems moronic that people should have to go through different phones to make their "Accessory" work. Parrot needs to get a clue. I know I'll be voting with my dollars elsware.
I can confirm, it will work as a stereo adaptor with the Touch Pro 2 but hangs up phone calls in the first second or two on the handsfree.
For Sale: One Parrot MK6000 stereo A2DP car kit, slightly used.
And I thought Bluetooth was supposed to be a standard...
I hate bluetooth!!!
What do you know... my parrot MK6000 now works just fine with my new HTC LEO...
Maybe it's because the LEO uses Broadcomm's bluetooth stack instead of the Microsoft's one... who knows...
JLPDA said:
I've had this problem with my Sprint Touch Pro since I've had it...running stock ROM or Merdin's ROM. Very frustrating...using Motorola HF820 in the car and AT&T EP5632 (BT/Landline phone)...same thing.
Click to expand...
Click to collapse
I also have the AT&T EP5632 and this happens. Does not happen on my Plantronics or Motorola earpieces though.
At one point, I thought I was having better luck with a DaG barebones rom. I like TF3D too much though...
Hello guys, let me start by saying im a total noob when it comes to the ppc
I recently purchased a HTC Magician to use as a work phone, i use a bluetooth headset a lot so it was a good option for a work phone. After i purchased it i decided to install the latest rom by Cotulla, rom HTCMAG_ROM_WWE_O4. It looks great, i like it alot, but the only problem i have is that i cant use my bluetooth headset reliably.
Its connected ok and does not drop out, but the problem is i cant hear people properly through the bluetooth headset, and im told they cant hear me either, its possible to hear that someone is speaking but not possible to understand what is being said.
After sifting through the threads here for days in the hope to find a solution, i could not find one and decided it might be wiser to just go back to wm 2003 se, which i hope has no problems with the bluetooth headset. Unfortunatly ive hit a brick wall with this option aswell, as it would seem all the threads ive looked at seem to point to links that are no longer available. So this leaves me with a phone that isnt able to be used for what i wanted it for
As i said at the start, i am a noob here so if im missing something here that i could do to solve this problem, could someone please point me in the right direction ?
Your headset is OK????
Hi!
I also use Cotullas latest ROM and i am also using my BT Headset without any problems and no "secret" settings.
Did you check your headset with a different phone? Maybe that´s the problem!
Cheers
Lui
Yea i used the bt hs on a dopod 838 pro, when i got the magician, i switched it from my dopod to the magician so i could use it for work. So i know the bt hs isnt causing the problem. And as ive seen some posts here about issues with bt and the Cotullas roms as being known problems, i naturally assume its the rom. But if its something else, then im all ears.
Just wont to get it working so i can use the phone with the bt hs.
As the imate site is down, and it sounds like imate might be going out of business due to some fraud problems. I cant seem to locate a rom with wm 2003 se, so i can try it to confirm if its the Cotulla rom, or something else.
Well im now trying t-mobile wm 2003 se, and so far the bt hs seems to be working great.
Hey Guys, i'm hoping you can help me.
I have searched this forum and couldnt find anyone that has the same bug as me. I apologize in advance if there is a thread already that discusses this.
I have a Ford Mondeo Titanium X 58plate. Bluetooth syncs up and sends/receives calls great, however When I try to hang up the call it crashes. Is anyone having the same problem?
I upgraded my o2 HTC phone to the latest 1.66 rom and I still get the same problem. Any help would be appreciated.
I too have the same issue. I have a Mondeo Zetec and suffer from the same issue. After hanging up, the phone continually tries to connect and disconnect and the only way to stop it is to turn off bluetooth completely. I logged the problem with HTC and they were trying working on the problem howver I havent heard anything from them for 3 weeks. Im considering changing the bluetooth stack on the phone but arent sure how and with which stack.
I heard that changing the stack to the Microsoft default causes other issues. Let me know if you get a response from HTC regarding a fix. I dont even bother connecting the phone to the car anymore because it just crashes everytime i get a call, its so frustrating.
This is the response I got from HTC:
We can never guarantee that our products will be compatible with car kits or bluetooth headsets.
There are different ROM versions of Windows Mobile 6.5.
It might be that this product is not 100% compatible with this specific car kit.
When it comes to upgrades and updates then you will have to contact O2 for them to provide the upgrades for you.
Best regards,
Jozefine M
HTC
Probably a generic answer to everyone.
Same issue/possible fix
I have a Titanium X sport exactly the same issue.
I was told a couple of days ago if you switch off Data connection in Wireless controls in Settings it helps and I have tested a few times and this does seem to work.
I have not had an opertunity to test thoroughly and would be interested to here if it helps you
I have a Verizon htc trophy. On monday I tried to activate bluetooth for the first time in a few weeks or so. I turn the status to on, it searches, doesn't find anything and then kicks back to status off. I've tried this with 4 or 5 different bluetooth devices.
I've scoured the internet and this forum with every search term I could think of with no luck or even mention of a similar problem.
Notes:
I updated to mango beta through the windows phone developer portal when it was made available. I'm pretty sure I was able to use bluetooth at some point with that os, but can't be sure. I updated to the newly available leaked 7720 last night hoping it would fix the bluetooth issue, but it still persists.
No other problems with the phone, and I haven't dropped it or anything. I do however use it to track my runs, and enough sweat has gotten into it to start to change the water damage stickers.
Wich devices did u want to connect?
This phone can´t connect with other phones, just with a few bluetooth-car-kits
and somethig like that!
I've now tried with a laptop, desktop, a cheapy noisehush bluetooth headset, a motorola s9-hd and also a motorola s10... Pretty sure all of which I have been able to connect with before (certain on the s9-hd and noisehush headset).
Any thoughts? This is a pretty limiting problem, especially since my state has banned the use of cellphones while driving.
I'm pretty close to opening the thing up and seeing if one of the Bluetooth antenna wires has popped off its connection maybe.
Anybody want to take a final stab at this question before I tear into my phone?
hi,
I have exact the same issue with my HD2. I have 7720 running. With 7392 it worked fine.
regards Coolity
It's possible there is an HTC driver needed to access the Bluetooth radio on the Trophy that is not on the Beta or RTM but would be on the final Mango roll-out ROM for this phone. All I can suggest is try to load the leaked VZW Trophy Mango ROM (but you can't unlock since it wipes the phone) or wait for VZW to roll out Mango for this phone.
Thanks for the responses. I have installed this version of Mango:
http://forum.xda-developers.com/showthread.php?t=1254384
which I'm pretty sure is as final as it gets. I did notice one thing, however. The firmware version seen here is 2305.13.20198.6 something, mine is 2305.13.20104.605.
Maybe this is the reason? All other revision numbers are the same, including the OS version in that picture.
This just in....
I also don't have regular fm radio. It's stuck loading (on 4 minutes now) with no moving forward.
Anybody else having these problems? Tried FM radio with the HTC shipped earbuds and it is still stuck on loading. The bluetooth is still experiencing the same problems.
I've tried to use the leaked htc verizon rom again but am not able to re-flash using the same steps as before.
I opened up the phone and looked around and it appeared that everything looked ok. no burn/oxidation marks anywhere.