When my phone is asleep (on the seat of my car), if I push the call button on my bluetooth headset, I get beeps and hear the prompt to speak the name - but nothing happens after that.
If I then wake my phone (with trackball or powerbutton), the phone immediately dials the number and makes the call.
I am using trackball wake on a custon FRF91 ROM. This seems to happen with a couple different ROMs I've tried.
Anyone else seeing this? Does this happen with stock? Any workarounds?
It would be more "handsfree" if I didn't have to grab the phone and wake it first.
Related
I love this bluetooth headset. I was in a really noisy resturant, my friend could not even hear the noise on the other end. This jawbone has some serious noise cancelling technologies. Then I went into the bathroom where the music was insanely loud (mexican mariachi stuff) and still friend couldn't hear any music at all.
Weird but cool.
But when I press the button on my headset to hang up a call, it tries to open up the voice recorder/voice calling app on the tytn2. Very annoying.
Do any of you know how turn off this feature? I just want to stop the call. Thanks.
All I can say is that it isn't normal behavior...sorry.
I see that behavior all the time with 2 Jawbones, push button to end call, the call ends but voice dialer opens. I just keep quiet and it cancels itself, very irritating I agree.
RemE said:
I see that behavior all the time with 2 Jawbones, push button to end call, the call ends but voice dialer opens. I just keep quiet and it cancels itself, very irritating I agree.
Click to expand...
Click to collapse
Never heard of that problem. MAybe its the dialer or even the rom ur using to cause this problem? Have u tried a different rom with ur bluetooth? Also try to install a different dialer and see if that helps. My jawbone works perfect on my att tilt!
deeznuts said:
Never heard of that problem. MAybe its the dialer or even the rom ur using to cause this problem? Have u tried a different rom with ur bluetooth? Also try to install a different dialer and see if that helps. My jawbone works perfect on my att tilt!
Click to expand...
Click to collapse
You using stock ROM or custom ROM?
this happens to mine as well. From what I've observed, it seem like a delay of some sort when you press the button to hang up, and then the call has already hung up on the other end, and instead of hanging up the call, the phone will just turn on the voice dialer.
it is almost certainly what fakts13 posted as a cause. I've never seen mine launch the voice recorder when hanging up from a call.
It is exactly what fakts13 said. A single button press on the Jawbone can answer or hang up a phone call, but it will also activate voice dialing if no phone call is active. The only problem that you are experiencing is that your other caller is hanging up before you, so there is no active call whenever you press the button on your Jawbone. Since there is no active call, the button press launches Voice Dial on your TyTN II. You could always disable Voice Dial altogether if you never use it.
anybody know of any freeware to do this? I searched around a little but no luck.
Huh. Can you expand on this a little please. So I know what Im looking for?
I think he means he wants bluetooth to be turned on automatically with incoming calls so he can use his headset, and afterwards for it to go back off to save battery.
Sounds like it would be useful, I'm interested too... if anybody knows...
I use a H300 motorola BTooth device as hands free. Since I don't want it to continuously transmit when I'm having it on my ear, I keep it switched off. When the phone rings I push the button to power it on and automatically as it powers on, it answers the call. When I finish I just push the button to power it off.
By that I mean that you can actually power on and off the BT everytime you receive a call. It doesn't have to be automatically powered on and off by itself.
Probably more than you want but phoneAlarm http://www.pocketmax.net/phoneAlarm.html does what you want. My experience though is that it takes too long for Bluetooth to turn on. Not too long that you miss the call but a good few extra rings.
Joe
I'll be darn if I can figure out what is going on here.
4.1.2, stock except for custom kernel brick bug prevention.
I've had this rom running since it was released (this is a note international, GBT via amazon, used in the states)
Never had an issue, but I've started to notice a couple missed calls. Today, I saw what was happening.
Incoming calls, the ringer only rings for maybe 1/2 second, phone continues to "ring" but you never hear
anything! It's like it has been silenced as if you quickly pressed a button. That's how it acts without bluetooth.
If I have my bluetooth (jawbone ERA) turned on, SOMETIMES, if the screen is off, it NEVER rings, on the speakerphone
I'm using to dial my Note, I hear it ring 2 times, then go directly to voicemail. Sometimes it does that, sometimes it does
not, otherwise, the phone ringtone plays for a split second, headset continues to ring normally. Screen shows the incoming
call, but no ringtone. I haven't tweaked, installed, updated anything to cause this. Just one day it started doing it.
I'm about to do a clear reset, but it's just a PITA to set it up. Device is going on 18 months old, first issue I've really had
with it other than a bad USB port or a worn battery.
Any clues?
edit: Found the issue...I use call control as a phone number blocker. In settings, I had on for blocked calls, "remove partial ring" turned on. Once that was turned off, everything started working.
I'll be on a call and the other person will suddenly be unable to hear me. This happens with stock and Pure Nexus (running on both elemental and shamu). It doesn't happen regularly. It hasn't happened in weeks, but yesterday it happened twice on one phone call and once on another. I can fix it during the call if I mute and unmute the phone on the display. When the phone mutes itself, the display control doesn't show that mute is active, only I after I press it and "activate" it.
I used to think it might have been my face pressing against the screen, but that can't be it as the screen is off while I'm talking. In order to fix it during a call, I have to turn the screen on first. Has anyone else had this problem?
I had this problem and found call screen lock in the play store (which solved it). It turned out I was somehow tapping mute with my face while on the phone after not tripping the proximity sensor...
It only happened rarely, but you can tell if you might be doing this if your screen occasionally wakes up while on the call without being pulled away from your face (the proximity sensor thinks it is not close to you face intermittently).
I use the phone a lot handsfree for work and it bugs me when the screen times out and locks on a handsfree call. I can't then easily mute, unmute, look at call durations, enter digits etc. without interacting with the phone in a clunky manner.
As an example i might be on a long conference call on speakerphone, mute my audio input to get up and walk around a little and then have to quickly unmute. To do this i have to press the side volume button and then the on screen unmute which sounds easy but can make for an awkward second or so of silence.
Basically i want the screen to stay on when in call and the proximity sensor detects it's not against my face.
Samsung has a phone app option for this i remember (keep screen on during calls).
Any suggestions ?
orbital247 said:
Any suggestions ?
Click to expand...
Click to collapse
Use a bluetooth earpiece/headset and add that as a trusted device. All the time it is on and connected the phone won't lock. Then just set screen sleep to something more appropriate like 5 minutes..
you could try something like this:
https://play.google.com/store/apps/details?id=com.ndtsoft.sensor&hl=en
i haven't tried it, but i think it could solve your problem
EDIT: i just tried an app called "WaveUP" and it did the trick. also has a lot of other cool features, as well.