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.
Related
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.
Apparently there is a known issue with the Microsoft bluetooth stack which makes it virtually useless to use this phone with Infiniti/Nissan vehicles.
I own a G37, and when I connect the Tilt, everything connects but the quality is sooooo poor that it sounds as if I have the phone in the house and the car is 100 ft away (crackling sound, and no one on the other end can hear me).
I have tried several of the roms here, including the official ones, and no luck thus far. I have tried playing around with the bitpool settings and once again no luck.
Anyone have any suggestions? Is there any way of replacing the Microsoft stack implementation from the Kaiser with the one from the Hermes? That one works perfectly with my car...
Have you tried Austinsync's clean rom? Its working fine with my M45 and I had the same problem you did with some other ROMs. Not sure if ROM change fixed it or one of the other hundred changes I make to my phone every other day. I assume you have adjusted the volume while in-call?
sell your car and buy American!
kireol said:
sell your car and buy American!
Click to expand...
Click to collapse
Your phone is made by a Taiwanese manufacturer. I tried searching for a American-made cellphone so that you could immediately begin your purchasing prospects, but was stunned to find that there is not one American cellphone manufacturer.
Your profile picture looks somewhat like a Dodge Ram to me. You might be interested to know that Chrysler recently built a new $315M Dodge plant in Brazil. They also worked collaboratively with Mitsubishi and Hyundai to design 3 engines that will be manufactured mostly in South Korea and Japan.
But let me get back to the topic at hand. I own a 2007 G35S Sedan and I have had very minimal trouble with my Tilt and the handsfree system. Everything works fine, including the reception meter (never worked on my 8525, even with WM6 ROMs). The only problem that I have noticed is that if I answer an incoming call using the button on the steering wheel, the car appears to start the call, though the audio is routed through the phone for the first 10 seconds and then the car resumes control. It is worth noting that I couldn't get my 8525 (WM6) to work with the car at all - even with the latest and greatest.
I will borrow my dad's Kaiser (as mine was returned earlier today), and try the Austinsnyc's superstorage rom. Hope it works, although I think it's based on the base HTC rom. As I'm sure they're using the same Bluetooth stack, problem should be the same.
Either way, I'll try and report if it works.
As far as the buying American... I thought that whole marketing scheme went out the window a few years ago when Chrysler merged with Mercedes Benz, and most of our products are made in China (as our workers are not willing to work so cheap without going on strike)... don't you just love the beauty of the world economy?
klasikahl said:
Your phone is made by a Taiwanese manufacturer. I tried searching for a American-made cellphone so that you could immediately begin your purchasing prospects, but was stunned to find that there is not one American cellphone manufacturer.
Your profile picture looks somewhat like a Dodge Ram to me. You might be interested to know that Chrysler recently built a new $315M Dodge plant in Brazil. They also worked collaboratively with Mitsubishi and Hyundai to design 3 engines that will be manufactured mostly in South Korea and Japan.
But let me get back to the topic at hand. I own a 2007 G35S Sedan and I have had very minimal trouble with my Tilt and the handsfree system. Everything works fine, including the reception meter (never worked on my 8525, even with WM6 ROMs). The only problem that I have noticed is that if I answer an incoming call using the button on the steering wheel, the car appears to start the call, though the audio is routed through the phone for the first 10 seconds and then the car resumes control. It is worth noting that I couldn't get my 8525 (WM6) to work with the car at all - even with the latest and greatest.
Click to expand...
Click to collapse
It was supposed to be a joke as it has nothing to do with the car. But since you wanted to act all high and mighty......
My Dodge ram was designed approximately 15 miles from my house. It was built 5.5 miles from my house. The company that built it employs approx 200,000+ direct employees and roughly 400,000 indirect, here in the U.S., where i live. At an average salary of $75,000 that's roughly 45,000,000,000 that the company that I buy my car from pumps back into the American economy. This does not include car dealers.
The 2007 G35S is designed in Japan. The 2007 G35S is built in Japan. The 2007 G35S employs maybe 1000 people here in the U.S. because someone has to import it and drive the boat, drive trucks, and do paper work. At an average salary(i'm sure it's way off but lets pretend) of $75,000 that's 75,000,000 that gets pumped back into the American economy. This does not include car dealers.
45,000,000,000 vs 75,000,000
yeah, you are right, it's all even. buy imported cars. it makes sense.
Thats EXACTLY the same problem with my 2007 G35 sedan and my HTC TYTN 2.
When i press the receive button, it takes 10-15 seconds to transfer over to the car audio (goes to the handset first).
THe only solution i have is to receive the call using the phone's talk button, which will go immediately to the car.
I am currently running Dutty's Touchflow Final 2 rom.
BTW. Before my G35, i had a 2006 Chrysler 300C Hemi rollin on 22's with full multimedia setup. My first domestic. I only owned imports before. After i came back to get my infinity G35 (after my major accident), i remember now why imports are so much better than domestci. The Infiniti is built like a ROCK, and the 300 was very crude in build quality.
Anyhow.
klasikahl said:
Your phone is made by a Taiwanese manufacturer. I tried searching for a American-made cellphone so that you could immediately begin your purchasing prospects, but was stunned to find that there is not one American cellphone manufacturer.
Your profile picture looks somewhat like a Dodge Ram to me. You might be interested to know that Chrysler recently built a new $315M Dodge plant in Brazil. They also worked collaboratively with Mitsubishi and Hyundai to design 3 engines that will be manufactured mostly in South Korea and Japan.
But let me get back to the topic at hand. I own a 2007 G35S Sedan and I have had very minimal trouble with my Tilt and the handsfree system. Everything works fine, including the reception meter (never worked on my 8525, even with WM6 ROMs). The only problem that I have noticed is that if I answer an incoming call using the button on the steering wheel, the car appears to start the call, though the audio is routed through the phone for the first 10 seconds and then the car resumes control. It is worth noting that I couldn't get my 8525 (WM6) to work with the car at all - even with the latest and greatest.
Click to expand...
Click to collapse
No problems in my M45...
Maybe it's the car and not the phone?
I had a G35 prior to the Bluetooth option so I cant speak about the quality there but the M45 has been pretty good. the Tilt has a low out put at times but 95% of the time it connects perfectly with zero issues. beats using a headset imo
could be the car, but more than likely it's not... here's why:
I have successfully paired and used 2 tytn, 2 8125 (Wizard), and 1 ol' school SMT5600. All worked fine without any crackling, or the other person on the other end not hearing me...
On the other hand, I have tried 2 Kaisers and both exhibit the exact same things...
(btw, in the info screen about the bluetooth connection the connection shows up as "poor" for the kaisers, excellent for the rest...)
It's hard to believe that I'm the only a-hole that has the Kaiser/Tilt and G37 combo out there... anyone else having the same problem or am I alone on this one?
Did you not read my post? I have a Tytn 2 and a 2007 G35 sedan with the exact same problems as you.. Just use the Talk button on your phone to receive calls..
Arent you on G35drivers.com?
marsb007 said:
could be the car, but more than likely it's not... here's why:
I have successfully paired and used 2 tytn, 2 8125 (Wizard), and 1 ol' school SMT5600. All worked fine without any crackling, or the other person on the other end not hearing me...
On the other hand, I have tried 2 Kaisers and both exhibit the exact same things...
(btw, in the info screen about the bluetooth connection the connection shows up as "poor" for the kaisers, excellent for the rest...)
It's hard to believe that I'm the only a-hole that has the Kaiser/Tilt and G37 combo out there... anyone else having the same problem or am I alone on this one?
Click to expand...
Click to collapse
Tilt + my Mercedes work great.
Same problem w/ Tilt & G35x
Not that I'm glad anyone is having this problem but glad to see it isn't just me. I started with an unlocked imported TyTN (Hermes) phone that worked perfectly in my '07 G35x purchased in May. I never had one problem pairing in the car, receiving or making calls, using voice commands via the car or audio quality.
As soon as I purchased my Tilt I immediately had problems in the G35x but not with any other bluetooth device (I also have a Garmin c550 and pair and make / receive calls with it without any problems).
I can pair the Tilt with the car - no problem. I can use voice commands to make a call - no problem. As soon as the phone starts to ring through the car speakers I can tell there will be a problem because the ring is very 'tinny'. I can hear the person answer and speak but they cannot hear me at all. I then put Dutty's ROM on the phone thinking maybe it was a stack issue that might have been resolved in a new ROM (assuming their had been updates to the BT stack). That did not make any difference.
I will by tomorrow test my corporate Blackberry in the car again. I had used it in the car via bluetooth while I had the Hermes - no problem. I will retest now that the Tilt isn't working.
Have any of you contacted Infiniti and / or AT&T? I could only assume until they have a quantity of calls will they say anything other than "not our problem" or, "never heard of that before".
If there are others with this problem it would be good for them to acknowledge their experience here along with any comparative good/bad feedback with other phones in the same and different car / devices.
Update: I've just tested my Blackberry 8700 that worked prior to pairing the Tilt with the G35. I can confirm that the Blackberry still works flawlessly. As the Tilt also works flawlessly with my Garmin device I think the cause is unclear but would appear to be with the Tilt as it is the only thing that has changed in the tests I've identified above.
Regards,
David
minirx7 said:
Did you not read my post? I have a Tytn 2 and a 2007 G35 sedan with the exact same problems as you.. Just use the Talk button on your phone to receive calls..
Arent you on G35drivers.com?
Click to expand...
Click to collapse
well, one of the ways I use the phone also is calling out... when I dial the number and call from the phone, the car bluetooth connects and the crackling starts... (i call my voicemail to test).
besides being an Infiniti/Nissan issue, it appears it is far more widespread... there's already a 20 page thread on BT and Kaiser! from that thread it appears HTC is aware of the issue and is working on an upgraded stack/rom... everyone cross your fingers and hope that one works!
Could you provide the link to that thread?
Thanks,
David
marsb007 said:
well, one of the ways I use the phone also is
calling out... when I dial the number and call from the phone, the car bluetooth connects and the crackling starts... (i call my voicemail to test).
besides being an Infiniti/Nissan issue, it appears it is far more widespread... there's already a 20 page thread on BT and Kaiser! from that thread it appears HTC is aware of the issue and is working on an upgraded stack/rom... everyone cross your fingers and hope that one works!
Click to expand...
Click to collapse
SteinyD said:
Could you provide the link to that thread?
Thanks,
David
Click to expand...
Click to collapse
here ya go... hope someone finds a fix soon...
http://forum.xda-developers.com/showthread.php?t=329270
Thanks .. I hope HTC truly has acknowledged the issue and is working on it. I sent an email tonight to HTC America and hope to get a favorable response soon.
marsb007 said:
here ya go... hope someone finds a fix soon...
http://forum.xda-developers.com/showthread.php?t=329270
Click to expand...
Click to collapse
Multiple solutions...
I'm using Dutty's TouchFlo Final Rom and I'm not having any problems with my 2006 M. So maybe you can try that ROM.
But on the M, I did have horrible problems with my E-Ten M500+ (continous feedback...C R A Z Y), and limited functionalities with my 3125. Both of those problems were solved instantly with this software: http://www.jetwaremobile.com/ They offer 30 day trial of their software, so try it.
marsb007 said:
well, one of the ways I use the phone also is calling out... when I dial the number and call from the phone, the car bluetooth connects and the crackling starts... (i call my voicemail to test).
besides being an Infiniti/Nissan issue, it appears it is far more widespread... there's already a 20 page thread on BT and Kaiser! from that thread it appears HTC is aware of the issue and is working on an upgraded stack/rom... everyone cross your fingers and hope that one works!
Click to expand...
Click to collapse
I do not have this issue with my g35... I do not get any crackling.. Its only when i try to receive calls, it delays like 10-15 seconds!!!
Making calls is NON-issue...
it really is crazy... I've tried that particular rom and it has the exact same problem. I have also tried the Jetware bluetooth stack, and once again, it does the same thing. I've tried about 5-6 different roms, from super clean roms, bigstorage, to the latest build numbers that I could find, and all do the exact same thing. I've played around with the bitpool settings, audiogateway settings, and nothing...
It may be that the combination of the G37 + Tilt just has something in there that makes it go crazy. Could be the car, but as I've said earlier, all other phones work, including the Hermes, without any problems whatsoever.
Anyone out there with a G37 willing to give the Tilt a try? I'm about to go to the dealer and pair it with other cars to see if it works!
If you have the G37 (coupe I guess?) then you have the 2008, right? I know they switched to the new hard drive based system. So maybe they don't have all the bugs worked out. Top it all off, MS's bluetooth stack is kinda shaky, so it might be amplifying the problem.
I don't see any service bulletins relating to this issue on your car either: http://x.infinitihelp.com/forum/local_links.php?catid=86 I doubt that Voice Recog system update will fix your bluetooth issues...but then it might. Worth a try.
marsb007 said:
it really is crazy... I've tried that particular rom and it has the exact same problem. I have also tried the Jetware bluetooth stack, and once again, it does the same thing. I've tried about 5-6 different roms, from super clean roms, bigstorage, to the latest build numbers that I could find, and all do the exact same thing. I've played around with the bitpool settings, audiogateway settings, and nothing...
It may be that the combination of the G37 + Tilt just has something in there that makes it go crazy. Could be the car, but as I've said earlier, all other phones work, including the Hermes, without any problems whatsoever.
Anyone out there with a G37 willing to give the Tilt a try? I'm about to go to the dealer and pair it with other cars to see if it works!
Click to expand...
Click to collapse
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
hi,
I am driving a BMW series 1. I have an integrated hands free system in the car. I can connect the Touch Diamond with it. Even all the contacts can be shown and dialed with the multi functional buttons on the steering wheel and the radio. Here comes the issue:
During a call the BT connection aborts. Sometimes after 5 seconds, sometimes after 5 minutes. When TomTom Navigator is running it hardly ever worked. So my guess is, it is a performance issue and if TomTom is not running then it only aborts because the battery gets below 60% and perhaps some kind of powersave mode would be activated? I am using a cooked Rom based on the latest original HTC Rom. With the original ROM it was even worse. I hope a cooked ROM would solve the issue. Unfortunately not.
The technical support from HTC told me to ask my car manufacturer. They told me of course the opposite. After I told the HTC guy that it works fine sometimes and I guess it is because of the battery, he just told me to keep it loaded all the time. Quiet funny, but if the performance is the reason then it will never work with TomTom used at the same time.
So, does anyone has any good idea what I could do? Are there any patches available?
I would be really happy for any answer. thanks
Sascha
R 1.11.25.1
G 52.58.25.30H
D udk syrius topaz R3 based on 2.04.00.00
I had an issue with connecting my diamond to my X5. I fixed it by changing the bluetooth handsfree gateway dll from HTC custom dll to the Microsoft voicecommand dll. Not sure if it will address your issue, but it is worth a shot.
I posted it on ppcgeeks.com. (Sorry i dont have the link handy at the moment)
thanks a lot. i will try and post the results.
So I have an xperia, and I have a new JVC Bluetooth deck, I was so impressed how flawlessly it worked with my old phone the Kaiser/tilt, but to my surprise I have not been able to get it to properly pair up with my newer xperia. They will read each other and try to connect but I always end up getting an error. Sometimes it still shows up as connected but nothing works. I used my kaiser/tilt for both calls and streaming music through my new JVC bluetooth deck and I loved it, so its pretty dissapointing when I upgrade to what is/was one of the hottest & expensive windows mobile phones and it apparently has bluetooth issues.
I tried a few fixes already like changing the registry to read as a normal phone and I added in a missing bt profile, unfortunately nothings changed. I am curious tho because i had a magician and they had whole bt stacks that I messed around with, and I'm also wondering if a flash or two of a new rom may make a difference. Ocerall I'm really happy with the X1 (unlike my tilt/kaiser which had lots of problems) so much so that I don't really feel the need to flash a new rom, but if it might have a chance of fixing my bt I'm all for it.
Let me know if anyone has any suggestions, tia.