I bought a Touch Pro 2 off of craigslist and stupidly didn't make a call before buying it. I thought everything was good since the phone was brand new with all accessories unused. When I came home I noticed the sound didn't work and the headphones icon kept appearing on top of the screen. I hard reset the phone and it still doesnt work. Does anyone know what could cause this? I unlocked the phone before realizing this problem and the seller now tells me the unlock caused this which I don't believe.
Does the sound work through the headphones at least? Perhaps there's something stuck in the headphone jack or the miniusb port?
Things look rough for you, man...
When I plug in the headphones it works fine. It doesnt look like anything is damaged inside the USB input.
When I plug in the y cable the voice command comes on, is that normal?
No.
Somehow your TP2 is stuck in headset mode.
With a normal jack this was a minor issue, (toothpick in the hole to free the switch) but with the miniUSB it's a major issue.
What I mean: With a normal jackplug we could solve it, but now we can't, I'm affraid.
When a hard reset doesn't solve this, you've got a hardware problem.
I'm affraid you'll have to bring it to a service center
I have an HTC TP2 from T-MObile, Windows mobile 6.1. My phone speaker no longer works. If I get a phone call I either have to put it on external speaker phone or plug in headphones to hear the other person. not looking to spend the money on a new phone. does anyone have any ideas how to fix this?
i have tried a soft and hard reset and have pulled the battery. but still no luck.
If a hard reset did not resolve the issue, and you are running stock software I would guess that it is a hardware issue. Specifically the speaker has failed, and you will need to replace/look for faults on the ribbon cable inside the lcd panel where the internal speaker is attached.
wizardknight said:
If a hard reset did not resolve the issue, and you are running stock software I would guess that it is a hardware issue. Specifically the speaker has failed, and you will need to replace/look for faults on the ribbon cable inside the lcd panel where the internal speaker is attached.
Click to expand...
Click to collapse
This. Unless you've done it before, you're likely to break something as well - taking apart a mobile phone (or rather the 'putting back together' part...) is NOT simple.
Hi,
Unrooted stock N7 (2013) here. This is strange but when I plug in my headphones the tablet will reboot as soon as audio starts playing. This happens with any app, any headphones. I DO get sound out of the headphones for the 5 seconds or so between plugging them in and the device rebooting. Any ideas??
budtz said:
Hi,
Unrooted stock N7 (2013) here. This is strange but when I plug in my headphones the tablet will reboot as soon as audio starts playing. This happens with any app, any headphones. I DO get sound out of the headphones for the 5 seconds or so between plugging them in and the device rebooting. Any ideas??
Click to expand...
Click to collapse
Sounds like your headphone-jack is causing a short circuit. Are there any control-buttons on your headphones? (they work with causing a short circuit). Is there any dust in the headphone-jack? If thats not the case, you might want to return your unit.
Edit: If this problem wasn't there from the first device-usage: have you tried a factory reset?
Yeah a short was my first thought as well, but it's hard to see that being the case since I actually DO get sound out of the headphones? It's had the problem ever since I got it and returning is not really an option since I bought it in on a trip in the States and I live in Europe. Factory reset doesn't help. I've tried with different headphones.I guess it's most likely a hardware fault I'll have to live with....
budtz said:
Yeah a short was my first thought as well, but it's hard to see that being the case since I actually DO get sound out of the headphones? It's had the problem ever since I got it and returning is not really an option since I bought it in on a trip in the States and I live in Europe. Factory reset doesn't help. I've tried with different headphones.I guess it's most likely a hardware fault I'll have to live with....
Click to expand...
Click to collapse
Well, your options are very limited indeed. If you dare, you could do a device teardown: the headphone-jack can be de-soldered and replaced by the looks of it: http://www.ifixit.com/Teardown/Nexus+7+2nd+Generation+Teardown/16072/. But, that will surely void your warranty + there is a huge risk of permanently damaging your device.
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.
Hi everyone.
I’m experiencing a weird ongoing issue with usb-c earbuds on the Pixel 3XL. Can’t get sound to play out of the right earbud, only the left. However, regular wired 3.5mm jack headphones work fine using the adaptor supplied with the phone.
Contacted Google, went through the usual troubleshooting steps (safe mode, factory reset etc) and no change. (All the latest updates are installed btw). Initially, Google sent me a replacement pair of earbuds. Sadly, these new ones didn’t work either. I’m no tech genius, but it suggested to me that the earbuds themselves are not the problem? In the meantime, I tried a friend’s pair. Same issue. So I contacted Google again....who insisted on sending me YET ANOTHER set of earbuds. Guess what? No sound in the right earbud.
I’ve since taken the phone back to the store I purchased it from. They sent it off to Google for ‘repair’. It arrived back...with exactly the same problem across all 3 sets of Google buds. I’m going to take it back again and ask for yet another replacement (already on my third after various previous issues. Waaaaah).
Before I do I just wonder whether, for the sake of expediency, anyone has any ideas what might be causing the right earbud issue and whether there might be a more straightforward fix that Google are missing?
Thanks in advance
dirtyfoucault said:
Hi everyone.
I’m experiencing a weird ongoing issue with usb-c earbuds on the Pixel 3XL. Can’t get sound to play out of the right earbud, only the left. However, regular wired 3.5mm jack headphones work fine using the adaptor supplied with the phone.
Contacted Google, went through the usual troubleshooting steps (safe mode, factory reset etc) and no change. (All the latest updates are installed btw). Initially, Google sent me a replacement pair of earbuds. Sadly, these new ones didn’t work either. I’m no tech genius, but it suggested to me that the earbuds themselves are not the problem? In the meantime, I tried a friend’s pair. Same issue. So I contacted Google again....who insisted on sending me YET ANOTHER set of earbuds. Guess what? No sound in the right earbud.
I’ve since taken the phone back to the store I purchased it from. They sent it off to Google for ‘repair’. It arrived back...with exactly the same problem across all 3 sets of Google buds. I’m going to take it back again and ask for yet another replacement (already on my third after various previous issues. Waaaaah).
Before I do I just wonder whether, for the sake of expediency, anyone has any ideas what might be causing the right earbud issue and whether there might be a more straightforward fix that Google are missing?
Thanks in advance
Click to expand...
Click to collapse
Does the issue show up immediately after a factory reset? If so, RMA. If not, then likely it is something that you are doing after clean install that is impossible to say what (I can't even think what other than hardware that you appear to already be replacing, so I doubt it is anything you are doing).
Deleted