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.
Hello there,
has anyone an idea how to realize this:
blackstone is in standby - bluetooth is activated - bluetooth headset is on - both connected - call comes in - I take the call with the bt-headset - talk - I end the call with the bt-headset - blackstone remains on until the adjusted time for standby is reached
but I would like the blackstone switch into standby mode immediately after ending the call
is this possible ?
greetz
smuggs
This needs addressed - sleep after a call during headset mode
In headset mode the phone does not go into sleep mode or power off automatically after a call. This is a major issue for those of us who leave the phone in the pocket in the car or when using bluetooth headsets. I have finished calls recently and then 5 or 10 mins later my phone would connect to someone random in the phonebook whilst driving which is quite embarrassing "I didnt call you" - "yes you did"!!
In the meantime I am using constant device lock but this is a clumsy solution for what surely MUST be a common problem. Can anyone else not help us out and try to get the device to sleep after a call during headset mode? I would be so grateful for a useful solution that doesnt involve a constant device lock that I dont really need!
Cheers
I'm having the same problem also....
The list grows - surely there must be others out there with the same problem. We should try and get out heads together to crack this one!
the_flyer said:
The list grows - surely there must be others out there with the same problem. We should try and get out heads together to crack this one!
Click to expand...
Click to collapse
ooch aye the noo ...
obviously NOT ... which makes me wonder ... as for me this is a main issue
pimpin' seems to be more important than functionality ... huh?
i guess i will write to htc and see what they r saying
will post answers here
greetz
smuggs
Sounds good man, keep up posted. Its a major issue for me too!
ok folks .. here is the very annoying answer i got from htc support
You recently wrote us about an issue that you have encountered with your HTC Touch HD. There is only one way to instantly set the device into standby mode: please press quickly the power on/off.
what shall i say ... THAT'S CRAP !!!
and i'm still thinking that there must be a workaround ... redefining the buttons or something like that ... any ideas from the specialists in here ?
c'mon guys - help us out here
greetz
smuggs
that's really strange...just tested it.
connection htc/jabra bluetooth.
htc device lock ON.
an incoming call arrives, pick up the call via bt-headset. end the call via bt-headset. phone is immediately locked again (htc own device lock), display is on. after 1 minute also the display turns off.
or do you mean something completely different?
Same here and it feels retarted.
Ooe of the major purposes of a bluetooth headset is to avoid contact with the device. So having to take out the phone or handle it (in a car/office whatever) after a BT call is rediculous.
BT headset drops call
I am not sure if I should pose my questions here but my Jabra BT headset is connected to my Blackstone on standby mode via BT. However, when an incoming call comes, the BT headset does not get the call but is transfered to the HTC handset instead. I have no problems making outgoing calls on the Jabra headset. It's frustrating when I am driving... could anyone tell me how to remedy this?
Thanks in advance.
end call via BT into standby works with LockMeLite
hello there,
with LockMeLite http://forum.xda-developers.com/showthread.php?t=478606 and my samsung wep250 bt-headset
it works
this headset is non-a2dp-capable
dunno if an a2dp capable headset will work, but will test is (next week)
greetz
smuggs
I have tried flashing newer fancy roms and tried various lockers but no applications are intuitive enough to fix this simple fault. When making a call in 'headset mode' the fast sleep mode prevents accidental presses during a call. Unfortunately when the call is ended via handsfree/car kit/recipient, the phone wakes back up to life.
Any locker I have used is active indiscriminantly when pressing the power on button to wake the device from sleep. I have tried lockmelite, hd tweak for inbuilt MS lock, pocketshield and another locker however none have the function to only lock the device whilst in headset mode and after a call has ended. This is a request to developers, expert cooks and modifiers please can anyone help us out?
Thanks a million
Check this, it can do the trick...
h..p://www.pocketshield.net/default.htm
S2u2 V2.04 workes fineas you needs, even look during a call (gives black screen)
I'll do a try
As I have the same request/problem I'll try the following with the help of AGEProfile.
- I create a profile actived when the headphone is connected, when this profile is activated it launches a program named MySuspend so my phone is suspended.
- I create another profile activated when the headphone is connected and there is a call in progress, this profile does nothing but it exists (only)
So when my phone goes connected with the headset (BT) it goes suspended.
When I receive a call it wakeup as normal and the profile is switched to the second one (but does nothing)
When the call finishes, the first profile is activated again and the phone goes suspended.
That's all (and it should work, I just made the setup for that).
Regards,
P.S. sorry for my english because it's not my language.
I also have this same question. After ending the call the screen stays unlocked and will inadvertently call a number sometimes.
I tried
Yes I made a try yesterday evening in real conditions and it work very well
So I'm very happy
I forgot to mention that I also use the Inesoft to have the screen locked when one call come in.
Hope this will be useful for you too
Regards,
Hello All,
I have been having problem with my sound profiles on my HD2. I usually have my HD2 on Vibrate profile and after a while it auto changes to Silent profile. Resulting me in missing all my calls and events. I have tried different ROM's and radio and it still occurred.
So I finally found the root cause of it...I have my phone auto pair with my car built-in bluetooth system. So what I have noticed is, when i switch the car ON, it pairs with my phone and set the volume to Normal profile. After switching the car off and exiting it, it switches back to Silent profile and not the original state i.e Vibrate.
I am not even sure why it even changes sound profile to Normal upon pairing in the first place....is there a way i can tweak or prevent these changes?
P.s: I'm running wm6.5.5 Rom ( Touch X-treme ROM)
Bump...no one has any ideas?
Can someone help as HTC have not been helpoful. I have been having problems with bluetooth dropping out randomly with my car-kit.
To cut a long story short if i set power save options to always on, then got my admin to disable auto lock on the exchange system. Then when i get in the car turn the phone bluetooth on it never drops out.
It would seem it is then a power save problem, the bluetooth clearly suffers when the phone goes into this mode.
Unfortunately i need the auto lock on from exchange (business reasons) and the max timeout is 10 minutes. so unless i wake the phone up every 10 minutes it will cause the bluetooth to drop out.
One other quirk is that the car bluetooth must be on before the phones or the bluetooth will drop out in about 10 minutes. This applies if i leave the car and return with the phone bluetooth on.
The phone always need switching on and off before it will work again.
The car software is the latest and technically the snap is not listed as a supported phone.
Is there anything i can do (WM 6.5)
Thanks
Bluetooth switches itself off when my new DHD goes into standby.
This means that when using a headset and the phone rings, I can't pick up the call with the headset, and the phone doesn't switch the audio back to the headset if I switch Bluetooth back on during the call and press the reconnect button on the headset - this would be expected behaviour, and has worked on other phones.
I can't find a setting to fix this problem, nor a solution in these forums or elsewhere. Is it a bug or have I missed something?
Ok I've found the problem: I'm running an app called battery Booster designed to help conserve battery power. One of its default settings includes turning off Bluetooth when the device is locked. D'oh!