I updated to 5.1.1 and all seemed well, but today, my phone all of a sudden is calling people on its own. In one case I was speaking to someone on the speaker phone and watching the screen and it began calling a phone number while I the call was in progress. I am not sure that it began with the update, as I have possibly seen this before, but I could never pin it down. Has anyone seen this and short of a factory reset, are there any suggestions? Thanks.
Related
Twice in the last hour I've made calls on the phone, and twice the call has started fine, as you would expect, but then, the call goes completely garbled. An unintelligible digital mess.
Any ideas why, and has anyone else noticed this problem?
Sorry for the bump mods.
Has no-one else experienced this issue?
Could it be a carrier issue rather than the phone?
I just found it weird that yesterday two or 3 calls I made yesterday, in fairly close succession all had the same issue - ie garbled and incomprehensible audio.
Maybe I need to send the phone back?
I have the same problem on mine, but less frequently. It sounds like a Transformer and then I get cut off.
I'm with 3, so I just assumed it was a carrier problem rather than a handset problem.
Im on T-Mob and Ive got it 2-3 times as well!
Hey guys,
Something really random just happened to me today. I was sleeping with my VZN Galaxy Nexus on my night stand when all of the sudden I heard a noise coming from my phone. I woke up and looked at it and noticed it was making a call to some number that starts with a "+2" and it was about 23 seconds into the call. I heard it say something that sounded like "Please wait while we prepare your photograph".
Needless to say, I freaked out and ended the call... but when I went to the call log that call was not there!
Has anyone had this happen to them or know what could be causing this?
Curious that you mention this; I was about to make a thread on the topic. Mine made a call around 6:30 AM CST. The number is *22899 and it's a number that you dial to update your PRL ("Please wait while your phone is being programmed"); it's the same as dialing *228 and hitting option 2. That said, I've never experienced a phone making the update by itself before.
Sent from my Galaxy Nexus using XDA App
Very weird indeed. That's around the same time my phone made the call... I guess I could see how I heard "prepare your photograph" instead of "being programmed" since I didn't have the phone up to my ear.
Anyone else?
Just a quick note, I noticed on Engadget that Verizon is having some data outages across the US. Maybe this has something to do with it?
http://www.engadget.com/2011/12/21/psa-verizon-users-reporting-data-outages-across-the-us/
Same here but mine happened at like 4 am or something. I had no idea wtf was going on...
Might be. I was going to add that I wasn't able to connect to the network at all this morning (though I've had an intermittent 3G signal just recently). I didn't even know they could remotely initiate a call like that; sort of creepy.
This just happened to me. Call is not in my recent calls list, it just automatically conencted. FYI I'm in the DC area so maybe its just something Verizons doing in different areas.
Just happened to me as well @ 2:30am PST. Happened twice actually. I ended the first call and the second one completed activation and hung up on its own. Odd.
Just happened to me TWICE again last night at 3AM... I had Data turned off completely too.
So I ended the call and 1 minute later it did it again.
I ended the second call and put it in Airplane mode for only a few seconds, then it never dialed any more last night
(I turn off Data when I go to sleep at night)
I've been having an odd issue with my GSM Gnex lately (probably past month or two). During a phone call, after a short amount of time (usually within 5 minutes), the outgoing and incoming audio will quickly fade away with some garbling. I can call back and have the audio return, only to die again. I don't make/take many phone calls, so I don't have a lot of data on it. I can't say if it happens on every phone call, but it has happened enough times that I know it's a problem.
This has persisted through various clean installs. I'm not sure, but I think it started with a ROM whose name I can't remember, then in CM 10.1 for a few weeks, and it just happened again tonight, after a clean install of the stock 4.3 JWR66Y image directly from Google last night. Although I did flash the newest UGLL1 radio, as well as SuperSU for rooting.
I'm thinking it's hardware, but I don't know enough to make a decision on it; I've had this phone since last summer.
Sorry for the vagueness and lack of detail. Does anyone have any ideas? Experiences? Things I could test?
Thanks in advance.
Bump.
EfemaN said:
Bump.
Click to expand...
Click to collapse
Bumping again. Forgot about this thread a while back.
I am not entirely sure if it is an android bug or specifically samsung. Anyway on my s5 and my N4 if I go to make a call occasionally it will say call not sent...when I go to redial the number the phone has already chosen a different contact at random to call...to make the issue worse the screen will then blink on and off in succession preventing me from stopping the random call...this seems to happen once or twice a week...I have already disabled the gesture option that calls people so I am at a loss here...anyone else experience this?
Not an Android bug. I've had it where the phone would try to connect and give up, but the second attempt would go through. That's a reception issue though.
It sounds like your software is glitch in for some reason. Usually a factory reset will fix this (unless you rooted and did something to alter the system, in which case, your alteration could be the cause). If not, then warranty time.
Sent from my Samsung Galaxy Note 4 (sm-910a) using Tapatalk
Yes, I have this too. Really annoying, happens every few weeks, and seems to go away after a restart.
Sorry to bring an old thread back to life but, has anyone figured out this problem? This happens on my Verizon Note 4 as well, so it is not carrier specific.
Everywhere else I have searched no one has an answer.
Just usually a call is placed. Then a quick message pops up with "Call not sent". Then another contact gets called instead. For me I don't see any pattern to how the wrong contact gets chosen.
This happened in KitKat and now is happening still in Lollipop.
Also I did a factory reset when I upgraded to Lollipop. Any ideas?
Edit: Just thought about this. Do any of you who have the problem use Google Voice?
I haven't been on here for a while and apologies if this is has already been covered I did try a search but couldn't find anything specific, I've had my 6 pro for a while now and its running (SP2A.220505.002) build I'm still having constant call issue's with this phone, I'm reaching the point where i might have to fire it back at google as I'm suspecting a Hardware issue.
Virtually every time I make a call it disconnects, yesterday during a 15min call to my missus, it disconnected 3 times. I've tried 5g default, 4g default, wifi calling on and off, nothing seems to make a difference, I've read that the update should have fixed this, but for me it hasn't, has anyone managed to sort this out if they've had the same issues ? Or is my phone dodgy, based in the UK if it makes any difference, thanks...