yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] slofmb:
Csc was properly shown with the 3 part rom and also manage to get it to show properly with the XXBLFB 1 part rom which has the EURBLG1 csc.

Call bug still present under any combination.

UPDATE: I just noticed that signal is dropped ( out of service area) between 25-35 seconds in the call in a very good signal area. Am now on stock XXBLFB with XXBLFB modem and EURBLG1 csc (my area csc) after wiping with every possible option (factory reset withing the settings a stock rooted rom after having already wiped and formated every single option in cwm recovery and using traingle away to reset counter so i can take it in tomorrow for repair if nothing else works. Then flashed the above mentioned rom from PC ODIN.

Is there anyone who is experienceing the bug not flashed siyah 1.2.6 once? Because that is the only common thing i can find here and i am pretty sure i did not experience the problem before that although i cant remember if that was when it started.
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
if you still have the bug, restore the bootup sound. That can also get rid of the bug.
[Galaxy S III Q&A, Help & Troubleshooting] slofmb:
If you go through the thread you 'll see that some (including me) have gone completely stock, no CF-root or any other mod (as a matter of fact not even apps from playstore, i havent even enterer my google account) and the bug persists. Am probably sending it back where i bought if for replacement/repair since the phone is intact and the counter for download has been reset.

By the way do we know if they 've got a way yo tell whether the download counter has been reset?
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
I don't know but I don't think they care much about. I totally bricked my s1 more than a year ago cause I was so stupid to try to flash a s2 firmware on it. Face palm. So I take it to my dealer and said I don't know what's happened. It just won't turn on. They send it to Samsung and I get my original phone back just unbricked with a new firmware on it. And no one said something like you got to pay you bricked by yourself, we know what you done. What I'm trying to say is that I don't think they will take a deeper look. Just repair it and finished, on to the next one.
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
go into download mode via the buttons. It will show the custom binary counter.

Did you use stock I9300XXALF6_I9300DBTALF4_I9300XXLF5_HOME.tar or higher? I found any versions lower than that caused the bug to appear.
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
Don't know but it seems that no one got that issue anymore. That's great. I also found out that for me always fixed the issue to restore the ui folder in system media.
[Galaxy S III Q&A, Help & Troubleshooting] slofmb:
I sent mine to samsung for repair and they couldnt fix it so i got a brand new phone...
[Galaxy S III Q&A, Help & Troubleshooting] fallenwout:
Something like this after updating to XXBLFB?

http://www.youtube.com/watch?v=ENNa-Darfwg

http://www.youtube.com/watch?v=fo46OXWEcX0

Watch the reception meter!

Both video are mine. I brought it to a Samsung repair center and they could not fix it either. They had to sent it directly to Samsung. I'm without a phone for at least a month cuz of this.
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
That sounds cool. Hope your issue is solved.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I'll just stay on Stock with Neak kernel. I think a custom Rom is not needed anymore.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Solidswede:
This is the exact same problem I have.

Sucks. I'll go to my retailer and hand it in. Luckily I saved my previous phone so I won't be without phone.

So frustrating...
[Galaxy S III Q&A, Help & Troubleshooting] Bravehelmet:
I've been downloading and flashing Cyanogen nightlies since I rooted my phone shortly after I first bought it in June.

Everything was ok until about a month ago when I flashed a new ROM and the earpiece stopped working.

Originally a fiddle about with rebooting, clearing various things and connecting and disconnecting my earphones would do the trick but it has got worse.

The only thing that seems to work now is to delete data, cache and dalvik cache then flash a ROM.

Who knows how or why this is happening or why this fixes the problem but hopefully clearing everything and reflashing a ROM will save people having to send their phones away!
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Still call audio bug even on omega v14 on stock everything fine

Gesendet von meinem GT-I9300 mit Tapatalk 2

EDIT: Okay the Tip from Chris_84 works like a Charm... restored System/Ui Sounds now i am on Omega V14 without any problem

did even some restarts :)
[Galaxy S III Q&A, Help & Troubleshooting] :
I'm having this same problem on cm9 & cm10 builds. I've tried not changing anything in the /system folder, but I believe some CM features do that anyways. So after the first reboot, I always lose call sound. I've also tried different modems, with no luck. The only thing that works, is to be on stock software. This sucks! This phone is useless IMO if I can't change anything on it & TouchWiz is downright ugly.

Anyways, thanks for the continued effort of those trying to figure this out. Hopefully it gets fixed before I end up selling this phone.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Hi,

this helped me on Stock Based Rom so it should work on CM9/10 too, because the "fix" was found out on CM.

http://xdaforums.com/showthread.php?p=30657425

Greetings
[Galaxy S III Q&A, Help & Troubleshooting] :
THANKS A TON!!!

