Develop Bugs

Omnia and Bluetooth headphone buzzing audio

Bought an Omnia a few days ago. Actually bought 2, but first one returned cause I thought it was defective.
Problem happens when I try to use my BT headphone. No problem in pairing, but as soon as I initiate (or receive) a call, I get an awfull noise (or buzz if you like) strong enough that it makes the headphone unuseable. As I said I had the same problem with both Omnias. I had this headphone (Nokia BH-101) for many months now and never had any problem.
I tried on 2 PDA and one smartphone without problem, so it kinds of rule out a headphone defect. Hard for me to believe both phones are defective on arrival, and showing the same problem on top of that, so also seems to rule out a phone problem. Incompatible???
Anybody ever had this kind of problem on an Omnia phone or any combination of phone/headphone?
Thanks for any helpful hint.

It might help if you posted which bluetooth headphone, but yes, I've seen cases in which a particular headset and phone were just incompatible.

I did put the model in my original post, but here it is again for quick identification: Nokia BH-101.
If anybody have this pairing (Omnia and Nokia BH-101), please let me know the result, good or bad!!!
Thanks

sounds familiar
I recentlyy bought a Jawbone 2 and i get a really loud buzzing intermitently when using it with my Mogul running nuerom titan build .Ive exchanged the headset and still have the issue but my otherr 2 bt earpieces work fine. Any help would be awesome Thanks.

[Q] To anyone with Bluetooth headphones

I bought the One X because the bluetooth performance of the Sensation was pathetic, and worryingly it seems the X has the same problem somehow.
I find that when wearing my Plantronics Backbeat 902 headphones that the connection is broken by something so simple as turning my head away from the pocket (front top jacket). I can hold the phone in my hand and simply pinch the top corner next to the camera and SIM slot to totally kill the connection.
At first it seemed that it must be the headphones getting old because how could the One X have a problem so widely known from the previous flagship? Well my Galaxy Tab 8.9 has no such problem. I can hug the tab as much as I want and just TRY to kill the signal, it will not happen. I can walk two rooms away and keep listening to music but the One X fails even a half meter from me if I turn the wrong way.
Can anyone else verify this behaviour? It is not that I want it to be the case, perhaps mine is just broken (odd because the screen/battery seem fine!) but if HTC have failed on another antenna then I will very much want a refund because two flagships in a row off contract is just too much to forgive!

Hi,
One X and Samsung HS3000 - I have found that connection stays mostly good, with maybe one or two tiny glitches per song - perfectly listen-able, and not as bad as what you describe, but not as good as I would have hoped - I am going to see if it is due to using extreme quality spotify downloaded tracks I'm playing (since the HS3000 is aptX it should stream at that kind of bitrate). I'll try lower bitrate and see if that makes a difference.

seems to work fine with Nokia BH-505 but i got cut off around 10m away.
Tried with an iPod Touch and it's about the same distance.

With Sennheiser MM400, I get perfect reception, in a leather case, in my pocket however I turn my head. In open air I get around 10 metre range. Maybe your bluetooth antenna is defective. If it's in your pocket make sure the screen faces inwards to your body. Also the receiver in your headphones could be on either side, so switching pockets may help.
Don't forget, other devices may appear to have greater range if they are transmitting at a lower quality than the One X. Also, I guess it could be that some headphones struggle to cope with higher bit rates if they don't have much buffer memory.
I'm blown away by bluetooth stereo quality compared to my sensation. My headphones had been sitting gathering dust until now.
Sent from my HTC One X using XDA

Thanks very much for the replies, that helps a lot. I cannot believe this but it is the phone.
I remembered I have a PS3 headset by Sony, never failed me. I just called my girlfriend and from the distance of my hand to my ear while sitting down - not even holding at arms length - I can KILL the signal by pinching the corner where the front camera is.
I love this device, it is truly exceptional. But two HTC flagships in a row that I paid for outright have failed in the thing I use daily. I do not think I can face trying repair this time. Never helped my Sensation Bluetooth.
So that's two headsets by two brands, both work perfectly with any other device (and a Nexus S) but the two HTC phones just die when I use them.
Coincidence probably but after this much money, I am going to try to get my money back. Even paid for two years accidental damage warranty this time. Really quite unhappy about this now..
Again, thanks for the feedback.

