I have searched this over and cannot find a solution to the issue. I have had my GS3 for a number of months now. Just recently, I could no longer receive SMS messages. MMS works ok. I called ATT, they blamed the phone since it wasnt one of theirs. I just hung up with them, as they're no help anyway. I went to the ATT store and one of the guys there took my SIM card out and put it in another phone. All of my messages immediately downloaded to the other phone. We took the SIM out and put it back in my GS3, and everything worked normal again. One week later, it's doing the exact same thing. I don't have another phone to put my SIM into, and I sure don't want to keep going back to the ATT store each week to dump my SMS messages. I have tried everything I can think of to fix it.
Does ANYONE have any suggestions as to why this is suddenly happening?
I am stock everything.
Check correct number in MMS settings Message Centre first .
jje
JJEgan said:
Check correct number in MMS settings Message Centre first .
jje
Click to expand...
Click to collapse
Did that. It seems there is only one. +13123149810
Can you make phone calls without problems?
ronj1986 said:
Can you make phone calls without problems?
Click to expand...
Click to collapse
Yeah, no problems making phone calls. I will say that the other thing that happens quite often is that my phone will make no noise on incoming calls or SMS messages. Someone can send me a message or call, and I'll be sitting right there with the device in hand, and it won't make a noise to let me know.
I am still awaiting my Jelly Bean update. Hopefully that will clear up most of it. It seems these problems began when it updated to 4.0.4.
But the SMS problem SUCKS.
On another note, if the Jelly Bean update doesn't fix these issues, I will be trading my I9300 for a Nokia 920 quicker than you can shake a stick.
im baffled by this problem too things I would of recommended 1st have already been checked. Have you tried a complete/fresh install?.
Seems your service centre number is correct too, have u tried changing it/deleting it, save then reenter the number again?
also found this page for ATT service centre numbers maybe theres more than 1 for your area?
http://www.att.com/esupport/article.jsp?sid=kb38686&cv=820#fbid=WduP4zjirUk
SwiftSmoke said:
im baffled by this problem too things I would of recommended 1st have already been checked. Have you tried a complete/fresh install?.
Seems your service centre number is correct too, have u tried changing it/deleting it, save then reenter the number again?
also found this page for ATT service centre numbers maybe theres more than 1 for your area?
http://www.att.com/esupport/article.jsp?sid=kb38686&cv=820#fbid=WduP4zjirUk
Click to expand...
Click to collapse
Yup. Wiped and reinstalled at the advice of ATT. No help. I am not the only one with this problem if you Google it. But there are no answers for the problem. I'm beside myself.
Can not receive SMS. (Permanent SMSC FIX)
Ok sorry for lasting so long.
Look at this and try. Maybe this is your problem. Had solved my problem. After flashing a new Rom.
If you have problems as described in first post and your smsc number is showing the right thing so also do this steps.
1. Find out the right SMSC (Short Messenger Service Central) number of your provider (for example O2 Germany is: +491760000443)
2.0 Then you have to translate/calculate it
at this site:
http://www.twit88.com/home/utility/sms-pdu-encode-decode
2.1 Type at SMSC your sms-provider-number (Example: +49xxxxx)
2.2 Delete Receiver and the small text under it
2.3 Click on Convert
3. A number appears at the right side, write it on a paper or copy it
4. Open Dialer and type *#*#4636#*#*
5. Click phone data and scroll down to SMSC
6. Then paste or write the number from 3.
7. Click actualize, update or something similar
8. Wait till your network is online again and then click refresh (about 5 seconds)
9. If your entered number still appears everything is working fine.
Sample for O2 Germany
(+49 is Germany replace it with the one from your country)
[SMSC] number is: +491760000443
[Calculated] number is: 0791947106004034110000910000AA00
[Showed] number after update is: 0791947106004034
(You have to cut "AT+CMGW=8")
Hope I could help some one with this.
UUK3 said:
There is a solution for that problem.
Will post it when I'm on pc. Cause it is a little bit much to write from phone.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I look forward to it!
How far away is your PC?
Anybody else know anything about this? It's doing it again. I cleared my messages on my wifes phone last Friday. It almost made it a week.
UUK said he knew of an answer and would post it when he got back to his computer, but he must be aboard the ISS or something. I can't contact him.
It's driving me crazy, not to mention I miss important SMS messages.
Have you tried flashing a new modem?
Sent from my GT-I9300 using xda premium
After Googling the problem, I am not the only one having this issue. It is happening all over. But I cannot seem to find an answer to it. I have contacted Samsung who was absolutely NO help, and ATT, who have created a ticket to try and help solve the issue. They even acknowledge it seems to be a much larger issue than just my device.
In the meantime, I will keep my eyes peeled here if anyone has any insight. I shouldn't have to flash anything as the device is entirely stock.
However, I think I have narrowed it down to the latest 4.0.4 update. It didn't do it before I got the update.
I will keep checking in here regularly.
My s3 suddenly stopped receiving SMS after flashing 4.1.2 Supernexus also tried Dark paranoid android and same issue. Prior to that 4.1.1 B1ackB3an all was great. On Vodafone UK and the SMSSC was correct, sending SMS was fine and if I'd SMS myself it came through straight away. Occasionally SMS were received early morning but nothing all day until sometimes they came through when I walked back into the house after work and it connected to the wifi. I cleared cache and fixed permissions and even when rolling back to 4.1.1 it still persisted. Unrooted and returned to stock lastest Samsung/Vodafone firmware last night and seems ok, will see how it goes over the weekend.
Happened to me before I rooted and if you search is a common problem unrelated to rooting. Mine just started up again after a couple of days (voda uk, 4.0.4)
Sent using Tapatalk
I am hoping when I get the JB update, it will take care of itself.
nigmol said:
Happened to me before I rooted and if you search is a common problem unrelated to rooting. Mine just started up again after a couple of days (voda uk, 4.0.4)
Sent using Tapatalk
Click to expand...
Click to collapse
Seems so from looking on Vodafone forum. I'd just assumed that it was due my switching ROM's as everything had been fine since I first rooted in August. Just coincidence that it started at the same time I switched. Did wonder if it was an S3 and a carrier thing as my wife's iPhone 4s also on Vodafone as been fine throughout.
---------- Post added at 11:27 AM ---------- Previous post was at 11:21 AM ----------
yeahmon said:
I am hoping when I get the JB update, it will take care of itself.
Click to expand...
Click to collapse
Hope it does for you, as it is so frustrating.
Yes. One thing I've noticed from Googling is that it is not carrier dependent. Interesting that rooted devices with different ROMs are experiencing the same issue. As previously stated, my device is 100% stock, not rooted.
Damn, it's doing it again. It didn't last but about 4 days this time. It worked this morning, but not tonight.
Related
I have checked the forum and no thread had the fix I am looking for. I have K13 flashed on my phone and it was working great for over a week, but now all of a sudden today it stopped connecting to rogers. I have the correct internet and mms apns but my phone does not connect to rogers. I get no data and can send messages only some of the time, but I can receive them. I also can make phone calls, but cannot receive them.
Regardless, I have tried entering the apns again, resetting he network connection multiple times and resetting my phone multiple times. I have no idea why it is doing this. Could it be due to the firmware or is there a setting I need to change. Please help!
I had an issue with rogers today also, had no connection at work through out the day but once i left work it started working.
I really don't think this is a rogers issue. I am going to try flashing a different firmware on my phone... maybe that will fix it... I really don't know what to do. :-(
Another discovery is it works on occasion only and sometimes it shows 3g but does not connect to H+ when it sends out data.
Sounds pretty weird. Did you insert another 50cents when the operator asked??
Was working for a week then with no change at your end the weird crap started...
I'd flash back to stock Rom for your provider and see if all goes back to normal. I'd make a backup 1st to switch back if it's your provider and not the device.
Good luck.
Sent from my GT-I9100 using XDA App
aceofclubs said:
Sounds pretty weird. Did you insert another 50cents when the operator asked??
Was working for a week then with no change at your end the weird crap started...
I'd flash back to stock Rom for your provider and see if all goes back to normal. I'd make a backup 1st to switch back if it's your provider and not the device.
Good luck.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I'm flashing back to an earlier version. KG5 was working fine for me... should I really flash back to original though? that would be KE2 for me.
SirRomie said:
I'm flashing back to an earlier version. KG5 was working fine for me... should I really flash back to original though? that would be KE2 for me.
Click to expand...
Click to collapse
Up to you really. If KG5 was working good try that 1st. That's what I would do if you are sure it's not your provider at fault.
Just a methodical process of elimination.
Sent from my GT-I9100 using XDA App
Fashing back did not solve the issue...
Doesn't point to your devices software to me from the little I know of your situation.
Could try a different sim...maybe from another network to see if there is something going on there.
Could try your sim in another device also. See if it works the.
Otherwise could flash back to stock. Reset flash counter if need be with jig and take back to shop and see if they can get it going.
Sorry I can't be more helpful without hands on.
Sent from my GT-I9100 using XDA App
I will try the sim card thing. It seems weird to me that it would just stop working like this, but after reading around some think that it is the modem? How could that have even changed in my phone? Does flashing cause it to change? It was working fine for two months solid and for one week on K13.
It is definitely not the sim card. Modem?
I did read somewhere that someones ime number changed when they flashed.
Might be worth a search as I dont have a link.
There is a way to check if ur ime is correct by using the dialer.
Sent from my GT-I9100 using XDA App
Well Rogers actually fixed the issue. I called them and they apparently had tower issues in my area. It is back up and running after me trying to figure all this out. Such a headache, but at least I will know for next time... a problem like this should not randomly arise and the modem should not change if stock firmware is used (given it is the right version). My IME is still there.
Glad to hear all is good. Had my doubts about it being your device
Sent from my GT-I9100 using XDA App
Thanks for all the help. I went through so many different processes, but I actually managed to get KIES to work with my phone now and all the settings I had are back on it too. So at least something good came out of it. Even if Rogers gave me a huge headache.
I cant remember what rom i started on when i first noticed it. but i dont receive any multimedia message, I can get text's all day long, but when someone send me a picture, and they say its sent from there side. i never get it.
funny part is if i send myself a mms, i get that. just none from nobody else. Ive tried flashing different radios, updating my profile. nothing seems to work. ive did clean installs + flashed superwipe for a fresh install.
i currently have
ROM: Fresh LTE 5.2.1 by flipz
BANDBASE: 1.05.11.0606
PRL: 25006
PRI: 2.45_003
KERNEL: 3.0.8-01368-g6fdcee1
http://forum.xda-developers.com/showthread.php?t=1839131
Most likely Sprint problem. I had issues too and was beginning to think it was the Rom I'm running (Cm10) low and behold, mms finally downloaded
Sent from my EVO using xda premium
This happens to me from time to time. I believe it too is a Network/Sprint problem. What I do to remedy the problem is use Google Voice to check for SMS, however you can't receive MMS through GV though.
2LoWw7 said:
This happens to me from time to time. I believe it too is a Network/Sprint problem. What I do to remedy the problem is use Google Voice to check for SMS, however you can't receive MMS through GV though.
Click to expand...
Click to collapse
this would work if i could get google voice to pull MMS from me phone number.
Steven 1 said:
http://forum.xda-developers.com/showthread.php?t=1839131
Most likely Sprint problem. I had issues too and was beginning to think it was the Rom I'm running (Cm10) low and behold, mms finally downloaded
Sent from my EVO using xda premium
Click to expand...
Click to collapse
is this a call in issue or a take your phone in deal?
the MMS not loading thread is different from my issue. He at least receives his MMS, they just don't download. Mines doesn't come through, at all.
So i took my phone into the sprint store, and there response was that the phone checks out ok on there diagnostics. And that they didn't know what was wrong with it. And after a stupid amount of time wasted on the phone with tech support and super geeks and bs. They still didn't know what was going on with the phone. At this point, I'm ready to take my phone back to sprint and demand a new replacement one. The update to 2.13v didn't fixed jack. How disappointing was that. I flashed and updated firmware and radios, profile and still nothing.
Finally, earlier today i updated my hboot with (PJ75IMG_Jewel_Boot.img_2.13.651.1_signed.zip) and boom, i got my mms back. I cant 100% say that's what made it work, since im not sure what made it stop in the first place. but its good to go now.
As the title suggests, suddenly I started getting force closes with com.android.phone when I'd receive a call. I immediately tried to call out, same story. I've been troubleshooting for the past few hours, and had no luck finding anything relevant on XDA or any other site.
Firstly I switched kernels, since I'd updated to DSB's latest, though I'd had no issues with it until then. That failed, so I reverted to Viper's stock build.prop, undoing some changed I'd been running for a while (and hadn't modified at all today).
With no luck there, I backed up my sdcard and did a full factory reset and formatted the sdcard in twrp and then in cwm, followed by a reinstall of the latest Viper ROM. Even that didn't work, so I relocked and RUU'd back. Twice. Same exact issue. I can text anyone just fine, data over LTE goes on as normal, but anytime I try to make a call, be it with the stock dialer or through a diff one from the play store (for kicks, last resort). I reseated the SIM card a multitude of times, to no avail. I get full functionality with my SIM in my other phone, so I'm sure it must be the hardware itself on the phone. Every time com.android.phone stops, the SIM initialization happens like when you physically re-seat the SIM.
The troubling thing is that I haven't done anything, save for a simple kernel and recovery update, which would've been negated by two RUU runs to stock. I haven't touched the SIM card or anything, at least until that started happening. Furthermore confusing is how all other functionality can remain except for actually making phone calls.
Removing the SIM entirely and dialing a number does the exact same thing, just as an FYI.
Has anyone seen this? Any ideas?
As I've unlocked my phone, my last resort is to go into a VZW store and act like an idiot so they don't check to see if i unlocked it. Further complicating that is the fact that the DNA was actually purchased on my own account, which I closed, and brought to an unlimited data line that was preexisting. I'm half tempted to wait for the official OTA and see if that will remedy the issue, but my fear is this may be a physical issue beyond the remedy of a firmware update.
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
ergotelis said:
http://forum.xda-developers.com/showthread.php?t=2126386
Check this thread, me and another member faced the same problem. I can get 3g/2g data, sms and all other functions just right. Just no phonecalls, every time i make a call i get a crash of the app.
So, i am pretty sure this is a software bug. For god's sake, what a strange problem!Did your phone used to work right?
I bought my phone from ebay, did not check if phonecalls are working(i couldn't imagine such a bug) and went straight away to rooting/other kernels/roms etc. But can't find a solution too,tried everything as you, and the worst, i am overseas!!!
Is the update coming soon?
edit1: i have seen lots of threads about sim errors,a very common issue of DNA, i am believing that these two bugs have something in common. No hardware defect, just software bugs.
Click to expand...
Click to collapse
thanks for the thread, for the life of me i couldn't find anything exactly relating to what i described. that is spot on though, and def makes me feel a bit more at ease that maybe it can be resolved with an update to the firmware that's due soon.
yea, the funny thing is that it worked flawlessly, i never even got the SIM error message, i'd been texting my gf, a few friends, and my parents and then my pops called in the evening and it immediately closed out the call before it really even rang. i called him right back and that's when the force closes started happening, calls never working agian thereafter. however, i was able to still text everyone i was before and data was working flawlessly as always, just no calls, not even after all the crap i did to troubleshoot.
the update is hopefully going to be out soon. the support documents came out a few days ago. i def can't survive on this galaxy nexus after having used my DNA since launch!
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
ergotelis said:
I will wait for the update too, hopefully it will be uploaded today or tomorrow i think. But just because i can't get on the air update, i need to download from a server the update and install it on my own.
If anyone finds a solution or have an idea of what to look/do, please post here. I am pretty sure it is a software bug, something is stucking the application from working properly. The other solution is RMA, but it is a very difficult to send it back and get it back again.
Click to expand...
Click to collapse
The update is out now, can someone send it to me too? I am overseas, trying to find a way to download it.
OP, can you test this one to see if you get a fix?Thanks!!!
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
After saying all that I just got the new update from Verizon. I assume I shouldn't flash this since I'm on a custom rom.
Sent from my Nexus 7 using xda premium
Thanks for the input, really interesting!Will try it right away! Hope you won't have any problems with the update now!
msturner79 said:
Ok, I had the same exact issue. I was stock then went to viper Dna then tried going to hatka and soft bricked my phone. I went back to stock using the RUU. That's when I got the com. Android. Phone crash message. So I had to re unlock reboot and then flash viper Dna again. Everything works as it should now.
Click to expand...
Click to collapse
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
ergotelis said:
THIS IS THE SOLUTION!Now working! A HUGE HUGE HUGE THANKS TO YOU!!!! :victory:
Click to expand...
Click to collapse
Hi guys i got a similar problem. My DNA was perfect since yesterday but now i can use data connection for internet. All the other stuff is working fine....SMS,call, wifi, the only thing that is not working is the 3g data. All of this problem came when i flashed the viper DNA, so i flashed the supercharged hoping it was an issue of the rom. Olso with the supercharged the problem was always here.... So i decide to came back to stock and i re-lock my bootloader and flasched stock RUU. But data connection is still not working :crying:
can anyone please tell me what can i do?
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
As I've unlocked my phone
ergotelis said:
Did you install patches 1.1.1& 1.1.2 from viper?They fix some gsm problems.
Click to expand...
Click to collapse
yes but notthing changed.... :'(
Now i'm compleatly stock and the problem is still here.
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
ergotelis said:
flash again the viper rom, do the whole procedure again, at least this is what i did and fixed the problem!(stock->viper->stock-> viper and then OK)
Click to expand...
Click to collapse
Which version of viper worked for you?
hard problem
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
jimmydee62 said:
Has any one figured out this problem? I have not been able to received any phone calls since I did s-off. I have tried everything that has been wrote so with no luck. I have relocked my phone and flashed stock RUU no change. Unlocked and tried several roms still no calls. formatted everything under CWM not change. Fixed permissions. Went back and re-locked and reflashed stock RUU. I know that some of the things above have fixed others phones and some still have problems. I also found a script someone wrote lock my phone which now it says locked and flashed stock rom after that still have problem. Does anyone here here a idea that I have not already mentione above? I like my droid dna but if I can't get it to make and take calls it is a paperweight.:crying:
Click to expand...
Click to collapse
Still broke?
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Still broke?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes it is still broke I just don't know what to do at this point paper weight right now.
Has anyone experienced issues with sending and receiving text messages? I've noticed a few times I would send a message, then later I see that it never went through, and is sitting there with a spinning circle next to it. It will stay like that until I restart the phone.
ledvedder said:
Has anyone experienced issued with sending and receiving text messages? I've noticed a few times I would send a message, then later I see that it never went through, and is sitting there with a spinning circle next to it. It will stay like that until I restart the phone.
Click to expand...
Click to collapse
Never had that problem with my stock Verizon GN2.
universexda said:
Never had that problem with my stock Verizon GN2.
Click to expand...
Click to collapse
I'm just running the stock rooted ROM.
Only happened to me once or twice but turned out I was in a corner of my building with a very weak signal.
I did get some weirdness with the old 'radio'/'modem' but flashing the new one helped. Have you tried the new radio?
ScottieB said:
Only happened to me once or twice but turned out I was in a corner of my building with a very weak signal.
I did get some weirdness with the old 'radio'/'modem' but flashing the new one helped. Have you tried the new radio?
Click to expand...
Click to collapse
What/where is that?
I'm no expert, but the radio/modem is basically the phone part of your phone - the communication part. There's a new version (is it firmware? I guess so) to flash which for some (like me) has improved reception. I don't think I've seen it do anything BAD, but I could be wrong. I got it from the Beans Rom thread. As always be careful, CHECK THE MD5, and I'm not sure if it needs a specific os version, but I installed it when I upgraded to Beans build 9.
It is in the second post here http://forum.xda-developers.com/showthread.php?t=2032447 (beans thread) or I'm sure you could search the forums for "VRALL4 Modem"
Hi guys,
my gf is having issues with her new L9 II D605.
When having a call there's absolutelly no sound coming from the speaker and the other side can't hear anything either.
After reboot everything works fine for a while (maybe even days).
It's already a second phone with the same issue.
No root, no hack, no system update done.
System reset doesn't help.
Any ideas what could it be pls? Faulty machine, second in a row?
Thx.
+1 Spain
+1 Vodafone Germany
greece same problem here.Trying 4,1,2 so far (3 days) no pro.
PS.please write yr country to make o conlclusion if its phone problem or phone company.
+1
Greece wind
+1 Serbia, Telenor network.
Greece Vodafone
+1
+1 Serbia mts
Ok so i flashed jb kdz and then updated to kk. Its been 5 days and i havent had no sound problem. So there is a problem with flashable zips in some regions.
I am not familiar with abbreviations so please explain. I have same issue. The issue appears when I have data on, perhaps. I have 4.4.2 version and the problem is frustrating. Should I go back to a previous version, and how please? Also I have install the VUTALK disabling soft that comes from LG, somehow it felt it was causing all that. I will push it with several calls to verify it's ok...
Does anyone have any settings to apply that may resolve the issue?
Does LG give a response to the issue??
Thanks
ps. btw I'm in Greece with Vodafone
shaggy.ba said:
Hi guys,
my gf is having issues with her new L9 II D605.
When having a call there's absolutelly no sound coming from the speaker and the other side can't hear anything either.
After reboot everything works fine for a while (maybe even days).
It's already a second phone with the same issue.
No root, no hack, no system update done.
System reset doesn't help.
Any ideas what could it be pls? Faulty machine, second in a row?
Thx.
Click to expand...
Click to collapse
Is this happening after camera failed to initialize? I think it is some bug in KK .
I have problem also with quiet mode. It won't go if wi-fi is on.
I am thinking to go back to JB 4.1.2 but not sure how.
zocca said:
Is this happening after camera failed to initialize? I think it is some bug in KK .
I have problem also with quiet mode. It won't go if wi-fi is on.
I am thinking to go back to JB 4.1.2 but not sure how.
Click to expand...
Click to collapse
so i send my phone about 10 days ago to service. They returned it saying it's fixed and tested. They have changed my ROM version from 20b to 20c-220-03. The phone worked fine, and I did not have problems with calls until today. I read your post and I remember that I accidentally open my camera today and it said "failed to initialize". After that the call problem appeared again. Now I forced my camera couple times until showed the same thing, and immediately tried to call my home number and here we go, call problem. It would be sooo nice if they could just fix this goddamn error which frustrates me a lot.
It's a stock zip bug, blame it on LG, try flashing 20d haven't had a problem with it, but I'll be using cm11 soon, which I think is much better. Cheers
Sent from my LG-D605 using XDA Free mobile app
I sent the phone to the service and guess what?
LG service centre is saying it's damaged and can't be repaired as they do not have the necessary spare parts.
So I'm getting my money back... hopefully...
No problem with calls nor messages anymore
I do not encounter this problem anymore. It might be that some automatic update has resolved it. I am currently using Android 4.4.3, build KOT49.D60520g.
By the way, I do not know about any lost text messages anymore (another issue of this phone) - - also ghostly SMS does not reveal any messages that would be lost without the app. But I try to keep the memory not full as well.