yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ClubOK:
When I am called by my friend or I call to it... He doesn't hear me. If to make mute/unmute - аll becomes normal. It happens at any call.

Sorry for my English.
[Vibrant Android Development] Binary100100:
So what we need to know is what is unique in your situation. What radio are you using? Because I've tried to replicate this too and only failed. I called myself from one cell phone to another over a dozen times and have made/received over a fifty calls and I haven't had this problem once.
[Vibrant Android Development] ori2:
In one of the previous pages, someone said the problem occurs when the call is made from other cell phones and landline didn't have those problems. I experienced that I can hear others but they cannot hear me in calling between cell phones.

The problem might be solved in latest builds but in twenties build, I always faced it. Only mute/unmute could make the others hear me.

So why don't you just try some cell-to-cell calls? I hope this helps for reproducing the problem.

test environment

- t-mobile to t-mobile

- t-mobile to at&t

- modems kb1, kb5, and as it is

- no custom kernels

- no modifications
[Vibrant Android Development] movieaddict:
ive been doing nightlies since #4 and i pretty much do every one as im a flashing addict. And i guess im one of the lucky ones because ive never had this problem, Its got to be certain situations maybe the reception or area they live in? just taking a guess?
[Vibrant Android Development] philow:
This happens anytime someone calls me. If I call out from my Vibrant no issue. Steps to reproduce:

Have someone call you or call your vibrant yourself

Say hello the calling party can here you fine

Keep talking and the calling party will have a hard time hearing you like you are in a tunnel

Press mute then immediatly press unmute (I have heard that pressing speaker then pressing speaker again works as well)

Talk to the calling party and they hear you fine

Hope this helps.
[Vibrant Android Development] Binary100100:
I cannot replicate it at all.

Here's what I've tried:

T-mobile to T-mobile is fine.

T-mobile to VZ is fine.

T-mobile to Nextel is fine.

using kb5 and whatever the roms come with.

Tested with both Neo 7, Neo 9 and standard kernel.
[Vibrant Android Development] tripleintegral:
My 2 cents: I am in India on Vodafone and also affected. So it is either:

1. Not affected by the operator.

2. Whatever is causing this is common for Vodafone and t Mobile in which case this does not help much.

I would like to think it is 1 but I can't be sure.
[Vibrant Android Development] michaelh99:
I suspect it's a hardware specific problem. I've flashed 15, 29, 33 and never had the problem. my flashes have always been stock
[Vibrant Android Development] atinm:
I just did some cell to cell calls too - is the issue a 'robot' voice like sound? I seem to get that now and then, but it doesn't go away with mute/unmute or anything and isn't consistent so wondering if that is just reception where I am at the moment (sitting between at least 4 computers, in a building . . .).

Of course, I am using KA7 modem and am on AT&T SIM as I don't have a t-mobile sim card and I think my device has been in the ocean or something before it was sent to me (if the sand inside the device is any indication ;) ).
[Vibrant Android Development] nedlog:
Just flashed build 35; no issues, running smoothly. I've never encountered the mute/unmute issue either, and also have been uploading since build 7 or 8. Build 20 was the only nightmare.
[Vibrant Android Development] tripleintegral:
Nope. If you're reproducing this correctly, you should have a pretty hard time making out what's being said. It should be kind of faint, like you're trapped in a well or a tunnel. Also, I'm on kb5.
[Vibrant Android Development] Jasonhunterx:
I am having external SD mount problem an I am on GB boot loader should I go back to froyo to fix that?
[Vibrant Android Development] chev:
This has been happening me also. I have to mute and unmute. Tried to do some tests also and always need to mute and unmute all the time. Btw im from the philippines.

Tests done:

landline to mobile(cm7)

Mobile(cm7) to landline

Mobile(nokia/htc) to mobile(cm7)

Mobile(cm7) to mobile(nokia/htc)

all of this tests require me to mute and unmute.
[Vibrant Android Development] atinm:
What modem?
[Vibrant Android Development] peiqijiang@qq.com:
i tried KA7 KB5

both need mute unmute
[Vibrant Android Development] peiqijiang@qq.com:
3G need mute unmute

2G use modern JL3 is fine

if 3G use JL3 cant get 3G signal

