yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
There is a 3 part firmware? Be careful with that, the risk of bricking is higher.

But please report back if it works...

With GT-I9300 tapatalked
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
I just re-partitioned my device with Odin to ensure that really, really everything would be wiped. (I know this can be dangerous if you do it carelessly, so never do it if you don't really know what you are doing).

Guess what, even that didn't make any difference. As soon as I deleted a single app from /system/app it was business as usual: call sound gone.

So now you know you don't even need to try that... :-)

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] Zabalba:
Thanks for taking that chance for the collective.

What about flashing Omega and just freezing apps. Rather than deleting them. Do you still have the bug?
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Omega has never worked reliably for me since I have this problem. With that ROM (and also all others that I have tested) the bug always pops up sooner or later even if I don't modify anything at all.

I only use stock now and there both deleting or freezing of apps activates the bug. I can however disable apps without getting problems.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Maybe its related to the modem we use?

At first i got my s3 rootet with stock T-Mobile Rom(Germany) it uses Modem I9300XXLE5... never had any problem.

I've seen on other Forums that users with Baseband I9300XXLE8 and other Modems got that Problem even on Stock and never used some kind of root...

Some got replacement and some still wate for a statement from samsung...

Maybe its a Modem related bug... thinking about rooting my stock T-Mobile Rom(Germany) again and do another test only with root and nothing else... but this is my last test...
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
i would say its a manufacturer bug. Mine is the pebble blue causing the issue and the white works 100%. Can those who are experiencing this bug advise phone color?

Also, could someone who has this bug, activate the bug and flash CF-ROOT to see if it goes away?
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I got the white one, just got a tip that it might help to flash the latest CM9 Nightly... i will try that this evening... and report back...

EDIT: Someone got time to test it with the latest nightly?... i need to wait to long for testing :P work...
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
Got a white one and have the problem with the phone bug when I'm on custom Rom. So I think it got nothing to do with the colour.
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
I don't believe it is a hardware problem as the problem doesn't appear under certain software constellations (=stock untouched).

Flashing CF-Root does not consistently deactivate the bug. I have tested that many times and have come to the conclusion that flashing CF-Root only sometimes and then only temporarily (=until next reboot) makes the problem go away.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Heres my S3 flashing history:

I use cm9 nightly since it is out and have this issue right after Siyah 1.2.6.

I came original from Vodafone Germany ALE6. I rooted this and afterwards I updated to ALF2 stock ROM. Afterwards I flashed deodexed ALF2 from Wanam and from there I went to cm9 nightly when the first version was released.

I parallel used Siyah when the first version was out for the S3 and I installed all upadates till 1.2.6 (well not 1.2.5, because 1.2.6 was out before I could recognize ;) ).

Everything worked perfect till I flashed Siyah 1.2.6. Since then I have this issue. But I don't know (as all of us I think) what the problem is.

Now I am on cm9 nightly from 24th June. My procedure is to flash the nightly, then flash gapps (without boot) and after first boot flash CF-Root 6.3 with mobile odin. This gets me a working system as long as I do not do anything on the system.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Why flashing cf-root after flashing cm9?

With GT-I9300 tapatalked
[Galaxy S III Q&A, Help & Troubleshooting] scarecrow2012:
The phones facing this problem are they made in Vietnam or Korea?
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Hey everyone,

look at this...http://xdaforums.com/showthread.php?t=1726605...

i will flash cm9 later and look if the bug is gone if not i am testing the thing with

provider options...
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Thanks for all your research, really appreciate it!

For me unfortunately neither flashing CM9 nor manually selecting the service provider made any difference at all.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Mine is white and it's made in Korea.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Its only to get SU form CF 6.3 because cm9 has other/older SU. Not really needed. ;)

One statement from the other thread maybe fits to what I recognized:

I had the problem that I could not even call my mobile when the problem occured. My S3 showed me that I should be connected to the provider but when I called my mobile it did not work as if I had my mobile turned of or in flight mode.

Next time I will try this.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I am on cm9 now...changed a file in system rebootet and it still works...

I just renamed the file...

What I did:

1. Flashed the Touch recovery

2. Wiped Data/Factory Wipe Cache/Dalvik

3. Flashed cm9 24.06. Nightly

4. Flashed Gapps

It seems to work now...

EDIT: Deleted a file...reboot...still works...

EDIT 2: Gone..

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Reflashed cm9 it works again.

It stopped working because I added a file to system.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
From where did you flash touch recovery? From ROM Manager?

Reflashing cm9 always helps for me temporarily.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
The official one :-)

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Look at this:

