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
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.
Bought Tilt few weeks ago and found out, like many on this forum, that in-car bluetooth phone system was not working properly. Sound was terrible and microphone did not work at all.
Things I tried: Tilt with AT&T rom; AT&T rom withouth bloatware;jetBTFExt-1.31; registry tweeks. Nothing worked.
I still have Qtek S200 and it works just fine.
Reading few post here and there, I found what worked for me.
After placing a call or answering a call, transfer it to handset and back to the car system.
Sound quality and microphone will be working properly.
I believe the problem is in establishing proper connection between Tilt and car system when call is initiated or answered.
Bad part about this workaround is that it take some time to push those buttons and it very very annoying. However, before real fix is found, if I need to have a long conversation during driving I will use this method.
ashrek said:
Bought Tilt few weeks ago and found out, like many on this forum, that in-car bluetooth phone system was not working properly. Sound was terrible and microphone did not work at all.
Things I tried: Tilt with AT&T rom; AT&T rom withouth bloatware;jetBTFExt-1.31; registry tweeks. Nothing worked.
I still have Qtek S200 and it works just fine.
Reading few post here and there, I found what worked for me.
After placing a call or answering a call, transfer it to handset and back to the car system.
Sound quality and microphone will be working properly.
I believe the problem is in establishing proper connection between Tilt and car system when call is initiated or answered.
Bad part about this workaround is that it take some time to push those buttons and it very very annoying. However, before real fix is found, if I need to have a long conversation during driving I will use this method.
Click to expand...
Click to collapse
I agree, thats the method Ive been using, but quite annoying. However it is a lot better than holding the phone in your hand while driving AND talking. Hope HTC will fix this annoying issue.
I am using HTC Rom and it links with Mercedes Benz BlueTooth perfectly. It shows all my contacts infomations alone with call history od called and received.
Navigation/phone system bug?
avega1027 said:
I agree, thats the method Ive been using, but quite annoying. However it is a lot better than holding the phone in your hand while driving AND talking. Hope HTC will fix this annoying issue.
Click to expand...
Click to collapse
Do you have a map screen coming up after you press "Use Handset" button? This is something that I have in my car (2007 G35x).
ashrek said:
Do you have a map screen coming up after you press "Use Handset" button? This is something that I have in my car (2007 G35x).
Click to expand...
Click to collapse
If youre refering to the GPS map, then yes. So then I have to press "PHONE" on the unit again to connect.
Penske MB said:
I am using HTC Rom and it links with Mercedes Benz BlueTooth perfectly. It shows all my contacts infomations alone with call history od called and received.
Click to expand...
Click to collapse
My TILT links fine w/the G35 but its the quality of the phone call that is terrible. Also I have heard of reports that the HTC ROM doesnt make the call quality any better vs the AT&T ROM
Hello,
I wonder if somebody can help me get to the bottom of this.
Basically, I have a TyTN II (branded as a T-Mobile MDA Vario III). I also have a Parrot 3200+ LS Colour car hands free kit.
Initially, I had a TyTN (branded as a T-Mobile MDA Vario II) and this worked fine with the Parrot. Problems began when I upgraded it to Windows Mobile 6 after an update was released by T-Mobile. What would happen is as I started the engine and the Parrot connected to the phone, it would say I was in a call even though I wasn't. It could only be resolved by rebooting the phone.
When I got the TyTN II, the problem became more frequent to the point where it was just annoying to use.
Now, this is where it gets interesting. Parrot are blaming Microsoft for this problem and aparently the problem *may* or *may not* get fixed in 6.1 which is some time off yet. It is a Bluetooth Stack issue aparently but I am not sure I believe them on this nor their attitude to if it will actually get fixed.
I am wondering if anybody knows anything more about this or any fix for it.
Best Regards,
Craig Brass
craigbrass said:
I am wondering if anybody knows anything more about this or any fix for it.
Click to expand...
Click to collapse
Install one of the 6.1 ROMs here and see if it helps?
I have this with my TyTn II and parrot 3300. It also used to happen with my Orbit.
I noticed that it only does it when a data connection is active. If I press the red button on the Parrot it clears and all is good.
Not sure if yours is the same issue.
I have a Parrot 3100, and have loads of problems! It randomly crashes, it randomly decides to want to call random people, it randomly decides to route the call through the Tytn II rather than the Parrot, and it randomly works without a problem. I emailed Parrot and got this response:
--------------------------------------------------------------------------
The HTC TyTn II is still undergoing compatibility tests with our products, thus is not listed as being compatible at present. We are currently also working closely with HTC to improve compatibility and functionality with new PDA devices running Windows Mobile 6.
I would recommend dialing out from the Parrot as opposed to using your handset as from experience this works best.
I would also recommend updating the software on your Parrot, the latest version is 4.16. To update you will need a Bluetooth enabled PC (preferably a laptop) and our Parrot update tool software. http://www.parrot.com/usa/support/downloads
--------------------------------------------------------------------------
Just noticed tonight that a new version is available for download, (4.17) so I have upgraded the Parrot and will give it a try tomorrow.
Cheers
so, was the upgrade succesfull? did it solve ur issue?
I'm also having issues using my tytn ii with the parrot ck3100. (standard firmware in it)
No, it hasn't completely. It has solved most of the problems, but it now decides to (randomly) mute incoming calls, and route the audio through the handset instead. It also decided to route the TomTom audio via the parrot! I didn't think that was possible???
I'm having some of the same sorts of problems w/ the Parrot CK3100 and my Tilt. Of course, I just go it installed last nite, so I haven't had a ton of time to play with it. I DID, however, do a long road trip today and here's what I've found.
When initiating a call from the phone, there's about a 50/50 chance that it will go thru the handset or Parrot.
One time, the Parrot locked up to a point that I had to get off at an exit and restart the engine to reset it.
I had to re-pair the phone and Parrot once, because the lost one another.
I'm running the latest AT&T ROM on my phone and latest firmware on the CK3100. I never had ANY of these problems w/ my Nokia CK-7W, but it had a REALLY annoying echo on the other end when used w/ anything but a Nokia phone.
Dan
Today, things got even stranger. As of this morning, the kit would try to initiate a phantom call every time the car was started and it connected w/ the phone.
Then, it was muting the radio for 1-2 seconds every 3 to 5 minutes - very annoying when listening to an audiobook.
As of this afternoon, both problems magically stopped. I have e-mailed Parrot tech support, but I'm not hopeful that I'll get a useful reply.
I have had so many problems with the 3200 that ,due to anger, I have broken the bracket and front screen. It mutes the radio even after the call has finished. Crashes too often. I have no audio at least half of the calls I make.
I must add that it also did this with my Trinity running WM6 but worked flawlessly with my SP5 smartphone.
I read "HTC and Parrot Announce Strategic Alliance" on the Reuters website.
How I chuckle.
Hi,
When my phone is connected to my car kit (Opel/Vauxhaul UHP) bluetooth sometimes stops randomly. I can turn bluetooth on again with the commmanager and everything is working again. But it can hapen again after a few minutes.
Does anyone have this problem to or even better a solution?
I allready tried all the different Radio Roms, but this didn't solve my problem.
Well with mine i have some hickus but it just happpends once a while.
Most irritating about Diamond and BT in my opinion is that wa have no equalizing for it. and the sound setup from the begining is horrible.
Asked here if anyone has a solution before but none replied.
But as far 2 your problem no. And i use a Pioneer system in my car.
Mauser.NET said:
Hi,
When my phone is connected to my car kit (Opel/Vauxhaul UHP) bluetooth sometimes stops randomly. I can turn bluetooth on again with the commmanager and everything is working again. But it can hapen again after a few minutes.
Does anyone have this problem to or even better a solution?
I allready tried all the different Radio Roms, but this didn't solve my problem.
Click to expand...
Click to collapse
HI
Same was happend with me (Opel), when my battery is low.
orsiga said:
HI
Same was happend with me (Opel), when my battery is low.
Click to expand...
Click to collapse
Mine is not low on battery, but I shall try it once connected to the cigarette lighter.
Nobody else has this kind of problems??
Mauser.NET said:
Mine is not low on battery, but I shall try it once connected to the cigarette lighter.
Nobody else has this kind of problems??
Click to expand...
Click to collapse
I've a JVC head and my bluetooth has no problem.
I have a Honda Accord with handsfree built in and I too am having problems. The phone and car both agree that a connection has been made but when i use it to either ring out or receive a call the radio mutes and when receiving the ringing tone sounds over the car speakers but I can`t hear the caller except on the phone which isn`t very useful. Would a ROM or radio upgrade help or is it just a compatibility problem
davemazo said:
I have a Honda Accord with handsfree built in and I too am having problems. The phone and car both agree that a connection has been made but when i use it to either ring out or receive a call the radio mutes and when receiving the ringing tone sounds over the car speakers but I can`t hear the caller except on the phone which isn`t very useful. Would a ROM or radio upgrade help or is it just a compatibility problem
Click to expand...
Click to collapse
I had this kind of problems also. Also syncing the phonebook gave me problems. You could try JETware, this solved almost all my problems, except now the bluetooth crashes
Mauser.NET said:
I had this kind of problems also. Also syncing the phonebook gave me problems. You could try JETware, this solved almost all my problems, except now the bluetooth crashes
Click to expand...
Click to collapse
Thanks Mauser. I tried Jetware as you suggest and I`m afraid it didn`t help in fact I think it crashed the handsfree system in the car like you. This is the final nail in the coffin for my Diamond. I just can`t get used to it so it`s off to Ebay with it.
davemazo said:
Thanks Mauser. I tried Jetware as you suggest and I`m afraid it didn`t help in fact I think it crashed the handsfree system in the car like you. This is the final nail in the coffin for my Diamond. I just can`t get used to it so it`s off to Ebay with it.
Click to expand...
Click to collapse
I'm sorry to hear that
I am very pleased with my Diamond... I would sooner put my car on eBay than my Diamond
Did you try to check almost everything on in the advanced settings of Jetware? I have also limited the phonebook sync to max 5 entries to debug and on the site of Jetware there wat a fix for Opel car kits.
Keeping my fingers crossed, but until now I haven't experienced any bluetooth crashes.
Mauser.NET said:
I'm sorry to hear that
I am very pleased with my Diamond... I would sooner put my car on eBay than my Diamond
Did you try to check almost everything on in the advanced settings of Jetware? I have also limited the phonebook sync to max 5 entries to debug and on the site of Jetware there wat a fix for Opel car kits.
Keeping my fingers crossed, but until now I haven't experienced any bluetooth crashes.
Click to expand...
Click to collapse
Thanks again Mauser. I tried various settings but without any success, I think the phone is just not compatible with the Honda. Having said that I don`t have much luck with bluetooth at all on the phone. More often than not It just won`t detect other bluetooth devices and when it does it won`t send or receive files so it`s time for it to go and I can go back to a trusty Nokia
Problems here with BT connection to car kit, too. I'm using the built-in car-kit of an Audi A4 (standard one not that with navigation, remote SIM, etc). I've noticed the following issues:
- when I try to make a call, the CD is cut off but NOTHING is heard in the car speakers UNTIL the other party answers the call (and then I start the conversation). No ringing tone, no nothing. I cannot hear the busy tone, or network failure/congestion tone and this is annoying since I have to keep an eye on the phone to see what's happening. I found myself checking the phone when, after calling someone, nothing happened and in fact I got a busy tone and the call ended.
- sometimes, when I receive a call, the CD stops playing but when I answer nothing is heard from the car speakers but only from the phone (as davemazo said also).
- when I receive a call, I hear in the car speakers a "standard" calling tone, not the ringtone I have assigned for that contact
I have to mention that with any Nokia I had before (and still have one as a second phone), these problems do not exist. I know there is a compatibility between Audi factory installed car-kits and Nokia, but BT is a standard and most of the functions should be supported despite the phone model/type. I've tried also with an iPhone and it's working great, as my Nokia do. I don't understand why it is like this with the Diamond. In fact, I think it is not related to Diamond itself...it's doing like this with ANY Windows Mobile device I've tried in the past (Orange C600, Samsung I600).
Are there any solutions for this? A CAB, a new BT radio, a software, anything?... I don't want to buy a new BT car-kit and try with different models until I find something compatible
Thank you for any info/tip
Rapier said:
Problems here with BT connection to car kit, too. I'm using the built-in car-kit of an Audi A4 (standard one not that with navigation, remote SIM, etc). I've noticed the following issues:
- when I try to make a call, the CD is cut off but NOTHING is heard in the car speakers UNTIL the other party answers the call (and then I start the conversation). No ringing tone, no nothing. I cannot hear the busy tone, or network failure/congestion tone and this is annoying since I have to keep an eye on the phone to see what's happening. I found myself checking the phone when, after calling someone, nothing happened and in fact I got a busy tone and the call ended.
- sometimes, when I receive a call, the CD stops playing but when I answer nothing is heard from the car speakers but only from the phone (as davemazo said also).
- when I receive a call, I hear in the car speakers a "standard" calling tone, not the ringtone I have assigned for that contact
I have to mention that with any Nokia I had before (and still have one as a second phone), these problems do not exist. I know there is a compatibility between Audi factory installed car-kits and Nokia, but BT is a standard and most of the functions should be supported despite the phone model/type. I've tried also with an iPhone and it's working great, as my Nokia do. I don't understand why it is like this with the Diamond. In fact, I think it is not related to Diamond itself...it's doing like this with ANY Windows Mobile device I've tried in the past (Orange C600, Samsung I600).
Are there any solutions for this? A CAB, a new BT radio, a software, anything?... I don't want to buy a new BT car-kit and try with different models until I find something compatible
Thank you for any info/tip
Click to expand...
Click to collapse
Hi Rapier,
I also had a SPV C500, MDA Compact, Qtek 8500, Samsung I600, HTC Touch Dual and now the Diamond. The only one which gave me no troubles was the SPV C500, but I think that was because this phone didn't support phonebook synchronization and had no network identification/signal strength over bluetooth.
After the SPV C500 it went wrong. First I noticed that after a hard reset it worked for a few days. Later (about 2 years later ) I found out that it was because the call history was going to long to sync over bluetooth.
Then I found Jetware in which you can limit syncing to any number of items. They even had a fix for the connection to my carkit.
Unit now... it works like a charm... but keep my fingers crossed
I don't know if your carkit is a Audi UHV, but I saw that they had a fix for that too! You have to just install Jetware and then run the fix-file from your phone. Good luck!!
P.S. I am in no kind related to Jetware, I just found out that it worked for me.
Yes, I have an Audi UHV 6634. Thank you for the info, I'll try that and post the results here. Though, my car-kit is not the advanced one and I don't have to sync anything with it (contacts or something else). It's most working as a plain hands-free device, no extra functions...speaking of which, I've noticed that on the phone is detected as "hands-free"...why not "car-kit" as I know a car-kit has other functionality as well? This is the "standard" BT device for any audio enhancements (even if it is a car-kit not a BT headset), or I have to activate something to be recognized as car-kit?
Mauser.NET said:
Jetware? I have also limited the phonebook sync to max 5 entries to debug
Click to expand...
Click to collapse
my Honda system doesn`t read the sim I can only dial out via handsfree using contacts i`ve entered into the Honda system otherwise I either have to read the number to the system and it will ring out (most of the time anyway) or make the call on the phone (illegally obviously) cancel the call and then say "redial" and the system makes the call. So uless I`m misunderstanding this setting I don`t think it will help me.
I`ve searched the Jetware website and I couldn`t find a fix for my Honda
UPDATE: So...I've downloaded it, install it on my Diamond (including the extension file for Audi UHV) and...no change. Everything as before with both issues. Disappointed, I've uninstalled Jetware then...surprise. AFTER uninstall, I can now hear through my car's speakers the ID ringtone Maybe some BT settings were altered and remained like this after uninstall, but I don't know why it didn't work when Jetware WAS installed...strange.
Anyway, many thanks...at least half of the problems are now solved and this only by install/uninstall a program...that's cool. I must now find a way to make the car kit ring when I make a call, this is still an issue.
P.S. I've seen that Diamond support Headset and Handsfree profiles...and when connected to my car kit is set as Handsfree. I suppose this is better than Headset...but still no ring out tone.
Rapier said:
UPDATE: So...I've downloaded it, install it on my Diamond (including the extension file for Audi UHV) and...no change. Everything as before with both issues. Disappointed, I've uninstalled Jetware then...surprise. AFTER uninstall, I can now hear through my car's speakers the ID ringtone Maybe some BT settings were altered and remained like this after uninstall, but I don't know why it didn't work when Jetware WAS installed...strange.
Anyway, many thanks...at least half of the problems are now solved and this only by install/uninstall a program...that's cool. I must now find a way to make the car kit ring when I make a call, this is still an issue.
P.S. I've seen that Diamond support Headset and Handsfree profiles...and when connected to my car kit is set as Handsfree. I suppose this is better than Headset...but still no ring out tone.
Click to expand...
Click to collapse
No thanx! I'm glad I could help
Mauser.NET said:
Hi Rapier,
I also had a SPV C500, MDA Compact, Qtek 8500, Samsung I600, HTC Touch Dual and now the Diamond. The only one which gave me no troubles was the SPV C500, but I think that was because this phone didn't support phonebook synchronization and had no network identification/signal strength over bluetooth.
After the SPV C500 it went wrong. First I noticed that after a hard reset it worked for a few days. Later (about 2 years later ) I found out that it was because the call history was going to long to sync over bluetooth.
Then I found Jetware in which you can limit syncing to any number of items. They even had a fix for the connection to my carkit.
Unit now... it works like a charm... but keep my fingers crossed
I don't know if your carkit is a Audi UHV, but I saw that they had a fix for that too! You have to just install Jetware and then run the fix-file from your phone. Good luck!!
P.S. I am in no kind related to Jetware, I just found out that it worked for me.
Click to expand...
Click to collapse
Hello,
I have a Mercedes car kit and facing the same issue as you: everything works perfectly for a few days when hard-resetting my device, even with my 500+ contacts (they are loaded in less than a minute), but after a few days/weeks I can't get to have my call history or contacts displayed in less than half an hour!
Yesterday I thought I'd just hard reset my device because I had this problem again, but unfortunately it didn't work!
Guess what I have done differently this time: yes, I backed up and restored my call history, which I hadn't done the previous times! So I guess it is indeed related to the call history, but I can't test for now!
I have installed JetWare and limited the call history to 5 numbers, I'll try this tonight and I'll keep you informed...
Hello,
So I have tested this yesterday (installed Jetware and limited the call history to 5 numbers), and now it works FLAWLESSLY! I can browse through my 500 contacts instantaneously when I pair my phone with my Mercedes car kit.
So, in my case it was also clearly the CALL HISTORY that was causing problems... A BIG BIG thanks to Mauser for pointing out this!
I'm also having problem connecting my Diamond to my Volvo S80. All the other functions work except that I could not hear the other party through my car stereo and I also could not diconnect the call with my car end key.
I'll try the Jetware and I'll report back later. Thanks for the pointer.
turt said:
A BIG BIG thanks to Mauser for pointing out this!
Click to expand...
Click to collapse
No thanx! ... glad I could help
Hi
I have been trying to pair my N1 to my nissan altima 2008 bose bluetooth system but it wouldn't pair. I tried countless number Of times but it won't work.
Does anyone else have this problem?
I think I read in the Google Nexus One forum that there are issues with Nissan/Infiniti cars and the bluetooth of the Nexus one.
hmmm... I have got mine paired with Chinese all in one DVD/SATNAV/DTV unit... it works very well.. It even automatically switches on the unit when It detects a bluetooth signals from my paired Nexus One....
Well, Im guessing its something to do with compatibility with the Nissan Bose Unit. Because I also had a difficulty pairing my Previous G1, But ONLY after updating to Donut 1.6. It eventually connected but after many many tries.
I have beeen doing some googling about this and it seems that many users are having problems pairing with different cars with 1.6 and above.
Weees said:
Well, Im guessing its something to do with compatibility with the Nissan Bose Unit. Because I also had a difficulty pairing my Previous G1, But ONLY after updating to Donut 1.6. It eventually connected but after many many tries.
I have beeen doing some googling about this and it seems that many users are having problems pairing with different cars with 1.6 and above.
Click to expand...
Click to collapse
Well the other option you have is to change your car... and get a car which is compatible with Nexus One...
see here: http://code.google.com/p/android/is...ct&colspec=ID Type Status Owner Summary Stars
this issue is known to carry through android 2.0 and 2.1.
I have the 2010 Mazda 3 sport with the Bose package and it pairs fine.
jeffokada81 said:
I have the 2010 Mazda 3 sport with the Bose package and it pairs fine.
Click to expand...
Click to collapse
Yeah, I have the 2010 Mazda 3i touring and no problems either.
ID have a kenwood deck in my mazda and all works good. is there some kind of factory reset switch on your stereo, that's what I have to do t get new phones working on mine.
I have a Parrot Mki9100 and I have some problems...when I am on the car my Nexus One connect itslef with the Parrot, but it disconnect and try to reconnect many times. At the end it stops trying...
So every time I have to go to Settings->BT->Long press on Parrot device and click connect. After that it works...very annoing...
Hm... I have an '08 Infiniti G37 with the Bose system and it pairs and works just as well as it did with my G1. I would have assumed that Nissan is using the same or a similar unit for the audio system for most of their cars.
Mazda 6 gt-m 2009 here, BT carkit has no probs with the N1
Tried to pair it with the parrot in my gf's car, but same probs as described by other users. Seems it's the Parrot; my iphone had issues with it as well.
Ah well, i'd rather drive my car then hers, so good excuse to use mine
I dont get how they end up making things worse by upgrading rather than making things better !!! I mean according to : http://code.google.com/p/android/is...ct&colspec=ID Type Status Owner Summary Stars
This problem has been known since 1.6 and I can defenitly confirm that since It took me forever to pair my G1 previously. But with my N1 , it just never pairs, so they even made it worse. Such an important option, you would think Google would have fixed it in 2.0 but to drag it to 2.1. This is just messed up.
That is very frustrating.
@OP, someone mentioned changing your car to accommodate your nexus one, that sounds like a great idea, but if you can't get it to work you can always go with a bluetooth add on option.
At Volkswagen there were some phones that were not connecting with the manufacturer add on and customers were pissed because they paid over $400 for the option. Another thing just as bad is purchasing the unit and not being able to use the bluetooth steering wheel controls because of compatibility issues.
My conclusion is that there are too many products out there and sometimes they are just not compatible with each other. In this case it sucks that it was your car...or should I say your phone?
Well, the Nexus connects fine to my VW premium bluetooth (from 2005) but the cars system can not access the phonebook.
Not even the sim contacts which the HTC Hero could do.....
Google support suggested importing the sim contacts into the Nexus.
I wonder if they read the mails before they answer....
I've always found OEM bluetooth to be pretty uncompatible, and yet to see an update for one.
I've got a kenwood unit, which works with my steering controls, connects handsfree and audio when I turn on my ignition, and it syncs the phone book fine, showing the callers name when the phone rings. (it cost £80....) and I updated it (it's a parrot bluetooth unit in there) from my laptop via bletooth.
The N1 works best of all the phones I've had (6 htc's in 3 years) with it.
I never had an issue with my old g1...until I flashed a 2.0 ROM. Everything pairs fine, music player worked, stereo would switch over, but no sound came from speakers on phone calls. Now my nexus is the same way. I've asked Cyanogen if he would be kind enought to look into it and hopefully he will.
My N1 (locked bootloader, not rooted) routes the audio just fine, did it work before you cyanogened it?
ck3100
Wel I tried to connect my N1 to the parrot ck3100. it will see it fine, but the moment I try to link it it says paring failed. Anybody had any better luck with the ck3100 and N1?
mgymnop said:
Yeah, I have the 2010 Mazda 3i touring and no problems either.
Click to expand...
Click to collapse
I've got a 2010 Mazda 3 sport - it pairs/plays fine etc with my Nexus, but the person on the other end of the line always complains that I sound *really* quiet. I never had that problem with my G1. Do you get any complaints?