Related
Hello,
Hopefully somebody can help me, the BT turns on after taking/recieving/missed calls. It is annoying. Does anybody know how to stop it? I have tied tuning it off or into discovery mode, but to no help.
Any suggestions anybody? is their a reg hack for it?
Thanks
I had the same problem and fixed it by uninstalling bluetooth tools stack. Seems Okfor first hour.
Regards
Richardracer
I had the same problem and can confirm removing BT Tools fixed it.
Seems to be an 'undocumented feature'
but if the circle (a clock i think) is made white (as in on) then it turns off itself after awhile
TooMuch2AM said:
Seems to be an 'undocumented feature'
Click to expand...
Click to collapse
It isn't an undocumented feature, it's one of the main features of Pocket Bluetooth Tools! In order to save battery, BT is kept switched off until a call comes in then it comes on (no messing around with the headset profile crap on the today screen). After the call finishes, if the timer is enabled in BPT, it turns BT off after about a minute (configurable in the registry).
PBT Website said:
"Today screen"
The icon on the left activates or deactivates Bluetooth. The clock symbol switches automatic power off for Bluetooth on or off. When activated (white backround as in the picture) then Bluetooth will be switch off after 60sec of inactivity.
Click to expand...
Click to collapse
Please take the time to read the documentation when installing software.
i still feel there should be the option to have bluetooth tools installed and not use the timer and still not have it turn bluetooth on when the phone ring
BT Tools made my headset completely non-functional. I could pair it after installation as instructed, but the phone would not put calls on the headset no matter what. Nice idea, but didn't work for me.
Has anyone actually measured the battery impact of having BT on? On my Ericsson T68 it had a very minimal impact on the battery life.
PBTool is wonderful. Before using it, after my first call of the day the xda would not release the connection. This meant it was running the bluetooth at full power continuously, which would drain the battery in about 3 hours, and the battery in the bluetooth headset in about the same time. So completely useless as a PDA.
With PBTools, it now closes the connection by turning bluetooth of a few seconds after the call finishes (Ive set it to 3 seconds in the registry).
It has finally made my headset usable, and for that I thank Towa.
I do wish he has made it more configurable, but at least he made is quite usable by default. Until another programmer comes along and does better, I dont think we have much to complain about.
Surur
Please take the time to read the documentation when installing software.
Click to expand...
Click to collapse
Thank you very much, smart ar$e.
TooMuch2AM said:
Please take the time to read the documentation when installing software.
Click to expand...
Click to collapse
Thank you very much, smart ar$e.
Click to expand...
Click to collapse
Hey, you're the one who obviously didn't RTFM. In your case it was an 'undocumented feature' only because you didn't read the documentation! If I'm the smart one...
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.
Hi,
does anyone know how is it possible to disable the LAST NUMBER REDIAL function? If my BT headset is in my pocket it happens many times, that the "-" button is pressed and it activates the LAST NUMBER REDIAL. It is very annoying....you can imagine. Is there any REGISTRY hack or somehing like that to solve this problem?
THX
That has to be one of the most annoying things!
Especially when you are having a moan about someone after the original call!!
Vijay??
Nobody has the same problem?
me too - it happens for me because I changed the LaunchAPEnable registry setting from 1 to 0 to send the sound to my headset over BT
WOlfgang
Can you clarify this problem? Which button is it that's being pressed? Hardware key or on the headset?
Explain clearly and I'll look into it and if I can help...
V
Vijay, you're too kind for your own good.. heh heh. (but we all appreciate it )
I had this problem with my BT headset and speaking for myself, it's when you hold down the button on the headset, you'll initiate last number redial.
If you just press the button you'll launch Voice Dialler..
I used to keep my BT headset in my pocket and I had both these issues.. eventually I resolved both of these problems by buying a £3 neck strap off ebay and wearing the headset round my neck.. :wink:
cheers,
gaspx
--
BT on for nearly 2 weeks!!
gaspx: there is a technique I'm working on which might help us out here.
It's messy and very very early stages right now, and sent me over the edge last weekend. But if the technique works, it'll open some very interesting doors. Please remind me in a few days. I'm afraid that I can't think of a quick solution, but in my usual style, an unnecessarily complicated solution might surface...
V
i have had the same problems aswell...
although i have been looking into the phone tools that only turn the bluetooth on when you have a phone call,
i am wondering if that will allouw bluetooth to turn on when transfering audio
VJVolubilis will automatically enable bluetooth and transfer audio (or attempt to).
V
Anyone figure out a way to do this yet? It sucks because I keep accidentally calling people from my headset.
I've looked around for a solution to this problem for a while now. Anyone come up with something? Vijay?
Any development on this issue yet? I accidently called twice today. Very annoying because I kept my BT headset in pant's pocket. Please help, Vjay and others professors.
How about powering down the headset? Maybe I don't get it but....
I just triple-checked, my Motorola H500, H820 & H700 will reconnect when I power them back up & press the button once as long as the phone's BT is on, even mid-call. Do these newfangled machines not offer that? What I do is answer the call on the unit w/ one ear and if I think it'll be more than a minute, I put the headset on the other ear to power it up, press to connect, and I don't miss a word (not on the H820, I'll take a pause to switch to that one when I pull it out of my gadget-laden diaper bag. Every mom needs a BT headset!). I think it'll hook up even during ringing, but calling from my skype seemed a little overkill for this response.
(I'm using a modified/very-simply-reduced version of the Jaguar ROM on a wizard at the moment, and many of Vijay's venerably ingenious tools.)
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?
Brought a jabra bt8010 and all is working fine, the only issue i have is that the screen will not go off.... Even when you press the off button quickly to turn it off it comes straight back on. This only happens when the Jabra is connected to it.
Anyone one got any ideas
Problem solved, it appears that there was a tweak i had applied to not go to sleep when within a call, when the Jabra is connected it must think that it is always in a call so the screen never goes off. Just reversed this tweak and now the screen goes off and stays off.
Well, I don't have a BT headset but never seen people having this issue. I think reversing that tweak is just a workaround, there must be another way to make it turn off automatically. Hopefully someone better informed will answer to this.
Anybody got any other suggestions ? Not an ideal fix but a fix none the less.....
I use the 8010 and I had that problem. I deleted the connection in both devices, and paired them again at a greater distance. The phone always communicate with the headset, like sometimes, the headset will come on for no reason. I look at the headset and the music icon disappear, then reappear. I still cant figure out why. Love the headset though. It doesn't come on that much no more, but staying on, no..
already tried deleting it on both ends and pairing, just does the same thing.
caller ID is now working though with the Jetware fix which is really handy.