nailerr said:
Thanks very much for the replies, that helps a lot. I cannot believe this but it is the phone.
I remembered I have a PS3 headset by Sony, never failed me. I just called my girlfriend and from the distance of my hand to my ear while sitting down - not even holding at arms length - I can KILL the signal by pinching the corner where the front camera is.
I love this device, it is truly exceptional. But two HTC flagships in a row that I paid for outright have failed in the thing I use daily. I do not think I can face trying repair this time. Never helped my Sensation Bluetooth.
So that's two headsets by two brands, both work perfectly with any other device (and a Nexus S) but the two HTC phones just die when I use them.
Coincidence probably but after this much money, I am going to try to get my money back. Even paid for two years accidental damage warranty this time. Really quite unhappy about this now..
Again, thanks for the feedback.
Click to expand...
Click to collapse
Stating the obvious here but have you tried in multiple locations to rule out interference?
I'm about to test my headphones again and try pinching the corner as you described.
Sent from my HTC One X using XDA

familyhousing said:
Stating the obvious here but have you tried in multiple locations to rule out interference?
I'm about to test my headphones again and try pinching the corner as you described.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Nope, can't replicate it. In fact the only way I can get any loss if quality at all is to walk 10m away. Looks like you got a duff phone.
Sent from my HTC One X using XDA

familyhousing said:
Nope, can't replicate it. In fact the only way I can get any loss if quality at all is to walk 10m away. Looks like you got a duff phone.
Stating the obvious here but have you tried in multiple locations to rule out interference?
I'm about to test my headphones again and try pinching the corner as you described.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Overly. Though more specifically right now, no. Which is why I can say a Samsung telephone or tablet work with the Plantronics or Sony headsets where the Sensation and One X do not. Same location, would have to be super specific interference.
I ride to and from work 6 days a week, and often between. This is why I use A2DP headphones for music or podcasts, sometimes calls. The amount of ground I cover should rule out any localised problems.
The most bizarre thing I can say is that out the box it seemed to be perfect, I was relieved. Since 2 weeks or so it has just dropped into a near non functional state. I would willingly say the power in my house was at fault but that has left so many other devices alone, including my girlfriends iPhone 4 and Nexus S.
I also tinker with tech a lot, just not down at the electronics level, so right now I feel I have tried everything (again) and been as good to the device as I could be, and just really, really unlucky.
Evidentially not all units are at fault so I will not play that stupid card of "HTC Can't make phones!" that some do when they have an issue, but you must understand I feel pretty ripped off nonetheless by now!

pleased I found this thread as I also seem to have the exact same problem. I have a fairly old Sony Bluetooth stereo headset that I used with my desire without any issues, with my one x if I move more than a metre away or place my hand between the devices they stutter and stop. I hate to think my phone is faulty as it seems fine in all other respects and reading the other stories that is fairly rare at the moment. I am happy to try other headsets as this one is quite old but if it is definetly a phone issue the sooner I sort things the better. does anyone have suggestions on things to try

scointer said:
pleased I found this thread as I also seem to have the exact same problem. I have a fairly old Sony Bluetooth stereo headset that I used with my desire without any issues, with my one x if I move more than a metre away or place my hand between the devices they stutter and stop. I hate to think my phone is faulty as it seems fine in all other respects and reading the other stories that is fairly rare at the moment. I am happy to try other headsets as this one is quite old but if it is definetly a phone issue the sooner I sort things the better. does anyone have suggestions on things to try
Click to expand...
Click to collapse
Not specifically, but if you do try something new (mine are also old - but work perfectly with other devices) please do report back. I'd love to keep this phone but a repair will invalidate my option for refund.

HOX on 1.2.9 and no issues at all, I'm using it alongside the HS3000 and connection is rock solid. Phone in pocket, and HS3000 clipped to my shirt. Even maintains a solid connection whilst using the London Underground.
However was in PC World and had major interruptions due to the various invisible signals in that store.
Generally it's fine, streaming via Spotify using Extreme Quality and via Poweramp.

nikzDHD said:
HOX on 1.2.9 and no issues at all, I'm using it alongside the HS3000 and connection is rock solid. Phone in pocket, and HS3000 clipped to my shirt. Even maintains a solid connection whilst using the London Underground.
However was in PC World and had major interruptions due to the various invisible signals in that store.
Generally it's fine, streaming via Spotify using Extreme Quality and via Poweramp.
Click to expand...
Click to collapse
I am slightly curious to see if the different BT revisions are at play - but that is super hard to work out.
Both my headsets are 2.1 devices, Sensation was 3.0 and One x is 4.0. The phones that worked properly are 2.1+EDR. But the Galaxy tab is 3.0 and works perfectly. So...
I am still thinking internal antenna of phone.