That worked perfectly for me. I was seriously debating on selling this phone & going back to my gnex on vzw. I feel so much better back on aosp. Thanks!
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Thanks also for trying :P wanna test paranoid Rom later so now I am on the save side that it really works I only tried it on stock :D

Which aosp you are using?

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] :
CM10 nightly 'beanpeeler'

http://get.cm/?device=i9300

Edit: I guess 'technically' it's an experimental build. It works great as long as I flash the old HW composer from the 8/14 build. Otherwise it studders & FCs a lot.
[Galaxy S III Q&A, Help & Troubleshooting] sintic:
Have the same problem with supernexus build 2...
[Galaxy S III Q&A, Help & Troubleshooting] stallemanden:
I am also seing a strange problem with sound.

I am running Omega v19 (The problem was also there with v17) http://xdaforums.com/showpost.php?p=26325755&postcount=2

Scenario 1.

I receive a call.

I can not hear the caller, and the caller can not hear me.

Scenario 2.

I make a call.

I can hear the one I am calling, but the caller can not her me.

I have tried "resetting" sound through: http://xdaforums.com/showthread.php?p=30657425

Did not change anything.

I have tested.

Recording sound - WORKS

Playing recordings - WORKS

Playing audio - WORKS

So from what I have found out, it seems only to be a problem during calls.

Is there anyone who might have a similar issue, or at least have an idea on how to fix it.

*EDIT*

I have just done additional testing.

The issue persists, when using bluetooth headset device. - Exact same senarioes as mentioned above.
[Galaxy S III Q&A, Help & Troubleshooting] wergor:
i have the same problem with temasek's cm10 rom as well as the official cm9.1 (didn't test any other roms). with temasek's build, it happend with roughly 1 out of 4 calls, until i restarted the phone (didn't fix the issue every time). with the official cm9.1, it happens in about 1 out of 10 (restart -> fixed)

i already tried enabling lockscreen sound, but still have this issue.
[Galaxy S III Q&A, Help & Troubleshooting] sintic:
So for now there is no solution for this problem right ?
[Galaxy S III Q&A, Help & Troubleshooting] stallemanden:
My solution

Hi - Just so that it is not skipped.

As mentioned, the first thing I did when I had installed the new rom, was to apply the modem driver, that should fit my phone.

However, after having talked to one of my friends that do some development on the android platform for CSR, I gave it a shot with the rom but without installing the modem driver.

That soleved it for me, so currently I am having no problems at all. (And just godt back to China, and checked that everything works here to.)
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
When you enable locksound make sure that the phone is not on SILENT mode den restart...so that the first sound after restart is the soundunlock sound...that always fixed the issue on every Rom...

If not on the first restart...shut the whole phone down for some seconds the switch it back on...

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] sintic:
still nothing is fix the problem on my phone.

I'll send it to repair is a few day's.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
For me it always helped flashing back to full stock Samsung Rom via odin. But now the locksound "fix" does the trick for me...

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] polyansky:
Possible solution

POSSIBLE SOLUTION

For all people who have problem of "no sound during call running non-stock rom". And for whose who tried re-flashing modem/kernel without any success. I have a solution, atleast for me. But first I should tell the simptoms of MY problem because I'm not fully sure that YOUR and MY "sound problems" are exactly the same.

My simptoms:

Problem appeared from nowhere (no flashing before, just usual using MIUI that I used for several months)

Running stock rom - everything is OK.

Running non-stock rom (I use MIUI) during call I got one of the cases:

- no sound at all

- terrible crackling sound of the other person (he hear me OK at the samr time)

- VERY rarely everything was OK on some OLD versions of MIUI

I've tried a lot of modems and kernels - nothing changed.

Today I was thinking why I have RANDOM result, and why sometimes reboting the phone helps to catch a "OK-sound case". I supposed that the problem is connected with different mobile-network-antennas (sorry for my english). I changed in settings "mobile network > selecting type of network" to "2G only" (in MIUI this setting has variants Both / Only 2G / ) and the problem disappeared! It is strange but it works - I've tried another MIUI-rom already.

When I looked for the information on this problem I underdtood that a lot of people have the same problem. So now I'm going to duplicate this message in some treads - maybe it will be helpful for someone - I hope moderators will not mind this.
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
I have followed steps 1, 2, and 3 then flashed Omega 5.2 and that did not work. Call sound was gone after reboot, as usual. But maybe it will work with Omega 6 as it might be closer to stock firmware, who knows. Could you test that and report back to us? Can't do any testing myself over the weekend.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] Zabalba:
Even do I have not had the problem since I unfroze my apps, I'm going to flash the latest omega. I will reformat /data, /system, etc and will report back.

---------- Post added at 07:21 AM ---------- Previous post was at 07:14 AM ----------

