GOOD READ - Text Message From The FUTURE problem - EVO 4G Q&A, Help & Troubleshooting

The problem is when I receive text messages from any network, the time stamp is messed up and shows up two minutes in the future (see picture below). I have done a complete hard reset about five times, tried all different software updates, went completely back to stock (unrooted), tried AOSP roms, tried Gingerbread roms, tried Sense roms with AOSP mms.apk, and whatever I try I cannot get rid of this bug. It causes all my text messages to be scrambled and not in order. I use this phone 90% of the time for texting. It's how I handle most of my business. I called Sprint and ended up getting up to their advanced tech support where they simply did a provisioning reset (completely unactivated and activated again) and after that they said there is nothing they can do. So I took it into the remedial Sprint tech in my local Sprint store (don't have enough time to travel 2 hours to get to a corporate store), and they did another master hard reset where they completely reloaded the software (I guess). Still not fixed. I am outside of my 30 days so i cannot do a swap. I cannot send my phone in to HTC because I simply cannot live without a phone for 2 weeks, and I don't have a backup. I've done all types of searching on google and the only thing I could find was about 6 months ago people were having this problem but the times were delayed by an hour or two. The texts are not delayed they show up on time, they just have the wrong time stamp. It has to be something with the network and not the software. My immediate suspicion is that is has something to do with my MMS provisioning to the network but I really don't know how to look into this.
This is probably one of the weirdest problems you will ever see. The picture at the bottom shows the right time in the corner but look at the time on my last incoming text. Off by two minutes in the future. Can anybody offer my some advice I am up for anything. I can also post or send anybody anything. I need this fixed but I just can't deal with Sprint anymore. I realized they are a business but if they support a faulty product, they should fix it without taking anything away from their customers. I always feel like Sprint is trying to take something away from their customers. Oh also one of the Sprint techs said the EVo would not get an official gingerbread update because Sprint wants to push other phones.........most likely a fib but who knows....sounds like Sprint and HTC. Anyways

Just a thought, what if those texts really are coming from the future? I mean for all you know you are caught in some sort of weird time vortex thing that distorts your perception of time, making it seem like you are in the present when actually you are two minutes behind everybody else. That would make any text coming in to you be from 2 minutes in the future. I know this sounds far fetched but I wouldn't discount it as a possibility.

This is a bug in android. Search the market for sms time fix and see if that helps.
Usually it's off by hours and not minutes though. There is also a setting somewhere that will let you use the local time instead of network time but I don't remember where it is at. You could also try disabling roaming, I keep mine locked to Sprint's network and never lose a signal.

Never heard of this fix, but I got the same bug. I just installed chomp sms, works perfect now.
Sent from my PC36100 using Tapatalk

Try CM7. Perhaps the bug was fixed in Gingerbread (2.3.1)

I tired gingerbread....and the funny thing is this only happens to some phones because my roomate has an evo right now and it does not do any of this....so it is not a problem with android......it has to be the Sprint servers or something. I'm on fully stock right now (no root). I tired gingerbread (CM7) and it didn't help anything. I'm taking my phone back into Sprint today but this time I'm going to give them hell. I payed 350 dollars for this phone I will not settle for "Oh, well we can't do anything about it." You shouldn't have to install anything extra on your phone. I tried that SMS fix but the funny thing is, it messes everything up because my Sprint texts are fine but my verizon and att are all futuristic. And no I am not in some weird wormhole or time continuum the phone is just messed up. It happens with electronics but there is usually this thing called a warranty that allows for direct replacement and for some reason cell phone companies have avoided this whole customer based process. I'll get back in about an hour.

Alright went to my local Sprint Repair Center and they could do absolutely nothing. However I did have the manager push through a priority claim ticket to the network engineers and hopefully, and I do mean hopefully, they call me back. Apparently the last few times I've called they told me they started a ticket, and actually didn't. I think they think I was telling them a lie or something. The manager there was actually extremely helpful and told me he would make sure I get a new phone if this doesn't work. If anybody has any other suggestions please let me know.

I'm curious if this would fix it...
Go to your time options. Settings-Date/Time If automatic is ticked, untick it. If its not, tick it. I would think the bug is caused when a text is sent with a timestamp via the network, at lets say 6:00 but your phone is registered as 5:58. Your timestamp would get all different kinds of backwards in your text app. I'm not sure if time on a phone would be on a BIOS chip like a computer, but it would make sense that your phone is just simply registering the time wrong. If you check/uncheck that and it still does it, simply hard-set the time two minutes ahead.

Recently I've started having the same exact problem, except I have the Samsung Epic. Called customer support once and they "reset messaging" which didn't help at all. Installing any third-party messaging apps haven't helped, and neither has switching between local and network-provided time. Also, its random, so most incoming messages are messed up, but some are actually correct.
I'll try manually setting the time ahead two minutes and bugging some people to text me.
Edit: No luck, with the time set ahead two minutes, incoming timestamps are two minutes ahead of the new setting as well.

av91 said:
Recently I've started having the same exact problem, except I have the Samsung Epic. Called customer support once and they "reset messaging" which didn't help at all. Installing any third-party messaging apps haven't helped, and neither has switching between local and network-provided time. Also, its random, so most incoming messages are messed up, but some are actually correct.
I'll try manually setting the time ahead two minutes and bugging some people to text me.
Edit: No luck, with the time set ahead two minutes, incoming timestamps are two minutes ahead of the new setting as well.
Click to expand...
Click to collapse
Please call technical support and get everything into the Sprint system. Ask them to push it to a network engineer. I have to wait until one of them get a hold of me but they may end up just replacing the phone. I'm glad to hear that other people are having the problem also. Also an update, it is text messages from all networks that do this, including Sprint. I will keep this thread updated because I need to get this problem solved. At this point, I don't think there is anything left for me to do from the user end. I just have to wait for Sprint to get it all figured out. I do have insurance and they said they might just put in a request for a new one at no cost to me......also sounds like bs because I thought you had to pay a 100$ deductible no matter what. The Sprint tech said you don't have to pay for the deductible if its a software or network issue and there is no screen crack or water damage. My EVO is in perfect condition but the software doesn't work. Hopefully they will give me a reconditioned one that actually works.

This is a Sprint network problem. Various sprint phones (not just Androids) are notorious for this type of behavior (wrong time stamps, messages out of order, delay in receiving and sending messages, etc etc). It's very frustrating indeed.
For the time being, try using one of the SMS apps on the market like Handcent or ChompSMS. You may still get incorrect time stamps from time to time, but your messages will arrive/send in order.

twoslo said:
This is a Sprint network problem. Various sprint phones (not just Androids) are notorious for this type of behavior (wrong time stamps, messages out of order, delay in receiving and sending messages, etc etc). It's very frustrating indeed.
For the time being, try using one of the SMS apps on the market like Handcent or ChompSMS. You may still get incorrect time stamps from time to time, but your messages will arrive/send in order.
Click to expand...
Click to collapse
I appreciate the response but I really don't like using aftermarket apps that don't go along with the theme of the phone. I'm real OCD like that. I don't even like apps that have free next to their name. If you pay 350$ for a piece of electronics, everything should work on it, including software and hardware. The sprint engineers need to get this figured out. This is unacceptable. The amount of money they are getting from their customers is ridiculous so why can't everything work. I realize their stock has taken a murdering but you have to keep your customers happy, that's number one. Anyways, I'm waiting too hear from Sprint but they said 72 hours not including the weekend so If I don't hear from them by next Tuesday, they will be getting a nasty call.

Exact same problem!
It has been driving me crazy. I will receive a text at 9:05, respond to it, and it will say it's 1-2 minutes earlier.
Another thing: we have four Sprint phones in the house. If we're all looking at them at the same time, they don't all say the same time. So, I tend to think that the time that shows when I receive a text is actually the time the sender's phone says. (Is that confusing enough for you?) Could that be the difference?
It only started recently, probably when I updated my phone last month.

This happens randomly on my Evo. Certain people I'm texting with, the time stamps will be out of whack, ranging from 2 minutes off, to over an hour off. My time stamp is always accurate, it's just the other person's that is inaccurate. I can be texting with a different person, at the same time, and the other thread will be perfectly normal. It's annoying. My phone also thought it was somewhere in Amsterdam (i wish i was there with it too) for a few hours, and nothing I tried would get it to show my actual location. I attribute all of this to google issues, and not actual problems with the phone.

k2buckley said:
This happens randomly on my Evo. Certain people I'm texting with, the time stamps will be out of whack, ranging from 2 minutes off, to over an hour off. My time stamp is always accurate, it's just the other person's that is inaccurate. I can be texting with a different person, at the same time, and the other thread will be perfectly normal. It's annoying. My phone also thought it was somewhere in Amsterdam (i wish i was there with it too) for a few hours, and nothing I tried would get it to show my actual location. I attribute all of this to google issues, and not actual problems with the phone.
Click to expand...
Click to collapse
Alright still not fixed as of Monday....I have one more day until I can call Sprint and give them hell which I love...not....but anyways I've been doing some testing on when actually the time stamp is off. The time stamp is off from any network including Sprint only when the phone is asleep (or the screen is off). Then the time stamp comes in 2-3 minutes in the future. When my phone is on everything comes in fine and one time and all the time stamps are good. It seems like when the phone is asleep its grabbing things from the network 2 min ahead for some reason.

