Hi Guys,
Just got my S110, which I love. Still trying to learn how different the phone functions are, compared to my C500, one thing I have noticed, and which I feel is a real pain is to do with the suppled headset and its intergration with mobile 2003.
It seems to be fine at answering calls - a quick tap, and that is it, but when it comes to ending a call, i have to hold the button for 3 seconds, and there is also no beep to notify that the call has ended. This is a bit annoying if you end the call with the handset in your pocket. There is nothing to let you know it has ended, apart from looking at the handset.
Does anyone know of a hack to shorten the length the button needs to be pressed to end a call.
Also is there any chance of voice tagging, like a normal phone. I have tried Voice commander, which I think is hit and miss.
Many Thanks
NickB23
Hi all,
Not sure why this happens but when I have my adapter (eBay link: http://tinyurl.com/l9maca) plugged into my car (phone<->mini-jack cable<->adapter<->car stereo) I either have voice dial launch automatically or the phone dialing the last number in call history. The voice dial isn't too bad since it launches and idles but the redial is really annoying. The headphones it came with did that too after a lot of wear and tear. Any know what causes it?? Is there a pin in the plug that I need to ground/disable? I would like to enjoy my music going without having to frantically grab my phone and hammer on the end call button while I'm driving.
Thanks.
holy crap i have the same problem with my phone, i dont have a car adapter but the headset thing is really annoying, i dont have the problem solved though....just figured i need to get a new pair of headphones which i havnt got around doing it
i have the same problem when i use headphones and i'am using them on my motocycle althought i lock the touchscreen, not even aplications like pocketshield didn't solve the problem. i hope that someone will come up with a solution that just disable the redial double tap function of the headset button or speed dial hold function. this functions also unlocks the touchscreen.
I just wanted to ask whether anyone else was having problems making calls. Sometimes when receiving or making calls I have the problem that the person on the other end is not able to hear me. I however can hear them perfectly and crystal clear. Is anyone else having this issue? The issue is usually resolved when I redial, but it's pretty annoying at times.
I'm on Vodafone UK.
The first call I made this happened to me, I think my head pressed against something to place the call on hold. The only indication you get that the call is held is a little pause icon in the task bar.
I've had this a number of times when the Hero has been connected to my Bluetooth car kit.
Even once its disconnected, I dial out and the caller hears me but I do not hear their ring tone or voice.
Turning Bluetooth off and then on again seems to cure it.
Random, does not happen all the time.
The Hero will also think its still connected to the car kit even after the car is turned off and I'm a long long way from it.
Same cure as above releases the 'connection'.
I've also noticed I get a pop up that says 'Bluetooth Headset Disconnected' when it was not or had not been connected for a long time.
Seems confused.
I use a BT handfree, but sometimes I may want to answer a call using the phone itself.
If I slide to answer, I don't expect the phone to transfer the call to my handfree. It has been working in this way for all the phones I used previously
However, N1 will still transfer the call to my handfree in this situation....Any solution? (other than pressing the bluetooth soft button on screen)
fatboyhk said:
I use a BT handfree, but sometimes I may want to answer a call using the phone itself.
If I slide to answer, I don't expect the phone to transfer the call to my handfree. It has been working in this way for all the phones I used previously
However, N1 will still transfer the call to my handfree in this situation....Any solution? (other than pressing the bluetooth soft button on screen)
Click to expand...
Click to collapse
That was what I was going to suggest. One additional button-press doesn't strike me as terribly burdensome.
Anyhow, the way it works makes sense to me. If I have a bluetooth headset stuck in my ear, chances are I'm going to want to use it for the call, even if I answered the call using the slide just because I picked up the phone to see who was calling and slid to answer while I had the phone in hand rather than using the button on the bluetooth device.
I Have been driven nuts by this for ages, to me the nexus one does it right.
My car handsfree answers after 4 rings, if I really didn't want to miss the call I'd press on the phone to answer, only then to panic when I couldn't hear them and then have to use speakerphone and turn off the radio manually and then have a really difficult conversation.
now, if the handsfree is connected it's always used.... I think there is a privacy function (that's what it's called on some other phones anyway) which will switch the call to the handset.
- Anthony
lol i don't know what you guys are smoking.... but it is up to personal preference i guess.
It would be better if we have an option for that so everyone will be happy
Hi guys,
I have been trying to find answers for this problem ever since i bought my Galaxy S2..but no luck so far.
The problem is trying to voice dial someone while the phone is paired with a bluetooth headset and on standby/screen locked mode. In other words i want to be able to voice dial someone when my galaxy is in the pocket instead of having to unlock the screen and go for voice dial and then say command which negates the whole point of having voice dial.
So far when i press the bluetooth's button, the phone goes - "what would you like to do" and then i try saying ''call (person)" but the phone seems to be doing nothing after that..but when the screen is unlocked and i do the same thing, it actually does dial(no point because if i am able to take the phone out and unlock it, i might as well dial it instead of voice). What really hits me is that the bluetooth actually does trigger the voice talk application and the phone requests me to say what i want to do but after that nothing happens.
Can you guys tell me whats going on? This problem is really making me hate this phone because the phone boasts so many ads about voice dialling but it cannot do a simple voice dial which is possible on ancient phones. Cheers
I've been playing with this for the past couple of days and here's what I've learned. It's complicated because there are multiple settings that effect each other. The phone has to be on to use Voice Talk. It can be locked, but has to be on and active. In other words, Voice Talk won't wake the phone up if it was shut off with the on/off button. Also, the app has to be in the foreground for it to listen. If you go to the home screen or launch another app its no longer active and listening.
Also, similar to the OP, my headset reacts strangely when I use its command button. When I push the button and say "phone command," it says "activating your phones inbuilt calling features," and then says "this feature is not supported on the connected phone." But, after that, Voice Talk is still listening but acts wonky. Instead, I set Voice Talk to Listen Over Bluetooth and I don't have to push anything - I just say Hi Galaxy. OP, I bet your headset's experiencing something similar. Try turning on Listen Over Bluetooth and Wake Up Command and then just say Hi Galaxy to start Voice Talk. I bet it works. Don't forget you can also set Motion to on and then just tap the phone twice (even if its locked) to activate Voice Talk. I'm guessing that uses less battery on both the phone and headset then leaving the Wake Up Command on.
Here's my take on each of the settings:
Listen Over Bluetooth
Has to be on for Voice Talk to work via a headset. If not, you can hear the prompts through the headset but Voice Talk is listening through the phone's built in mic.
Auto-Start Listening
I haven't figured this one out. Either off or on the phone seems to behave the same way. The best I can figure is that Voice Talk starts listening immediately the first time its opened instead of having to tap the button to make it start listening.
Wake Up Command
If Listen Over Bluetooth is active, the Wake Up Command has to be on for Voice Talk to hear Hi Galaxy.
Driving Mode
Is really mislabeled. All it does is announce new e-mail (but not read them) and read text messages.
So that's my take. I'd be interested in everyone else's experiences and if they've learned anything different or better.
BarryH_GEG said:
I've been playing with this for the past couple of days and here's what I've learned. It's complicated because there are multiple settings that effect each other. The phone has to be on to use Voice Talk. It can be locked, but has to be on and active. In other words, Voice Talk won't wake the phone up if it was shut off with the on/off button. Also, the app has to be in the foreground for it to listen. If you go to the home screen or launch another app its no longer active and listening.
Also, similar to the OP, my headset reacts strangely when I use its command button. When I push the button and say "phone command," it says "activating your phones inbuilt calling features," and then says "this feature is not supported on the connected phone." But, after that, Voice Talk is still listening but acts wonky. Instead, I set Voice Talk to Listen Over Bluetooth and I don't have to push anything - I just say Hi Galaxy. OP, I bet your headset's experiencing something similar. Try turning on Listen Over Bluetooth and Wake Up Command and then just say Hi Galaxy to start Voice Talk. I bet it works. Don't forget you can also set Motion to on and then just tap the phone twice (even if its locked) to activate Voice Talk. I'm guessing that uses less battery on both the phone and headset then leaving the Wake Up Command on.
Here's my take on each of the settings:
Listen Over Bluetooth
Has to be on for Voice Talk to work via a headset. If not, you can hear the prompts through the headset but Voice Talk is listening through the phone's built in mic.
Auto-Start Listening
I haven't figured this one out. Either off or on the phone seems to behave the same way. The best I can figure is that Voice Talk starts listening immediately the first time its opened instead of having to tap the button to make it start listening.
Wake Up Command
If Listen Over Bluetooth is active, the Wake Up Command has to be on for Voice Talk to hear Hi Galaxy.
Driving Mode
Is really mislabeled. All it does is announce new e-mail (but not read them) and read text messages.
So that's my take. I'd be interested in everyone else's experiences and if they've learned anything different or better.
Click to expand...
Click to collapse
Thanks for this detailed reply. I think at some point I have tried these settings but not sure if they were in the exact matching order. I will give it another go with everything set up to the way you have mentioned and see what I get. I am sure I am very close to actually getting it to work though..fingers crossed ..and yes if anyone else have different combinations of settings or ways they got it to actually work from a locked screen, please share it here. Thanks.
BarryH, I did try those exact settings like you had mentioned but still no luck. On triggering the voice talk with bluetooth headset's button, i can hear voice talk say "what would you like to do?" and does not respond to anything i say. (while screen is off).
I am thinking of installing Vlingo and trying to get that to work this way? Not sure if it would make a difference though.
vijith555 said:
BarryH, I did try those exact settings like you had mentioned but still no luck. On triggering the voice talk with bluetooth headset's button, i can hear voice talk say "what would you like to do?" and does not respond to anything i say. (while screen is off).
I am thinking of installing Vlingo and trying to get that to work this way? Not sure if it would make a difference though.
Click to expand...
Click to collapse
If you do what I suggested you don't have to push the command button. The phone will be listening for the "hi galaxy" command all the time.
Sent from my GT-I9100 using XDA Premium App
I noticed the same thing, when paired with my car, the phone does not respond to pressing the button on my parrot if the phone is locked
I disabled the factory lockscreen and now use widget locker instead, problem has gone away
connectsys said:
I noticed the same thing, when paired with my car, the phone does not respond to pressing the button on my parrot if the phone is locked
I disabled the factory lockscreen and now use widget locker instead, problem has gone away
Click to expand...
Click to collapse
I was thinking of trying this next as I have run out of options..so you say it worked? Then I will get widget locker and see how I go. So let me get this straight - i get widget locker and use the lock screen that comes with that or using widget locker i disable the stock lock? Or I should disable the stock lock from settings and then use widget locker? Cheers
yea disable stock lock in settings and then use widget locker only for lockscreen
connectsys said:
yea disable stock lock in settings and then use widget locker only for lockscreen
Click to expand...
Click to collapse
Tried this last night and unfortunately its still doing the same thing. On holding the bluetooth headset's button while the phone's screen is off I can hear the phone go "what would you like to do" and right after this i say commands like "call (someone)" but nothing happens. When the phone's screen is on, it actually works when i do the same thing which just surprises me to as why. Also when the screen is off and voice talk not on the front screen the wake up command doesnt work. So again a person has to leave his screen on (without letting the phone go to standby) and leave the voice talk app running for voice dial to work.
And to make things worse the double tapping with motion turned on settings doesnt bring up voice talk when the screen is off..again putting me in the same situation. The only way voice talk work on this phone is when the screen is on so far which isnt really practical in situations you would want to use voice commands..i hope samsung or google brings a better solution to this issue because this phone's got so much boasting about being able to voice command but isnt able to perform what an iphone or old nokia do
If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!
k1sr said:
If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!
Click to expand...
Click to collapse
I cant agree more about it being counter-intuitive..and yes its not nice the voice prompts coming through the phone but i remember once somehow the voice prompts did come through the bluetooth headset i dont know how. Like you said something is not letting it operate properly, like blocking it. I havent used this Tasker but have used task manager like apps in the past. So you believe you could try to figure out a fix for this..i appreciate your efforts because I am just lost at the moment. Let me know how you go mate. And I will let you know if I get around this issue too. Thanks mate
k1sr said:
If you've got Tasker, you might be able to set something up... I noticed the same problem last night, and yeah, it's totally counter-intuitive...
I'll let y'all know how I go...
BTW - also noticed that while it may listen through my car bluetooth, it certainly doesn't play through it, and it's next to impossible to hear the mousey voice in a moving vehicle muffled in the depths of my pocket anyway...
Stupid half-baked software!
Click to expand...
Click to collapse
Ok i found a way to get this voice dialling to work when the screen is off but not using a bluetooth headset, instead the wired headset for the time being.
So I can trigger voice dial when the phone is in the pocket and voice prompt comes to the headset, i say command and it works . I dont mind it working for the wired headset as that is good enough for the time being while driving. If you need to know how i got this done just give me a buzz. There are two pieces of software that I got to set this up. Cheers.
I just deleted built in vlingo crap and took generic Google voice dialer apk from my nexus s. Plus side you don't have to be connected to net to dial contacts and I can hear reply in headset as well.
Sent from my GT-I9100