My mom's S4 has been a good little workhorse for a year now, but recently it's started acting bizarrely. At random, when she dials, nothing will happen. It will say dialing, the call timer will start, but she can't hear a ringing tone, the caller, and the caller can't hear her. I've looked this up, and it seems to be a common enough problem for S4 users, with no solution that I've been able to find. I've tried to see if something is jamming the headphone slot, but nothing is in there. The only way we can get calls to work again is to reboot the phone, and that works only around half the time.
At the same time, any time this problem is present, Wifi won't auto-connect, or connect at all. It will recognize the hotspots around us, but it just marks them as "saved". If I try to connect, it attempts it, then reverts back to saved. This fixes itself after the reboot as well.
Does anyone know what's going on? Is this a hardware problem that I'll need to replace the handset because of? Will a factory wipe or a ROM fix this? I've been wanting to try a clean, easy ROM for her, so maybe this is the time? Any help would be greatly appreciated.
On the subject, any suggestions for ROMs? The Google Play Edition one looked nice, but I didn't know if that came with any significant down sides for her. Thanks in advance!
greycobalt said:
My mom's S4 has been a good little workhorse for a year now, but recently it's started acting bizarrely. At random, when she dials, nothing will happen. It will say dialing, the call timer will start, but she can't hear a ringing tone, the caller, and the caller can't hear her. I've looked this up, and it seems to be a common enough problem for S4 users, with no solution that I've been able to find. I've tried to see if something is jamming the headphone slot, but nothing is in there. The only way we can get calls to work again is to reboot the phone, and that works only around half the time.
At the same time, any time this problem is present, Wifi won't auto-connect, or connect at all. It will recognize the hotspots around us, but it just marks them as "saved". If I try to connect, it attempts it, then reverts back to saved. This fixes itself after the reboot as well.
Does anyone know what's going on? Is this a hardware problem that I'll need to replace the handset because of? Will a factory wipe or a ROM fix this? I've been wanting to try a clean, easy ROM for her, so maybe this is the time? Any help would be greatly appreciated.
On the subject, any suggestions for ROMs? The Google Play Edition one looked nice, but I didn't know if that came with any significant down sides for her. Thanks in advance!
Click to expand...
Click to collapse
Sounds like a factory data reset is long over due. It should fix any issues thats been going on. If not I would take it into Verizon to get looked at, or call to get a replacement.
Related
This is really frustrating! :evil:
The signal on my phone shows good reception, but meanwhile the phone is off. When people call me, they get forwarded to my voice mail, although the phone never rang in the first place!
Does anyone else have this problem, and better yet... how do you fix it?
Thanks!
can you call from it ?
I usually don't know that it's off and 'in disguise' when it happens. I only find out later when someone tells me that they called but my phone was off. I check the phone and it's on. I try dialing and it doesn't work, so I hang up and try again, and... presto! It works again!
How weird is that?
I actually know two other people who are facing the same problem, but none of us know how to fix it.
maybe a newer rom ?
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.
I've been searching around for a solution to this issue for a long time, but seems like I'm the only one suffering from it.
My Telus S3 works great with my 2005 Acura TL for a few weeks, and then suddenly, after I go into the car, the bluetooth will connect automatically, but the Handsfree Links system within the car will stuck, showing a "In Use" message on the HUD, as if I'm making a call. And the only voice commands available are: Transfer, Send, Go back, Cancel, none of the commands go anywhere, even the go back and cancel wouldn't do a thing, as well as the "Hang up" button on the steering wheel. It will stuck in that status for anywhere around 5-20 mins, and then it'll hang up by itself and everything works fine again, I can make phone calls and everything.
The only solution I found is to go into my phone and call someone, before the call even connected, I hang up, this will "reset" the call status, and it won't stuck anymore. But this is very annoying to do every time you entering your car...
Un-pairing, delete and re-pairing doesn't help either. As soon as I pair my phone to the car, it'll stuck. I tried my old Galaxy S on my car after this happens, it works like a charm. And before I got my S3, I've been using my S1 with my car for more than 2 years and never had a problem.
So this definitely seems like something is wrong with my S3, I talked to Telus support, they said they never heard of this problem before, and they suggest me to do a factory reset, but it'll be a pain to reinstall everything so I haven't tried it yet, just want to hear what you guys think first.
EDIT: sorry, just realized I posted on the wrong forum, please move this for me, thanks.
So nobody has this issue?
bump
Just found out my friend using a S2 is having a similar issue with his bluetooth handset, and yet there's nobody on xda-developers has this problem?
hmmmm....
Sent from my SGH-I747M using xda app-developers app
There's loads on XDA with issues with the bluetooth, it's the reason this will probably be my last Samsung phone as they simply can't get it to work reliably and the same issues keep cropping up on all their models.
kitch9 said:
There's loads on XDA with issues with the bluetooth, it's the reason this will probably be my last Samsung phone as they simply can't get it to work reliably and the same issues keep cropping up on all their models.
Click to expand...
Click to collapse
Yes i can see that, but it seems like people are having issue *pairing* the phone to the car, but my phone pairs with my car every single time, never had a problem with that, it's just after pairing, the car got stuck in call mode for 5-20mins..... :crying:
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?
Hey Folks,
i ran into some really weird, yet strange Problems with my Honor 7. Let me tell you what happend:
I used my Phone on B140 for more than 2 Years without any Problems. Now i upgraded to B396 (Removed Root+ChineseTWRP, Full Update to B396, then installed TWRP+SuperSU), and used it afterwards without any Problems for like a Week or so.
Then, i was on my Way, looked something on on Facebook, turned it off, after 2 mins wanted to turn it on again - no Reaction. Totally nothing Tried booting it up Normally, to Recovery, To Fastboot - with and without plugged USB to PC, absolutely nothing happend. Had it on Power for like half an Hour, nope. I was shure it died.
The morning after, i just pressed the Powerbutton as a way 2 say goodbye - Empty Battery Sign! Wtf?! I was able to charge and use it again. Unfortunatly with some minor Problems.
- Whatever i try, when calling, i can clearly hear the other person, but the other part cant hear me. I tried it both with headsets and normal, in- or outgoing call, doesnt matter. Generally the mic is working, though. Was able to record my voice and play it back.
- Bluetooth aint working anymore. When i try to turn it on, the switch stays in the right position (doesnt change the color anyway), and afterwords its flipping back. Oh, and when i look at the "about"Section, under Bluetooth Mac it states "not available".
So. What the h*** is going on there?! Like i said, after upgrading to B396, it was working for at least a week without any problems, without the problems described above. So i highly doubt its a general problem with the upgrade/flashing. But what else?
And, any advice how to a) fix and b) prevent further failures?
Of course it would be best to know what initially caused those problems, but i really cant tell. Anyone any ideas?
Like anyone else of course, one needs a reliable phone. I mean, im happy that i can at least communicate over IM (yes, 3G/4G works without any Problems). But i'd love to make calls again, to e.g. tell my boss id be slightly belated or let mum know everythings alright :laugh:
So, any Idea what caused that, how to solve and prevent that is highly appreciated!
Greetings and Thankin u in advance!
Folks, i still have that strange Issue/Behaviour (though, of course, in the Meantime im using another Phone ).
But think that should be possible to totally, absolutely, reset the Phone, and trying to get rid of those Problems. Too Sad to see the Phone collecting dust, where it might be a great Device for a Friend.
What i did by now:
Unroot
Reflash Fastboot recovery, boot, cust, system.
Factory Reset
Update.zip in dload
But there is still no Bluetooth-Adress available, when calling i cant hear the other Person.
It somehow seems not to completely reset the phone - there are still user-data on the Phone.
As i really dont care about those data - is there something else i can do above fastboot flashing those files mentioned above, to absolutely start from a scratch?