[Q] people complain they cant hear me - One (M7) Q&A, Help & Troubleshooting

Hi i'm using a rooted htc one and people often complain they cant hear me during calls. I was wondering if there was anyway I could enhance the microphone so that my voice is louder. I'm using android 4.1.2 and sense 5. The case i'm using has a hole on the back in the top right corner and on the bottom to the left of the usb adapter jack where I think the microphone(s) are. I looked at other threads but I was having this problem before I rooted my htc one and was hoping that now it has been rooted there was some sort of hiden control I can use to turn up the michrophone setting. Thanks

bump

If it wasn't working right before you rooted it, then it means it is a hardware problem. I don't think this is necessarily a sensitivity issue. I think it has to do with the noise canceling.
Talk to HTC or whatever carrier you have.
Also, make sure to hide all signs of root!

Hej layzz, there is a thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2380867
Just as I mentioned there, it could be the hole at the underside of your case being just way to small, or (as I realized just recently) a very special hardware problem (so to say). During calls I had always covered the mic with my little finger, no wonder no one understood me.
Give it a shot

Xayden said:
Hej layzz, there is a thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2380867
Just as I mentioned there, it could be the hole at the underside of your case being just way to small, or (as I realized just recently) a very special hardware problem (so to say). During calls I had always covered the mic with my little finger, no wonder no one understood me.
Give it a shot
Click to expand...
Click to collapse
i had a similar problem too, i upgraded to 4.2.2 on 2.24 (ARHD) and now its fixed.
the proximity sensor is also fixed

Muhammad.Muayad said:
i had a similar problem too, i upgraded to 4.2.2 on 2.24 (ARHD) and now its fixed.
the proximity sensor is also fixed
Click to expand...
Click to collapse
The mic hole at the bottom of the device is clearly visible. Would you mind posting a link to that rom please?

layzz said:
The mic hole at the bottom of the device is clearly visible. Would you mind posting a link to that rom please?
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2183023
This ROM is based on 4.2.2 on 2.24 all my problems are pretty much fixed

I have this very same problem on my brand new stock device. I created a thread for the same problem. I found that the earpiece quality was brilliant but again people could not hear me or said I was very quite. I experimented with case on and case of and calls to different phones and 9/10 times the problem was there. I then decided to install android revolution hd to see if there was a problem with the stock rim for some reason. Sadly this didn't work. I then turned my attention to the lower microphone. Now I am not suggestion you do this by any means however in my case I felt I had nothing to lose as I was going to have to send the phone to HTC to get fixed if I could not sort it myself.
I got the small sim removal tool and stuck it into the mic hole in a bid to try and open the hole up abit as it seemed very small and I wondered also if it was blocked. I did this a little at a time and then tried calling people to see if there was any change. Instantly there was an improvement. However, now it seemed like 5\10 calls were low. So, I tried the same again.
I now have not had the problem in the last 15 or so calls I have made however what I have noticed is that now for what ever reason when I'm in calls the person on the other end sounds a little distorted through the earpiece. Don't know why this should be and maybe a completely unrelated problem or something linked to installing the other rom. Either way at least people can hear me now.
Sent from my HTC One using xda premium

Thanks everyone. The problem seems to be fixed after installing that custom rom

Related

[Q] Screen goes black during calls

