• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Bluetooth will not wake up Atrix 4G if screen locked

I'm sorry, I had to chime in on this as there is a lot of misinformation in this thread.

First of all, BT Handsfree Voice Dialing was introduced to Android in 2.2 FroYo, as was the Slide-to-unlock; I know this because I researched this in depth and upgraded from one Android phone to another specifically for BT voice dial. The Atrix had Slide-to-unlock out of the box when it shipped with 2.2.1, this problem has nothing to do with the wake to voice dial as it's not a "new" implementation.

In FroYo on the Atrix the BT Voice Dial from a "locked state" worked fine for most headsets, but not all, especially older some ones. I upgraded to a Motorola H790 and it worked well from a locked state, with the Slide-to-unlock feature enabled. The only option that it would not work with was the fingerprint scanner, which was understandable.

The issues you have found dating back to 2009 were simply because Android as an OS did not support hands-free VD period until 2.2. But it does now. Other Gingerbread phones don't have an issue with it. Motorola *tried* to bypass the fingerprint scanner security with an option in the setting in their 2.3.4 update and it *broke* what had previously worked.

Very few people care about the hands-free cell phone laws, and there are states that don't even have them. On another forum for which I have been a moderator for since before the release of the Atrix, we have over 7,000 Atrix users and I would estimate only 10-20% even use BT, let alone BT voice dialing. Your assumption that there should be "millions" of users complaining about this is just incorrect.

This has nothing to do with a third party app, a battery setting, or a Wifi/BT setting. It is a problem that has been acknowledged by Motorola employees as an unintended issue and they are looking into it. Period. There isn't a promised fix, but don't write it off to user error or "just the way it is." Please stop spreading misinformation, it doesn't help anyone.
 
das8nt said:
Please stop spreading misinformation, it doesn't help anyone.
Click to expand...

Everything I've stated about the technical issue has a link to back it up. Perhaps you should READ the links. My information came directly from them.

You also mis-quote me and take part of what I said out of context. I never said THIS issue would have millions of people complaining. I was stating that actual bugs in the build effects MILLIONS of people.

You also take my information about percentages using BT out of context as well.

So, who's spreading misinformation??
 
das8nt said:
The Atrix had Slide-to-unlock out of the box when it shipped with 2.2.1, this problem has nothing to do with the wake to voice dial as it's not a "new" implementation.
Click to expand...

There was a graphical slider on the lock screen. But, if you didn't put a security measure on the phone in FroYo, it didn't LOCK the system functionally. In other words, without a security measure (fingerprint, pin or pattern), the slide to lock was as functional as nipples on a man.

In GB, that function changed. Even without a security measure, the phone goes into a Locked state when the screen goes off.

In a locked state, only emergency calls are allowed until you unlock. Since it was not locked in that state on FroYo, the Voice Dialing worked. But, since GB fully locks it, it does not allow voice dialing until you slide to unlock and release it.

There is a difference between how the two function.

I can provide you with many more links replicating this problem across different devices.
Both, since GB came out, people having it without a security measure. And, before GB people having this problem with a security measure.

Please take the time to FULLY read all of the links I posted. Not just the first few posts.

As for the Motorola thread you linked to, most of those people are having issues with the BT in general, not powering back on. That very thread was what originally had me wondering if it was a power saving issue. Especially as some users would have BT come on for a few seconds and go back off. Very similar to what the OP here posts. In fact, if you pay attention, you will notice he's already posted in that thread (Last post on the page you link to).
 
chandler48

I came across something else that struck me as a difference between us as several people on other forums suggested using VLINGO instead of the default. Since I used Vlingo for years on my BB, I did set that on my phone and recommend it.

