Annoying problem..Headphones cause random calling :S - Touch Pro, Fuze General

Hey,
i just came across an annoying problem..It happened out of nothing
when my headphones are plugged in, my TP starts calling the latest contact or activating the voice speech (long press on Yes)
This ONLY happens with the headphones plugged in. It never used to do that and now suddenly it does (haven't installed or modified anything between the time that it happened)
what could be causing this?
i can think of the button getting stuck (although it doesnt feel or look stuck)..
any thoughts or ideas are welcome

Giannis86 said:
Hey,
i just came across an annoying problem..It happened out of nothing
when my headphones are plugged in, my TP starts calling the latest contact or activating the voice speech (long press on Yes)
This ONLY happens with the headphones plugged in. It never used to do that and now suddenly it does (haven't installed or modified anything between the time that it happened)
what could be causing this?
i can think of the button getting stuck (although it doesnt feel or look stuck)..
any thoughts or ideas are welcome
Click to expand...
Click to collapse
I've the same problem but with my Diamond.
I realized that's a problem of the cable, because it's broken inside and crosses the signal between the headphone & calling order. It normally happens when you move the cable or turn it in an specific section of it....et voilà! You make a call!
or maybe it's me that i'm turning crazy
But I'm annoyed too

I also had this problem and a new set of head phones resolved it

Related

No Sound After Using Headphone Adapter

I use the HTC adapter with my ATT Fuze to listen to music in my car. When I unplug the adapter to get out of the car, my speakerphone no longer works. If I get a call, it will vibrate but not ring. If I adjust the volume, I don't hear the indication beeps. However, if I make or receive a call, I can hear them through the regular speaker, and they can hear me.
I've tried adjusting the volume everywhere possible, adjusting the audio profile, changing the ringtone, etc, but the only way to fix it is to soft reset. Needless to say, it is very inconvenient to have to reset my phone each time I get out of my car.
I did search the forums but couldn't find any solution. Unlike these people:
http://forum.xda-developers.com/showthread.php?t=526930&highlight=sound+headphones+aux
http://forum.xda-developers.com/showthread.php?t=508225&highlight=sound+headphones+aux
my phone does not show the headphone icon indicating that it still thinks the headphones are plugged in. It also will not allow me to use the TouchFlo Audio Booster, further evidencing the fact that it knows the headphones aren't plugged in.
I had to replace my phone for a different reason, so I have verified this problem on two separate physical units. On both I tried cleaning out the USB jack and wiggling the connection around as suggested elsewhere on the forum, but neither solved the problem. In the process of getting my old phone ready to send back to ATT I restored my stock SPL and ROM and verified that the problem still existed. Other than the stock stuff, I have experienced this issue on EnergyROM 2.0 41609 and 41709, EnergyROM 3.0 'Magic' 20090709, and EnergyROM 3.0 'Mercury' 20090722.
As suggested here:
http://forum.xda-developers.com/showthread.php?t=526930&highlight=sound+headphones+aux
I thought my Bluetooth stack may be causing the issue, so I flashed a new radio as well. I was originally using 1.14.25.35, and am now on 1.14.25.05, which NRGZ28 says is the best for his Mercury ROM. Still didn't fix it. I'm at a loss for what to do, and wonder if anybody else has come across a solution, or has any idea what the problem could be.
Any thoughts or suggestions would be greatly appreciated.
Inferno
im having same problem dude. Have you tried going to your audio recorder and recording yourself and then making a call. That helped get mine back the way its suppossed to be.
That worked. Very interesting... Does anybody have any idea why this might be the case? Is there a registry value somewhere that needs to be reset after I use the adapter?
NRG has a couple of little apps he includes with his ROMs, namely "Finger Menus OFF/ON" and "Notification Manager OFF/ON" that I assume just wrap up a registry value switch. Would it be possible to code the registry values I need into an app like this, so I can click a button and have my sound working again after I use the adapter? Any senior members willing to do this for me or guide me through the process?
And thanks for the tip Mr. Ewok.
Inferno
bump
The voice recorder trick doesn't work for me anymore for some reason. Anybody else have any suggestions?
Thanks,
Inferno
Hardware
hey,
I had exactly the same problem with my Fuze. I've never flashed anything but the stock rom. I sent it to PPC techs because I had them repair another problem. They told me it didn't have anything to do with the speaker or cables, but they "heated up the board" and it started working. I'm wondering if there's a manufacturing flaw (like a cold solder) involved.
BTW PPC techs didn't charge me anything but shipping to repair it (as it was under their warranty, even though it wasn't their fault). Nice guys!

[Q] sudden pop then no audio

hi all,
i've posted in another thread about this issue but i feel it may be slightly different. i get this issue on every rom i've tried, in which there will be a pop sound then audio will cut out, but come back on its own after between a few minutes or an hour (give or take). a restart of the device fixes it instantly also. this happens using headphones and earpiece/speaker, depending on what i'm doing (music, games, calls respectively). i suspect it's a hardware issue considering it happens seemingly randomly (after about 30 seconds to a minute of plants vs zombies 2, anywhere between 5 seconds and 20 minutes using headphones, but only once during a phone call).
any ideas? or is my device buggered?
cheers.
so after faffing around trying out different scenarios, i've come to the conclusion that it's either having wifi/3g/both enabled that seems to cause these audio drop outs. went for a walk earlier with headphones in but still had wifi/3g enabled, audio dropped out, so unplugged headphones, disabled wifi and 3g then plugged heads back in; no audio drop out for the entirety of my journey (about 45 mins).
any ideas??
twist3d0n3 said:
so after faffing around trying out different scenarios, i've come to the conclusion that it's either having wifi/3g/both enabled that seems to cause these audio drop outs. went for a walk earlier with headphones in but still had wifi/3g enabled, audio dropped out, so unplugged headphones, disabled wifi and 3g then plugged heads back in; no audio drop out for the entirety of my journey (about 45 mins).
any ideas??
Click to expand...
Click to collapse
I have had similar issues. It happens when I use a non stock kernel. If I use stock, or elementalx with vanilla voltages and no over clocking, I don't get the audio drop outs. Do you use the stock kernel?
I did find the problem was less severe when running magio rom, but it was still present. Over the past few months I've been using aosp roms mainly and didn't have an issue until maybe 3 weeks into using odyssey 3.21, that's when I switched to magio. As the problem lessened, I switched to odyssey rc (most recent) and it's back to being bad. As I mentioned, if I disable wifi / 3g I can listen to music no problem, but if I'm on a bus I want to be able to use data as well as music!
I'm going to run an ruu and reflash, see if that sorts it
Just in case anyone else gets this issue, i have a work around (at least i haven't experienced any dropouts whatsoever with audio since doing this).
disable wifi & 3g before plugging headphones in
plug in headphones
turn back on which ever you're going to need (or both)
no dropouts
Sound Drop Easy Fix!!
I believe I have discovered a fix for the problem we are having with the audio. I used your headphone fix and it worked beautifully but I decided that I didn't want to carry around my headphones every where I went. I then discovered the SoundAbout app in the play store. I downloaded the app and used the widget from the app for the easiest fix. I put the SoundAbout widget on my home screen and when I needed WiFi or Data I simply toggled the SoundAbout widget on, waited about 10-15 secs and enabled WiFi, waited and then I toggled the SoundAbout widget off. Once I was done with WiFi or data I toggled the SoundAbout widget back on, waited, disabled WiFi, waited and then toggled the widget off again. Doing this prevented the sound drops and I have been using my phone normally ever since.
I found that the sound would go out if you were on WiFi and you received a call so in the SoundAbout application I changed "SoundAbout Service" to ON - Foreground and "Phone call audio" to Wired Headphones and that seems to solve that issue. If you have any other issues or work arounds let me know.
i'm not getting any issues with calls now since i've started using this practice. as long as when i'm out i disable wifi i don't get any issues. the main problem for me was that i always listen to music when on a journey, but now as long as i disable wifi then start music, then put wifi on again it's fine. phone calls don't get glitched when i do this (even after stopping music playing and receiving a phone call).
hopefully at least others will find this thread useful
Hopefully so! I decided to go back to stock now audio is working 100%... I'm content for now at least
derrioned said:
Hopefully so! I decided to go back to stock now audio is working 100%... I'm content for now at least
Click to expand...
Click to collapse
aye, gonna do the same this weekend then re-root. been putting it off for weeks now lol

Car bluetooth problem with official CM13.0 (and CM12.1)

I was hoping that CM13.0 would solve my Bluetooth problem but did not.
Although most of the time is working with a factory Bluetooth system (in a MB car) every now and then it disconnects.
Disconnection usually happens when there is an incoming call - before I press the accept call button, phone disconnects and reconnects a second or so latter.
I had this problem with CM12.1 and I was hoping CM13 would fix it - only in CM12.0 it was working fine.
Rare times it disconnects while idle – or it happens often and it goes unnoticed.
Is there any solution I missed?
Things like complete factory reset / clearing cash etc are done with no change in the results.
Car has no update (it’s an Alpine NTG2.5 system).
papars said:
I was hoping that CM13.0 would solve my Bluetooth problem but did not.
Although most of the time is working with a factory Bluetooth system (in a MB car) every now and then it disconnects.
Disconnection usually happens when there is an incoming call - before I press the accept call button, phone disconnects and reconnects a second or so latter.
I had this problem with CM12.1 and I was hoping CM13 would fix it - only in CM12.0 it was working fine.
Rare times it disconnects while idle – or it happens often and it goes unnoticed.
Is there any solution I missed?
Things like complete factory reset / clearing cash etc are done with no change in the results.
Car has no update (it’s an Alpine NTG2.5 system).
Click to expand...
Click to collapse
Sadly, this is a wide problem with a lot of Android phones.
One of the fixes Ive read around is to not give so many permissions when pairing a Android device. Example I read: Someone's device would never connect if they shared contacts with their car. You can share contacts and have the hands free not working or not share any contacts and have handsfree working. Its a trade off.
So far CM13 seems little better.
What I can't figure out is the pattern, if there is one. Why sometime it works and sometimes is not. When I initiate the call from the phone or the car keypad, 99% it will work without a problem.
When I receive a call, its a hit or miss. Sometimes it works, sometimes it doesn't. The only reason the phone is not landed out of the window is the fact that reconnection is quick, so I get to answer the call from BT no matter what. But is frustrating.
I remember my first phone with this car was a (non smartphone) nokia. In that case from BT I could hear the selected phone ringtone and the phone did not ring at all.
With any smartphone from then on, both the phone rings (with its own ringtone) and the BT rings with a generic tone. Oh well ...
BTW I had zero problem with BT when I first bought OPO - but then it had CM12.0 I think.

Google Pixel No Sound issue

Guys, this issue has been pestering for a month now and I seem to have not found a fix for this yet. I first started to notice the problem with my phone when I was unable to attend the calls, the screen will usually get stuck or i will not be able to swipe up the green button during the call. Even if sometimes I manage to i will be able to hear the other person speak but I wont be able to speak to them. So sometimes once I restart the phone it will seem to work fine for an indefinite period of time and again it starts.
Then things started getting very bad, sometimes during normal device usage, the screen just turns to a monochrome black and white screen ( just as you see when there was no signal on older television sets). And when I switch to the bootloader screen, when I power the device on, I get a very thin green line for an instant on the screen and then the booting sequence starts.
I have made a lot of factory resets and stock image flashing, and by far I noticed one considerably situation, the times when the sound functions fine, the booting sequence where the 4 google dots animation appears and when there is no sound, the booting sequence gets stuck on Google and made by Google screen.
Other observations are during abnormal device behavior, no function related to sound will properly. To elaborate it, Google assistant wont work, videos cannot be played and even the system sounds wont be heard. I am open to suggestions here. Please let me know what can be done to test the phone out. FYI I know there is a problem with the Pixel microphone, but I am not convinced that its the exact problem. Please correct me if I am wrong. Thank you.
Sounds like a hardware defect. RMA if possible.
Sent from my Pixel using XDA Labs
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
That's the only way I suppose!...did you get the phone directly from the Google store?...are they accepting phones bought from a retailer?...since I am in Singapore now...Google support is next to nothing here...try contacting them but it's of no use...only when I get to India I will be able to go forward with the replacement!.....but the thing is .... yesterday...I updated the phone to Oreo and the audio stopped working completely....and after repeated switching between safe and normal mode....the speakers are working now...but the microphone is still busted.
This happened to me, I was given a replacement phone from EE UK
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
MK1207 said:
Current update guys...as per the pixel support centre person's suggestion ...I rebooted the device to safe mode to check if the phone is operating normally ...which it did not....but surprisingly ...after restarting to normal mode ...it started working normally again...my query is how is this zeroed down to an hardware issue if in case it's perfectly working for a while and at some point goes bonkers...can you guys please enlighten me on this...coz I don't have much knowledge on the hardware field.
Click to expand...
Click to collapse
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
ndiri said:
hello, i am facing the same things as you do since updating to oreo, my question is how do i test everything in safe mode, to see if everything is alright as you did
Click to expand...
Click to collapse
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
MK1207 said:
Tough luck mate! Sorry to hear that....you can check it out by pressing down the power button until you get the power off and restart menu. Keeping pressing down on the power off menu...it will reboot to safe mode without your prompt. In safe mode for me it was the same....maybe you will have a better luck...try it out!
Click to expand...
Click to collapse
well, its been almost an hour the phone wont turn sound back on.
Keep switching it to and out of safe mode...at some point ideally at least the speakers must start lest the microphone. Tried contacting Google about it and no response at all...mine started acting weird only for the past month...I suppose from the Aug months patch update....tried reverting it back to previous stock versions...but I suppose the damage is permanently done
When I contacted google, they told me to send it back to Canada and let someone there give it to google.. which won't happen in my case , my phone also started acting like this after Oreo beta . Now I will restart the phone whenever it happens to get it back working :/
The only reason I am still sticking to this phone is coz of it's camera. Planning to get back to India around December to get this fixed. Support for pixel in Singapore now is next to nothing since it wasn't launched here. I had no problem at all with the Nexus line up but this is kind of a disappointment.
Alaadragonfire said:
It is a hardware issue indeed, I am facing the same issue, I contacted google , they told that replacement is possible tho I'm out of Canada at the moment so I'm just dealing with it through my Bluetooth earphones, everybody works fine with Bluetooth.
Click to expand...
Click to collapse
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
MK1207 said:
You've mentioned it as through Bluetooth it works fine....care to elaborate on this?...are you able to input voice commands to Google assistant and speak over calls using it ?...since I am planning to buy one in case its a perfect workaround
Click to expand...
Click to collapse
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Alaadragonfire said:
Yea, Bluetooth works fine for calls, as for google assistant voice command you can enable that from google app settings. Of course other media will be working with Bluetooth as music, YouTube, etc..
Click to expand...
Click to collapse
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
MK1207 said:
Excellent!...thanks for the input....let me check and get myself one and I will have to manage with it till December....and are you able to connect to a laptop thru Bluetooth...coz I am unable to do so...it just says paired...but the bt symbol in the phone doesn't change to connected..did you try that out ?
Click to expand...
Click to collapse
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Alaadragonfire said:
Hmmm I don't remember connecting to a laptop via Bluetooth.. you mean for file transfer ? Anyway Bluetooth has nothing to do with the sound issue we are facing, it might be your laptop Bluetooth driver needs to be updated
Click to expand...
Click to collapse
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
MK1207 said:
Just bought a Bluetooth headset....works fine for the most part...but sometimes during calls...the phone just hangs and it automatically restarts....sigh! pixel just can't be trusted to be my daily driver?
Click to expand...
Click to collapse
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Alaadragonfire said:
Sorry to hear so, I actually installed ElementalX kernel and it is less to happen. Try to flash the kernel.
Click to expand...
Click to collapse
Planning to do just that....I may have better luck with a custom kernel...will post an update once I have flashed it.
I had been on the 8.0 beta for a while. Then got 8.0.
Though just 2 days ago, my mic was starting to have issues. Then yesterday, only my speaker phone would work.
Now I can't get any audio/mic except though Bluetooth (I've got a portable speaker with a mic, and Bluetooth on my car.
Contacted Google support. Will be getting a replacement on their warranty.
They didn't tell me this, but I did some searching, and apparently many of the pixels (mostly from the first 3 months of production) had an issue with the soldering of the audio codec. though usage, little bumps here and there, that soldering can get loose. Which explains why my audio and mic were spotty, and within an hour yesterday morning, all aspects of it stopped working.
So, it's a hardware issue.

A lot of small but terribly annoying errors!

Hello! I think it's worth telling everything from the beginning. In the middle of summer, I discovered that my front camera refused to work. At that time, I did not pay attention to it, because I almost do not use it at all. Then, in October, there was a problem with the sound on the phone, it disappeared and did not work without headphones. Before the sound was lost, there were some problems and the sound partially disappeared, but it was solved by rebooting. After the loss of sound without headphones, it came to the loss of sound with Bluetooth headphones connected. With headphones connected, audio and video (in other things, everything where there is sound) stopped playing, I checked, and the problem was not in them at all. Next on the list. On December 20-27, the phone stopped seeing the second SIM card! I decided to pull it out and put it back in, and the problem was fixed for a while, then it stopped being solved with this method. And this morning my camera and flashlight stopped working at all. I'm terribly upset. I decided to check what was wrong with the camera using the CIT, and it said "cameralist don't match". I'm wondering what ways it's possible to eliminate all this ****, and if it's possible at all. and which is easier, to solve these errors or buy a new phone?
mort! said:
Hello! I think it's worth telling everything from the beginning. In the middle of summer, I discovered that my front camera refused to work. At that time, I did not pay attention to it, because I almost do not use it at all. Then, in October, there was a problem with the sound on the phone, it disappeared and did not work without headphones. Before the sound was lost, there were some problems and the sound partially disappeared, but it was solved by rebooting. After the loss of sound without headphones, it came to the loss of sound with Bluetooth headphones connected. With headphones connected, audio and video (in other things, everything where there is sound) stopped playing, I checked, and the problem was not in them at all. Next on the list. On December 20-27, the phone stopped seeing the second SIM card! I decided to pull it out and put it back in, and the problem was fixed for a while, then it stopped being solved with this method. And this morning my camera and flashlight stopped working at all. I'm terribly upset. I decided to check what was wrong with the camera using the CIT, and it said "cameralist don't match". I'm wondering what ways it's possible to eliminate all this ****, and if it's possible at all. and which is easier, to solve these errors or buy a new phone?
Click to expand...
Click to collapse
Which ROM are you using

Categories

Resources