Hello there xda!
I have had this problem with my galaxy S for quite some time now but since I still haven't found a solution I turn to you!
HereĀ“s the thing, whenever I make or receive a call on my phone the screen blacks out. It stays black until I yank out the battery.
Sometimes the screen comes back when the call ends but this is more the exception rather than the rule.
If I got my headphones/headset in, the screen does not go black, so I try to always have them plugged in.
My thoughts are that something is wrong with the proximitysensor in the phone and is blacking out the screen, I got an app that show all sensors and the values didn't change when I covered the sensor.
I have rooted my phone several times with different roms so when this problem occured I tried all kinds of different roms to see if it would fix the problem.
No stock roms or other roms have worked so I assume its a hardware fail but for whatever reason I cant help but think that its more likely to be a software issue.
I am currently running darkys 10.2.2 rom.
If you got any questions that could help you come up with an answer, don't hesitate to ask
EDIT, Solution!
For anyone with the same problem, I FIXED IT!
I ordered a new earpiece on the internetz, installed it and now the phone works perfectly!!
The earpiece actually has both the headphone jack and the proximity sensor and the light sensor on it, so replacing the earpiece replaces all of those.
Hope this helps someone!
Hey dude, i dont know how you can fix the proxmity sensor if it is broken,
however, i have heard of other people with the same problem.
And they solved it with an app called ProximityScreenOff wich is downloadable form market.
atleast you wont have to yank out your battery everytime you get an call!
Hope this helps!
pzayx said:
Hey dude, i dont know how you can fix the proxmity sensor if it is broken,
however, i have heard of other people with the same problem.
And they solved it with an app called ProximityScreenOff wich is downloadable form market.
atleast you wont have to yank out your battery everytime you get an call!
Hope this helps!
Click to expand...
Click to collapse
Tried some different settings but couldnt get it to work.. Screen still shut off during calls
Thanks for the try though! Might have to order a new proximity sensor and see if it fixes it
For anyone with the same problem, I FIXED IT!
I ordered a new earpiece on the internetz, installed it and now the phone works perfectly!!
The earpiece actually has both the headphone jack and the proximity sensor and the light sensor on it, so replacing the earpiece replaces all of those.
Hope this helps someone!
snelpiller said:
For anyone with the same problem, I FIXED IT!
I ordered a new earpiece on the internetz, installed it and now the phone works perfectly!!
The earpiece actually has both the headphone jack and the proximity sensor and the light sensor on it, so replacing the earpiece replaces all of those.
Hope this helps someone!
Click to expand...
Click to collapse
LOL, i was just ABOUT to post this EXACT same solution then read your post. I had the same problem and other problems that wererelated to the network, dropped calls, black screen after calls begins etc. and installing an earpiece from an T959's took care EVERYTHING. I'm not sure how this earpiece fixed the network problem. If somebody knows and would like to enlighten me, that's be great!

Call issue

I've got a problem with calls. On stock ROMs and Paranoid Android, with every kerenels.
Sometimes I can't hear the person with who I'm talking but only on "normal mode". When I activate loudspeaker or plug in headphones I can hear without problems but after deactivating or plugging out the problem comes back and I can't hear anything. This occurs not always but very often.
Can someone helps?
I had this issue you may want to check with other people around here who are running cyanogenmod as far as I know mine was spoiled so I had to change it no idea if it was cause by cyanogenmod highly doubt it
I have the same issue! I actually had it when I was running OEM software, before rooting I sent it in to sony with the complaint 3 times. Each time they returned it with simply a software update applied.
I find if you cover and uncover the light sensor a couple of times it tends to fix itself, but its frustrating!
Yes, very frustrating! But this must be a software defect.
Maybe someone could make a fix...
Any help?
I highly doubt that it is a software defect issue but if it is a really software defect issue causing the ear speaker to fail then sony has some explaining to do nevertheless some of them reported the same issue with cyanogenmod 11.0 so honestly I dont know what is causing this but overall it seems like quite a big issue..
http://talk.sonymobile.com/t5/Xperi...e-can-t-hear-me-with-my-xperia-zl/td-p/758763
did you amplify the speaker or did anything to it, in the past etc ? like fauxsound
if you never did did you remain on stock kernel with cm11 all the way
Yes. I used some mods like pxa, but without any mods and with the problem exists
kael2404 said:
Yes. I used some mods like pxa, but without any mods and with the problem exists
Click to expand...
Click to collapse
then your hardware is damage sent it to the service centre
But it exists only sometimes and mostly with weak range
kael2404 said:
But it exists only sometimes and mostly with weak range
Click to expand...
Click to collapse
yeah it is damaged how long did you have your xperia z cause I had mine for 1 year 3 months before it died today it works fine.
huh? so what is causing this? sound-mods or just bad luck? had my xperia z 1 year 4 months and so far its ok... (*touch wood*) will be gutted if it dies...
must be sound mod blow out the speaker o.o no idea but I got mine fully replaced.
I had the same Problem. After installing Sound About from playstore and disabled headphone detection the Problem is gone
haha it isn't the old 'dust in the headphone socket' problem is it?