EDIT

Something interesting I read in the Omega thread
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Thinking about testing it this evening. And report back.

I hope this bug never comes up when i flash Stock Rom via Odin, thats what i am scared of.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Flashed Omega 6.0 all was working perfect did about 20 restarts made Titanium Backup restore Everything....then i tried Franco R5 bug came back. Only thing that helped was flashing Stock Rom via Odin again. But Wipe was not needed....strange....i think it has something to do with Sound stuff in all the new Kernels...with some devices...

Gesendet von einem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Danke fürs Testen. Thanks for testing! Interesting that a kernel change made the bug come back. After my own testing I thought kernel changes wouldn't matter...

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Had many different roms before on my s3 and kernels.....it all started with siyah 1.2.6... maybe I'll do some other tests with Omega and older custom kernels....

EDIT: Now i am flashing XXALF2 Stock Rom + CF-Root then i change something in system like (Camera Shutter) and do some serval restarts if the bug comes up on stock

just with root... if not then i am sure its because of the sound stuff... hat XXALF2 before only with root and change Shutter sound and had no problems...

few more tests to come...

i dont know why i am doing this... because the S3 got even enough power on Stock ...

Gesendet von meinem cm_tenderloin mit Tapatalk 2

---------- Post added at 09:19 AM ---------- Previous post was at 09:01 AM ----------

After 7 restarts Call Sound works...

---------- Post added at 09:51 AM ---------- Previous post was at 09:19 AM ----------

So right now i am on Stock Omega 6.0 and everything works... done Titanium and other "usual" stuff... serval restarts and Call Audio still works...

I'll leave it now on my S3 and report back and the end of the day...
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Changed something with Omega Files...Call Sound gone...okay thats it...gonna leave the Custom Scene for a while...it looks for me that no one cares about this bug...

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Well, I do care for sure and some others like Zabalba also do. But yeah we are not really many people who seem to care and for now we don't really seem to have a clue about the causes and possible solutions of the problem. It's frustrating!

I will also do further testing after the weekend. I am on the countryside with my family and can't test anything right now.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] WhiteHartMart:
I had the same problem with losing call sound - worse for me though as it doesn't even work in stock now - its either hardware related or somehow software/drivers are completely goosed on my phone.

Replacement phone due this week - will be staying on stock rom for the first few weeks at least ;-)

Sent from my GT-I9300 using Xparent ICS Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
How did you flashed stock Rom? It only worked for me by flashing with pc odin. Not with mobile odin. And just to get sure i made a factory reset within the normal options.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] WhiteHartMart:
Thanks but I've tried PC Odin a number of times and wiped the phone more times than my rear :-P. Have also tried 3 different custom roms and 2 stock ones - nothing makes any difference :-(

Sent from my GT-I9300 using Xparent ICS Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
I did some more testing. I am currently on the latest nightly (22.06.) of cm9. I installed "secure settings" (a tasker plugin) and within secure settings I installed the helper (which is installed in the system). Right after this I had again the call sound problem. Whenever I am called the caller will not hear me but I can hear him.

And I recognized another thing. I rebooted and wanted to try if the sound problem is still there. My mobile was booked in at vodafone but I could not call my mobile from another phone. From my mobile I could call other phones. For a caller it is, as if I have turned of my mobile.

I use universal number at vodafone. When my mobile is off (not booked in) a caller automatically is getting a voice message that he is transferred to another phone (my home). I get this message even if the mobile says that it is booked in to my service provider.

So when I have the sound problem it looks as if my mobile is not correctly booked in at the service provider but my mobile tells me that everything is ok. Maybe this can help for isolating the bug. I can start calls from my mobile but noone can call my mobile. So the issue may not be locally on the S3 but on the connection to the provider.

EDIT: I have to take back the next statement, simply flashing CF-Root with mobile odin does not work all the time.

And I found a way to reenable the sound. Whenever I get the sound problem I install CF-Root-SGS3-v6.3.tar with mobile ODIN and I so it works until something is changed on my system partition. So this is my workaround till hopefully someone found a fix for this nasty problem.
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
I'd like to share my experience with this issue.

I have a white (mrs) and pebble blue (mine) s3. Both i flashed Omega 6, titanium and other sys apps. Only the white one remained with 0 issues.

The pebble blue on the other hand experienced loss in sound when calling and unable to send SMS/MMS. Flashed 2 different stock roms from samfirmware and other custom roms. It worked for a moment but any changes to the file system resulted in no sound. One positive though is that everything else works perfect.

Sent the pebble blue back to the store and hopefully they will replace with a new one.

