Related
Hi BA people,
I've spoken with my friend that has a Hymalaya (QTEK 2020) device, and he was joking me about all the trouble I have with the BA. It has a perfect bluetooth device that works with a lot of headset without noise, WM2005 already installed and working, very rare softresets, and spend less money than me. Amazing thing, I don't use wifi and so...
Franky, it seems to me that this device is a fake.
No people is working anymore on bluetooth that is dead by month and month, stopped at BT3900 and after 6 month I'm still unable to use my motorola HS801 headset that is lying in a corner with a lot of dust.
I was wrong when I buy this QTEK 9090, the older model was better. I think that I will not make the same error another time. Bye Bye HTC.
Sorry to hear that
I'm sorry to hear that you are not satisfied with BA. I'll admit that it has some bugs, but I'm happy since I use WiFi far more than Bluetooth. I almost bought a Treo 650 or Xda Mini, but WiFi was the deciding factor for me.
Hope they fix the Bluetooth problems with headsets though. I had a Nokia headset from my old phone and I couldn't use it with my IIs. At least sharing files through Bluetooth isn't a problem anymore.
contrary to the first poster..
i actually bought this phone knowing its problems...
Solving the problems one by one through the forums is one of the fun things that an xda2s / BA owner can do..
Everyday , I am discovering something new about the BA device.
I guess if I wanted a regular phone that already worked as it should...
I'd have sticked with my Nokia 6600.
Now I have a BA device which has inherrent problems, which forces me to read up the forums here and get really technical about the phone..
This actually made me love the phone more...
Hey guys,
It's so strange...
I know a lot of people aren't satisfied with the Phone or BT on a BA.
I have an SX-66, two weeks now, and it's working so well.
I can pair up with my BT GPS device 100% of the time, with NO problems at all. No need to repair when I turn off unit, etc. etc.
I used to have lots of problems with my HP.
The SX-66 is great.
Also, in terms of a phone, I am also truly happy with it.
I am in my basement and get 40% or 20% signal strength, and I can actually talk on it.
With my old cell phones T-616, Motorolla 720,... no way they would work in the basement.
Very strange how people have so many problems...
This device is 100% great in my books.. (and I am very very fussy!)
Also, since I installed MS Voice Command 1.5... WOW... it is easier to use than any Cell phone i had in my life!
M
I agree with the first poster - I too have a Motorola HS801 which I can't get working properly on my O2 XDA IIs. Highly annoying, but I don't want to risk buying another BT headset in case it doesn't work either!
I have had mine for almost a year now and I have had great success with it! It does have it's issues,but at least we are able to "fix" them ourselves. I use both the b/t and the wifi on a daily basis without any real problems.Btw,I use a motorola hs820 and it works very well for me.I have very few if any resets with the new radio.If I have any complaints about it,it would be with the Truefax.
simopimo said:
I agree with the first poster - I too have a Motorola HS801 which I can't get working properly on my O2 XDA IIs. Highly annoying, but I don't want to risk buying another BT headset in case it doesn't work either!
Click to expand...
Click to collapse
I have been using a Sony Ericsson Akono 660 Bluetooth with the pda2k BT3900 radio 1.12 and firmware of 1.40 for the last 2 months and I have paired it once. It works really well. I have a coverage of about 10 feet from the pda2k in line of sight and about 4 to 5 feet if the pda2k is in the car and I am outside etc.
For those of you who are not aware of which BT headset to use. I had compiled a thread on www.clubimate.com sometime back which lists those headset (reported by users) which seemed to work and do the basics, ring when call comes in, answer or hang up the call etc.
I would suggest they you review this list before making a decision on buying any BT headset. I also believe that iMate has released a list of officially tested BT headsets known to work with pda2k etc.
good luck
I was considering the Jabra BT800 because their web site states that it's supported with the XDA IIs, but after seeing some comments from others in these forums, it's so hard to work out what to go for.
therock112, I'm sure we're all looking forward to seeing that list!
I have tried the various ROMs with my PDA2K and the BT headset (tried HS810 and 820) are so inconsistent. The BT headset is a great idea but poor with this PPC. I wonder if the Samsung i730 is my next hope.
also disapointed
yes guys to my regert i have to admit that the ba is quite a failer in all the meaning
whaen you pay for device around 700 us$ u expect a little more then we get
the bt the wifi and the problem that seem far far away to be solve so what the solution is just to show our finger up againt ba product what ever
the name is and if the manfacture and microsoft will not improve we shuld decide and if somebody want to have fun by solving problem each day he can use a simple math book!!!!!!
Hi albnigxda!!!!
Do not get nervous....I hv used PPCs since 1997, all that HP and compaq stuff,XDAI/II/IIi/mini/HP6365/ and now BA(PDA2K)
and I can assure that BA is the best....
I use SE HBH 65....no problems
Couple of times use Wi Fi at some malls and cafe shops...Just wonderful with battery and speed.
My BA has become more stable after installing latest O2 ROM and choosing the particular band frequency(1800 MHz in my case) and no bad signal problems...
Use lot lot of applications with 512 MB SD card....
With all the above and 120 calls per day on avrg with 1 hr of GPRS usage My battery lasts for 26-30 hrs(Of course, during day time I keep OFF the backlight, as I use MS voice command and it tells who is calling)
So keep.up and go ahead...u hv the Best Handset of the World....
I can tell u as I hv also used Sony Ericson p8xx/9xx Almost all Nokia symbian phones to the latest 6681.....and I can tell u none can match the preformance of BA...
I hope, this will encourage you.
Good Luck
Have pda 2k latest rom off imate site have gotten 40 feet line of site , out of site is not so good. us a jabra bt800 am on it all day i have more problems with blue tooth on my laptop then my phone have had 3 other ppcs before this one its the best by far.
Hi Guys,
Recent got an XDA IIi after being with the older XDA II for over 16 Months.
But I have recently run into problems with my BT Car kit :
Motorola Bluetooth Car Kit HFW-8000.
Basically the problem is that it does not always connect to the Car Kit and when it does it will only from time to time connect and let me have a handfree conversation.
I have also used the Broadcom Bluetooth Cab file here in order to extend what Bluetooth Profiles that can be used but seems not to have any great bearing to stablize the issue.
So I went down the Hard Reset Road but again still intermittent issues, I then upgraded the ROM to the New one on the O2 Website the v 1.11.169 ROM.
I also had similar issues with the XDA II but it was resolved by using the Pocket Bluetooth tools, which was great and never once after installing it did I have any issues with the Car Kit.
http://www.bluetooth.jazztel.es/
One of my questions is, is there a similar programme to to above Pocket Bluetooth tools for the XDA IIi as I have tried it with the XDA IIi but does not work.
Or does anyone know how you would revert to have the XDA II radio or is there a work around for it.
Thanks Guys
Woody
Hi Woody_XDA,
I have had my XDA2i for a couple of months now and recently got a O2 blue headset for it, I had simular problems with the headset disconnecting and having to manually connect every time I switched it on. After browsing this wonderfull forum I decided to do a corperate install and get rid of the O2 active interface, since then no problems at all. I now use Pugs modified ROM version 162 with radio 1.04 and have no stability problems at all with no twice weekly reset. Hope this helps you and many thanks to Pug for his ROM.
Mace
Ditto, I also use the custom firmware with 1.04 radio and bluetooth works a charm. It still eats battery like nothing else, but it works with no problems. Also like the fact that the XDA can cope with my GPS receiver and my handsfree kit simultaneously, that's handy for in the car.
Cheers Guys for the information, took it on board and works great, did a great deal of stress testing in order to confirm it and works excellent..Thanks to PUG again and guys thanks for the info much appreciated and this is by far a great forum
Mace - you mention some bluetooth issues being resolved since you applied the custom ROM... I posted in the Alpine Applications forum here the other day a list of issues with bluetooth that I was wondering had been addressed - so far no reply - are these the symptoms that were cured for you??
Hi Bewlay Brother sorry, I missed your other post on Bluetooth issues, my original problem was that every time I switched on my BT headset , which is a O2 Blue, I had to open the BT manager and make the connection, the phone would then occasionally lose the connection and sometimes whilst still showing a connection refuse to transfer the call. This was using the official 162 ROM with the O2 active UI. I have since installed Pugs 162 ROM with radio1.04 and done a corporate install and BT seems to work perfectly, switch on the headset, it connects, never loses pairing and transfers calls.
Hope this helps you, and thanks again to Pug,
Mace.
Mace - what you describe sounds similar - my problems were essentially the loss of pairing with my Motorola headset a lot of the times when the XDAIIi switched off its display and went into stand-by mode, also if I closed the boom bike on the headset (to temporarily turn off the headset) it would fail to re-pair when I next opened the boom mike... the other issue was that I had to make sure the phone keyboard was displayed on the XDA once I had paired up otherwise the last number redial function on the headset would not work - if I pressed the dial button on headset and the phone display was not on the screen it would simply open the phone display function but fail to then dial the number - really crap. Also reception was poor to headset even over relatively short distances from the XDA. IF these areas in particular could be cured by the upgrade then I am eager to do it - I must admit I have read that this upgrade has not been without problems for some people here so it is going to be a tough call.
Just a thought, but have you done a personal or corporate install as I think the main fix with Pugs ROM was the upgrade to radio 1.04, which I don’t think affects the BT, so a corporate install with your existing ROM may make a difference.
Did a corporate install when it was new out of the box...
whats the difference between the corporate and personal install?
Corporate doesn't install ANY of the branded O2 interface - so no gubbins, nothing to slow down the phone, you just get a bog standard Windows Mobile 2003 SE installation, aside from the O2 GPRS and SMS settings. Bosh.
hi
i've been reading the posts and i have the same problem where can i get hold of pug's ROM if it's possible cos this seems to get rid of the problem
And then today, headset will not automatically connect, needing Bluetooth manager to be opened to make the connection. AARRRGH!
BT car kit problems
I have the 1.04 Radio, but it still won't sync with my 2003 BMW 325xi bluetooh or with my 2005 Acura MDX bluetooth.
Help!
Unstable Bluetooth Signal Strength - Samsung WEP200 Bluetooth Headset
Hi, I just got a Samsung WEP200 Bluetooth Headset. It would pair with my O2 XDAIIi but I cannot hear any voice in both incoming and outgoing calls. When I check the BT Manager, it shows a totally unstable BT strength that varies from very strong to very weak. The same headset worked well with other BT phones. My ROM version is 1.11.00 WWE, Radio version 1.04.00.
Any help would be greatly appreciated.
I've recently purchased a BT-359 bluetooth GPS receiver. It looks sweet -- and it'll look even sweeter once its little blue light is blinking quickly indicating that its paired with my Treo 750.
I strongly believe the issue lies with the MS bluetooth stack, and I very much want to upgrade to the Broadcom / Widcomm stack. There are very active boards in all the other phone forums talking about porting a version of this vastly superior stack to their hardware platforms -- I'd like to make this the call for someone to do the same for the Treo 750. Better yet, I'd like to add this thread as a call to Broadcom to charge each of us $20 for something that should have been included in our phones in the first place - I'll hapily pay it.
If anyone has any ideas for getting the Braodcom / Widcomm stack working on a Treo 750 then please post it here. My entire day of internet searching has me confident that there are many Treo 750 users who will appreciate it.
I'll post my sob story below - happy hacking.
As I mentioned above (in the opening post of ths thread) I've got a vested interest in finding a way to get the Broadcom / Widcomm stack onto my Treo 750.
Alright, I've now submitted a support ticket to GlobalSat (they only do "selective" telephone support). I've also tried several other work arounds that have necessitated several hard resets of my device. I'll list a few of the solutions I've tried below, so that other frustrated users can hopefully save themselves a few steps (and headaches). Before I start this, i've got to give a plug for Sprite Backup which has made the process of trail and error bearable. I've got several work apps installed (most painfaully mNotes) which are a chore to re-configure. I'm glad that Sprite was around to restore my handheld after each of these solution attempts. Things I tried:
1. From Aximsite, I installed the Broadcom Bluetooth StackX51V05.cab -- I tried this file first because it had worked for several Dell Axim users trying to pair the same BT-359. It was also attractive to me because it provided me a path out of the MS bluetooth stack and into the Broadcom / Widcomm bluetooth stack, while also offering an uninstall option. The program installed easily, I made a couple registry tweaks suggested at Axim site, and I performed a soft reset. When the phone re-booted, i received a error informing me that I didn't have enough driver memory to load the Bluetooth Radio. I downloaded a task manager and turned off everything I could, all to no avail. Finally, I had a hunch that perhaps the Axim bluetooth was operating on a different hardware COM port, so I tried setting the registry settings for the new Broadcom driver to 0 through 9 (rebooting after each setting change) to see if that would work. In the end, nothing worked. I did get access to the broadcom interface and I can definitively say that there are far more options available in that driver than in the MS driver. I can also say that, from what I read, consensus is that the braodcom driver is far superior to the MS driver.
2. Next, from this site (XDA developers), I tried the BBS_HERMES_03.zip, and the Helmi_Hima_BroadComm_1.7.6.0500.ZIP both of which have been developped by Hemli_c who is aparently the god of this stuff. Both yielded control panels that looked similar to the Axim site solution, however neither of them worked - they both gave the same memory error. I played around with many more registry settings here trying to get them to work, again, without any luck. These were the most detailed instructions I found - I'm happy to give tips to anyone trying to better my results. http://forum.xda-developers.com/showthread.php?t=285696
3. Next, I became very interested about the WM6 "cooked roms" which are available on XDA. Now this is where I really wish the Treo folks were more geeky (or I had the time to figure it out myself). The other hardware platforms all have SEVERAL WM6 implimentations cooked up, each touting the best mix of CAB add-ons (including the broadcom bluetooth driver). I downloaded Helmi_c's, but it wouldn't work on my Treo (I did learn that to get into bootloader mode on the 750, you need to hold the side button while you press the reset button inside the SD card door). This was a bit of a nerve racking procedure, as I was convinced Sprite couldn't bail me out of that mess -- i was half thankful when the ROM refused to load (although I am excited to get WM6 loaded on my phone).
4. Finally, I sent another support request to GlobalSat in hopes that I'd get a response. I'm very excited to get this toy working, and this messing around is finally starting to get past the fun stage, to the genuinely annoying stage. I'm actually starting to think that I might not be able to get it to work (at first I just thought it'd be a challenge that would be kind of fun).
If anyone has any questions, or suggestions, I'd be glad to hear them.
I'll post again as I find out more.
I don't know that I can help any technically, but you have my moral support. The MS bluetooth stack is horrible and a constant source of headaches for me. Thanks for all of the effort and thanks for posting all of your information. Even if, in the end, you don't manage to slay the beast you have at least earned yourself a happy face sticker from me ;-)
I use the widcomm stack on my axim X51v and it is indeed superior to the ms stack.
It would be great to use it on my treo.
It is so much better and with a lot more options.
My skills about these things are close to zero, but you do have my moral support too.
First of all, an update on USGlobalSat... they aren't winning any points so far. In response to my query about their GPS receiver not pairing with my Treo 750 I got the following response:
Thank you for contacting USGlobalsat's online care. In reply, we recommend a 72 hour battery removal allowing the device to reset. In many cases, this action corrects many performance abnormalities. If problems continue, then proceed by contacting the original reseller requesting a product replacement.
Now onto some more positive news. I had some temporary success with one of Helmi's Bluetooth stacks for the Universal. The specific file I loaded was either UNIBR176.0500.zip or UNSIGN_UNI1.7.6.0500.zip.. I'm not sure which (I'll post again with the exact process).
The process and files worked perfectly for about 18 glorious hours. My GPS paired, my stereo headset paired, and everything seemed to be working perfectly. The next morning, everything was still working perfectly. When I went to leave work (and use my GPS to find a restaurant), I couldn't power on the bluetooth radio. Whenever I clicked on the bluetooth button, I once again got the "insufficient driver memory to start bluetooth radio" error. I hadn't added or modified anything since the night before (I was afraid to mess anything up).
I have just returned from dinner and am in the process of restoring a Sprite backup (which I love) and will try to recreate my success. I'll report back tonight, and again in 24hrs -- hopefully this time the solution is longer lasting.
I have been trying to get this to work on my trinity--any tips would be welcome.
Frustratingly, I'm back to getting the memory error below. Even if I hard reset, and JUST load up the bluetooth driver (none of my other apps) it no longer works. It must have been a complete fluke that it worked for those 18hrs. I'm going to try again tonight - recording my steps exactly - in hopes that it either works, or that someone can pinpoint my error.
I am fairly sure that the fact that this installation was designed for another device isn't helping me get this working - hopefully I'll stumble across the solution.
I got the hermes version installed ok but it would never pair or detect a bluetooth device. you can get around the memory error by cleaning out your today plugins and getting SK tools. Use the SK tools to stop cprog.exe, then compact heaps and free memory.
ok, I've made some progress and will try and summarize here (sorry for the slow reply). These things are listed in this order for a reason, if I don't do them in order, then the driver won't load:
Hard Reset Palm
Install mNotes (to device)
Install Google Maps (to storage card)
Install Sprite Backup (greatest program ever) (to storage card)
Install Braodcom Bluetooth Stack (see procedure and file location above) (to device)
If I install Google after I install the bluetooth stack, I get the out of memory error (and I couldn't correct it using SDK tools). Also, this setup is kind of finicky about soft resets, occasionally the bluetooth driver won't load, but this is resolved by simply resetting the device.
Things that don't work (that did work under old stack):
Bluetooth Activesync
Voice calls through my sony stereo bluetooth headset
Things that now work that didn't work before
My bluetooth GPS receiver now works
Stereo quality from MP3s is vastly improved (noticeably)
Hopefully someone will come up with a Broadcom stack designed specifically for the Treo 750 - I'd pay for it.
If ayone else has any tips, please post here.
Thanks,
Gavin
I've yet to get the stack to work at all. I have hard reset, installed the stack, used sktools, but no luck. Did you do any other tweaking?
Bump...hoping to hear back on this. I've tried repeatedly and get the same results. I also noticed that it knocks out my microphone on the phone so I cant even make calls when I install the widcomm stack. I swear I am going to chuck this 750 and get an 8525.
Same result as gmctavish
Stack worked great until suddenly radio could not load. I tried installing in safe mode but I get the same results. Maybe if you use a 3rd party task manager and stop the BT service and then install this it will work? I'm going to try.
Very intermittent but when it works it works good.
I had success adding some functionality by using http://www.jetwaremobile.com/
I used it to allow phonebook and call log transfer to another application...Streetdeck (streetdeck.com).
I now can use my car pc to dial/receive calls.
sorry this response took a while. I did not do any tweaking beyond what I described above. Sorry I can't be of more assistance.
I've been working with the Broadcom stack installed for almost two months now - I have several ups and downs I can report.
The Good
The driver itself loads after 90% of hard resets (when it doesn't load, another hard reset gets it to load -- this is strange)
My Bluetooth GPS receiver works (the original reason for me trying to use the stack
My stereo headset works for listening to music and TV shows
I've got a bunch of software installed and I'm not getting out of memory errors (mNotes, google maps, tom tom, bee line, TCPMP, Sprite Backup, PDAnet)
Association/Discovery is UBER painless, I turn on the headset or the GPS receiver and they pair with the phone without any fuss.
No dropped connections
The Bad
Listening to the bluetooth headset with the bluetooth GPS receiver connected and feeding data to either tom tom or google maps is unbearable - 50% of the music is dropped
Activesync over bluetooth doesn't work
I haven't been able to get the phone paired with my computer to use the phone as a bluetooth modem (using junefabrics PDAnet)
My stereo bluetooth headset works fine for audio (some skipping and not great sound, but it works)... however it no longer works for making calls - as soon as I try and make a call it is dumbed to the handheld.
I've been having some issues with my Tilt and my car's hands free setup (see: http://forums.wireless.att.com/cng/board/message?board.id=cingular&message.id=105410). The problems seems to lie with the Microsoft bluetooth stack on WM 6.1. HTC is no help with this issue so I want to take matters into my own hands. Is there a way to replace the default Microsoft bluetooth stack with another, more reliable compatible stack from a reliable company (not Microsoft or HTC)? I don't want to get rid of my Tilt, but I need it to work right in my car. I'm thinking of staying away from purchasing WM 6.1 smartphones because of this.
frustrated...
Wow, no one has answered my post here, at ATT, at Kenwood, or on tiltsite. HTC answered only to tell me that compatibility doesn't necessarily mean that it would work (bs). This is very frustrating. I've read post all over xda developers and the rest of the internet about tilt bluetooth problems yet no one has an answer. I've completely giving up on trying to get bluetooth to work right with any of my devices (car, computer, etc). I can't imagine buying another HTC product. Good luck to everyone else out there struggling to get bluetooth to work on their tilt while the motorola, blackberry, lg, samsung, and other phone users watch with amazement and pity. Keep fighting the good fight. Hopefully one of you will win. I've completely lost!
That's a pretty strange story you've got there, because I have zero problems with my Tilt and bluetooth pairing to all manners of devices... on a regular basis, I connect my Tilt to my car's Pioneer stereo deck, to my laptop and desktop, and to my wireless headphones and I've had little to no difficulty. Actually, the easiest pairings so far have been between my Tilt and Pioneer Stereo Deck... At least for basic features - in order for the phone book entries to show on the deck's LCD display it required an upgrade from WinMo 6.0 to 6.1 and then in the deck itself I have to manually download the contact book. But that's the only troublesome thing I have to do, which is mostly an advanced feature any way that I could live (but prefer not to) without.
Sucks that you're having problems, all I can suggest is make sure you're doing everything properly... I've had no problems I couldn't overcome with my Tilt and bluetooth capable devices, especially since Windows Mobile 6.1 came out.
Hi,
I'm having the same problems, also when disconnecting from the BT carstereo after a phonecall, the device freezes up.
Anybody found a solution for this problem yet ?
Ny the way, my car stereo is a JVC KD-BT1
GRTZ,
Niels
@k4ever: Have you checked out this thread?
http://forum.xda-developers.com/showthread.php?t=285419
From what I can tell, they've ported the Widcomm BT stack to the Hermes and TyTN, so I imagine it's not far off from the Kaiser/TyTN-II, if it doesn't already work (my BT is working fine, so I'm not too likely to mes with my phone to find out-- but I hope this helps!)
-Weasel5i2
EDIT: Here's a CAB from the newer threads of the above post:
http://rs38.rapidshare.com/files/30721150/broadcomm_bt_stack.CAB
Thanks
Wow, thanks for the replies.
@ceosion
I got it working with a Pioneer deck in Best Buy. I was actually debating buying one, but I paid $500 for my Kenwood setup. All of my other phones work with it, to include other WM phone (not from HTC). I contacted Kenwood, but I have not recieved a reply.
@Weasel5i2
I tried the Widcomm stack when I used the stock ATT rom. It completely disabled bluetooth on the Tilt. I will try it with the PDA Corner rom I'm currently using (the best!) after the holiday weekend.
Thanks again for the replies!
k4ever said:
Wow, thanks for the replies.
@ceosion
I got it working with a Pioneer deck in Best Buy. I was actually debating buying one, but I paid $500 for my Kenwood setup. All of my other phones work with it, to include other WM phone (not from HTC). I contacted Kenwood, but I have not recieved a reply....
Click to expand...
Click to collapse
I am experiencing Bluetooth connection issues between the Tytn2 and a kenwood DNX8220BT As far as I've heard from kenwood the Tytn2 is only supported with the older version of Windows Mobile (6.0)
I've also tried the Kenwood with my wife's Touch Diamond (Also HTC but other CPU, don't know about the BT radio though) but that one is also experiencing trouble. I didn't get any indication when they would have a new firmware version ready.
You did indicate that you also tried another WM phone, which version of WM does that one operate on?
@Mautje
The other WM phone was a Samsung Blackjack II running WM 5. I downgraded my Tilt to the default WM 6 Rom from ATT, but I had the same problems. I'm running the PDA Corner WM 6.1 Rom now. Does matter which ROM I use, I get the same results on the Tilt.
widcomm stack a no-go
I tried the Widcomm stack. It did not work at all. Kept getting error that "there was not enough memory to run, please reset device" or something to that nature. Could not uninstall so I had to re-flash my ROM. Back to square one.
k4ever said:
The other WM phone was a Samsung Blackjack II running WM 5. I downgraded my Tilt to the default WM 6 Rom from ATT, but I had the same problems. I'm running the PDA Corner WM 6.1 Rom now. Does matter which ROM I use, I get the same results on the Tilt.
Click to expand...
Click to collapse
To bad. I was also looking into the other roms on this forum but it wil probably not work..
Kenwood is reporting that it should work with the rom version mentioned in the compatibility sheet.
In the sheet for version 1.43 firmware there is no mention at all of a rom version just the Tytn2.. I guess that's the WM 6.0 version
[/B]Hi, just received my TD2 last week and is enjoying it. I have one major issue though. In my car I have a Pioneer AVIC X3 system including GPS, AV and BT. Its the one with the motorized monitor.
Unfortunately it seems that HTC has chosen a different type of BT that is NOT compatible with my Pioneer system.
Does anyone know of any fixes ?
Maybe you can draw more attention to your thread by adding an appropriate title. Good luck finding a solution!
I had a very high end pioneer, never again.
With mine, the problem was that the pioneer won't recognise PDAs, but it will recognise Smartphones and mobile phones. (Each bluetooth device broadcasts what type of device it is.)
I actually told pioneer the problem, how to fix it, and their support would only say "your phone is not on the supported device list". After i put the effort in to help them improve their systems dramatically, they couldn't even be bothered to acknowledge it / forward it to the development people.... so I spent £600 on a kenwood, worked like a charm, Kenwood's bluetooth modules are made by parrot. (also the £70 kenwood I also have works great too)
There are some registry edits that work to make your phone identify itself as a smartphone, as long as it has the MS bluetooth stack, not sure the exact details though, I've not needed to do that since I got rid of the pioneer.
Hi Trinode,
Thanks a lot for your comments. If I was to try the registry edit thing... would you know a link somewhere where I can get this information ? Otherwise I'm probably forced to change the Pioneer system also.