For some reason the microphone on my Sensation is no longer working
The microphone is incredibly quiet (shouting sounds like a whisper), but there is obviously still some response. Occasionally I get a "popping" noise from the microphone.
I'm trying to work out what could have caused the issue. I'm using Albionman's CyanogenMod 10.1 Jellybean 4.2.2 Rom and no other users have reported a problem with it. The only thing I can think of that might have caused an issue is flashing a new radio and RCdata.img file. I've tried changing the radio and it's not made a difference, but I'm not sure if there's any way of getting rid of the RCdata? Could the radio even make a difference to the microphone?
Does anyone have any other ideas for fixes or ways to find out if this is a software or hardware isse? Any help people can offer would be great! :good:
Quick update and some extra info:
I've tried flashing different ROMs on there and it's made no difference. I get the same whisper level sound in calls, sound recorder and video.
Does the video use the two microphones separately to record sound? If so, if one was broken then I'd still expect the sound to be a lot louder than it is (though obviously not normal volume). The chances of both microphones breaking simultaneously seems kind of slim...
Replaced microphone... still not working
So today my replacement microphone turned up and I set to work replacing it. I plugged it in and powered up the phone to check it was working and I STILL have no microphone :crying:
This leads me to believe that it must be a software problem, so does anyone know what things can affect the microphone? I've tried different ROMs, different radios, taking the SD card out and seemingly everything else
Any ideas?????
Edit: sound is exactly the same with microphone unplugged completely
I flashed the stock RUU yesterday and the microphone came back
I then foolishly decided to try installing a custom ROM and the microphone stopped working. I thought I'd be able to flash the stock RUU again and fix the issue but this time flashing the stock RUU didn't work :crying: I'm wondering if I've got a bad sector on the ROM or something... :crying:
again install stock RUU then
ganeshp said:
again install stock RUU then
Click to expand...
Click to collapse
Yeah, I did... several times. It hasn't worked this time though for some reason.
Related
Hi all, hopefully someone might have seen this issue or at least know a way around it.
Basically over the last few days I have noticed that when I am on a call my internal speaker tends to drop out and I hear nothing. It does it constantly, drops out for a second or 2 every 5 - 10 seconds.
If I put the speakerphone on it doesn't drop out at all, so I am thinking it isn't a radio/reception issue.
I have no idea about bluetooth as I don't use it, but I can tell you the wired headset that comes with the phone is fine also.
This problem occurs regardless of which ROM I have installed as I have tested over a few different ROMs.
Any ideas ?
Cheers.
Sounds like an internal hardware problem. I had that speaker go out on a Blackjack 2 and replacing the speaker fixed the problem.
I was thinking the same thing, but obviously I am hoping it isn't. Too lazy to be dealing with hardware issues and sending it away for repairs etc etc.
I have the same problem. I replaced the speaker, I used the phone for 1 day and after that the problem appeared again. I dont know from where the problem is appearing. Maybe some one from here have any idea.
Where did you get hold of a replacement speaker?
speaker problem
I have the same speaker problem. Seems like it happened after I updated to the newest rom. Anyone else notice this?
Same here
I have the same issue. I sent the phone back for repair but they refused due to the rom change.
their OFFICIAL line was that 'due to changing the software on the phone you have used a rom image that has 'OVER POWERED' the speaker and damaged it'.
if you replace the speaker it will happen again.
what you all need to do is clarify which rom was install when the fault occured. Unfortunatley i can't help with that as i have tried several roms since to try and fix the problem hoping it was software.
hope this helps.
Hello
I have just notiched that when im holding the loudspeaker up to my ear i can hear a clicking noise not very loud I can only hear it when holding it against my ear...
have somebody notiched that ??
I am on Android Revolution HD rom 3.6.2 I have also tried 4.1.3 and it makes the same clicking sound
I am on Radio
Radio_10.58.9035.00U_10.15.9035.02_2
Does this mean anything ??
hope anybody can help.. thanks
maybe the phone rubs against your ear produces those clicking sounds...
jjdoctor said:
maybe the phone rubs against your ear produces those clicking sounds...
Click to expand...
Click to collapse
NO.........
I just started having this same problem. Just rooted my phone and installed Android Revolution HD 6.5.2 XE. I have the Regular Sensation 4G. It worked great for a couple days, now anything that normally plays through the device speaker just makes a very very quiet ticking noise. You have to hold your ear almost to the phone to hear it. Headphones and earpiece work fine. I tried flashing the non XE rom, but got the same issue. I read through 8 pages of searches and didn't find any resolution, just a few other people that had what sounded like the same issue. Has anybody fixed this without replacing the phone?
stampern22 said:
I just started having this same problem. Just rooted my phone and installed Android Revolution HD 6.5.2 XE. I have the Regular Sensation 4G. It worked great for a couple days, now anything that normally plays through the device speaker just makes a very very quiet ticking noise. You have to hold your ear almost to the phone to hear it. Headphones and earpiece work fine. I tried flashing the non XE rom, but got the same issue. I read through 8 pages of searches and didn't find any resolution, just a few other people that had what sounded like the same issue. Has anybody fixed this without replacing the phone?
Click to expand...
Click to collapse
I have JUST got the exact same problem, in-call (front) speaker works, but if I switch to loudspeaker during call it goes silent, save for sticking your ear to the phone in which case you can hear that the rear speaker is making a constant clicking/oscillating type sound, albeit very quiet. This issue I initially presumed to be ROM related, but the issue persists across the board, AOSP, Stock, all ROMs. Thus I have also just ordered a replacememt speaker and will post the results.
I have the exact same problem with mine s4 active
Bouchang said:
I have JUST got the exact same problem, in-call (front) speaker works, but if I switch to loudspeaker during call it goes silent, save for sticking your ear to the phone in which case you can hear that the rear speaker is making a constant clicking/oscillating type sound, albeit very quiet. This issue I initially presumed to be ROM related, but the issue persists across the board, AOSP, Stock, all ROMs. Thus I have also just ordered a replacememt speaker and will post the results.
Click to expand...
Click to collapse
disassemble phone and make sure the speaker is seated correctly, if it's seated correctly then you might have a duff speaker, alternatively try a bog standard rom aka default one, and see if it works
bluefender said:
disassemble phone and make sure the speaker is seated correctly, if it's seated correctly then you might have a duff speaker, alternatively try a bog standard rom aka default one, and see if it works
Click to expand...
Click to collapse
[UPDATE] New speaker arrived, took everything apart, swapped speakers, rebuilt, booted up, pressed the volume up button- 'no sound'! Pressed the volume up button with ear to the loudspeaker and there it is again- quiet clicking sound, best way I can describe it is that it sounds like a mini tazer! Took everything apart again, checked connections over and over (bearing in mind the loudspeaker just has two pins that rest directly on to the circuit board itself- I.e not hard to check), rebuilt, rebooted, same problem! Did a nandroid of my current and flashed a stock ROM,,, SAME PROBLEM!
Either the replacement speaker is also duff, or I am seriously missing something. :banghead:
Sent from my HTC Sensation using xda app-developers app
there are two speakers in the sensation as far as im aware, also have you tried another rom aka viper or revolution etc
Bouchang said:
in-call (front) speaker works, but if I switch to loudspeaker during call it goes silent, save for sticking your ear to the phone in which case you can hear that the REAR speaker is making a constant clicking/oscillating type sound, albeit very quiet. This issue I initially presumed to be ROM related, but the issue persists across the board, AOSP, Stock, ALL ROMs.
Click to expand...
Click to collapse
I'm stumped, love my old Sensation too so I'm relying solely on vibration to no miss calls. As I said, across the board..
I had Sultan's CM11 but had bugs so i reverted back to my nandroid of Albinoman's CM10.3, which is when it happened! Which made me think it was software related, but I've tried all ROM bases since to rule out all variables and it persists. Switching the loudspeaker and still there, checking the motherboard and all other connections and nothing makes a difference. Possibly the new speaker is also a duff?
Sent from my HTC Sensation using xda app-developers app
did you do a full wipe, i would try going back to the basic ruu rom that came with the phone before giving up, although you will lose root, woth a try
as you could root again, have a go
bluefender said:
did you do a full wipe, i would try going back to the basic ruu rom that came with the phone before giving up, although you will lose root, woth a try
as you could root again, have a go
Click to expand...
Click to collapse
I Always do a full wipe when I flash any ROM. I backup all apps and data with Titanium, then enter 4EXT to make a nandroid of current ROM, then do a full wipe- system, cache, Dalvik, before I try a new ROM, time consuming I know but that's probably one of those OCD'esque things I do. And I've taken similar consideration in trying to rule out what this could be. I'll try one more time your suggestion!
Sent from my HTC Sensation using xda app-developers app
Is/has anyone experiencing/ed issues with their AT&T HTC One X's Bluetooth A2DP capability when streaming music and/or playing any types of audio?
Mine is a new phone, and it makes a continuous crackling / jitter noise when audio is being streamed to the car's BT stereo. I have also tried this on my computer's BT headset, and it does the same thing. It sounds like the white noise you get from an old TV when you do not get a signal, only the frequency of that noise is less frequent. Using my LG Optimus S right on the side, I do not get any disruptions in my audio stream, so it doesn't seem like it is an environmental interference problem.
Unfortunately I rooted and flashed my phone to Noctural Dirty ROM before I got a chance to try anything out on the stock ROM, so I am not quite sure if this behavior is limited to the ROM (software issue) or if there is actually something wrong with the phone (hardware issue) that I should go get a replacement.
Searching through the forums I am getting mixed feedbacks (some folks are saying that they are getting replacements, while some say that the issue comes and goes).
Any thoughts on this?
Thanks!
Well, for the heck of it I flashed the stock RUU back and lo' and behold, the problem vanished. Crystal clear sound... How can this happen?
As soon as I root the device and flash to a custom ROM, this problem again resurfaces...
Perhaps I am doing this wrong?
From stock:
1) Unlock bootloader
2) Flash recovery
3) Flash boot.img
4) Wipe system, cache, davlik-cache
5) Install rom
6) Reboot
7) Install streaming app + BT pairing
This seemed to happen on all the ROMs I have tried so far - ViperXL, Noctural, CleanROM, Calkulin...
Maybe I also need to flash the radio or something?
Any ideas?
Thanks.
Does anyone have any ideas on this? I tried it on the latest CM10 and it's still having the same issues... The only thing that worked is stock... very disappointing
Sorry, it sounds like possibly hardware.
I'm on Cleanrom, and stream to my truck and use a old Jawbone for voice, both work well enough.
WR
Sent by WR's O/C'd One-XL on CR-V
I guess no one knew anything about this or has this problem.
Anyhow, I exchanged my device for another one and it seemed to have resolved the issue.
What remains curious was, why did the original phone not have any problems on stock ROMs but problems on almost all other rooted ROMs? Perhaps the Bluetooth stack was different or there was some kind of settings difference between these? Ummm...
I have the same issue with my Rogers One X.
However, it does not go away if I revert to stock with the RUU, though it does become much less intense than with AOSP ROMs.
I spoke with HTC tech support on a couple occasions and after several diagnostic steps they concluded it was a hardware problem and issued an RMA. I made it perfectly clear with them that my device's bootloader had been previously unlocked, which did not seem to be a concern since this was hardware-related.
However, after sending my device to their authorized repair center here in Canada, it was returned to me untouched with the mention "Unlocked phone - Return without repair". At the time of sending it in, the bootloader had been relocked and the device was 100% stock.
I called HTC back again, asking why they'd issue an RMA number after I mentioned upfront that I had unlocked the bootloader if the device would just be sent back to me, and they said that there was nothing they could do. They disagreed with this policy but it was that of their service provider called FutureTel here in Canada...
In short: I don't think this issue can be fixed, it is probably a defective motherboard.
I guess I am lucky that AT&T doesn't have the same policy, at least as not as I know of... heh
HTC One X bluetooth problem
I have the same issue with my One X. Bluetooth audio sets static and garbled when the phone is in my left pocket. Tried resetting phone and a replacement, but same problem. I tried several different new headsets with same results. Definitely hardware problem. ATT device support center gave me an S3 replacement, but I dont care for the interface, so I may just live with it or send it in to HTC for repair. S3 is way better hardware, but the interface kills it for me.
Hi Everyone,
I have a big problem.
I helped a friend of mine to change the stock rom to cm10.1. Before the rom install I needed to open the bootloader. Unfortunately given the circuit board was changed previously in the phone the official HTC unlock did not work so I needed to perform the wiretrick unlock. The whole unlock process took a few hours with numerous trial and error but at the end it was okay and was able to install cm10.1 in a few minutes.
The rom performs much faster than the stock but there was a downside. When he makes outgoing calls in every 1 from 3 there is a cracking noise instead of the normal dial out tone and also when the call is answered the noise is still there so nor he, nor the other end could hear anything.
I updated the rom to cm10.2 with proper factory reset but nothing changed…
Have anyone experienced something like this? Could this be caused by a short circuit due to the wire trick? Is there any fix for this?
I searched the forum and googled other sites as well but I was not able to find the same issue.
Thanks
mad
Radio?
Can the issue be caused by old radio version? The current version is 11.24A.3504.31_M which is not the latest. However given the wrong file could brick the phone I would not temper with it unless absolutely necessary. Thx.
[Q] In-call mic & speaker dead on stock device, can only make calls with Bluetooth
Anyone else encountered this problem? It's NOT a volume issue, it's an 'in-call speaker and mic not working at all' issue. About two months ago my phone calls completely cut out all in-call sound, UNLESS I use a Bluetooth headset, in which case I can talk and hear just fine. When it first went out, I was able to use the mic and in-call speaker as long as I put it in speakerphone mode, but after a few weeks, that cut out, too. It will answer the call...I just can't communicate without BT engaged. Factory reset and other known "try this first" solutions have been dead-ends.
The OTA to KitKat didn't change or help anything in regard to this problem, and the same problem persists in the same fashion. I am currently still stock...after modding my M7 on TMO repeatedly, when I switched to Verizon and got an M8, I resolved to stick with stock and try to appreciate getting the OTAs before the other carriers. All well and good--until your in-call sounds bugs out and renders your device useless as a phone unless you put your BT earpiece in first.
I'm curious if this is a widely known problem, as I couldn't find evidence of it being common, but wasn't sure if I was just looking in the wrong place or using the wrong search terms. If so, is there a decent fix, or did VZ just sell me a lemon? If there's not a decent solution, would Factory Reset, unlock, and flashing TWRP and a good aftermarket ROM, say CM, cause this problem to be fixed?
Just figured I'd ask the hive before I dig into it myself and end up pissing away the rest of my weekend on it. Cheers and thanks!