i just got the car and it wont recognize the titan...i love my phone so i dont want to change it...i have the latest sprint rom installed...any other custom roms that might get the 2 to pair?? any other ideas?? thanks
let me borrow your SL550 and i'll let you know...
what do you mean by latest sprint rom? the latest official is 3.35. the latest leaked 'official' is rom 3.49 with radio 3.39.10 and it does have some BT improvements. i know someone mentioned a car BT system that started recognizing their titan as of 3.49/3.39.10.
dcd1182 said:
let me borrow your SL550 and i'll let you know...
what do you mean by latest sprint rom? the latest official is 3.35. the latest leaked 'official' is rom 3.49 with radio 3.39.10 and it does have some BT improvements. i know someone mentioned a car BT system that started recognizing their titan as of 3.49/3.39.10.
Click to expand...
Click to collapse
lol, i barely trust myself with her
thanks...i have the latest official one...ill try the leaked one and let you know how it goes...
cool, please do let us know as this is probably relevant for the guys from the previous discussion, i think they had infiniti and/or bmw.
if it doesnt work out, i know which one i'd pick. one SL550 is worth 323 titans...
funny thing is i just had a bmw and it would connect but not transfer the contact list but i didnt care cause i drive was so tedious...but i love the system in the benz so itd be nice if it worked.
(just downloaded the ROM...installing!)
Congrats on your new car! I wasnt able to get it to work with bluetooth system either..... wish it was SL550! Drive safe!
I do not have the same vehicle, thankfully, but I have a 2008 Ford Fusion with Sync and it connects to the Mogul fine and downloads the phonebook, does all that fun stuff.
It can't do the text message reading/composing that Sync offers, but thats a Mogul limitation.
It has worked with just about every firmware I have used, both official and DCD's since whatever firmware first allowed us to use GPS (thats just around when I got the car).
It does some odd things, like for whatever reason, if I use the bluetooth stereo option (if I wanted to stream music to my car over bluetooth for whatever reason) it mutes my phone after I shut off my car. I normally keep it on vibrate, it turns it to complete silent.
But from what I read thats a Mogul issue, and turning off Bluetooth Stereo streaming solves it. Regular hands free calling works great.
So hopefully that tells you something, the Mogul is fully capable of being used with bluetooth vehicle audio systems, I guess its just picky about which ones.
Although the 3.39 radio and 6.1 ROMS made Jetware Mobile software obsolete for connection to my Audi (including phonebook sync), you may want to try in with the Benz if the upgrades alone don't work for you. The biggest improvement for me on the 3.39 radio compared to 3.35 was with bluetooth.
I would read the owners manual of your Benz. I have noticed that most expensive cars have there own festive way of pairing a phone to the car.
xxballinboi786 said:
i just got the car and it wont recognize the titan...i love my phone so i dont want to change it...i have the latest sprint rom installed...any other custom roms that might get the 2 to pair?? any other ideas?? thanks
Click to expand...
Click to collapse
I have an E350. The car would recognize the mogul. It did not transfer the contacts initially ( first 2 weeks) but not one day it did. Showed the same behavior with 3.35 as well as the leaked 3.39.
Related
Should I stick with 1.66.00WWE or move to the 1.7X ROM??????
Also what type of Bluetooth head sets are you all using, any specific recommendations or success??
Thanks!
I'm still using the 1.66.00WWE that came with my device.
I'm using the O2 Bluetooth headset and have had no problems with it at all - voice quality is fantastic, battery seems to last for ages and I've never lost bonding...
I've been working in Malaysia for the past 4 years and about to return to Sydney. I have the 1.66.00WWE that came with my device and will probably keep it.
I'm using a Logitech BT headset and thought it is bigger than the SE-HBH 60 I had previously it is a lot more comfortable to wear, sounds clearer (to me and the person on other end of call) and has a longer battery life.
Very happy with it.
Ed
Thanks guys, appreciated.
Im in Melb, using 1.72.00
I havent had any problems with it, but I dont use BT headset, I do use a BT GPS quite a lot and have had no problems.
But I havent noticed that upgradeing from 1.66 really added anything worth while either. As I havent had any problems Im not going to downgrad either, but I would not recomend upgrading unless you are having some particular problem until the SE version finally comes out.
Just remember you are using Optus network, and I think after you upgrade you do require some patch in order for you GPRS to work.
Gee, guys, you're all well ahead of me... I'm still runnning mine with the 1.60.00WWE (ex. ROM 1.60.44)... wonder when I'll see an upgrade...
Besider the older version - everything's fine
I ended up trying both a Belkin and also Motorola head-set. Both had very poor quality for the inbound direction of the call, filled with crackle and echo.
My outbound direction is fine........
Anyone got a suggestion?
I have the thing basically working. I am also getting a Vox 710s to try as well.
My primary concern at this point is auto connect. I am a consultant and get in an out of the car a lot. So it is pointless if I have to click the stereo 6 times each time I get in. I need the thing to just work. I may return the deck if I can't get it too work.
So I need to find out where the failure is. Then I can pursue it with the manufacturer. Why can't this stuff just work?
So if I find a bluetooth headset that does auto connect to the phone do you think that is enough I can't got to pioneer and say the problem is your deck?
If the head set doesn't auto connect which I find hard to believe then I can work with jetware or cingular to see what is up. I am guessing it is the deck.
Thoughts
opps
phone is a cingular 8125 up to date roms running the latest Jetware.
another poster on crutchfeild says tmobile dash does autoconnect
does this narrow down the cause?
I spent over a month working with Pioneer and Jetware with an AVIC Z2 GPS unit with Pioneer's ND-BT1 adapter. In the end, I had to pull the Z2 and installed a Kenwood. Pioneer tech Support finally admitted that they suffer problems with nearly all PDA type phones, especially when they 'sleep'. Seems the connection is dropped nearly as fast as it is made and the devices won't stay connected. Mine dropped EVERY call when the backlight went out after 60 seconds of non-pda use. If i set time timer up to 5 minutes, it dropped the call when the PDA went to sleep. Leaving the PDA on all of the time of course drained the battery.
My wife now has the HTC Touch in her car with the AVIC Z2 and the ND-BT1, however, the problem isn't there. Pioneer has come out with a 'Service' upgrade program for the Z2 and the Touch uses a newer WM6 version. The two seem to be compatible.
thanks for the insight
Having just read the mk6000 review I don't feel so bad. I was wondering how well as system between your speakers and you deck would work.
That said I ordered an unlocked 710 (vox) to test out with wm6 and bt 2.
I am hoping this will work. Do you think I will still need Jetware?
xophere said:
Having just read the mk6000 review I don't feel so bad. I was wondering how well as system between your speakers and you deck would work.
That said I ordered an unlocked 710 (vox) to test out with wm6 and bt 2.
I am hoping this will work. Do you think I will still need Jetware?
Click to expand...
Click to collapse
Try it first without Jetware. It is now with at 30 day free trial and limited features but good enough to test once you get your new unit. If you find out that you need it, then register it.
I have had a Pioneer DEH-P9800BT for many months now, and I am getting sick of having to click 6 times to connect the phone. You would think that the stupid thing could perform the same thing when you turned on the car/stereo. I wish I could get a firmware update or something to fix it.
Replace your Pioneer with the one of the Sonys (MEX-5000BT if you need preouts, MEX-2500BT if you don't). I've been using the 5000 since January -- once I did the initial pairing, it connects every time both in handsfree & A2DP.
Hi all,
I have bought 3 x HTC S740 for my company. They are SIM free versions running on Vodafone UK. CE OS 5.2.20279 (Build 20279.1.3.4) - Radio 12.23.30.06H_0.24.30.24 - Ril Version 2.002.
The phones keep locking up (at least once a day). Nothing happens if I press any buttons. If I wait 3/4 minutes the phone will come back to life (and it'll actually start doing the commands I send with the previous button presses). It looks like it's a CPU problem.
Also, the bluetooth keeps disconnecting in the car. It shows as turned off on the phone and you have to restart the phone to be able turn BT back on.
Of course, HTC is no help. Is it worth trying a different ROM?
Thanks
gezzaroy said:
Is it worth trying a different ROM?
Click to expand...
Click to collapse
I would say yes. I have non of the problems you mentioned, so they could be Vodafone ROM's bugs.
It's not running the Vodafone ROM; it's running the HTC one (SIM free). I was actually thinking of trying the Vodafone ROM. What ROM are you running?
Oh, I misread your post. Mine runs:
Rom version: 1.14.401.1
Rom date: 10/06/08
Radio version: 0.24.30.24
No significant problems with it so far.
My ROM version is 1.14.405.1 dated 27/10/08. Any chance you could extract your ROM and post it?
See my post about the bluetooth. Yes I tend to notice it when I have been using it in the car (you don't drive a BMW do you) but not always.
I am not getting any lock ups though.
Yes I saw your post. I drive a push bike The guy who uses the phone drives a Saab 93. His HTC S730 worked perfectly in that car. HTC said we should have checked the phone was compatible. Duck & dive!!
gezzaroy said:
Yes I saw your post. I drive a push bike The guy who uses the phone drives a Saab 93. His HTC S730 worked perfectly in that car. HTC said we should have checked the phone was compatible. Duck & dive!!
Click to expand...
Click to collapse
I am not sure this is a car kit related issue because my phone does work fine with the car it's just that every now any then, I notice that the bluetooth has switched off.
it does not do this whilst it is connected to the car. It's just that I come to make a call and realize that the phone has not connected because the BT has turned itself off at sometime before I got into the car.
I've not been able to recreate the problem. The Saab belongs to a Sales guy, so he's always running around and I can't keep up on my push bike but what he says is that Bluetooth switches off whilst connected in the car and then he can't turn it back on unless he restarts the phone.
Same Proble
I hve the same Problem with a Opel Astra. And thers no help from HTC.
I recently installed the Bluetooth update from the HTC website.
Since then the disconnecting from the car problem seems to have got an awful lot better. It now only seems to happen if I have previously disconnected a BT headset and then walked out the door and got straight in the car.
anyone solve it?
I have soled it using this...
http://www.htc.com/europe/SupportDownload.aspx?p_id=163&cat=0&dl_id=609
To be honest I think that it worked for me...Im not 100% shure
Anyone else with a Parrot MK6000 having problems making and receiving a call while connected to the kit? Mine works great on stereo A2DP but when trying to make a call the voice cuts out after a second or two and then a few seconds later disconnects, probably because the person on the other end can't hear me and hangs up. At first I thought it was the phone and got a replacement but no joy. A similar thing happened with my Omnia last year and I got rid of the phone because of it thinking the phone was at fault but now I don't think so. Kit works fine with other phones but not Windows Mobile even though the phones I am having problems with are listed as completely compatible and tested on Parrots website. My software version on the kit is 1.03a which is their newest. Any ideas? Still waiting on a reply two days later from Parrot. Seems kind of screwy to have to worry whether and accessory like this will even work with your expensive phone. I thought that was why they came up with standards. These things aren't cheap or easy to install.
Try a Firmware update to the Parrot MK6000. Also ask them a way of configuring your HTC to work correctly. If they say that is full compatible, that's because they tested, and if they tested they know the definitions inputed in the phone.
I've a MK6100 and it works fine, not exactly the same... but yeah try the firmware upgrade
None to try
I've already got the most recent firmware. Parrots testing is crap. When I first got the thing within a day, I knew that I needed a firmware update on their upgradeable "ahem" unit. Software upgradeable was even plastered all over the box. The unit that came in that box had the 1.0 software and guess what. Faulty testing. They had to replace it with a unit that had the current software because they made a mistake in testing and updating would not work on the 1.0 units. That was over a year ago and there is still no firmware updates. They knew they had a problem with WinMo phones even then and now they are saying compatible? Onl good thing that happened then was I was in Detroit and drove my big truck right up to the door of their headquarters. One of their lab guys was forced to reinstall the unit that had been installed just two days earlier. You would think they would never want to have to do something like that again. So anyways, I have a call and and email into them to let them know I have a problem and no response. Hopefully someone else who thinking of buying one of these units see's this post and takes the warning stay away, at least if you have a smart phone because these people aren't going to support you. (At least not unless you embarrass them by pullling up to their front door in a 75 foot truck )
Techitrucker said:
(...)(At least not unless you embarrass them by pullling up to their front door in a 75 foot truck )
Click to expand...
Click to collapse
Yeap, that's also a good way of making them do what they promise... And to claim warranties...
Stay away from Parrot bluetooth
I have two parrot handsfree units, CK3200LS in my car, CK3100 in my wifes.
They have caused nothing but trouble for my WM phones (Tilt and now TP2)
I can't get the TP2 to pair with the CK3100. I'm waiting for parrot to respond to my help request. Their support info is worthless. The instructions refer to settings which don't exist and password format which is unusable (/"1234/" ?).
When the WM phones successfully pair, there is a re-occuring problem in both Parrot units where there appears to be an incoming call (it doesn't show a caller ID - just 'CALL') but the call cannot be answered. If you press the green button to answer, the unit locks up. You can't "disconnect" with the red button. The only thing you can do, is turn the car off, wait for the unit to turn off, and then turn the car back on to reset. Sometimes my Tilt would get locked up from the call and need to be soft-reset as well.
I had the unit working successfully with non-WM phones for some time, so it was no longer under warranty. When it started with the WM phones I took it to the installer. He was aware of the problem, but had no idea how to deal with it as the problem is so transient.
Bottom line - stay away from Parrot if you have a WM phone.
sblevine
have you try Jetware? I think it may solve alot of your problems
Used Jetware in the past and it caused more problems than it solved. After paying and exhorbitant amount of money for a setup, should not be needing to spend another $15 bucks and installing new software on the phone anyways. The answer I received from Parrot is that even though their website specifically says that the TP2 is a supported phone they are not aware of that and it is not. Real organization there. They also said they will no longer be supporting the MK6000 with software updates not that they supported it much to begin with. They are more than happy to try and find a workaround which I will try but not holding my breath. This will be the last Parrot product I will purchase. The MK6000 is less than 2 years old and is a hard install. It is unimaginable that a company should stop supporting such a product in such a short period of time. The vehicle you need to rip apart to install this thing will more than likely be in financing three times as long. Thoroughly unacceptable.
I had some issues with the TP2 on my carkit too. I discovered that issue was with the ROM on my TP2. Because the carkit downloads the contacts, TP2 just blocks somehow, The response of the phone was slow, I could not accept calls... Then I have installed 6.5 beta version of rom for TP2 and it has sloved the issue. Maybe you could just try installing "official ROM" 6.5.
I am glad you have written this all down. I have an MK6000 in my car now, and while I have some issues between it and my (soon to be old) Tilt, I can make calls, have full conversations and listen to music. I just have to put up with weirdness after I hang up the call and check to ensure my phone isn't suddenly in silent mode when I turn the car off.
I would like to know, what else is out there as far as installed hands-free kits that will work with WM phones? I've got a Tilt 2 coming to me this week (yay!) so I really don't want more problems!!
-Chuck
so is the parrot mk6000 worth it, i need a bluetooth car kit and it has the basic functions i need
also is this a good price or is it available cheaper from another place , the site i saw it at i think was mynewgps.co.uk
Many thanks
HI all,
I can't post in the Dev section yet so I will ask here. I installed this ROM last night and it all went well except for today in the car while testing bluetooth I have no audio unless I switch the source away from Bluetooth and back (say, set it to Speaker then back to BT). I did a full wipe again and re-loaded the ROM and still have the same problem. I am using the .19 radio if that makes a difference and my car has the older (2008) Ford Sync system (2.1).
Is anyone else having a similar issue?
rpoitras said:
HI all,
I can't post in the Dev section yet so I will ask here. I installed this ROM last night and it all went well except for today in the car while testing bluetooth I have no audio unless I switch the source away from Bluetooth and back (say, set it to Speaker then back to BT). I did a full wipe again and re-loaded the ROM and still have the same problem. I am using the .19 radio if that makes a difference and my car has the older (2008) Ford Sync system (2.1).
Is anyone else having a similar issue?
Click to expand...
Click to collapse
This seems to happen quite a bit. It's a semi known issue from a number of cusom ROMs. Have never seen a solid fix for it except what you just described. Some people have this problem and need to competely turn it off and back on to get it to work! If it truely is a dealbreaker for you (it shouldn't be...not that big of a glitch), best bet is to stick to a ROM closer to the original tbolt software.
Its not that its a dealbreaker but it kind of defeats the purpose of using handsfree in the car when I would have to pick the phone up and switch BT inputs to get it working. I had a low Bluetooth volume problem with a rom before which was fixed with, I think, a different radio but I never had this one before. I noticed someone else posted the problem in the official thread so hopefully comes out if it. Thanks.
So this happens every time u get a call, or only every time you connect to the car?
I haven't received any calls yet while connected to BT but it happened when making calls and it seems once I do the toggle to get things working then it "sticks" and works thereafter. I haven't tried reconnecting while in the car to see if the fix would stick afterwards but this morning when I got into my car I tried making a call and it worked great first time and I know I rebooted the phone multiple times last night with doing backups of the rom, etc. Maybe it somehow worked itself out or maybe it's just an intermittent thing. I didn't change anything since the install.