Anyone else get this issue?
Is this a known issue?
Is there a fix?
Gets annoying, as I use my phone as my radio source and plug it into my stereo via headphone jack. Two out of three times it will not pipe the headphone audio out, but will when I reboot it (a 4-5 minute process as you can imagine).
For clarity, the following takes place:
4+ hours elapse since last phone reboot..
I start Pandora or similar audio program,
Music, talk, etc begins playing out speakerphone,
I turn on stereo and plug phone into stereo,
Audio stops.
I unplug headphone jack,
Audio resumes playing out speakerphone.
I reboot phone,
I start Pandora or similar audio app,
Audio plays out speakerphone,
I plug in headphone jack,
Audio plays through stereo as it should.
Rinse and repeat every 4+ hours.
Bump.
Does nobody else have this issue?
Sent from my SCH-I500
I did, it was getting shut down by my text to speech services. Instead of rebooting, I can go to the settings, text to speech, and play the sample, it will kick the headset connection back on.
Buji said:
I did, it was getting shut down by my text to speech services. Instead of rebooting, I can go to the settings, text to speech, and play the sample, it will kick the headset connection back on.
Click to expand...
Click to collapse
Sure enough, that worked perfected to get the sound routing correctly again without a reboot. The new question is.. how can we prevent this requirement? Obviously this isn't normal behavior. What causes the headphone routing to choke in the first place?
Heeeeeellifiknow. I don't even know what made me think to check the tts output of all things. I do have a call announcer (not using the stock tts call announcer). I was mostly just resigned to see if the problem stayed after the delayed froyo update, or if we end up getting a gingerbread rom.
I, too, use a 3rd party announcer (Call Announcer). I'm betting the option for call announcer to use its own TTS settings is what screws it up. I'll let you know once I test the theory (after I get a call).
Sent from my SCH-I500
The issue is definitely caused by Call Announcer, not the fascinate software. I had headphone working, then had someone call me, and the headphone stopped working. No options in Call announcer changed the issue.
I filed a bug report with the author of Call Announcer, but until then, uninstall Call Announcer if you want the bug to go away.
Related
I'm running Mammon's 1.0.4 DK28. This isn't really important as it's happened w/ every DK28 ROM I've used and it's the most extremely frustrating thing for me.
It goes like this...
I have my phone synced to a jabra earpiece and to the radio in my truck (Clarion CZ500)
I don't use my jabra much but when I do, I get the same weird behavior as in my truck.
In my truck, I get bluetooth connected. I can hear sounds etc. from my speakers. I can stream Pandora, etc. and it works fine. I can make a phone call and it will connect, but no sound unless i switch to speaker, then back to bluetooth.. After I hang up, I can't get bluetooth to produce sound at all. I disable bluetooth and try to listen to music etc. from the external speaker and only get sound from the phone's earpiece. If I make a call, and put it on speaker, still no sound from external speaker, only from the phone's earpiece. Then, after completing a phone call, the phone is sitting idle and makes a popping sound from the earpiece.. random time intervals but still happens until I power cycle the phone.
Any ideas as to how or why this is happening ?? It's extremely frustrating.
Thanks
I have this problem not just with android, but wp7 also. Whenever i plug my headphone in the music player would randomly start, stutter, and skip songs. The only way to stop this is to pull my headphone out. This happens with every android build i have flashed for the past year. How can i fix this?
I have one set of in-ear phones that cause skipping (and false calls on winmo) during playback, and I can't explain it. My best guess is that the 3.5mm jack is leaking signal into the connector for the stock headphone controls, sending false signals that the phone thinks are commands from the remote.
Try some other earphones,if it doesn't happen then it's something along those lines.
I also get this with my sennheiser cx270's, sometimes its fine, other times it goes berserk.
Same, no other earphones seem to fix this, so I'm thinking it's the jack. It happens every once in a while.
$1 gets you a reply
Cross posting from the CM7 Epic forum to get more exposure and see if there is anyone NOT experiencing this problem and also maybe see if this extends beyond CM7 to regular Epic GB users. Here is the original thread I created.
Here is the post:
The Issue: When the phone is placed into the Samsung Car Dock, and then subsequently a hands free BT call is placed, the audio quality over the hands free is terrible and unusable.
I have been experiencing this issue since I started using CM back in October, and it was only today that I finally (and accidentally) discovered the action that causes it to happen. For the longest time I thought the problem somehow centered on switching from playing A2DP audio (which always sounds just fine) to the phone call, though I couldn't repeat this consistently, as sometimes I could get a call with good quality, but most of the time, even with freezing Music so it didn't start automatically when BT/car dock were connect, calls just sounded horrible.
Today, all that changed and I figure out that no matter what the state of A2DP music is, as long as the call is placed/received BEFORE the USB connector of the car dock is slid in to place, the audio quality is just fine. If you put the phone in the dock and engage the USB connector and then place/receive a call, you run into my aforementioned issue. I tested to see if this was related to the Car Home app, and running the app and placing a call out of the car dock was just fine as well. You can place a call, and then plug in the car dock and everything is OK that way too.
So something has to happen when the car dock is physically connected to the phone that messes with the audio. Can someone attempt to repeat this problem so I know it is ultimately not someting weird with my car/head unit/whatever. I don't believe it is because I didn't experience this issue before I switched to CM7.
Click to expand...
Click to collapse
Bump on this topic, no one else notice this? Can people try this out and see what happens, even if you don't normally use the device that way?
TL;DR I LOVE my phone, these Bluetooth issues are going to make me smash it into a million pieces. Any custom rom's or fixes for the OEM rom that FIXES them once and for all? I had NONE of these issues on Android 5 on my old phone. A factory fresh phone with no added apps is STILL unstable.
Long read:
I pre-ordered the 6P and have had a mixed relationship with it the past 6 months, the thing pissing me off most is the Bluetooth on this thing.
I DID install MHC19I and it did not help, with anything.
Here's what's happening.
#1 I have a Moto 360 watch that drops bluetooth connection and when it restores, google voice search on the watch remains broken until I restart the phone. This was not an issue on my old phone.
#2 I also am having hell with headsets/speakers. I will be listening to a speaker, get a call, and the damn music doesn't pause and starts playing over the headset AFTER I answer the call, this isn't everytime, but it happens enough to piss me off.
#3 When I hang up the call, the sound does not always go back to the speaker, it says it is, but I hear nothing OR it says it is, and I hear the music coming from the phone. Play Music, Pandora, and Spotify. I have to go into bluetooth settings and force a reconnect. This is happening in my Car, in my house with my Yamaha BT receiver, with a Logitech BT adapter, and a jbl bluetooth speaker.
#4 Sometimes when I first reconnect to the speaker after being out of range, the sound stays at the phone even though it says the speaker is connected.
#5 Just can not keep a stable connection with my 2016 Acadia. The phone has locked up on multiple occasions when either making or receiving phone calls through the car. "Phone has stopped" or something like that.
I upgraded to Android N in an attempt to improve my situation in the least and I don't know what I expected. It's way worse.
Compound all the issues above with:
#1 Delayed notifications to my watch (it starts vibrating to notify me of a call AFTER my ringer has already been ringing 30 seconds)
#2 "mute phone calls on the phone" when connected to watch is broken (The ringer goes off no matter how many times I flip the setting on and off)
#3 It stops broadcasting the playing song information to the display via bluetooth to my car or receiver FREQUENTLY
#4 Answering a phone call via bluetooth occasionally locks up requiring a disconnection from the headset and then I can proceed with the call on the phone.
#5 It either doesn't send the audio to the headset and/or the bluetooth and watch controls lock up (can't change song or control volume, but the music continues playing fine.)
#6 The BIGGEST issue was my 2013, and now my 2016 GMC Acadia. I am going to crash it one of these days with all the dicking around I am doing with the phone when trying to listen to music or take a phone call.
Anyone? I am seriously contemplating giving up EVERYTHING I like about android and getting an iPhone JUST because of these Bluetooth issues (which DO NOT exist on the iPhone 6s).
I solved all my bluetooth issues by turning bluetooth volume all the way up, then turning it down 4 steps from full volume. No drop outs or disconnects from anything since!
I think you must have a defective phone. I have zero problems with Bluetooth on the 6p and I have 10+ Bluetooth devices I use at least 3 of them daily.
Sorry you're having trouble...
I completely factory reset my phone. NO third party apps. Running MHC19I. Music has been fine all day, phone calls are still a problem.
I dial a number, it say's dialing, but I never hear it ringing in my headset. Then the caller picks up and the call timer starts counting. I can clearly see it says it's sending audio via bluetooth and I hear NOTHING. Same on my car shows it's being sent to the radio, but the radio never get's the clue. It works when it wants too, and a restart of the phone always fixes it when it isn't working. It's very frustrating.
I think u might have a defective device BC I'm not experience any of these with my Bluetooth headset. And I'm Stock on MHC19i also .. Sorry u having these bad experiences.
Sent from my Nexus 6P using Tapatalk
Hi,
my audio playback crashes reproducibly after seconds to minutes when i listen to music (play a video, make a call..) with any -> wired <- headset or headphones connected.
After that i have to reboot the phone to get audio working again; just unplugging headphones leaves the device also silent until next reboot.
The crash affects incoming call ringing, calls, anything related to audio.
I don't now when it started, must have been during winter time because Bluetooth audio playback works with no problems.
I'm unrooted and on stock rom. The OTA update to nougat did not solve the problem, either, as well as deleting cache.
Motorola support told me to reset phone before further support steps will be considered. I did not yet reset the whole phone, because i need it during traveling..
If anyone knows the problem, maybe related to an app,... let me know
derlotse
Same thing here , stock or custom ROMs.FM radio works good but that's about it.
derlotse said:
Hi,
my audio playback crashes reproducibly after seconds to minutes when i listen to music (play a video, make a call..) with any -> wired <- headset or headphones connected.
After that i have to reboot the phone to get audio working again; just unplugging headphones leaves the device also silent until next reboot.
The crash affects incoming call ringing, calls, anything related to audio.
I don't now when it started, must have been during winter time because Bluetooth audio playback works with no problems.
I'm unrooted and on stock rom. The OTA update to nougat did not solve the problem, either, as well as deleting cache.
Motorola support told me to reset phone before further support steps will be considered. I did not yet reset the whole phone, because i need it during traveling..
If anyone knows the problem, maybe related to an app,... let me know
derlotse
Click to expand...
Click to collapse
I just installed viper for android and the problem seems to have gone away.