Since the jelly bean update, everytime I use a headset and press the play/pause/answer call button, it removes silent/vibration and the notification sound comes out of the phone speakers instead of headset. It's really annoying and it makes it hard listening to music at work.
I have this issue on official and AKOP roms. Anyone has this issue and knows how to fix it?
Hi Guys
I have just purchased a Motorcycle Sena SMH10 with boom mic and whilst i've got it working fine as an MP3 player, it doesn't seem to recognise any voice requests. If I press the little phone button, the screen on my S3 switches over to google voice but doesn't register any commands. When the phone is asleep (and pin locked), I also get the same. I press the button and after a short while I'll hear a beep and the phone will tell me something like it didn't recognise/hear anything.
The phone is running 4.2.1 and the SMH was upgraded to the latest firmware.
Also, in the phones bluetooth settings I can only see two entries for the Sena, "Phone Audio" and "Media Audio", should I be seeing "Microphone input" or something like that?
Thanks guys!!!
I'm new to rooting and I rooted my Samsung Galaxy S2 T989 to Android version 4.1.2 jelly bean.
What I just recently found out is that the function of the headphone mic doesn't seem to work like it did when the phone wasn't rooted.
When I press on my mic's button during a call, it doesn't end the call like it did before the phone was rooted.
When i'm NOT in a call and I press the mic's button, it doesn't play music.
When I try using my headphone's mic while on the phone with someone, the person can't hear me. I know the headphone mic works because I tried it with a non-rooted phone.
Anybody have a solution to this issue?
Or has anybody else using this version of android run into the same issue?
Hey all,
So Im running Dirty unicorn 4.4.2 and I got a Bluetooth headset for my motorcycle helmet. Initially when I pressed the voice call button on the BT voice dialer popped up. I wanted Google now insead so I disabled the voice dialer and than it allowed me to select google now. Well here is the issue, I can say "Ok google" and it hears it and begins listening but after that it does not hear anything I say. I have selected to use Bluetooth in G Now settings and have even tried to enable the screen tap sound checkmark (which I head had issues being off) with no luck.
Does anyone have any idea what is causing this? One weird note is while G Now is listening the volume indicator does some weird jumps but it does it when I am not saying anything.
Thanks in advance.
Anyone have any idea? I have a local build of Dirty Unicorns up and running on my computer so I can modify source and kernel but have not found anything that would relate to this problem.
We finally have our watches updated with the long waited 1.4 internal speaker enable firmware.
I was so excited to side-load the update to my watch and seeing the new features activated, but with more usage to the watch/phone (note5) I started getting frustrated.
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
2nd flaw is the strange behaviour using Facebook messenger calling when audio is diverted to watch, but this time the calls fail.
I thought i would see if its only me facing this, is it the combination of my phone/ watch misfit? or its the update?
I have already factory reset my watch, to no avail.
Please share your experiences guys.
For me this works super cool, no problem. Speaker is very loud and clear. I use it 50% volume at home, whitch is enough.
taiseer999 said:
Phone calls cannot be received (heard or voice out) from phone if bluetooth (Play phone audio on watch) is selected. (unlike my previous iWatch)
Click to expand...
Click to collapse
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
C3C076 said:
When you accept phone call on a phone voice is automatically directed through phone's earpiece. When you accept it on the watch, voice goes through the watch.
You can also switch voice direction during call using button having BT icon within in-call screen. This is how it works for me on Nexus 5x and I find it quite consistent.
Click to expand...
Click to collapse
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
taiseer999 said:
Unfortunately answering the call from the screen doesn't activate the ear speaker in my case, but I can activate the loud speaker!
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Answering the call from the watch screen will answer on the watch. To me that is as expected. If you want to answer it on the phone use the phone to answer instead of watch.
Sent from my Nexus 6 using Tapatalk
I guess it's dependent on a device type, Android version it is running and most importantly a dialer app that it is running.
I can imagine devices having custom dialer supplied by a vendor that significantly differs from the standard Android one could yield different results.
Anybody else encountered FB messenger crash?
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Edit: Point 3 somehow fixed (or demonstrates randomly). But still: no audio stream between phone and watch.
nalott said:
I'm facing very serious problems while trying to use HWatch to make/answer calls.
1. Without activating "Play phone audio on watch" everything works as before (no way to answer the call without pulling the phone). Somehow expected behaviour.
2. When I activate "Play phone audio on watch", I can answer the call on watch and apparently it thinks the call is going normally. Byt nothing can be heard on either side of the call. On phone the in-call UI is also displayed and no sounds played or recorded.
3. What's even worse, when I conventionally answer the call on my phone, it's somehow answered also on watch, with result being similar to 2 - no voice whatsover on either device - for about 10 seconds. After that the call is hung up on watch and starts to be hearable on phone. This is very annoying.
I admit, I have an old Samsung Galaxy SII running SlimKat 4.4.4 (which should include standard AOSP dialer). Maybe it has an old version of Blutooth or something screwed elsewhere. But for me the new 1.4 functions are now plain unusable.
Click to expand...
Click to collapse
Well I am somehow facing same issues with my GN 5 with the latest MM, in addition to crashing of FB messenger... Line and other voice calling apps are running fine.