Related
My Atom thinks the earphones are plugged in when they aren't.
If I answer the phone, no sound, presumably because it thinks the earphones are plugged in and is trying to use those.
Activating the start menu or media player has no sound.
The FM Radio starts (which will only happen if it thinks the earphones are plugged in).
But they are not plugged in.
I am currently on ROM 20060426B1WWE.
The same thing happened on ROM 20060105B1WWE, the first ROM I upgraded to.
I know what you're going to say, that there is a hardware fault, either with the earphone connector or the speakers simply don't work.
Firstly, the speakers do still work. If I start the FM radio and set the little button at bottom left to use the speakers as well, they work.
As for the earphone connector, when I had the problem on the 0105B1 ROM, I could fix the problem by performing a hard reset. Sadly this doesn't fix the problem with the latest ROM, but I'm pretty sure that a hard reset doesn't fully reset the device's configuration.
So I'm pretty sure this is not a hardware issue. I think the OS keeps track of whether the earphones are plugged in, and this has got out of sync somehow.
The last time it happened, I did the following:
While I was playing an mp3 and listening with the earphones, I pulled out the connector and the speakers did not start to play as I think they should have. Now, as I said above, it thinks the earphones are connected all of the time.
Anyone seen anything similar, or have an idea of what I can do? I rang O2 and while they admit it is probably a s/w problem, they want me to send the Atom to them. I don't want to be without it for a week or so because it is my phone and I rely on it. So I thought I'd try here.
Thanks,
invisible earphone...
Hey Peter
I've got the exact same issue once...
But the problem i found for mine was that SOMEHOW when I plug out the headset jack, the slightly retarded Atom thinks I have not..
Just plug in the headset again and pull it out slowly... Then try out the phone if its back to normal...
It seems that the Atom is slow in picking up the disconnected headset...
Hope it works for you as it did for me...
Good Luck
Invisible earphones
Hi bulletproof_78,
Thanks a lot for the reply.
I have just tried it and no luck. I pulled the earphones out very slowly.
I think this is one of the biggest problems with any style of MS Windows. They want to cache everything for the sake of performance, and the cache gets out of sync with the thing it's caching. In this case I bet it tries to keep track of the earphone state internally. But if it misses an event like unplugging them, the internal state is different from the thing it is trying to cache.
Anyway, down off the soapbox.
I'll keep in mind what you said, and try it a few times over the next few days.
I might end up having to send it to O2 (all the way up to @#$%^! Queensland) so they can lose it, or replace it with some questionable one that they haven't fixed properly, or god knows what else.
Anyway, thanks again.
Atom thinks earphones plugged in
For anyone listening out there, the problem has gone away.
I don't really know why.
The only thing I did out of the usual was to turn Bluetooth on. The timing was perfect for me to think that this is what must have fixed the problem.
Do you think that might have fixed it? No I don't either.
And I'm reluctant to try to get it back into that state to see if this fixes it because I'm not that confident that this has fixed it.
I sure hope someone else has this problem and O2 or Microsoft hear about it.
I had the exact same problem you did. I fixed mine by very gently running a paperclip around the inside of the audio jack. Problem Solved!!!
I had the exact same problem you did. I fixed mine by very gently running a paperclip around the inside of the audio jack. Problem Solved!!!
hi guys i faced the same problem last week and i had to get it reparied from the repair shop and they informed me that the jack it not working properly and they will replace it with other jack which is used in sonyerricson cell phones as it is the same. I have got it done and now i have no problem.
Please try this method at the last.
Thanks Novice Boy
i tried the paper clip idea and it worked.
About 5mm inside the earphone jack, on the side closest to the USB port, you can feel a small 'bump' (lets call it the g-spot!) as you run over it with the paper clip. Do this with an MP3 playing or something and voila.....the music comes out of the speaker again and the phone rings, i can talk to people again. Seems there is a fault in recognising whether the earpiece is plugged in or out as many have suggested.
MT
Thanks Novice Boy
i tried the paper clip idea and it worked.
About 5mm inside the earphone jack, on the side closest to the USB port, you can feel a small 'bump' (lets call it the g-spot!) as you run over it with the paper clip. Do this with an MP3 playing or something and voila.....the music comes out of the speaker again and the phone rings, i can talk to people again. Seems there is a fault in recognising whether the earpiece is plugged in or out as many have suggested.
MT
Click to expand...
Click to collapse
Even a tooth pick would do :shock: Have not been using my FM radio but decided to try and got this problem! Was carful not to "short" anything inside so used a toothpick and it worked :lol:
Hi, mine is doing exactly the same thing and did intermittently for a while. Now I cannot get phone audio at all! I have even tried flashing the ROM and still nothing. Works perfectly with portable hands free. Do you think the audio plug is shot? Thanks.
awesome!!!
the paper clip trick really work!!! thanks Novice boy !!
I had this problem too, thanks to you guys and now its fixed.
Worked for me too..
Ok...This toothpic thing really works..
But I cant believe that after paying so much...I am encountering problems like these..
Anyone has any idea if the problem is solved for good or now we need to carry a toothpic too with a stylus...
Even mine problem got resolved automatically. I faced it 2 weeks back.
I tried re inserting the Headphone slowly and removingit and everything came back to normal
hey ive also had this problem...the only thing is that my phone doesnt think it has the headset plugged in because when i open the FM radio it says insert headset...it works when the headset is in and when its on speaker phone but other than that i cannot hear the person...i dropped my phone and this happened....i tried all the methods mentioned but its not fixing the problem...im guessing it could be hardware but the speaker and everything still works except for when your in a call...any ideas?
same prob due to wrong adaptor
i have the same problem. it's like the earphone jack is stuck because the fm radio works even without the earphones. sometimes this registry setting works sometimes it does not let me know if it works for you/anybody...
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\System\State\Hardware]
"Headset"=dword:00000000
even i had this problem in my atom exec a few weeks back sorry i saw this now and for a pemanent solution for it is dont put anything inside just apply very little coconut oil on the handsfree connecter and then connect it to ur phone and keep removing and reinserting it for a couple of times and it will work for sure this happens due to dust or some particles getting stuck between those connectors not allowing the mechanism to work correctly hope it helps beacuse toothpick trick works fine but its temp and reoccur
t.stratus said:
even i had this problem in my atom exec a few weeks back sorry i saw this now and for a pemanent solution for it is dont put anything inside just apply very little coconut oil on the handsfree connecter and then connect it to ur phone and keep removing and reinserting it for a couple of times and it will work for sure this happens due to dust or some particles getting stuck between those connectors not allowing the mechanism to work correctly hope it helps beacuse toothpick trick works fine but its temp and reoccur
Click to expand...
Click to collapse
I have the same problem and was very sad until trying the toothpic trick, even thought If I hit my pocket the problem returns, so I will try your recomendation, thanks!
Is there a hardware repair procedure, so maybe this part can be removed and replaced?
Yes it is a hardware problem. The headphone socket is faulty.
I've a HP 6828 - which is identical to Atom. I had this problem also.
Pls check this thread how to solve it yourself:
http://forum.xda-developers.com/showthread.php?t=421982
same problem goes to me to.. at first i'm quite shocked..there might be something damaged..then i insert a tooth pick (scared if i use paperclip could short the electrical terminal inside..) into the earphone jack.hoping a miracle to happen, then few moments, my atom back to normal..
my gf's 8525 speaker blew. its only a few months old. i was wondering when i call att to get it warrantied will i have a problem since i have the unofficial "official" rom installed. i think if i upgrade to the officially released as of nov. 1st rom that i shouldnt have any problems getting it fixed. i doubt they would check the spl version and what not which is my major concern.
any of you have any experience on this issue or any suggestions on if you should try to downgrade the spl after i upgrade the rom?
what do you mean the speaker is blown? Is it physically blown out
Often the connector comes loose or unplugged and all you have to do is plug it back in, but this requires tools and taking the phone apart. search, there are some "How-to" posts out there.
its blown as in the sound comes out very garbled. similar to when a car speaker is blown
can anyone please help with this?
Hello all!
First, thanks for an awesome forum! It has both helped me tweak my Wizard, and also get help when I have needed it.
Well, I have no choice now but to ask here. Last autumn, my warranty was almost up, and a wierd problem presented itself. The mic and speaker suddenly just stopped working! The sidespeakers still work, I think, because the phone rings when someone calls me. But the caller can't hear me, and I can't hear the caller. And there isn't a hint of sound in it, no static or noise, there simply is nothing.
As there were only a few days before the 2 year warranty was up, I ran to my dealer and turned it in. A few weeks later, the phone returned, working again. But now that I come to think about it, I don't remember if I got a replacement or if they actually repaired it... It looked a little like they handled it rough though, maybe it was another phone... Well, that's not important right now.
The same thing has happened again! Summary:
1. Mic & phonespeaker dead
2. Stereo speakers work under certain conditions
3. Wired headset that came with the phone works, both for calling and media
So it seems like a hardware problem. Please note, although I downgraded the phone to original, official Swedish Qtek 9100 ROM, it has been thoroughly tweaked and upgraded to a number of different WM6 ROMs - but all that has been working beatifully!
Still, what are the odds for the mic&speaker dying twice in a row, on different phones (i think the present one is a replacement)?!?
Question: Does anyone recognize this? Is there a possibility that it is software related, and maybe fixable? I have searched both the web and these forums but haven't really found any information on it.
ANY input would be greatly appreciated!
Additional information:
Qtek 9100 (Swedish), G3 model, WM6 upgrade successful (unlocked)
EDIT: There are no system sounds, which is wierd, because the phone can still ring. I thought the system sounds came from the stereo speakers on the sides of the device?
Hello all!
It is a glorious day to be alive!!! Or to have a fully functional Wizard, at least!
Lol - my topic isn't very old, and i reply to it myself with a solution (?). I Googled after the Wizard service manual, and found it right here on Xda .
In all honesty, i didn't do all that much. I just followed the disassembly instructions of the wizard about half-way through, to the point where you get down to the back of the motherboard. I poked and fiddled enough to locate the mic assembly, only to discover that the mic is soldered to the mainboard of the phone. So, i figured i'd just leave it be, because if the mic is really broken the motherboard needs to be repleaced, or a replacement mic needs to be soldered on there.
After removing A LOT of dust in there (honestly, i think the service center that had my device last time wasn't very careful with anything, even a screw was missing! ), i reassembled it. The flat cable running to the keyboard was also a little skewed, but that may have been me, anyway i corrected it too. Same with the speakers.
Long story short, after successfully reassmbling the phone, i fired it up, called my home phone and voila! I works!
Not much of a fix, as i don't really know what i did exactly, but dust, dirt and some bad connections/soldering may have benn the culprit.
All in all, i'm very pleased with my afternoon here. Thanks for stopping by .
epatnor said:
Hello all!
It is a glorious day to be alive!!! Or to have a fully functional Wizard, at least!
Lol - my topic isn't very old, and i reply to it myself with a solution (?). I Googled after the Wizard service manual, and found it right here on Xda .
In all honesty, i didn't do all that much. I just followed the disassembly instructions of the wizard about half-way through, to the point where you get down to the back of the motherboard. I poked and fiddled enough to locate the mic assembly, only to discover that the mic is soldered to the mainboard of the phone. So, i figured i'd just leave it be, because if the mic is really broken the motherboard needs to be repleaced, or a replacement mic needs to be soldered on there.
After removing A LOT of dust in there (honestly, i think the service center that had my device last time wasn't very careful with anything, even a screw was missing! ), i reassembled it. The flat cable running to the keyboard was also a little skewed, but that may have been me, anyway i corrected it too. Same with the speakers.
Long story short, after successfully reassmbling the phone, i fired it up, called my home phone and voila! I works!
Not much of a fix, as i don't really know what i did exactly, but dust, dirt and some bad connections/soldering may have benn the culprit.
All in all, i'm very pleased with my afternoon here. Thanks for stopping by .
Click to expand...
Click to collapse
hi epatnor,
I think the problem with your phone was a stucked microswitch in the 2,5 mm connector for the headset. I read about it here in the forum. Sometimes the switch stays in the closed position and the phone still thinks the headset is connected. Thats why all the sound is sent to the not connected headset and therefor your phone seems to be not working (unless you connect the headset)...
But removing the dust is for sure not a bad thing...
For the next time: I think there was an easier solution for this problem than disassembling your phone...
regards
huibuh_1
Thanks huibuh_1,
Yes this was probably not the smoothest way of "fixing" it. That said, the stucked microswitch theory would actually fit my problem well - I can see now that the exact problem I was having would arise if such a switch was indeed stuck.
However, I think that the problem would be more intermittent since I actually use that port now and then - especially since it's the only way to talk (besides using a bluetooth headset that is). And since I connect the wired headset now and again the switch is used and moved, I suspect that this would result in the speaker/mic coming online again maybe..? Temporarily at least?
All the same, thanks for replying - this might happen again and with your information I'm better prepared for it!
Hi there!
I have been trying to fix this S4 (M919) which came without a T-Mobile rom (In Australia) and I have ran into audio problems over the past few days. I have attempted to fix it by recovering the modem but that did not help. I read about others fixing their phones with a simple flash but those i9505 firmwares do not work with this device. I flashed the T-Mobile firmware to see if it would work but still no sound (plus its not a T-Mobile SIM but that can be fixed by flashing CM12.1 )
It also says that in download mode it is a M919 but underneath the battery, it's a GT - I9505 (what?) I once fixed this problem a while back with flashing TWRP via odin and that apparently fixed it, for some time.
I have tried flashing: modem_CWM_UVUAMDL, M919UVUFOH3, GSM_Modem_XXUFNA5 (FAIL), Albe95_S6_PORT_V4-5 (Same problem as other roms 'no sound' and BL_I9505XXUHOA7_user_low_ship_MULTI_CERTXX
Roms I tried: CM 12.1, CM 11, Slimrom Lollipop unofficial, Albe95_S6_PORT_V4-5 and some t-mobile based rom.
NOTE: I do not use T-Mobile, however t-mobile packages work but I still have 0 sound from speakers & ear piece. ALSO, before this problem occurred, the name of the device when connected to the pc was GT-I9505 now after flashing 'M919UVUFOH3' it is now SGH-M919.
Right now it is on CM 12.1 nightly build (jfltexx) + open gapps + root and busybox (Still no sound)
Additional Information: I can send messages, download apps and everything but I cannot call nor listen to music (both speaker and earphones) Cm12.1 runs the best for now.
So can someone help me? Whenever I press volume controls, the phone would lockup (only on stock) and on other roms, there is also no sound (earpiece & speakers) also music players tend to crash (Such as AudioFX) . Please help me out!
You have a Frankenphone. In your case, it happens to be a US T-Mobile S4 that has had its IMEI replaced with one from an I9505. The ROM I believe is not the source of the issue here, but that the speaker module has failed, requiring replacement. The part should be on Amazon, and should be very easy to replace. Once you replace the module, install the Google Play Edition ROM from the development section and enjoy. Cyanogenmod should also work, but don't try installing a ROM ported directly from a Galaxy S6, like Albe95's ROM. M919 devices trying to run such a ROM will have no network and no WiFi, with no way to enable it.
Strephon Alkhalikoi said:
You have a Frankenphone. In your case, it happens to be a US T-Mobile S4 that has had its IMEI replaced with one from an I9505. The ROM I believe is not the source of the issue here, but that the speaker module has failed, requiring replacement. The part should be on Amazon, and should be very easy to replace. Once you replace the module, install the Google Play Edition ROM from the development section and enjoy. Cyanogenmod should also work, but don't try installing a ROM ported directly from a Galaxy S6, like Albe95's ROM. M919 devices trying to run such a ROM will have no network and no WiFi, with no way to enable it.
Click to expand...
Click to collapse
Thanks for the reply, also here is the guy I bought it from. I believe your statement makes sense but if the speaker failed, why wouldn't the headphone jack work? I fixed it before with TWRP (weirdly) but here are some links. Is this module what you are referring to or is it the long connector that comes from the top to the bottom?
Link to phone
Speaker Module
You said about: "M919 devices trying to run such a ROM will have no network and no WiFi, with no way to enable it." I believe that is true as I tried that and I got no WIFI at all So you solved some of my worries
Well, now we know why he cannot post to the United States. He's knowingly selling these Frankenphones. The IMEI was likely changed because the original IMEI was blacklisted.
As to the speaker, I only went by the evidence presented. You had tried multiple ROMs, both Touchwiz and otherwise, and none of them resolved the speaker issue. Ergo, the only remaining possibility is that it's a hardware issue. Your fixing the issue in TWRP is odd. The fact you were only able to do it once and weren't able to do it again leads me to believe that TWRP "fixing" the problem was a placebo effect and that there's something else wrong. Now, I believe the speaker module to be the culprit, but do not remember if the audio controller is located on that module.
Where both speaker and headset are not working, you may have a mainboard issue, which will require you to get your money back from the guy you bought this S4 from. Then get yourself an untouched S4 using your XDA account and purchasing through Swappa. With Frankenphones, I ALWAYS recommend getting your money back ASAP, as they often are more trouble than they are worth.
Strephon Alkhalikoi said:
Well, now we know why he cannot post to the United States. He's knowingly selling these Frankenphones. The IMEI was likely changed because the original IMEI was blacklisted.
As to the speaker, I only went by the evidence presented. You had tried multiple ROMs, both Touchwiz and otherwise, and none of them resolved the speaker issue. Ergo, the only remaining possibility is that it's a hardware issue. Your fixing the issue in TWRP is odd. The fact you were only able to do it once and weren't able to do it again leads me to believe that TWRP "fixing" the problem was a placebo effect and that there's something else wrong. Now, I believe the speaker module to be the culprit, but do not remember if the audio controller is located on that module.
Where both speaker and headset are not working, you may have a mainboard issue, which will require you to get your money back from the guy you bought this S4 from. Then get yourself an untouched S4 using your XDA account and purchasing through Swappa. With Frankenphones, I ALWAYS recommend getting your money back ASAP, as they often are more trouble than they are worth.
Click to expand...
Click to collapse
Well, as I said I fixed it with TWRP and I believe (I just confirmed and remembered) I fixed the problem again (about 1 month ago) by flashing CyanogenMod this time. There are links that prove people have fixed their devices with various methods.
Also, if it were to be a hardware problem, why would the audiofx application crash, volume control menus hang on stock firmware and no ear piece sound? It just doesn't make sense! If you have any other solutions please tell me! I really want to fix it but I am starting to believe it is a hardware problem. I really hope it isn't. Also, I confirmed the IMEI number and its a i9505 but in odin mode, it says sgh-m919 :/
Cheers!
just out of curiosity, can you get sound through a pair of headphones???
just because I had a problem of having no sound before, and it turned out that the headphone socket was damaged , in such a way that the phone ALWAYS thought it had a pair of headphones connected, thus no sound from either of the internal speakers.
i had to replace the headphone socket on mine (real easy, it just clicks in place) and since then, no problems.
Gloris said:
just out of curiosity, can you get sound through a pair of headphones???
just because I had a problem of having no sound before, and it turned out that the headphone socket was damaged , in such a way that the phone ALWAYS thought it had a pair of headphones connected, thus no sound from either of the internal speakers.
i had to replace the headphone socket on mine (real easy, it just clicks in place) and since then, no problems.
Click to expand...
Click to collapse
Nope. It isn't headphones or speakers because the software will also crash if I have problems like that. If the software worked fine (no hanging with volume controls or media players) then the speaker/3.5mm jack module would need replacing. I think I got a dodgy factory second handset. Will probably send it back for warranty to the seller.
PS: The S4 ain't mine. It is my sister's. Furthermore, it is an m919, no a i9505 (I checked via the IMEI numbers)
Well congrats on fixing your headphone jack!
TheUnknownThing said:
Nope. It isn't headphones or speakers because the software will also crash if I have problems like that. If the software worked fine (no hanging with volume controls or media players) then the speaker/3.5mm jack module would need replacing. I think I got a dodgy factory second handset. Will probably send it back for warranty to the seller.
PS: The S4 ain't mine. It is my sister's. Furthermore, it is an m919, no a i9505 (I checked via the IMEI numbers)
Well congrats on fixing your headphone jack!
Click to expand...
Click to collapse
(I think) there is no variant in galaxy s4 known as m919,so it might be i9505
Sent from my GT-I9505 using Tapatalk
@yahya wessam: SGH-M919 is a T-Mobile (US) Galaxy S4. He most definitely does NOT have an I9505.
Strephon Alkhalikoi said:
@yahya wessam: SGH-M919 is a T-Mobile (US) Galaxy S4. He most definitely does NOT have an I9505.
Click to expand...
Click to collapse
Oh wait there is, i thought there is only 2 variants:
i9505 and i9500
Sent from my GT-I9505 using Tapatalk
Those are the international models, but there are also a dozen different models just for North America.
Yea. Faulty factory second phone. We will send it back and hopefully they will replace it.
Hello,
When I make a call, in 50% of the time, the person I call cannot hear me. It is very frustrating because... the Axon 7 is a phone.
I am A2017G 100% stock on official 7.1.1 and I made a factory reset after I installed 7.1.1.
I remember some messages about this problem in another thread but I think a specific threat has to be made because the problem was NOT SOLVED in 7.1.1.
How do you people live with this? Did anyone find a solution?
Envoyé de mon ZTE A2017G en utilisant Tapatalk
A2017G and I have this trouble too. My temporary solution is to turn of and of loudspeaker - as for now after that microphone works. I dunno why that issue occured in my phone after upgrading to 7.1.1. I do not have that trouble in 7.0.0 (I'm stock, locked bootloader).
While this may sound stupid and condescending, it's not meant to be. I used to face the same issue when I used the phone. Initially thought that it was a problem with microphone, but it was also a bit weird cos it only happened when the phone was in my right hand. That's when i realized that the microphone is placed at the bottom right corner. When I held the phone in my right hand my little finger would cover the microphone and the person at the other end couldn't hear me. Changed my grip and haven't had any problems anymore.
crazedgod said:
While this may sound stupid and condescending, it's not meant to be. I used to face the same issue when I used the phone. Initially thought that it was a problem with microphone, but it was also a bit weird cos it only happened when the phone was in my right hand. That's when i realized that the microphone is placed at the bottom right corner. When I held the phone in my right hand my little finger would cover the microphone and the person at the other end couldn't hear me. Changed my grip and haven't had any problems anymore.
Click to expand...
Click to collapse
Need to check that - may we just keep covering mic with finger lol
Definitely not a finger! I am on standard 7.1.1 software and people do not hear me. People from Reddit.com have suggested installing Google Dialer and contacts but that unfortunately did not help. Any suggestions for now? Do we have to wait a month for updates?
This issue just happened to me for the first time. 3 attempts to call failed. The person could not hear me. A reboot fixed it.
Hope a solution is found.
I'm on stock, unlocked and not rooted, 7.1.1.
I confirm Little Finger has nothing to do with my problem. It is just a phone that can not make a decent call. Google Dialer did not help neither.
Indeed, a "fix" is to quickly activate loudspeaker then come back to normal... But the person you call already had time to say "Allo? Allo ?" à few times and be upset about it... Not professional AT ALL... I remember I bought... a phone.
Envoyé de mon ZTE A2017G en utilisant Tapatalk
Any one knows if there is a fix for this already?
I do not have that trouble on B2 7.1.1 update anymore.
I have the same problem on the U version of this phone and I have the latest software as of August 2017.
I used to have the same problem. I turned off VoLTE Voice calling and the problem went away.
Sent from my ZTE A2017U using Tapatalk
Hey everyone, hope all is well.
I found a fix for my axon. If you don't want to read my trial and errors and just want the fix, scroll to the bottom. Sounds like you guys have an issue where turning speaker on and off fixes it, so this might not be the fix for your issue, but, I thought it was worth a try since it's basically free.
I bought an axon 7 off eBay. From day 1 people were saying they couldn't hear me very well. I thought it was cell service.
It seemed to slowly got worse.
It got to the point where people couldn't hear me at all.
I downloaded an app to locate cell towers and service range. Service didn't seem too bad...
Found forums like this one, tried talking on speakerphone. It worked, but people said it was still hard to hear me, cutting in and out, etc. Turned off mic access for ok Google and eventually EVERYTHING else.
Deleted apps even... No fix.
Eventually went to a place I knew had good cell service, called someone, and they couldn't hear me at all! Def not mic access, def not service...
Axons warranty doesn't work for resold phones... The speakers and Dolby..I didn't want to go back to a Samsung or whatever..
That's when I started looking for hardware fixes.
I decided to do a Google search one last time before starting down that road, but looked at videos this time.
And I found a fix!!!!!!
youtu.be/KNGMM-H0oxc
So simple. Take a needle to the tiny mic holes. Mine was so clogged, the junk in it actually looked like the hole until the needle disappeared into it like a toothpick into a brownie hah.
Crystal clear on calls now.
So going back to the forums I read before and posting my fix. Hopefully it helps others.
So happy!
Mhcapa55 said:
Hey everyone, hope all is well.
I found a fix for my axon. If you don't want to read my trial and errors and just want the fix, scroll to the bottom. Sounds like you guys have an issue where turning speaker on and off fixes it, so this might not be the fix for your issue, but, I thought it was worth a try since it's basically free.
I bought an axon 7 off eBay. From day 1 people were saying they couldn't hear me very well. I thought it was cell service.
It seemed to slowly got worse.
It got to the point where people couldn't hear me at all.
I downloaded an app to locate cell towers and service range. Service didn't seem too bad...
Found forums like this one, tried talking on speakerphone. It worked, but people said it was still hard to hear me, cutting in and out, etc. Turned off mic access for ok Google and eventually EVERYTHING else.
Deleted apps even... No fix.
Eventually went to a place I knew had good cell service, called someone, and they couldn't hear me at all! Def not mic access, def not service...
Axons warranty doesn't work for resold phones... The speakers and Dolby..I didn't want to go back to a Samsung or whatever..
That's when I started looking for hardware fixes.
I decided to do a Google search one last time before starting down that road, but looked at videos this time.
And I found a fix!!!!!!
youtu.be/KNGMM-H0oxc
So simple. Take a needle to the tiny mic holes. Mine was so clogged, the junk in it actually looked like the hole until the needle disappeared into it like a toothpick into a brownie hah.
Crystal clear on calls now.
So going back to the forums I read before and posting my fix. Hopefully it helps others.
So happy!
Click to expand...
Click to collapse
Don't think its the solution to the muted call bugg. It's in every rom..the only thing that's helping us to go back to stock.
Don' think going back to stock helps either. I'm on Nougat 7.1.2 and it's happened 5 times now in 2 days for me. Nothing fixes it except a reboot. I've only had this phone for 6 days as well brand new.
For those with an older phone or one that does this all the time and reboot doesn't temporarily help, make sure the mic hole is not blocked with pocket lint or something.
fab4272 said:
Don' think going back to stock helps either. I'm on Nougat 7.1.2 and it's happened 5 times now in 2 days for me. Nothing fixes it except a reboot. I've only had this phone for 6 days as well brand new.
Click to expand...
Click to collapse
If u flash slim2 based on stock u don't going to have the bugg.. The muted call bugg is in every custom rom and clearly it's impossible to fix that unfortunately.
So flash the slim rom and u are good to 2 go.
Wasn't this issue fixable by disabling the "okay Google everywhere" feature? I know it's claimed as just a workaround.
TheMagicianThing said:
Wasn't this issue fixable by disabling the "okay Google everywhere" feature? I know it's claimed as just a workaround.
Click to expand...
Click to collapse
Nope, I use LOS with no GAPPS and I experience the bug.