on 30-07-2013 14:19
on 30-07-2013 14:19
I received my Galaxy S4 on 27th April.
Two weeks ago all in call sound went. Movies, games and music worked fine but I cant hear caller and caller cant hear me.
I checked volume (d'oh), reset the phone, factory reset the phone and reflashed stock firmware. Still didnt work.
I sent the phone back to O2 and it was repaired (by Chris apparently). I was informed of the repair steps and the phone was back to me working within the week.
I checked it and everything was fine. Re-installed my Apps and everything was fine for a week or so.
Now the same thing has happened. No sound in call but fine everywhere else.
I've logged it with O2 again and its going back in to be repaired.
I'm not a phone noob and but I've not flashed or rooted or dropped this one! I've kept it on stock and have searched the internet and forums but cant find any solutions (so far just reboot / WCDMA only / Noise Reduction Off).
I cant believe I am the only one experiencing this and why wasnt it fixed first time?
O2 have been pretty good to be fair but if this repair doesnt resolve it I will expect a new phone not a third repair!
Any thoughts?
on 19-08-2013 13:53
Okay so the phone went back to o2.
Got a call from the technician saying No Fault Found. I explained what the problem was and he went away, flashed the phone and returned it. Exactly what I've done both times.
So I've had the phone back a week or so and havent installed anything related to calls or the speakers. Guess what ..... The in call volume has gone again.
This is the third time.
I've just been on O2 chat to Sagar and he suggested buying an O2 Pay as You Go phone.
PARDON! I'm on a 2 year contract spending over £50 a month and this is the best advice they've got!
Can anyone on hear please suggest how I escalate this as I am really not happy with O2's customer service or technical aptitude.
Each time the in call volume goes, it goes in for repair. They find nothing wrong, even though I've proved the issue in store. They flash the firmware and nothing else (allegedly) and it works again ... for a week.
This is a £500+ device and this wouldnt be acceptable for a TV or Car .....
on 19-08-2013 14:11
on 19-08-2013 14:11
I understand that after a third repair for the same issue they will offer you a replacement phone.
on 19-08-2013 14:14
on 19-08-2013 14:14
You might want to make an official complaint to the independent complaint review service here:
19-08-2013 14:17 - edited 19-08-2013 14:18
"I understand that after a third repair for the same issue they will offer you a replacement phone."
Even though they stated No Fault Found (even though I proved there was a fault?).
"You might want to make an official complaint to the independent complaint review service here:
Thanks for the link ... I may well do that.
on 12-09-2013 11:40
I've had the same issue too.
I just got my phone back from Samsung yesterday after them taking two weeks to fix it. And guess what. The same fault has occured again less than 12 hours after I got it back. Now I have to send it in for repair again. That's going to be a whole month with no phone. 😞
Did you get yours fixed in the end?
on 31-10-2013 16:42
I'm going to revive an old topic to speak in-depth about this issue. I've scoured the web to find an answer to this problem and not many people seem to have one solution. People seem to have one of two underlying faults.
The first fault is relative to the headphones being plugged in (the headphones icon shows at the top of the phone when they're not plugged in) and this can be worked around simply by using the app SoundAbout. If this is your issue download the app and follow the instructions in the SoundAbout forums to overcome this. They also do a widget to help toggle your headphones.
The second fault (the one I'm faced with) is a little bit of an unknown and seemingly a software/network fault. Having spoken with David at SoundAbout, he has said that this issue occurs on both Verizon and Sprint networks, but can be worked around in the mobile networks menu or going through various prompts from the providers to update the phones to accept communication from the cell towers to solve the sound issue.
Now, I have not seen anything from O2 detailing this issue and frustratingly one of the simple fixes that came in the form of old firmware on the S4 was to switch to WCDMA, but the latest firmware doesn't have this option, and switching to 2G only doesn't do anything either. The question I have is, does anyone know anything that I don't to solve this problem?
Also, before anyone asks. My speaker and headphones work fine, my earpiece also works when doing the #*0*# debug mode, so to me this seems as if this isn't a hardware fault, so there MUST be a way to solve it, I just want to know how?
on 27-12-2013 11:58
Reviving your revived topic haha.
Have you managed to find out a solution for the problem? I've been looking everywhere on the net for answers but having no luck. Some say it could be apps eg. WeChat/Viber causing this software glitch. I don't want to send the phone off to Samsung for repair and be told they can't reproduce the problem
Thanks!