I just bought a auxiliary cord for the phone I am running the latest cyanogen rom 5.0.4.1. I plugged it into the phone and car and started experiencing problems. Everytime I touched the phone the song would change is there a way to fix this or is anyone else experiencing this problem? Its really pissing me off. Could it be Cyanogen the problem? The Cord its self. My phone is defective? Let me know thanks!
*update*
i tried with head phones and shook the phone in numerous positions nothing happened. so i wonder what this problem is
Related
Lately I've been having issues with my phone recognizing headphones. Sometimes when I plug in the headphones, my phone still uses its speakers. A reboot solves this, so its not a big deal, but it is rather inconvenient since rebooting drains the battery quite a bit. Usually, this happens after I unplug my headphones once. When I plug them back in a few hours later, my phone doesn't register the headphones until I reboot.
I tried cleaning out the lint as other forum posts have suggested although I'm certain it's not a hardware problem. I'm not sure if its ROM specific, but if it matters I'm running the latest ICS BCM (3.3U1) from dk_zero-cool. I had this problem once before running CM7, but the problem came and went. I've been having this problem for a week now, which is longer than anytime before.
Any suggestions will be greatly appreciated.
Did you try a different headphone
Sent from my HTC Nexus One
I have the same problem here, only a reboot will fix this problem. Seems that its ROM or driver related
Yes, I did try a few pairs of headphones, along with my car's audio cable. Same problem.
A rom/driver problem may be the issue, but after reflashing the rom after a full wipe, the problems still there.
I had that problem too. Turns out it was PowerAmp. The daemon that checks for headphone plug/unplug to stop/restart playback was screwing it up. I disabled those functions in the PowerAmp prefs and never had the problem again.
That's probably the problem. Doubletwist doesn't have that option though. I guess I'll try switching to poweramp and disabling that. Hopefully it works.
Hello,
I just used my headphone jack for the first time over vacation last week, and I was wondering if anyone else had issue with their headphone jack? I took a pair of working headphones (that I use for my computer) plugged them into the phone (on stock rom) and I only get one ear to work. Could this have been caused by unlocking the bootloader or anything? it's the first time I've had this issue, and it sucks because it makes the phone partially unusable.
Is this something I should contact motorola over? Or maybe there is a firmware fix somewhere? I'm doing a little thinking out loud.. but I want to see if anyone else is having issues?
Haven't experienced that issue. Sounds like a hardware problem.
Sent from my PACMAN MATRIX HD MAXX
HereGoesNothing said:
Hello,
I just used my headphone jack for the first time over vacation last week, and I was wondering if anyone else had issue with their headphone jack? I took a pair of working headphones (that I use for my computer) plugged them into the phone (on stock rom) and I only get one ear to work. Could this have been caused by unlocking the bootloader or anything? it's the first time I've had this issue, and it sucks because it makes the phone partially unusable.
Is this something I should contact motorola over? Or maybe there is a firmware fix somewhere? I'm doing a little thinking out loud.. but I want to see if anyone else is having issues?
Click to expand...
Click to collapse
My Bravo does that sometimes, it was caused from plugging and unplugging too way many times (2-3 times a day for 2 years). I thought had a similar situation with the AHD, but it ended up being a short in my headphones volume slider.
Try blowing dust out like an old NES game, rotating the plug while plugging/unplugging a few times, and try multiple headphones if possible -- it might just not like those particular headphones.
Unlocking the bootloader won't cause an issue like that. Could be either hardware or software failure. To test if this is a software issue, try flashing multiple roms and see if the condition persists. If it does then this is likely a hardware failure. If hardware and unlocked, contact Motorola and tell them it just quit turning on one day say "I went to bed, woke up, and it wasn't working." Do NOT mention kernel, rom, CM, bootloader, root, XDA, Linux, or anythin that makes you sound like you might know something -- trust me there. If they'll accept it for warranty with that excuse fry the board so it can't boot, which we have 2 options for -- super clocked way over volted kernel or splicing a 110v male end directly with the mini usb plug for a phone. If the don't accept it for warranty, you'll have to buy a replacement jack (maybe front housing, never looked up AHD spare parts) and fix it yourself.
Had a similar problem. Use rubbing alcohol and a one of those thin dental brushes.
The alcohol will vaporize (DONT POUR IT IN OBV). It could be an issue with dust collection over one channel connection.
For a control expt try with another pair of earphones to make sure they're not the problem
HereGoesNothing said:
Hello,
I just used my headphone jack for the first time over vacation last week, and I was wondering if anyone else had issue with their headphone jack? I took a pair of working headphones (that I use for my computer) plugged them into the phone (on stock rom) and I only get one ear to work. Could this have been caused by unlocking the bootloader or anything? it's the first time I've had this issue, and it sucks because it makes the phone partially unusable.
Is this something I should contact motorola over? Or maybe there is a firmware fix somewhere? I'm doing a little thinking out loud.. but I want to see if anyone else is having issues?
Click to expand...
Click to collapse
Please check whether your headphone jack is 3.5mm or 3mm plugging 3mm on 3.5mm causes this issue...
Sent from my Atrix HD using xda app-developers app
Hi all
I've had my Note 3 for a while now, rooted w/ Kingo way back. Just recently, every time I plug my phone into an audio source, there's an audible *pop* coming from that source whenever I start playing a song/video. It's kind of like when you turn off an amp or a soundboard and the speaker pops because of the burst of electricity that's going through at the end. Is there a way to fix this? Has anyone else encountered this problem? It's only started happening recently, so I'm kind of confused...
ToastyD said:
Hi all
I've had my Note 3 for a while now, rooted w/ Kingo way back. Just recently, every time I plug my phone into an audio source, there's an audible *pop* coming from that source whenever I start playing a song/video. It's kind of like when you turn off an amp or a soundboard and the speaker pops because of the burst of electricity that's going through at the end. Is there a way to fix this? Has anyone else encountered this problem? It's only started happening recently, so I'm kind of confused...
Click to expand...
Click to collapse
This would happen all the time in my 2013 GMC Sierra. I just turn my head unit off before I plug or unplug it.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Did you ever find a fix for it? Aside from just turning off the console? It's rather annoying to be listening to my playlist when it pops the speakers every time I get a notification or when the song changes.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Anyone find a solution to this problem? I just got my replacement note 3 and it started doing this. Anywhere I plug in AUX it does it. When I use Pandora it pops at the beginning and ending of every single song as well as the beginning and ending of every notification sound. I'm wondering if this a hardware issue and if I should request another device.
Hello everyone! I picked up a Nexus 6 the other day, and I have ran into a very interesting audio problem with it. I like to use it in my car to listen to Spotify. However, for some reason, when I plug in the cable, it does not always detect that the cable is plugged in, and still outputs sound through the phone speakers. I originally thought this was the aux cable I was using, and I replaced it, but it was still happening. I was messing with it a bit more today and it seems that if I plug it in slowly, it will play out of my car just fine. However, if I plug it in normally, it is like it doesn't see the cable at all. This does not happen at all with other systems at all, be it other cars or home audio gear. It also does not happen with my deck and a different phone (I tested it with my old One M8). Currently, I am using SoundAbout to force it to output to the headphone jack before getting in the car, but this is getting to be a bit of a pain to remember to disable it each time I take my phone out. Has anyone else ran into a similar issue? Does anyone have any suggestions?
Okay, for some time now, the last few ROMs i have flashed to my TP, I have no sound coming from the speakers. Headphones and bluetooth headphones/speakers work just fine. What could be the issue here, what can I try to fix this issue? I believe this issue started from ICS and now even Marshmallow. Anyone else having this problem?? Any troubleshooting tips to possibly fix this issue? On the WebOS side, speakers work like a champ, so I'm wondering if it's codec, kernel/ROM related etc??
Update: So after plugging headphones in, leaving them in after a reboot, and taking them in, the sound came back up again...haha smh, weird stuff, but I guess I'll take it haha
I think it was the reboot. My sound often dies if I start or stop a video a few times (VLC, youtube, netflix). Some days once is all it takes.