hi guys,
I'm having some problems from time to time with the conecction between my p3300 Artemis Vanilla ROM 1.0. and the parrot 3200LS.
the problem is that when I turn on the car and the bt connection is set automatically the parrot appeas as if I was in a call.
if I finish the call still the p3300 and the parrot are linked becuase I cannot reproduce the radio or the CD's ("phone" appears in the display of the car).
if I turn off and on the car, when the bt connection is set again happend the same.
The problem is solved only if I make a soft-reset, so the problem is in the pda and I never had this before with WM5.
any idea?
thanks
kkfuti said:
hi guys,
I'm having some problems from time to time with the conecction between my p3300 Artemis Vanilla ROM 1.0. and the parrot 3200LS.
the problem is that when I turn on the car and the bt connection is set automatically the parrot appeas as if I was in a call.
if I finish the call still the p3300 and the parrot are linked becuase I cannot reproduce the radio or the CD's ("phone" appears in the display of the car).
if I turn off and on the car, when the bt connection is set again happend the same.
The problem is solved only if I make a soft-reset, so the problem is in the pda and I never had this before with WM5.
any idea?
thanks
Click to expand...
Click to collapse
I had a similar problem earlier this week with my Parrot CK3000. But the problem only happened after I tried to download and use MS Voice Commander software. I tried to uninstall and go back to default Speed Dial but it wouldn't work correctly anymore with the Parrot kit or my headset. The software changed my registry settings - couldn't figure out how to fix it, so I had to hard reset.
But, right after a ROM upgrades and hard resets, I get the "phone" condition you described. It's like, the BT channel is just open, waiting for a command. The way to fix it is just to make a phone call and then hang up using the Parrots "end call" button. Then everything goes back to normal and this does not happen again. I only get this if I hard reset or ROM upgrade. Try it.
I was fine with official asia 3.7
I was fine with Vanilla 1.0
Had the problem with Official Europe
Just installed Vanilla 2.0 and we will see how it goes.
Related
As everybody know, its quite annoying use Universal as mobile. then, i decided to start to use the Bluetooth headset!
But doesn't work all the time.
If i set one headset, it works fine for few hours, then, after a while, without any message, bluetooth in my Universal turns off it self!!
At begin i though that would be my headset, then i tested with my other headset, and is the same!
Beside that, when i try to pair it them once more, it has static on it.
So, to be able to use it again, i need to:
- Remove device in my bluetooth list
- restart headset
- Search for device once more
And then, it works for a while again.
Well, i have tested in two headset over here, The Dopod H1 and Targus.
Does anybody knows what is going on or had same problem?
Thanks in advance!
Same here
I have experienced the same problem with my JasJar. The bluetooth radio seems to turn itself off from time to time. I think it is somehow related to WM2005, because I had the same issue with a Himalaya running WM2005. What is weird is that the blue light continues to blink. If you go to the wireless manager applet, it sometimes shows the bluetooth as on and sometimes as off, but if you go to the bluetooth setting, it shows the radio as off.
Any suggestions?
TIA
Panabax
Buzz_lightyear may have the solution here: http://www.buzzdev.net/index.php?option=com_content&task=view&id=60&Itemid=41
I'm trying this at present. BT stayed on overnight, despite very low battery, and I'll put it into use all of today. If I go a full day without losing BT then it's solved for me cos I was losing it ALL the time 2 days ago.
Hmm, I had a better day with this reg hack - but I did lose BT once. SO, inconclusive at present.
Guys - I have searched the whole internet and can confirm that there is a problem with the ROM
Until it is fixed Bluetooth will not work as it should
This is a problem i had with original jasjar rom (september 2005). First official upgrade and all subsequent roms have solved this problem. I'm actualy using helmi's aky 3.5 1.3.1 and sony hbh660 dayly without any problem.
Hi,
I had an old ROM release on my Qtek 9090 and with it my GPS Bluetooth device worked fine.
Yesterday I got myself a Parrot EasyDrive and it would not connect to my Qtek 9090. It would however work fine with my 2 Nokias.
So I decided to finally (after one year) upgrade my Qtek and I used the 1.42 ROM from this site.
No the Parrot EasyDrive works fine, but my GPS receiver has this annoying problem: whenever I want to use the GPS receiver, the pairing window opens up, asking for the passkey (1234). The problem is, that it won't keep it, no matter what I do.
I tried to remove the GPS-Device in the Bluetooth manager and I deleted the pairing partnership. Then I made a new connection with pairing, etc.
After turning Bluetooth off, the pairing information is lost.
Meanwhile, the Parrot Easy Drive carkit works fine.
Any suggestions?
Cheers,
vma
Well, I ended up solving the problem myself...
While messing with the registry to remove the operator branded dialpad of the new ROM I installed, I managed to mess up my Qtek 9090 and lost the screen alignment. Because of that, I could not access the lower part of the screen anymore, thus it became impossible to realign the screen.
As stupid as it might seem, I had to do a hardreset at end, otherwise the device was useless (Side-question: is there any shortcut to get the screen alignment for the Blue Angel?).
After doing the hardreset and after re-installing all applications again, I paired both the carkit and the GPS receiver without problems.
It seems that if the pairing goes wrong the first time, one has problems afterwards. Would be nice to know how to really reset all connections without having to do a hardreset.
For all of you that went through the pain of reading my two posts:
I purchased an Parrot EasyDrive carkit, which was on sale for 35 Euro. It is a device that plugs into the carlighter and that has voice recognition.
I then passed new cables for Ground and 12V from the lighter to under the steering wheel and attached them to the speaker part of the carkit.
The result is a proper Bluetooth carkit with voice recognition (you say "telephone" and then the name and the carkit dials the number on the phone - all contacts have to be send one by one from the phone's contact list through Bluetooth and then you train the name twice - memory holds 200 contacts), where you just see the little knob with the two buttons - for just 35 Euro!
I say, that's an excellent deal!
Cheers,
vma
hi.
i just bought a motorola bluetooth handsfree for my car HB830. i paired it to my exec and it started working. now the problem is that sometimes the pairing fails and the phone doesnt transfer the call to the handsfree i.e the call remains in the phone. when this happens the exec shows that bluetooth is turned off which i switch back on but the problem comes back after the next call. i.e the phone doesnt seem to be able to transfer the call to the handsfree.i have upgrade my ROM to Rom:1.30.107 WWE
Radio: 1.09.00
Ext ROM: 1.30.162 WWE
is this a problem with the new radio ? should i downgrade to the older radio? if yes then which one and how do i? please help me guys.. thanx
My Uni does the same with my parrot CK3100 car kit...
Its a major pain in the ass....
Seems to work fine with my Jabra JX10 tho..
:roll:
Same problem here with a medion bluetooth car radio.
Most of the times my universal thinks it's paired (icon in the calling screen), but when making or receiving a call it disappears.
After a succesfull bluetooth call, it isn't posible anymore to call handsfree.
Bluetooth also regulary turns itself off. Tricks found in another topic are not the solution for me
if you enable the device lock start\settings\personal\lock
Prompt if device is unused for 16.7 hours
set simple pin
the phone and the parrot device keep there pairing with no problem at all i have been testing it for the last 48 hours
if you disable the above it loses the paring straght the way.
strange is they anyone else who can try this
Thanks
Paul
bluetooth headest problem
hi.
1st thing how do u set it for 16.7 hrs.... it just gives me options of rounded off hours.
i tried setting it for 12 hrs.. it works better but still a problem
Maybe this is a clue:
I use the newest Qtek German Rom, which is from April or May. This should be same version like WWE version.
Since I upgraded to this Rom, all my problems with Bluetooth disappeared. It works fine with my Logitech mobile pro 2 headset. I assume, the problems are only because of the rom.
try upgrading and see, how it works.
Yesterdaty I updated to WM6.5 and now try to get everything working again. Somehow my TP2 won't pair with my bluetooth carkit anymore. With WM6.1 this was no problem. The phone still pairs perfectly with my computer (also bluetooth connection) so I think the bluetooth connection is ok.
When parining to my carkit it finds the device, then I have to enter a password on the TP2, and after that it just sais "pairing connection failed", and it will not work. I am sure the password is not changed since yesterday. I tried it several times. I do not know what to do anymore. Could this be a setting somewhere? I get the feeling my password is not send properly but have no idea.
Meanwhile I tried pairing my carkit with another phone and no problems there. So my conclusion is: something has changed with bluetooth, updating to WM6.5 which makes it now impossible to pair my TP2 with my carkit.
Is there maybe a programm for the TP2 which give me more controll over bluetooth (like maybe go to an older standard)?
I have exactly the same problem as you
good to hear I am not the only one. Hope someone will come up with a solution for this.
I did nor observed any issues when pairing my TP2 after reflashing to WM6.5
There is another issue however - I can not hear any voice until it is charging.
Unplugging of the charger fixes this issue immediately. Horrible...
Seems, HTC guys are saving money on testing by using us as Beta Customers.
Would a custom ROM be a solution for us?
I updated to the "energy 6.5.1 rom" and guess what..............
The same problem. The rom is very nice, but my TP2 still won't pair with my BT carkit which is very big problem for me.
Is there maybe a way to downgrade just the BT part of a rom to WM6.1. I read on different forums there is something that is called a BT stack. Could this be the problem?
I have a ton of problems with bluetooth pairing now. However, I don't know whether it's the fault of 6.5 or the Tilt 2. Here is what I am experiencing...
- On car deck or headphones, the skip buttons don't do anything
- on car deck or headphones, I have to disconnect Stereo Audio and then reconnect to actually get sound. It NEVER works when it auto connects.
- Music will do a brief skip when you shut the screen off
- Stupid message about volume control every time it connects (resolved by switching to custom rom)
- SMS or any kind of alert tone now turns music way down so that the tone is the only thing you hear. Which is super awesome when I'm driving my drunk friends around and they are singing along to a song when suddenly it mutes so everyone can hear my incoming text message.
Not a single one of these issues existed when I had my Fuze.
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
orb3000 said:
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
Click to expand...
Click to collapse
No I do not think so, because I used the official WM6.5 with the same problem. Does someone know a way around this issue. I strongly believe that if only I could pair I have some options to work with it (in 6.1 it worked like a charm). If I only could pair without having to send the passkey it would be great step forward. I presume with sending the passkey, the bluetooth of the TP2 sends out other "rubbish" that confuses my carkit.
My problem is solved and guess what, it had nothing to do with my TP2. The problem was my carkit. It has a maximum number of bluetooth devices (5) it can pair to and the last one (the WM6.1 version of my phone) had been reached. So a hard reset on the bluetooth carkit and the problem was solved.
Well, at least I now know how to flash a rom to my phone and I think I learned more about the phone reading through all the forums. Thanks all for thinking with me on this problem!
Does anyone else still have this problem?? I have removed all the devices from my car and continue to have the same pairing error just after entering the passcode. Stock Spint ROM worked great, but multiple 6.5 upgrades don"t pair..............suggestions/ideas??????
bluetooth settings, advanced, enable beam data exchange,check the box
Interesting.....I actually found a fix. Instead of pairing the phone with the car, I paired the car with the phone. I didn't even know that this was possible, but it did the trick!
All of a sudden when I try to start BT or use a BT device I get an error saying BT can not be started because the BT stack could not start. If I soft reset I can then start BT without issue. I decided to just leave BT on over the weekend since I was driving and it connects to my car stereo automatically when on. This morning, I go to sync using BT and the icon is in the tray, but I get the BT can't connect error. Soft reset and works fine. What could be causing this?
Is this with the stock rom or a custom one?
I have also experienced this, but I build/flash custom roms so often, I never bother to track down or even research the issue.
Best regards,
-boggsie
In my sig, OEM AT$T ROM.
OK, I think I have found the problem. I have CleanRAM scheduled to run every morning at 7:45 so that my Tilt 2 starts the day fresh. It is configured to run a Level 2 cleaning. Apparently, this is causing some process to be shut down relative to the Bluetooth stack that then causes the error when trying to use Bluetooth. It doesn't shut down BT completely, so the Taskbar icon remains. I'll either have to drop CleanRAM down to Level 1 or just do a soft reset every morning to re-establish BT. I wonder if the developer of CleanRAM is aware of this issue?