nailerr said:
I am slightly curious to see if the different BT revisions are at play - but that is super hard to work out.
Both my headsets are 2.1 devices, Sensation was 3.0 and One x is 4.0. The phones that worked properly are 2.1+EDR. But the Galaxy tab is 3.0 and works perfectly. So...
I am still thinking internal antenna of phone.
Click to expand...
Click to collapse
It should be backwards compatible. But you got 2 headsets and tested on various devices so the BT in the phone might not be all that.
Have you tried updating your firmware? Do you have the latest 1.2.9?

nikzDHD said:
It should be backwards compatible. But you got 2 headsets and tested on various devices so the BT in the phone might not be all that.
Have you tried updating your firmware? Do you have the latest 1.2.9?
Click to expand...
Click to collapse
It's 1.29.x.x but yeah. I did wonder if that was at play, forgot to ask what other people were running earlier since when mine was working properly it was 1.26 but I cannot place where the problem began as I was busy/sick/away.

UPDATE : ok tried in the same place with my old sony HBH DS970 headset and major cut out if i cover headset or top of phone or walk more than a metre away.
Tried exactly the same with my turtle beach px5 headset (which has blutooth obviously) and everything is much better walked 5 metres no problems, covered phone with no real problem (did glitch just once).
I am running 1.28 T-mobile branded so now need to narrow down if certain types of profile or headset brands are the problem.
Pity I really like my sony headset

scointer said:
UPDATE : ok tried in the same place with my old sony HBH DS970 headset and major cut out if i cover headset or top of phone or walk more than a metre away.
Tried exactly the same with my turtle beach px5 headset (which has blutooth obviously) and everything is much better walked 5 metres no problems, covered phone with no real problem (did glitch just once).
I am running 1.28 T-mobile branded so now need to narrow down if certain types of profile or headset brands are the problem.
Pity I really like my sony headset
Click to expand...
Click to collapse
Thanks, adding some interesting details there.

so next question....can anyone recommend some cheap (£50ish) portable headset that works well with HTC one x and sound reasonable.

Would love to help you out there but clearly not in the situation. I was also looking into a new set with Apt-X (as the X supports it) but settled on none before realising the phone was a bust unit.

No problems with my HOX as well and i use 2 headsets (depends which one is charged) : Plantronics and Nokia.I don't have any problems with them so far and i keep my phone preety far from the headset.

I find that with my Creative WP-350 headset and my phone in my jean pocket, if I put my hand in my pocket over my phone I get the occasional break in the connection but that's the only situation is happens and is fairly avoidable.

[Q] GS3 and Eclipse CD5030 - no BT audio

as the title states, I have connected the two devices and for some reason i couldn't hear the person i am talking with. But the person i called can here me loud and clear.
Troubleshooting done...
1. Connected an iphone4 and it does work. That means the TX/RX of my car stereo is working properly.
2. I then tried connecting my GS3 to a different bluetooth speaker, it is working proplerly. Making calls and streaming audio.
What should i consider looking for to find a fix? My doubts are the compatibility of the bluetooth. If it is, is it possible to fix it?
Thanks

I have a similar issue on my pioneer 80prs and eclipse mkii 7200 where tli hear them but they can't hear me... My phone mic gets used as the input method instead of my decks mic.... Never solves it and it only started doing this once I got to jelly bean back on my galaxy nexus
Sent from my SGH-T999

I see. Well i have tried loading a different rom thinking that was the case and sadly still does the same thing. The only weird part was i can hear all the touch sound on the phone thru the car's speakers but when call/music is initiated you can't hear nothing.
I have found a solution by selling the HU and getting a new one. This time i will be asking the seller if it is compatible or not.

[Q] Jaybird Bluebuds X problems on Galaxy S6?

Anyone having any Bluetooth issues with the S6? In particular, with the Jaybird Bluebud X earbuds? I emailed Jaybird support to see if they are aware of any issues. Based on my research, I cant tell for sure if there is a known issue or not.
Basically, heres whats happening. This is the first time Im using a Bluetooth headset but pretty confident this isnt a settings issue.
Bluetooth pairs fine. But if my phone is not within a foot or two, or not in direct line-of-sight of the earbuds, the sound cuts in and out, or totally out. So if I put the phone in my pocket, I lose sound. If I hold the phone behind my back, I lose sound. Bluetooth stays connected, but the sound goes out abruptly. It doesnt get distorted or faint, it just cuts out. If I bring the phone back in line-of-sight, or close to the phone it works great. But it kind of defeats the purpose. I had to hold the phone at my chest on my walk to work this morning in order for it to work right. If I cover the top half of the phone, it goes out (eerily similar to the old iPhone issue with the antenna, if you touch the frame a certain way it seems to go out). But sometimes depending how I touch the controller-side earbud, it goes out. Its as if anything that blocks the line-of-sight or sensors on the phone/earbud, it blocks sound. I tested this in Safe Mode as well and the problem is still there.
For whats its worth, I have a Jambox at home and the S6 connects fine with it, no matter where I am in the apartment or how Im holding the phone. So I really doubt this is a problem with the phone but who knows. I have my old S4 on KitKat at home that I will test with tonight as well.

