Related
I've just got a jawbone icon, and twice already I've been on the phone, and someone else calls (call waiting), immediately the headset disconnects and eventually reconnects. Not sure if this problem lies with htc or jawbone.. does anyone have a jawbone or infact any bt headset to see if this can be reproduced?
Sent from my Desire HD using XDA App
I'm quite worried to hear this. I've ordered a plantronics bluetooth headset which should be arriving on monday. I'll definitely update you once I've had a play.
Sort of ironic that the only reason I wanted to get the headset was because the loudspeaker is so bad... And now we see that BT doesn't work too well either.
Sent from my Desire HD using XDA App
Im using a Sony ericsson MW600, works flawlessy with my earlier phone but its behaving really weird on my Desire HD.
Listening to media in all it forms often works without hassle, but as soon as the phone function is being called - it randomly disconnects, reconnect, and by then the phone has already switched the sound back to the phone.
Also seeing alot of problems with switching the sound between different modes during a call, the option is there, but nothing happens.
And sometimes I cant even call people trough my BT headset, I connect it, doesnt use it for anything else before - and call someone, and still it doesnt get the sound right
So, some problems alright - longing for customs ROMs
utor99 said:
And sometimes I cant even call people trough my BT headset, I connect it, doesnt use it for anything else before - and call someone, and still it doesnt get the sound right
Click to expand...
Click to collapse
Me too .. workaround whilst in the phone call is to switch to speaker or 'desire hd' and then back to bt headset this works every time for me
Sent from my Desire HD using XDA App
problem also with carkits
The BT problem also exists in connection to several carkits.
See post Bluetooth Problems
Leon
Feel free to correct me, but I think this problem belongs to the Jawbone.. it just happened on my other phone aswell (not android) so hopefully it's not a desire hd thing also..
I Will bump this One.
I have a mw600 and am experiencing some annoying problems.
First of all I cannot use it for calls at all. Cant even record anything from the headsets mic.
Second i have noticed that the sound quality is bad compared to when i connect the device to an itouch.
I really hope this is a software issue so I dont have to send the phone in for reparations.
Anyone else noticed the same issues with sound quality?
Were u able to fix it?
Sent from my Desire HD using Tapatalk
Using MW600 myself - works fine (for calls and music)
did not try recording - don't think it's supposed to work.
- remember that you need to pick up the phone using the answer button on MW600 if somebody calls you, or else it defaults to internal speaker, (and you can choose MW600) then. (move sound).
The only problem I've seen is, that sometimes MW600 cannot be used for calls anymore, it helps then to restart the hansfree, and it works again. - this did not happen on HD2.
Same Problem
lawrence750 said:
I've just got a jawbone icon, and twice already I've been on the phone, and someone else calls (call waiting), immediately the headset disconnects and eventually reconnects. Not sure if this problem lies with htc or jawbone.. does anyone have a jawbone or infact any bt headset to see if this can be reproduced?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Have the same exact problem with Icon HD. This is the Jawbone, not the phone / BT error...
Jawbone ERA - the best of the best!!!
The sound is just amazing! :good::good::good:
Anyone else having issues with wifi calling? Initially people were complaining they could not hear me or constantly telling me to repeat myself. I left myself a voicemail on my work phone and was surprised how low the volume was. It's as if the mic gain was turned all the way down. I had to turn the volume to maximum just to makeout what I was saying. Additionally, the earpiece volume is also a tad low on my end. I'm assuming it's safe to say there is nothing I can do till Tmobile updates the phone, right?
tibere86 said:
Anyone else having issues with wifi calling? Initially people were complaining they could not hear me or constantly telling me to repeat myself. I left myself a voicemail on my work phone and was surprised how low the volume was. It's as if the mic gain was turned all the way down. I had to turn the volume to maximum just to makeout what I was saying. Additionally, the earpiece volume is also a tad low on my end. I'm assuming it's safe to say there is nothing I can do till Tmobile updates the phone, right?
Click to expand...
Click to collapse
I just did a test on wifi calling to my voicemail at home and the volume was fine, sounded like a normal call. There was another voicemail on there as well from someone else and it was the same volume as theirs.
Robertsonland said:
I just did a test on wifi calling to my voicemail at home and the volume was fine, sounded like a normal call. There was another voicemail on there as well from someone else and it was the same volume as theirs.
Click to expand...
Click to collapse
Hmmm...weird. I have no issues with mic volume during regular cellular calls and Skype calls (tested these two by leaving myself voicemails also).
I will call technical support and see what they have to say.
Thanks for the reply Robertsonland
I haven't had any issues (I had latency and sound issues on my Samsung Vibrant and Blackberry Curve before that using UMA) on my Sensation using Wifi calling yet. I used my friends phone while making a wifi call to it, and there was no delay at all, and the sound is great.
Bump. No one else is having low mic outgoing volume issues with wifi calling?
tibere86 said:
Bump. No one else is having low mic outgoing volume issues with wifi calling?
Click to expand...
Click to collapse
Happens to me sometimes, but not too often
Sent from my HTC Sensation 4G using Tapatalk
tibere86 said:
Bump. No one else is having low mic outgoing volume issues with wifi calling?
Click to expand...
Click to collapse
Constant. Wifi Calling is unpredictable. I have no network reception and the phone struggles to keep on wifi calling. I have tried most available roms all the patches and three devices. WIFI Calling is unreliable while using the phone. It works fine when left alone 90% of the time. However those times you pick up the phone and it doesn't show Wifi Calling, or it just then kicks in; you are catching it in its moment of sudden tmobile retardation. And i have tried it will all sorts of access points, obsessed over dd-wrt settings for weeks. Even ended up bricking a couple devices (JTAG ftw).
S-OFF Sensation LeeDroid 1.2 1.3 TMO-US Wifi Calling v1.0
If it's going in and out of WiFi calling like that it's the Sensation's WiFi reception causing the issues.
Do you put your hand over the top part of the phone when you're on a call?
My friends complain that they can hear themselves. Like an echo effect.
Sent from my HTC Sensation 4G using XDA App
Happens all the time with me and my wife...to the point that I don't use wifi calling anymore. It is certainly a problem.
echoing on speakerphone has happened to me, solution.. don't use speakerphone.
Well I'm glad I found this thread because I am having the exact same issue and was going to return my Sensation. I have no regular cell signal in my house so I have to rely on the Wifi calling and it sucks from time to time. I have to repeat myself and sometimes the other person can't hear me even if I'm yelling in the handset. So from what I've been reading, it sounds like this is a normal (abnormal) wifi calling issue with Tmobile. That sucks!!! Is there any fix or possible bandaid for this problem?
Does this only happen with the Sensation or are others having this problem with other phones?
Bumb
Anyone have found a solution to this issue ?
I just joined Tmobile and i an having the same issue .
Microphone seems to be very week and i sound far away when i call using wifi .
Tried to hold the phone in different positions and i am using a case but no changes .
Tinofet said:
Anyone have found a solution to this issue ?
I just joined Tmobile and i an having the same issue .
Microphone seems to be very week and i sound far away when i call using wifi .
Tried to hold the phone in different positions and i am using a case but no changes .
Click to expand...
Click to collapse
I have the same issue sometimes too, If i try to turn on speaker phone the mic cuts off all together. Using Revolution HD
You know .
I truly do not believe its a reception ( wifi reception or anything ) .
I ran packet capture and it all look`s "ok" no drops or resets .
This thing looks like a poor VOIP decryption , either on the phone or the Tmobile servers.
IT IS a software issue . And defenitly need to be attended to .
what i did notice that i have a sensation and so do my wife .
I get the issue she doesn't .
The difference i rooted my machine ( still uses original ROM i have a trust issue regarding running some unverified kernel`s ) .
Any thoughts ?
I have called Tmobile about the issue. The tech I talked to said there were no other reports of low mic volume. My mic volume works perfect when using Skype or SIP. But when on Wifi calling, the mic gain is way too low. I have left myself test voicemails, and I have to have the volume cranked all the way up to hear myself. Hopefully the issue will be resolved with the next software release.
Man that sucks .
This Wifi calling is cool and i like it , but if it doesnt work whats the point .
Any way to contact the development team of this product ?
Calling and talking to some dude in India at Tier I do not help here...
I have used several custom ROMs and Kernels and have had no issue with sound volume or quality using the WiFi calling app. It may be a simple hardware difference during manufacturing. Just as some people's phones work flawless while OC'd and others crash even though they all have the same model CPU. I would try to get a replacement phone to see if it works better.
I actually have another 2 new phones next to me .
Any way to clone my OS (including the config and everything ) to the other phone ?
Then i can move my SD and SIM .
Whenever I install official JB 4.1.1 or lux droid v3, My speaker sound is changing by itself drom speakerphone to in-ear.But always do that after I record video and play it.All media sound (ringtone, music..etc) went through IN-ear speakerphone.I tried "villec2_jb_speakerfixv9" but no help.
I have HTC One S cid_032 s3 vesion.What to do now ?
ty
Can anyone hlp me ?
ficicaaa said:
Whenever I install official JB 4.1.1 or lux droid v3, My speaker sound is changing by itself drom speakerphone to in-ear.But always do that after I record video and play it.All media sound (ringtone, music..etc) went through IN-ear speakerphone.I tried "villec2_jb_speakerfixv9" but no help.
I have HTC One S cid_032 s3 vesion.What to do now ?
ty
Click to expand...
Click to collapse
Well, I'm facing exactly the same issue. It is quite strange. If I record a video on my phone, and then play it, the sound would come from earpiece (front speaker) instead of rear speakers. And after that, the ringtone (on incoming calls), video playback sounds will keep on coming from the front speaker (earpiece). I do not know whether it is a hardware issue or a software issue. Can someone confirm it?
My phone (S3) has JB 4.1.1. I do not know whether Jelly Bean update is causing this issue or not, coz when I bought this phone, it was already upgraded to JB.
Can someone who has upgraded his phone to JB confirm it? Are these kind of issues related to hardware or software?
And well to fix it on temporary basis, what I did was I made call from some other number to my phone (One S), the sound/ringtone was coming from earpiece. After making this call, I went to Sound settings (in HTC one S) and re selected the ring tone and it solved the issue. Now the ringtone and other sounds are coming from rear speakers. If the issue is not resolved after re selecting the ring tone, do one thing, flip your phone and make call again to your phone, reject it, and then again select some ringtone for your phone, hopefully it'll resolve your issue on temporary basis. I also tried that (though the option "flip for speaker" is not selected in my phone).
It seems only few handsets have this issue. :S ?
Anyway if anyone else is facing the same issue, let us know here, so we can discuss about it.
Sent from my HTC One S using xda app-developers app
Hello,
I have the same problem. Sometimes, my sound get crazy and it can be hear from front speaker, except from back speaker.
After that, I have to do a restart and it's OK, but that's annoying.
VilleC2, it happens after JB update.
Impo5sible said:
Hello,
I have the same problem. Sometimes, my sound get crazy and it can be hear from front speaker, except from back speaker.
After that, I have to do a restart and it's OK, but that's annoying.
VilleC2, it happens after JB update.
Click to expand...
Click to collapse
Yeah true. Its quite annoying. Hope it will be resolved in the next update. :S
Sent from my HTC One S using xda app-developers app
First off, please read the poll questions carefully. I'm trying to assess if this is an issue with all XT926 phones or just some, and whether the common thread is that only people with unlocked bootloaders (non-dev editions that is) or locked and unlocked bootloaders experience it?
Here is a description of the issue at hand. Please read it through and then vote in the poll, choosing the answer that best fists your scenario:
There is an annoying "pop" or "click" sound that occurs every time a notification sound occurs, or when I start typing (I use Swiftkey and have key-click sound turned on), or when I lock or unlock the screen. This doesn't happen under JB. It only occurs with the KK OTA.
I have an unlocked bootloader and I was part of the soak test. When I received the soak OTA and applied the update, I noticed the sound behavior.
I have since used an FXZ to flash back to stock JB (9.30.1) and applied the official OTA this time around and the popping/clicking noise is still there.
I know this is supposedly the final update to this phone, but this annoying popping noise needs to be fixed. I'm not the only one that experienced it during the soak as well as with the official OTA.
I've done everything that was asked which is the following:
Turned off sound on key press setting - didn't help.
Turned off Touch Sounds and Vibrate on Touch - didn't help.
I don't know if people fully understand what I'm saying. I know that you can have click noises turned on when you do keypresses and such. Those work fine and I know what they are. The sound I'm talking about sounds like an electrical pop, like there is a short in the phone somewhere. It only occurs on the first keypress when I'm typing in something. If that area I'm typing in loses focus (such as the Google search bar) and then I go back to it and start typing again, the pop noise happens on the first keypress but any further typing in it doesn't make the popping noise, just the normal key clicks unless it loses focus and I come back to it again.
Same goes with notification sounds. When the first one comes up, the popping noise occurs right before or with the notification noise. If I keep the screen on and another notification sound/alert comes up, it happens again.
Or, when I unlock the screen, it gives off the popping noise right before the unlock sound. When I lock the screen, it happens right with or just right after the unlock sound occurs, at least that's what it seems to do.
All of these are repeatable issues.
I really hope a fix can be found for this as it is kind of annoying. Otherwise, the KK update seems to be pretty stable.
Thanks!
I'm running 183.46.10 with an unlocked bootloader and I haven't run into this issue.
Not sure if the exact phone type is relevant, but mine is a RAZR HD Maxx.
killrhythm09 said:
I'm running 183.46.10 with an unlocked bootloader and I haven't run into this issue.
Not sure if the exact phone type is relevant, but mine is a RAZR HD Maxx.
Click to expand...
Click to collapse
It may or may not, but I'm going to see how this all fleshes out. Maybe it's a small number of phones, but I do know people on the Moto forums during the soak had reported this same issue.
If it has to do with either the bootloader being unlocked (or I just have a phone that is "bad", but I don't see how Kit Kat would make the popping noise but JB doesn't), then I'm going to live with it. I definitely do not want to trade this phone in and get one that can't be unlocked. That, or they replace it with something else, of course, they may not do that since it's unlocked when it wasn't meant to be.
Actually, just as I was typing this, I heard two pops while the screen was off. No sounds, but when I looked, I had a notification from Google Play stating that there were two updates to apps on my phone. I believe that was why it popped. The phone was set to vibrate, but it still made the popping noise.
There are lots of reports of the same issue by xt907 users who updated to Moto 4.4.2.
I had to deal with something similar when I was working on the branch of 3.4 caf audio code backports to 3.0 razrqcom/cm kernel for cm-10.2/cm-11.0.
If I remember correctly (it's already quite some time ago), I had to make this revert to fix this issue: https://github.com/CyanogenMod/andr...mmit/1212f2e043341016cacd6b0d93435380750bd78e
In any case, it sounds like an issue that needs to be fixed in kernel.
kabaldan said:
There are lots of reports of the same issue by xt907 users who updated to Moto 4.4.2.
I had to deal with something similar when I was working on the branch of 3.4 caf audio code backports to 3.0 razrqcom/cm kernel for cm-10.2/cm-11.0.
If I remember correctly (it's already quite some time ago), I had to make this revert to fix this issue: https://github.com/CyanogenMod/andr...mmit/1212f2e043341016cacd6b0d93435380750bd78e
In any case, it sounds like an issue that needs to be fixed in kernel.
Click to expand...
Click to collapse
Awesome. That is the first plausible explanation I've heard so far. Everything else has been guesses (turn off this, turn off that, hey what about key press clicks in your keyboard, etc, etc, etc), even though I explain it happens on the first key press but no others as long as the input box keeps focus.
I doubt Motorola will issue a patch for this, but I wonder why it affects some phones and not others?
With the official FXZ out, I decided to reflash my phone with it and the popping noise persists.
Sigh.
I just had this problem last night with whatsapp and thought of this thread. it made a poping noise when I sent a message even though my device was muted.
Another app was doing it as well, I just forgot the name of it cause I was seriously really, really tired ha.
Sent from my DROID RAZR HD using Tapatalk
DireWolfZero said:
I just had this problem last night with whatsapp and thought of this thread. it made a poping noise when I sent a message even though my device was muted.
Another app was doing it as well, I just forgot the name of it cause I was seriously really, really tired ha.
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
Well, someone on the Motorola forum stated they spoke with a Motorola rep and the rep said an update is forthcoming in the next few weeks to address issues people found after the update, but it was mainly for text messaging issues. Let's hope it addresses this popping noise, but I doubt it.
What sucks is, some of this stuff was found during the soak test and yet, they still released it. Shame.
For unlocked bootloader only!
Boot images for XT926 and XT907 stock kitkat:
XT926: http://d-h.st/vre
XT907: http://d-h.st/KXA
Both boot images contain the recompiled stock kitkat kernel with increased sleep time after lineout PA enable, as in this commit: https://github.com/CyanogenMod/andr...mmit/1212f2e043341016cacd6b0d93435380750bd78e
To be flashed via fastboot:
Code:
fastboot flash boot bootXT926speakerfix.img
or
Code:
fastboot flash boot bootXT907speakerfix.img
Please note that I don't own xt926 nor xt907, so I can't verify that the boot images boot at all, nor that they actually fix the issue.
(xt897 haven't got an official kitkat update yet, and it's possible that it won't happen for Photon Q at all.)
Be prepared to flash the stock kitkat boot.img in case of a failure if you're going to test this. You've been warned.
Please let me know how it works for you, thanks.
EDIT: links updated to correctly re-packed boot images. xt926 image confirmed to be booting and fixing the issue by iBolski.
kabaldan said:
For unlocked bootloader only!
Boot images for XT926 and XT907 stock kitkat:
XT926: http://d-h.st/FV2
XT907: http://d-h.st/Ka4
Both boot images contain the recompiled stock kitkat kernel with increased sleep time after lineout PA enable, as in this commit: https://github.com/CyanogenMod/andr...mmit/1212f2e043341016cacd6b0d93435380750bd78e
To be flashed via fastboot:
Code:
fastboot flash boot bootXT926speakerfix.img
or
Code:
fastboot flash boot bootXT907speakerfix.img
Please note that I don't own xt926 nor xt907, so I can't verify that the boot images boot at all, nor that they actually fix the issue.
(xt897 haven't got an official kitkat update yet, and it's possible that it won't happen for Photon Q at all.)
Be prepared to flash the stock kitkat boot.img in case of a failure if you're going to test this. You've been warned.
Please let me know how it works for you, thanks.
Click to expand...
Click to collapse
Thanks for creating this. I tried flashing it and it hung at the Motorola logo. I couldn't get into recovery at all to try and clear cache and dalvik.
When I flashed the original KK boot image, it booted back up.
Not sure if I have to wipe data as well, but I'm going to hold off on that at this time.
Thanks!
iBolski said:
Thanks for creating this. I tried flashing it and it hung at the Motorola logo. I couldn't get into recovery at all to try and clear cache and dalvik.
When I flashed the original KK boot image, it booted back up.
Not sure if I have to wipe data as well, but I'm going to hold off on that at this time.
Thanks!
Click to expand...
Click to collapse
Thanks for the feedback.
It's a simple little change in kernel space, no involved userspace actions as dalvik cache or data wipes should be needed for this. If it doesn't boot then it means something has derped in the process of zImage replacement inside of boot.img...
@iBolski could you please test http://d-h.st/vre ? Thanks.
kabaldan said:
@iBolski could you please test http://d-h.st/vre ? Thanks.
Click to expand...
Click to collapse
Wow! So far, so good. Popping noise has disappeared and this booted up just fine.
Of course, might have to go through this again if/when the update to the OTA comes out. Supposedly, per a Moto rep, there is another one forthcoming to fix issues with text messaging. Makes me wonder if either the popping noise comes back or is fixed?
In any case, thank you. I'll keep testing and let you know if I run into other issues, but so far, this seems to be working just great!
BTW, what exactly was the fix and what was the cause of this popping noise? Why did it affect only certain phones and not all?
Also, per Android Authority, the upcoming 4.4.3 for other devices fixes an issue with popping noises when playing flac audio: http://www.androidauthority.com/android-4-4-3-bug-fixes-389036/
Wonder if this was the same issue?
iBolski said:
Wow! So far, so good. Popping noise has disappeared and this booted up just fine.
Of course, might have to go through this again if/when the update to the OTA comes out. Supposedly, per a Moto rep, there is another one forthcoming to fix issues with text messaging. Makes me wonder if either the popping noise comes back or is fixed?
In any case, thank you. I'll keep testing and let you know if I run into other issues, but so far, this seems to be working just great!
BTW, what exactly was the fix and what was the cause of this popping noise? Why did it affect only certain phones and not all?
Also, per Android Authority, the upcoming 4.4.3 for other devices fixes an issue with popping noises when playing flac audio: http://www.androidauthority.com/android-4-4-3-bug-fixes-389036/
Wonder if this was the same issue?
Click to expand...
Click to collapse
As I've said in this thread before, I've encountered the same popping noise when I was working on CyanogenMod moto_msm8960 kernel, during the backporting of caf 3.4 kernel sound related code to our 3.0 kernel.
The commit that fixes it (I've already linked it twice in this thread) is this:
https://github.com/CyanogenMod/andr...mmit/1212f2e043341016cacd6b0d93435380750bd78e
(Now I've noticed that I actually pushed it during my birthday. Do you see the dedication? )
The popping noise may not be too apparent on some devices. Every component has some tolerance, e.g. capacitors of the same nominal value don't have the exact same capacity. So the popping noise may be very subtle on some devices, while it can be rather prominent on other ones. Also, some people are less sensitive to particular sounds.
This case has nothing to do with 4.4.3 flac fixes.
It's specific to WCD9310 audio codec and the speaker amplifier used by moto_msm8960 device family.
kabaldan said:
@iBolski could you please test http://d-h.st/vre ? Thanks.
Click to expand...
Click to collapse
this worked for me, thanks!
I have the speaker pop issue as well. How exactly do I flash this through Fastboot? I don't flash it through normal recovery?
GBerg2119 said:
I have the speaker pop issue as well. How exactly do I flash this through Fastboot? I don't flash it through normal recovery?
Click to expand...
Click to collapse
Do you have an unlocked bootloader? If not you can't flash it.
Sent from my DROID RAZR HD using Tapatalk
I tried the XT926 one but it seems to either loop at the boot animation or occasionally it will come to the homescreen but say something like "com.android.phone has stopped working" in a pop up that wont go away
Edit: should add my phone is on Dhacker's CM11
(bootloader was unlocked yesterday \(^o^)/ )
Edit again:
I restored the stock ROM and flashed it again. Works fine. Not with CM11 though
Jaysp656 said:
I tried the XT926 one but it seems to either loop at the boot animation or occasionally it will come to the homescreen but say something like "com.android.phone has stopped working" in a pop up that wont go away
Edit: should add my phone is on Dhacker's CM11
(bootloader was unlocked yesterday \(^o^)/ )
Edit again:
I restored the stock ROM and flashed it again. Works fine. Not with CM11 though
Click to expand...
Click to collapse
Indeed. The boot images linked in this thread are meant only for the stock 4.4 ROM.
The fix will be included in CM11 in the future, but it can't merged right away as it is, at this point.
The msm8960dt-common kernel used by CM11 for KK bootloader is now shared by many Motorola devices (as Moto X, Droid Ultra/Maxx, in addition to newly included support for original moto_msm8960 line).
As this patch increases the audio latency, we will have to figure out the way how to make it optional first.
Not even every xt926/xt907 device needs it...
I will talk about it with David later, but I'm currently busy working on 3.4 kernel based CM11 for Photon Q which is stuck on JB bootloader as the KitKat update for Photon Q has been unfortunately canceled by Motorola. Once I'm done with Q (I need to finish it before we switch to supporting KK bootloader only by the official CM moto_msm8960 builds), I'll get back to this.
Thank You!!!!
So glad I found this thread - this popping noise has been killing me ever since the upgrade. BL was unlocked because I had missed my window to unlock before getting the patch, but that has now since been fixed with the news of the exploit re-appearing.
This fix appears to have worked for me - I was always able to tell that split second before my phone was going to make a sound because of that damn pop. Much appreciated!
Hi,
I've already asked this question on Cyanogenmod forum but it was never answered. Here, on xda-developers I see that people encountered the same problem on HTC One Mini - low microphone performance while using Cyanogenmod (see this post for example: http://forum.xda-developers.com/htc...m-cyanogenmod-12-unofficial-build-m4-t2985009 - I would like to take part in discussion but as my account has been created a minute ago I can't respond to a post in 'development' section).
Someone stated, that this is common issue of Lollipop - I'm not an expert but I wound't say so. My HTC One Mini performs really well in terms of call quality and reception. The only issue I have with it using Cyanogenmod is the microphone performance. Just after installing CM people I called complained that they don't hear me well (it didn't happen while using stock Android).
I would really like to try some of the unofficial CM12 for my One mini, but call quality (both way) is a critical thing for me. Is it possible to help fixing this issue? I would like to help. If providing any logs/statistics/other* makes sense then let me know.
Cheers,
Jakub
potential fix
http://forum.xda-developers.com/google-nexus-5/development/mod-camcorder-audio-quality-fix-t2837930 this may be a possible fix if it's the same problem as for the nexus 5. Somebody with android developing/porting knowledge should find if it is the problem occurring our One Mini and try to port if. And yes, I've tried to flash the zips from link with no luck
But there is no noise suppression option in HTC One Mini (both in stock ROM and CM).
Hey Jakub!
I am facing the same or a similar issue.
Microphone level seems to be quite low such that sometimes I have to speak quite loudly to be understood on the other side.
With my old SGS2 I also had audio issues but using a (wired) headset I had no problems. Unfortunately with One Mini, the headset's microphone does not seem to work
Did you try using a headset?
encelados said:
Hey Jakub!
I am facing the same or a similar issue.
Microphone level seems to be quite low such that sometimes I have to speak quite loudly to be understood on the other side.
With my old SGS2 I also had audio issues but using a (wired) headset I had no problems. Unfortunately with One Mini, the headset's microphone does not seem to work
Did you try using a headset?
Click to expand...
Click to collapse
I remember that I've used headset with my One mini, but I don't remember if I was using CM back then. For sure I got complains only while not using headset. So probably problem is only with internal microphone. Anyway - such issues makes the Cyanogenmod not usable for me because I know how annoying it is when you don't hear the other end well.
And to make it clear once again - I've never got complains while using stock ROM and I find call quality & reception really good on HTC One mini when using stock. With CM only microphone performance seems to be worse.
I was using stock-based InsertCoin rom until I flashed CM12.1 and at least in terms of in-call audio, I also never had a problem either with the internal or headset microphone.
My guess is that the microphone sensivity simply is too low, which can also be observed in the voice recorder. When loudly talking into the microphone, either internal or headset, quality is fine.
Unfortunately, I also cannot make any comments in the main thread yet :silly:
Downgrading HTC firmware seems to work for me. I extracted the firmware.zip from the first OTA update available for the One Mini (OTA_M4_UL_JB_50_HTC_Europe_1.31.401.1 in my case in France) and flashed my device with it. I haven't tested other firmwares yet but here is a big resource available on the net with all you need for testing (firmwares, OTAs, RUUs, etc...). As I can't post URLs with my newbie status you can find it by typing "downloads for HTC One Mini by Krocko - Android File Host" in Google.