Speaker crackle/distortion is it hardware och software related?

Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Jaxione said:
Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Click to expand...
Click to collapse
No problem for me here, not even on the highest volume level. If some users have this issue its probably a hardware faillure rather then software.
Jaxione said:
Hi!
Seen many others facing the issue with speakers crackling/get distorted att hight volumes on notifications/ringtones. For example alarm sound named Oxygen sounds distorted on higher volume and also the ringtone Ganymede. But youtube and such sounds like they should even att highest volume. Is this on all phones? Is it software or hardware related? Absolutley loving the phone but if my speakers are broke I need to try and get a replacement.
Can anyone confirm that they have no distortion/crackle at all?
Br J
Click to expand...
Click to collapse
Some devices are facing this issue. If it's only happening on highest volume then it's a software issue or else it's a hardware issue
SAW_JOK3R said:
Some devices are facing this issue. If it's only happening on highest volume then it's a software issue or else it's a hardware issue
Click to expand...
Click to collapse
If it is a software issue, how come only some devices have it and not all?
Br J
Jaxione said:
If it is a software issue, how come only some devices have it and not all?
Br J
Click to expand...
Click to collapse
I've no proper explanation to give But same happening with force shutdown / random force reboot issue. It's affecting Many users but not All
SAW_JOK3R said:
I've no proper explanation to give But same happening with force shutdown / random force reboot issue. It's affecting Many users but not All
Click to expand...
Click to collapse
This sucks How could they solve software issues that is only affecting some phones? If I send mine back It will take 2-3 weeks for it to come back. And I think the company that I bought it from will just scratch their heads and find no problem with the phone. I from sweden and Motorola isnt represented here so I have to go through the company I bought it from sucks. Will never buy from them again.
Br J
Jaxione said:
This sucks How could they solve software issues that is only affecting some phones? If I send mine back It will take 2-3 weeks for it to come back. And I think the company that I bought it from will just scratch their heads and find no problem with the phone. I from sweden and Motorola isnt represented here so I have to go through the company I bought it from sucks. Will never buy from them again.
Br J
Click to expand...
Click to collapse
It's not their fault. It's Google's fault. Go to this Google Forum Topic and go to first page. You can see it's marked as complete by a google employee. Fix will come with the new update
SAW_JOK3R said:
It's not their fault. It's Google's fault. Go to this Google Forum Topic and go to first page. You can see it's marked as complete by a google employee. Fix will come with the new update
Click to expand...
Click to collapse
Read throught the thread. The only thing google are saying is that the cant reproduce the problem. Can read anywhere that they will fix it.
Mvh J
Jaxione said:
Read throught the thread. The only thing google are saying is that the cant reproduce the problem. Can read anywhere that they will fix it.
Mvh J
Click to expand...
Click to collapse
They can only fix it by update
SAW_JOK3R said:
They can only fix it by update
Click to expand...
Click to collapse
If you read through that thread you will se that it was set to completed because of that the google employee couldnt reproduce the problem and therefor asks people to ask for a replacement phone. So I dont think they marked this thread Completed because it will be solved in an update.
Br J
Jaxione said:
If you read through that thread you will se that it was set to completed because of that the google employee couldnt reproduce the problem and therefor asks people to ask for a replacement phone. So I dont think they marked this thread Completed because it will be solved in an update.
Br J
Click to expand...
Click to collapse
Yeah, I know. That's why said. As it's marked as completed, that means the support team of the forum was not able to solve the issue so they've forwarded the issue to Google devs to solve it
SAW_JOK3R said:
Yeah, I know. That's why said. As it's marked as completed, that means the support team of the forum was not able to solve the issue so they've forwarded the issue to Google devs to solve it
Click to expand...
Click to collapse
Lets hope they do. It must be software related in my case. Noticed a thing when testing a bit today. When I hold my phone normally the "crackle" / "bad sound" comes from the top speaker and the bottom one sounds fine but if I turn the phone to landscape mode the crackle jumps down to the bottom speaker and the top speaker sounds fine. Reaaally strange
Br J
Jaxione said:
Lets hope they do. It must be software related in my case. Noticed a thing when testing a bit today. When I hold my phone normally the "crackle" / "bad sound" comes from the top speaker and the bottom one sounds fine but if I turn the phone to landscape mode the crackle jumps down to the bottom speaker and the top speaker sounds fine. Reaaally strange
Br J
Click to expand...
Click to collapse
The crackle problem does the same on me ,except the landscape experiment which I haven't done .But if it really occurs just as you explain ,than it is most probably (or it looks like) software related issue. Anyway it indeed seems strange :|
I just enabled encryption and regarding cracks and rispy sound it seems better.
Maybe someone else who have this issue can test?
I definitely have this issue. On latest M firmware on Sprint variant. I manually flashed firmware.. Saw somewhere else on here where someone solved problem by installing viper audio and setting to super hi quality sound.. May try that. Seems like I recall on og Nexus 7 some kernels would cause the device to get too hot (like the charger that came with phone does for me..) And speakers would get messed up as a result and distort. Hope that's not the case here. :banghead:
Its most likely software. It almost sounds the same as the speaker distortion that the one m8 had when running cm due to the lack of proper audio drivers. Its most likely a driver issue which is why some have had success with viper. For now I would not max out volume when using the phone just to protect the speakers and we will just have to wait and see if google releases a fix.
toknitup420 said:
Its most likely software. It almost sounds the same as the speaker distortion that the one m8 had when running cm due to the lack of proper audio drivers. Its most likely a driver issue which is why some have had success with viper. For now I would not max out volume when using the phone just to protect the speakers and we will just have to wait and see if google releases a fix.
Click to expand...
Click to collapse
I sure hope that you and others who've said same are correct. If that is the case Google needs to get with it and push an image that fixes it asap.
Update: (Sprint N6-latest firmware-M..) I installed Dirty Unicorn test build 5.1 dated 3/29 from their G+ community and not one crackle comes out even on the highest volume my device is fine. Was not like that on stock Google rom.. I was getting a feedback sound coming from exterior speakers as well and its not present anymore. Just wanted to share that.

