I just received a refurbished Samsung T989 and have experienced to major issues.
Since I've received the phone, I've done the following.
Root the device
Performed a back up with Nandroid
Installed custom roms
The custom roms I've tried in clude Cyanogen mod 9.1, MIUI, and Paranoid Android.
They all give me the same problem. During a call there would either be no sound from either the S2 and the other phone.
Otherwise, when the call does properly connect, the mic on the T989 would be very soft, so soft that the other end cannot make out what is being said.
I've tried restoring back to the stock rom (Telus) and the soft mic issue would disappear. However, when I attempt to switch off the phone or reset it, it would do neither. The lights on the capacitive buttons would remain on after the phone LCD screen turns off.
I would greatly appreciate a solution to the former problem, so I can just stick with a custom rom.
Thanks
Look in the development section, there is a sticky with links to all the flashable radios for T989. Do a factory reset, wipe /system, clear both caches, flash a ROM properly, and then flash a new radio. See if that fixes your problem.
arcsine said:
Look in the development section, there is a sticky with links to all the flashable radios for T989. Do a factory reset, wipe /system, clear both caches, flash a ROM properly, and then flash a new radio. See if that fixes your problem.
Click to expand...
Click to collapse
Thank you for the reply. I beleive I have flashed a rom properly and have flashed the radio
SGH-T989D TLLE4 (Telus).
I performed
The operations in this order:
Wipe data/factory reset
Format System
Flashed Dark Side Super Wipe EXT 4.zip
Flashed Radio
Flashed Rom
This did not fix my problem. Enabling Noise suppression mitigates the problem however it is not fully fixed.
Related
I noticed that in every single ROM thread it says to wipe data and factory reset before flashing..
but one time i forgot to do it and just wiped cache then flashed a new ROM, and so on, and so on..
After i booted my phone i noticed that all my data and settings was exactly how it was before i flashed the new ROM..
i have done it this way with Juggernaut 5.0 and SlickMod 3.6 RC1 and never experienced a bug or anything unusual by doing it this way.. (although every time i tried an ICS ROM I followed the instructions perfectly)
it sure saved me a lot of time setting up my phone again
my question is ... has anyone seen bad results by doing it this way?
Theres more to it than that. The problems arise when you flash system data on top of another rom's system data. The ROM maker may have put tweaks in that mixed with another ROM's tweaks could cause unwanted effects. For example, TDJ builds his roms and kernal specifically for his roms, and states if you use another kernal his tweaks wont work.
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
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.
Hello everybody,
I'm running the latest stock Android 4.3 on a rooted Note 2 with CWM installed. What happens is that when I use the phone to make or receive phone calls (streaming music is ok instead) in my car (but I experienced the same problem in another car) the Bluetooth all of a sudden goes off and I need to either turn the screen on or toggle the bluetooth button.
Any idea on how to fix it?
Thank you,
Davide
Hi! Have you tried a Factory Reset? It will wipe your phone clean, so back-up your stuff first. Come back after with the results, maybe this will fix the Bluetooth issue.
Ruwin said:
Hi! Have you tried a Factory Reset? It will wipe your phone clean, so back-up your stuff first. Come back after with the results, maybe this will fix the Bluetooth issue.
Click to expand...
Click to collapse
Actually I wanted to avoid that...
Okay, so let's try something else first and see where it leads: Go to CWM and make a Nand Backup. Then wipe your Cache and Dalvik Cache. Reboot and test. Most probably this will not solve, but it's worth trying. Get back in CWM and this time wipe Data + Dalvik + Cache (Factory Reset basically). Boot and test. If not working, you can restore the Nand Backup to get back your apps and data. If it is working, well, lucky you, you'll have a great time installing all your apps back
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.