Here is a little background on my problem.
I just recently bought a new Nexus 4 (my first android phone). The other day I was on walking on the road listening to some music on my wired earphones. I received a call which I answered by pressing the button on the Mic of the headset. After 3 seconds the call got disconnected and I heard a Google now beep. What had happened was, when I picked up the call, the phone unlocked itself which is normal. But the proximity sensor is disabled when you are connected to a headset (wired or wireless doesn't matter) as a result of which my phone registers random inputs in my pocket (which disconnected the call and opened google now). Is there a way to enable the proximity sensor when connected to a headset?
I cannot believe Google ****ed up this basic thing. I see Samsung phones doing it properly with their ROM.
@moderators This is my first post on XDA so I am really sorry if this post is too long or in the wrong section.
Related
I upgraded from the O2 XDA mini to the Orange M3100 and use the same Sony headset and can't get the voice tags to repeat in the headset after they have been recognised. It worked fine with the O2 phone, you pressed the headset power switch briefly, said the name and the phone played the match back to the headset. This new phone simply shows the name on the screen and repeats through the phone speaker. Tried to pair it again but still the same, anyone had this and found a fix?
As an update I was using the voice dial function the other day sat in the car and could hear the recorded name in the headset but it's reall quiet. The previous HTC phone was a lot louder so is there anyway to increase the volume of the spoken voice tag in the headset, I have the headset volume up full but still it's too low to hear properly.
I've seen some other posts on getting stereo headsets working with this Orange device. Can anyone help me find a way of getting the phone to increase the volume of the repeated voice tag in my bluetooth headset please?
Well there are only 263 posts re. Bluetooth and headset problems in this thread
http://forum.xda-developers.com/showthread.php?t=285419
If you can't find any answers there, there are about another 10 threads about headset and bluetooth problems, about 15 threads on Voice Command problems and you combine the two and you have a nightmare
... almost makes you want to use a wired headset and hand dial.
Trust me, I thought this would be easy.........
The previous HTC device I had (Wizard with O2) worked fine, press headset button, speak, phone confirms back and then dials. This one has such a low volume that you can't hear what it says. I read through a load of the posts but they all seem to be trying to solve problems I don't have, for me the headset and phone works, the TomTom GPS v6 also works, the TCP video software is almost there and all of this without having to hack any programes.
I tried it again today and before when I thought it was very quiet it was in fact the speaker on the phone I was hearing on the seat next to me, the headset does not reply the voice tag.
Surely others must be using BT headsets with this phone and use the voice dial tags when driving etc?
Roy_S said:
Trust me, I thought this would be easy.........
The previous HTC device I had (Wizard with O2) worked fine, press headset button, speak, phone confirms back and then dials. This one has such a low volume that you can't hear what it says. I read through a load of the posts but they all seem to be trying to solve problems I don't have, for me the headset and phone works, the TomTom GPS v6 also works, the TCP video software is almost there and all of this without having to hack any programes.
I tried it again today and before when I thought it was very quiet it was in fact the speaker on the phone I was hearing on the seat next to me, the headset does not reply the voice tag.
Surely others must be using BT headsets with this phone and use the voice dial tags when driving etc?
Click to expand...
Click to collapse
I don't have these issues so don't know the exact thread but I have read that many ppl are having the same problems as you. I think they have solved all but incomming notifications - so go looking and you should find.
Ok, I've this issue since the day I upgraded from v1.6 to 2.1 and until there isn't any fix available. The topic exists in Official SE Forum and there isn't any useful info provided by them.
In hope to get help from XDA members, here is the issue:
Does anyone notice that when you are using bluetooth headset, the proximity sensor doesn't work? Is it a bug in Android v2.1 or am I missing something? I'm using MW-600 with X10i Android 2.1 if that matters. (The same phone and bluetooth worked fine with Android v1.6)
I'm interested into it too but it seems that there is no way to fix it! :-/
The proximity sensor works when the phone is connected to MW-600, but it will not work when dialing or receiving a call because the audio is directed to the bluetooth device and you dont use the phone's earpiece to hear the audio.
sharathx10 said:
The proximity sensor works when the phone is connected to MW-600, but it will not work when dialing or receiving a call because the audio is directed to the bluetooth device and you dont use the phone's earpiece to hear the audio.
Click to expand...
Click to collapse
Agreed, but when you are using bluetooth, I hope you don't expect me to carry to phone in my hand. I usually leave it in my pocket and this causes unnecessary touches and often ends in either disconnect bluetooth or call ended.
Sometimes I notice it causes to open the contacts and dial someone's number
Please also mind that all these problems aren't found when you use the same bluetooth the same way with Android 1.6 !!! Now how to justify that?!?
So something new I noticed yesterday. I seemed to have misplaced my blueant q bluetooth so while I search for it I decided to use my car's radio Bluetooth interface. I paired it with my car's radio and made and answered a few calls. I made a few stops and when I started my car back up my note connected to the bluetooth fine and immediately started to redial. I thought it was just a fluke the first time it happened but then I noticed it happening on five other stops. I ended up turning off the bluetooth on the note to keep me from hanging up on my friends.
Anyone else experience this? I've searched for a fix but I haven't seen any just others (mostly with plantronics headsets) have the same issue.
Weird
Normally, if you double tap BT headset button, all phones will start redial last number. Sounds like your car radio may have sent out double tap command by error. Does it happen with your Bluant headset? If not, you have your car's radio to blame, not Note.
I'm still looking for my blueant... I think it was moved "somewhere safe" during a recent spring cleaning and now I forgot where that safe spot was. Yeah I don't think it's the note that has a problem but it is weird that not of my other phones redial when they connect only seems to be with the note.
I'm going to try some more diag testing tomorrow.
Hi there - long time lurker, first time poster!
Now, I'm not sure if this is a phone setting issue, an Android issue or my satnav/hands free issue - and sorry if this is a common problem, I did a search on the forums and haven't managed to find anything yet, probably using the wrong key words
So then, I've paired the S3 with my Navigon 70/71 (rebranded as maps & more by Volkswagen) and it works beautifully for streaming music. It connects as soon as I enter the car and holds the signal well!
...however, when I go to make a call from the satnav - it dials the number fine, but plays the audio through the phone earpiece and not the satnav speakers.
Of course, to remedy this I can manually click the headset icon on the phones call screen - but this is far from ideal as it means every time I nip in the car I have to get the phone out, set it to send audio through the bluetooth device and then start my journey. The moment you forget renders the hands free useless and you click answer or dial on the satnav and it plays the audio through the phones earpiece
My old phone used to just allow me to get in the car without a thought, get a surprise phone call, click answer on the satnav and all the conversation would play out through the car speakers without a second thought... can I do this on ICS and the S3? Basically getting it to auto route audio through to the car stereo when connected?
Thanks for your help and sorry if this is the wrong section/covered a million times before..
Hello,
I'm new to this site so apologies if I'm in the wrong place or this has been raised before but I've googled with no joy..
I have a Samsung Galaxy S3 i9300 uk unlocked.
For the last month or so m having problems with Bluetooth devices and loudspeaker (seems to be connected)
I can connect to bluetooth devices fine, beats wireless and vw car bluetooth.
It connects automatically and I can talk and hear fine, after a while the sounds drops and it goes echo like, I can't hear the other person at all but on the phone the green button Nader headset is still lit up and the connection is still made. I have to press the headset button to in light it/disconnect it and then re press to connect / light the button back up. I then can hear the person again but it does this continuously throughout the call. Listening to music via Bluetooth is fine and this problem doesnt arise.
When using loudspeaker it's the same, will go to phone (button lit) and I have to press it again twice to disconnect and reconnect.
Can't find out why this happens. I've done a factory reset and it allowed me a few days of it working fine but then goes back to normal.
Anyone else having this problem? I've read a lot about it disconnecting and having to repair but mine seems to stay connected but just drop the sound?
Cheers
Syak2008
same issues
I am having the same issues... did you find the solution?
Same issues too.. i thought it was my ford bluetooth (POS!)