Now i am afraid to update anything on the white one but i guess if it is working 100%, there shouldnt be any issues.
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Than you for your feedback. One thing may be of interest. Did you ever flash Siyah Kernel 1.2.6 or did you have this issue without this special kernel version?
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
i flashed my phone about 20 times with different combinations.

Flashed from Omega 5.1-6.0 with all siyah versions = no sound.

Flashed the 2 latest stock firmwares only from samfirmware = no sound

When i mention no sound, it happens as soon as i touch the file system. Even as simple as adding some ringtones in the system/media.

edit.. Weirdest part is, my mrs one works 100% even after touching the file system
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Ok so the one identical thing that all people with the sound issue have is still that they once flashed Siyah 1.2.6.
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
interesting you say that. the white one has Siyah 1.01 only, never flashed 1.2.6. Maybe that is why it is still working 100% even after modifying file system.

But i dont see how 1.2.6 sticks to the s3 even after flashing a new rom??
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Thanks for all your reports! To sum up, the problem seems to be less likely to appear with untouched stock firmware. Rooting in itself doesn't seem to have a negative impact. But any changes of files on /system trigger the bug to appear or to come back.

What kind of causal relationship might there be between simple changes of the file system and the functioning of call sound?

I have no idea at all to be honest. What about you guys?

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] Zabalba:
Judging by the responses and newcomers to the thread, some of us do care greatly about the bug. I thank you for taking the time and experimenting with the bug.

I don't think we can say for sure it was Siyah that flubbed something up unless it messed something up on the hardware level after flashing it once.

I wanted to create a list of all the apps we install/restore using TB. It might be a app that does not play nice with GS3 under certain conditions.

I guess I could use Excel to keep track of common denominators.

What do you guys think?
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Hmm i dont know if this helps. I got the same apps as before the bug...

Could it be possible that some code change something on the hardware?

Maybe we could ask chainefire for help if flashing cf-root via mobile odin helps to stop the bug...?

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Sorry, but this does not always help after I changed something in the system as I had to recognize now. I just installed a tasker plugin that installs something in the system and after this flashing CF-Root with mobile odin does not always help as it did before.

So we are still at the point where changing anything on the system partition "activates" the bug.

So currently I have only one way to temporarily get rid of the bug that 100% worked till now. I am on cm9 nightly. And when the bug appears I flash the latest cm9 version and gapps (without boot between) and the bug is gone. Without gapps it may work too. After this I flash CF-Root 6.3 mit mobile odin and it still works.
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Great idea! Thanks a lot Zabalba!

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Maybe its because we flash without pit? isnt pit for complete repartition?
[Galaxy S III Q&A, Help & Troubleshooting] Zabalba:
Tasker is one of the apps I normally installed. Does anyone else use Tasker?
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
I am also wondering whether repartioning would help to finally get rid of the bug. Anybody who knows how to do that without risking to brick the device?

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
I don't use tasker.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] Zabalba:
I would hold off on re-partitioning anything.

Sometimes this kills the device...
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
The plugin I installed is not from tasker, its an external plugin from another programmer. This plugin installs a tool in the system and this reanimates the bug.
[Galaxy S III Q&A, Help & Troubleshooting] ciscostud:
No audio issues here with 1.2.6.

The only rom I've flashed is foxhound and I have never changed any audio settings with extweaks.

Never flashed a different modem

Virgin Mobile Canada gsm network
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
When i experimented it was quite random. After a flash, i install root explorer, titanium, task killer and startup manager. All installs fine and phone still works. As soon as i drop some files into system/media for my ringtones, it would crap itself. Using titanium to freeze and startup manager to remove startup is random. As i mentioned i flashed it about 20 times, each time the bug happens at different times.

---------- Post added at 08:45 AM ---------- Previous post was at 08:43 AM ----------

Could someone try flashing CF-Root only once the bug happens to see if it fixes itself? This way i dont mind as i modify everything i want, flash CF-Root, then i have a 100% working phone.

Sorry i dont have my phone with me to try.
[Galaxy S III Q&A, Help & Troubleshooting] jonny68:
try a different kernel i recommend Franco kernel.
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
I dont think it has anything to do with what kernel you use. Even stock animates this bug when file system is touched. But on the flip side, the other s3 has no problems.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Someone tried cm9? Is there the call audio bug too?

With GT-I9300 tapatalked
[Galaxy S III Q&A, Help & Troubleshooting] WhiteHartMart:
Didn't make any difference for me :-(

Sent from my GT-I9300 using Xparent ICS Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I am so confused about this...maybe some phones are different manufactured...

With GT-I9300 tapatalked
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
Yeah it's really frustrating. Got to change from omega to stock cause of this. Next weekend I will try to flash a stock Rom with three parts and flash again omega. The issue for me begin when I flashed siyah kernel 1.2.6. Before everything was just fine. Hope someone find a fix for this issue.