[Q] SGS2 In-call problem - Galaxy S II Q&A, Help & Troubleshooting

So I normally use a HTC device, but this time I need help with my brother's Samsung Galaxy S2 device. The problem is that from time to time, while in-call, i can't hear anything in both speakers, no matter what I do. The problem seems to come and go without me doing anything. I had it "fixed" in a service, but they just replaced the earpiece-jack module(which seemed to have worked for a day or two, but the problem came back). I have done numerous software resets, using the special recovery that samsung had provided (volume up+home+power), and had my software reinstalled at a service, but nothing seems to have worked. Does anyone have any thoughts on this? If you do please help me..:crying:

Related

[Q] Microphone not working

Hi, I'm a bit of a newbie to XDA, but I came across a problem which I browsed the forums and the internet for a few hours to solve to no avail. A few days ago I made a call to one of my friends who apparently couldn't hear anything from my side. I checked this over and restarted my phone a few times to see if that would fix it. Unfortunately the problem persisted, and when I tried to record any audio, all I would hear from the playback is noise. I assumed that it was a faulty flash of Trigger v2.8, but ODIN'ing back to stock didn't seem to fix the problem. I use the phone in Canada, and won't be visiting the US anytime soon, so I can't go to a T-Mobile booth to get it checked out. Is there anything I can do? Any help is greatly appreciated.
check settings and make sure you do not have anything off, that could happen, But if you can't resolve find a compatible kernel for your ROM and try flashing that. That usually will fix most problems.
Good luck
Thanks for the help, but I was unable to fix the problem using these methods. I'm starting to believe it is indeed a hardware problem, but I would want to receive some more input and where I should take it to be fixed if that's the case.

[Q] Unique issues; screen unresponsive, random reboots, freezing

Soo I have a Galaxy S II I9100. And it was great until something happened. Lord knows what happened to it. But I was running the latest version of Sensation ROM (1.6) smoothly. Then yesterday all of the sudden my phone kinda stops working more or less. The screen became unresponsive at times, the screen would activate on its own and then I would not be able to use it. After taking the battery out and restarting it things were OK for about 5 minutes.
Then after trying to open any sort of applications the Voice Command app would start and I wouldn't be able to exit out of it. After mashing the home button I could get out of it and then trying to open anything would result in a black screen (status bar active at top). So I figured maybe something went wrong with the software. I happened to have an update .zip of Sensation from 1.5 to 1.6, so I reflashed. This did not really help out. Even plugging in the USB cable was a 50/50 chance, Windows would tell me that the device is seemingly defective and sometimes it would work. But then trying to open USB Mass Storage was a big headache as well.
So I let it sit the night and then this morning I used Odin to flash a stock kernel. This seemed to help out somewhat, it made the system more stable and usable for a little bit. In the meantime I went to the so called "Samsung Cell Phone Service Center" in my city which turned out to be some repair shop for iPhones (go figure). After elaborately explaining my problems they said "must be a software issue". Which it is't. Anyways in the meantime I called Samsung America for direction, after talking to 3 different CS reps they referred me to call Samsung UK because that's where the phone was manufactured.
After that I did a factory reset and that made the issues even worse.
So I'm at a cross roads. I am probably going to be putting a call into Samsung UK tomorrow to try and figure something out.
Do a FULL wipe in CWM and then flash a stock rom. See if that helps. If not, then it's a hardware problem.
I had done that and then flashed a stock ROM which removed CWM, root, and the Sensation ROM. While that seemed to have helped, it would still randomly reboot (fewer than now) and the same issues persisted but less frequently. In the SGS2 stock recovery mode I did factory reset and wiped all data and cache and the problems are back and more frequent. I did take the phone to the beach but it was in a bag wrapped in a shirt..
could that have somehow caused this issue with the hardware?
I'm thinking that this is a hardware issue.
Yes, I think it is. One thing that comes to mind, did your modem change when flashing different roms? If not try a different modem. Otherwise it's really a hardware problem.

