(It's been mentioned already by several people here but is burried in the 1.4 update discussions. I feel the need to pull this serious problem to the daylight.)
It behaves as follows:
With the Bluetooth "Play phone audio on watch" option OFF everything works fine but like before 1.4 update (no phone call possible from/to the watch).
When I enable "Play phone audio on watch", strange things begin to hapen when I try to use the newly enabled phone call capability.
Call initiated from the watch or answered on the watch results in mute call. Other than that the GUI of the phone and the watch behaves like the phone call is connected and running. The problem of not working proximity sensor (http://forum.xda-developers.com/showthread.php?t=3330372) also applies here.
Call answered conventionally on the phone results in several seconds mute call (very annoying, making all the "Play phone audio on watch" unusable in practice), after that everything is ok (like in the scenario 1 - "Play phone audio on watch" OFF).
So, it seems I have a problem with sound streaming between my phone and watch. The problem of Shazam not working (http://forum.xda-developers.com/showthread.php?t=3258367) applies fully (don't know if relevant here). I didn't find any other way to test it. I'm on Slimkat 4.4.4, Samsung Galaxy SII. Fresh factory reset after 1.4 sideloaded update.
Microphone is working (Google voice search tested).
Speaker is working (Ringtones are playing)
Please help with further troubleshooting.
This update, to say the least, is very buggy. I have the same issue you do with calls making the phone capabilities nearly useless.
I have factory reset a few times. I think the OS is the culprit. Its putting the watch too far to sleep (if such a thing is possible).
I have hesitation on my watch faces (some more than others) and my bluetooth will randomly drop then reconnect.
nalott said:
Call initiated from the watch or answered on the watch results in mute call.
Click to expand...
Click to collapse
I haven't had this problem so far. Maybe it's related to the Android version running on the phone. I'm using Android 6.0 (HTC One M8 / Google Play Edition).
In case more users confirm this issue, I think it's a good idea to make a report in the AOSP issue tracker:
https://code.google.com/p/android/issues/list
I've done that for the proximity sensor issue.
I can confirm Shazam not working for me with MEC23L.
Related
Has anyone else experienced the flowing BT issues with jelly bean?
1. Can't make any 3rd party dialer apps the default without completely disabling google search
2. Built in voice dialer so bad its unusable when used with bluetooth
3. Cant use the center button to activate any voice functions except built in voice dialer. No google search.
4. If you answer a call while listening to media then after hangup media resumes again at zero volume?
5. If you are a heavy BT user like myself are you happy with JB?
None of the above were issues with my sony mw600 on ICS.
I haven't tried the others, but I do have issues 2 and 3. They have been reported on here multiple times, but no solution yet.
JimSmith94 said:
I haven't tried the others, but I do have issues 2 and 3. They have been reported on here multiple times, but no solution yet.
Click to expand...
Click to collapse
If its convenient could you try #4. I'd like some confirmation that I'm not alone.
I can't even get jb to see my hands free
Same problem.
It looks like Google messed up the Bluetooth functionality.
Voice Search is useless.
I purchased voice speed dial and now it can't be activated using the BT button or the center button.
What's interesting is that "Voice Search" that came preinstalled does work with the BT button unless I disable it.
yaronkle said:
I purchased voice speed dial and now it can't be activated using the BT button or the center button.
Click to expand...
Click to collapse
Actually I did get mine to work. You have to first disable google search which basically nullifies all of the new JB features on the phone.
There are only 2 or 3 devices that officially have jelly bean at this point. As more devices come over the complaining will certainly rise. Wait and see. I think this is a pretty big deal.
NCguy said:
Has anyone else experienced the flowing BT issues with jelly bean?
1. Can't make any 3rd party dialer apps the default without completely disabling google search
2. Built in voice dialer so bad its unusable when used with bluetooth
3. Cant use the center button to activate any voice functions except built in voice dialer. No google search.
4. If you answer a call while listening to media then after hangup media resumes again at zero volume?
5. If you are a heavy BT user like myself are you happy with JB?
None of the above were issues with my sony mw600 on ICS.
Click to expand...
Click to collapse
re: #4 - I don't have a problem resuming media playback after a phonecall over bluetooth. I do however get a 5 or so second lagwhen connected to my car's audio system... Maybe that's what's causing it? Have you tried waiting a few seconds to see if it plays?
I have an issue since 4.0.4 where my MW600 is lagging, audio from games and notifications is lagging 1-2 seconds... In calls and videos played with the built in video player, audio plays just fine, no lag... In my iPad 2, Nokia E51, Motorola Milestone, the same headset also works just fine, no lag perceived in any scenario....
krausy87 said:
re: #4 - I don't have a problem resuming media playback after a phonecall over bluetooth. I do however get a 5 or so second lagwhen connected to my car's audio system... Maybe that's what's causing it? Have you tried waiting a few seconds to see if it plays?
Click to expand...
Click to collapse
No, I don't think it lags although its possible because volume level goes to zero and I can't hear a thing until I raise it again. It seems like the media starts again upon phone hang up, you just can't hear it a zero volume. I am using an mw600 bluetooth headset.
please report problem here
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=35199
The more posts the quicker it might get fixed. Hopefully
scarecrow2012 said:
please report problem here
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=35199
The more posts the quicker it might get fixed. Hopefully
Click to expand...
Click to collapse
Agreed. Priority is only medium at this point. Need a lot more posts.
I'm having issues with the playback on my N5X when using headphones w/ remote. Bluetooth seems to work without issue.
The problem is, randomly, and usually within a minute of starting audio and putting the screen to sleep, audio playback will stop. Once I unlock the phone, it looks as if the OS still thinks audio is playing. If I toggle the play/pause button, I can get it to restart audio, but it does not pick up at the point where I heard the audio stop -- as if it continued playing while "muted". This occurs in at least 2 separate apps, which is why i'm thinking it's either an Android bug or possible a HW issue.
Anyone seen this?
Well I guess that answers my question...
tjkrz said:
Well I guess that answers my question...
Click to expand...
Click to collapse
I've had a problem playing audio using Podcast Addict over bluetooth, but it's not similar to what you're describing. In my case, playback just pauses randomly for a second or two, then continues. This can happen after 1 minute of playback, or 20 minutes. I'm assuming at this point that my problem is with the app, android 6.0 is still very new and some apps may have problems (like camera apps flipping everything upside-down).
Exactly the same issues with my Nexus 5X... Deezer and Podcast Addict. Music starts but as soon as the display is turned off, approx. one minute later the sound stopps but when I turn the phone on again the player looks like still playing... Very annoying... Have you changed someting like the "lock when power button is pushed" option ore anything which is connected to the display?
Same here with Spotify... I find that I have to unplug and replug the headphones, hit pause, then play again. :/ Have you tried disabling Doze for your music player? It may have something to do with that, but I haven't experimented with it yet.
tjkrz said:
I'm having issues with the playback on my N5X when using headphones w/ remote. Bluetooth seems to work without issue.
The problem is, randomly, and usually within a minute of starting audio and putting the screen to sleep, audio playback will stop. Once I unlock the phone, it looks as if the OS still thinks audio is playing. If I toggle the play/pause button, I can get it to restart audio, but it does not pick up at the point where I heard the audio stop -- as if it continued playing while "muted". This occurs in at least 2 separate apps, which is why i'm thinking it's either an Android bug or possible a HW issue.
Anyone seen this?
Click to expand...
Click to collapse
Yes I Had this problem. Mine did the exact same thing as yours. I rebooted the phone and it seemed to fix the problem. I can't tell if I would have had the problem again because I sent my phone back the next day for a replacement. My WiFi was terribly slow so they are sending me a new 5X.
I'm having the same problem when I use Google Music. I don't even have to turn the screen off. Did you have any luck figuring the problem out?
jurey said:
Exactly the same issues with my Nexus 5X... Deezer and Podcast Addict. Music starts but as soon as the display is turned off, approx. one minute later the sound stopps but when I turn the phone on again the player looks like still playing... Very annoying... Have you changed someting like the "lock when power button is pushed" option ore anything which is connected to the display?
Click to expand...
Click to collapse
Yes, I did deselect "Power button instantly locks". I'll try putting it back to the default to see what happens. I know this has nothing to do with the "Smart Lock" state, because it happens even when I'm away from home.
Otherwise, I've found nothing that solves the issue. It's very annoying. The good thing is it probably only happens 10% of the time when I turn off the display with audio playing.
Yeah it's happening every single time I play music. Driving me crazy
Having the same problem. Seems to only happen when I'm doing something that would trigger the motion sensors. So when walking, all audio gets muted within a few seconds of me starting to walk, then stays muted. However, if I pause the audio, after 10 seconds I hear a pop (like the sound of a speaker turning off or something similar) and audio is available again. Exact same thing happens when I'm biking. If I'm stopped, music will continue until I start biking again, pause music, ten seconds later pop, resume. Everything is fine until I stop again, then repeat.
This isn't a problem when I take the subway, or a bus.
It's not just music that's muted though, all notification noises and alarms are also muted. The phone thinks the volumes are all where they're set, but won't play anything either over headphones, bluetooth or the speaker.
A reboot has not fixed my issue. System logs haven't revealed anything. Since this doesn't seem to be a super widespread problem, I'll be RMA'ing this one and hoping it doesn't happen on my next.
I'm not the only one
I have similar issues with mine, using podcast addict and YouTube with either wired headphones or wired aux jack.
What I find weird is that I am able to continue watching the video but without sound. I am unable to reliably replicate the problem but it always happens very quickly in the car using the wird aux input.
Sometimes the headphones will be fine for a long time while I'm sitting still and other times it will seem to stop even if I have no motion happening or have not touch the headphones.
Would be interested in trouble shooting this please advise.
Putting my phone away without turning off the screen seems to make this happen less. However, since this doesn't seem to be a super widespread problem, I've RMA'd my device. Not interested in starting out with a broken handset.
Been happening to me too - think since the MDB08L update. I just turned off Google Now 'Always On' and my podcast is playing fine (so far, lol). Not ideal because I do use OK Google, but continuous audio playback is way more important to me. Hopefully it'll be fixed soon. How can we report issues like this to Google?
Interesting. I use Nova Launcher and switched off Google Now 'Always On' in the phone settings, but left it enabled in Nova Settings 'Gestures and Inputs'. I can still say 'OK Google' on any screen and so far the audio is playing without stopping every minute or so.
Getting this too. Was out running earlier with headphones in, stopped playing randomly five or six times but found skipping track made it work again. At home, had it on loud speaker, got 5 seconds in but it froze, skipped track and got 3 seconds, skipped again and just got 1 second. Gave up after that..
But it works fine when connected to a bluetooth speaker or my car!
scgf said:
Interesting. I use Nova Launcher and switched off Google Now 'Always On' in the phone settings, but left it enabled in Nova Settings 'Gestures and Inputs'. I can still say 'OK Google' on any screen and so far the audio is playing without stopping every minute or so.
Click to expand...
Click to collapse
I tried this - switched off the "Always On" option. Went for a 40 min run tonight with music on through headphones and it didn't stop playing once.
Even now, got the phone playing through loudspeaker and it's having no problems!
Exact same issue here .
Audio playback stops but device still thinks its playing ie speaker icon on top bar. Sometimes stopping app and restarting helps other times no joy. I have also heard the short pop sound when it stops.
So far has happened in Youtube, google music and in some games. Also intermittent loss of text alert tones too.
Only sure fire way to reset is to restart phone.
I shall give the switching google now always on off trick see if this helps and report back (never use it anyway but still it shouldn't prevent audio)
Try a reboot
droidXish said:
I have similar issues with mine, using podcast addict and YouTube with either wired headphones or wired aux jack.
What I find weird is that I am able to continue watching the video but without sound. I am unable to reliably replicate the problem but it always happens very quickly in the car using the wird aux input.
Sometimes the headphones will be fine for a long time while I'm sitting still and other times it will seem to stop even if I have no motion happening or have not touch the headphones.
Would be interested in trouble shooting this please advise.
Click to expand...
Click to collapse
I did more searching online and found enough other people are having a similar to think that there's something going on with the software. One post on a nexus 5 X subreddit had talked to Google support and went through a process of a safe mode boot as well as a reboot. I have not tried a safe mode boot but a reboot has resulted in the best playback experience I have had since owning this phone. No interruptions in audio for the last several hours . I'm on Verizon and have not received any updates as far as I'm aware. I am hoping that this will last.
My phone updated yesterday... I'm not sure but I haven't run into this problem yet with the new update. It has only happen 3-4 times before the update but we'll see
Tank87 said:
My phone updated yesterday... I'm not sure but I haven't run into this problem yet with the new update. It has only happen 3-4 times before the update but we'll see
Click to expand...
Click to collapse
After updating yesterday, I had it occur again this morning with video playback and the audio muting. So wouldn't be too hopeful, sadly...
Today I downloaded a dB meter app from Play Store, and I wondered why it didn't work, then I found out that it wasn't the app's problem but the phone's.
I tried other apps from Play Store that use the mics including Recforge, Sound Recorder, etc but still no sound signal coming from the mics, and yes, calling doesn't work. (Using headphone/earphone with plug-in jack works.)
An interesting finding is that when I tested with Shazam, after I pressed the turning Shazam logo, it almost immediately told me that no song was found, it was like whenever the app detects dead silence in the first 1 sec, it just gave up listening any longer.
I was using BlissPop so I switched back to stock-based SuperZen, suspecting it is ROM related problem but still no luck, still dead silence
Then I even switched to Latest WW Official Stock, but when I get into the test menu via the calculator app and performed the two mic tests, both of them failed. (I'm sure that it is not the speaker's problem)
So, I wonder if I can safely say that the phone's microphones are hardware dead now, if it is true maybe I will be sending the phone to repairment later next week. Or is it possible that it is some deep level software problem that I'm not aware of?
I have doubt because all other components are working except the two mics, and I think it is pretty abnormal for two components at two different side(top and bottom) of the phone to hardware malfunction at the same time. (Also because of the Shazam app's behaviour)
Thank you.
(English is not my first language so please forgive me if I sound rude or awkward )
Hi, have you resolved the issue?
Hi comcraizer,
did you find a solution to this?
Thanks.
comcraizer said:
Today I downloaded a dB meter app from Play Store, and I wondered why it didn't work, then I found out that it wasn't the app's problem but the phone's.
I tried other apps from Play Store that use the mics including Recforge, Sound Recorder, etc but still no sound signal coming from the mics, and yes, calling doesn't work. (Using headphone/earphone with plug-in jack works.)
An interesting finding is that when I tested with Shazam, after I pressed the turning Shazam logo, it almost immediately told me that no song was found, it was like whenever the app detects dead silence in the first 1 sec, it just gave up listening any longer.
I was using BlissPop so I switched back to stock-based SuperZen, suspecting it is ROM related problem but still no luck, still dead silence
Then I even switched to Latest WW Official Stock, but when I get into the test menu via the calculator app and performed the two mic tests, both of them failed. (I'm sure that it is not the speaker's problem)
So, I wonder if I can safely say that the phone's microphones are hardware dead now, if it is true maybe I will be sending the phone to repairment later next week. Or is it possible that it is some deep level software problem that I'm not aware of?
I have doubt because all other components are working except the two mics, and I think it is pretty abnormal for two components at two different side(top and bottom) of the phone to hardware malfunction at the same time. (Also because of the Shazam app's behaviour)
Thank you.
(English is not my first language so please forgive me if I sound rude or awkward )
Click to expand...
Click to collapse
I also have a problem with mic in Skype only when using speaker phone, regular phone works fine with speaker phone. This happens only with the mm bootloader on every ROM, worked fine on lp bootloader with any ROM. Anybody else have this issue?
Hey Guys,
everytime i connect my fire phone (slim kat) to a bluetooth speaker, i dont get any sound out of it.
What i tried so far:
-used multiple bluetooth devices (car; mobile speaker; tv sound bar) with no success. Everyone showed the same problem.
- removed all devices from the pairing list
- visible to all devices
- wiped cache
- tried spotify and poweramp
-moved from cm11 to slim kat: the problem was solved for like 15 min. The sound then suddenly stopped without me touching the display (no sound then, but the music player continued to play)
Any ideas? I uploaded a video showing the problem. all i get from the speaker is a silent buzz, which i tried to capture in the video at 01:20.
Also notice the weird volume button at 00:57...it switches from the normal audio speaker to the bluethooth speaker every time i change the volume.
https://youtu.be/sxMLdcQzb8E
I hope someone can help me.
I had a similar problem on stock, turned out to be my wearables apps. Microsoft Health and Pebble time, kept disconnecting me from everything else. May be completely unrelated, but worth a try. I uninstalled those apps and it started working fine.
Thanks for reply, but i dont have any wearable apps installed on the phone
Cmon guys, please help me. I know a lot of you guys are really into this topic...
Well so I have the issue where microphone would not work sometimes, yeah I know Pixels have the hardware microphone issues but I am not sure! For me suddenly the mic would stop working! No sound in videos, no sound picked up from audio recording apps, no google assistant response etc., but the good thing is phone call audio always works! So I let a sound decibel metre app run for half an hour to see whether the audio is breaking in middle, and no, there is no breakage in middle, so when it works it works, it doesn't stop in middle, but when I wake the phone up after say a one hour standby then it stops responding. Sometimes a reboot fixes it, sometimes it simply starts working after a while!
I am on stock ROM, rooted with SuperSU and using suhide etc., could this be a software issue?
My mic stopped working in Sept or Oct. Also connect a headset and audio still plays from the speaker. But phone somewhat knows a headset was connected, the music will stop playing from the speaker when I unplug the headset. After Oct update I a reset, issue persist.
Oh, and I can't use the phone as a phone. If I answer or call, the phone hangs and reboots.
No issues here, since it works sometimes, means that no hardware issue, try a factory reset.
ControlNode said:
My mic stopped working in Sept or Oct. Also connect a headset and audio still plays from the speaker. But phone somewhat knows a headset was connected, the music will stop playing from the speaker when I unplug the headset. After Oct update I a reset, issue persist.
Oh, and I can't use the phone as a phone. If I answer or call, the phone hangs and reboots.
Click to expand...
Click to collapse
I'm having the same problem with mine. I have to reboot and let it settle for a few min after then it seems to work fine for a while until it happens again.
Sent from my Pixel XL using Tapatalk
Are you using the call recorder app ? I find that to be the culprit.
Next time, it stops working, just ls -l /dev/snd, and see whether one file is with permission 600. ( I could not recall the detailed filename now ).
After changing the permission to 660 of that file, everything will work once again.
ithehappy said:
Well so I have the issue where microphone would not work sometimes, yeah I know Pixels have the hardware microphone issues but I am not sure! For me suddenly the mic would stop working! No sound in videos, no sound picked up from audio recording apps, no google assistant response etc., but the good thing is phone call audio always works! So I let a sound decibel metre app run for half an hour to see whether the audio is breaking in middle, and no, there is no breakage in middle, so when it works it works, it doesn't stop in middle, but when I wake the phone up after say a one hour standby then it stops responding. Sometimes a reboot fixes it, sometimes it simply starts working after a while!
I am on stock ROM, rooted with SuperSU and using suhide etc., could this be a software issue?
Click to expand...
Click to collapse
Problem persisted factory reset and updated factory image install. Warranty replacement and replacement is working fine.