Alrigth just an update on the situation.....called Sprint back they said they had no recollection of my callings the last couple of days....completely unacceptable. Anyways I got real nasty with them and got sent up to retentions (I told them the iphone for verizon looks really good right now.) Walked all over the retentions people and they said just go to a store and get a warranty swap (since I pay the 7 dollars a month or whatever.) I went to the local store (Lafayette, IN 47909) and they said that I was the first one with this problem but not the last. Apparently right after I left the store the first time I went, about 10 to 15 people came in right after that with the same problem. The manager at the store finally got a technician ticket in and apparently the problem has reached a ton of people all the way down to Indianapolis. Even some of the workers at the store are having problems with their EVOs and Epics. The explanation I got was it has to do with android and the text messaging server within the Sprint Network. If anyone else is having this problem...PLEASE CALL SPRINT AND ***** TO THEM. They need to fix this as soon as possible but they won't recognize it as THEIR problem unless a bunch of people call in about it. It should be getting fixed but I will check back on Friday.

I noticed this same problem on mine. Looks like I'll be calling Sprint tonight and stopping by my local store. Maybe I'll just go to Sprint World HQ here in KC and talk to them about it.

pscalett said:
I noticed this same problem on mine. Looks like I'll be calling Sprint tonight and stopping by my local store. Maybe I'll just go to Sprint World HQ here in KC and talk to them about it.
Click to expand...
Click to collapse
Please do....I'm wondering if there is a bug in the sms server that is causing this and it is slowly spreading nationwide. I call dibs on pointing this out if this is the case. This was from the mouth of a Sprint Employee. "Sprint will not do anything on an individual level but if the problem spreads to more than enough people, they will jump on it immediately." Now how much people is the real questions? I think the Sprint people thought I was crazy and now they are gonna be like....damn we should have listened to him. It's been going on for about 2 weeks now and I'm hoping it gets fixed before the end of the billing cycle.

Hey OP...as you may have figured by now your not the only one. I get it too. I kind of just let it go since it was minor. Mine also, when someone sends me a pic it goes to the very top of the conversation as opposed to in line with the rest of the texts...again i kind of let it go, but i do understand that we all paid our money, we should have perfection or at least 99.9. Thing is i dont want to swing by sprint and them see warm 2.2!!!! Then i'm really screwed!!!!!!!!!!!!!!!!!!!!!!!

Just do a backup and flash a stock RUU.....sprint needs to know about this..It has nothing to do with our phones but everything to do with their servers and they wont do anything until enough people complain. Anybody in the midwest that is getting text message problems, please call Sprint and complain. Explain to them exactly what is happening and tell them to give you a ticket number and tell them you expect a call within 72 hours. Get you case in so this can be fixed for everybody.

Related

MMS and Text messege delivey... slow??

Is there an issue with text messeges taking like YEARs for them to be delivered to a non-sprint device? I have a buddy who has this phone. We were at the bucs game and he was trying to text me a few times. I did not get them until we met back up. I thought it was due to the high congestion of the local tower but it continued through out the day. Anyone else experience this? I was ready to go out and buy this phone until I found out about this. BTW I have VZW.
eakrish said:
Is there an issue with text messeges taking like YEARs for them to be delivered to a non-sprint device? I have a buddy who has this phone. We were at the bucs game and he was trying to text me a few times. I did not get them until we met back up. I thought it was due to the high congestion of the local tower but it continued through out the day. Anyone else experience this? I was ready to go out and buy this phone until I found out about this. BTW I have VZW.
Click to expand...
Click to collapse
Just today at work me and a buddy who run different departments were shooting pics back and forth, they appeared on his phone nearly instantly after they officially left mine...I have an ET4G he has a E4GS.
Sometimes that happens. Depending on if you ever got away from that one tower there could have been a message queue a mile long that needed to be processed first..Hell, it could have been your Verizon service. I know that sometimes that same thing happens to me with people on Verizon though that never happens to me with anyone else.
I think just consider it 'random' and feel better about it as there are so many variables that may or may not be involved that it isn't worth worrying about. In my experience in my area with my friends this is not typical at all. That may be completely opposite to you, but, I doubt it. Test more if you want to be sure. I feel confidant that you'll both come up with nearly random in-explainable results...and if the results are so repeated that it's obvious what the problem is I doubt it's that ET4G's send messages slowly.
...though I have been wrong before...
It did happen a few times when I had the Photon also. Maybe its just sprint.... When I had the photon it was between myself and my wifes iPhone on ATT.
I am having issues sending picture mail in the first place due to the data issues on this phone
eakrish said:
Is there an issue with text messeges taking like YEARs for them to be delivered to a non-sprint device? I have a buddy who has this phone. We were at the bucs game and he was trying to text me a few times. I did not get them until we met back up. I thought it was due to the high congestion of the local tower but it continued through out the day. Anyone else experience this? I was ready to go out and buy this phone until I found out about this. BTW I have VZW.
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App

High pitch squeal / squeek / fax tones during phone calls

