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?
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 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.
Sorry if I'm posting a question that's been answerred before, but I haven't been able to find a thread to this problem:
sometimes my Nokia BH-102 will disconnect in the middle of a conversation in the car. The only option at that time is to pull the TP2 from it's holder and put it to my ear.
Whether it's the headset or the phone, I don't know, but it used to work in combo with the old Nokia E60 I used to operate......
Chances are it's the TP2, but how to fix it?
Only 'tweak' was to install tomtom, but without the 2 dll's which have been causing some problems.
Has anybody experienced anything similar?
Bluetooth visor problem
I have had problems with my headset - Supertooth Visor One Bluetooth Car Kit. Not quite the same as you though - the problems I have is that when I make an outgoing call, everything works fine but when I recieve an incoming call the audio stays on the handset rather than coming out of the bluetooth headset - which means I have to pick up the phone. I also have installed TomTom 7 and I had to do the 2 dll fix as my bluetooth was completely broken otherwise. So I guess maybe TT7 is responsible in some way. Only thing is, I dont want to do a hard reset to find out!!
I'd already read about the Tomtom BT-issue so I cleared the 2 dll's out of the cab prior to installation.
So the originals should still be in use. BT is/was working and I have been synching using BT. That's not the problem.
There should be threads out here pointing you to the original dll's. you could past them over the current ones and see if it helps.
I experiencing the same problem, and didn´t install tomtom.
So now it looks like it's a problem in the TP2 then.
Hopefully a BT-guru can investigate? This is way beyond my capabilities.
In the meantime I'll know what to do if and when it happens: take a chance on the cops seeing it and issuing a ticket.....
I'm having a similar issue, my headsets plural, have this problem. It will disconnect but what is happening is the headset is shutting down. If I hold the power button on the headset it comes back on and will work again.
If it was one headset I would think it is faulty but I've had this problem with three headsets and the Bluetooth in my car.
Is it possible that the phone is sending a shutdown command? BTW I am using the stock TMOUS 6,5 ROM and have tried some of the cooked ROMS with the same effect.
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!
Hello guys,
I just got a Sony bluetooth headset and I am trying to use it with my HTC TYTN II. At first I paired the phone and the headset and I was able to listen to music and talk through the headset, all perfect. When I was listening to music, the bluetooth icon on my phone represented a music note and a headset over it.
When I turn the headset off once and then on again, it connects automatically with the phone but in some other mode. The bluetooth icon now represents the bluetooth sign with a headset over it. Now when I listen to some music, it comes from the speaker of the phone, not from the bluetooth headset. Talking through it is not a problem.
If I pair the phone and the headset again, it works just fine (showing again the music note) but once I turn the headset off and on again, I lose the music mode.
Does anyone know how to fix that? Thanks in advance.
I fixed the issue by installing AutoA2DP (found in this forum).
I've had a similar problem on my Tilt. I originally posted the following on the ROM thread. Since then, I have found that the AutoA2DP has not fixed the problem. I still have this issue about 70% of the time, and sometimes I can't get the bluetooth to work at all, not even after a soft reset. Sometimes it seems as if the bluetooth has no power, the phone can't communicate with the headset except when within a few inches of one another. Then it magically seems to resolve itself. Anyway here's my original post from the ROM thread.
The other day I installed an app on my phone called Schaps Network Plugin, which allows you to map network drives to the phone the same way you can do with a desktop. It allows me to access the home network directly via my wifi. It was something I needed and it seemed to work great, for a day. The next day my bluetooth headset would not connect. Long story only slightly shorter, it seems the problem was with the headset connecting via A2DP and doing so automatically. This always worked just fine in the past. Suddenly it wouldn't work. I tried a ton of things including a "fresh" install of everything and formatting my memory card to start with nothing on it. I flashed the original rom and then flashed this rom. I did hard resets each time. Did this twice. Even tried the bluetooth in the oem rom to see if I still got the problem. I did, and it is still with me. I can manually get the headset to connect via A2DP using the bluetooth settings, though even then it may take reconnecting several times to get it to work. However, when I turn the headset off and then on again, the A2DP does not reconnect, just the hands free. But the sound is not routed through the phone's speaker either, at that point. In fact you often get no sound at all, nothing via the headset or the speaker. OTOH, if you activate Voice Command, the headset does work while Voice command is running. After it shuts off, you are back to no sound. It seems as if the hands free works fine, but the audio gets partly routed to A2DP but does not connect to the headset. If I reset the phone, the headset connects correctly and efverything works until I turn the headset off again. Also if I pair the headset again, everything works correctly until I turn the headset off. Though pairing is not as trouble free as it used to be either. Sometimes it will not pair up wihtout repeated attempts. I did find this program, AutoA2DP which has patched the problem. It detects when a paired bluetooth device connects, and forces a connection via A2DP as well. But I never had this issue in the past, and my wife's phone still has no problem. I am not sure the Schaps Network plugin had anything to do with it, other than the timing. Seems odd to me that the bluetooth stack would suddenly develop issues that persist even after two fresh flashes of the rom. Any ideas, suggesitons, etc.? This is really bugging me, and although the patch seems to be working, the phone is still not acting "right." In the past, and on my wife's phone, if a bluetooth headset is turned on, it automatically connects, and all sounds, including the system sounds, are routed through the headset. Now, sometimes they are, and sometimes they aren't.