Some new information after some testing at the office this morning.
Tried the earbuds with a Galaxy Note 4, and iPhone 4S, and the same problem is happening. So thankfully it doesnt look like an issue with the S6. I'll be sending these earbuds back for a new pair and report. If problems continue, obviously I'll be trying another kind of earbuds.

Stopped and picked up the Plantronics Backbeat Go 2. So far, these are working perfectly though they may not be quite as loud. But its good to know it doesnt appear to be a problem with the phone. Must be some kind of compatibility issue with the Bluebuds. I have a replacement set of Bluebuds on the way so Ill report back if they work any better than the first pair.

My bluebud x does the same. Walked over a foot away and the music stops. Walk back closer to the phone music comes back on.

Received my replacement Bluebuds and the same problem occurs. So there must be some kind of compatibility issue.
Jaybird says they are unaware of a known issue but I find that hard to believe.
So Ill be using the Plantronics for now since they seem to work fine.

Samsung S6 issues
I recently purchased the JayBird BlueBud X and literally had the same issue. It connected and paired perfectly fine, but it only lasted for about 10 seconds before the sound went away. You could press any button on the BlueBuds and it would start up again for a few seconds and the sound would go away again. It paired perfectly with my sister's Samsung Galaxy S4 and my friend's iPhone 5. I called their technical support and they suggested, I send it in and get a replacement. I wasn't having any of that BS. I just returned them. Sadly, they were the most comfortable earbuds, I have ever worn. There is some compatibility issues that need looking into.
ryan2202 said:
Anyone having any Bluetooth issues with the S6? In particular, with the Jaybird Bluebud X earbuds? I emailed Jaybird support to see if they are aware of any issues. Based on my research, I cant tell for sure if there is a known issue or not.
Basically, heres whats happening. This is the first time Im using a Bluetooth headset but pretty confident this isnt a settings issue.
Bluetooth pairs fine. But if my phone is not within a foot or two, or not in direct line-of-sight of the earbuds, the sound cuts in and out, or totally out. So if I put the phone in my pocket, I lose sound. If I hold the phone behind my back, I lose sound. Bluetooth stays connected, but the sound goes out abruptly. It doesnt get distorted or faint, it just cuts out. If I bring the phone back in line-of-sight, or close to the phone it works great. But it kind of defeats the purpose. I had to hold the phone at my chest on my walk to work this morning in order for it to work right. If I cover the top half of the phone, it goes out (eerily similar to the old iPhone issue with the antenna, if you touch the frame a certain way it seems to go out). But sometimes depending how I touch the controller-side earbud, it goes out. Its as if anything that blocks the line-of-sight or sensors on the phone/earbud, it blocks sound. I tested this in Safe Mode as well and the problem is still there.
For whats its worth, I have a Jambox at home and the S6 connects fine with it, no matter where I am in the apartment or how Im holding the phone. So I really doubt this is a problem with the phone but who knows. I have my old S4 on KitKat at home that I will test with tonight as well.
Click to expand...
Click to collapse

The same thing happens with my LG Tones, the antenna seems to be in the left side on them and having to go through my body to the phone in my pocket is just too much. It's been an issue with both phones I've used it with, the S6 and the S4 before it. Bluetooth in low power devices just seems to have to be super weak.

Has anyone found a fix for this problem as yet? I have the same issue with my bluebuds when I am at the gym as well.

You don't know how much effort I put into figuring out it was the phone and not the bluebudsx. Ended up returning and getting G new headphones 3 times, before sending in my phone to be replaced. Figured out that the new phone was still dropping the connection too, so it had to be the phone and not the headphones. It really sucks because I run twice daily, and Bluetooth made things so much easier. It looks like just bad hardware from Samsung, so there won't be a fix coming. Just gonna have to used wired headsets again...
Oh and for the record, I'm not having issues with distance causing drops. The drops occur randomly after usage, anywhere from 5 minutes to 6p minutes into my run. So everyday is a new day when I go running, since im always worrying about when my music will cut out and mess up my rhythm. Tested bluebudsx with my N5, Note 4, and EVO LTE. None cut out randomly during runs. So I came to the conclusion it has to be bad hardware on the S6.

