bluetooth hell - MDA III, XDA III, PDA2k, 9090 General

i just upgraded to the bt 1.00 3900... coz i thought it would help me with my problem of turning on the bluetooth and always getting the "cannot turn bluetooth on coz of insufficient memory" or something to that effect but it seems upgrading didnt solve that problem. i really dont understand what the problem is.why wont it turn on when i really dont have many applications running along with it just wisbar and pocket plus.i use bluetooth mainly to sync my xda to a pc and its getting really frustrating having to reset all the time in order to activesync it.connecting to the cradle is not really a very attractive option to me coz i use the brando hard plastic and leather case which will necessitate for me to take it out of the case every time i want to connect to the pc.whats with this cannot turn on bluetooth thing?how do i solve it?

what programs have you installed?
Is Voice Command in the list?
There are a few other programs that use the same memory space as the bluetooth stack, and will not allow bluetooth to run...

Related

Need bluetooth help badly!~

Please help me out I'm incredibly frustrated with this thing. I recently got the PDA2k and installed WM05 on it. It looks very nice and it runs speedy with no problems. My problem is the bluetooth which is huge thing to me. Either my headset (Tekkeon Eztalker Mini) is not compatible which I doubt or I'm making a stupid mistake.
This is what I did step by step: I click on the bluetooth icon and turn on the bluetooth, I then put my headset in pairing mode and the imate is able to recognize it and I enter the Pw and I put Set as handsfree. That's it, I would think I would be done at this point yet nothing happens, the headset doesn't do anything and I know its not Tekkeons fault because I was able to hook it up easily with my HP 6315.
So what's going what am I missing?
Also theres a tab at the bottom called "Com Ports" but I only see under this option "Incoming Port", and the description at the top says there should be another option called "New outgoing port". Does this have anything to do with it?
What Am i doing wrong? It's driving me crazy I can't really use the phone without the headset.
help me out pls
Bluetooth
I know the feeling, i have gone back to 2003 cause of that but now i am back on wm5. The bluetooth issue is not fixed yet, it is not stable, it keeps going off. There is a suspend cab file, but it does not work for me yet, also try pokect zen beta. You might get a longer period of bluetooth
thanks for responding, but the problem is not that it suspends or stops working. It doesn't start working at all even though the imate detects it. It's like it's not connected at all, not that it disconnects. I'm doing something wrong I just don't know what.
The bluetooth piece is not faulty and the unit is practically brand new. whats going on?
I used "Display Switch" binded button (From Wisbar Advance 2) or "Toggle Screen" (From SPB Pocket Plus) to turn off the backlight instead of using power button .
This work around will keep bt connection alive.
Note:
1. If you suspend your BA using psShutXP your bt connection .
2. You have to disable auto turn off device under Start -> Setting -> Power
Note:
1. If you suspend your BA using psShutXP your bt connection will be disconnected.
I'm sorry I'm not sure I'm explaining myself correctly. I understand that if the power goes off I will lose the BT connection but the problem is not KEEPING the connection alive, the problem is MAKING the connection. I follow all the steps , the imate recognized the headset but I'm not able to use it..also shouldn't a headset picture show up at the top of the screen when the bt headset is connected (cuz mine doesnt). what am i doing wrong?
thanks.
still need help please.. if someone can walk me through how to setup a bluetooth connection that would be great cuz I apparently haven't done it right.
The headset icon only shows in Phone app
The headset icon only shows up in the Phone application. It no longer is displayed in the notification area (top row).
If your device is paired up, when you make a call, you will see the headset icon in the top right corner.
You may also need to clear any old pairings that you headset has. I have a Jabra 250 and it happens all the time.
there we go you have solved my problem!. I didnt' have to open up the phone application on my hp 6315 to use the bt. So wait can I listen to music with windows media player through the bt headset or does it only work when making phone calls? I was able to listen to music on the HP 6315, is it different with the Imate or is it the NEW 05 os? Please enlighten me
thank you thank you
also one other thing does this mean that if i want to use the headset with the phone that I have to press the answer button on the imate rather than the headset..cuz that would suck big time.
what about when people call me can i answer with the answer button of the bt headset or no?
It works fine with the headset button for answering or hanging up.
Later.......... 8)
droy001 said:
what about when people call me can i answer with the answer button of the bt headset or no?
Click to expand...
Click to collapse

stereo bt but mono sound