http://androidforums.com/samsung-galaxy-s3/565955-samsung-galaxy-s3-problem.html

http://www.boards.ie/vbulletin/showthread.php?p=79269682

So maybe Samsung has a problem with the S3 and all our thoughts were wrong?
[Galaxy S III Q&A, Help & Troubleshooting] WhiteHartMart:
Thanks - that's confirmed mine is hardware related then - a couple of firm knocks against my hand and the in call sounds returned!! They've gone again now though but at least I got chance to listen to my messages before my returns envelope arrives :good:
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Thanks was interesting to read, but I wonder if it's really about “our” bug/problem. The symptoms seem to be different.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
I can confirm some of these symptoms. E.g. I couldn't call my mobile while the S3 showed me 100% provider connection but I could call other phones from my S3. And I already heard about someone who had the voice problem with a stock rom.

I wonder if someone could logcat the problem and a specialist could analyze it. The more people get that problem the more will care about. So I think there will be a solution.

I contacted Samsung support about this. I am curious what I here from them.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
From a German Forum:

Ist das bei euch auch so, dass ihr nach dem Stummschalten des Handy nicht mehr telefonieren könnt? Es kommt nichtmal das Freizeichen während dem Anruf. Es kommt einfach nichts mehr aus dem Lautsprecher raus. Unter anderem kann mich mein Gegenüber nichteinmal hören obwohl die Verbindung steht. Dann muss wohl das Mic auch aus sein....

Wenn ich die Stummschaltung wieder ausmache funktioniert alles wieder Prima.

that means:

as soon he put the phone into silence/vibrat mode, he got the same bug that the phone speaker is dead... but as soon he made volume up, everything worked fine...
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
I have done some more testing today and would like to report my results here - even though I am not sure if this information is of any use for you, to be honest.

First I tried to get OMEGA working on my phone. I started with Omega 6 and this didn't work at all. I had call-sound in the first and the second boot cycle, but then it was gone again, even though I didn't touch the system partition at all. I tried to reproduce by fresh installing the same ROM once more and this time the call sound survived three or four re-boots before it vanished again.

Second I tested Omega 5.2 once again (had tested it several times before) - this time without changing anything on the system partition. The testing first went surprisingly well. I could reboot several times and the call sound was still present. But - and that really puzzles me - taking a photograph (!) with the stock camera made it loosing call sound again after the following reboot. I am pretty sure that the use of the camera activated the bug - as I could reproduce exactly the same behaviour three times.

Finally I also tested a deodexed and rooted stock rom: XXALF6 from Wanam. On my handset this rom seems to be even less prone to the bug as odexed vanilla firmware. I could flash the camera mod and several themes without loosing call-sound. Now I have rebooted about 10 times and everything is still okay. I guess I will stay on this rom for a while, because for now I am pretty sick of flashing and flashing and flashing all the time. But I have no ilussions, I know the bug is still there...

What about you guys? Any news???
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I've tried so much the last 4 days, that i'am sick of flashing.

Today i flashed Stock Rom XXALF2 UK and everything is working fine.

It looks like when i am staying on Stock everything is okay without any problem.

And i must say it isnt that hard not to have root and stick with stock.

At least for some weeks or until the bug is really identified.

Maybe the bug is fixed with XXALF6 but i really dont want to try, as long as i can

enjoy my S3 without bug... i will stay on stock...
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
I'm now on stock rom. XXALF6. Just rooted it by myself and everything is fine until now. Maybe this weekend try a little more modification to test what the bug needs to get reactivated.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Is XXALF6 better then XXALF2? what do you think?
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Hm Wanam ALF6 and stock rooted ALF6 are doing fine? But Omega 6 is on ALF6 too and for citronbitare it didn't do.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I am on stock XXALF6 too. But didn't root and everything is fine. I guess

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
I have tested many variants of both and my impression is that it doesn't make any difference.

*** via Tapatalk ***
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Any News? is everything still working?
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
Using this configuration for a week or so and everything runs fine.
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Stock ALF6 with root, but you did not do anything on the system up to now, right?
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Some people say that putting the battery in and out helped to activate the call audio again...

I am wanting to try kernels so bad...the sound on franco is so great...

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
No. Just root it. But like i said this weekend i will do some more modification to see how far i can go. :)
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Okay i did it. XXALF6+Root+Siyah Kernel. Did 10 restarts everything is fine.

Just used Triangle Away. But i leave the system untouched for now ;-)
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Another thing we may follow. I flash gapps always after a new nightly cm9. And I flash two versions, the current one and before gapps from 17th march (which is suggested by cm9 but does not include gmail).

