OK guys, LG Turkey keep asking me what are the symptoms of ghost call issue. So I thought it might be a good idea to point out all the problems related to ghost call isue so that they can understand the problem better and find & fix it from the core. IF LG asks you about detailed problem, you can C/P this list.
-The problem is related to USIM handling.
-When you try to call someone, if the USIM is crashed, the phone will give you a warning like "Wait for internal process to complete."
-If you go to contacts, you will see that the phone is trying to pull SIM contacts. When the process is over, Phone will tell you that "USIM Loading done". After that, you can make your call.
-If you call someone, sometimes, after the firt 5 seconds of connection, USIM crashes and you start hearing a buzzing noise. Now try to call the same person again, you can't. You will have to wait for USIM to be loaded again.
-When USIM crashes during a call, the end call button will not work for a time.
-Sometimes, USIM driver or handler, or whatever it is, crashes when someone call you. If this happens, then the phone keeps ringing until you reject the call. If you do not reject, the phone keeps ringing until the battery is full drained.
-When USIM handler crashes, it does not recover automatically always. This is the time you recieve neither calls nor SMSs.
I think:
-The problem has nothing to do with either 2G or 3G
-Nothing to do with hardware
-It is all related to baseband or USIM driver that comes with Gingerbread version.
These are all the problems I have experienced so far. Please comment if you had different problems, but only related to ghost calls.
What I don't understand is that not every body has the ghost calls issue.
I bought my phone second hand. Original owner bought it at July for 600€. he had it upgraded to 21A. No root no nothing. Its a Greek phone. I never had the ghost calls issue as long I was using it stock. Also the battery was extra ordinary. Maybe 30% all day.
After a week I decided to root. A bad decision and phone bricked. I unbricked it but baseband changed. Again no ghost calls.
I repartitioned it, changed a few Roms again no ghost calls.
I came think its a hardware issue for a few. So better thru to find what you have in common with others or demand a refound.
orlox said:
What I don't understand is that not every body has the ghost calls issue.
I bought my phone second hand. Original owner bought it at July for 600€. he had it upgraded to 21A. No root no nothing. Its a Greek phone. I never had the ghost calls issue as long I was using it stock. Also the battery was extra ordinary. Maybe 30% all day.
After a week I decided to root. A bad decision and phone bricked. I unbricked it but baseband changed. Again no ghost calls.
I repartitioned it, changed a few Roms again no ghost calls.
I came think its a hardware issue for a few. So better thru to find what you have in common with others or demand a refound.
Click to expand...
Click to collapse
In my opinion it can't be an hardware problem, because with Froyo Rom never happen... and the hardware is the same.
maybe something related to sim card,carrier or coverage?
I never had ghost calls with Froyo. It all started when upgrading to Gingerbread. I also experienced dropped calls with a buzzing noise and RIP (Reorganizing Internal Process) messages while trying to make a call. This is consistent with what cool_recep posted. I cannot say much about SMS because I don't use them a lot.
It might be useful for LG to know the frequencies at which my carrier operates:
COSMOTE GSM 900
885 – 890
930 – 935
COSMOTE DCS 1800
1760 – 1785
1855 – 1880
COSMOTE UMTS
1950.3 – 1965.3
2140.3 – 2155.3
1905.1 – 1910.1
I never had baseband or airplane mode crashes, like others have posted around the forum, or the reorganizing internal process problem, I just had a guaranteed instance of a ghost call, so there were probably more. I had called someone, he answered and said he was busy and that he'll call me back in 2 minutes. After 5 minutes of looking at the phone I called him back and he said he called me but I didn't answer. I had been using the GB rom (v21a official, via kdz update) for a few weeks without having any of the other problems, but once I had confirmation that ghost calls occur for me too I went back to froyo.
As for the frequencies, I can't get any clear info off the web, but Orange Romania runs on either 900, 1800 or both. 99% of the time I was on 2g only.
I think it´s nice to tell which operator everyone is using.
Operators work differently, sending data in a different way from the others. For example: some send NITZ information all the time, others send just when the device attaches to the network.
The ghost call issue may happen only with operators which send some kind of data others don´t, or with operators which send too much data, triggering the bug which crashes the USIM, who knows?
I use Vodafone.
//Sees that actually his operator can be seen on the left. //Facepalm
I have v20c and am with rogers in Canada. Haven't had any ghost call issues whatsoever
Sent from my LG-P925g using XDA App
I am going to update to that new Portugal ROM 21A and check it out...
I've got the v20c rom for Hong Kong. Ghost call is still here (but less frequent)
But then I noticed the data connection is very unstable... even if I haven't been moving around, and staying in a place of strong signal. Wonder what caused the problem...
Related
A few weeks ago I got a HTC Desire on Virgin Mobile (I believe they use T-Mobile's network) in the UK.
I'm having a bit of a problem with it, though. At seemingly random points, if somebody tries to phone me, it will go straight to my voice mail. If I then try to phone them back it will work. And usually, if they try to phone me back after that it will work too.
At first I thought it might be a problem with my phone being on standby, as that's when it seems to happen the most. But I have received calls when it's on standby and I've also had a few calls go straight to voicemail when the phone isn't on standby too.
Does anyone have any ideas why this might be? I've tried looking through the phone settings for anything obvious that could be causing this problem but I can't see anything.
same thing here
weird problem, kind of a biggy, my phone wont receive calls. I've run through several pages of google search over this issue, no answer, though I came across a few people with similar issues. I figured xda would be my best bet, if you guys can't help me...
Everything else works great, web, email, sms, outgoing calls, everything but incoming. This is kind of a big deal, I sort of need my phone to be working. When I get an incoming call, the phone vibrates, rings once, then goes silent. There's nothing on the caller id, but I did note that the signal drops to zero when it rings, dropping the call. From the other end, you just get cut off, it doesn't direct you to voice mail even.
I am currently running paragon rc6 rom, but just swapped over from the phoenix 5.2 rom tonight, as I mistakenly thought the issue was with the rom, but considering that it has continued even after flashing a new rom, it would seem to be something else entirely.
I don't know what the issue is, I swapped sims with my wife's phone, worked just fine calling her phone with my sim, but my phone still wouldn't work with her sim in it.
I have had the battery in and out a half dozen times in the past 24 hours, so I don't think that's going to fix the issue......I don't know what else to try. Can't very well call Rogers since they'll just blame the issue on the fact that I was screwing around with my phone, and since it flashes back to a stock at&t confige, I can't very well flash it back and pretend I never did anything
appreciate your help, stressing me out a little, need my phone for work, and my wife will have my balls if I broke it
I bought Nokia Lumia 800 about 1week ago, I've found a lot of bugs, most of all is that I can't end the call when after someone calling me. Nothing changed though I press the end button, at the top of the screen, it displays 'end calling', I can press back to open other apps, but the it's still maintain there. Few minutes later, it's gone automatically. But sometimes, it will reboot.
Someone said it's because of the sensor at the top right of the screen, if receive calling, do not hang up in the dark.
Someone said turn of 3G in the 'network', someone said turn on the 'roam', I've tried all of the them but none is work, can someone help me of it?
I have to say I have already regreted for buying it.
The two major issues I have read about the Lumia 800 are battery drain and end call issues. The latter does not seem to have a fix yet.
Did you cut your sim?
Of course I cut my sim. Someone said they have already fixed this problem,and I don't know how.
End calling issue seems just happened to nokia, other brands like HTC or sumsung haven't reported such problem like that.
It happened on my Omnia once i guess, but it only lasted about 30 seconds, and after that the phone was acting just fine, no reboots nor anything. Idk if it's the same tho...
ilovewp said:
Of course I cut my sim. Someone said they have already fixed this problem,and I don't know how.
End calling issue seems just happened to nokia, other brands like HTC or sumsung haven't reported such problem like that.
Click to expand...
Click to collapse
The reason I asked was people were trying to find a pattern to see if it was a cut sim issue. Some carriers offer micro sims.
If you can I would exchange it. Or return it.
My Lumia has problems in USSD operations too along with this call not ending problem
It occurs mostly in the devices in India as operators push remaining prepaid balance through USSD . Even *123# is not working for me sometimes. Lumia sure has some problems with USSD operations.
I sometimes get this problem on my DVP as well.
Before releasing A handset's phone functions should be thoroughly checked in all the markets where the handset has to be released.. These problems are unbearable
I have read through the FAQs and seen several posts from users of other phones and other networks with the same issue, but there has not been an answer to be found.
I've experienced this issue with 4 different ROMs now, so it's not ROM-based. I've tried 3 different radios, so it's not likely modem-based.
The issue is that I will get voicemail notifications for calls I miss, but I'm sitting at my desk with my phone and it didn't ring, nor is there a missed call indication. 5 minutes later, someone else might call me and the call comes through fine. It appears to be purely random. People who call me sometimes get through, sometimes not. It's not the same person who can't get through, or the same network.
Does anyone have an idea what is happening?
dontezuma said:
I have read through the FAQs and seen several posts from users of other phones and other networks with the same issue, but there has not been an answer to be found.
I've experienced this issue with 4 different ROMs now, so it's not ROM-based. I've tried 3 different radios, so it's not likely modem-based.
The issue is that I will get voicemail notifications for calls I miss, but I'm sitting at my desk with my phone and it didn't ring, nor is there a missed call indication. 5 minutes later, someone else might call me and the call comes through fine. It appears to be purely random. People who call me sometimes get through, sometimes not. It's not the same person who can't get through, or the same network.
Does anyone have an idea what is happening?
Click to expand...
Click to collapse
Your description definitely sounds familiar. There are times when the phone was under clothing or left on vibrate, then there are those back to back instances where you notice because the first call went straight to voicemail and the next one gets through.
Ideas? Maybe not, but there may be some clues worth considering. Every wireless carrier I've used suffers dead spots where you are 99% guaranteed to have your call drop in progress driving by.
Locally (NJ) AT&T has 2 on the westbound "covered roadway" leading to the skyway. My point is I've observed where they won't affect my passenger's TMobile calls. Oddly, when I experience this there, the call has usually gone on uninterrupted through the Holland Tunnel. Must be an infrastructure quirk.
The drive by carrier dead zone is a fixed location call deterrent. An expert could probably say how much each example is based on tower locations versus radio interference. I guess a similar scenario might be possible wherein the call recipient is stationary, like at your desk, and some moving interference breaks a fragile tower connection. I have to say it seems a lot less prevalent with SR vs. previous smartphones and with my current ROM / Modem vs. former ones.
pc103 said:
Your description definitely sounds familiar. There are times when the phone was under clothing or left on vibrate, then there are those back to back instances where you notice because the first call went straight to voicemail and the next one gets through.
Ideas? Maybe not, but there may be some clues worth considering. Every wireless carrier I've used suffers dead spots where you are 99% guaranteed to have your call drop in progress driving by.
Locally (NJ) AT&T has 2 on the westbound "covered roadway" leading to the skyway. My point is I've observed where they won't affect my passenger's TMobile calls. Oddly, when I experience this there, the call has usually gone on uninterrupted through the Holland Tunnel. Must be an infrastructure quirk.
The drive by carrier dead zone is a fixed location call deterrent. An expert could probably say how much each example is based on tower locations versus radio interference. I guess a similar scenario might be possible wherein the call recipient is stationary, like at your desk, and some moving interference breaks a fragile tower connection. I have to say it seems a lot less prevalent with SR vs. previous smartphones and with my current ROM / Modem vs. former ones.
Click to expand...
Click to collapse
Thanks. No, this is definitely chronic and not related to dead spots. I have my phone with me at my desk, 3 or 4 bars, no issues. Just doesn't come in. It's been really bad since moving to the JB ROMs. It pretty much never happened without explanation (dead zone, etc.) when I was on ICS and earlier. :/
One other performance problem that my Captivate had resembled this.
When I complained to Customer Service, they did some kind of remote (non-destructive) "reset" of my account. That corrected the random call drops I had reported then.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
pc103 said:
One other performance problem that my Captivate had resembled this.
When I complained to Customer Service, they did some kind of remote (non-destructive) "reset" of my account. That corrected the random call drops I had reported then.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Were you dropping calls midstream, or not receiving calls? My problem is with not receiving calls when I'm somewhere I usually do and at times when my cell service looks fine (adequate bars).
dontezuma said:
Were you dropping calls midstream, or not receiving calls? My problem is with not receiving calls when I'm somewhere I usually do and at times when my cell service looks fine (adequate bars).
Click to expand...
Click to collapse
Now that you mention, I recall it was a mix. Bars were good, some calls were silently missed, others FCd the phone app while ringing in, forcing reboot. Good, stable calls surrounded the (<5%) failed ones. AT&T's account reset corrected both issues. Stock ROM back then was Éclair or Froyo.
Hello,
I'm asking for some help to diagnose my call problems on UMTS.
First of all, three things happened recently, and let's assume that they happened roughly at the same time:
I dropped my Nexus 5 on concrete shattering the screen completely;
Google released Lollipop which some people believe has problems with 3G and LTE;
I'm using a rather old SIM card manually cut to fit micro-SIM dimensions.
About two days after receiving my Nexus 5 back from guys servicing it (new LCD screen) I had a telephone conversation that was disconnecting once every minute or two. There was no problem recalling though. The same day later I noticed that dialer app says "Emergency calls only" which was pretty weird. I was on Cyanogenmod 11, some recent nightly back then.
My first guess - revert to earlier nightly via TWRP. It didn't help - I was still on emergency calls only and nobody was able to call me. However, I could browse Internet without any problems on 3G.
Second guess - clean flash stock 5.0.1. It didn't help too, however calling went back on for some time (several minutes) before breaking back to "Emergency calls only".
Third guess - buy a starter SIM and check if it works. It did at first but stopped after an hour or so.
Fourth guess - bring the phone back to guys servicing the LCD to check antennas. I've left it for two days. It was opened and antennas checked. Everything was fine, not even a bent flex.
For all this time when on 3G/LTE data transmission worked flawlessly. I could download Google Maps, browse the Internet, whatever. It's just the very basic phone function that acts weird - as if I wasn't registered to a network. Everything seems to work fine on 2G, except for very rare disconnects (once per two, or three days).
So, considering it's pretty weird I'm seeking for help - could it be possible that after hitting concrete something broke down on the motherboard that results in such weird behavior? Or is, perhaps, my retro-SIM dying? Any ideas? Maybe flashing a well-tested radio ROM? Diagnostic apps?