Anybody running into this? I bought a GNex about 2 weeks ago and when on a call I get a high pitch squeal randomly. Loud... like pull the handset from my head loud. The person on the other end doesn't hear it. I called VZW several times and they say they haven't heard of this. My wife got the same phone when I did and it happens to her, too. My twin got the phone about a week later and his is fine. I took the phone in to VZW earlier this week and they mailed me a replacement... it does it also. I changed the ROM to the Open Kang ROM to see if it might be a software thing... still doing it. Very frustrating. It happens when sitting in my office on 4G or 3G, when driving, etc... no real rhyme or reason that I've been able to figure out. The squeal happens every 3-15 minutes without any real pattern. I don't see any notifications or anything that are new after the squeal takes place.
If anybody else is experiencing this can you post? If you fixed please advise! Thanks!!!
aharper said:
Anybody running into this? I bought a GNex about 2 weeks ago and when on a call I get a high pitch squeal randomly. Loud... like pull the handset from my head loud. The person on the other end doesn't hear it. I called VZW several times and they say they haven't heard of this. My wife got the same phone when I did and it happens to her, too. My twin got the phone about a week later and his is fine. I took the phone in to VZW earlier this week and they mailed me a replacement... it does it also. I changed the ROM to the Open Kang ROM to see if it might be a software thing... still doing it. Very frustrating. It happens when sitting in my office on 4G or 3G, when driving, etc... no real rhyme or reason that I've been able to figure out. The squeal happens every 3-15 minutes without any real pattern. I don't see any notifications or anything that are new after the squeal takes place.
If anybody else is experiencing this can you post? If you fixed please advise! Thanks!!!
Click to expand...
Click to collapse
Yes, that happened to me when i was running stock at first too. Once i flashed AOKP 4.0.3 and franco's kernel, I haven't had that problem at all. It was REALLY annoying, sporadic, no rhyme or reason. It was also waaayyy louder than i thought the speaker could ever get ironicly enough. Also dont know if the new radios might have helped too, I flashed those separately because they aren't included on the 4.0.3 roms. Hope it helps =\
I called Verizon about this again today. I had enough trouble with one device that they sent me a second device. The second device does it too. Very frustrating. The device is also much slower than my old Incredible. I officially hate this device. Should be faster with a solid connection to 4G. I'm going to see what is necessary for VZW to somehow get me out of this device and into anything different. Hell, at this point I'm ok with an iPhone... anything but this.
I'm going to use this thread to track what I've been doing in the hopes that it can help others if they are dealing with VZW with this issue.
Dec/11 - bought the GNex new. Had the squealing problems and talked with the store I bought it from. They thought it was an app and suggested I make changes to my apps. I did that for a week or so and they finally exchanged the phone for new.
Jan/12 - new device arrives. Same trouble. I dropped the stock OS and went to the OKP OS. Same trouble. Figure I'll take notes for vzw and see if I can figure it out. What I found...
Seems to happen when talking with other mobile users, never to a land line. Later narrowed it down to only other vzw users, did not happen when talking to at&t users. Later narrowed it down that it only happens to other vzw users who are using the GNex device as well.
Called vzw last week after growing frustrated again. They had me do some troubleshooting on the device and re-provisioned my account. Same trouble. They sent me another new device. I put this device back to stock and relocked.
Feb/12 - 3rd device arrives. Stock OS, no apps installed. Had the same problem that same day. Called vzw the next morning and they had me put the device in safe mode so that they could determine if the problem was hardware or software. If you didn't know there was a safe mode now you know. Boot holding the down vol button until you're in the OS. Immediately had the same problem.
Called vzw back and demanded a different device. They told me they couldn't change the device because I was outside of 14 days. No kidding, I wouldn't be outside of 14 days if vzw hadn't been asking me to do all of this troubleshooting. I finally agree to pay full retail price if they credit my account for the past 3 months of troubleshooting. Nope. They make me upgrade eligible and I went a completely different direction to an iPhone hoping that this stupid squeal would be gone. I'll sell the GNex for close to retail on Craigslist at this point.
Mar/12 - iPhone is running for a day and I talk with my wife (GNex device). The squeal is there but MUCH SOFTER in volume. I will talk with my brother as I leave work tonight because I always have trouble with him on the phone. Hopefully this will help me know for sure.
What I think I'm finding is that it's not necessarily my GNex that had a problem... it's the reception from OTHER GNex users that is causing me the trouble. My wife has complained about the problem as well but at a much lesser frequency and only when on the phone with me. We don't talk on the phone that much. The curious piece is that my brother doesn't have the problem.
More to follow as I figure out for sure whether or not the iPhone has the same problem. If so then it's not my device, nevermind that I'm on my 4th device in 3 months. VZW has been entirely worthless through this process and has made me fight the entire way. Their customer service is horrible and the managers that I have been talking to should be fired. I can't believe they allow managers to talk with customers the way some of these guys do (especially this last Paul LaFranky dude (not sure about his last name)).
So I just came across this thread while doing my normal daily browsing here and find it interesting.
My nephew who has a SGSII here in east coast Canada on Bell txt'ed me earlier to ask if I ever get a "crazy squeal noise from your phone when you're trying to make/receive a call".
It's not all the time. He said it happened about 4 times in the past few months and it's only a land line. He doesn't make a lot of voice calls, mainly the 1 land line (work). When it happens, he hangs up and calls back and it's fine.
It may be completely unrelated to your issue. He's on stock gingerbread.
Anyway, thanks for posting the details and keeping record, i'll follow this for sure.
I have now had two calls today with the high pitch noise. At this point it is def not my device as I'm now on an iPhone. Good news is I can go back to the gnex. Bad news is that I'm all but certain that gnex devices are somehow SENDING these tones. With as unhelpful as vzw has been I'm beginning to think I may simply need to call those people less often... So annoying. I'll call vzw in the morning and see what they have to say. Ugh.
Mine does it too. It is my second one as my first stopped working on 3g so they replaced it. The first phone did it too. I just live with it.... I dont talk on phone much.
I get them as well with the GN, but I was also getting it with my thunderbolt from time to time.
My brother is upgrading to 4.0.4 today and will drop a new OS on his GNex. Once he does that I have asked him to call me to chat for a little bit. It would be great if that takes care of the problem! Fingers crossed. If that doesn't solve the problem I will call VZW with the additional info. If it does then I'll go back to the GNex and sell this new iPhone.
Update - called VZW to have my account updated with the latest notes. While on the phone the lady I spoke with acknowledged that there is a KNOWN ISSUE FOR THIS PROBLEM with Samsung devices. The devices that she said are affected are the Galaxy Nexus, the Charge and the Stratosphere. Samsung is supposedly working on an update that will address the problem. No ETA for that update.
I sure wish someone had told me about this sometime over the past 3 months of troubleshooting... it would have saved me the money for the iPhone as well as the hassle with vzw. Hopefully someone here will get some good out of this.
How odd. I have a VZW Nexus, but have not encountered this issue. I don't often make calls, but they sound fine when I do.
The problem is on the other end for the person you are talking to... they will hear a high pitch squeal from time to time. Mine would do it as often as every 10-15 seconds or so or could be as little as every half hour (or not at all depending on length of call).
I have talked with my brother a couple times today after he upgraded to 4.0.4 and haven't had the problem at all. I wonder if that update includes some work to fix this. ??

LTE Gnex Radio Problems? Try This