glad I saw this, I was considering these for jogging/exercising, I'm presently using a Samsung HS3000 with a pair of Beats UR Beats, guess I'll stick with that combo
sent from my S6 using tapatalk

I have the LG tone pros and same thing happens to me. I also have a pair of Plantronics Backbeat fits and it also does the same. The phone has poor Bluetooth as well as antenna. My signal sucks most of the time
Sent from my SM-G925P using XDA Free mobile app

No issues here and i use them all the time at the gym. Always go drink some water and leaving my phone behind without a hitch. Galaxy S6 W8 Variant with XtreStoLite 1.4a (5.0.2)

Xtrestolite is a Rom for S6, right? That makes me think that it maybe a software issue with the phone not a hardware issue.

I'm wondering if it has to do with 5.0. 2 Android. Has anyone flashed the new 5. 1.1 release? If it is software that's causing issues, maybe something was changed between versions. I would test it myself but I need to stay on 5.0.2 for personal reasons.

numel007 said:
I'm wondering if it has to do with 5.0. 2 Android. Has anyone flashed the new 5. 1.1 release? If it is software that's causing issues, maybe something was changed between versions. I would test it myself but I need to stay on 5.0.2 for personal reasons.
Click to expand...
Click to collapse
Just got my jaybirds and my S6 (G925T) is running 5.1.1 and is having the same issue. Music will play for 30sec-1min but then it cuts out. The bluebuds x work fine on my Nexus 7 which is also running 5.1.1
---------- Post added at 03:11 PM ---------- Previous post was at 02:40 PM ----------
It seems like I was able to fix the issue for my S6. I enabled Bluetooth HCI snoop log in the Developer options and then copied the file (btsnoop_hci.log) to my computer and found in Wireshark that my Logitech bluetooth adapter was showing up a lot even though it was not paired to my phone. I disconnected the adapter and found that I can play music without the dropped audio. I'd recommend everyone to take a look at their logs and see if there is any weird traffic from other bluetooth devices. It's somewhat disconcerting that a device not even paired to my phone could cause problems with the headphones.

icj217 said:
[/COLOR]It seems like I was able to fix the issue for my S6. I enabled Bluetooth HCI snoop log in the Developer options and then copied the file (btsnoop_hci.log) to my computer and found in Wireshark that my Logitech bluetooth adapter was showing up a lot even though it was not paired to my phone. I disconnected the adapter and found that I can play music without the dropped audio. I'd recommend everyone to take a look at their logs and see if there is any weird traffic from other bluetooth devices. It's somewhat disconcerting that a device not even paired to my phone could cause problems with the headphones.
Click to expand...
Click to collapse
Interesting. I'll try that, but I'm thinking I have a different problem since I can be walking around or running outside and connections will still drop randomly.

I am having the same issue on Samsung Galaxy S4 and Samsung Galaxy S6 Edge +. Soooo annoying. The only pattern that I was able to figure out is that sound will cut out every time there is a Bluetooth interference. Even when there are no other Bluetooth devices within miles. When ever you have any other apps running in the background that try to connect to Bluetooth devices sound will cut out. For example when u have some fitness tracking app trying to connect to a Bluetooth device that is not with you. It seems that there are few different ways that your sound cuts out and all has to do with Bluetooth interference or searching. It would be awesome if someone has a solution.

Samsung GS6 and Jaybird Bluebuds X connecting
Hello all,
I was having the same issue with my Samsung GS6 ATT running 5.1.1.
I would put the phone in my pocket or walk a few feet away and the signal would drop out (skip).
Reading all the posts on here stating it wasn't the buds I tried the one thing that possibly on mine can cause the bad signal.
I removed my case! (OBLIQ case)
Since doing that I can walk 30 ft away without being in line of sight of my phone with no drops.

I'm having no issues during training, with my new pair of Jaybird Bluebuds X and my Galaxy S6 running Stock 5.1.1. BTW I'm using a Ringle SLIM case on my S6.
It's there any way to show battery percentage on an Android Phone? . This is possible on IOS.