i dont know why...:(
[Vibrant Android Development] shreddintyres:
ive used ka7 kb1 and kb5, now this issue is not one that is persistent, it happens somewhat sporadically.

I will recieve a phone call every now and again (most occurrences on ka7) and when i pick up the calling party either cannot hear me at all or will hear me very faintly, once i toggle the mute/unmute button they seem to be able to hear me fine for the remainder of the call (my calls last up to 1 hour).

Im not terribly familiar with how the ril and mic interact with eachother but would a logcat following the call help?
[Vibrant Android Development] Wizeblood:
Happens to me frequently, although not 100% of the time... only seems to occur with incoming calls... running kb5...

~Thanx! You know what you did!~
[Vibrant Android Development] bigtom624:
This is what happens to me also.
[Vibrant Android Development] Jackdog89:
I've been fortunate and only had it happen to me on build #29 with the KB5 modem, incoming calls only.

Maybe this isn't related, but out of curiosity; for the people that have it happen consistently, how old is your sim card?
[Vibrant Android Development] atinm:
Is the mute/unmute only required for voice calls over the main mic? Or also for wired headset mic, bluetooth mic?
[Vibrant Android Development] Jackdog89:
Someone reported earlier that they used bluetooth exclusively to avoid the problem. I don't think the issue persists over bluetooth. I have no idea about the wired headset.
[Vibrant Android Development] ginzberg:
I have only experienced this with the main mic. Not scientific, but unless someone can confirm the issue over bluetooth (which i use often), and/or headset (i never use), it may be isolated.

* added thought

Seems that this is exclusive to incoming calls. When I answer over bluetooth, I use the pickup button on my bluetooth. Curious what relationship between the different ways one can pickup a call and the different ways one can transmit voice (main/bt/handset mic).
[Vibrant Android Development] atinm:
I need someone who always has to do the mute/unmute and is available to help me debug/test a fix to contact me - send me a PM.

Thanks,

-Atin
[Vibrant Android Development] Phateless:
It's when RECEIVING calls. I haven't seen this bug yet either but barely use the Vibrant so don't have adequate testing.

So vz to T-mobile,

Nextel to T-mobile,

That's what we need to test.
[Vibrant Android Development] chev:
KB5 sir
[Vibrant Android Development] cojonesx:
I never have issues with the wired headset
[Vibrant Android Development] jonathanhuerta4:
Ditto, never had an issue with a wired headset, or a Bluetooth headset for that matter. I mostly use the wired headset, and the Bluetooth when driving.:)
[Vibrant Android Development] loganthered:
Except I tried different builds and that didn't fix it.

Yeah I used one. Is that the culprit? And here I thought the GB bootloaders would help with CM7.
[Vibrant Android Development] Relikk356:
I consistently have to hit the mute/unmute every time I receive a phone call. It's been described as though I sound like I'm in a tunnel if I don't. It sounds fine if I call out. I have not tired to receive a call through Bluetooth nor a wired headset. So if no one has PM'd you yet I can help in your debugging process. My PM sent.
[Vibrant Android Development] Poser:
Mute/Unmute issue:

-only on received calls

-across ka7 kb1 & kb5

-problem is intermittent (less than 25% of received calls)

-persistent irregardless of signal quality
[Vibrant Android Development] ChristoA1:
On my wife's Vibrant, it happens *every* time I call her...
[Vibrant Android Development] atinm:
Can the people who have to do the mute/unmute try the zip I am attaching below? Just install it like you would any nightly - it says 'KANG' because I am building it locally on my machine, but should be the same as the latest Nightly code but with some code changes for the audio driver to handle the mute/unmute problem with main mic.

http://www.multiupload.com/CNG6SKKUSF

Let me know if the problem persists.

Thanks.
[Vibrant Android Development] djf8:
I wish I would have waited another day or so to flash back to bionix so I could have helped you debug.

I had to mute/unmute on every call I recieved. I was on kb5 modem and the build is in my sig.

edit*

I'll give this a shot either this weekend or monday depending on when I get a call I've been waiting on.....gah stupid work stuff getting in the way of my cyanogen mod addiction. I should have kept my g1 as a backup for times like this.

Thanks for all your hard work man.
[Vibrant Android Development] Relikk356:
Downloading now...
[Vibrant Android Development] Relikk356:
Installed.

