Database Users

Bluetooth Shuts Itself Off

I have experienced a strange problem with my JasJar bluetooth radio. 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 (thanks to Buzz). 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. Turning it on, with the applet, or in the bluetooth settings, is only sometimes successful in actually getting it working again. Ressetting the device works every time. No need to re-pair.
Any suggestions?
TIA
Panabax

INFURIATING!!!
Makes device useless as a phone. I am missing call after call!
I tried buzz's reg power hack, but I got dropped again this morning. my current hypotheses are based on the few things that happened btwn ok & bad today:
- may happen after an alarm
- may happen when charged
- may have been caused by a missed call
we need 2 elevate this. it is a SERIOUS flaw. have tried 3 BT devices - all the same!

craigiecraigie4 said:
INFURIATING!!!
Makes device useless as a phone. I am missing call after call!
I tried buzz's reg power hack, but I got dropped again this morning. my current hypotheses are based on the few things that happened btwn ok & bad today:
- may happen after an alarm
- may happen when charged
- may have been caused by a missed call
we need 2 elevate this. it is a SERIOUS flaw. have tried 3 BT devices - all the same!
Click to expand...
Click to collapse
This is what happens if you buy a "beta" product for tons of money. Next time be more clever and buy later, when the operating software is near to final. And btw HTC sucks 'coz they are selling / producing a non-final product.

Edit: i've made a mistake in the registry... found by ekapco. THANX.
uploaded new cab below...
buzz