Background
This is by no means definitive, so don't everyone go get your panties in a wad and pitch fits like 12 year olds.
So several days ago I noticed that my GNex was starting to have issues with dropping calls and data connections. Basically, I was dropping data and voice despite having a connection to the network about every 2-5 hours, requiring a reboot. This happened over a 3 day period in a stationary position, in radically different places (like 80-150 miles apart). It was happening on 3G and on 4G so I was pretty confident that it wasn't just a localized outage or the local tower acting up. I'm no expert and certainly no /dev, but I've been around some Android devices a time or two.
I'm a big proponent that 95% of problems with an Android device are user error. That doesn't mean you're holding it wrong or that you're stupid, merely that something the user has installed or set is affecting something else, that affected something else. As an example, shortly after getting my GNex I installed TweetDeck. I had used Navigation several times to test GPS (first thing I did being a SGS owner) so I knew it worked and worked well. Anyway, immediately after installing and setting up TweetDeck, my GPS crapped. It would see satellites but not connect... even after 30 minutes....even after rebooting, clearing AGPS data, blah blah. Being objective, I decided to freeze TweetDeck with TB. As soon as I did, GPS returned. As soon as I unfroze it, GPS failed. I uninstalled TweetDeck and reinstalled from the Market, and had no more issues.
Solution (For me at least)
With that event in mind, and a crapped out radio, I went looking through my app drawer for apps that access the radio. I picked out Network Info II 0.6.0, Real Signal 3.5 and Network Signal Info 1.51. I rebooted and waited. Here it is three days later, and I have yet to have a single voice or data drop. If I've had one on the data side, I haven't noticed and it certainly wasn't for long.
I don't know how or why. All I know is that I've never had any form of radio trouble and those apps were recently installed, and that without them, the radio issues are gone. Take it for what it's worth, which probably isn't much. But if you're on 4.0.4, with 4.0.4 radios and you're suffering from radio problems, flip through your app drawer and remove or freeze applications that have the sole purpose of polling data from your radios. Who knows, maybe having 3 was 1 or 2 to many.
Thanks for the write up. And I really think the issue with certain apps interfering with OS-level stuff is a big issue, and one that nobody seems to want to notice.
There are a ton of posts, not only on this forum but on others, where people are saying they have so many issues with the Nexus and this and that. What a lot of people don't realize is that, yes, certain apps that are either poorly coded in general or not coded for ICS can potentially interfere with the normal operations of your phone.
A lot of people tend to use/stick with apps that they are used to, right? I came from the G1, the very first Android phone, so I've been using Android for awhile, and I bet that other people are too. Some apps are a staple of people's usage, meaning as soon as they get a new device, those same apps are the first to be downloaded and installed. However a lot of times those apps are abandoned by their developers, never to be touched again.
So of course an app that was coded on Froyo or even Eclair that calls the GPS or the radio or bluetooth stack or something else hardware related can potentially cause issues, especially with ICS being such a radical change from Gingerbread.
Question for OP. When you lost your data after 5 hours or so, was your 4G or 3G signal still showing as well as the data bars still moving like they are active but technically your data is not connected at all?
Was it apps you added that you froze or system stype apps? How did you see what accesed the radio?
[email protected] said:
Question for OP. When you lost your data after 5 hours or so, was your 4G or 3G signal still showing as well as the data bars still moving like they are active but technically your data is not connected at all?
Was it apps you added that you froze or system stype apps? How did you see what accesed the radio?
Click to expand...
Click to collapse
Yes. It was doing the typical thing you read about where people will have gray bars, 4G/3G showing, "Verizon Wireless" on the lock screen but no connection to anything at all.
The applications I froze are all 3rd party market apps. Check out the permissions for Network Info II as an example. My not so scientific hypothesis wonders if too many apps that can read "Network State" and "Phone State" going at once is too many. Again, not really based on anything at all, but I wouldn't be surprised to learn that multiple apps or a poorly coded app constantly requesting Network/Phone State could throw radios into a tailspin and cause those radio crashes that we see from logcats.
And as a disclaimer, I'm not knocking those applications or saying that there's anything wrong with them. I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation. Going back to what I said eariler, 99% of people that install TweetDeck on their GNex probably don't have GPS issues because of it, ever. I did until uninstalling and reinstalling and haven't had issues since.
I see this as possibly being no different, at least in regards to a 4.0.4 Bootloader, OS and Radio Package.
Food for thought: Apps have not been updated to work 100% with ICS?
KWKSLVR said:
Yes. It was doing the typical thing you read about where people will have gray bars, 4G/3G showing, "Verizon Wireless" on the lock screen but no connection to anything at all.
The applications I froze are all 3rd party market apps. Check out the permissions for Network Info II as an example. My not so scientific hypothesis wonders if too many apps that can read "Network State" and "Phone State" going at once is too many. Again, not really based on anything at all, but I wouldn't be surprised to learn that multiple apps or a poorly coded app constantly requesting Network/Phone State could throw radios into a tailspin and cause those radio crashes that we see from logcats.
And as a disclaimer, I'm not knocking those applications or saying that there's anything wrong with them. I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation. Going back to what I said eariler, 99% of people that install TweetDeck on their GNex probably don't have GPS issues because of it, ever. I did until uninstalling and reinstalling and haven't had issues since.
I see this as possibly being no different, at least in regards to a 4.0.4 Bootloader, OS and Radio Package.
Click to expand...
Click to collapse
Alright, so will that app tell me what is accessing that feature or do I need to go through every app to find out and what exactly shoould t say in the access?
Help me out here please because this is starting to annoy me!
The fastest way to see what apps have what permissions is Menu > Settings > Apps then go through each app and scroll down to permissions. Or you could back up your apps with TB, do a Nandroid then completely wipe the phone and live with it totally untouched (minus your gmail account of course) long enough to see if the problem goes away.
Don't get me wrong, I've never seen an LTE phone that didn't occasionally disconnect for a few seconds. People that say, "OMG my Rezound never did" are either full of it or didn't pay attention. There are plenty of cases of Rezounds, Maxx's and Thunderbolts having brief and random disconnects. But there's a huge difference between that, and losing signal as often as I was and as often as many people here say they do. There's nothing you can do about the former, but hopefully this is something that can be done about the latter. I'm crossing my fingers that it may help and that it's a relatively simple fix because frankly, until I saw it for myself I thought a lot of people were being drama queens. I'm not a whiner, I'm a doer, so I encourage everyone to go do.
bk201doesntexist said:
Food for thought: Apps have not been updated to work 100% with ICS?
Click to expand...
Click to collapse
There are a TON of apps that haven't been updated. I have a paid app that hasn't been updated that is abandoned and still on the market. Works fantastic except on ICS.
I've thankfully been free of radio issues thus far on my GNex, but I want to thank you for this thread.
KWKSLVR said:
I'm a big proponent that 95% of problems with an Android device are user error. That doesn't mean you're holding it wrong or that you're stupid, merely that something the user has installed or set is affecting something else, that affected something else.
...
Being objective, I decided to freeze TweetDeck with TB. As soon as I did, GPS returned. As soon as I unfroze it, GPS failed. I uninstalled TweetDeck and reinstalled from the Market, and had no more issues.
Click to expand...
Click to collapse
KWKSLVR said:
I make this post primarily to encourage people with the issue to think logically about the apps they have installed and experiment with removing some out of the equation.
Click to expand...
Click to collapse
Not to jump up on too high of a soapbox, but I couldn't agree with you more.
It's very satisfying to read about people methodically, empirically testing. It's something that seems rare these days.
So thank you!
KWKSLVR said:
The fastest way to see what apps have what permissions is Menu > Settings > Apps then go through each app and scroll down to permissions. Or you could back up your apps with TB, do a Nandroid then completely wipe the phone and live with it totally untouched (minus your gmail account of course) long enough to see if the problem goes away.
Don't get me wrong, I've never seen an LTE phone that didn't occasionally disconnect for a few seconds. People that say, "OMG my Rezound never did" are either full of it or didn't pay attention. There are plenty of cases of Rezounds, Maxx's and Thunderbolts having brief and random disconnects. But there's a huge difference between that, and losing signal as often as I was and as often as many people here say they do. There's nothing you can do about the former, but hopefully this is something that can be done about the latter. I'm crossing my fingers that it may help and that it's a relatively simple fix because frankly, until I saw it for myself I thought a lot of people were being drama queens. I'm not a whiner, I'm a doer, so I encourage everyone to go do.
There are a TON of apps that haven't been updated. I have a paid app that hasn't been updated that is abandoned and still on the market. Works fantastic except on ICS.
Click to expand...
Click to collapse
My signal does not go in and out but randomly after hours it might lose data. By looking at it you would never know because everything looks fine but behind the scenes data is not working.
So what we are looking for in permissions is what you listed in the 1st post and that is what will be listed?
I thought it might have been me running in tablet mode so I just switched back to phone mode. Would like to see if it is actually caused by what you say.
[email protected] said:
My signal does not go in and out but randomly after hours it might lose data. By looking at it you would never know because everything looks fine but behind the scenes data is not working.
So what we are looking for in permissions is what you listed in the 1st post and that is what will be listed?
I thought it might have been me running in tablet mode so I just switched back to phone mode. Would like to see if it is actually caused by what you say.
Click to expand...
Click to collapse
When I froze those apps, I picked them because I knew they had access to:
Network communication > view network state > Allows an application to view the state of all networks. The part in bold is the description of what the permission "View Network State" means. That permission is under the "Network Communication" Category. Some apps will have more than that single permission under Network communication, some with have none at all. "Real Signal" has the fewest permissions out of the three I froze, and maybe all three don't HAVE to be frozen, but I haven't tested that yet.
Another random thought. During that time period, I also had a BUNCH of random reboots.
Maybe on other devices 95% user error might be closer.
But, not on my Gnex! What if you bought a completely new phone and have not installed any apps. The first time you open up the stock browser and use it for 5 mins or so on 4G LTE next to the cell tower -75 db stationary and still lose connection of both data and voice with "the triangle of death" on 2 separate GNex with 2 new SIM cards? Is this a bad batch? To me, "bad batch" is when we say 1/100 is a faulty device but this is almost reversed with GNex. We should exchange devices until we find a "good batch"
All I am saying is we all should be a little more compassionate for people like me. A lot of problems are made by users, sure. But it sure isn't 95%....It's more like samsung/google/vzw 60% in this case..
I hope I shed a little light on all the users that did not create user errors yet still have radio problems and VZW keep telling us to wait because issues are going to be addressed with the supposed firmware update that should have come in Feb, now March. Now...I don't know when.
Thank you for your post though, you rock
With anything, even product reviews, the people that have issues always make up the vocal majority. No one talks about how things work the way they should.
If my phone truly dropped 4G as often as it did when I had this application conflict, I'd be in the Verizon store every day until I either had a replacement or got banished from the store. If Verizon told me that it was "normal" and to live with it, I'd pay a visit to management at a different Verizon store and pay an online visit to the BBB. If that didn't do any good and I was really REALLY bored and had nothing better to do, I'd probably draw up a letter to Verizon's legal department about the liability Verizon could have when a consumer can't call 911 in the middle of the night because the radio crashed.
I still think it's an incompatibility hiccup with ICS more than necessarily an issue with Verizon's LTE network. I see GSM owners complaining too. And, as I said in the OP, I can only speak for a "stock" 4.0.4 bootloader/modem/radio experience. I've seen posts from people talking about how their problems have disappeared since making the move from 4.0.2 to 4.0.4. All I can speak of from my own experiences is that I've never had a problem from any version of ICS other than what I experience.
Come to think of it, I think I'll defrost all three of those apps and see what happens, especially since the phone in my hotel seems to be in working order.
OK, in the couple of hours since I've defrosted my cocktail of apps I've:
Opened the Facebook app, watched it poll for GPS and lock, then closed the Facebook app only to have GPS stuck on. Once I went into Settings > Apps > Location Services and tried to uncheck "GPS satellites" it rebooted. After rebooting, the phone showed 4G and a connection to Google's servers but I couldn't browse or use any app that is web based (like speed test, gmail, etc). After about 30 minutes of trying, I rebooted again and everything was fine. I have a feeling it's related to Real Signal looking at the plethora of stuff it monitors and that it's starting up on boot.
That's all I personally care to see. Needless to say, they're all frozen again.
I don't think there is a problem with real signal, I only installed it after having these problems to start with.
Since I got my nexus it works randomly drop voice and data. People would call me and get a fast busy signal. I tried many different radios and they all behaved the same. I switch my network to CDMA only and haven't dropped data or voice in two days.
Sent from my Galaxy Nexus using xda premium
On 4.0.4?
I don't think it's necessarily just Real Signal. I think it's multiple apps polling data from your radios. After a few more days, I'll go through them one by one. So far in my experiences on my setup, there is something up with the combination of those apps.
Again, there's a solid chance that a combination of other apps could give other people similar issues.
I will say this, even if I had problems before installing those apps, this particular cocktail would only make them worse.
It's not ICM
Hi all - First post here, but have been having nightmares with my wifes Nexus - mine is fine and drops NOTHING - EVER.
Hers on the other hand - we are on our 2nd one and I was informed by Verizon today, that it's been 14 days since they replaced it and I"m stuck with it. I rooted her phone and installed 4.04, which fixed the random reboots she was having, and her signal LOOKED stronger, but she is dropping calls like mad and getting kicked off the network randomly.
Anyway, it does not appear to be a ICM thing - I was reading a review on IT World (I'm not allowed to post links till I've posted 8 times? ) - They are describing THE EXACT SAME THING the Galaxy Nexus is having. So there is a switching problem WITH VERIZON. The Maxx isn't ICM and the phone is a totally different manufacturer (Motorola)
I'm smelling class action lawsuit.
Woodk1 said:
Hi all - First post here, but have been having nightmares with my wifes Nexus - mine is fine and drops NOTHING - EVER.
Hers on the other hand - we are on our 2nd one and I was informed by Verizon today, that it's been 14 days since they replaced it and I"m stuck with it. I rooted her phone and installed 4.04, which fixed the random reboots she was having, and her signal LOOKED stronger, but she is dropping calls like mad and getting kicked off the network randomly.
Anyway, it does not appear to be a ICM thing - I was reading a review on IT World (I'm not allowed to post links till I've posted 8 times? ) - They are describing THE EXACT SAME THING the Galaxy Nexus is having. So there is a switching problem WITH VERIZON. The Maxx isn't ICM and the phone is a totally different manufacturer (Motorola)
I'm smelling class action lawsuit.
Click to expand...
Click to collapse
Yes, indeed.
I am very surprised to not see one yet!
It means all of us with this issue is actually being very patient at the moment.
Again, for anyone who does not have this issue at all, and curious to find out what issue we all are actually describing here by LTE Connection Drop + Voice Drop is:
http://code.google.com/p/android/issues/detail?id=24345
Man, why does everyone always pull the "class action lawsuit" line?
Firstly, you're not going to do diddly squat legally about it, so stop kidding yourselves (and us) when you say that you are.
Secondly, no service you pay for is "guaranteed" to have 100 percent uptime. My Comcast internet connection goes out every 3 months or so anywhere from 5 hours to one day. Do you think I have legal grounds to sue them? Nope. When a thunderstorm rolls in and you lose power for 12 hours, can you sue your electric company? Nope. In fact, I'm pretty sure in most ToS contracts or forms that you sign, it states that they do not guarantee you anything.
LTE is a relatively new technology, and Verizon is the first one to offer it. There's going to be hiccups and growing pains. It's been a year and it's A LOT better now than it was back when it started. 4 years ago we were all happy to get something faster than EDGE speeds, and now we get connections capable of 40/50 Mbps down at times and people are still unhappy.
I understand people's frustrations with the network/switching issues that are occurring between CDMA and LTE. But we live in an age where everyone feels entitled and important enough to immediately sue another company at the drop of a hat.
Here's an idea: If you are faced with severe LTE switching issues and it's a continuing problem, call up customer support. Tell them what is going on and let them help you. Yes, you are past your 14 day return policy, but you have one year of a device warranty, they will ship you out a replacement device. Since your Nexus works fine and your wife's does not, it leads me to believe that it's not a network issue in your area, and either: A. Your wife got two dud Nexus' in a row, which sucks but is not unheard of. or B. Your wife is using some sort of app or service that interferes with the radios. If you still have the issue after the 3rd replacement, call them up again and explain, and they just might be able to give her a different device altogether if the Nexus isn't working out for her.
Dear MMcCraryNJ,
hear my long plea if you have the time. If you don't that is okay.
Firstly, I am so glad you seem to be not affected by this issue on your GNex.
Every single day, I wish I was in your shoes.
On the brighter side though, with LTE Data/voice drop & severe vertical banded screen & one-way-microphone outbound issues, I have come to join in XDA forum. I've also gotten to know countless VZW / Samsung customer service representatives at all levels as well as local store customer service agents.
Secondly, I, and I am sure most of all the other GNex users with above issues, know that no product & service is guaranteed to work perfectly with 100% uptime. Personally, it takes a significant defect of any product for me to call customer service at all. I am one of those, who actually try to live with products that have minor flaws everyday. If GNex did drop my LTE 3-4 times daily, I'll live with out much complaint let alone 3 months that you've mentioned. 3 months of uptime would be heavenly, but I'll actually be perfectly fine with 3 hours uptime. Sadly, my uptime has been 5-10 minutes with LTE. If my one-way-outbound microphone cut off issue happened 1 out of 10 calls, I'll live happily. Sadly, nearly every other call makes my voice into a robot and I have to call back again.
I am personally coming from Droid Eris long long time ago when Android first came out with newest 3G technology back then. Eris wasn't issue free but my satisfaction with what I got was pretty much 95%. You see, as long as a product performs what it claimed to perform 60-80% of the time, I am happy. Claim and advertisement that Verizon made with CDMA Galaxy Nexus in the US as "The latest 4G LTE Pure Google ICS Smartphone meeting the most reliable 4G LTE network in the world" caught my attention, as many others, to actually decide to choose this new phone with my 2 year contract over countless androids that came out in the past 3 years.
Again, our frustration that is described on these post is described in detail here (http://code.google.com/p/android/issues/detail?id=24345) it is not a LTE / 3G switch issue only. Switching issue is very small part of this problem. I will not go into any detail of one-way-microphone cut off issue at all, due to its unrelated nature on this particular post.
Just as you've suggested naively, your suggestions in order that you wrote them in were exactly the steps I thought and took from very first day I purchased GNex back 4 months ago from a local verizon store. I have stopped in at the verizon store to get exchanges of the actual device, SIM card. None of these replacements solved the data/voice drop issue. I am all talking about stock 4.0.2 without any apps installed on any of these GNex. It can't possibly be the bad batch as I received batches that were produced in completely different months. I loved whatever was promised with GNex so much that I was determined to find the one for me as no other devices Verizon offer at the time appeal to me at all. As 14 days has passed, the local verizon literally told me to 1) wait for the update 2) root your device to all different kind of ROMs and Radios 3) call VZW customer service. Which all of the advice I followed, I am still waiting, none of the ROMs and radios solved the issue.
Ever since then, I've been calling VZW and Samsung (when VZW transferred me), and talked to numerous customer service representatives at all different levels. (Level 2 & 3 and at some points I've been transferred and escalated twice to a person really higher up) With my efforts, I was actually able to tag all my calls, and send them screenshots (via e-mail), and follow through to actually make above mentioned issues officially put on VZW technical bulletin. It is a huge improvement, because when I first called about these issues, they told me "They've never heard of these issues.". Now, after all of our efforts, they admit there's over "120 technical bulletin reportings on these issues."
You do think that it is so easy to get a refurbished factory replacement phones with all my history right?
The answer is sadly No. They've been literally telling me to wait a little longer no matter how much I requested them to get me a replacement device. They are indeed very hesitant to keep replacing devices for all of us especially now days where the supposed update is going to resolve these issues. And on my end, I want to see first if the software fixes it, because I am literally burned out to get another screen protector install everything again, etc. Now the official answer is wait....for the update. If they don't keep their last promise of March update to resolve this issue, that is when my patience will run out and I'll jump to a different device. Although, I love this phone....
This is the longest online posting of any sort in my life ever. I hope this somewhat gives you a new perspective on what unlucky GNex user like myself had to go through in the past 4 months due to getting "bad batches"
Trust me, I hate to live in a society where anybody can talk about law suits against anybody. But, this was one of my first moments that I literally felt like I was hopeless & got betrayed by VZW / Samsung / Google. I started to fantasy about way to make them responsible for this poor product and service. All I wanted was at least 60 percent working "4G LTE Smartphone". (4G LTE is turned off due to connection drop, Phone is unusable as business purposes due to frequent one-way-cut off). After $299 and 2 year contract with $75 monthly service bill of 4 months with all the time I spent to help VZW/Samsung with this issue as a customer, my wildest dreams of thinking of participating in a class law suit, which will never happen, actually make me feel a little bit less helpless towards these major corporations as a customer.
Thank you for hearing my plea. I sincerely apologize for the length of this post.
Hope more of us can enjoy this great GNex in the near future.
After all, I love this device, I love this XDA forum and GNex community. I wouldn't want to switch to a different device just yet

