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.
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?
Hey all, im glad this site is up its been great finding what i can really do with my wizard!
here is he issue im having. the wizard has 3 different speakers and 1 microphone. 2 side speakers (used to play music, or speaker phone) and the 1 main speaker (used for hearing calls). none of the 3 work when im making calls, listening to music, alarms, or any of the "screen click" sounds and the microphone doesnt work on phone calls or note recordings. however, the one time the speakers do work is when i have an incoming call, i tried listening to see which speaker its coming out of and it sounds like all 3. the headphone jack still works so thats what ive been using. pressing the speaker phone button while on a call (that i cant hear) doesnt do anything, the UI doesnt show any change or switch to indicate its changed to speaker phone and the "speaker on" button doesnt change to "speaker off" like it used to.
originally i thought this was a ROM issue, i was using the manufacturer's ROM (cingular 8125, unlocked for tmobile service) so i followed the lovely tutorial and switched my phone over to the t-mobile 2.26 ROM. this had no effect, so I then upgraded to XDA's WM6 ROM and while i love this new ROM it still did not fix my sound issue.
im stumped, any help anyone can offer would be great. I wanted to post here before i crack it open to look at all the insides.
same problem!
I'm having the exact same problem! I just noticed the problem recently, when my phones alarm didn't sound. I'm running a custom cooked rom from mattk_r 318 kitchen, but I don't think the rom is the problem, as i am indeed still hearing sound from the head phone jack. I don't think the internal speakers are broken, as when a call comes, the phone rings, and the sound come out from the speaks as mentioned above!
Help!
dropped?
have you ever dropped your phone?
I have dropped mine a couple times and thats the only cause I can come up with. But this never seemed to be a problem until recently.
no major drop recently.
i havent really dropped it recently at all.and for some reason i dont think the hardware is the problem,because i tryed voice recorder,and it records my voice and i can play it
back through the headset.so that confirms that the mic and both spealers work (rings
when incoming call). i really dont want this to be the downfall for my wizard! is there
any key registry entrys for sound maybe that we could have a look at? btw my wizards a G4 if thats makes any difference.
please help!!
mine is a g3, if it were a software issue then reflashing should have solved it. right? i dont know enough about the internal workings of the wizard to know what a flash actually does.
?
Anyone have any ideas on what I can try?
Well, a flash is an OS upgrade/downgrade. It contains drivers, programs, registry settings, things of that sort. Sounds like your problem is hardware related, nothing to do with the OS itself.
I assume the warranty on that baby has already expired, so you're pretty much on your own.
Two options come to mind:
1. The obvious... buy another Wizard
2. The not so obvious... buy another Wizard with a broken screen and take all of its guts out and put them in yours.
A third option also exists... (ther's always a third way)
Mind you, this is for INFORMATION PURPOSES ONLY! In no way do I condone the below mentioned method.
Get a new line of service with Cingular and buy the Wizard to use with it. Exchange their boards, swap the IMEIs using the Wizard Service Tool utility found on these boards, cancel the line of service and return the "new" Wizard.
Sound issues
I have had a similar problem but located my problem to the microswitch which is in the headphone socket. Might be worth trying pulling the headphones in and out a few times to see if it allows the microswitch to release (if that is the problem?)
Steve
The wizard is magic
Some how my wizard seemed to repair it self. Its sound is working again...i didn't reflash or do anything special....weird. I think its because the phone had a good vibrate....ive got one of those speaker docks for the wizard..i put it in there...got a phone call and talked and stuff...but while it was in there (with the mic plugged it) it vibrated alot...maybe that flicked the switch mentioned above?
weird..this phone never ceases to amaze me. I just hope it doesn't happen again... because it appears to be emerging as a problem as the wizards get older?
Keep up the good work guys!
LOL!!!!!!!!! its so simple and yet so amazingly smart
wow, Steve you are the most amazing person EVER!
I put the headphone piece in about 1/10 of the way and slowly made a swirling action as i slid it all the way in, clicked the start button on wizard and i heard the "click" for the first time in a month!
Thanks!
I tried different options to get my sound back, no luck so far
Problem started after using the headset-connector to connect it to an FM-Transmitter.
After reading this thread, my guess is that the "micro-switch" is in a wrong position. So I opend my MDA, but can't find any "switch" in that connector.
Is there some more info about that connector, a connection-diagram perhaps ?
what worked for me was inserting the headset jack in roughly, robbing each side of the headset jack to try to hit the "switch". that might work for you.
Yes!!! Thank you a lot!
I have the same problem, no sound in my speakers, just vibrate and sound in handsfree. I figure out that this micro-switch could be the problem, but I haven't know how to solve it. Thank you once again, I love my SPV!! and this community.
Fixed!
Woohoo!
This problem just cropped up for me on the weekend.
Thankfully it wasn't long before I happened across this thread.
About a minute of persistent jiggling the microphone jack did the trick.
Thanks!
Hi all
Sorry, if this has been answered before. I've searched about an hour now in the forums, but couldn't find any solution.
I have a TyTN II and a Motorola BT headset H700C. This combination worked like a charm so far.
Today suddenly, I cannot start or take over incoming calls anymore.
Analysing the problem I detected, that my headset is suddenly only available as a hands-free device instead of a headset device to my phone.
So I repeatedly tried to delete pairing information and re-pairing the headset to the phone, but no success. I always only get it as a hands-free.
The strange thing is, that I'm not aware of any config changes or newly installed software on my phone. Still I suddenly have this weird behaviour.
Does anybody have a hint for me? Would appreciate any, so I can get my headset back to proper functionality again.
Thanks
McYoda
mcyoda from urt? lol.
Hey i just saw an update on the HTC website that addresses a bluetooth issue.
You have to sign up and all that good ****. Then select your device. Theres also a camera fix if you were getting the maze pattern.
I have all sorts of connection issues w/ my motorolla s99 im constantly having to repair it seems when i use the wall plug. IF both items are charged fully, i can walk away (out of distance) music will stop, and when i get close enough it repairs automatically. Something has bugged me out for sure, still working on my issues. (thinking charging the bluetooth on the car charger might be ****ing it up).
Ok so I'm trying to trace down what might be happening here.
Ive got a LG Tone Pro 750 BT headset which I totally love for the most part (epic battery time for one thing). Bought it about a month ago.
About a week ago, maybe two, something weird starts happening. I'll get a call, pick it up and no sound. Caller may or may not hear me, but if they do, it appears to be garbled (I've done a poor job of asking callers if they could hear me and inquiring about that part of the experience so not very good feedback there).
Since I'd had the BT headset for a couple weeks already, I don't even consider there could be a problemo there. So I take the SG4 to Sprint and have a tech check it out.
He comes out to see me (never happens).
Asks me if I have the LG Tone Pro headset. He then proceeds to tell me that he has the same problem on his LG (!) phone with that headset (although it's a later model than my Tone Pro 750...next one up from that model).
He says that the only way he has been able to fix it is by unpairing and re-pairing the headset. Says he has to do it every other day or so.
That was early last week.
So for the next day or two, I go without the headset being re-paired. All is well with the three or four calls I get.
I pair the headset but don't get any calls. I do listen to some podcasts and that is fine (but was never a problem so no change there).
The next day (this morning) I get a call. Problem is back. I try turning off BT making calls and that doesn't fix it. Have to restart the phone.
So I do and I can now make and receive calls. However, BT is off.
It sure looks like this is a problem with the headset.
But I also noticed a preponderance of SG4 owners complaining about a somewhat similar issue where the mic would suddenly turn off on their phone, mid call. Seems WIFI signals would somehow interfere with it (I tried turning off WIFI though and that didn't fix it).
Is there anything else I can do to diagnose this better and maybe get to the bottom of it?
What could be happening here? Is this the headset not playing well with the OS? Is there a way to tell?
Why would this start happening off a sudden two weeks after I'd been using it heavily with no problems?
Also, I'm trying to find more instances of this issue online but it's tough one to Google.
(As a side note, LG doesn't seem to be a very good company when it comes to customer service. I saw several instances on Android Central where their customers reported issues with the headset and then were told their posting violated the TOS of the forum. WTF is up with that? Have they not realized there is ths thing called the Internet? Do they think people won't eventually catch on? )
I'm seriously considering returning this thing, but the truth is, I really want to keep it if I can get it to work. Probably a pipe dream though, now that I've written all this out. lol
I'm even considering rooting my SG4 and throwing another ROM on to see if that fixes it. That's how much I like the headset.
Happy to receive any feedback from fellow forum members. Thanks in advance.
PS: Just realized I haven't really tried just unpairing and re-pairing more than once so I'm going to test that some more over next few days meanwhile...
I am having the same problem but with different headset (MOW and Jabra).
One thing that I tied worked but I can only use my headset to listen to music. In each headset setting located in the Bluetooth pairing list, I uncheck the CALL AUDIO and leave the MEDIA AUDIO check. This allows me to use my headset for music but not calls.
A complete fix would be great, please?
BT media audio works, phone audio fails
readable said:
I am having the same problem but with different headset (MOW and Jabra).
One thing that I tied worked but I can only use my headset to listen to music. In each headset setting located in the Bluetooth pairing list, I uncheck the CALL AUDIO and leave the MEDIA AUDIO check. This allows me to use my headset for music but not calls.
A complete fix would be great, please?
Click to expand...
Click to collapse
Glad you posted this because I hadn't even thought to try, as part of my troubleshooting, whether I could still play media on the phone through the headset when call audio was not coming through.
Last night I made a couple of calls just fine with my LG Tone Ultra (upgraded to see if this fixed the problem, but no change) and then made a third one. On this third one I could not hear any sound but the call connected (it was to my wife--she later told me she got a call but no sound on her end either).
So this is very strange. Somehow the BT headset is just dropping the call side of the audio.
And, it's doing so randomly.
Sure would like some more insight on what is likely the cause of this situation. I submitted a question to LG through their website but no response. That was days ago.
Chapter 2 of this problem
readable said:
I am having the same problem but with different headset (MOW and Jabra).
One thing that I tied worked but I can only use my headset to listen to music. In each headset setting located in the Bluetooth pairing list, I uncheck the CALL AUDIO and leave the MEDIA AUDIO check. This allows me to use my headset for music but not calls.
A complete fix would be great, please?
Click to expand...
Click to collapse
Just posted a new thread on this issue with some log data that I'm hoping a kindly dev may help decipher.
Letting you know in case you want to keep an eye on that thread as well.