iam currently using latest rom from dopod and motorola 820, although the two earpiece have sounds it is only mono, can someone help to make it stereo? o recomend what rom to use, thanks
In order to have stereo audio on a Bluetooth device, you need a profile called A2DP, which is currently only supported by the latest Qtek Universal ROM at the moment:
ftp://xda:[email protected]_Updates/UNI_QTEK_13077_176_10900_WWE.exe
Dopod has not released a ROM supporting A2DP yet.
thanks for the help, God bless
No problem. Do let us know whether it works well or not.
it works, i have stereo sound, but need improvements, in a song the bluetoth stops 3 to 4 times when playing, the player dont stop its the motorola 820 that stops several times.
I did come across a post with a patch for the A2DP flaw the other day. It's somewhere on this site - do a search and see if you're lucky.
Found it: http://forum.xda-developers.com/viewtopic.php?t=46811&highlight=universal+a2dp
It worked for me for a little while so try it.
Hi,
I have used A2DP a lot with my JasJar the last 4-5 months, and had written a summary of my experiences with this "lag/stuttering"-issue in another thread here...I have copied the most essential of that text below...might be usefull info for you;
-----------------------------------------------------------------------------------
It seems to be two major factors affecting this "stuttering"/"lag" (from my experiences at least...I have used A2DP a lot with my Universal...couple of hours every day);
1. Universal struggling outputting(RAM/CPU...or both!?)
One help here is to apply the registry "A2DP priority" fix (found it in the forums here...and so did richardlai).
Another is to close all programs before using it (I usually do not do this...I usually only do it in hindsight when I get the problem).
2. Signal between Universal and headset struggling (obstructions between Universal and headset, WiFi nearby, so forth)
I for example get this problem if I put my Universal in my trouser pocket (I know, I must have big pockets, and walk around, I get stuttering/lag occationally. If I then take it out, and hold it in my hand farily still when I walk...no stuttering. I have found, that when I walk, it is Ok to have it in my backpack/rugsack...then for some reason it very rearly stutters...so I usually do that.
But when I walk of the bus at work, and walk into the "campus" of my workplace, which is cramped with radiotransmitters (is norways largest Telecom company)...I get a lot of stuttering, and need to take it out of backpack, and hold it in my hand, at it gets a lot better.
In short: A2DP with the Universal works, but is sensitive to disturbance/obstructions/moving around...and to make it worse, it is also sometimes dependant of the Universal itself struggling with CPU/RAM. So you can not totally get rid of the problem...but you can do a lot to minimize it...I almost never experience it now...except in the campus-area at work that is.
I have BTW had the exact same problems before with Qtek 2020 and Qtek9090 (which I got hold of some "A2DP patches", when I had those devices). ...but I really had a LOT more stuttering with those two...so much so, that I never used A2DP with them on a daily basis.
-----------------------------------------------------------------------------------
I also wrote a short post on my experiences with the different stereo headsets I have...yes, they actually act a little bit different it seems (regarding resume/pause button, and how easy/automatic they "reconnect"). You can see it here; http://forum.xda-developers.com/viewtopic.php?t=47977
Hope this is of some help for you!
RonnyGydar: I came across your little summary a little while ago and have done the registry fix, but the problem still exists! Do you think altering the value in some way would help?
richardlai,
I added the registry value manually...found a reg-file (or was it a CAB-file!?) that supposedly should add it...but when I checked later the key was still not added in the registry?
So I added it manually.
BUT, I do still have the problem...but that seems to be radio interference/distance so forth...since when I hold JasJar in my hand and don't move it around, I NEVER have an problem. ...and actually fairly rearly when I have it in my rugsack/backpack.
With 1 or 2 exceptions...where it lagged "all the time"...but then a soft-reset cured it.
So if you have this problem with your phone lying in front of you on the table...then it really sounds like it is the JasJar/Universal that IS the cause (and not interference)...and yes then the registry hack should help.
BUT I have not done any real testing of the effect of it...I am not sure how much effect it really has...all I know is that I had a "lot of problems" with lag before...and now I almost never have it.
...I hate those "diffuse" problems...when it is impossible to measure in a "scientific" way that "this cures it", and "this do not"! :-(
Sorry about the "little help" I give here...but this issue is a bit "fuzzy"...I have gotten it enough under control to that it isn't a problem any more (during a 1 hour workout, I will typically get this gap/lag 0-2 times...and that is not a problem for me...at least compared to what I experienced 6 months ago, where I was lucky if I could hear 10 seconds without any problems).
The stuttering problem seems to be permanent now... Luckily I have a HP hx4700 (which has a Broadcom bluetooth module) and works perfectly with my Jabra HT620s. Anyone using an A2DP ROM other than Qtek? I'd like to try a different ROM to see if it would make a difference.
only a second of sound
i use the qstarz bt stereo headset (http://www.qstarz.com/products/bh-q392s.aspx) and it works fine for phonecalls, but when i set it for wireless stereo and start a media player (TCPMP, WMP, Pocket Player...) i mostly only get sound for one second and then it shuts up. the players keep playing, the buttons on the headset can pause, resume and change tracks but there is no sound at all.
i get full wireless stereo playback occasionally, but i can't figure out what differs from time to time.
i applied the above patch with no success. anyone has a thought on the matter?
Ariel.
richardlai said:
The stuttering problem seems to be permanent now... Luckily I have a HP hx4700 (which has a Broadcom bluetooth module) and works perfectly with my Jabra HT620s. Anyone using an A2DP ROM other than Qtek? I'd like to try a different ROM to see if it would make a difference.
Click to expand...
Click to collapse
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
edit:
I use the latest OFFICIAL Qtek 9000 WWE ROM. (Without the ExtROM though ) And i did not use any patches regarding A2DP or Bluetooth.
this is what i tried, many times. i get the activesync sound, sometimes from the speakers, sometimes in the headset, but almost always only one second of sound afterwards.
i found that by pairing the headset to the universal by pressing and holding the green button on the headset untill the universal recognises (doesn't take long) gives better results.
pairing it by the instructions of the headset (putting it in discover mode, and then searching for a device with the universal) will give me the one second sound almost every time.
Biffert said:
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
Click to expand...
Click to collapse
Well, this has ALWAYS been the sequence I use (and I don't think you can do it in any other way). The real problem here is either the buffer memory or processor load.
richardlai said:
Biffert said:
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
Click to expand...
Click to collapse
Well, this has ALWAYS been the sequence I use (and I don't think you can do it in any other way). The real problem here is either the buffer memory or processor load.
Click to expand...
Click to collapse
Then there is no A2DP problem, the only solution is to lower the overal systemload. Stop all programs you have running, disable every today plugin that need frequent updating (memory, battery meters etc.) Free up as much RAM as you possibly can. I have AT LEAST 16 mb RAM free when playing music via BT.

Bluetooth headgear disconnect mid-call

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.

Dueling Bluetooths

I have a 2005 Acura with bluetooth phone. My girlfriend and I both have pairing to it, she has an old Sprint A920, I have a Tmobile TP2. If we get into the car around the same time, her phone always wins! Of course the ideal solution would be if the car had a function to prioritize who gets bluetooth (if it connects hers, then sees mine, to disconnect hers and connect mine), but alas, nothing like that. I assume the car is polling for a bluetooth and picks the first one it finds. It doesn't seem related to who it paired last, or who made a call last, and we tried unpairing both then pairing mine first or hers first.
So, other than her turning off bluetooth (a pain on her phone) whenever we get back to the car, is there any solution to get it to like me more? Is the problem in the speed the TP2 connects? Any way to speed that up with the stock ROM.
And while I'm here anyway, many thanks to all the amazing people in the XDA community.
greatbrit said:
I have a 2005 Acura with bluetooth phone. My girlfriend and I both have pairing to it, she has an old Sprint A920, I have a Tmobile TP2. If we get into the car around the same time, her phone always wins! Of course the ideal solution would be if the car had a function to prioritize who gets bluetooth (if it connects hers, then sees mine, to disconnect hers and connect mine), but alas, nothing like that. I assume the car is polling for a bluetooth and picks the first one it finds. It doesn't seem related to who it paired last, or who made a call last, and we tried unpairing both then pairing mine first or hers first.
So, other than her turning off bluetooth (a pain on her phone) whenever we get back to the car, is there any solution to get it to like me more? Is the problem in the speed the TP2 connects? Any way to speed that up with the stock ROM.
And while I'm here anyway, many thanks to all the amazing people in the XDA community.
Click to expand...
Click to collapse
I've found that my Windows Mobile devices are slower to pair with Bluetooth headsets/car kits than the older dumbphones I've had (mostly Motorolas).
A partial solution to the problem with the Acura HandsFreeLink, if it pairs to her phone first, is to press the HFL button on the steering wheel and say "Next Phone". It will unlink her phone and link to your phone. That way you can keep both phones paired to the car if needed and still use your phone if the car happens to link with hers first.
dwboston said:
I've found that my Windows Mobile devices are slower to pair with Bluetooth headsets/car kits than the older dumbphones I've had (mostly Motorolas).
A partial solution to the problem with the Acura HandsFreeLink, if it pairs to her phone first, is to press the HFL button on the steering wheel and say "Next Phone". It will unlink her phone and link to your phone. That way you can keep both phones paired to the car if needed and still use your phone if the car happens to link with hers first.
Click to expand...
Click to collapse
Awesome solution, TYVM! Funny, I think I remember help telling me that command but never thought that was what it did Now I just have to find a way to say 'next phone' without my g/f hearing me

bluetooth paring problems WM6.5

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!

Categories

Resources