Hi all, not sure if this is a common problem but just wanted to see if it was and if there has been a fix. I have a i9023 on T-mobile USA. Right now, I have bootloader unlocked and flashed the original 4.1.2 image from google. The problem occurred before unlocking or flashing anything. I was hoping that would have fixed it.
So I notice that whenever I end a call, the phone's signal immediately drops (grayed out and no blue or usually the outline of the right triangle only). When that happens, I can't make any calls out or receive any calls until the signal comes back up. So, when I hang up, I can't make another quick call. It stays like this for about a minute after each end call. Happens about 90% of the time.
I'm not sure when this problem started but I did update from honeycomb to ics then to jelly bean about 2 or 3 months ago via OTA.
Should I flash a new radio, request for a new sim, or something?
Related
I've got some serious issues with my Nexus 4, I've found posts with similar problems but not exactly what I have. I'm at a loss what to do next so any advice would be much appreciated.
I bought a N4 around March this year, direct from Google, and connected it to TPG Mobile here in Australia which uses the Optus network.
It was fine until about the end of May or beginning of June where it started losing signal regularly. First thing I noticed is it would start dropping calls and displaying "No network available", the triangular status bar at the top would go blank (completely black, not grey) for about 30 seconds, then it would return to normal signal and I could make calls again. However it would do this every few minutes, whether I was on a call or not, and each time it would last roughly 30 seconds and then return to normal.
Around the same time I started to receive SMS on either a delay, or they'd arrive on-time, but then keep sending multiple times for about the next hour.
I rang Google, they got me to go through recovery mode, then it worked fine, for about 24 hours, before it started again. They sent me a new device, which did the same thing within hours of activation, so I requested a 3rd device. At the same time I thought it might be the sim card, so I got a new one of those too.
My 3rd device and new sim card worked perfectly for about 3 days then the same problem started. Factory resets etc seem to fix the problem for either minutes or hours, but never permanently.
Then last week I noticed further weird symptoms, I started getting the usual sms to say someone had called and left a voicemail, however my phone never showed any sign of a call (visual, audio or missed call in the call log). I confirmed with several people who tried calling me and they confirmed the phone rang on their end before going to VM. I tried it myself from a landline and it randomly rings or doesn't ring on my end, however I also noticed when I hung up on the landline without answering my Nexus 4, it continued to ring indefinitely, ie. it hadn't registered the caller hung up.
My provider assures me there isn't an issue in my area, my wife uses the same provider (with an iphone) and has not had these issues. I can't swap sim cards with her though as she has a full-size sim. I tried another sim with my phone for a few hours and it worked fine, however my phone with my sim will sometimes go a whole day without issues so it wasn't long enough to truly test it.
I've deleted all apps that might somehow affect it and the hasn't helped either.
Basically I'd like to know is this likely to be a phone issue, and I pursue the issue with Google, or some sort of network/sim issue and I pursue it with my provider?
So this is a very minor issue (I think?). Anyways, the call log on my Nexus 4 displays incorrect times. I am running stock 4.2.2, unrooted. (I had it rooted and unlocked, but I relocked/rooted it)
So what I mean is if I call someone the call log will say I called them we'll say 10 seconds ago once the call ends. If I go back into the call log a couple minutes later it will still say I called the person 10 seconds ago. If I make another call it'll update the call log. This isn't really a big deal, but it's still kind of odd. I'm wondering if this is a normal issue perhaps? When I was running CM10 on my old Galaxy S2 it did the same thing.
Thanks for the help guys.
I've been using AICP for a while (Marshmallow), but haven't done an update in a while. By a while, I mean that I don't think I've flashed anything in weeks. Suddenly, I cannot make or receive calls today. Yesterday I made a number of calls just fine. I checked all the standard possible causes, dialer apps, default apps for phone, etc. After no success, I decided to flash back to stock.
Now I'm on stock 6.0. Same problem, cannot make calls. All I get is a screen which says "dialing" until it makes a tone sound and hangs up, never rings anyone. My phone never rings or responds when other people call. I do have full bars and service, and my APN is set up properly with AT&T in the USA. SMS and Data work fine, and so does WiFi. No other problems at all with the phone. I've had it for about a year and a half with no real hardware issues other than a loose charging port. No drops, no cracked screen or anything.
I'm wondering if anybody has a clue about what the problem with my phone is. I'm willing to generate and provide logs if there's a way to do that which could show the issue.
EDIT1: Derp, just tried the SIM in my girlfriend's phone. Seems to by my sim card. I'll go to AT&T tomorrow and report back here if the issue is fixed.
Hello!
I just re-rooted my Samsung S4 phone to Android 6.0.1 ResurrectionRemix and so far everything works great! Just one small problem...I can make local calls but when I try to call long distance it doesn't complete dialing and give me a "Call Ended" without completing the call.
Any ideas? Are there any threads that you can point me out to?
I've rebooted, tried airplane mode on and off. Unless I have to flash again??? Any ideas??
I would updated the modem and bootloader.
If that doesn't work, then clean flash another ROM to see if the same thing is happening there.
This post is now solved
It turns out that the whole area I was trying to call by long distance the telephones were down. It had nothing to do with my Android OS!
Last week I flashed the .23 firmware along with Santod's stock .23 ROM. Flash seemed to go ok, I did a full wipe prior and just set up the phone from scratch. Right away, I started having voice calling issues, both incoming and outgoing. Some incoming calls, though not all, wouldn't ring and I'd get notified of voicemail. For outgoing calls, about half the time the call would drop during the Dialing phase. For both incoming and outgoing calls, those that actually went through, quality was such that both sides couldn't be understood. A quick call back, and sometimes the quality was ok. (if the call actually went through) During this time, I also noticed that the phone was dropping to 1x during the call, and I no longer had working HD Calling to other Verizon customers. I thought it might be the tower I was connecting to, like maybe VoLTE was down, but the issue was present across town.
I tried redownloading (checked hash) and reflashing both firmware and ROM, same issue. I tried using the .23 RUU, same. I tried using the .20 RUU, same. While on .20, I took the OTA back to .23, same. I even did the RUU back to the last Marshallow ROM. When I did that, I'm having the same issue, except now I'm stuck on 3g instead of 4g. (still drops to 1x for calls, drops, poor quality) When that didn't work, I took OTA's back up to .23, but it's still stuck on 3G. Network Settings says LTE/CDMA.
Can anyone point me in the right direction to solve this?
I believe the only way you will get 4g back is to wipe the modems. This happened to me too.
From the white bootloader screen run the following two commands in adb
fastboot erase modemst1
fastboot erase modemst2
Hope this helps.
This got the phone out of 3g. It still drops to 1x for phone calls, though. I haven't had a chance to test call quality or see any drops yet.
Thank you very much!