Today I downloaded a dB meter app from Play Store, and I wondered why it didn't work, then I found out that it wasn't the app's problem but the phone's.
I tried other apps from Play Store that use the mics including Recforge, Sound Recorder, etc but still no sound signal coming from the mics, and yes, calling doesn't work. (Using headphone/earphone with plug-in jack works.)
An interesting finding is that when I tested with Shazam, after I pressed the turning Shazam logo, it almost immediately told me that no song was found, it was like whenever the app detects dead silence in the first 1 sec, it just gave up listening any longer.
I was using BlissPop so I switched back to stock-based SuperZen, suspecting it is ROM related problem but still no luck, still dead silence
Then I even switched to Latest WW Official Stock, but when I get into the test menu via the calculator app and performed the two mic tests, both of them failed. (I'm sure that it is not the speaker's problem)
So, I wonder if I can safely say that the phone's microphones are hardware dead now, if it is true maybe I will be sending the phone to repairment later next week. Or is it possible that it is some deep level software problem that I'm not aware of?
I have doubt because all other components are working except the two mics, and I think it is pretty abnormal for two components at two different side(top and bottom) of the phone to hardware malfunction at the same time. (Also because of the Shazam app's behaviour)
Thank you.
(English is not my first language so please forgive me if I sound rude or awkward )
Hi, have you resolved the issue?
Hi comcraizer,
did you find a solution to this?
Thanks.
comcraizer said:
Today I downloaded a dB meter app from Play Store, and I wondered why it didn't work, then I found out that it wasn't the app's problem but the phone's.
I tried other apps from Play Store that use the mics including Recforge, Sound Recorder, etc but still no sound signal coming from the mics, and yes, calling doesn't work. (Using headphone/earphone with plug-in jack works.)
An interesting finding is that when I tested with Shazam, after I pressed the turning Shazam logo, it almost immediately told me that no song was found, it was like whenever the app detects dead silence in the first 1 sec, it just gave up listening any longer.
I was using BlissPop so I switched back to stock-based SuperZen, suspecting it is ROM related problem but still no luck, still dead silence
Then I even switched to Latest WW Official Stock, but when I get into the test menu via the calculator app and performed the two mic tests, both of them failed. (I'm sure that it is not the speaker's problem)
So, I wonder if I can safely say that the phone's microphones are hardware dead now, if it is true maybe I will be sending the phone to repairment later next week. Or is it possible that it is some deep level software problem that I'm not aware of?
I have doubt because all other components are working except the two mics, and I think it is pretty abnormal for two components at two different side(top and bottom) of the phone to hardware malfunction at the same time. (Also because of the Shazam app's behaviour)
Thank you.
(English is not my first language so please forgive me if I sound rude or awkward )
Click to expand...
Click to collapse
I also have a problem with mic in Skype only when using speaker phone, regular phone works fine with speaker phone. This happens only with the mm bootloader on every ROM, worked fine on lp bootloader with any ROM. Anybody else have this issue?
Related
I was using GPS navigation on google nav and playing music through the HTC media player and GPS signal wouldnt stick if i was moving, only if i was standing still. Something is preventing this multitasking. I need someone to test if it is just me or my ROM or these specific apps. I am running fresh .2 ROM btw.
UPDATE
GPS breaks when playing music through the external speaker. The signal will be lost, or really spotty until you stop playing music. HTC has not commented on the issue. Does anyone know why this is happening? Is it possible to fix?
yep i am using stock unrooted evo and i get same problem i was playinf music thru stock player and go to google nav and it wont find gps signal after pausing music it finds signal them i turn the music bak on and it looses signal
Haven't tried the stock music player, but I listen t
o podcast all the time while using the gps.
i think its a bug in the htc stock player i tried same thing with doubletwist player and get no issues
edit
i got lost signal on gps also with doubletwist now seems like a bug with google nav
Could you post your ROMs if rooted and also has anyone tried Sprint Nav? I will go and grab a sprint nav apk and test when I get a chance. This is very inconvenient and I am curious as to why it isnt working.
Uhhh, no problems here, playing mp3 from SD card using stock music player and got a GPS lock in a matter of seconds.
Latest radio
fresh .2
-Edit- Mine works sometimes but mostly doesn't, so yeah bug is present
anyone hear anything from htc about this, posted on their site and twitter and didnt hear anything, maybe i should call about this issue.
I don't use the stock music player app for anything but I experience this exact issue when trying to use pandora and the GPS. As soon as i shut pandora off it picks up signal again.
NEW FIND, any app, GPS and MUSIC through the speaker causes GPS signal to be lost. It works while using headphones but not the speaker.
Wow, is this a hardware or software issue?
You know, I actually forgot about this for a while, there has been no official word on this bug, and I havent heard anyone knowing why this happens.
I never even thought to try running my gps without music, I just thought it had a very crappy gps antenna or something. I have yet to try it without music to verify this as well, but tomorrow I probably will test it out.
Just a wild stab at the dark, but maybe the magnet in the external speaker interferes with the GPS antennae? Not too sure about that though....
Hmmm, would be interesting if the placement of the speaker and the GPS is the actual problem, I really hope not though. The problem doesn't occur when the GPS app uses the speaker or you get a notification playing on the speaker though, maybe the duration is short enough to not loose the signal? I emailed HTC about this issue, didn't have time to call them about it.
I can verify this, did a two hour trip last night and didn't lose the signal once with the music not playing.
Yes, it's because of the speakers
This is a funny problem. Something about the speakers is interfering with the GPS reception. It's not just that the speakers are on, but how loud it is. The louder the sound, the worse the reception.
I'm running the stock ROM. I used GPS Status and the stock music player. I played a song that is fairly constant in loudness, and noticed that as I turned up the volume, I would start loosing GPS satellites, and then as I turned the down the volume, I would get more GPS satellites.
Update: I tried the same test out on my Hero, and it definitely doesn't have the problem.
Ha, HTC already knows about it. And it doesn't look like they're gonna do anything about it, and this guys reply probably explains why my car charger takes forever to charge my phone.
Dear "My Name",
I understand that the GPS Signal will be lost is you use your device GPS with Music playing. As the device pulls more resources from the battery, the phone may become warm. The device has a built in sensor that registers the amount of heat the phone is generating and will shut down some features as the device heats up. Normally the Charging port will be turned off first, then the various radios will be disabled such as GPS, Wi-Fi and Bluetooth. If you are experiencing an issue while using multiple features of the device at the same time, I recommend that you stop using one or more of the programs and see if the problem persists (As you have). I do apologize for any inconvenience that you may have experienced.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number "My Ticket Number".
Sincerely,
Jeffery
HTC
Click to expand...
Click to collapse
Emrys_90 said:
Ha, HTC already knows about it. And it doesn't look like they're gonna do anything about it, and this guys reply probably explains why my car charger takes forever to charge my phone.
Click to expand...
Click to collapse
If that's indeed the case, one can try underclocking to prevent the heat buildup.
acrh2 said:
If that's indeed the case, one can try underclocking to prevent the heat buildup.
Click to expand...
Click to collapse
Nope, HTC is just throwing something silly. What they describe may be true, but playing music doesn't instantly generate heat, nor does that heat instantly disipate once you turn down the volume, or plug in a headset.
As I tested above, you can slowly degrade your reception by turning the volume up slowly. This is clearly a different issue, and it is a reasonable inference that there is some sort of interference between the speaker and GPS.
Also, if HTC insists, you can prove them wrong by keeping the phone plugged in and showing that it is still charging the battery even when the GPS looses signal.
I experienced a series of reboots on my phone this weekend while driving and using the phone via a bluetooth headset. Simultaneously I was attempting to use Google navigation. I typically could connect to my caller and then would reboot within 10 seconds or so. This happened three times before I was able to figure out that the GPS connection was a culprit and temporally disabled GPS while using the phone.
Lamest part and this isn't the first time this has occurred! On the original firmware shipped from HTC I had a few identical crashes that I have only now realized were because of this combination of GPS+bluetooth.
Right now I'm running a simple OTA update + root using toast's method.
I've this problem when using headphones, where there is this click when audio is started or stopped on the One X, like when using the music player or watching videos. This problem does not extend to the phone's in-built speaker, so when say, starting and stopping music while on the phone's external speaker, there is no clicking noise.
What I've ascertained at least is that this is not affected by any existing apps which modifies sound (since I did a factory reset and tried the audio again, after reading one of the threads on XDA).
But two new things have occured recently, which are
1) I unlocked (and then re-locked) the bootloader (I actually wanted to install a third-party ROM but I had to put that on hold because I didn't have time).
2) My phone just acquired a OTA update from HTC (software no: 2.17.707.3)
Unfortunately as I got this OTA just about a day before I unlocked the bootloader, I cannot determine whether this problem started after the OTA, or after the bootloader was unlocked (there was a factory reset forced by the phone), or if this clicking sound has even anything to do with it. But it definitely didn't occur either before the OTA or the bootloader unlock.
Does turning off the Beats Audio "enhancement" affect it?
BenPope said:
Does turning off the Beats Audio "enhancement" affect it?
Click to expand...
Click to collapse
Hi,
Do you mean just turning off or disabling beats? If it's just turning off beats then no, it doesn't resolve the problem.
Oh and one more thing is that if it helps, when stopping audio, there's this very faint static (the white noise sound) which can be heard for approximately 2 seconds before the static terminates with the clicking sound.
Have you used any volume boosting apps?
I used volume+ free and if I boost the bass setting and/or the virtual room it does exactly what you are describing.
Rob
adognoW said:
I've this problem when using headphones, where there is this click when audio is started or stopped on the One X, like when using the music player or watching videos. This problem does not extend to the phone's in-built speaker, so when say, starting and stopping music while on the phone's external speaker, there is no clicking noise.
What I've ascertained at least is that this is not affected by any existing apps which modifies sound (since I did a factory reset and tried the audio again, after reading one of the threads on XDA).
But two new things have occured recently, which are
1) I unlocked (and then re-locked) the bootloader (I actually wanted to install a third-party ROM but I had to put that on hold because I didn't have time).
2) My phone just acquired a OTA update from HTC (software no: 2.17.707.3)
Unfortunately as I got this OTA just about a day before I unlocked the bootloader, I cannot determine whether this problem started after the OTA, or after the bootloader was unlocked (there was a factory reset forced by the phone), or if this clicking sound has even anything to do with it. But it definitely didn't occur either before the OTA or the bootloader unlock.
Click to expand...
Click to collapse
PurpleRob said:
Have you used any volume boosting apps?
I used volume+ free and if I boost the bass setting and/or the virtual room it does exactly what you are describing.
Rob
Click to expand...
Click to collapse
I doubt that It's an app because I did a factory reset and then the clicking noise is still there when I start/stop audio (before installing any apps, of course).
Anyway I have a theory that It's caused by beats, because say, when using the phone speaker to play any audio, beats is not activated and there is no clicking noise. I'm not sure how much credence this theory has though.
adognoW said:
I've this problem when using headphones, where there is this click when audio is started or stopped on the One X, like when using the music player or watching videos. This problem does not extend to the phone's in-built speaker, so when say, starting and stopping music while on the phone's external speaker, there is no clicking noise.
What I've ascertained at least is that this is not affected by any existing apps which modifies sound (since I did a factory reset and tried the audio again, after reading one of the threads on XDA).
But two new things have occured recently, which are
1) I unlocked (and then re-locked) the bootloader (I actually wanted to install a third-party ROM but I had to put that on hold because I didn't have time).
2) My phone just acquired a OTA update from HTC (software no: 2.17.707.3)
Unfortunately as I got this OTA just about a day before I unlocked the bootloader, I cannot determine whether this problem started after the OTA, or after the bootloader was unlocked (there was a factory reset forced by the phone), or if this clicking sound has even anything to do with it. But it definitely didn't occur either before the OTA or the bootloader unlock.
Click to expand...
Click to collapse
The clicking sound it normal, you can reduce this effect but not remove it completely, this pop/click sound when starting or stopping music indicates the DAC being muted when not in use and voltage to the DAC gets cut off (no you cannot stop that from happening). That static sound is the voltage going though
try and remove all you equalizers, volume modifications, virtualizers, bass boosters etc to reduce this effect
ZeroInfinity said:
The clicking sound it normal, you can reduce this effect but not remove it completely, this pop/click sound when starting or stopping music indicates the DAC being muted when not in use and voltage to the DAC gets cut off (no you cannot stop that from happening). That static sound is the voltage going though
try and remove all you equalizers, volume modifications, virtualizers, bass boosters etc to reduce this effect
Click to expand...
Click to collapse
Thanks for the elucidation, however if I may ask, do you have any idea as to why this wouldn't have happened before? I've owned the HOX for 5 months and it only happened now. Moreover, why does this sound not happen on the phone speaker but only over headphones?
adognoW said:
Thanks for the elucidation, however if I may ask, do you have any idea as to why this wouldn't have happened before? I've owned the HOX for 5 months and it only happened now. Moreover, why does this sound not happen on the phone speaker but only over headphones?
Click to expand...
Click to collapse
I only have it over the headphones as well, its totally normal, during time it will start to get noticeable, but no need to worry about it, if it annoys you well, there it not much that can be done except turn off beats audio..... I don't mind it since I don't start/stop all the time lol so it's not that bad
I may/may not make a difference but you could switch kernels (if you are rooted) and see if this effect still happens, Since the hissing noise/popping sound is by voltage
ZeroInfinity said:
I only have it over the headphones as well, its totally normal, during time it will start to get noticeable, but no need to worry about it, if it annoys you well, there it not much that can be done except turn off beats audio..... I don't mind it since I don't start/stop all the time lol so it's not that bad
I may/may not make a difference but you could switch kernels (if you are rooted) and see if this effect still happens, Since the hissing noise/popping sound is by voltage
Click to expand...
Click to collapse
My phone isn't rooted.. yet.
Say, could this thing be fixed by an update? Is it a hardware-specific issue (maybe it has something to do with the previous OTA)?
adognoW said:
My phone isn't rooted.. yet.
Say, could this thing be fixed by an update? Is it a hardware-specific issue (maybe it has something to do with the previous OTA)?
Click to expand...
Click to collapse
i can assure you that this is not a hardware issue, I know many people have this as well
It can be fixed in the future by htc
ZeroInfinity said:
i can assure you that this is not a hardware issue, I know many people have this as well
It can be fixed in the future by htc
Click to expand...
Click to collapse
Okay, thanks for your help. It's really appreciated.
Oh and sorry guys, one last question, but not really related to the clicking thing.
When I re-locked my bootloader, the command prompt reads:
<bootloader> Lock successfully...
FAILED <status read failed <Too many links>>
finished. total time: 0.121s
Click to expand...
Click to collapse
But under the bootloader screen on the phone, it reads re-locked (the words in the pink colored highlight).
So, is there something I should be concerned about here?
(It's been mentioned already by several people here but is burried in the 1.4 update discussions. I feel the need to pull this serious problem to the daylight.)
It behaves as follows:
With the Bluetooth "Play phone audio on watch" option OFF everything works fine but like before 1.4 update (no phone call possible from/to the watch).
When I enable "Play phone audio on watch", strange things begin to hapen when I try to use the newly enabled phone call capability.
Call initiated from the watch or answered on the watch results in mute call. Other than that the GUI of the phone and the watch behaves like the phone call is connected and running. The problem of not working proximity sensor (http://forum.xda-developers.com/showthread.php?t=3330372) also applies here.
Call answered conventionally on the phone results in several seconds mute call (very annoying, making all the "Play phone audio on watch" unusable in practice), after that everything is ok (like in the scenario 1 - "Play phone audio on watch" OFF).
So, it seems I have a problem with sound streaming between my phone and watch. The problem of Shazam not working (http://forum.xda-developers.com/showthread.php?t=3258367) applies fully (don't know if relevant here). I didn't find any other way to test it. I'm on Slimkat 4.4.4, Samsung Galaxy SII. Fresh factory reset after 1.4 sideloaded update.
Microphone is working (Google voice search tested).
Speaker is working (Ringtones are playing)
Please help with further troubleshooting.
This update, to say the least, is very buggy. I have the same issue you do with calls making the phone capabilities nearly useless.
I have factory reset a few times. I think the OS is the culprit. Its putting the watch too far to sleep (if such a thing is possible).
I have hesitation on my watch faces (some more than others) and my bluetooth will randomly drop then reconnect.
nalott said:
Call initiated from the watch or answered on the watch results in mute call.
Click to expand...
Click to collapse
I haven't had this problem so far. Maybe it's related to the Android version running on the phone. I'm using Android 6.0 (HTC One M8 / Google Play Edition).
In case more users confirm this issue, I think it's a good idea to make a report in the AOSP issue tracker:
https://code.google.com/p/android/issues/list
I've done that for the proximity sensor issue.
I can confirm Shazam not working for me with MEC23L.
Hi,
I have my OP3 for 2 weeks, but there is something strange, the phone is opening the music player in the notification without reasons, sometimes when I'm scrolling across an app or while I lock the phone. At least 2/3 times per days !
But it doesn't launch the music, it just open the music player in the notification.
I'm using full STOCK phone, I disabled the next/previous music gestures, didn't changed anything !
If someone could help me for that it would be nice ! Is it a know software issue ? Maybe I would have a hardware issue ?
Thanks !
This won't be much help but sometimes PowerAmp did that too on CM13 for absolutely no reason, with BT off, so it wouldn't have connected to the car stereo. Wish I could figure out why
Salty Wagyu said:
This won't be much help but sometimes PowerAmp did that too on CM13 for absolutely no reason, with BT off, so it wouldn't have connected to the car stereo. Wish I could figure out why
Click to expand...
Click to collapse
Could it be hardware related ?
I have been having the same problem for a long time and I have always been on OxygenOS(currently running the Open Beta 7). I always thought it was a problem with Saavn but I didn't look for an alternative or a solution since I had paid for its pro service. This now seems to be a general problem...
TheSkyline35 said:
Hi,
I have my OP3 for 2 weeks, but there is something strange, the phone is opening the music player in the notification without reasons, sometimes when I'm scrolling across an app or while I lock the phone. At least 2/3 times per days !
But it doesn't launch the music, it just open the music player in the notification.
I'm using full STOCK phone, I disabled the next/previous music gestures, didn't changed anything !
If someone could help me for that it would be nice ! Is it a know software issue ? Maybe I would have a hardware issue ?
Thanks !
Click to expand...
Click to collapse
Edit: Never mind, somehow I missed that you already tried this, sorry.
Disable the "Music control" from Settings->Gestures and see if that helps. I had the music player opening a couple of times when leaving locked phone on the table, I guess my fingers touched the screen and phone thought I was drawing the music control gestures
Harsh862 said:
I have been having the same problem for a long time and I have always been on OxygenOS(currently running the Open Beta 7). I always thought it was a problem with Saavn but I didn't look for an alternative or a solution since I had paid for its pro service. This now seems to be a general problem...
Click to expand...
Click to collapse
Still happning on the Beta 7 ?
How is it possible ? It's not software solvable ?
Because if it's a hardware issue that I couldn't fix then I would like to know it and maybe push back the phone before the end of my 15 days return.
I had a similar issue where Google music would start by itself, even with gestures disabled. I uninstalled gm updates, cleared all cache, reinstalled gm. So far so good. However, just today another perhaps unrelated problem: music is routed through external speakers while listening over the same wired headphones. I made sure plugged in all the way, it only worked by removing and reinserting them.
Sent from my 1+3
hi
its not a hardware issue. Actually its a gesture issue. Disabled it from the gesture menu. Problem solved for me
thanks
rohit_sachdeva2002 said:
hi
its not a hardware issue. Actually its a gesture issue. Disabled it from the gesture menu. Problem solved for me
thanks
Click to expand...
Click to collapse
I already disabled gestures, didn't changed anything. This morning when I woke up the music player was again in the notification, whereas I didn't touched the phone during all the night. And this happen even when I'm using the phone.
millicent said:
I had a similar issue where Google music would start by itself, even with gestures disabled. I uninstalled gm updates, cleared all cache, reinstalled gm. So far so good. However, just today another perhaps unrelated problem: music is routed through external speakers while listening over the same wired headphones. I made sure plugged in all the way, it only worked by removing and reinserting them.
Sent from my 1+3
Click to expand...
Click to collapse
Well, this seems to be a GM issue. I have Spotify on the phone and it's only launch the stock music player.
Well so I have the issue where microphone would not work sometimes, yeah I know Pixels have the hardware microphone issues but I am not sure! For me suddenly the mic would stop working! No sound in videos, no sound picked up from audio recording apps, no google assistant response etc., but the good thing is phone call audio always works! So I let a sound decibel metre app run for half an hour to see whether the audio is breaking in middle, and no, there is no breakage in middle, so when it works it works, it doesn't stop in middle, but when I wake the phone up after say a one hour standby then it stops responding. Sometimes a reboot fixes it, sometimes it simply starts working after a while!
I am on stock ROM, rooted with SuperSU and using suhide etc., could this be a software issue?
My mic stopped working in Sept or Oct. Also connect a headset and audio still plays from the speaker. But phone somewhat knows a headset was connected, the music will stop playing from the speaker when I unplug the headset. After Oct update I a reset, issue persist.
Oh, and I can't use the phone as a phone. If I answer or call, the phone hangs and reboots.
No issues here, since it works sometimes, means that no hardware issue, try a factory reset.
ControlNode said:
My mic stopped working in Sept or Oct. Also connect a headset and audio still plays from the speaker. But phone somewhat knows a headset was connected, the music will stop playing from the speaker when I unplug the headset. After Oct update I a reset, issue persist.
Oh, and I can't use the phone as a phone. If I answer or call, the phone hangs and reboots.
Click to expand...
Click to collapse
I'm having the same problem with mine. I have to reboot and let it settle for a few min after then it seems to work fine for a while until it happens again.
Sent from my Pixel XL using Tapatalk
Are you using the call recorder app ? I find that to be the culprit.
Next time, it stops working, just ls -l /dev/snd, and see whether one file is with permission 600. ( I could not recall the detailed filename now ).
After changing the permission to 660 of that file, everything will work once again.
ithehappy said:
Well so I have the issue where microphone would not work sometimes, yeah I know Pixels have the hardware microphone issues but I am not sure! For me suddenly the mic would stop working! No sound in videos, no sound picked up from audio recording apps, no google assistant response etc., but the good thing is phone call audio always works! So I let a sound decibel metre app run for half an hour to see whether the audio is breaking in middle, and no, there is no breakage in middle, so when it works it works, it doesn't stop in middle, but when I wake the phone up after say a one hour standby then it stops responding. Sometimes a reboot fixes it, sometimes it simply starts working after a while!
I am on stock ROM, rooted with SuperSU and using suhide etc., could this be a software issue?
Click to expand...
Click to collapse
Problem persisted factory reset and updated factory image install. Warranty replacement and replacement is working fine.