Excellent troubleshooting, icj217 - I experienced this same issue to where the audio would drop between every 5-8 mins on my GS6 using the Bluebuds X (regardless of distance). I've cleared all the paired devices (including the Bluebuds X) on my GS6 and re-paired the headphones and they seem to be working fine now. I'm wondering what's going to happen once I re-pair all my other bluetooth devices. If I inherit the problem again, this will be just another reason to dump the GS6 and go back to my Nexus 5.
icj217 said:
Just got my jaybirds and my S6 (G925T) is running 5.1.1 and is having the same issue. Music will play for 30sec-1min but then it cuts out. The bluebuds x work fine on my Nexus 7 which is also running 5.1.1
---------- Post added at 03:11 PM ---------- Previous post was at 02:40 PM ----------
It seems like I was able to fix the issue for my S6. I enabled Bluetooth HCI snoop log in the Developer options and then copied the file (btsnoop_hci.log) to my computer and found in Wireshark that my Logitech bluetooth adapter was showing up a lot even though it was not paired to my phone. I disconnected the adapter and found that I can play music without the dropped audio. I'd recommend everyone to take a look at their logs and see if there is any weird traffic from other bluetooth devices. It's somewhat disconcerting that a device not even paired to my phone could cause problems with the headphones.
Click to expand...
Click to collapse

Headphones and in-call audio issues

Not sure if it had anything to do with the update, but I have been power cycling my phone a lot lately...
Headphones: My headphones don't seem to be registering that they're in, so the sound comes through the speakers--but the headphones work when plugged into other devices. (I have picked up a pair of bluetooth headphones until I figure it out, which work fine.) After power cycling the headphones work again for a while somehow, but will randomly stop again, so it must be a software issue. It could have to do with being unplugged while audio is going?? Not sure
In-call: I can't hear the other person, but they can hear me. If I switch to speaker phone, I can hear them (not sure if they can hear me while on speakers, they usually hang up by the time I realize they are really there but I can't hear them...) It's so weird. I have to say, "I can't hear you, I'll reset my phone and call you back in a minute".
Anybody else with this problem???

I've been struggling with the same problem on 3 different Fire Phones. All phones are running Fire OS 4.6.3. I discovered this problem after plugging into my car stereo via the 1/8" audio jack. If not immediately, shortly after disconnecting the cable I would be unable to hear the party on the other end during a phone calls, though they could hear me. I also found that the jack would no longer switch from Speaker to Wired audio and vice versa when I plugged a cable into and out of the 1/8" audio jack.
It looks to be an OS issue as the problem is remedied by a restart. I am really curious if I happened to get 3 lemons or if anyone else experiences this. If this is an issue with Fire OS, have so few people used the audio jack? I am tempted to install Cyanogenmod to see if this remedies the problem, though I would expect this sort of issue to occur with Cyanogenmod as opposed to the stock FireOS install.

Thanks for letting me know there is someone else out there with the same issue. I hate thinking I'm the only one!
BTW alexandergrig did you get a warranty replacement for them or you just bought 3 when they were on sale or something?? I am thinking of trying to replace it on warranty, since the issue is new-- it just started a couple of weeks ago, and I didn't experience the headphone/call "mute" issue throughout most of the life of the phone. The other thing that I don't get is why it won't let me take a video--it stops after 1 second (also a recent issue).

The phones were not on warranty replacement but rather purchased new. How long had you been using your phone without issue? What version of FireOS are you currently on? Have you side loaded Google Play?
Today, for example, I had no issue with plugging headphones in and removing them. I later plugged the phone to my car stereo via mini-jack and had no issues playing music or placing and receiving calls (using the speakerphone) while it was plugged in. When I unplugged it, I was able to make calls. Later when I plugged the phone into my car stereo again, I had the same problem. Basically all the audio was being routed to the speaker and not the audio jack. No matter how many times I plugged and unplugged the cable, no audio was being sent through the audio jack.
I also happened to try the Soundabout app on the Google Play store, thinking that perhaps the audio was not being routed properly. Unfortunately, when I forced the output to the "wired" audio jack, at best I would hear some popping noises. All this gets resolved with a restart, however inconvenient that may be.
I find it hard to believe that the 3 phones I have worked on all happen to be lemons, though I guess it's possible. I wish I could get some feedback from others to determine if they are having any such issues. Like I said before, this is something that you might expect from a custom ROM not a stock OS install. I'm not sure how much of a pain making an Amazon warranty claim would be. If you opt for this, I would appreciate it if you could let me know how this goes and if the replacement unit works properly. Part of me wonders if a Cyanogenmod install would remedy this issue. If not, then it's got to be something more complicated beyond my ability to troubleshoot. I am very tempted to try.

I got the phone in February, and it has worked fine until about two weeks ago. My headphones (the ones that come with the phone) started malfunctioning, and there was an OTA update around that time, so I am suspecting it could have been either thing. I side loaded Google's apps during my first week with the phone, and my current OS is 4.6.3 (463001620) [but I don't know why is says "Installed Tuesday, February 18, 2014" since it has definitely been updated since then...]
I'lll let you know how the warranty stuff goes. Maybe they'll give me a replacement that works...