Not receiving incoming calls. Big problem!!

Having a very strange problem with my S3. I've noticed it at home more than anywhere else but basically what happens is that if someone calls me, the phone doesn't ring on my end but I do get a voicemail notification after they've left a message. Then when I talk to them, they tell me that on their end my phone rang once or twice and then went straight to voicemail. And my phone doesn't show any missed calls so obviously, my phone never detected that there was an incoming call.
BTW, it doesn't happen all the time. Sometimes the calls come in just fine.
I've checked my signal strength and it's always between 3 and 5 bars. I've missed more calls than I can count because of this. Some of them were important calls.
And I don't have any problem making outgoing calls or using the data connection for anything.
Any idea what's going on?
BonesHopkins said:
Having a very strange problem with my S3. I've noticed it at home more than anywhere else but basically what happens is that if someone calls me, the phone doesn't ring on my end but I do get a voicemail notification after they've left a message. Then when I talk to them, they tell me that on their end my phone rang once or twice and then went straight to voicemail. And my phone doesn't show any missed calls so obviously, my phone never detected that there was an incoming call.
BTW, it doesn't happen all the time. Sometimes the calls come in just fine.
I've checked my signal strength and it's always between 3 and 5 bars. I've missed more calls than I can count because of this. Some of them were important calls.
And I don't have any problem making outgoing calls or using the data connection for anything.
Any idea what's going on?
Click to expand...
Click to collapse
Is it just certain contacts? You may have them set to go directly to voicemail by accident. I can't find where the list is in the phone though ahah, I can see how to add them to reject list though.
EDIT: Found it go to dial-pad and hit menu and then call settings and you will see call rejection see if you have anyone in there.
Halmo said:
Is it just certain contacts? You may have them set to go directly to voicemail by accident. I can't find where the list is in the phone though ahah, I can see how to add them to reject list though.
EDIT: Found it go to dial-pad and hit menu and then call settings and you will see call rejection see if you have anyone in there.
Click to expand...
Click to collapse
Nope, has nothing to do with who's calling. Sometimes a call from the same person will come through but ten minutes earlier it didn't.
Ive had similar problems in the past. Turned out the phone signal was going up and down. When it was up, calls came through. And down, well duh. Either way, try a new radio. Maybe it'll hold a signal better. I've heard people complaining about H1, but cant say either way myself. Just a suggestion.
Ends said:
Ive had similar problems in the past. Turned out the phone signal was going up and down. When it was up, calls came through. And down, well duh. Either way, try a new radio. Maybe it'll hold a signal better. I've heard people complaining about H1, but cant say either way myself. Just a suggestion.
Click to expand...
Click to collapse
how can I try a new radio?
BonesHopkins said:
how can I try a new radio?
Click to expand...
Click to collapse
there's a thread in development. some people call em modems, but its the same thing. Choice of 3 i think.
Having the exact same issue is your phone always in lte while this happens?
Sent from my htc_jewel
Andrew149 said:
Having the exact same issue is your phone always in lte while this happens?
Sent from my htc_jewel
Click to expand...
Click to collapse
As far as I can tell.
stay away from LH1 modem it's trash....
BonesHopkins said:
As far as I can tell.
Click to expand...
Click to collapse
Same here
Sent from my htc_jewel
BNaughty said:
stay away from LH1 modem it's trash....
Click to expand...
Click to collapse
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
I have to say that even though on paper the S3 blows the iphone out of the water, for pure functionality without problems, the iphone is definitely way ahead of the S3. I'm pretty much stuck with it for the next two years but I have a feeling that if things stay more or less the same in the cellphone market, I'll probably be switching back to iphones after my contract is up. The S3 is very cool but I've just had way too many problems with it that I never had with my iphone. My iphone just..........worked. With my S3 calls don't come through, I'm constantly having to force stop apps so my battery doesn't drain all the time (and even then, half the time the battery drains like crazy no matter what), the visual voicemail is sketchy as hell and doesn't work right half the time, the data connection even when it shows a strong LTE signal is often very slow and times out a lot, and a bunch of other misc. annoyances that I never had with the iphone. I wouldn't say I'm sorry that I bought the phone because I wanted to try out the latest and greatest but when my friends and coworkers have asked me about it, I've been telling them they'll be better of waiting for the iphone 5. Sorry to vent but overall, after having it for almost two months, I've concluded that I'm very disappointed with this phone. Sure, I can do things with it that I couldn't do with the iphone but f*ck me, at least with the iphone I could do basic sh!t like receive phone calls and check my email without the connection timing out all the time.
BonesHopkins said:
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
I have to say that even though on paper the S3 blows the iphone out of the water, for pure functionality without problems, the iphone is definitely way ahead of the S3. I'm pretty much stuck with it for the next two years but I have a feeling that if things stay more or less the same in the cellphone market, I'll probably be switching back to iphones after my contract is up. The S3 is very cool but I've just had way too many problems with it that I never had with my iphone. My iphone just..........worked. With my S3 calls don't come through, I'm constantly having to force stop apps so my battery doesn't drain all the time (and even then, half the time the battery drains like crazy no matter what), the visual voicemail is sketchy as hell and doesn't work right half the time, the data connection even when it shows a strong LTE signal is often very slow and times out a lot, and a bunch of other misc. annoyances that I never had with the iphone. I wouldn't say I'm sorry that I bought the phone because I wanted to try out the latest and greatest but when my friends and coworkers have asked me about it, I've been telling them they'll be better of waiting for the iphone 5. Sorry to vent but overall, after having it for almost two months, I've concluded that I'm very disappointed with this phone. Sure, I can do things with it that I couldn't do with the iphone but f*ck me, at least with the iphone I could do basic sh!t like receive phone calls and check my email without the connection timing out all the time.
Click to expand...
Click to collapse
All of the issues you listed are not really S3 specific because I have had none of them and have had my phone since release. Apart from the video voicemail which I can't comment on because I have never used.
BonesHopkins said:
My baseband version is UCLG1.
btw, I never had this problem with my iphone 3GS which I had for almost 3 years.
.
Click to expand...
Click to collapse
I've had my I747 since release in June and not experienced any of these issues. Over the years with Blackberrys and the Galaxies I found most problems result from variances in the network. Signal strength, carrier software and even where the phone is in the house. I dislike much about the iPhone (I do have a 4th gen iPod) and much prefer the openness of the Android OS and NO iTunes. Hope things with S3 get better for you.
Still having the problem. It seems to happen most often when I have LTE enabled. I disabled it using the method mentioned in another thread where you remove the sim then enter a code which takes you to the menu where you can choose what to use.
When I had LTE disabled, it didn't seem to miss as many calls. But when LTE is on, I miss a crapload of calls. I'd leave LTE off but for some reason it keeps re-enabling itself every few days so it's turning into a massive pain in the ass.
Any suggestions?
I have the same issue as you, but I'm on Wind Mobile. This issue happens intermittently anywhere between 1 to 2 days, my phone will stop being able to receive calls. It's very frustrating and Samsung is really no help. After two attempts on trying to "repair" my phone, they have failed each time. The only thing they did was they ran a "RF Test" and everything passed, they said. So they re-flash my phone with the same ROM - again and again.. I told them, "This is my second time sending it in, and you guys are redo'ing the same steps as the first repair. You don't need to be a rocket scientist to know this, but wouldn't you think when you send me back the phone - the issue is still going to be there?!" ... And sure enough, when I got the phone back, I was still unable to receive calls..
So I took matters into my own hands - I flashed it with a older release stock rom and I tested it for 2 weeks, and it was able to receive calls. When I flashed with the earlier release, it also flashed the baseband. Either way, I should not be prevented from using the up to date software! This is a Samsung issue but if you ever tried dealing with them over the phone, it's painful. They said they would send me a REFURB replacement - (believe me, I tried fighting for a brand new phone, since I paid for a brand new phone and this issue came straight out of the box - it's not even my fault to begin with!) it's been 3 weeks and I still don't see any phone replacement nor did I receive any mails from Samsung.
Btw, Galaxy S3 is the phone I have.
If you discover a permanent fix for this issue, please let me know. I've been searching but no luck.
Thanks!
UPDATE: it's been over a month and I still don't see any phone replacement nor did I receive any mails from Samsung. So I called Samsung today after a month and 2 weeks. They said my replacement have been cancelled. First they said it's approved and requested me to send in my receipt for the phone. I had done the the very moment I hung up the phone from when they told me my replacement was approved (that was over a month ago). They want me to sent it in again to Samsung so they can "test". This is just ridiculous and getting out of hand. Does ANYONE have a fix for this????
Other forums are saying this is a wide spread issue...
are u missing imei, or just the problem you descibe... try flashing the latest modem... maybe yell at it while it flashes...
Nope, just having the issue I described... IMEI is exist and is valid.
aftershocks said:
Nope, just having the issue I described... IMEI is exist and is valid.
Click to expand...
Click to collapse
There's some newer modems out you could try but it still sounds like hardware...
Not sent from your phone...
Sorry for the late entry here but I'm also having the issue. aftershocks, and anyone else having this issue, open battery stats - what does your "mobile network signal" bar look like? Mine is mostly tan except for when I make calls, which then it goes green. I also have an HTC One X (AT&T model) and the bar's mostly green on the HOX.
I've flashed back to the original modem (UCLEM) to see if that helps and I'll move forward from there if not. UCDLK3 was the modem I was originally on when I noticed the missed calls. Here's the thread with radios: http://forum.xda-developers.com/showthread.php?t=1831898.

