Related
Info in my sig. I was on a previous version of CM (4.2.12.2, iirc) and had no problems. It did run sluggish, but was guessing it was due to my class 2 sd card and using swap/ext/fat32 on it.
I repartitioned my card to all fat32 and loaded 4.2.13 yesterday. It runs much faster, much more responsive than before.
Now, when on a call, it sounds like it's breaking up, like I have bad signal every once in a while. When it would do it, I checked and had 3G and 3-4 bars. I was at my house, where I've never had problems before. This happened both with just the my3g and on a BT headset. Initially I thought it was where I was in the house, but it happened no matter where I went.
I searched and found a thread titled "Background noise" talking about improved call quality. I can't post a link because I'm a no0b, but here's the info, with attached filename Audio-mic-gain-fix.zip:
scheng said:
Is there any way to reduce the background noise of the Magic on the voice call? Will it be improved by updating the latest radio?
Click to expand...
Click to collapse
sombionix said:
You can try this. It has improved my call quality a lot. Follow these instructions using terminal app.
*unzip the files using astro or file manager of your choice*
Open terminal emulator
Type - su (enter)
Type - mount -o remount,rw /dev/block/mtdblock0 /system
Type - mkdir /sdcard/mic
Type - cp /system/etc/* /sdcard/mic
Type - cp /sdcard/download/*.csv /system/etc/ (or whatever directory you unzipped to)
Type - reboot
Click to expand...
Click to collapse
sombionix said:
Are you rooted with a modified ROM? If so, many people have complained about poor call quality, distortion, etc. This file has fixed this problem in many cases. The *'s stand for 'files'. If you call out an * in a command it pulls all files in that directory. However, another example would be *.csv, which would only pull .csv files, or whatever file extension you put after the *. Sorry, hopefully that makes sense.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Since the file is named audio mic gain fix, it seems this is more for the mic gain, not the ear speaker.
Am I having the problem this is intended to fix?
Thx!
If you're having a problem with your ear piece (speaker), I don't think the mic-gain file will help with your situation. The mic-gain file was intended to improve call quality via the microphone. Some users were claiming that the people they were calling said they could hardly hear them or that there was distortion and background noise.
I don't believe there have been any reported issues with the ear piece using any Cyanogen ROMS, but I could be wrong. Sounds more like a hardware issue. One way to test is to downgrade to a previous ROM and see if you still have the issue. If so, more than likely, its a hardware problem.
Good luck!
That's kinda what I figured. I'll continue using it to see if I still have probs. If so, I'll try a different ROM.
thx for the infoz.
This might not help but I had the same problem when updating from 4.2.5 to 4.2.13. It was fine on 4.2.5 and had a little background noise frequently. But once I upgraded to 4.2.13 calls were horrible all the time, the person could barely hear me. I decided to do a warranty exchange and unrooted it. Calls were fine once I was on stock 1.6, still had some background noise but not on all calls.
Got my replacement the next day, rooted straight to 4.2.13 and had no problems cept for the background noises every now and then.
I have a MyTouch3G as well.
Weirdkid said:
This might not help but I had the same problem when updating from 4.2.5 to 4.2.13. It was fine on 4.2.5 and had a little background noise frequently. But once I upgraded to 4.2.13 calls were horrible all the time, the person could barely hear me. I decided to do a warranty exchange and unrooted it. Calls were fine once I was on stock 1.6, still had some background noise but not on all calls.
Got my replacement the next day, rooted straight to 4.2.13 and had no problems cept for the background noises every now and then.
I have a MyTouch3G as well.
Click to expand...
Click to collapse
Maybe I'm misunderstanding, but are you saying that you exchanged your phone to fix your problem? I highly doubt that the Cyanogen ROM you had installed caused a hardware problem. Could have possibly caused a glitch if you didn't install it correctly. However, you should have just wiped everything and tried again. Or, if you were really feeling up to it, started from scratch by unrooting in fastboot with the SAPPIMG.nbh, then rooting again with the recovery image and ROM of your choice.
fwiw, I did a wipe, reformated the sdcard, and a fresh install of CM 4.2.13.
I have a feeling it was just poor reception at the time. I don't talk on the phone that often, but used it today for about 5 mins and it seemed fine. I was riding in a car and background noise was loud (my buddies arguing over steroids & McGwire, lol), but the guy on the other end had no probs hearing me.
Glad to hear you got it fixed.
Sorry, I guess that was out of context. That was @Weirdkid, stating that I didn't do an upgrade like he did. I haven't touched it since yesterday, I wanted to let roll to see how it plays out.
sombionix said:
Maybe I'm misunderstanding, but are you saying that you exchanged your phone to fix your problem? I highly doubt that the Cyanogen ROM you had installed caused a hardware problem. Could have possibly caused a glitch if you didn't install it correctly. However, you should have just wiped everything and tried again. Or, if you were really feeling up to it, started from scratch by unrooting in fastboot with the SAPPIMG.nbh, then rooting again with the recovery image and ROM of your choice.
Click to expand...
Click to collapse
Not quite, I was already getting static every now and then even before root(I thought I could live with it). It was just a little glitch I guess and that pushed me to get an exchange. After the unroot and back to Donut, the glitch with all calls getting low quality was gone but still getting minor static noise every now and then(just like before). Sorry for the confusion.
Okay, so I continued to have poor call quality and 3 calls were dropped. I went back, did a full wipe, no swap/ext, and reloaded CM4.2.13 and had the exact same problems.
I decided to load Dwang's rom and no longer have the problem of dropped calls and/or poor call quality.
cougar694u said:
Okay, so I continued to have poor call quality and 3 calls were dropped. I went back, did a full wipe, no swap/ext, and reloaded CM4.2.13 and had the exact same problems.
I decided to load Dwang's rom and no longer have the problem of dropped calls and/or poor call quality.
Click to expand...
Click to collapse
Yeah, I stopped using Cyan's ROM when the 4.2.10 release came out. Great ROM, just seemed to have increasing issues after 4.2.9. You should try the Super D rom. Fastest and most stable ROM I've run, hands down.
http://forum.xda-developers.com/showthread.php?t=613809
Thanks for the the recommendation, I was looking at that one, but haven't changed my SPL. No reason, just haven't ventured down that road yet.
I've been looking at the 10mb ram hack, searching for pros/cons, but just see people using it and no full explanation of it.
Is there any real benefit to it, and what does it actually do?
cougar694u said:
Thanks for the the recommendation, I was looking at that one, but haven't changed my SPL. No reason, just haven't ventured down that road yet.
I've been looking at the 10mb ram hack, searching for pros/cons, but just see people using it and no full explanation of it.
Is there any real benefit to it, and what does it actually do?
Click to expand...
Click to collapse
Not a problem. Also, if you have a mt3g, you don't need to upgrade your SPL to run the Super D rom. Aside from that, just make sure you have the correct radio, then do a full wipe and flash the ROM.
In regards to the 10mb ram hack, it definitely increases system speed and performance. So that would be your 'pro'. However, the ram hack is created by pulling 10mb of ram that would normally be used for graphical processes, and instead applies it to your operating system. The con would be a decrease in 3d game performance. So, if you play a lot of 3d games, then I wouldn't recommend the 10mb ram hack. If you don't, then use it. Currently, the only Super D rom you can download that doesn't have the ram hack is the 1.6.6 beta, which as of right now is fairly stable. However, If you are considering switching to this rom, just wait a couple days, the developer has announced that he is releasing the 1.7 stable version this week. I'm assuming he will have two separate downloads. One with the ram hack, and one without.
Btw, I didn't see your phone setup before my last post. You DO have the correct radio to run the Super D rom. So, all you have to do is a full wipe and flash the rom.
Nice! I forgot I was reading the page in the Dream/G1 section...I got this one how I like it, so I'll roll with it a few days and keep an eye out for Super D 1.7.
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have the exact same issue. Very strange and rare. So the occasional reboot fixes it but annoying at times.
sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have come across the same today on the 2.05 revision. It started this afternoon, since I have had to reboot 5 times. The latest was only about an hour or so apart. When I make calls, I do not hear any sound, no ring tone, not the other person. Also adjusting the ring volume with the volume keys does not make any sounds. Even on my bluetooth headset I do not get any sound. No rings on incoming calls, no speaker phone ... absolutely nothing. This has become a huge issue an I'm going back to my 1.5 image at this point.
Actually, reading through threads about both ROMS, I'd say there are quite a few people starting to encounter this problem...has anyone with this issue gone back to 1.5 to see if it goes away then?
S
just a note, the people on the other end when making a call can't hear anything either but the call does go through. i had to use the g/f BB to call and my buddy thought it was his phone. I'm so mad because I thought this was a done deal but looks like I gotta go back to 1.5
+1 same issue on Fresh 2.0d
When it happened it affected incoming and outgoing calls, earpiece, speakerphone, microphone -- the works. Person on other end could not hear anything either. Fixed with reboot.
me and my coworker both have this issue with our heroes, he couldn't stand it and went back to fresh 1.1 and it went away
I still get the issue once a day, full reboot solves the issue.
I cant seem to pinpoint when it happens, it just happens.
it started with the first fresh 2.0 and then continued with every 2.1 i have tried
i couldn't find a post in this forum relating to a fix for this, unless someone can prove me me wrong and i hope someone does
+1 same issue on Fresh 2.0d and DCv1
Same as others, a reboot will fix it but by that point you just missed a call.
Or if the sound goes out you might miss a few calls from not being able to hear the phone ring.
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Avalaunchmods said:
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Click to expand...
Click to collapse
Thanks. You're speaking greek to me as far as the boot.img and all that but if you have an idea of what's going on I'm all ears on fixing it. If there is any sort of info we can provide just let us know.
Im here to help as well, If you need any testers I am willing to do what ever is needed! Anything to fix this problem!
Related?
10chars
http://forum.xda-developers.com/showthread.php?t=657244
Click to expand...
Click to collapse
DroidDhakan said:
Related?
10chars
Click to expand...
Click to collapse
Of course it is,its the fix(hopefully) for it
Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).
Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.
What carrier are you on?
this happens to me too.its so annoying. im on att
Can't find the thread but it was pretty long.
nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.
This sounds like an att problem not a nrsux one problem
I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.
I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One
Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.
I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.
Sounds more like a network issue than a hardware issue, IMO
This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.
Ok I'm not a complete newb but I can't figure this out and its been driving me nuts for over a week now...
SGH-1337M (Rogers)
Up until last week I'd been running the nightly builds of CyanogenMod and loving it, the phone was fast had lots of functionality then I did a nightly upgrade and my phone stopped working. Incoming calls would ring but when I picked up the call I couldn't hear the caller and they couldn't hear me. After much frustration I ended up flashing back to stock. This fixed the problem but the phone was useless as far as I was concerned for everything but making phone calls. It was laggy, I couldn't listen to music (it was staticy) and just generally full of all of the extraneous crud that Rogers seemed to think I should have on my phone. (I honestly couldn't suggest the phone to anyone who was going to run it as a stock device if this was how it came out of the box!)
Now On Sunday I decided to try again and after setting everything back to defaults I reloaded Cyanogen and at first it seemed that things were working properly... until last night. Again I got a call and when I answered it there was no audio.
I can't figure it out, I'm running the correct radio now after flashing to stock (I337MVLUAMG1) but I just can't seem to get it to work and stay working. Besides Cyanogen I'm only running two other "root" apps Fantastic audio installer and AdAway.
Any suggestions would be great, I just can't go back to stock on this phone...
Any ideas?
I think I have the problem figured out...
Seems like it was a combination of a bad build of CM and the "Fantastic Audio Installer"
Beware of compatibility issues with apps like this...
Good morning everyone! Since I've moved from stock I've has an issue with the MIC during calls where the person on the other end will not be able to hear me. I would have to put the phone on speaker and scream into the MIC for them to hear me. Disabling google voice or toggling speaker would not fix the issue for me. Today I was looking through the modules on Magisk when I saw one called "Android MIC fix." After downloading, installing and restarting the phone I made a call and walla. The recipient was able to hear me clearly. Needless to say I was very much excited. So for those with the MIC issue I recommend trying out this module.
Thank you for posting this. I'm desperate for a mic fix. I've just installed it, but will not be back in an area with a cell phone signal until tomorrow. I'll post in a day or two whether it seem to have fixed my mic issues. Magisk will not pass SafetyNet check, but it might be worth giving up some apps, if it can fix the issiue with people not hearing me on a call until I turn speakerphone on and off.
celticchrys said:
Thank you for posting this. I'm desperate for a mic fix. I've just installed it, but will not be back in an area with a cell phone signal until tomorrow. I'll post in a day or two whether it seem to have fixed my mic issues. Magisk will not pass SafetyNet check, but it might be worth giving up some apps, if it can fix the issiue with people not hearing me on a call until I turn speakerphone on and off.
Click to expand...
Click to collapse
I think Magisk passes safetynet again. there are some XDA articles about the new beta. I didn't try though
Choose an username... said:
I think Magisk passes safetynet again. there are some XDA articles about the new beta. I didn't try though
Click to expand...
Click to collapse
After installing the Magisk 13 beta, it does pass SafetyNet check for me. This is where to download the beta, of course, but not for anyone who is new to this stuff, of course (Betas are always at your own risk).
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
As for the mic issue, more to come in a day or two, once I'm in an area with cellular coverage again..
This fix didn't work for me.
This fix sounds promising, since I've found that when the mic seems to be non-functional, that the other party on the line can hear me if I yell at the phone. However, despite getting Android pay working on B25 with Magisk 13, it just crashes when trying to install modules. Anyone else have any luck with it?
After using the module some more I found that, while yes, I was able to use the headset, the quality of the call was horrendous. So I disabled the module. I'll just have to live with using speaker until a permanent fix is found
This also didn't work for me. I kept having further problems with Magisk beta, so I've removed it for now, and I'm hoping for a better patch, before shelling out for a new phone.
As for B06 nougat, turkey (a2017g) the issue feels like solved for me. I've done about 40-50 callings without any doubts. Also no need to turn on/off loudspeaker. "Ok Google" from any screen turned on so imo - issue fixed.
I didn't faced any mic issue..... I just tuned off the OK Google even on 7.0.1 till then everything is perfect
Laleka said:
I didn't faced any mic issue..... I just tuned off the OK Google even on 7.0.1 till then everything is perfect
Click to expand...
Click to collapse
Yeah because the issue occur when you have "ok Google" turned on from any screen and now you can have it turned on without any mic troubles in call.
Hey everyone, hope all is well.
I found a fix for my axon. If you don't want to read my trial and errors and just want the fix, scroll to the bottom.
I bought an axon 7 off eBay. From day 1 people were saying they couldn't hear me very well. I thought it was cell service.
It seemed to slowly got worse.
It got to the point where people couldn't hear me at all.
I downloaded an app to locate cell towers and service range. Service didn't seem too bad...
Found forums like this one, tried talking on speakerphone. It worked, but people said it was still hard to hear me, cutting in and out, etc. Turned off mic access for ok Google and eventually EVERYTHING else.
Deleted apps even... No fix.
Eventually went to a place I knew had good cell service, called someone, and they couldn't hear me at all! Def not mic access, def not service...
Axons warranty doesn't work for resold phones... The speakers and Dolby..I didn't want to go back to a Samsung or whatever..
That's when I started looking for hardware fixes.
I decided to do a Google search one last time before starting down that road, but looked at videos this time.
And I found a fix!!!!!!
youtu.be/KNGMM-H0oxc
So simple.
So going back to the forums I read before and posting my fix. Hopefully it helps others.
So happy!