All 3 phones were on 4.6.3 while having this problem. They had immediately been updated to 4.6.3 after purchase. I did test this prior to installing all the Google Play services, but there was no difference. I have not tested this on any other version of FireOS.
Today I made a point to test this more thoroughly. Phone works properly while connected to car stereo via audio jack. I can call out via Speakerphone without issue. However 5 times today when I disconnected the mini jack from the phone, I could no longer router audio through the jack when plugged in again and I experienced the issue where I could not hear the person on the other end of the call but they could hear me.
Plugging in headphones also would not work. This evening, I tested it with a pair of stock apple iPhone earbuds and it has not been behaving in the manner described above. I listened to music for 15-20 minutes, unplugged it and then I'm able to hear the music through the phone's speaker. After plugging it in again, the audio is properly routed to the headphones again. I was able to do this about 10 times without issue. Then at some point the same issue occurred.
I'd like to say that it's an issue with 4.6.3 or perhaps some sort of service that is not handling the audio routing properly and needs to be restarted via a reboot. I kind of wish that I would have tested this issue on another version of FireOS. Despite everyone's disdain with FireOS and my own past inclination to play around with stuff, I really wanted to stick with the stock FireOS, but this lack of proper functionality is bothering me so much I might be inclined to try CM11.

I don't know if this will help you but there's an app called SoundAbout that will force audio through the headphone interface whether the phone thinks a headphone is plugged in or not. You'd have to get a copy of the apk and sideload it on fireOS though. https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix

I had SoundAbout installed a few days ago but that didn't seem to solve the problem. When I force switched it to the audio jack, I got nothing or some pops. It just seems something gets corrupted or quirky until one restarts the device.
danielnealclark, today I was trying to shoot some video with the Fire phone and ran into the same problem that you had by the way. I'll start another thread on this issue to see if anyone else has experienced this.
I only add this because it's getting to the point where I am very tempted to install CM11. If the sound issue persists (though I'm sure other issues might crop up then, lack of mute during a call being one as I understand it...) then I'll have to give up and come to the conclusion that it is some intermittent hardware issue on some of these units.

Let me know how CyanogenMod works if you try it. It prob has it's own issues too. I am going to try to get a new phone through the limited 1 year warranty. I'll keep you posted about the process

