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've searched a bit, and can't find a solution to the problem I'm experiencing. When I got the phone last week, it discovered and paired with my bluetooth earpiece without issue. Now it won't even detect the bluetooth device?
I did install: Closeall, omapclock, smartskey, and lokiwiz unlocker. Sometime during or after, bluetooth stopped working correctly. Are there any known conflicts between the above applications and bluetooth? fyi- I did try my earpiece with another phone, and it works fine.
I should mention that I inadvertently deleted a file called "ssdaemon" (or something close to it) from the startup menu, during the smartskey install. I performed a hard reset and the file returned. Bluetooth still does not work after the hard reset and several soft resets. I've also tried playing with the blutooth settings to no avail. How do I resolve this issue?
Between this issue and that damn speakerphone being stuck on while using a regular earbud style earpiece this buggy ass phone is pissing me off! The freaking speakerphone stays on, and I can't get it off unless I perform a reset. :evil:
This is really annoying because I'm hearing impaired and rely on either a special blutooth device or a hearing aid adaptor (I can't use a cell phone in the normal fashion, all I hear is static). These two problems currently render the device useless to me.
I think that loading a different rom or waiting for cingular's update will help, but I'm not sure. Any help on either of these issues is much appreciated. Thank You!
Nick
No ideas or advice?
can't automatically turn off the display in MortPlayer when the music is playing through BT
Hi! I've had the exact same problem. It seems difficult to find a program that turns the display off when using BT. I have tried the one built in to mortplayer, mortsaver, deltalock, screenguard etc nothing works. But if I change HKLM/System/CurrentControlSet/Control/Power/State/ScreenOff to 001000000 in the registry then it works! When this is changed you will be able to play music with the phone in "off" mode so I guess it stops programs from running by modifying the suspend mode somehow. It does affect your batterytime negatively though...
Is there any solution to the problem?
I have got the same problem with my bluetooth headset and PocketMusic (or MortPlayer):
The display turns off if there is no bluetooth headset connected. But it does NOT turn off if the headset is connected.
Krischaaan
Display problem
RomeoOlsson said:
Hi! I've had the exact same problem. It seems difficult to find a program that turns the display off when using BT. I have tried the one built in to mortplayer, mortsaver, deltalock, screenguard etc nothing works. But if I change HKLM/System/CurrentControlSet/Control/Power/State/ScreenOff to 001000000 in the registry then it works! When this is changed you will be able to play music with the phone in "off" mode so I guess it stops programs from running by modifying the suspend mode somehow. It does affect your batterytime negatively though...
Click to expand...
Click to collapse
Hey. I've tried this method, but still can't seem to get this fix to work. Which value needs to be modified? And can you confirm what the value is (five or six 0's after the 1)? Also I have a sub category within the screenoff category. Does anything in here neeed to be changed? Thanks in advance.
I had encountered the phone auto mute after making 1st call ie on 2nd outgoing calls onwards the opposite party will n ot be able to hear me.
This may be due to my installing various software programs which I cannot identified as I installed many at the same time and after restoring from my spb backup after rom upgrading
I can overcome it by pressing the soft "mute" button twice and thereafter the opposite party will be able to hear me.
I am wondering whether there is any egistry settings/modifications that I can do to overcome this issue instead of hard reset and thereafter reinstalling all my programs and data which is time consuming.
Thanks to anyone inadvance who can share and help.
The cause/solution is finally found
Initially I thought is the radio problem
Then I thought it is the software programs problem
Next I thought it is due to the custom rom.
Finally I found the problem is due to "activating the auto recording phone" in resco audio recorder V4.62.
Deactivate it and the MUTE problem is gone
hi bro, i have the same problem which really pisses me off at time. i did not realise its resco audio, shall try out and see if it happened again.. did you try other call recording software to see if the same happens?
I had this problem with my G2 as well. Every time I have bluetooth on and then go to turn it off, it causes the phone to reset.
I have tried different combinations of control to try and differentiate what might be the cause. GPS on and off, Wi-Fi on and off etc..None of those seem to matter. Just whenever I turn off bluetooth the device resets.
Any ideas? Maybe something that will be addressed in a future bug fix update.
Nobody having the same issue? No ideas?
CBConsultation said:
Nobody having the same issue? No ideas?
Click to expand...
Click to collapse
Just tried mine - does not reboot (mine is temp rooted - should not make any difference).
UPDATE - i also connected a headset first.
I suppose I should clarify the circumstances so testing might be quicker.
If I simply turn bluetooth on and off there is no issue. But when I connect a headset and use as normal, if I turn bluetooth off it reboots the phone. I had the exact same issue with my G2 as well.
Yup, my MT4G does this as well. It's somewhat random, it only happens when I'm disconnecting the BT in some fashion but not every time.
This past time I still had the BT headset connected, all I did was end a (voip w/ csipsimple) call that was over the BT. Just closing the audio channel was enough to kill it.
I'm using a jawbone icon, are you using an aliph headset as well?
Happened to me on my G2, my MT4G should be here tomorrow. It doesn't happen every time, I'm looking for the cause and take note of what I was doing or what app was open when it happens.
I'm using a Motorola Roadster.
I've been unable to determine the common denominator so far... The only thing that is constant when this happens is I have the Car Home app set to open and activate dock mode whenever my Motorola Roadster Bluetooth Speakerphone connects to my phone.
Anybody else have this setting configured??
Agh, I thought it was only me and only when I was using a SIP soft phone connected to Trixbox... hmmm
hah2110 said:
Agh, I thought it was only me and only when I was using a SIP soft phone connected to Trixbox... hmmm
Click to expand...
Click to collapse
Happened to me once also, but also had two other restarts without the bluetooth being involved. I don't think I like this phone.
I called TMobile about it and they just told me to do a complete reset on the phone. I figure I'd try that in case the 2.2->2.2.1 OTA caused something to be messed up but it didn't make a difference.
I have noticed that when it is going to reboot, the "Bluetooth headset disconnected" message doesn't appear when I turn off the headset. The phone continues to work for a few seconds with the bluetooth connected icon still showing (the dots on the side of the BT icon) then it reboots.
hah2110 mentioning sip got me thinking.
I had sipdroid running in the background... I've disabled it and so far haven't been able to reproduce the reboots. With it on I can cause the reboot after two or three disconnects with both a Jawbone Icon and a Blueant Z9.
To be clear, with sipdroid running I can reproduce the reboots *without* actually placing any calls with sipdroid, but with it completely off the phone has been stable.
Interesting... SipDroid does say BT is experimental. I always figured it was problematic because it is using different protocols. Basically [in my mind at least], you are trying to "pretend" that the phone is on a phone call when it is really just using data and other resources of the phone all combined to seem like a phone call. I've had other issues with volume (ringer vs. in-call) when using SIP clients because of that very reason. 3CX supports bluetooth but doesn't flag it as experimental.
Please post questions in Q&A section.
Whosdaman said:
Please post questions in Q&A section.
Click to expand...
Click to collapse
The OP was posting a problem, not an inquiry.
So, after some hunting and tweaking I seem to have found at the very least an answer (maybe).
After rooting the phone I seem to not be having the issue of bluetooth causing reboots after it is turned off. Not sure what that means but I have tried to replicate the problem and have been unable to so far.
Ok I have been experiencing the same issue.
However this is my situation.
I never experienced this until I installed Bluetooth Audio Widget.
A handy app that routes all audio to the BT headset, so you can listen to music on your mono headset. They do state that in all froyo versions it has a known issue where if you shut the headset off before disabling BT it will cause a reboot.
I have used the app for several months knowing this and not having a problem with that glitch. However after awhile it became an issue where it would reboot regardless of the order that you would shut them off.
And all that took place ONLY after enabling the widget.
In just the past week+ it has now been causing the reboot issue no matter what.
It will now reboot regardless of my enabling the widget or not.
Walk out of range of the phone with the headset enabled and it causes a reboot.
Turn off the headset-reboot
turn off BT-reboot
This used to only take place AFTER I had enabled the Bluetooth Audio Widget.
It was an acceptable glitch when it was just caused by the widget.
Now it's become unacceptable.
This is on a stock MT4g non rooted.
with a Plantronics Explorer 240