How about the others? Did you flash gapps and if yes which version(s)?
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Hello Guys,

i am on Omega 6.0 + Siyah Kernel for about 2 Days now and the bug as not poped up again because i dont change something on system.

Flash the Rom + Kernel thats it...

Titanium if you freeze apps just dont freeze system apps... it tells u when

if you try.

i am happy with that.
[Galaxy S III Q&A, Help & Troubleshooting] Zabalba:
Update on my particular issue.

I have not had the bug reactivate since I unfroze some apps quite some time ago.

The only changes I've made since then would be the Dormancy mod. After that mod everything continued to work.

Today I made a backup using TB and through cwr. After reboot I could not hear calls. I rebooted once and my sound came back.

This has to be the most irritating bug I've ever encountered.

If I run into it again I'm going to try and fix permissions.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Because of your post i desited to make a backup(CWM) too and look if the bug comes up... ta da... bug was not there.... strange...

I read on a german forum that it helped just to take the battery out for a few minutes and the bug was gone...
[Galaxy S III Q&A, Help & Troubleshooting] Zabalba:
It's equivalent of power cycling the phone (reboot)

I want to make it clear I had two degrees of the bug.

The first which was the kind I encountered the most, presented itself intermittently. For example sometimes someone would call and I could not hear them or call back, but once I rebooted it resolved itself.

The second kind which I only experienced when I was on Omega 5.0 + Siyah 1.2.6. No amount of reboots made a difference. The bug persisted.

I also want to post I'm currently on Omega 7.0 + Siyah 1.2.6 and I'm not experiencing the bug.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Have you changed something on the system?...wait a minute 7.0 is out? Nice need to download :D

EDIT: just a little Update... Changed the Touchwiz Launcher in system/app did a restart and still got call audio :D

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
So you guys think it's gone now? That would be great!

Edit: Where the hell you get download link for v7.0? :) Cause for me still stands v6.0.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I dont know if it's gone :-/ I keep my system changes on a very very minimum level...

I am even scared of using the provided omega files mods...

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
Before i sent my phone away, i flashed it with stock XXALF5 and the bug was still there. So i dont know what the differences are between stock vs Omega 7?

What kind of system changes did you do? For me, when i drop something in the system/media (ringtones) or overwrite a system/app, the bug appears.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I only changed my launcher... and flashed siyah kernel...still no bug...

I really dont think it's hardware related...

Have you flashed stock with pc or mobile?

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
Little update. Yesterday i flashed omega v7. Did a full wipe before. The first two boots no bug. After the third reboot bug back again. Turned phone off after that. Today as i woke up and turn my phone on, bug is gone for now. Don't know what the hell is wrong.
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
Atleast theres some good signs with Omega 7. Have you tried modifying the file system? like drop something in the system/app or system/media?
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
update: my white s3 got this bug just now. didnt even install anything or touch the file system. so weird
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I am bug free since a week now...I don't know right now I am on omega 7.0 and neak ...everything great so far....

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
Got to go back to stock again. The first two reboots everything was great but than bug back again without touching anything.
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
so to confirm what you have done.

1. flashed to latest stock rom

2. then flash to omega 7

3. then flash neak

all working? Did you touch the file system, do any titanium backups etc?
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
That would be very helpful to know.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I flashed at first my Stock Rom which was on the phone fresh out the box.

Then I flashed Xxalf2 then xxalf6 then omega 6 with siyah then omega 7 with neak.

I did a nandroid.

After that I restored my user apps and changed the twlauncher with es file explorer in system/apps.

Everything is fine at the moment.

Edit: now I froze tw launcher with titanium and using nova ...restart everything fine.

Edit2: Maybe it's kernel related? Someone might try it? I leave my system for now because everything works.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
If this works that would be great. Did you flashed the firmware via mobile Odin or via Odin on the pc?
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Everytime only with PC Odin maybe thats why it works... i dont know...

i am just happy that it works... i dont have to send my s3 to service...

If you try could you report back if it works for you?
[Galaxy S III Q&A, Help & Troubleshooting] Chris_84:
Will try it maybe tonight. But again many thanks for your report!
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
going to try this

GT-I9300 I9300XXALF6 Android 4.0.4 2012 June I9300DBTALF4 Open Germany

then Omega 7

then siyah 126

its driving me crazy. cant even use titanium
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
Bug came back... tried psx4droid... phone need to be restarted with battery out... now bug... flashing GT-I9300 I9300XXALF6 Android 4.0.4 2012 June I9300DBTALF4 Open Germany now...

and leave it for a while... so crazy...
[Galaxy S III Q&A, Help & Troubleshooting] citronbitare:
Thanks a lot for all your testing and your reports!

