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.
Related
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.
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
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?
I didn't want to open yet another Polaris bluetooth problems but none were like mine.
I have the O2 Orbit 2 and I had bluetooth mute problems which were usually resolved with soft reset, I think that ever since I installed HTC's official bluetooth mute fix the mute problems got worse.
Every couple of calls or when I plug something to the mini usb (ear phone, charging, data, etc') my bluetooth is muted, the connection is established and I think I do hear through it but with extremely low volume (less then a whisper, more like back ground noise) the mute almost never fixes itself, it goes on even if I flash with a different ROM!!, what fixes it is playing with turning on and off the connection to the headset while in call or, while in call pluging and removing the wired headset, once it's back, it usually stays ok until (randomly) when I plug something to the usb, at first I though it will never work again (flashing something like 10 different roms...) but this fix is less then convenient, again, sadly the official fix doesn't help.
Anyone knows the return policy to O2 from Germany? I live at Israel so I think it might be a problem...
Same problem for me.
After the original fix, my bluetooth headset is always mute.
I have ordered a new original HTC M200 headset. I hope it will work............
Original M200 arrived today.
Don't work. Always mute.
I have tried to uninstall the original fix without any resultate.
Did you get yours to work?
You can try the on/off trick, I usually call my voicemail when the mute starts and then goto options and turn handsfree off, then again turn it on, sometimes it works after 4-5 tries sometimes after 2-3 minutes...
Sometimes the voice comes back in slow motion!!, I thought at first that it was garbled, but once I have a voice mail of a woman who talked fast so when the voice came back in slow motion she sounded like a very low voice slow talking man.
no, don't work on any headset......
It's a hardware problem ??
Hey guys...just wondering if you guys found a solution to this problem. I have this problem with my touch pro. The A2DP works, but for some reason handsfree through bluetooth is muted and I can't unmute. Hope you guys found a fix and can help me out.
Hi there,
Can anyone help me solve this problem:
Ik have a Sony car radio with a BT hands free function (MEX-BT2500) in my car. When I make a call, the radio stops and I can speak hands free, hearing the conversation on the car-speakers. All nice, like it should be.
Problem is when I receive a call. The radio stops and I hear a ringtone (not my phone-tone though ). When I awnser the call, the caller can hear me, but I can't hear him, unless I take the phone in my hand and put it on my ear. The sound doesn't come through the car-speakers. So an incoming call can't be awnsered handsfree.
With my former phone (nokia 6230), it was no problem. Anyone knows how to solve this?
If it was the same as my problem, turn up the volume on the phone
My phone was the exact same, for some reason when it connected it was turning the volume right down!
Hope yours as as simple
todd69 said:
If it was the same as my problem, turn up the volume on the phone
My phone was the exact same, for some reason when it connected it was turning the volume right down!
Hope yours as as simple
Click to expand...
Click to collapse
Unfortunately my problem is not that simple. I got an incoming call yesterday when I was driving, but again no sound. When I called back, there were no problems. Does anyone else have a solution?
Well, I don't have the Sony-stereo, but I've got a Pioneer with BT. I have bumped into several issues with it, and the solution is the same every time:
-first, if you have a settings-option called something like "reset BT-memory", try that one, and pair phone again.
-If that doesn't work, next step is full reset of the stereo, meaning you pull it out and disconnect the power. Then plug it back in, and re-pair phone.
This at least did the trick for me, now voice-dial works perfectly, and I even have "BT Audio", meaning I can play my Topaz' music on my carstereo without hassle.
Could also be something else simple, you are using the stereo to answer and not the handset?
If I answer using the phone with my stereo then I get the same issue as you, answer using the stereo and all is well