You should have the Vlingo app installed stock (I can't remember if it's stock or not since it's on my list to always have anyway). If not, grab it from the market, it's free.

IN the phone settings, go to "Voice input & output settings" and for the "Voice recognizer" set it to Vlingo.

In the vlingo app, go into settings, and in advanced settings, turn on "Listen over bluetooth."

You can also enable the "In Car" mode in Vlingo as it FORCES the BT to stay on because it listens for you to say "Hey Vlingo" - I've never used that, but I've heard that it will drain your battery.

And for those that say this is ONLY an Atrix issue, and no other GB phone has this problem... I found this tip for people having this issue on the Nexus S on GB.
 
WolfmanRobby said:
Everything I've stated about the technical issue has a link to back it up. Perhaps you should READ the links. My information came directly from them.

You also mis-quote me and take part of what I said out of context. I never said THIS issue would have millions of people complaining. I was stating that actual bugs in the build effects MILLIONS of people.

You also take my information about percentages using BT out of context as well.

So, who's spreading misinformation??
Click to expand...

I believe you are as you can't even recall what you have said.

Did you not say this in reference to THIS specific issue:
That does not mean it's a problem with EVERY phone, and a problem with the GB update itself. Sure, you see dozens of posts about people having issues. What you don't see is MILLIONS of Atrix users that don't bother to come online and say they are not having a problem.
Click to expand...


I don't believe I took you out of context at all as this statement clearly says you believe 90% of all Atrix users would complain about an issue. Does this not infer that you believe 90% of Atrix users use BT Voice Dialing?

Another reason why I don't believe this is the GB update...

I've been doing this for YEARS on the BlackBerry, Windows Mobile and Android platforms. When there is a BUG or FLAW in an OS release, it effects all of the devices in some way. Maybe some users don't notice it, but it effects them. You wind up with 90% of the people complaining about the issue.

I've seen a small fraction of Atrix users complaining about post GB update BT issues. I'm talking less than 5% of the total units sold.
And, so far, everyone that I've talked to, we've found that is was something with absolutely no relation to the GB update. From their BT hardware, to settings, to 3rd party apps on the phone.
Click to expand...

Your less than 5% of units sold fits right in with my deduction that very few actually use the BT VD and would notice this issue.
 
WolfmanRobby said:
There was a graphical slider on the lock screen. But, if you didn't put a security measure on the phone in FroYo, it didn't LOCK the system functionally. In other words, without a security measure (fingerprint, pin or pattern), the slide to lock was as functional as nipples on a man.

In GB, that function changed. Even without a security measure, the phone goes into a Locked state when the screen goes off.

In a locked state, only emergency calls are allowed until you unlock. Since it was not locked in that state on FroYo, the Voice Dialing worked. But, since GB fully locks it, it does not allow voice dialing until you slide to unlock and release it.

There is a difference between how the two function.

I can provide you with many more links replicating this problem across different devices.
Both, since GB came out, people having it without a security measure. And, before GB people having this problem with a security measure.

Please take the time to FULLY read all of the links I posted. Not just the first few posts.

As for the Motorola thread you linked to, most of those people are having issues with the BT in general, not powering back on. That very thread was what originally had me wondering if it was a power saving issue. Especially as some users would have BT come on for a few seconds and go back off. Very similar to what the OP here posts. In fact, if you pay attention, you will notice he's already posted in that thread (Last post on the page you link to).
Click to expand...

Your description of how the screen locks on GB makes no sense. The BT VD WORKS if the screen is lit and the lock is still on. It's only when the screen is OFF does it not work. In your explanation, how would you be able to make emergency calls if the screen was OFF? You can do NOTHING with the screen off. Do you mean when the screen is ON but LOCKED? Because you CAN BT VD with the screen ON and LOCKED.

Just please accept the fact that your assumptions are incorrect and let it rest. There IS a fix for it, but it's up to Motorola as to if we ever see it.

By the way. I Have Read Everything. It makes no case in your favor. The point is that it WORKED for 5 months on the Atrix and now it doesn't; that's it. It can work, it's works on other GB phones.

Arguing with you is pointless because you're arguing non-points. I'm done and hope you'll concede as well. It's pointless.


Edit: No Lock isn't ans "answer" it's simply a workaround that shouldn't be needed. My co-workers' DroidX (2) and OG Droid, all with GB, work fine with the the phone screen off, locked and in their pocket. There is NO REASON our's shouldn't as well.
 
das8nt - I'm not going to argue with you because you are twisting words around.

Those posts you quote of mine, you left out parts. Like I how I said it works on the 7 Atrix units I have hands one with, all running GB.

It's not an ASSUMPTION. Voice Dialing by BT with the screen off does work on GB as long as the phone is not locked. I can do it with mine right now. My fiance can do it on hers. Both of her kids can do it on theirs. I've seen it work on 7 units. That's not an assumption, that's first hand working knowledge.

As far as I can tell it has to do with either the fact that we use the NO LOCK app to bypass the locked "Emergency calls only" or that we use VLINGO that's always listening.

Heck that last link you just posted, if you acutally READ it, someone there says they got it to work by just holding their Headset button longer.

And, if you will take 2 seconds and google "Android Gingerbread Voice Dial Screen Lock" - you will find OTHER people having this issue on OTHER model phones, not just the Atrix. The common fixes mentioned were:
-on GB, Use No lock and Vlingo (What I've suggested here
-on FroYo, just disable the security features (Fingerprint, pin, pattern...)

But, you seem to think you know everything. Instead of offering up help to the OP, you just want to argue.
 
For anyone else reading this, I've contacted Mark through the Motorola forums about this issue. I've worked with him on the SOAK program.

I've given him details on my phone, and that it does work. And, I've told him to pass my contact info on to the engineers working on the issue to contact me to compare my settings to someone that is having the problem.
 
Well, for those CLAIMING that no other GB based phone has this this issue...
https://supportforums.motorola.com/message/472447#472447

You'll see, as I've stated, people with the Nexus S have this as well.

So, it' not something specific to the GB update on the Atrix. That's not to say it's not a GB issue. But, if it is, it's a general issue from Google, and not so much something Motorola broke. That means it's less likely something Motorola will be able to fix. But, more likely an OS update is going to have to come down the line from Google.

This also furthers my (and other peoples) opinion that it's related to how the GB update handles the lock screen. It's doing more than just turning off the screen.
 
Has anyone found a solution to this problem? I'm having the exact same problem indicated. Voice dialing used to work perfectly for me. In the last few weeks, if the screen is dark and I tap the BT call button, nothing happens. If I then push the power button (even 10 minutes later) to bring the screen back to life, the Atrix says, "please say a command." Until a few weeks ago, pressing the BT call button would automatically bring the screen back to life without my first having to press the power button. Now pushing the BT call button only causes the screen to do a quick flash and go back to dark.

I am using the Atrix with a Plantronics Voyager Pro+, Jawbone II and a Jabra SP700 (not all at the same time). The problem is the same with all devices. I'm a long distance commuter (150 miles round trip on interstate highways) and voice dialing is really important - especially while I'm in Maryland where just touching a cellphone can get you a ticket.

Any solutions???
 
rhmerriman said:
Has anyone found a solution to this problem?
Click to expand...

From the last reports over on the Motorola support forums, there has not been a fix.

Speculation is that they released a batch (Or several batches) of phones with bad chips in them that flaked out with the GB update. If that's the case, there is no fix.
 
I am experiencing the same problem as well. I do not get it as often, since my phone is usually docked when I am driving. But when the phone is in its case, and I go to voice dial, I have to pull the phone out of the case and hit power to get prompted. I have both a Plantronics Voyager Pro headset, and a Jabra BT8010 which I keep around as a spare, and if I want to hear music in stereo.

There is one thing I seem to remember about the last update to the OS. I got a prompt once about this, If I wanted voice dialing with the screen off. I don't know why I said NO, but I did. I have not been able to find that menu choice again, anywhere.

I am going to unpair everything, and try setting up one headset again, just to see if I can find that menu again. I will report back on what I find.

Thanks!
 
No dice:
- made sure all headsets were off.
- did a factory reset on the BT8010
- UnPaired all headsets
- rebooted phone
- paired just the BT8010
- No extra menu appeared.
- problem still exists.

Oh Well, on to Plan B
 
Hold button on headset until you hear the tone indicating redial.
Immediately release and press button to hang up before phone dials.
Phone is now awake.
Press button on bluetooth and wait for the prompt.
Not as quick as you'd like, but it is hands free.
 
Mines work fine. I press and hold the blutooth button until I hear a beep, release button, then hear a second beep and then voice commands. This only works with the stock lock screen though.
 
I know it is late in the game, but since I had a dog in the fight, it seems the fix came with system update 4.5.141
Motorola problem? Android problem? Whose "system".
 
You must log in or register to reply here.
Back
Top Bottom