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
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?
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.
Hello,
I have not seen a thread on this nor has Google searches helped but I have an issue I wanted to post to see if anyone else was having the issue.
I use my phone for work and often have it on speaker phone, out of no where the call goes quite and the person on the other end of the call can not hear me anymore. Upon looking at the phone the speaker phone seems to get disabled and the call goes back to the handset. This happens often when using the speakerphone but certain calls are worse then others.
In one call I had the speaker phone get disabled about 10 times which was close to every 30 seconds or so. This is very very annoying, I have also rebooted the phone. At this time I am not modded and have less then ten apps installed and I am pretty sure none of the apps I installed are causing the issue.
I will note that I do have the phone connected to bluetooth a lot and when the issue happened I tried to disable the bluetooth while on the call but the issue persisted.
Is anyone else experiencing this issue?
Speaker phone and Bluetooth turning off at random
I am having the exact same problem. But for me this happens with Bluetooth and speakerphone. This is getting really frustrating for me and potentially dangerous when I try to switch back to Bluetooth while driving.
Have you figured out a solution for this yet ?
Whenever I connect to one of my Bluetooth devices it shows that it's "Connected to xxxxx" in the secondary screen.
However, after I disconnect from the Bluetooth device it still says its connected in the secondary screen and the secondary screen just hangs there frozen saying its connected. I can only get rid of it by restarting the device.
Anyone else having this issue?
I'm experiencing this issue. I think it started happening after applying the latest update.
to fix it w/o restarting the device, you can go to settings - display - second screen and turn off 'show when main screen on' and back on.
I have this and all kinds of BT issues with my car.
Bluetooth has given me a lot of problems. Secondary screen stuck displaying the "connected" message, Bluetooth crashing, and high CPU usage when not connected. I've had better experience by toggling Bluetooth off and on with Tasker after disconnecting from my car. Figure it gives it a kick causing it to play nice.
McNutnut said:
Bluetooth has given me a lot of problems. Secondary screen stuck displaying the "connected" message, Bluetooth crashing, and high CPU usage when not connected. I've had better experience by toggling Bluetooth off and on with Tasker after disconnecting from my car. Figure it gives it a kick causing it to play nice.
Click to expand...
Click to collapse
So it's not just me having bluetooth issues lately. I was getting ready to drop by AT&T because of all the problems it''s been giving me lately connecting to things on bluetooth...
Mine has recently started doing the same thing with second screen stuck on connected to vehicle Bluetooth. I do remember updating recently so I am unsure what cause this issue. I am using stock with ATT
peekeesh said:
to fix it w/o restarting the device, you can go to settings - display - second screen and turn off 'show when main screen on' and back on.
Click to expand...
Click to collapse
I tried this trick and it only works temporarily. After an hour or so the same connection message will appear even though I'm not connected. So annoying. Come on LG! I like their devices but there is always some annoying issues with their phones.
Are you guys also experiencing general notification issues?
Example, I click on a Twitter or Kijiji notification and the app won't open or I can't respond within the notification shade any more.
See https://forum.xda-developers.com/showpost.php?p=72734315&postcount=10
I'm wondering if this is the cause of everyone else's bluetooth/notification issues. Worth a shot.
Ever since I upgraded to 10K from 10J on T-Mobile it has started doing this. Once I am connected I never have a problem with Bluetooth but connecting has been inconsistent ever since upgrading. My car stereo for example used to connect automatically now to get it to reconnect I have to turn off the stereo and the Bluetooth radio on my phone and then both back on @ same time otherwise I have to manually connect through the phone BT menu
Been having issues with bluetooth too. I've gotten into the habit of just turning it off after I get out of the car, then turning it on right before I get back in the car. If I leave it on all the time it fails to connect about half the time I turn on the car, if not more. Strangely I don't have the same issue with my Anker speakers, so I sort of assumed the car was the problem, but it seems not from these comments
McNutnut said:
See https://forum.xda-developers.com/showpost.php?p=72734315&postcount=10
I'm wondering if this is the cause of everyone else's bluetooth/notification issues. Worth a shot.
Click to expand...
Click to collapse
This seems to have fixed it for me! I had the same issue after updating my phone to the latest build.
thisisjason said:
Been having issues with bluetooth too. I've gotten into the habit of just turning it off after I get out of the car, then turning it on right before I get back in the car. If I leave it on all the time it fails to connect about half the time I turn on the car, if not more. Strangely I don't have the same issue with my Anker speakers, so I sort of assumed the car was the problem, but it seems not from these comments
Click to expand...
Click to collapse
Same exact issue. It only seems to happen to my car stereo since I upgraded to 10K. But my other speakers and headsets 99% of the time it will connect by itself.
Same issue here. Super annoying. Appears to have shown up around the same time that all my notifications stopped working.
I've been having the same issue. I use Car Home Ultra, and noticed that it was very delayed starting, and would start randomly even after leaving my car/disconnecting bluetooth. I thought it was a problem with that app, but now it appears it's that the phone is delayed in notifying of bluetooth connect/disconnect.
I constantly have the "connected" notification taking up the second screen until I reboot.
I am experiencing this aswell, and , when connecting to my SYNC 3 in my Ford Focus, it says connected, but it isn't. If someone rings me, the hand set rings.
It seems to be the initial handshake, if the phone's bluetooth is off when i turn car on, then i turn blutooth on and select "sync 3" it's all good, but if bluetooth is already on , and i switch car on , i get the message on the radio it's connected to my phone... but i cant access contacts or messages ( even though they are ticked in bluetooth menu )...
lucky for the 2 year warranty...
Disabling the Google app has fixed this issue and fixed my push notifications. Not ideal but doesn't appear any other answer exists.
Anybody have any updates on this issue? I have been having the connected message showing more frequently to my vehicles. I have been turning off second display and back on to remove. Thanks for the suggestion Adam about disabling Google app but like you said it is not ideal.
So on Verizon they just pushed a system update. Post update, I enabled Google app, and everything appears to be working great thus far.
I don't remember when but the issue just kind of went away without any action on my part. Maybe it was an update?