[Q] I need some help/advice

My SG3 replacement is only days old after a long battle with the old one. I thought a new phone would be the end of this but it too is doing the exact same thing with one new wrinkle. I will outline the symptoms and hope someone can help me out.
The problem is the phone will lose the ability to send or receive sms messages nor can the phone receive phone calls. The only way to restore the phone to working order was/is to reboot. I only become aware of the situation when family members would email me asking why I am not answering them. The phone always appeared normal to me, had bars of service etc. Only while waiting on a replacement phone from AT&T did I discover by accident that if I tried to make an outgoing call, 90% of the time would also fix the condition.
In my many call sessions with AT&T, I went through all the steps you would expect. New SIM card, made sure I was upgraded to 4.1.1 Jelly Bean, reset, they said they checked to make sure phone was provisioned correctly etc. Finally they said they would send me the warranty replacement.
The new fone came and for two days worked perfectly but I noticed it was running ICS so I upgraded to JB. The symptoms returned the same day. This could be coincidence or not as the old phone would sometimes go for days without an issue. Are the problems from JB or from an app I am running?
That one new wrinkle I mentioned is that in the middle of last night, the phone rebooted on it's own.
I have since deleted most apps on the phone trying to see if this is the cause. Only a dialer app is left on the phone and that too will go if the issue reoccurs. (EDIT: Also am still running Apex launcher)
My questions:
Is it possible an app intermittently can cause a phone to lose sms and incoming call ability?
Could the upgrade of JB be the cause by itself or an incompatibility between an app and JB?
If this reoccurs, do you see any merit in a reset with zero apps brought back?
Any other suggestions are most welcomed.
Thanks
I would try flashing another ROM. Something de-bloated, or if you dont need the Samsung stuff use AOKP.
s60convert said:
My SG3 replacement is only days old after a long battle with the old one. I thought a new phone would be the end of this but it too is doing the exact same thing with one new wrinkle. I will outline the symptoms and hope someone can help me out.
The problem is the phone will lose the ability to send or receive sms messages nor can the phone receive phone calls. The only way to restore the phone to working order was/is to reboot. I only become aware of the situation when family members would email me asking why I am not answering them. The phone always appeared normal to me, had bars of service etc. Only while waiting on a replacement phone from AT&T did I discover by accident that if I tried to make an outgoing call, 90% of the time would also fix the condition.
In my many call sessions with AT&T, I went through all the steps you would expect. New SIM card, made sure I was upgraded to 4.1.1 Jelly Bean, reset, they said they checked to make sure phone was provisioned correctly etc. Finally they said they would send me the warranty replacement.
The new fone came and for two days worked perfectly but I noticed it was running ICS so I upgraded to JB. The symptoms returned the same day. This could be coincidence or not as the old phone would sometimes go for days without an issue. Are the problems from JB or from an app I am running?
That one new wrinkle I mentioned is that in the middle of last night, the phone rebooted on it's own.
I have since deleted most apps on the phone trying to see if this is the cause. Only a dialer app is left on the phone and that too will go if the issue reoccurs. (EDIT: Also am still running Apex launcher)
My questions:
Is it possible an app intermittently can cause a phone to lose sms and incoming call ability?
Could the upgrade of JB be the cause by itself or an incompatibility between an app and JB?
If this reoccurs, do you see any merit in a reset with zero apps brought back?
Any other suggestions are most welcomed.
Thanks
Click to expand...
Click to collapse
It is possible that it's coming from a app that you have/had. Knowing which one though is hard and can only be tested by you (often uncommon apps).
I highly doubt it's from the upgrade to JB as more people would complain about this.
Usually, problem like this comes from either a bad SIM or on the carrier's side. Could be good to check your APNs as well (make sure they match your carrier's).
As for the phone rebooting, what exactly happened?
BWolf56 said:
It is possible that it's coming from a app that you have/had. Knowing which one though is hard and can only be tested by you (often uncommon apps).
I highly doubt it's from the upgrade to JB as more people would complain about this.
Usually, problem like this comes from either a bad SIM or on the carrier's side. Could be good to check your APNs as well (make sure they match your carrier's).
As for the phone rebooting, what exactly happened?
Click to expand...
Click to collapse
I will check the APN's, never did that before.
The rebooting is new. The phone was over 50% battery power and as usual, sat on a table along side my bed. 1:12am, I woke up to the AT&T tones you hear when it reboots and phone was lit and just finishing up rebooting. Hasn't done it since. So far today, the phone has lost sms/call ability once and the rest of the apps save Apex and Dialer1 were removed, all widgets etc.
All my APN settings are grayed out and I cannot change any of them so I thought I would post pics of same hoping they are correct.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
s60convert said:
I will check the APN's, never did that before.
The rebooting is new. The phone was over 50% battery power and as usual, sat on a table along side my bed. 1:12am, I woke up to the AT&T tones you hear when it reboots and phone was lit and just finishing up rebooting. Hasn't done it since. So far today, the phone has lost sms/call ability once and the rest of the apps save Apex and Dialer1 were removed, all widgets etc.
Click to expand...
Click to collapse
s60convert said:
All my APN settings are grayed out and I cannot change any of them so I thought I would post pics of same hoping they are correct.
Click to expand...
Click to collapse
Odd that you can't change them, althought, haven't been on stock in a very long time so dunno if they allow it.
They did make you do a factory reset in recovery right?
No, they had me to do it from an internal menu.
You said while running ICS you didn't encounter with that problem, run ICS for a couple more days to see if JB is your problem.
Sent from my SPH-L710 using xda premium
mar.ioo said:
You said while running ICS you didn't encounter with that problem, run ICS for a couple more days to see if JB is your problem.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
On this new phone which came with ICS, I had only ran that for two days before upgrading to JB which I am currently running. How do I go back to ICS?
s60convert said:
No, they had me to do it from an internal menu.
Click to expand...
Click to collapse
Know that this will make your phone like it was out of the box (data wise), therefor, you will lose your apps, texts, call logs and such. A backup is suggested before going through with this, which can be done in recovery as well (called nandroid, under backup).
Recovery mode: Hold vol up+home+power button until you see the recovery screen. There will be a factory reset option.
s60convert said:
On this new phone which came with ICS, I had only ran that for two days before upgrading to JB which I am currently running. How do I go back to ICS?
Click to expand...
Click to collapse
Flash through ODIN a Stock ICS ROM or another option is try to find an ICS ROM in the development thread/original development.
Tip: I always make a stock backup through recovery as soon as I root my phone.
Sent from my SPH-L710 using xda premium
s60convert said:
On this new phone which came with ICS, I had only ran that for two days before upgrading to JB which I am currently running. How do I go back to ICS?
Click to expand...
Click to collapse
stock firmware: http://forum.xda-developers.com/showthread.php?t=1968625
Thanks for the help guys! The phone has not had any issues since yesterday morning when I deleted all widgets and almost all apps. This is hardly definitive as it has fooled me in the past but another couple days will tell. If not, I will have to put your suggestions into play.
Last Wednesday I became aware that some incoming calls were receiving error messages (typically "the phone call can not be completed at this time" and not able to ring my phone. I have tried to call my S3 and received the error messages about 6 times on different days as have several callers. There are at least 3 different error messages one in English only with no error codes, one in English/Spanish with the error codes MI01ML & MI01EE or GE and one in English/Spanish with the error codes MI01GL & MI01EE.
At least 8 calls to AT&T tech support have resulted in different completely answers and no resolution. I was told today by an individual at the Costco wireless kiosk where I purchased the S3 that a friend of hers with an S3 has the same problem and her friend's husband knew someone at AT&T who told him this issue is a known problem and is caused by a mistake AT&T made in the programming and that it will take 1-2 months to resolve. Further, AT&T will not admit there is a problem and the level of tech support we can reach as consumers have not been made aware of the issue. This would explain why every time I called I got completely different responses and no resolution. The problem is only with S3's, no other phone AT&T uses.
My cellphone is my main business line thus I can not afford the luxury of having potential clients and current clients unable to call me on an intermittent basis for the next 1-2 months. Fortunately I bought my S3 on Black Friday and Costco has a 90 day exchange policy so I am picking up a new LG Optimus G today because the $20 I will have to pay to upgrade to it is a sale price that ends today.
There is a possibility rooting the S3 may resolve the issue and I spoke with a very technically savvy individual who also works at the Costco kiosk who offered to root my phone but said he could not guarantee it would resolve the issue. Thus I have no choice but to get the LG and I would much prefer keeping the S3 because I spent 35+ hours finding a case/holster combo that allows outward screen placement in the holster (BodyGlove ToughSuit) and probably won't be able to find one for the LG (BodyGlove doesn't offer the ToughSuit for the Optimus G).
I've spent at least 10 hours trying to resolve this issue and am really disappointed that I can't keep my S3 but I must have a phone that receives incoming calls so the LG is my resolution.
mty msi said:
Last Wednesday I became aware that some incoming calls were receiving error messages (typically "the phone call can not be completed at this time" and not able to ring my phone. I have tried to call my S3 and received the error messages about 6 times on different days as have several callers. There are at least 3 different error messages one in English only with no error codes, one in English/Spanish with the error codes MI01ML & MI01EE or GE and one in English/Spanish with the error codes MI01GL & MI01EE.
At least 8 calls to AT&T tech support have resulted in different completely answers and no resolution. I was told today by an individual at the Costco wireless kiosk where I purchased the S3 that a friend of hers with an S3 has the same problem and her friend's husband knew someone at AT&T who told him this issue is a known problem and is caused by a mistake AT&T made in the programming and that it will take 1-2 months to resolve. Further, AT&T will not admit there is a problem and the level of tech support we can reach as consumers have not been made aware of the issue. This would explain why every time I called I got completely different responses and no resolution. The problem is only with S3's, no other phone AT&T uses.
My cellphone is my main business line thus I can not afford the luxury of having potential clients and current clients unable to call me on an intermittent basis for the next 1-2 months. Fortunately I bought my S3 on Black Friday and Costco has a 90 day exchange policy so I am picking up a new LG Optimus G today because the $20 I will have to pay to upgrade to it is a sale price that ends today.
There is a possibility rooting the S3 may resolve the issue and I spoke with a very technically savvy individual who also works at the Costco kiosk who offered to root my phone but said he could not guarantee it would resolve the issue. Thus I have no choice but to get the LG and I would much prefer keeping the S3 because I spent 35+ hours finding a case/holster combo that allows outward screen placement in the holster (BodyGlove ToughSuit) and probably won't be able to find one for the LG (BodyGlove doesn't offer the ToughSuit for the Optimus G).
I've spent at least 10 hours trying to resolve this issue and am really disappointed that I can't keep my S3 but I must have a phone that receives incoming calls so the LG is my resolution.
Click to expand...
Click to collapse
Question, did it ever effect text messages to your phone, both outgoing and incoming? This sounds like what I have concluded also. Thank you for the info. My phone failed yesterday afternoon again and I was going to do a factory reset from recovery but am pondering root/rom to see if that might be a better solution. My only worry is that if the phone also fails with a rom, I will have issues going back to AT&T for help with the boot counter thing (not sure exactly what is called) but they will know the phone was rooted/rommed.
The customer service techs are no help as you mention, they just put you through steps from a trouble shooting book. I dred having to call/deal with them again
BWolf56 said:
Know that this will make your phone like it was out of the box (data wise), therefor, you will lose your apps, texts, call logs and such. A backup is suggested before going through with this, which can be done in recovery as well (called nandroid, under backup).
Recovery mode: Hold vol up+home+power button until you see the recovery screen. There will be a factory reset option.
Click to expand...
Click to collapse
Just did the reset from recovery mode as you list above and did not restore or bring back ANY apps but I suspect this is not going to be the solution. Next step will be to try a rom I guess.
s60convert said:
Question, did it ever effect text messages to your phone, both outgoing and incoming? This sounds like what I have concluded also. Thank you for the info. My phone failed yesterday afternoon again and I was going to do a factory reset from recovery but am pondering root/rom to see if that might be a better solution. My only worry is that if the phone also fails with a rom, I will have issues going back to AT&T for help with the boot counter thing (not sure exactly what is called) but they will know the phone was rooted/rommed.
The customer service techs are no help as you mention, they just put you through steps from a trouble shooting book. I dred having to call/deal with them again
Click to expand...
Click to collapse
This morning AT&T Tech Support called me and stated the intermittent inability to receive calls was a random issue with their 4G/LTE network in every area of the country they have it for every 4G/LTE phone they sell, not just the S3 as the Costco kiosk manager had told me. The AT&T Tech Support person further stated this has been a known issue since 1-09-13 and was due to the Lucite (not sure of spelling) switches they use in their 4G/LTE network. Further, AT&T and Lucite engineers had tried several methods to resolve this issue but have not yet finalized what the resolution will be or what date it will be.
She stated the reason she was calling was to tell me a case should not have been opened for my phone because it was a known issue. When I questioned her as to why after my numerous calls to Tech Support no one had informed of this she said it was because all of the Tech Support people I had spoken with were not fully utilizing their resources.
Most unfortunately that call came 15 hours after I got the LG Optimus G. Last night I was so dissapointed with the Optimus in comparison to my S3 I was furious AT&T had put me in such a position. After I got that call this morning I called the Costco kiosk and got a new S3 this afternoon. But now I'll spend at least 4 hours updating to 4.1.1 and reinstalling all my business apps (having to go through all those settings is a PITA), my MS exchange, Google & Yahoo emails, homescreens, ringtones etc.
Supposedly the work around is to disable the 4G/LTE which has been done to my new S3 until AT&T resolves their network issue. I can't comment on your text issue because I don't text that frequently. I did receive texts with my old S3 after the intermittent unable to receive phone calls issue started with it last week and I also received emails on all 3 accounts so I don't believe I had any data issues. I'm uncertain how SMS text relates to 4G/LTE as far as AT&T's network issue.
One of the Tech Support people that I had spoken with 3 times previously because she called me back twice called me again today when I was at the Costco kiosk picking up the new S3 and I told her about the call I had received this morning and asked her to call me back in a couple of hours. When she did she stated she had researched everything available to her and found nothing about this known issue but when she spoke to her manager about it the manager was aware of the issue. So, after speaking with 8-10 different Tech Support people over the course of a week I can only conclude AT&T management deliberately withheld this info from the frontline people you and I would speak with.
At this point I wanted monetary compensation for all the time I'd spent talking to Tech Support, going to Costco twice to get new phones and having to setup new phones. On a sidebar, I spent four hours last night including one hour with LG Tech Support trying to set up my MS Exchange email and was unable to do it because the Optimus G's native MS Exchange mail app does not allow the choice of a TLS certificate so LG Tech Support was trying to set it up through K-9 and wanted me to call back this morning when their specialists would be available. I went to bed last night thinking to myself WTF, an allegedly high end phone that you can't setup MS Exchange email on???
Moneywise the first offer from the Tech Support person was to pay for the month's bill and after talking to her supervisor it was raised to two months. She stated that was the maximum they could offer and to possibly obtain more I needed to speak with Billing. After transferring me to Billing the first individual I spoke with refused to increase the amount which did not make me a happy camper so I demanded to speak with his supervisor who doubled Tech Support's offer. Still, for me, that pales in comparison to the 30 hours or so I've spent/will spend because the frontline Tech Support people could not address the issue. Had I been told last Friday morning what the problem was I could have either deactivated the 4G/LTE in my original S3 or reactivated my 3G Captivate and the problem would have been resolved. Instead, it brought my business to a halt, infuriated some of my clients because they could not reach me and caused me to waste a week trying to have the ability for people to call me. And who knows how many potential clients I may never hear from?
I will say the Billing supervisor I spoke with documented everything I told him and said he intended to rectify how AT&T's Tech Support is handling this known issue. He completely agreed with me that it was absolutely ridiculous for me to have to spend so much time resolving this issue. For the first time in the numerous calls I've had to make to both AT&T Wireless and UVerse over the years I felt I was actually speaking with someone that could and would make a difference.
I'm still PO'ed about having to setup the new S3 when I had one that was setup perfectly for my needs and the 6 hours I wasted yesterday picking up the LG and trying to set up the MS Exchange email.
I have a virtual PBX/efax service I purchased two weeks ago that I pointed at my cellphone and what this debacle did teach me was to point it at my landline as well. I couldn't be sure until I got the AT&T Tech Support call this morning that it wasn't causing the unable to dial through to me problem so I haven't fully set it up yet and that costs money that's been wasted too.
Shame on AT&T for not properly addressing a known issue with their customers. Is it any wonder why they consistently rank last in customer satisfaction surveys?
Ok long phone call with AT&T yesterday afternoon after yet another failure. At first, the guy wanted to put me through the usual diagnostic hoops but I stopped him and told him to just listen to what's been done and what the symptoms are. After a while he stopped me and said he knew exactly what the issue is and will fix it for me right now! Now I do not know what all the terms he threw at me mean but I will list them here for reference. I told him that the phone was reset yesterday morning and zero apps were installed so it had to be a network issue or something wrong with my account. He told me there were "routing number mismatches" and my "LRN" was incorrect. Also said they had me on the wrong network and moved me to the Cingular wireless network. Don't know where I was previously. He also mentioned that the SOA was updated with LRN to the proper SPID. I was told the changes could happen immediately but for sure within 24 hours. No failure yet but this phone has fooled me before and gone for a couple days without failing.
One thing I didn't think was related is that I talk with my wife a lot during her long work commutes and we are constantly loosing the ability to hear one another. There are periods of silence then it pops back in. This literally happens in every call we have and we attributed it to either a tower issue or her car's Bluetooth etc but since the tech made these changes, not one call issue in the three conversations we have had. Also it seems that text messages are received and send instantly unlike they used to sit for a bit before going. Hmmmm.
I hope I do not have to post in the next couple days that the phone has failed again, it is really getting to me.
guys,
it is an ATT issue,
here is a temp solution for a fix:
1) With phone on, take off back cover and press your SIM card so it releases from the spring. It won't come all the way out as it's blocked by the battery. This seems fine - I didn't bother trying to force it out as I didn't want to break anything...
2) Once you see the message that the SIM card is removed, go to the dialer and dial *#2263#
3) You should see a menu with band selections. The current setting is "Automatic". If you switch to "GSM All", you will be EDGE (2G). If you switch to "WCDMA All", you will be on HSPA+ (3G, though AT&T and others call it 4G).
4) Press the SIM card back into place until it clicks. For whatever reason the phone will not recognize it until you reboot. Upon reboot you should see your new setting in effect
please see, post, comment here:
http://forums.att.com/t5/Android-Di...ls-Phone-issue-or-Android/td-p/3270741/page/3

Categories

Resources