Buzz, you're a legend!
Trying it right now, will report back tomorrow.
Can u not help us on all our other problems (http://forum.xda-developers.com/viewtopic.php?t=28343)? Your posts on Buzzdev.net indicate that you're far more technically savvy than most ppl here.

Tried headsetfix on my BA still no go
BT is stopped after 3-5 min.

ekapco said:
Tried headsetfix on my BA still no go
BT is stopped after 3-5 min.
Click to expand...
Click to collapse
BlueAngel? I think, this is a Universal fix.

BlueAngel? I think, this is a Universal fix
Click to expand...
Click to collapse
So ????
Registry is almost the same on this issue.

ekapco said:
In your headset fix shouldn't reg setting be hds1: instead of hds1 ?
Click to expand...
Click to collapse
of course... i'm so stupid... sorry...
should be hds1:
THANX ekapco...
buzz

ThExSenatoR said:
This is what happens if you buy a "beta" product for tons of money. Next time be more clever and buy later, when the operating software is near to final. And btw HTC sucks 'coz they are selling / producing a non-final product.
Click to expand...
Click to collapse
WOW!
That was a helpful post. Thanks.
Buzz; can you explain what your fix actually does? I don't have a cab extractor here to look at the contents.

fix sets hds1: = dword:0 for 'unattended' system power state.
hds1: is headset device identifier.
bkl1: is backlight
wav1: is wave device
dsk1: is block/disk device
etc...
let's have some fun with those power settings...
open your regeditor and change
[HKLM/system/currentcontrolset/control/power/state/on]
"bkl1:"=dword:4
and
[HKLM/system/currentcontrolset/control/power/state/backlightoff]
"bkl1:"=dword:0
after changing the regs, press power button to off and on again. that will flush and apply new settings.
ok. the above settings will REVERT backlight's behaviour. I mean, when device is on, backlight is off. after inactivity timeout, light goes on.
well... funny experiment...
that proves, that devices could be powermanaged from here.
if you've had enough fun, revert those settings to normal. ;o)))
now set in:
[HKLM/system/currentcontrolset/control/power/state/unattended]
"bkl1:"=dword:0
that SHOULD turn the backlight on, when you leave the device untouched for a longer time (when the display goes off) or if you press the power button.
so leave it untouched and watch the display to see what's gonna happen on the 'unattended' state.
after approx. 5 minutes (never measure that), just when the display is about to off itself, BACKLIGHT FLASHES for a second and goes OFF.
why? we just said, bkl1:=0 (ON)?
so our settings are overriden. maybe that 'flags' settings?
lets see later, but exactly the same happens with BT connection even if we say ON, it goes off...
I have to sleep now in 'unattented' state, but meanwhile you can look at msdn, coz I saw those flags description there.
good night
buz

Hi,
your tricks are very helpfull. The Bluetooth keeps on now on my device. Can you do the same to the wifi connection?

EyeOfTheStorm said:
Hi,
your tricks are very helpfull. The Bluetooth keeps on now on my device. Can you do the same to the wifi connection?
Click to expand...
Click to collapse
Please follow my last post here or you have to tell me your wifi device handle.

I try to find the device ID
In "HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Power/Interfaces" i fount this 4 IDs
{8DD679CE-8AB4-43c8-A14A-EA4963FAA715} Power-manageable block devices
{98C5250D-C29A-4985-AE5F-AFE5367E5006} Power-manageable NDIS miniports
{A32942B7-920C-486b-B0E6-92A702A99B35} Generic power-manageable devices
{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1} Power-manageable display
Does this help? Or am I wrong?

O Hell! Your hack seems to have kept it alive overnight, and I truly thought it was solved. But today I'm finding that the BT problems go way deeper than sleeping (nothing to do ur hack):
- In the middle of a call, with my phone within 2 feet of me at all times and both devices fully charged, it disconnected BT and continued the call on the handset
- Thereafter I got the kind of trouble we've experienced in the past:
- A new call coming in only answers on the handset. Pressing the BT button initiates a SECOND call out on the BT - to the last number dialed.
- Trying to make an outgoing call it LOOKS like the headset is enabled, but as soon as the call initiates the headset icon dissapears and the call continues on the handset
- Throughtout, BT seems to be on (ie no on/off issues)
- All seemingly fixed by a reset.
Basically it feels like the BT stack is a complete disaster. When u start ROM hacking this Buzz, I'm very much looking forwards to going back to the old BT stack.
Any thoughts Buzz?

craigiecraigie4 said:
O Hell! Your hack seems to have kept it alive overnight, and I truly thought it was solved. But today I'm finding that the BT problems go way deeper than sleeping (nothing to do ur hack):
- In the middle of a call, with my phone within 2 feet of me at all times and both devices fully charged, it disconnected BT and continued the call on the handset
- Thereafter I got the kind of trouble we've experienced in the past:
- A new call coming in only answers on the handset. Pressing the BT button initiates a SECOND call out on the BT - to the last number dialed.
- Trying to make an outgoing call it LOOKS like the headset is enabled, but as soon as the call initiates the headset icon dissapears and the call continues on the handset
- Throughtout, BT seems to be on (ie no on/off issues)
- All seemingly fixed by a reset.
Basically it feels like the BT stack is a complete disaster. When u start ROM hacking this Buzz, I'm very much looking forwards to going back to the old BT stack.
Any thoughts Buzz?
Click to expand...
Click to collapse
...stupid question, but:
does it actually have MS BT stack??
buzz

there is another problem, it seems that my mobile doesn't accept any connection from any nokia mobile, it says to them (unable to connect), i don't know why???????????

I too am experiencing Bluetooth problems with my O2 Exec and a Motoroa HS810 headset. I use voice tags quite a bit and for the most part this works well however sometimes the EXEC fails to respond to the button press on the headset.
I first noticed this when I did the reg hack to make MS Voice Command the default Voice dialler and presumed that maybe there was a problem with MS VC so went back to VoiceDialler. However the same thing happens with VoiceDialler. To get it working again i have to turn off bluetooth in the Wireless Settings panel and then turn it on again. After this it starts to work again (but not ideal if your driving).
I think this might be the same problem mentioned above, i.e. bluetooth says it is on, the blue led flashes on the phone, but in reality it has switched itself off. I did some more testing while the headset was not initiating voice dialling and called the Exec. After a short time, the headset icon appeared on the "Incoming Call" message area and my headset burst into life. This would make sense I suppose because doesn't Headset mode start bluetooth up when a call is received (presuming it is off)?
Looked at Buzz's reg hack for Bluetooth but didn't really understand it

Here's what didn't fixed it for me.
After more reading today I realize I was way wrong.

Re: Here's what fixed it for me.
I can confirm that these registry settings work perfectly on the blueangel Great job.

Answering calls when open and Speakerphone mic volume

Hi,
Is there anything that can be done to improve the mic volume when on speaker phone - I have had complaints when more than a foot or so away that people can't hear me.
I have the phone open on my desk most of the time and am just trying to work out the best way to deal with calls as they come in. At the moment unplugging the USB and then flipping the screen and then trying to answer the call seems a bit ham fisted and I keep on loosing calls

I personally never use my MDA Pro as a conventional phone. I find it too bulky. My own method is to always use a bluetooth headset.
If I was in your situation, I would have the Universal open on my desk, with the bluetooth headset lying beside it. When the phone rings, simply put on the bluetooth headset,press the call receive button on it, and away you go.

You don't really need to flip the screen, just close it and then use the green button to answer the call. Will work fine with the USB connected if you don't mind people looking at you strangely.

Hi Guys,
Thanks for the responses.
I don't have a headset so haven't gone down that route yet. Will they work with Skype and VOIP software etc on the phone?
As for closing and then picking up, I'm wondering if the phone has a problem because I have tried this a couple of times and have lost the calls although I am generally unplugging the USB, closing the phone and then answering - have only had the phone a couple of days so still getting the hang of it.

Hmmm....can it be used when in pda mode to answer and make calls... I have tried this, but I think either my machine's mic & speakers dont work on the inside (screen side) of the clamshell, the other person on the line can't hear, and I hear their voice (distantly), which means it is coming out of the back of the screen, not the front. Its either that or the device just isnt designed to work in this orientation.
Has anyone else tried recieving or making calls with the screen facing out in portrait mode?
Re the Bluetooth headset answering method, great idea, I do this, but I have found that sometimes my o2 blue headset loses the pairing when I press the answer call button, so I lose the call anyway.
Can anyone tell us how it should work, will the recent rom upgrade fix this, is there even a mic and speaker on the inside lid?

Can anyone tell us how it should work, will the recent rom upgrade fix this, is there even a mic and speaker on the inside lid?
Click to expand...
Click to collapse
The Mic is right next to the power button, so it is as close to your mouth when in PDA mode or closed. Also There are two speakers on the hinged lid, in PDA mode it's the slightly recessed oval shape 10mm from the top dead centre.
I've never discovered a software method of disabling this speaker. Possibly a hardware fault? Might be worth discussing with your handset provider

Bluetooth Static When Answering Calls

I have a Cingular 8125 paired with a Plantronics 320. When I answer an incoming call with my bluetooth headset, the other party hears static while the headset establishes a connection. Once the connection is ready, the static disappears. It only lasts for a second or so, but is highly annoying to the other party. Has anyone else experienced this or have a solution? This also happens with my old Tekkeon BT headset, so I know it is a phone issue. Thanks!

Are you using both ring and vibrate at the same time? Perhaps a custom ringtone?
If so, I have had the same situation. Unfortunately, the only solution at the moment that I know of is to turn off the vibrate, or don't use Bluetooth.
I submitted this to HTC a while back after experiencing it on my 8125, and an 8125 I had to replace it.
EDIT: I've only tested it with two 8125's, and a Samsung WEP150 and Motorola H810 (I think) headsets..
Also, as an experiment, try calling yourself from another phone, and answer with the headset. What you'll likely notice is that the static goes away as soon as the vibrating stops.

sk0t. Thanks for the reply and info. It sucks that we have to disable vibrate. I'll give it a shot and see if I don't blow out my friends' eardrums.
*UPDATE*
That did the trick. Thanks.

psychotron said:
*UPDATE*
That did the trick. Thanks.
Click to expand...
Click to collapse
Suspected it might. It certainly does suck that we have to disable vibrate when using a BT headset. Drives me nuts actually.
When I went through and discovered this (haven't seen reference to the issue anywhere in my searches), I had tested with something like 3 different headsets and two 8125's.. Was able to duplicate it every time once I figured out what the cause was.. Very very strange..
I just hope that HTC can do something with this issue on these phones..

Wish I had found this thread a couple of weeks ago. I went through 3 Plantronics 510 headsets and two Cingular 8125 before making the discovery that the problem was tied to the vibrate ringer setting.
One thing I've done--since I'd still like the vibrate feature--is you can set the ringer to "vibrate then ring". I just have to make sure I don't pick up while the handset is vibrating--which isn't too hard since that usually is just the first caller's ring.
Another think I found when troubleshooting: if I put my handset in another room and pick up incoming calls everything is fine. Seems like the vibration needs to be in proximity to the headset for this problem to occur.

hmm i just got my bt headset and was told of the static...
thanks for the info guys will deff turn of the vibration to see if that prevents the static when answering a call

BlueTooth Problems.....Please Help!

Using my 8525 for a bit over a month now, and I love the phone. Plenty of hacks/tweaks/edits and the phone is just how I like it right now.
Driving a 2005 Acura TL with the built in HandsFree Link and the phone paired seamlessly.
Recently, I notice that while on a call, sometimes the BT Link will drop and automatically transfer the call to the handset. This only happens here & there, not every call. Once call so far after I hung up in the car, the phone was still on and I ended up leaving someone a 6 minute voicemail of me driving, listening to music.....that can be dangerous!!!
Any help or suggestions?
Thanks,
John

i HAD SOME DISCONNECTS WHEN I RECEIVING MESSAGES..IS THAT IT?

No, it will just drop the bluetooth signal mid-call, then to get the car to recognize the phone again, I have to turn off the car and turn it back on to reset connection.....

johnny--2k said:
Recently, I notice that while on a call, sometimes the BT Link will drop and automatically transfer the call to the handset. This only happens here & there, not every call. Once call so far after I hung up in the car, the phone was still on and I ended up leaving someone a 6 minute voicemail of me driving, listening to music.....that can be dangerous!!!
Click to expand...
Click to collapse
I've had the same problem, only once or twice in about a week, using my Jawbone bth headset. Very disconcerting, but survivable. I can see where losing the car pairing might be a bit more problematic.
I wonder if this is because of the /weak/ Bth stack on the TyTN???
-Humbert

Possibly. I thought I saw some upgrades for the BT Stack on here somewhere but now I cant seem to track them down.
Something about the BT Radio shutting down or going into sleep mode after a while and a registry edit to keep it on at the sacrifice of minimal battery life which is fine by me...

Didn't read you mentioning it, but does bluetooth power off during the breaking of the link? If it does, read on and try the following..
not sure if this will help, but try to disable your auto power off options, uncheck the on battery power and on external power..
I had this solved some bluetooth problems especially using the Hermes Widcomm hack and MSI Blueplayer..

Yes, the BT does turn off, but then on again automatically as soon as the call is ended.
Where are you talking about? Is this in the registry or the BT Settings? I was not sure if the WidComm stack is fully functional as of yet, if so, is it in the Wiki?
Thanks again,
John

The WidComm stack is definitely NOT fully functional yet. One of the problems I have with this stack is that, the bluetooth will power off when my wizard turns off or goes into standby, which is not normal!
Not it is not a registry setting, but it is just how it behaves on my system. Sorry for not being a help... I know how the MS Stack pisses people off..
Best regards,
Eugene

Hey, every little bit of info I can get helps....
Thanks for the info on the WidComm Stack....I might just wait and deal with the MS untill the WC is fully functional and possibly in CAB format....just to make life all the easier!

OK, So today my phone would not drop the BT signal from my car.....after being home for 4 hours, it was still trying to use the HandsFree when recieving or making calls....took me a minute to figure out because the dialer skin I have is black at the top, so I could not see the headset icon at the top and was wondering why I could not hear anyone or use speakerphone.
Hopefully it was just a freak accident and wont happen again, but just incase, any suggestions?

Bluetooth settings for handsfree - without incoming call delay

Hey folks,
I've been struggling with this issue for months now and couldn't find a solution yet. Had the same problem with my Polaris before.
When using BT Handsfree profile, either with my Jabra 250 headset or with my built in car handsfree (Parrot) I get a more or less big delay after accepting a call until the audio stream is transferred from my phone to the BT device.
Meaning, accepting the call in the car results in like 5 seconds delay until I can actually hear what the person on the other end is saying. Until then the voice is still routed via the phones builtin speaker, as if no BT device would be connected.
Same happens with my Jabra headset, though the delay is less there. Maybe 2-3 seconds sometimes.
I tried playing around with Shaps Advanced Config or HD Tweak Bluetooth settings, but no luck so far :-(
Could anyone who is using BT handsfree devices, especially car kits, tell me if you get your audio on your BT device right away, without delay on your BT device? If yes, please tell me exactly what settings you are using for your BT on the phone, e.g. Bitpool min/max, Audio Gateway on/off, Joint Stereo Yes/No etc.
Please let me know if ya using S2U2 as well, I think this could add up to the problem, though for me I still have the issues when I disable S2U2
thanks,
boba

i am using a Bury comfort BT and it rings 2-3 seconds b e f o r e my phone rings! i did not tweaked any settings in my HD. i am not using s2u2.

I also have a Parrot in car hands-free system. Have to say, whilst there are and have been some 'issues' (from time to time) a long delay when an incoming call is accepted isn't one I get.
I don't have the 2 programs you mentioned, as I'd not heard of them before - so I'm running my HD (as far as BT goes at least) in stock trim - FYI I have the auto-answer selected (in 'Settings>Phone>More') set to talk after 4 rings, as a personal pref.
I do have issues with the BT on these phones - I think it's a WinMo thing though, as it's been the same on all the WinMo phones I've had - the BT is pretty retarded unfortunately and it's the one major gripe I have with it and ultimately 'put up with' (very begrudgingly, as it's a feature I use a lot)
Issues are;
Occasionally the phone will answer instead of the car kit (if it's in my pocket - although I may have solved that by having pocketshield 'slide to answer' on there now)
It will NOT auto-answer at all on my BT stereo headphones NOR [more annoyingly] my Scala-Rider motorcycle helmet kit (where every other 'normal' phone I have had has done so with no issues at all)
Every now and again it will freeze the car-kit by showing that there is an active call, when there isn't - and the only way out of it is a soft reset of the HD itself
I only wish there was a fix/tweak for the BT in WinMo - but it seems that most programmers don't see this as a priority area and as such it's not been resolved - maybe 6.5 will address it...but I'm not holding my breath!

Hello, same problem with my Motorola bt350, with and without s2u2.
Same with stock ROM or with dutty's ROM and other.
Its a known win 6.1 BT stack issue.
Regards
T

@ boba23
If you find a fix for that issue please tell me!!! its so annoying
T

Same issues here. Anyone find a fix.

thought it was mine in car blue tooth that has this problem...good (or bad?) to know that it's not an isolated incident.

same issue...
I have parrot MK9000 and HTC BH S100 (stereo). The delay is the same. I do not think there is going to be a solution.

Ι have the transfer delay BT issue here too.... the others person voice is going out from the phone for 2-5 sec and suddenly its transferred to BT heasedet.
Preety annoying, it happens to all my ΒΤ headssets (Jabra , Samsung) the dead seconds just varies.
Plz guys anyone who has solved this let me know

boba23 said:
Bumping this thread up again, since I am still facing the delay issue. I am pretty sure it's not ROM related, since I had this issue with all 6.1 roms I tried. Right now using Topix 2.7.
Played around with Advanced Config BT settings again, but I still have that incoming call delay with my Jabbra BT250. Mostly takes 3-4 seconds, after accepting an incoming call till I hear sound on my headset. I really can't believe that this is an issue that only a few ppl are facing. I have nothing spectacular installed, even disabled S2U2 to see if that helps, but nothing :-(
boba
Click to expand...
Click to collapse
I think this has to do with a combination hands-free / rom version. I have a built in car kit and if I accept the call with phone answer I get the voice right away on the car kit. If I accept it on the radio, it will take 2-4 seconds before sound is transferred to car kit.
I've made another test on a parrot car kit, with same ROM version as before, and it behavior was diferent. If I accept the call on the car kit button, the sound is transferred immediately to the car, if I accept the call on phone button, I get instant sound, but on the phone - private mode....
I made also this test with a plantronics headset, and the sound is transferred right away to the headset either I accept the call on the headset or the phone
so
I am using topix 2.9.4 6.1 rom version - but already tested with several 6.1 roms and 6.5 - behavior is more or less the same

boba23 said:
Bumping this thread up again, since I am still facing the delay issue. I am pretty sure it's not ROM related, since I had this issue with all 6.1 roms I tried. Right now using Topix 2.7.
Played around with Advanced Config BT settings again, but I still have that incoming call delay with my Jabbra BT250. Mostly takes 3-4 seconds, after accepting an incoming call till I hear sound on my headset. I really can't believe that this is an issue that only a few ppl are facing. I have nothing spectacular installed, even disabled S2U2 to see if that helps, but nothing :-(
boba
Click to expand...
Click to collapse
Hi Boba, you're not alone I use BT sometimes as a backup.. and I too have an annoying delay of several seconds... at that very moment I think "hey where's the incoming call", I then hear the sound from the normal phone speaker, and when I switch to the normal phone again the sound is passed to BT ....

Bluetooth Incoming Call Delay
Has anyone come across a solution for this yet?
I have always had a 1-2 second delay in being able to hear the caller using my BT250 headset but, after installing the Orange update ROM, the delay seems to have increased to 3-4 seconds. The caller can hear straight away though.
I have just purchased a BT2020 headset and the delay is still 3-4 seconds.
I am not confident in installing different ROMs (because of my limited knowledge) but would install any that will eradicte this really annoying delay. Any suggestions?

alanu said:
Has anyone come across a solution for this yet?
I have always had a 1-2 second delay in being able to hear the caller using my BT250 headset but, after installing the Orange update ROM, the delay seems to have increased to 3-4 seconds. The caller can hear straight away though.
I have just purchased a BT2020 headset and the delay is still 3-4 seconds.
I am not confident in installing different ROMs (because of my limited knowledge) but would install any that will eradicte this really annoying delay. Any suggestions?
Click to expand...
Click to collapse
Just spoke with Orange Technical Helpdesk and they are sending me a new handset.......will publish result.