My S22+ suddenly started to have a seriously distorted speaker which meant ringtone and notifications sounded like mud. I thought it might be a software bug, but then realized if I pressed down on the middle of the phone, everything was good! Some quick Google searching showed that I was not the only one having the problem.
Must be a build quality issue for Sammy, but of course they refused to admit there was any issue and wanted me to get it repaired. I've decided to send the phone back instead and get my trusty S20+ back. I just don't have time to be inconvenienced by their problem.
have you tried it in safe mode?
think its been fixed in update ? mine was doing it when fist got it but now seems ok
funny mines started to do it again after few months and latest update but then went back to normal again ????? not even cold so cant blame that
Related
Hiya everyone.
Woke up this morning and switched on my phone, it seems to be in low graphics mode or something. You know when you start windows with no graphics driver? well my screen is like that. Colours are washed out...it looks awful.
Was working fine last night, didn't do anything that would cause anything like this over the past few days. Have not rooted or debranded or anything.
Because I got my Galaxy S2 last week O2 will pick it up and doorstep replace it but would like to know if I can do anything myself.
Anyone have any ideas?
Much appreciated
Something just screwed up very bad, if i got it right, your phone is still with warranty (not rooted?) in that scenario, your best option is to go back to shop and pretend to have it replaced.
If you are rooted, you may try to flash a stock rom over it, but this will not solve any hardware fail, just if the problem is generated by the rom.
Connected to wifi, there were 2 updates from samsung, ran them and upon reboot everything was back to normal.
Pleased it's fixed but fingers crossed this isn't the start of things to come.
So this has been happening randomly on calls for about two weeks now. I'm still on Stock everything and would like to know if this is a known problem, if something is wrong with my phone, or if there is a fix? I'm past the point of returning and getting a new one and plus, I have grown atattched to this phone LOL.
I've tried hitting speaker and then turning it off but that doesn't work. Tried ticking mute and then unticking it, not working either. Reboot doesn't work. Resetting back to stock doesn't change it either.
Thanks to all.
AJ
Sounds like a typical ATT phone call. Would you and the person on the other end both happen to be on speaker phone? I cannot have a call via speaker to my wife if she is on speaker (which see insists on using) - there is too much voxing going on, I only hear every couple of syllables.
T
Sent from my SAMSUNG-SGH-I777 using XDA App
Not a speaker phone call. Seems like it happens mostly when I make calls from speed dial from my homepage screen. I can't conf
irm that last bit though lol.
Another question is this....I just turned my phone completely off and it had 42 % battery. When I turned it back on it now has 22% left.....what in the world is going on lol???
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
asjdwf said:
Would I be better off reverting back to 2.3.4? Or just getti
ng another sgs2?
Click to expand...
Click to collapse
I need more details to say this for sure, but I THINK you may be having the same issue I had. Not many people seem to have this issue (only seen a handful across a variety of forums). So if you happen to be a fellow sufferer, then welcome to the club!
My problem was:
After the 2.3.6 update (UCKK6), the person on the other line had trouble hearing me because my voice cut in and out frequently, yet randomly. On my end though, they came in nice and clear. I often had to deal with people hanging up on me because they thought my call dropped or that I hung up, or had to deal with a lot of people repeating "hello? hello!? You there!?" as I helplessly tried responding and not being heard.
My Solution(s):
1) keep the 2.3.6 update, but flash just the 2.3.4 (UCKH7) modem. Everything on your phone will work fine, but you will get the following FALSE warnings (FALSE as in the phone says it can't do something, yet everything works fine anyways. These are only based on first-hand experience and may not happen to you.)
a) upon boot (not wake/unlock) there will be an error notification about you not being able to access your external memory card due to security reasons... don't worry, its bull.
b) when using your phone as a mass media storage device, you will get a notification about the mass storage function not being able to work... this message is also bull.
2) Or you can just completely return to 2.3.4 (UCKH7) and either ignore the update prompts or freeze the process until a newer update that hopefully fixes our problem (or ICS) is released.
I did (1) for about 2 weeks then did (2) after reading all the battery complaints blamed on UCKK6. It reverted just to play it safe with battery life (plus they say that "if it ain't broken, don't fix it" and for me, UCKH7 wasn't broken and the update definitely broke it).
Wow, that sounds identical to me except its they can hear me but I can't hear them LOL. I reverted last night with odin one click downloader and the stock kernel for battery life so we will see what's going to happen today. Is this a phone problem physically or is it software?
Thanks
AJ
For me, its a software issue (modem to be specific) because it only happens on UCKK6 (and the leaked UCKJ1, UCKJ2, and UCKJ4) and when on UCKH7, my calls are as clear as a LAN line.
I say that if the problem still exists now, then its hardware. In that case, try contacting Samsung for a replacement if your ATT warranty is up. You could try ATT too because its a defective phone and they may still do something.
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
I googled vibration not working galaxy s2.
Found this but I didn't watch it as I am not on wifi.
http://www.youtube.com/watch?v=3JA3PXNYjJM
gerbs said:
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
Click to expand...
Click to collapse
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
jcordova23 said:
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Yeah, already called att for a replacement and its on the way. Finally decided to give up after getting it back to 100% stock (kernel rom bl etc).
I literally tried everything. But in the end it makes sense that it is a hw problem since so many others have run into it too. Poop.
i watched the video you showed. i started to mess around with my settings while i inserted my headphones on. Somehow, everything is fixed but the vibration is not as strong as before.
Furthermore, my aux does not work with this phone sometimes. It would need to be connected a certain in order for it to work.
I probably dropped my phone while I was working out while i have my headphones on. The connector probably got messed up in the process.
I might need to send my phone in for a replacement. Since i'm not under warrenty, i might send my phone to a lab. I'm pretty sure they can do something about it.
iichrisphamii said:
I might need to send my phone in for a replacement.
Click to expand...
Click to collapse
The vibrator turned out to be a hardware issue for me as expected, fyi.
Right guys, I have been on the Original Development section asking similar questions and had good suggestions, but here is the problem in a lot more detail as I don't want to spam the section with the same problem and get literally no reply as people are busier with other things on there. Basically the phone has it's two speakers, the earpiece at the front and the speaker at the back both of which are working and functional. However the problem lies in the phone calls. I bought the phone on stock firmware, latest UK generic update it was and everything was fine. I decided to root the phone and flash PA 2.13.1. As soon as I did this I came across a few issues, one being NFC not working and the current and seemingly unfixable issue that I have with the phone calls where, as I receive a call and answer it the microphone doesn't work, I can't hear anyone and they can't hear me. Both on loud speaker and through the earpiece. It's as if they disable when a call comes through. But when I hang up or they hang up I can hear the end call tone, the beep coming through the earpiece. So I know that it works. The same goes for loud speaker, however I already knew that it still worked as I can play music through it cleanly. It's in perfect working order.
I've tried several solutions, including flashing new modems, RIL etc. Flashing 3 part software. I have yet to try flashing the 3 part software with a .PIT file, like mx.pit as I simply can't find that file (if someone would be as kind to link me it) anywhere. I'm currently back on stock XXALE8 UK firmware. The problem is still there. I STILL can't make a phone call without this annoying thing happening, and as I said, the problem wasn't there before I flashed PA. It's so f****** annoying as I followed the instructions perfectly, I mean, I've been using android since 2009 and rooting and flashing is nothing new to me. I've never had an issue as severe as this one.
Anyways, thanks in advance for any suggestions you guys can throw at me, I know you'll all agree when I say the GS3 kicks ass and you'll know my pain when I tell you it's being a broken piece of crap haha!
EDIT: Right, I have made another definite discovery with this problem! It's to do with my signal. When I answer a call or make a call, it appears to connect to the caller for roughly about 0.01 seconds as it says it's connected, but then it hangs silent for a while, about 13-15 seconds before disconnecting saying there is no service in the area. Give it another five seconds and the signal reconnects. It is the exact same effect you would have if you were on the phone on the train and went through a tunnel, it would say you were connected when you aren't. Does this make sense, anyone know what the cause of this could be?
I cant find a straight answer anywhere. I bought a Nokia Lumia 920 a week and a half ago and I'm on my third handset. This is because each one has been apparently faulty.
The first handset I had was great until the screen started to flicker/shimmer to the point where it hurt to look at it. I got that one replaced with a second device, which was better, up to the point the flickering returned and it froze, shut off and wouldn't turn again. I got this one replaced with a third device and this one was flickering/shimmering straight out of the box.
I have looked on google followed tips and tricks to try and get this phone working but to no avail. So I just wondered if you guys knew of anything im missing or a ROM I can install to fix these problems or future updates which will fix these problems because I am going into the EE store tonight to get my money back. I am so annoyed because its a beautiful phone and I would like to keep it.
Thanks
Sam
Phesefalus said:
I cant find a straight answer anywhere. I bought a Nokia Lumia 920 a week and a half ago and I'm on my third handset. This is because each one has been apparently faulty.
The first handset I had was great until the screen started to flicker/shimmer to the point where it hurt to look at it. I got that one replaced with a second device, which was better, up to the point the flickering returned and it froze, shut off and wouldn't turn again. I got this one replaced with a third device and this one was flickering/shimmering straight out of the box.
I have looked on google followed tips and tricks to try and get this phone working but to no avail. So I just wondered if you guys knew of anything im missing or a ROM I can install to fix these problems or future updates which will fix these problems because I am going into the EE store tonight to get my money back. I am so annoyed because its a beautiful phone and I would like to keep it.
Thanks
Sam
Click to expand...
Click to collapse
Sounds to me you have something in your area causing it. Maybe a very strong electrical/magnetic field. Just seems odd three in a row would have the same issue and so far I am pretty sure you are the only one to report this since you found no answers as well.
Keep in mind that per FCC rules your phone must accept interference but may not cause interference. So if there is something in your area causing it then you are out of luck as it is not an issue with the phone.
Unless its the entire area of bristol or im just magically electro magnetically charged i dont think its that. I'm not the only one who is getting this problem, I said I cant find a definitive answer. I cant find an answer about updates or patches that would fix this problem. I understand that phones and radiowaves are very susceptible to interferance but this problem is happening in different places and at different times.
I've managed to find that the shimmering will happen more while multi tasking so having headphones plugged in, music and trying to access the xbox app.