Re: Atrix not waking up when Bluetooth button pressed after GB up
I also have the Motorola Atrix and a Bose Bluetooth earpiece that has ceased working since the
upgrade to 2.3.4. Before the upgrade everything worked perfectly. When I would punch the button on the earpiece the phone would come out of standby and say:
"Please say a command".
After the upgrade it will not take the phone out of standby. I punch the button on the headset and I hear a beep but that is all. I have to get the phone out of my holster and manually take it out of standby by pressing the power button, then it will ask for a command. Totally defeats the purpose of handsfree Bluetooth.
I have called Motorola 4 times, we have deleted the connection, re- paired, same thing.
I have taken the headset to AT&T store and paired it with another phone that had the new upgrade on it and got the exact same results, it would not bring the phone out of standby.
I called Bose and shared the problem and said I thought it was a compatibility issue, so they are sending a new headset.
However it is NOT the headset, because after I returned the headset to them and was waiting on the new Bose headset I took out an old Jawbone headset, charged it up and paired it up with the phone, and got the exact same problem with a different headset. The Bluetooth Jawbone could not bring the phone out of standby.
SOOOOOOOOOOOO, my contention is that this is an operating system issue. That something occurred in the settings after the upgrade that is preventing the phone from working with the Bluetooth. I wrote on the Android Platform's Forum with the following, " I would appreciate it if you would do some testing with Bluetooth earpieces and find out what the issue is and let me know if there is going to be a patch or fix in the near future. This is very dissatisfactory as I need my headset for handsfree operation in the car. " and got no answer. So sad that they won't at least acknowledge there is an issue and they are aware and maybe attempting a patch. Sure would go a long way in giving us users some peace of mind to know they are working on the issue. I have tested and did all the trouble shooting to totally convince myself that it is not the phone, it is not the earpiece, it is Android.
If anyone has any good news about this subject please let us know.
Thanks
texaseagle46