Got a replacement phone, and it worked fine until today...
I thought that a certain pair of headphones were the culprit, and I never should have plugged them in to my replacement phone (they are official amazon fire phone headphones BTW). This pair of headphones went bad and were only working in one ear when in the fire phone (but they work fine in both ears on my computer, which I don't understand) and it was around the same time my last phone had the headphone issue described at the beginning of the thread, so I thought the issues may be related. I tried them today, and oops, they messed up another phone!
From the other posts on this thread, there is an issue with certain headphone jacks--not sure why. But if a certain headphone jack gets plugged in, the phone will forever think (until power cycling) that there are headphones in during a call, and never think headphones are if you try to plug in headphones for music/games.
I guess I still have it under warranty since it is a replacement through Amazon. I'm gonna try to do some resets, troubleshooting, etc...
So pissed right now

I've been having this issue as well. It is very annoying!

I have the same problem, as I previously posted. Unfortunately nothing I did remedied the problem nor was I able to find out any more information.
Daniel, did you end up getting Amazon to replace your phone previously, as you had mentioned?
I honestly think that this is not a problem particular to only a few models. I don't feel that a replacement would help because sooner or later it arises again it seems. It could very well be a jack problem, but I really feel this is some low level quirky OS issue. Originally I had mentioned that I might switch to CM. I've decided that this would lead to additional quirks going this route, so I will continue to keep my phone stock. The true test is if someone with CM experiences this issue or if switching to CM remedied the problem. Unfortunately, I've had so many frustrations with technology as of late and so little time, I don't have it in me to fiddle around anymore. I'm not sure if we can expect Amazon updates to remedy this, and all we can do is hope some day we get an update.
My main problem was that I use my Fire phone to connect to my stereo via Aux input. So I was constantly having issues. I ended up simply purchasing a USB bluetooth adapter for my car stereo and going wireless with the Fire phone and it's worked well. I must admit my Fire phone is not my go to phone for listening to music with headphones because of this, but I always found that the Amazon earbuds were less likely to cause this problem than other ear buds in my case.
After a long listening session, the only thing that helped me was simply rebooting the phone. A really crappy solution, but definitely more productive for me than continuing to tinker with this issue for me. Or going bluetooth. For those experiencing this issue, please keep us updated if you find a long lasting solution or if you have experienced any remedy with CM. Or, if our farfetched dream of an Amazon update were to become a reality...
All the best in the New Year folks!
danielnealclark said:
I thought that a certain pair of headphones were the culprit, and I never should have plugged them in to my replacement phone (they are official amazon fire phone headphones BTW). This pair of headphones went bad and were only working in one ear when in the fire phone (but they work fine in both ears on my computer, which I don't understand) and it was around the same time my last phone had the headphone issue described at the beginning of the thread, so I thought the issues may be related. I tried them today, and oops, they messed up another phone!
From the other posts on this thread, there is an issue with certain headphone jacks--not sure why. But if a certain headphone jack gets plugged in, the phone will forever think (until power cycling) that there are headphones in during a call, and never think headphones are if you try to plug in headphones for music/games.
I guess I still have it under warranty since it is a replacement through Amazon. I'm gonna try to do some resets, troubleshooting, etc...
So pissed right now
Click to expand...
Click to collapse

alexandergrig said:
For those experiencing this issue, please keep us updated if you find a long lasting solution or if you have experienced any remedy with CM.
Click to expand...
Click to collapse
I second that post! If anyone solves this one, let us know.
alexandergrig: I did get them to send me a new phone, since it was under the 1 year warranty. The phone call took about 45 minutes, with me trying to convince them by plugging in headphones/unplugging headphones to show that it was really broken. Before that call, though, they told me the first thing I had to do was perform a factory reset before they would even consider progressing to a replacement. [BTW the Fire phone has a great native backup tool if you are just migrating from one fire phone to another, it's all cloud based]. The new phone was a refurb.
I think I'll try the bluetooth thing for my car, that's a great idea. I really like my bluetooth headphones for work (as a bonus I found out they connect to my computer super easy too--at the same time as my phone even--so I can run desktop-only music sites)

Curious if anyone was able to fix this. I had this occur on my original Fire Phone. Amazon replaced it in Nov 2015 and my new one just started doing this....

jagernbeer said:
Curious if anyone was able to fix this. I had this occur on my original Fire Phone. Amazon replaced it in Nov 2015 and my new one just started doing this....
Click to expand...
Click to collapse
Good luck. I also am on my 2nd Fire, and like you have the same problem back again. The funny thing is, it was caused by the stock headphones, other headphones gave me no problems. So what did I do? I gave up! And now I LOVE LOVE LOVE my bluetooth headphones. They are so easy to use and no more cords. Try it out, you'll never go back (until the batteries die... but they charge pretty quick)
Good luck to you.

I experienced this problem on 3 separate Fire Phones. So either I am very unlucky or this problem is more widespread than we know. Because of this, I doubted that a replacement would help me. I will say that I have used my one 64gig Fire Phone without this problem being an issue for months and so I came to my own conclusion which might not end up being very helpful but...
I was able to experience this constantly when I made it a point to plug and unplug the headphones for testing purposes (both stock Amazon as well as the older Apple earbuds). Ultimately, the way I ended up using my phone's audio output was by streaming audio via bluetooth to a USB bluetooth adapter connected to my car stereo almost daily. Also most every day I would usually go from the Bluetooth audio in the car, to plugging in my headphones for my 3 mile walks, and then unplugging the headphones and reconnecting via Bluetooth in the car to drive home. Doing this for the past many months, I did not encounter one issue with placing calls via the phone itself, speakerphone or even via the mic on the earbuds.
Because of this I am concluding (as I initially believed) that it might not be hardware but rather the Fire phone's low level OS/system software that governs the audio jack that happens to be buggy. It's like there is an issue with the jack status detection routine and it gets "stuck" in one mode. I may be wrong, but there is a good possibility that Fire phone users that do not experience this problem, very well might start if they constantly plugged and unplugged their headphones from the jack, attempting to place and/or receive calls in between. At some point this issue might arise. But in my experience it goes away and corrects itself until the next time, unless anyone else has experienced otherwise.
Due to the lack of significant continued development of the Fire Phone, Amazon will likely not address this problem via an update. My sense is that if not everyone is experiencing it because it is a software issue, then it's prevalence is due to usage patterns. I, like others, in the beginning found this to be a constant problem the more I tested it, especially with plugging and unplugging the headphones and making calls. With my 3 phones, I have a hard time believing it's actual hardware only because it eventually seems to resolve if I change my usage patterns.
Might be totally different for you guys, but I guess this is my final conclusion. I sold one of my 32gig Fire Phones and still plan on using the 64gig, despite picking up a couple of other phones.
A.G.