[Q] "Insert sim card" error :(

Hi
Recently my S2 just stopped reading my SIM when I was going to call someone. Since then it has refused to read my SIM, or any other SIM for that matter.
To fix this problem I've tried resetting the phone to factory settings (in 3 different ways ( hard-reset.com/samsung-i9100-galaxy-s2-hard-reset.html )) with no luck.
I've also tried installing alternative ROM's, but with the same result.
The phone was already rooted with an insecure kernel when this happened, so warranty is long gone.
Though, one thing I did realize was that even though I did hard-reset the phone several times, some of the settings on the phone remained untouched, like my locking pattern and a few other settings. Does this mean that hard-resetting the phone isn't really an actual hard-reset? If that's so, is there any way to properly 100% reset the phone?
In short; I'm running out of options on how to fix this. I refuse to believe it's hardware related, just because I'm stubborn like that.
Any help would be greatly appreciated (really).
Habitats said:
Hi
Recently my S2 just stopped reading my SIM when I was going to call someone. Since then it has refused to read my SIM, or any other SIM for that matter.
To fix this problem I've tried resetting the phone to factory settings (in 3 different ways ( hard-reset.com/samsung-i9100-galaxy-s2-hard-reset.html )) with no luck.
I've also tried installing alternative ROM's, but with the same result.
The phone was already rooted with an insecure kernel when this happened, so warranty is long gone.
Though, one thing I did realize was that even though I did hard-reset the phone several times, some of the settings on the phone remained untouched, like my locking pattern and a few other settings. Does this mean that hard-resetting the phone isn't really an actual hard-reset? If that's so, is there any way to properly 100% reset the phone?
In short; I'm running out of options on how to fix this. I refuse to believe it's hardware related, just because I'm stubborn like that.
Any help would be greatly appreciated (really).
Click to expand...
Click to collapse
You can refuse to believe in gravity too, but falling from high distances will still hurt.
If you tried more than one SIM in the phone and none work, but those same SIMs work in other phones, than more than likely, it is hardware related.
Did you check you imei?
078gregory brings up a good point. So if it's not missing IMEI info, THEN it's likely hardware.
Isn't it funny how everything suddenly works itself out once you cry out for help?
Today I've been trying around 10 different ROM's on the phone. Custom and stock. As one last attempt I gave a random ICS 4.0.3 march ROM a last try, and guess what. I got the SIM prompt. I can not believe it. So yeah, it's working now. I have no idea what caused it, but I believe the phone was stuck in flight mode somehow, and just needed an extra push to get out.
Either way, it's working like a charm now. Thanks for the replies though.
Habitats said:
Isn't it funny how everything suddenly works itself out once you cry out for help?
Today I've been trying around 10 different ROM's on the phone. Custom and stock. As one last attempt I gave a random ICS 4.0.3 march ROM a last try, and guess what. I got the SIM prompt. I can not believe it. So yeah, it's working now. I have no idea what caused it, but I believe the phone was stuck in flight mode somehow, and just needed an extra push to get out.
Either way, it's working like a charm now. Thanks for the replies though.
Click to expand...
Click to collapse
Don,t forget to press THANKS button on ctomgee
Hi people. I have the same problem Habitats decribes. Mi s2 is stuck in flightmode and cant get out! i have reset the phone in every kind of way but no succes. Now i read here on this forum that flashing my phone to ICS 4.0.3 can help solve the problem. I'm on 2.3.6 now. This flightmode thing happened al over sudden. I have done nothing strange with the phone. Its not rooted either. I was planning to go to a samsung servicepoint and let them check whats wrong. But now i read this thread and see that i can relate to this problem of Habitats. I think a also will try to flash ICS 4.0.3 and watch what happens. But theres another problem. KIES don't recognize my phone anymore so what can i do? Can someone please help me out? Thanks in advance
I'm having the exact same problem, could you please tell me which rom worked for you Habitats? Thanks in advance!
Update:Last tuesday i went to the vodafone store were they have a samsung service department also. I explained my problem to them but they don't seem to recognize the problem. Although i read that many people here at xda's and over the internet have similar issues with this phone.Strange! So they sent it to the repair centre. Yesterday i could see in the track and trace menu of the repair centre that my fone was ready and send back to the vodafone store. Status: Boardswap. So they swapped the whole board! Didn't know that the problem was that serious! So i hope i can pickup my galaxy s2 soon this coming week!! I can't wait!I'm on my old HTC Touch HD now. Its ok with the windows but on Android....Arggghh!! Whatsapp is a pain and more. Its so laggy!. I will give an update soon again!

[Q] Bluetooth auto connect issue. Please help!

I was on stock uk three rom and started to have problems with Bluetooth auto connecting to my car. It had been working fine since I got my phone back in June. I decided to try stock XXBLG8 to see if this helped. For a week it has been fine then other day upon entering my car my phone didn’t auto connect up. I have done some reading and found others having a similar issue but can’t really find a fix for this issue. My S2 worked perfectly for the whole year I had it. I have removed some app etc that were more recently installed but this obviously hasn’t fixed it. I don’t understand why it was fine for nearly 3 months and now this. I really don’t want to factory reset in case the issue is still there afterwards.
Anyone know why this is happening? Is it a bug with the phone?
Anyone got any idea about this?

[Q] Calling problem- caller can't hear me and vice versa

Hi,
I own a SGS3 and I couldn't find the answer to my problem anywhere. So basically I had Cyanogenmod on my S3 and one day somebody called me and I couldn't hear them (they couldn't hear me either). I tried putting them on speaker and still nothing. I thought that maybe my phone was damaged, so I tested the mic and speaker on Skype. Surprisingly, it worked perfectly. I concluded that it must be a software problem, so I tried going back to factory settings - nothing happened. I just got my phone back to the stock OS but the problem is still there. Any help, please?
Thank you in advance!

Categories

Resources