[Q] Did anyone experience a very faint clicking sound form the phone with some apps?

I just got a nexus 6, and after installing a few apps I've noticed a faint clicking sound during phone calls.
At first I thought it's coming from the call, but later discovered it's coming from the upper half of the phone itself, and I can only hear it when putting my ear flush against the screen (can't hear anything from the back).
I (accidentally) discovered it's because I'm using a live wallpaper. No idea why, but when I changed the wallpaper the noise was gone. It can also be caused by a few other apps, though I wasn't able to find a common feature or attribute between those apps. The noise starts immediately after opening the app, and stops immediately after exiting.
If It's relevant, I'm on Chroma rom, LP 5.0.2 running franco kernel.
It doesn't actually bother me, but I'm still curious about this, as well as a bit worried the it might be an indicator for a wider issue, so I'd really like to hear your opinion.
If anyone would be willing to try the original "culprit", here it is (It's just a normal live wallpaper): https://play.google.com/store/apps/details?id=com.schulermobile.puddledrops
Thanks
dude1001 said:
I just got a nexus 6, and after installing a few apps I've noticed a faint clicking sound during phone calls.
At first I thought it's coming from the call, but later discovered it's coming from the upper half of the phone itself, and I can only hear it when putting my ear flush against the screen (can't hear anything from the back).
I (accidentally) discovered it's because I'm using a live wallpaper. No idea why, but when I changed the wallpaper the noise was gone. It can also be caused by a few other apps, though I wasn't able to find a common feature or attribute between those apps. The noise starts immediately after opening the app, and stops immediately after exiting.
If It's relevant, I'm on Chroma rom, LP 5.0.2 running franco kernel.
It doesn't actually bother me, but I'm still curious about this, as well as a bit worried the it might be an indicator for a wider issue, so I'd really like to hear your opinion.
If anyone would be willing to try the original "culprit", here it is (It's just a normal live wallpaper): https://play.google.com/store/apps/details?id=com.schulermobile.puddledrops
Thanks
Click to expand...
Click to collapse
Hi, I think you might find some more info here:
http://forum.xda-developers.com/showthread.php?t=2962949
It seems that this is a somewhat common issue.
I actually found the issue you linked to in another place. At the time it didn't seem to be relevant (I thought noise isn't from the speaker), but on second thought, this is probably it.
Thanks.
dude1001 said:
I actually found the issue you linked to in another place. At the time it didn't seem to be relevant (I thought noise isn't from the speaker), but on second thought, this is probably it.
Thanks.
Click to expand...
Click to collapse
No problem at all. I hope that a solution becomes available for this issue.

Multitouch with +5 fingers

****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine
Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
anyone ?
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.

Categories

Resources