Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Could have been a bad flash / download
Did you check the md5sum?
leftcranium said:
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Click to expand...
Click to collapse
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
topherk said:
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
Click to expand...
Click to collapse
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
leftcranium said:
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
Click to expand...
Click to collapse
Yeah, a full system wipe might be the ticket. Let us know if that works.
I'm Back Baby
I tried a system wipe and a rooted stock rom. This didn't work. I then tried the LJ7_Stock_with_count_reset16 rom and my sound was ok. I cleaned out the mic hole with a pin and bam sound was like normal. I'm now back on TPRGS3.14 and everything is good. I think I had 2 issues but possibly only 1. messed up mic from multiple flashes and crap in the mic hole. I guess checking for a physical problem even as small as a mic debris is an easy first step.
thanks for the suggestions
Related
ROM: Intergalactic 2.2 (AT&T TouchWiz JB 4.1.1)
short story- for some reason, after a song finishes playing, the next song will route through to the phone speakers even though i have headphones/aux cable plugged in.
long story- i was going on a few months using AOSP based JB ROMs (CM10, AOKP, etc). but when AT&T finally released the official JB, i decided to switch back to TouchWiz (but on the custom ROM side). on Jan.1, i started with LoserROM v.1.5.1, and that's when this first started happening. on that ROM, when a song ends, it switches to phone speakers, i would get a dialog saying "Unfortunately, settings has closed." luckily, version 1.6 came out soon after, so i tried that and it still happened.
so i decided to switch to Intergalactic v.2.2 yesterday. but now, it's kinda acting the same. the same switching to phone speakers occurs, but i'm not getting the dialog box anymore.
other stuff- before i started using AOSP based ROMs, i tried out the ports of JB TouchWiz (T-Mobile ports, Sprint ports, AT&T GNote2 ports), but this never happened before.
testing- this happens on both the stock/TouchWiz Music Player app and Google Play Music app. also, both ROMs were flashed after a clean wipe.
temp fix (kinda)- if i skip to the next track, it automatically switches back to the headphones/aux cable. but if i press Previous/restart the same track, it still plays through the phone speakers.
i found these other threads, but no resolution was found:
* http://forum.xda-developers.com/showthread.php?t=2093243
* http://forum.xda-developers.com/showthread.php?t=2090006
i don't want to switch back to AOSP. does anyone have any suggestions?
mrhomiec said:
ROM: Intergalactic 2.2 (AT&T TouchWiz JB 4.1.1)
short story- for some reason, after a song finishes playing, the next song will route through to the phone speakers even though i have headphones/aux cable plugged in.
long story- i was going on a few months using AOSP based JB ROMs (CM10, AOKP, etc). but when AT&T finally released the official JB, i decided to switch back to TouchWiz. on Jan.1, i started with LoserROM v.1.5.1, and that's when this first started happening. on that ROM, when a song ends, it switches to phone speakers, i would get a dialog saying "Unfortunately, settings has closed." luckily, version 1.6 came out soon after, so i tried that and it still happened.
so i decided to switch to Intergalactic v.2.2 yesterday. but now, it's kinda acting the same. the same switching to phone speakers occurs, but i'm not getting the dialog box anymore.
other stuff- before i started using AOSP based ROMs, i tried out the ports of JB TouchWiz (T-Mobile ports, Sprint ports, AT&T GNote2 ports), but this never happened before.
testing- this happens on both the stock/TouchWiz Music Player app and Google Play Music app.
temp fix (kinda)- if i skip to the next track, it automatically switches back to the headphones/aux cable. but if i press Previous/restart the same track, it still plays through the phone speakers.
i found these other threads, but no resolution was found:
* http://forum.xda-developers.com/showthread.php?t=2093243
* http://forum.xda-developers.com/showthread.php?t=2090006
i don't want to switch back to AOSP. does anyone have any suggestions?
Click to expand...
Click to collapse
This is ROM related, I believe you should post this in his thread with a logcat.
i thought that too, but what are the chances this happening on 2 separate ROMs?
i originally had this posted on LoserROM's thread when i was using that ROM, but the dev never heard of this before.
mrhomiec said:
i thought that too, but what are the chances this happening on 2 separate ROMs?
i originally had this posted on LoserROM's thread, but the dev never heard of this before.
Click to expand...
Click to collapse
that's why you need a logcat. Mentionning the issue doesn't do much good if they can't reproduce it. Did you try it after doing a full wipe (clean flash)?
yep. clean wipe on both ROMs, same issues.
i still figured i'd post here, especially since i found those threads with the same issue while using a custom ROM.
mrhomiec said:
yep. clean wipe on both ROMs, same issues.
i still figured i'd post here, especially since i found those threads with the same issue while using a custom ROM.
Click to expand...
Click to collapse
It's odd that this only happens on TW ROMs but kinda cuts out the hardware issue.
If you listen to a lot of music, you might have to flash a AOSP ROM for now until the issue is fixed but before doing so, I would still try to get a logcat of the issue so the Devs can look at it and *hopefully* find a fix.
i remember reading one time that someone suggested about doing a clean install twice to fix something. i wonder if that would be something to consider in this case?
and if so, that would be wipe cache/factory install, wipe cache, wipe dalvik, format /system. then do it again. then flash ROM, then wipe cache, wipe dalvik?
mrhomiec said:
i remember reading one time that someone suggested about doing a clean install twice to fix something. i wonder if that would be something to consider in this case?
and if so, that would be wipe cache/factory install, wipe cache, wipe dalvik, format /system. then do it again. then flash ROM, then wipe cache, wipe dalvik?
Click to expand...
Click to collapse
You can always try it. But once done, it should be done. Did you have this problem when you flashed stock JB?
never tried stock JB. i'll try that too. i saw a thread for a flashable one.
mrhomiec said:
never tried stock JB. i'll try that too. i saw a thread for a flashable one.
Click to expand...
Click to collapse
Oh I miss understood you. In the OP, you mentioned it was finally released and took for granted that you flashed it.
But you could flash the stock rooted JB and start from there.
my bad. edited first post for clarification.
mrhomiec said:
ROM: Intergalactic 2.2 (AT&T TouchWiz JB 4.1.1)
short story- for some reason, after a song finishes playing, the next song will route through to the phone speakers even though i have headphones/aux cable plugged in.
long story- i was going on a few months using AOSP based JB ROMs (CM10, AOKP, etc). but when AT&T finally released the official JB, i decided to switch back to TouchWiz (but on the custom ROM side). on Jan.1, i started with LoserROM v.1.5.1, and that's when this first started happening. on that ROM, when a song ends, it switches to phone speakers, i would get a dialog saying "Unfortunately, settings has closed." luckily, version 1.6 came out soon after, so i tried that and it still happened.
so i decided to switch to Intergalactic v.2.2 yesterday. but now, it's kinda acting the same. the same switching to phone speakers occurs, but i'm not getting the dialog box anymore.
other stuff- before i started using AOSP based ROMs, i tried out the ports of JB TouchWiz (T-Mobile ports, Sprint ports, AT&T GNote2 ports), but this never happened before.
Im actually having the same problem with my Galaxy S3, mine is the Verizon version running 4.1.1 jb. The problem popped up right after the update. My phone isnt even rooted, ive meant to get around to it but just havent. I wouldnt say your roms are the problem.
testing- this happens on both the stock/TouchWiz Music Player app and Google Play Music app. also, both ROMs were flashed after a clean wipe.
temp fix (kinda)- if i skip to the next track, it automatically switches back to the headphones/aux cable. but if i press Previous/restart the same track, it still plays through the phone speakers.
i found these other threads, but no resolution was found:
* http://forum.xda-developers.com/showthread.php?t=2093243
* http://forum.xda-developers.com/showthread.php?t=2090006
i don't want to switch back to AOSP. does anyone have any suggestions?
Click to expand...
Click to collapse
Im having the same problem on my Verizon Galaxy S3 running 4.1.1 and its not rooted.
[UPDATE]
so i tried to clean wipe twice, flash the latest Intergalactic (v.2.3), wipe cache, wipe dalvik, reboot.
still no success.
the Intergalactic dev is aware of this issue. and especially since the above user is getting this on a non-rooted phone, so i'm guessing it's a TouchWiz thing.
mrhomiec said:
[UPDATE]
so i tried to clean wipe twice, flash the latest Intergalactic (v.2.3), wipe cache, wipe dalvik, reboot.
still no success.
the Intergalactic dev is aware of this issue. and especially since the above user is getting this on a non-rooted phone, so i'm guessing it's a TouchWiz thing.
Click to expand...
Click to collapse
Yep. Most likely is a TW base thing. Expect it to be fix in 4.2.2
hi, after flashing any aosp rom (slim rom, cm, paranoid, ...) my microphone is dead. i don't hear the other caller and he can't hear me. the microphone is fine because when i flash a tw rom afterwards everything works fine again. interestingly the mic works after the first restart after the flashing. as soon as i restart for a second time the mic is dead.
it does not matter wheater i flash with clockwork mod or twrp. i always make a full wipe (cache, dalvik cache, factory reset, internal memory, rom; basically all reset options twrp offers) before installing the new rom. i install the new rom (any aosp rom) with a new kernel that fits the android number and the correct gapps. sometimes i used the old kernel but it makes no difference regarding the mic.
i don't think i make anything wrong during the process because everything else works just fine. so far i always ticked the box to restore data with my google account, can this be the problem.
any clues where i go wrong? i hope someone can help me with that problem because i love my note 2 but i hate tw.
thanks in advance.
Hi, my name is Daniel and I am in serious need of some help. I have a rooted T999 for T-Mobile. TWRP recover installed. I am running into some frankly strange issues. If I am in a call and I am not using the speaker, no one is able to hear me. If I am in a call, they can hear me but with occasional clicking sounds and very bad quality. I tried re installing the baseband but it does nothing. Can anyone help me please?
Baseband version: T999UVEMJC
Thank you!
What Rom and Kernel do you have ? If on Stock then can you do factory reset ?
I am running complete stock. The only thing I put was TWRP 2.6.3 I believe. I have factory reset a few times to no effect.
If you are not on Touchwiz Stock 4.3, then please switch the Baseband to LJC.
Will that solve the mic not working without speaker?
Yes I suspect it might.
Ok, I downloaded the correct basebadnd you told me and flashed it through TWRP. I booted and it showed no signal. Then I went into setting, networks, and mobile networks and it said please insert SIM card. I cleared cache and installed the old baseband and it works but in the same manner.
I don't think you mentioned your Current Rom. Please also provide Kernel.
I have taken a screens hot and attached it. Should help answer your question, I hope
Please if possible, try a AOSP Rom instead of Stock Touchwiz. At the least it will rule out hardware issues. If that's not an option, and SELinux is enforcing, I don't know if you can change.
Yeah, I tried a AOSP rom and no dice. I was looking online and saw that I am actually not the only one. Other people who took the 4.3 update seem to be having this issue.
The AOSP Rom took out the TW Rom as a culprit. If you still have an issue the probably a hardware issue.
Hey guys so I was looking and it turns out I'm more clueless than even I originally suspected. The ROM I originally flashed was based off of Touchwiz. What ROM should I be flashing because I cannot seem to find one that is aosp to the core?
The one I was going to try was Dirty Unicorn but I cannot tell if that even is what I should be trying.
Try Liquidsmooth, Pacman, SlimBean and so on. There are a number of quality Roms out there. I only suggested 3 that first popped into mind
Alright. I'll try those.
I have been looking for a solution to this problem for weeks and have found nothing that will fix it.
I am currently on CM11-M3, and have had the problem since 10.2. No matter what ringtone I select it will not play during an incoming call.
I have been testing with wheresmycellphone.com. Ehen a call comes in the phone will vibrate once and very rarely the ringtone will play for a fraction of a second, but most of the time there is no sound. I have noticed that the mute icon (speaker with a line through it) flashes in the notification area briefly the second the phone starts ringing.
Does it be behave the same way on other custom and stock ROMs?
Are you clean flashing?
audit13 said:
Does it be behave the same way on other custom and stock ROMs?
Are you clean flashing?
Click to expand...
Click to collapse
I dirty flashed 10.2 from 10.1, I did a clean install when I switched to CM11, every flash since has been with a cache/dalvik wipe. I have not yet tried a rom beyond CM.
You should try another ROM, even if it is based on CM11 to see what happens.
audit13 said:
You should try another ROM, even if it is based on CM11 to see what happens.
Click to expand...
Click to collapse
I will when I get a moment. I need to be accessible for work right now so I can't risk any excessive off time just yet.
zero|fade said:
I will when I get a moment. I need to be accessible for work right now so I can't risk any excessive off time just yet.
Click to expand...
Click to collapse
Well, I finally got off my ass to try fixing this again. I was going to try installing SlimKat, and as prep I wiped cache, dalvik and then factory reset. I rebooted to try receiving a call before I started work on flashing the rom and the phone now rings fine. I have no idea what changed, I had tried a factory reset on M2 and it didn't fix the issue. This is the first factory reset I applied to M3 though.
I am currently running Cyanogenmod 10.2.1 on my Sprint GS3. I am running into a few issues, of which I have had over many builds. For one, my phone will random reboot when using it, while it happens rarely, it seems to do it at the most inconvenient times and I am left waiting for it to reboot for no reason. The next, and definitely most annoying glitch, is the "disconnect reconnect" issue with PCs. When connected to a PC, it repeatedly disconnects and reconnects and never stops this loop. I hear the disconnect/connect sound over and over until I actually disconnect the phone. Because of this, I am unable to add new music, photos, etc. At first I thought it was just the current build, but after updating to 10.2.1 from 10.2.0, and so on, nothing has really changed. I'm not sure what to do at this point other than just go back to the factory ROM. If any of you have any idea why this may be happening, let me know. Thanks in advanced.
hotelmariofan said:
I am currently running Cyanogenmod 10.2.1 on my Sprint GS3. I am running into a few issues, of which I have had over many builds. For one, my phone will random reboot when using it, while it happens rarely, it seems to do it at the most inconvenient times and I am left waiting for it to reboot for no reason. The next, and definitely most annoying glitch, is the "disconnect reconnect" issue with PCs. When connected to a PC, it repeatedly disconnects and reconnects and never stops this loop. I hear the disconnect/connect sound over and over until I actually disconnect the phone. Because of this, I am unable to add new music, photos, etc. At first I thought it was just the current build, but after updating to 10.2.1 from 10.2.0, and so on, nothing has really changed. I'm not sure what to do at this point other than just go back to the factory ROM. If any of you have any idea why this may be happening, let me know. Thanks in advanced.
Click to expand...
Click to collapse
That's an interesting experience, which I haven't had so far.
Did you dirty flash the rom or completely wiped your phone before installing?
Which modem version are you on?
Robbie Doo said:
That's an interesting experience, which I haven't had so far.
Did you dirty flash the rom or completely wiped your phone before installing?
Which modem version are you on?
Click to expand...
Click to collapse
I don't format the phone between cyanogenmod updates, but I do when installing a completely different ROM (factory -> Cyanogenmod). As far as the modem version goes, as of now, I am running LJ7. I believe that was on there by default, although I may be wrong. I did try others before (If I remember right) installing the original. I tend to have horrible reception in KC (everywhere actually), so I was hoping to fix it that way.
hotelmariofan said:
I don't format the phone between cyanogenmod updates, but I do when installing a completely different ROM (factory -> Cyanogenmod). As far as the modem version goes, as of now, I am running LJ7. I believe that was on there by default, although I may be wrong. I did try others before (If I remember right) installing the original. I tend to have horrible reception in KC (everywhere actually), so I was hoping to fix it that way.
Click to expand...
Click to collapse
You're right, there's no need for completely formatting the phone between nightlies. However, your modem seems to be an older version. I believe the CM 10 based on MD4 and the CM 11 is based on MK3. You can verify this in their respective forums though.
My suggestion would be to download the latest modem and the CM 11 onto an external card. Format your phone completely. Install the modem then install the CM 11 + KK Gapps.
Let us know how it went if you go through it.