1. On the first call received I couldn't hear the caller but they could hear me.

2. I called the caller and everything worked fine.

3. They called me back and everything worked fine the second time I received their call. I did not sound like i was in a tunnel and I could hear the caller.

phone call was received from G2 on Tmobile network.
[Vibrant Android Development] ChristoA1:
Got it installed. Got boot loops the first time (scared the crap outta me as I'd never hit them before!) but I got that resolved... It may take a bit to really test it, but I'll report back!

edit: Annnnnd totally forgot gapps >_<
[Vibrant Android Development] Relikk356:
FYI, jut Got another phone call and I sound like im in a tunnel again per the caller.

Phone called received from ATT network, Iphone 3GS
[Vibrant Android Development] djf8:
Hrmm....guess I'll let you and others be the test subjects haha.

I'll hold off until one of you reports everything is rainbows and sunshine on the mute/unmute issue.
[Vibrant Android Development] atinm:
The upload I put up is purely for people who are going to help me test. There is nothing else that is different about it compared to the nightly. If you're not going to test it, refrain from commenting - it is just irritating when I'm working so hard on a phone I actually care nothing about to see a 'haha' (implying "I'll let you suckers test it" . . . )
[Vibrant Android Development] Relikk356:
Third call received said that they could here me, but after I hit mute/unmute I sounded much clearer.

Third caller, on ATT network and on a non android samsung phone.
[Vibrant Android Development] atinm:
http://www.multiupload.com/WAWJXXOYWF

Can you try this one? Same fix, but in a different spot in the code so it always runs before a call.
[Vibrant Android Development] Relikk356:
Downloading...
[Vibrant Android Development] shreddintyres:
if i recall correctly the 2.2.1 port that Krylon and Eugene did had the same problem, they found a work around so iono if it might be of interest to you, the fix is implemented in the 2.2.1 rom called bionix frost, so it might be worth taking a look at their code.
[Vibrant Android Development] Relikk356:
Installed, awating a phone call from friends. Should get it shortly.

UPDATE:

Caller could hear me but once I did mute/unmute I sounded much clearer.

Call was on Verizon and a blackberry. He doesn't know which one.
[Vibrant Android Development] Phateless:
The Vibrant IS my backup phone to the glacier which is why I haven't been able to help you guys test much. Sim is in the Vibrant now so will post if I have info to add.

On another note, has anyone tried installing the wifi calling app? I'm surprised not to see it since it works perfectly on the glacier. They'll probably merge it in down the line, I know we're still in very early phases.

LOL, my gf called while I was typing this. She said our call quality was perfect and I did not have to mute/unmute. This was the first call on this phone since booting up today.

I honestly think you guys are getting bugs because you're not letting the rom finish "thinking" on first boot after flash.

Do a factory reset/data wipe and let it sit there for 10 mins on first boot before you set up.
[Vibrant Android Development] Phateless:
I REALLY appreciate all your hard work. Lack of aosp roms is why I never bought a Vibrant before and why I sold my Vibrant 4g.
[Vibrant Android Development] atinm:
Anyone else try my last upload? I think that's about as best as I can do . . .
[Vibrant Android Development] Relikk356:
Yet another phone call...

*** Making a code name for Mute/Unmute, M/U.

Same thing as before, caller can hear me but once I hit M/U i sound much clearer.What was interesting this time is they said i sounded clear at first and then sounded like i was in a tunnel. I did the M/U and everything was fine after that.

Caller on tmobile/G2.
[Vibrant Android Development] Relikk356:
Okay, thanks for the effort. If you decide to do this again let me know, i'm always willing to help. I'm on alot, just not logged in often. For now im going to the GYM, thanks again!!!

PS. I'm already an Organ donar.
[Vibrant Android Development] ChristoA1:
What's really interesting is that for different people, the symptoms are different. For instance, in our case, the issue *always* occurs on receiving calls. However, it has never been a problem on *outgoing* calls...
[Vibrant Android Development] cashyftw:
Can't install, keep getting instillation aborted ( the one just posted by atinm )
[Vibrant Android Development] ChristoA1:
Downloading this one now... If we could actually get T-Mobile signal in our apartment, I could actually test these much faster!

...anyone wanna work on WiFi Calling? ;D
[Vibrant Android Development] nedlog:
Thanks for testing; I didn't realize until today that I have the same problem. It really is only when I receive calls that the other person says I sound like a "robot" but the M/U cleaned it up. Didn't realize how many calls I make and how few I get. :eek:
[Vibrant Android Development] atinm:
I need to hear from more people who have tried my latest upload to tell me whether this is working for them without having to do mute/unmute.
[Vibrant Android Development] flipper2006:
Did the 2nd one just get pulled from mega? I was in the middle of the downloading and i just "file reset error" then wentto do it again and it says file is unavaialble... this is the 2nd version you posted today, i will try from another source.. weird..
[Vibrant Android Development] atinm:
I didn't pull it . . .
[Vibrant Android Development] ChristoA1:
Ok, issue is still there... I've also noticed that it typically happens right around 5-10 seconds into the call.
[Vibrant Android Development] granduke:
Downloading now. Will update with my results.
[Vibrant Android Development] Locksmith81:
Issue of M/U is still there. I'm on T MO Vibrant 3G call
[Vibrant Android Development] Phateless:
Using this rom 100% stock. Just got a client call and they said they could hear me fine.

I did m/u anyway but they said no change. I don't seem to have this issue for whatever reason.

Those with the issue - when was the last time you did a full wipe? Flashing over may not count.
[Vibrant Android Development] bigtom624:
I tried both files and nothing changed for me. I'm using KB5 Modem also. When I first answer the other party can here me but after that they can't here me at all until I mute/unmute.
[Vibrant Android Development] atinm:
Oh well, thanks all. I'm going to leave it as is because I cannot duplicate it, and this seems to be dependent on device as opposed to a generic bug.
[Vibrant Android Development] Phateless:
atinm, have you played with wifi calling on this rom at all? I was going to pull the apk from my glacier rom but since it has HTC in the filename I kinda doubt it will work on the Vibrant.

I downloaded and installed the apk from the Vibrant 4g but it force closed. Rebooting now to see if that helps, next is to move it to /system/app and see if that accomplishes anything. I know this apk is from 2.2.1 so that's probably one reason it won't work.

Let me know what I can do to help. I'm not a dev but I'm good with tinkering.

EDIT - nothing but force closing, also tried to the apk from the newest nightly for glacier. Would love to get this working.
[Vibrant Android Development] themoose:
Thank God for 35. M/u fixed and sever battery drain fixed!
[Vibrant Android Development] Locksmith81:
You using the kernel that came with #35?
[Vibrant Android Development] atinm:
No, and it won't work. The wifi calling requires work in the kernel and framework - and as none of us are actually on TMobile, someone on TMobile has to figure it out.
[Vibrant Android Development] aghoshhajra:
Baseband Issues

I haven't updated my phone in a LONG time, but I just recently tried nightly #35. I'm having an issue with my baseband. It says unknown and I do not get any service.

I have already tried flashing both the KB1 and KB5 modems from scrizz's thread for 7.1 modems. As I am typing this, my phone randomly rebooted as well. I'm not sure what the problem is. I wiped data, cache, and dalvik prior to flashing 35. I am coming from the KANG version that was out much earlier (maybe early this month or late last month). Any ideas? I know there have been MANY changes since the kang version that I would like to capitalize upon. The only reason I didn't bother to do this before is because my phone was working great, so I figured, why mess with a good thing? Now I know why not...

Any help would be appreciated!
[Vibrant Android Development] inrelief:
As a disclaimer I haven't yet been able to run any tests against your QA build.

As this problem is fairly widespread, it feels to me that isolating this behavior device dependent feels like an incorrect call.

Not to say it's easily reproducible -- I doubt that it is.

In personal experience, it happens on a percentage of all incoming calls and I can confirm it's occurred when incoming calls originate from T-Mobile and from Verizon wireless.

I do plan to test your QA build as soon as possible.

An outstanding question I'd like to clear up --

Some on this board have suggested it may be necessary to odin back to stock and then re-install the latest build (versus having updated from the original nightly).

I'm admittedly in the dark when it comes to the post-install environment sanity. Given your familiarity, does this sound like a viable requirement?

I'd also like to reiterate my support for your work -- it has definitely breathed new life into a device I had otherwise given up on.
[Vibrant Android Development] awolbrin:
com_android_phone crach then moveing to new cm7

i cant upgrade from #8 to any other >#12 (including #33)

then i do upgrade my com_android_phone crash all the time

i can see my base-band (i tried ka7/kb5/kb1) but nothing works, if i am on airplane mode i can see my imei/imei-sv and they match my phone.

i did everything that is Written in "[TUTORIAL] Fool-proof method to install latest CM7/MIUI without losing Baseband/IMEI"

but no good

then i flashed the AIO-toolbar stock rom and kernel i had the same problem, this rom (i thinks it's stock t-mobile) allows you to save it's error log, so i attached it to the massage.

please help my understand what can i do.

i will be happy to donate to the one that will help my fix the problem, I'm Desperate.
[Vibrant Android Development] movieaddict:
I would odin back to stock then reflash cm7 in my opinion if ur coming from that old kang
[Vibrant Android Development] Relikk356:
I'll odin and then reflash 35 or the Kang, which ever has the new fixes. I've never done a fresh install of cm7. Maybe that will take care of it. can't do it till Sunday, as im busy tonight.
[Vibrant Android Development] atinm:
The call is purely based on my not being able to reproduce it and therefore not knowing what is wrong. I would welcome someone for whom the Vibrant was the primary device to take it over, but so far no Vibrant developer has stepped forward. To whoever mentioned Eugene - he doesn't release source code and so is generally useless to us.

You shouldn't need to Odin back to stock.
[Vibrant Android Development] Cesarp 24:
How is battery life on 35?

Sent from My CM7 Monster
[Vibrant Android Development] inrelief:
Thanks for your response -- as a developer by profession I 100% understand the situation.

I've got **** for experience doing kernel hacking/android OS development but what the hell...I've been looking for a reason to setup a linux partition on my new machine.
[Vibrant Android Development] atinm:
Mute/unmute - status:

I have basically hacked in a mute/unmute when using the mic - its the best I can do because it seems Samsung framework might be sending down something related to enabling the mic when starting a voice call, but it is non-standard and so we haven't figured out what it is.

If someone else takes this up, that's where one would need to look at first, basically log the calls into the kernel driver wm8994_aries.c and wm8994.c in sound/soc/codecs in the froyo stock kernel that you've built with logging on and figuring out what the calls into the driver need to be and what they do and then port them over to wm8994_herring.c and wm8994_samsung.c in the kernel source for Gingerbread that we have on our repository under github/teamhacksung/android_kernel_samsung_aries-common.

Then, once that's done - look for the gentec driver stuff and add that if you want internet calling!
[Vibrant Android Development] inrelief:
Thanks for the update. Great overview of the issue.
[Vibrant Android Development] Wizeblood:
Thanx for your efforts Atin!

~Thanx! You know what you did!~
[Vibrant Android Development] atinm:
https://github.com/teamhacksung/and...mmit/2f6322f4642df41b5d82fca05ded54e691c02079 - that's the relevant commit I hacked in.
[Vibrant Android Development] notverycreative:
I would love to help, but alas, I know very little C, only Java.
[Vibrant Android Development] movieaddict:
atinm , thank you for ur hard work and dedication
[Vibrant Android Development] treyvaporizer:
+1, thanks its very awesome that you're doing this even though it doesn't matter to you

Sent from SGH-T959 (CM7)
[Vibrant Android Development] ewidtfeldt:
If anyone was planning on taking this forward I do recall there being something to do with screen turn off and proximity sensing that was contributing as well. Is there a way to put a delay in your mute/unmute code like say:

When proximity is close and screen turns off THEN mute unmute. This could also be why those with headsets aren't effected. The proximity sensor isn't triggered by their face.

Just a thought. Not a dev, just an idea-man.
[Vibrant Android Development] nedlog:
Thanks for everything, my phone rocks now!!
[Vibrant Android Development] Locksmith81:
Didn't you ask this in the Platypus thread?
[Vibrant Android Development] Locksmith81:
Anyone else get random reboots during a phone call? Confirm by anyone?
[Vibrant Android Development] hitman818:
Didnr you ask this in the platylus thread to? Lol.