After 20 minutes of working all sounds disappeared, mic is not working and headset is not working too. Tried different roms, still no luck.
Anyone else experiencing this?
Freikugel said:
After 20 minutes of working all sounds disappeared, mic is not working and headset is not working too. Tried different roms, still no luck.
Anyone else experiencing this?
Click to expand...
Click to collapse
Sounds like hardware. Return for warranty repair or replacement
If rooted;
1. Use Triangle Away to reset counter
2. Flash back to original official firmware
3. Wipe any evidence of SU apps etc and also internal sdcard
UpInTheAir said:
Sounds like hardware. Return for warranty repair or replacement
If rooted;
1. Use Triangle Away to reset counter
2. Flash back to original official firmware
3. Wipe any evidence of SU apps etc and also internal sdcard
Click to expand...
Click to collapse
Done everything you've mentioned and returned phone to the supplier. Just wanted to know if it is a mass defect or is it just my unlucky phone.
Related
hi guys, i have this problem which i'm not sure is attributed to the hardware or defective apps.
About 1week ago, my phone speaker suddenly not working, at that point of time i was using stock KK5 with JKay settings.
I clear my cache, dalvik, not working.
Wipe all, flashed to checkrom 4, not working.
Nandroid back to KK5, flashed to newest KL3 2.3.6, not working.
Since its the festive period, don't want to leave my phone to service center, since my backup phone is a dumb phone.
I don't want to update my apps since if need flash to stock, i update for nothing. Nonetheless, i yesterday night upgrade, but speaker still not working as well.
But now when i plug in my phone to desktop, the speaker is suddenly working again, as i can hear the beep sound, and when i tried to play songs, it is working as per normal. I restart the phone, the speaker now is still working.
So therefore should i still send my phone to service center?
ngsngn said:
So therefore should i still send my phone to service center?
Click to expand...
Click to collapse
Honestly, that's something only you can answer. It seems the problem has fixed itself, hasn't it ? If that's the case then I don't see what the problem is
I guess the bottom line is, does that problem occur when you're running stock ? If it doesn't, then it's obviously an issue with whatever rom/kernel you were using. If it does happen with stock as well as with custom rom/kernel, then it's probably a hardware issue and me personally, I'd get it fixed. I didn't pay $500+ for a phone to have the speaker stop working after a few months. I have a "dumb" phone as a backup as well, having to use this for as long as a repair takes wouldn't be an issue for me.
Hi,
I'm using Stock rom with custom kernel. One thing to note is that by default, it is shipped with DXKI2. I updated to KJ3 and subsequently KK5 without doing a full wipe. Only cache and dalvik wipe. Along the way i did switched kernel, but i used the samsung ultimate kernel cleaning script to clear any files left by previous kernel.
It is only last week during KK5 that it suddenly go defective on me. Tried KL3 and stock kernel, does nothing to help it. It is only just now then it miraculously fixed itself.
So let say if i did go to the service center, what kind of reasons should i explain to them in order to 'fix' it?
Seriously ?? How about "the speaker is failing intermittently" ?
Back everything up to external SD, flash stock, reset the download counter with a jig, do a factory reset to get rid of any apps that might give whomever is repairing it a hint that you've rooted the phone & send it in for warranty service.
Not exactly rocket surgery :-|
ngsngn said:
So let say if i did go to the service center, what kind of reasons should i explain to them in order to 'fix' it?
Click to expand...
Click to collapse
MistahBungle said:
Seriously ?? How about "the speaker is failing intermittently" ?
Back everything up to external SD, flash stock, reset the download counter with a jig, do a factory reset to get rid of any apps that might give whomever is repairing it a hint that you've rooted the phone & send it in for warranty service.
Not exactly rocket surgery :-|
Click to expand...
Click to collapse
Ok, noted.
For now i shall monitor for another week, if it is failing again, service center shall it be.
Thanks.
Update: I reboot, re root, still fine... but when i nandroid backup finish, clear counter using jig, no sound again....
Probably loose wiring? Service center shall it be!!!
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
citronbitare said:
Until yesterday I used several different ROMs, without having any sound problem.
The problem started when I flashed Syiah kernel 1.2.6 (which might be a coincidence), while being on OMEGA-ROM. Thereafter I couldn't hear anything in phone calls any more (but others can hear me) on any ROOTED firmware or ROMs.
Reverting back to Syiah 1.1 (or switching to any other kernel) didn't help, neither did flashing any other rom.
Full wipe (including all storage space) solved the problem temporarlily. But after reboot no sound in phone calls again. Also changing the modem first helped, but the problem re-appeared after the first reboot.
Finally I flashed stock rom (LF2) via ODIN. Now the problem was solved - I believed. I could hear people in phone calls even after several reboots. But as soon as I rooted the phone with CF-Root AND changed some files on /system/media/ui the call sound was gone again after the following re-boot.
I reflashed again to stoch firmware via ODIN and now I have to live with an unrooted phone, which is not the worst thing in the world. But I really would like to be able to use custom ROMs again...
Anyone with similar experiences or with any idea about possible causes and/or solutions???
*** via Tapatalk ***
Click to expand...
Click to collapse
Really nobody who could help???
Can you record sound with other apps?
That should see if its a problem with just the phone apk or a more native problem.
Sent from my GT-I9300 using xda premium
Well, others can hear me but I can't hear them in phone calls. There is no problem with the phone speaker, because I can use viber without problems.
*** via Tapatalk ***
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Well, it shouldn't be hardware related, because there is no problem on unmodified stock firmware.
*** via Tapatalk ***
Zabalba said:
BUMP! I'm having the same problem!
I'm hoping it's not a hardware problem.
I wonder if any dev can chime in.
Click to expand...
Click to collapse
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
JJEgan said:
Kernel has sound modifications for last version 1.26
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
marcinrek21 said:
You have the same problem, but after flashing syiah?
If yes it is not coincidence i think.
Click to expand...
Click to collapse
Yes, it all started after flashing syiah 1.2.6. So maybe it's not a coincidence after all.
*** via Tapatalk ***
Zabalba said:
I noticed I had the problem intermittently when I first started using Foxhound on Saturday. Foxhound comes bundled with Syiah.
I thought it was something else all together. I asked in the Foxhound thread and only one other person +1'd my post. Today I switched to Omega hoping it the problem would go away and it was actually worse.
I was testing just now and every time I called my phone I could hear nothing on my handset or through headphones. Just in case I did't accidentally flubbed anything else up I unfroze all the TB apps I had frozen to see if it was working. Interestingly after defrosting and rebooting I can hear again. Attached are the apps I had frozen.
But this has not been the first time it was working correctly and then go back to not hearing calls.
Click to expand...
Click to collapse
For me it has also been an intermittent problem. Kernel changes, modem changes, wipes, etc often temporarily helped - but only for one boot cycle. A reboot always brought the problem back. Only on stock firmware I can always hear.
*** via Tapatalk ***
marcinrek21 said:
I strive for that. What I would do:
Flash stock rom
Factory reset via stock recovery
flash stock
cfroot
and then check if it is still a problem.
That is why the topic OMEGA asked that the next versions were the stock kernel.
That is why in order to avoid such problems.
Click to expand...
Click to collapse
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
citronbitare said:
I have done exactly that - and the problem is gone as long as you only do these steps. But modifying the system partition in any way (changing, deleting or adding files or flashing custom rom) brings you back to square one.
*** via Tapatalk ***
Click to expand...
Click to collapse
And may you have an earlier backup? Stock with cfroot or similar?
marcinrek21 said:
And may you have an earlier backup? Stock with cfroot or similar?
Click to expand...
Click to collapse
The sound problem is there even when I restore earlier backups. Now I am on stock firmware and everything is okay.
But I would like to use custom ROMs again with working phone call function, which is not possible for now.
*** via Tapatalk ***
This is the weirdest problem that I have seen here.
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
citronbitare said:
Just a status update. I have done some more testing and obviously what makes call sounds not to work is certain changes to the system partition (as compared to stock firmware).
In my case call sound works as long as I am on stock firmware (no matter what stock firmware; I have tested three or four different ones). If I root stock firmware with CF-root I still have call sound. I also can change kernels and it is possible to modify host files with ad-free.
However, as soon as I manually change or modify anything on the system-partition with root explorer or when I install custom ROMs the call sound disappears after the next reboot - no matter what radio I use. I also have tested the radio from the newest malaysian firmware which has surfaced today.
Click to expand...
Click to collapse
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Zabalba said:
Thanks for your testing!
Like I mentioned in my earlier post I unfroze all of the apps and I have not run into the issue. My phone is running Omega 5.2 with Siyah 1.2.6. I'm totally expecting the problem to return but it has not so far. I wish it was consistent and reproducible.
Click to expand...
Click to collapse
I'll keep my fingers crossed and hope that you have finally gotten rid of this problem. And thanks btw for asking Chainfire and Indie too look at this thread!
*** via Tapatalk ***
I got that problem myself, the only thing that really helped for me is to
flash my Stock Rom that where on the Phone out of the Box... since 2 Days
the Bug is gone. But havent tried any other Stock Rom.
I want to try Omega 6.0 Rom...(now)
I was thinking about flashing CF-Root and do those steps before custom:
1. Wipe Data/Factory Reset
2. Wipe Cache Partition
3. In Advanced ---> Format System/Cache/Data (someone tried this before?)
4. Flash the Rom.
My Question is for those guys like me where the only solution is to stay on
non rooted stock rom, have you tried flashing a custom rom with step 3. from above and still encounter the call issue?
I read somewhere that with step 3. the Phone is really FULL WIPE.
Sorry for my bad english :silly:
I'll keep it simple.
I have an ATT 4.5.91 2.3.4 rooted Atrix 4g.
No custom rom, recovery, kernel, nothing.
A few hours ago, my phone rebooted and ever since, Error comes up under the Wi-Fi as caption.
Bluetooth also refuses to work.
So I simply backed up my stuff via Titanium and did a factory reset via fastboot.
Problem is, the problem is still there.
I'm panicking, what should I do?
leews24 said:
I'll keep it simple.
I have an ATT 4.5.91 2.3.4 rooted Atrix 4g.
No custom rom, recovery, kernel, nothing.
A few hours ago, my phone rebooted and ever since, Error comes up under the Wi-Fi as caption.
Bluetooth also refuses to work.
So I simply backed up my stuff via Titanium and did a factory reset via fastboot.
Problem is, the problem is still there.
I'm panicking, what should I do?
Click to expand...
Click to collapse
Try wiping cache and dalvik, then flashing another compatible kernel.
~Sent from my Motorola Atrix 4G Badass~
Sounds like you have the very common wifi/bluetooth chip burnout. Its a hardware issue, no amount of changing radios or wiping is going to make a difference. Only option is to warranty claim it.
pre4speed said:
Sounds like you have the very common wifi/bluetooth chip burnout. Its a hardware issue, no amount of changing radios or wiping is going to make a difference. Only option is to warranty claim it.
Click to expand...
Click to collapse
Ugh. My warranty was over ages ago. Think I'll go buy another phone. Thanks for the help!
For those who may be looking at this later, hitting the phone at the column under the camera temporarily activates wifi( where the chip should be, go look at ifixt teardown if you want to know exactly know where it is), although this is not reccommended.
It's been a week or so that my phone freezes. If I leave it for some 20-30 minutes, it resumes normal operation. However these freezes are very frequent. This is happening on all ROMs I'm flashing. I even tried flashing pure stock ROM (ZSEMA1), and the freeze is still happening. Before I take it to the dealer (I live in a country where Samsung is not present, and the dealer will most probably need to ship it away for fixing), I'm trying to see if this happened with anyone else and how they managed to fix it. Also, other than resetting the flash counter, what do I need to do in order to take it back to complete stock?
Hi! I have the same problem. I rooted my phone and loaded clockwork recovery and flashed the camera app from 4.2
Now my phone randomly freezes (always when in sleep so I can't turn it back on). Only way to get it to start is to remove battery or soft reset. Any one else have this?
Is your phone around 6mths old, by the accident? Did it started recently?
I do not want to be bad news trumpet, but please read symptoms in this thread...
spamtrash said:
Is your phone around 6mths old, by the accident? Did it started recently?
I do not want to be bad news trumpet, but please read symptoms in this thread...
Click to expand...
Click to collapse
I had checked it, and indeed my phone's eMMC is VTU00M. However even the XXELLA ROMs are still freezing.
Have the same issue, random lockups. I have the SDS eMMC so Im giving the XXELLA flash a try...
vikeor said:
Have the same issue, random lockups. I have the SDS eMMC so Im giving the XXELLA flash a try...
Click to expand...
Click to collapse
I have tried Omega 38. Now I'm back on stock, XXELLA, and still getting lockups.
pushrodv8 said:
I have tried Omega 38. Now I'm back on stock, XXELLA, and still getting lockups.
Click to expand...
Click to collapse
Remove Ext SD Card .
Wipe phone / format sd card through CWM recovery .
Flash correct stock firmware via Odin .
Install no apps and test > fails return to service centre .
jje
pushrodv8 said:
I had checked it, and indeed my phone's eMMC is VTU00M. However even the XXELLA ROMs are still freezing.
Click to expand...
Click to collapse
You know, if your eMMc is already failed - new ROMs are unable to do anything. The nature of so called "fix" is the prevention only, there are several threads about SDS AFTER flashing XELLA/XELLC in General section.
SOLVED
Ok so since I'm in Qatar I flashed the United Arab Emirates stock ROM (XXELLB) and it's been 1 day without any hiccups. This is the longest the phone has gone without hanging, and I must say the it's REALLY VERY RESPONSIVE. Crossing fingers.
Hi all!
I recently bought used Samsung galaxy s3. It was shipped to me with Android 4.1.2. During customization i found out that when i'm listening to radio everything sounds perfect on earphones, but when i'm trying to listen to music stored on my SDcard or to watch a movie through stock players, all i can hear is nothing or noise when i turn volume on max. Then i flashed another stock rom but in 4.0.4 version. and then everything worked like a charm. I upgraded ICS to JB and i have the same issue. I wrote a mail to samsung and they told me to use *2767*3855# code, but it's not working. It would be a hardware problem but when it worked on ics and not on jb I realized that it has to be software related problem. Cas someone help me solve this mystery?
Go to settings, factory reset and test again. Perhaps follow sticky guides on flashing latest stock rom via odin on your pc.
Don't flash any older roms, they will cause sudden death.
factory reset didn't help :/
piotrek1488 said:
factory reset didn't help :/
Click to expand...
Click to collapse
Service centre if stock rom fails .
Thats presuming you have formatted the sd card .
jje