I have been myself on deodexed and rooted stock XXALF6 (compiled by Wanam) for the whole week. I could theme the rom with ICS Domination & ICSwiz, so that it looks almost like AOSP. Could also flash the camera mod and could block ads with adaware. I could do all these things without "waking up" the call sound bug; have used my phone this way and did countless reboots without any problem for the whole week. So I am pretty happy that there is a way to fully use the device (even with some minor modifications).

However, I would really like to be free again to do whatever I like with the device. And I know that I cannot modify the file system as I would like to (tried that in the beginning of the week and it promptly brought the bug back).

It's a kind of strange situation. It seems to be possible for all of us to have a fully working phone as long as we don't do to certain modifications that require root privileges. This certainly is a good thing in itself.

The problem is that we all like to modify our phones. Yet, if we can't resolve this problem we have to live with the situation not to be able to do this. After all we can't tell Samsung that they should replace our device. Why should they do that? You can't claim that a phone that is fully working with (unmodified) official firmware should be replaced. Officially our phones are not supposed to get rooted and modified...

Well, I will probably also do some more testing next week when/if I have the time and opportunity to do so. Thanks again for all your efforts so far!
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
Update in this order

- Flashed GT-I9300 I9300XXALF6 Android 4.0.4 2012 June I9300DBTALF4 Open Germany

- Installed CF-6.3

- Installed titanium backup and froze apps

- Installed Startup Manager and removed unnecessary startups (at this point the bug appears)

- Installed SETCPU

The phone works perfect. Doing a CWM backup now. Will update tomorrow as its ZZZ time

Things to do tomorrow:

- Install Siyah to undervolt

- Install 15 status toggle

Only thing is im missing the english samsung keyboard as it only supports Deutch.

update this morning

- Installed Siyah 126 and undervolted all steps == phone works perfectly

- Dropped a ringtone into system/media/ringtone == phone works perfectly

Installed Omega 7 == BUG!!!!

Could it be that stock is ALF6 and Omega 7 is ALF5 where they dont match thats causing the bug?

Restoring backup

*update*

Constantly updating file system. Installing through CWM == phone still works
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
So now youre on stock xxAlf6 only with custom kernel and everything works?

I thought about testing just kernels and nothing else...i think stock rom is fine.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
yes im on stock rom but everything works. The only thing im missing is the 15 status toggle. Need to find one made for odex ALF6. Im thinking of flashing vertimus theme but ill wait for my phone to return tomorrow from service
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
You gave your phone to service? Did the bug came up even on stock without mods?

Gesendet von meinem cm_tenderloin mit Tapatalk 2
[Galaxy S III Q&A, Help & Troubleshooting] porkchop8:
i have a blue and white one. i took the blue one in last week cos i couldnt get it to work properly. I am getting it back tomorrow as they found no fault with it (fair enough). The blue one - I flashed the earlier version of ALF6 & Omega 5/6/7 all works fine but unable to install any mods.

With the white, i tried the ALF6 Germany version with mods and it works fine. As soon as i tried Omega 7, it failed. I am happy with the stock rom as i am able to use siyah, setcpu, titanium and other tweaks without animating the bug.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
I am happy too with stock... and like u said the fact that kernels etc. work is nice :) i am on stock alf6 germany now to with neak kernel :) hope i can stay with that
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
Yesterday the bug came back on cm9 nightly and I could not get rid of it. Restoring from Titanium always gave me the bug. Then I tried Omega 7 without success. I have a nandroid of my original rom only with CF-Root that I can use to kill the bug and start with new tests.

In the end I started from scratch. Triangle Away, Stock ALF6 ROM (GT-I9300 I9300XXALF6 Android 4.0.4 2012 June I9300DBTALF4 Open Germany) from samfirmware. Counter is 0 and device Status not modified.

Then rooted with CF6.3 and did basic installation without any Titanium things. After basic installation of my about 80 Apps I flashed Neak and it still worked.

Then I made a backup with Titanium and a CWM nandroid and afterwards UV with VoltageControl and it still works.

I will stay on stock ROM now ;).
[Galaxy S III Q&A, Help & Troubleshooting] saigai:
I wonder if this could be related?

http://xdaforums.com/showthread.php?t=1745974

I tried to check what was changed, but couldn't figure it out.
[Galaxy S III Q&A, Help & Troubleshooting] alexwontlose:
deleted
[Galaxy S III Q&A, Help & Troubleshooting] ElenaPower:
These two files will only work with this special ROM I think so be careful. But if this really is the solution it will be spread to other ROMs fast I think.