My HD2's VIBRATE function has been on and off ever since I installed ENERGY ROM. It will initially work, but make a weird sounding, not normal, sound for a while, and then just stop working completely.
Does anybody know a possible solution to this?
Thanks!
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
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 ?
for some reason recently my google maps and waze no longer mutes the audio of any music playing when it gives turn by turn directions. it used to work just fine, whenever it would start the give directions it would mute my music. any one else have this problem ...or have a fix?
Waze should still have a configuration setting to mute it; Maps this seems to be an app change as I noticed this as well. There is a setting once you are in a route where you can set it to mute during calls, I have not found any other option for muting.
weird. this is a recent thing for me. i never had to make any change in any app or do anything before. this really just started happening about a week ago for me.
While driving, I use Google Maps or Waze and make phone call using my bluetooth headset. During the call my GPS stops.
My Nexus is rooted and I faced this issue on different ROMs (Stock and Custom).
Anybody had this issue before? What's fix?
If that happens on both stock and custom ROMs there's a pretty good chance it's a hardware problem in which case there is no fix that is practical given the value and age of the phone. One thing you could try is to put your phone in safe mode and see if the behavior stops. If it does stop then an app you installed is causing an issue. If it keeps happening then you probably have a hardware problem.