LTE Gnex Radio Problems? Try This - Samsung Galaxy Nexus

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

Related

GOOD READ - Text Message From The FUTURE problem

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.

Any Idea how the GPS will be?

i havent gone threw every review but any of u guys catch anything in any review?
the epic by far was the best phone ive used but the GPS was down right awful and sprint nor samsung did anything to fix it
XDA fixed it enough to keep me happy. I think people are blowing this gps thing way out of proportion. "If it doesn't work perfectly or, at least as good as other phones then it must be the most awful thing ever!".
Silent25r said:
XDA fixed it enough to keep me happy. I think people are blowing this gps thing way out of proportion. "If it doesn't work perfectly or, at least as good as other phones then it must be the most awful thing ever!".
Click to expand...
Click to collapse
was never blown out of proportion.....my girls epic who is stock can never get a lock
mine who was rooted would get signal but never better then 40m lock and would lose signal constantly.....try taking an 9 hour drive with it on and see how many times ur signal is lost
imtjnotu said:
was never blown out of proportion.....my girls epic who is stock can never get a lock
mine who was rooted would get signal but never better then 40m lock and would lose signal constantly.....try taking an 9 hour drive with it on and see how many times ur signal is lost
Click to expand...
Click to collapse
I certainly remember that a lot of people had trouble, but I never did. Mine always locked perfectly and quickly and never gave me trouble on drives short and long.
imtjnotu said:
was never blown out of proportion.....my girls epic who is stock can never get a lock
mine who was rooted would get signal but never better then 40m lock and would lose signal constantly.....try taking an 9 hour drive with it on and see how many times ur signal is lost
Click to expand...
Click to collapse
I never understood the gps deal. It seemed so sporadic. Mine always worked and I am stock. I used it last weekend on EH17 to drive 5 hours to saint louis and it was perfect the entire way there and back. Didn't cut out once. But you see some people worth working gps and others without it.
Sent from my SPH-D700 using xda premium
I have to agree on the gps sucking. On any drive over an hour I could expect to loose lock. I'd imagine if we looked in some of the other GSII forums we might get a clue.
the only thing i ever loved more about my evo then the epic was the gps....htc never gave me gps issues ever
when i had the bionic or droid x they both locked on quick
Backing up the GPS being just short of useless. Remember, just because YOU haven't experienced the problem doesn't prove there isn't one. On Eclair I had very little trouble, but on FroYo I would constantly lose signal mid-trip, having to frequently turn it off and back on to re-lock and hope I wouldn't lose it right when I was in the middle of complex turns or had missed a turn and needed re-routing. In the Gingerbread leaks it turned to completely useless, locking up 100% after as little as 10 seconds of use, requiring a full restart of the phone to be useful again.
So yes, the Epic's biggest flaw was its next-to-useless GPS, hands down. That said, most reviews of the entire Galaxy S line agreed the GPS was bad on all versions. So far I've heard nothing of the sort about the Galaxy S II phones in Europe which suggests the entire line will be similar, including our new Epic 4G Touches.
imtjnotu said:
was never blown out of proportion.....my girls epic who is stock can never get a lock
mine who was rooted would get signal but never better then 40m lock and would lose signal constantly.....try taking an 9 hour drive with it on and see how many times ur signal is lost
Click to expand...
Click to collapse
If you couldn't fix it then that wasn't the norm. I would have returned it to Sprint and got a different one within the first 30 days.
9 hour drives? No problem. Longest I've been on was 6 but the GPS didn't have any problems. The battery on the other hand...
got mine yesterday, used GPS with google nav and telenav. drove for about an hour in farm country Ohio. GPS took a few seconds longer to lock than my EVo but once locked didn't drop signal. Still a little early to tell but no obvious problems yet.
TurboFool said:
Backing up the GPS being just short of useless. Remember, just because YOU haven't experienced the problem doesn't prove there isn't one. On Eclair I had very little trouble, but on FroYo I would constantly lose signal mid-trip, having to frequently turn it off and back on to re-lock and hope I wouldn't lose it right when I was in the middle of complex turns or had missed a turn and needed re-routing. In the Gingerbread leaks it turned to completely useless, locking up 100% after as little as 10 seconds of use, requiring a full restart of the phone to be useful again.
So yes, the Epic's biggest flaw was its next-to-useless GPS, hands down. That said, most reviews of the entire Galaxy S line agreed the GPS was bad on all versions. So far I've heard nothing of the sort about the Galaxy S II phones in Europe which suggests the entire line will be similar, including our new Epic 4G Touches.
Click to expand...
Click to collapse
Since I don't know who you were responding to I will assume it was me. You know that goes both ways right. Just because YOU have experienced the problem doesn't prove there is one. I have used every official build and every gingerbread leak except EE03 and I have never had a single problem. I use GPS frequently. I have never had a lockup. I have always had an instant lock. And I have always been able to get within 10 meters with the average being 3 meters. However, I never said there wasn't a problem. I just said I never understood the issue as to why it worked for some and not others. You would think that it would be global if the hardware is identical. Makes me wonder if it has anything to do with location in respect to the satellites. Never tried to dig into it because fortunately I didn't have the issue. But I do hope that the touch is without issues because not having gps would be a deal breaker for me.
Sent from my SPH-D700 using xda premium
crawrj said:
Since I don't know who you were responding to I will assume it was me. You know that goes both ways right. Just because YOU have experienced the problem doesn't prove there is one. I have used every official build and every gingerbread leak except EE03 and I have never had a single problem. I use GPS frequently. I have never had a lockup. I have always had an instant lock. And I have always been able to get within 10 meters with the average being 3 meters. However, I never said there wasn't a problem. I just said I never understood the issue as to why it worked for some and not others. You would think that it would be global if the hardware is identical. Makes me wonder if it has anything to do with location in respect to the satellites. Never tried to dig into it because fortunately I didn't have the issue. But I do hope that the touch is without issues because not having gps would be a deal breaker for me.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Just because he experienced the problem means that a problem exists. Whether it's a wide spread problem or a unique incident, the problem still exists. On the Epic forums people are constantly complaining about GPS issues. There are few fortunate ones like you who haven't had the same issues. I didn't have GPS issues for a while until my job had me drive long distances.
cachorropedorro said:
Just because he experienced the problem means that a problem exists. Whether it's a wide spread problem or a unique incident, the problem still exists. On the Epic forums people are constantly complaining about GPS issues. There are few fortunate ones like you who haven't had the same issues. I didn't have GPS issues for a while until my job had me drive long distances.
Click to expand...
Click to collapse
So if you brick your phone because of something you did is the phone bad. Is there a flaw in the phone? No. And again, I never said there wasn't a problem. Actually I said that there was a problem for some and not for others. The only point I was making is that I didn't understand why it worked for some and not others. I wish we could have found the root cause.
Generally speaking GPS on the galaxy S line sucked world wide. Generally speaking it appears that samsung fix this in the galaxy s II.
This is based on reading numerous reviews on both; though it is always possible they messed up on the epic touch as it is slightly different and has wimax; I'm expecting it to work like a charm.
-
I do wonder how many folks who tested gps on the galaxy s remember to ignore wifi triangulation when voicing a comment.
Forgot about this thread and started another a bit further down. I managed to sneak GPS status onto our demo phone yesterday and it locked to 9/10 sats in less than 2 seconds from inside. Accuracy was only at 30m when I cut it off, but it was indoors in a spot where my epic cannot lock at all. Pretty sure it's fixed.
Sent from my SPH-D700 using XDA App
crawrj said:
The only point I was making is that I didn't understand why it worked for some and not others. I wish we could have found the root cause.
Click to expand...
Click to collapse
I did spend a fair amount of time investigating the GPS issues on EC05. There are at least two problems: (i) GpsOne Xtra data that fails to download and update, eventually resulting in stale ephemeris and inability to get timely locks, and (ii) a RIL synchronization bug that results in the GPS crashing with 5% probability on every exit/switch of a GPS utilizing app.
The latter of those two problem is definitely confirmed and affects every EC05 Epic. However, if you only use Navigation once a day, you'll run into that bug an average once a month and might not even notice it. But it is possible to reliably reproduce.
The former of the two problems I never fully understood. The GPS should work as long as you reboot once a week, but we know folks whose phones chronically couldn't download new Xtra data on reboot, likely becuase it was attempting to do so "too quickly" after establishing a network connection. Forcing an Xtra download through GPS Test, GPS Aids, or with a patched framework resolved the issue for most of those folks. The remaining issue is that the ephemeris would still go stale very quickly (hours) on some phones, and an EFS/NVRAM clear appears to help that.
Part of the issue is that the "brokenness" of the GPS is somewhat subjective. It's entirey possible for the GPS to absolutely not be able to get an Xtra-assisted lock, but using almanac data still get one in 30-60s in a vehicle. For some folks, that might be "good enough" and wouldn't think there's much of a problem.
cachorropedorro said:
Just because he experienced the problem means that a problem exists. Whether it's a wide spread problem or a unique incident, the problem still exists. On the Epic forums people are constantly complaining about GPS issues. There are few fortunate ones like you who haven't had the same issues. I didn't have GPS issues for a while until my job had me drive long distances.
Click to expand...
Click to collapse
I think the opposite of what your saying is true. This problem isn't as wide spread as it seems. The few who have this problem are very loud about it and complain about it over the forums. Though I seriously doubt that they are the majority.
If fixing your gps doesn't work then you can always set it back to stock and take it in for repair. If they can't repair and you don't have insurance then you can pay a small fee for a epic with a working gps. I doubt anyone is forcing people to live with a phone that the gps doesn't work on.
Considering that it has a dedicated GPS chip "SiRFstarIV GSD4t GPS" I doubt that we are going to see the same issues.
The integrated GPS on the SoC stinks, and samsung knows that. Using the SiRFstarIV will solve 99% of peoples GPS problems.
engadget claims it is solid. fwiw. http://www.engadget.com/2011/09/15/samsung-epic-4g-touch-review/
Our calls were absolutely solid. The phone's reception is on par with the best handsets around, and we never suffered from dropped calls or degraded quality. Our calls came in absolutely clear, and we think the speakers go to 11 because we had to actually turn down the volume to comfortably hear the other end of the line. The same thing could be said about the loudspeaker for calls and music, which both came out loud and clear without needing to strain our ears or feeling like we needed to break out the headphones. However, the sound seemed a bit limited when watching a full-length blockbuster movie, though we believe this had to do with the quality of the movie itself and not the phone.Last but not least, we double-checked the GPS to make sure it wouldn't have similar concerns to the Galaxy S series, and weren' t disappointed. In several locations -- including a basement next to a window -- the GPS pulled up our location in less than ten seconds. Needless to say, this is definitely a sound improvement, one we imagine had special attention given to it throughout the course of the phone's development.
Click to expand...
Click to collapse

2nd Nexus - reception still sucks

I burned through my extended battery in 2 1/2 hours today, and 4g drops were ridiculous. I finally called tech support, and they told me to exchange for a new one. So, I got my second one, still getting 4g drops. My wifes Thunderbolt (my old phone) holds 4g full strenght in my house all day. I am highly disappointed in this phone. If Rezound gets s-off by January 15, I may be switching. It sucks, because I really like this phone other than the signal.
Also, when I talked to tech support, she said there is an update coming in March, which I also read elsewhere on these forums. Why would they wait until March, seems kind of wierd.
I always read about people complaining about this phone. I have this to say to you:
If you don't like it get another phone.
I'm sure there are plenty or Rezounds out there for you.
Haven't you guys read that the LTE network has been on the fritz?
Sent from my Sensation using Tapatalk
Cool story bro.
Sounds like an issue with the LTE tower near you. My reception has been great. I'm at 14 hours and I still have 19% left...barely had it 24 hours. If you have multiple phones wigging out, there are two possibilities:
1) The User
2) The Network
Let me guess, you restored all of your titanium backups and/or restored from Google Servers?
Here's another thought. Did you get a new 4G Sim card or did they just pop the old one into the new phone? Ta-Da.
Omg so many Verizon-noobs complaining, of course it has bad battery, it's LTE...
By the way i dont believe you in going from 100% to 0% in 2 and a half hours with two different batteries, unless you are dumb and has screen on 100% etc. If, however, you are serious, call Verizon or something.
Actually, half you guys are arrogant assholes. No, I installed everything fresh, my f*%$ing Titanium files wouldn't transfer from old Nexus back to my computer without hanging up. Yes, I have a high-end computer with no issues, yes the samsung drivers are installed, MTP sucks. Yes, I owned a TB since day one and never had 4g reception issues in my house. No, there are not tower issues, I know how to troubleshoot. I get 10mbs down on both this phone and the TB, except the TB doesn't lose its 4g signal. And yes, I got a new SIM card with my new Nexus.
Plus, I work downtown on the 33rd floor, and my TB held a 4g signal most anywhere in my office, even in the ****ter in the middle of the floor. My Nexus, burned through the battery twice in 8 hours and was in 3g half the day. But, I guess it's user error. It's clear as day there are issues with reception, it's just can you tolerate it.
Baguett said:
Omg so many Verizon-noobs complaining, of course it has bad battery, it's LTE...
By the way i dont believe you in going from 100% to 0% in 2 and a half hours with two different batteries, unless you are dumb and has screen on 100% etc. If, however, you are serious, call Verizon or something.
Click to expand...
Click to collapse
No one said I burned through 2 batteries, I said I burned through an extended battery in 2 1/2 hours, screen is on auto, and you are an arrogant prick also. Do you assume everyone is dumb because they have issues with their phone? Also, I have been on 4g since day 1 with the Thunderbolt, I know where f##$ I get 4g and where I don't.
I had a little over 12hrs 36min with minimal usage in an area with known bad signal and had 21% left today, go figure i guess. Granted I only used my phone during my breaks and lunch. Still good for being connected to LTE all day imho. Im happy with the results I've had and I am totally realistic with battery life with an LTE phone, so much so i bought the extra battery+charger. If i happen to be in an area when I know I won't have the option to charge my phone, i swap the battery and have near full charge. It's awesome.
Software issue. Go cry to VZW please.
Yaaaaawn. User err... ogance.
Crazy world, ay?
You guys really are being dicks.
First off, it's clearly not the distance from the 4G tower because the thunderbolt is working just fine.
Second... the guy posts here saying he's had trouble with his second device. And being that an older device is working just fine he's looking for some answers. He's not trying to craptalk the device, but looking to see if anyone else has had the same trouble. That way in can gauge if he should attempt to get a third replacement, or swap out the phone for another device... or maybe someone figured out an issue with a specific ROM or discovered a radio that fixed his issue.
Instead he gets you Trollolols that are being complete dorks by telling him to switch to rezound or cry to VZW.
If you have nothing substantial or beneficial to say to his predicament, why is it so hard to just to stfu and move along?
Take that crap to androidforums.com where it belongs.
To the OP... have you attempted a different radio? Here's an article on it.
http://androidcommunity.com/leaked-...alaxy-nexus-improve-signal-slightly-20111221/
And you can try here to download some.
http://rootzwiki.com/topic/12864-ra...ge__hl__+galaxy++nexus++radios__fromsearch__1
Gall0ws, thanks for the links, and support. I actually flashed the new radios on my last nexus, didn't get much of an improvement. The TB is between 75 - 85 dbm in my house, and the Nexus (including the new one), is typically between 95 - 115. I don't even care about the reading, because when I have 4g, it's fast. It's the drop outs to 3g that suck. Also, going to monitor this device for a few days before I flash the new radios, so I can really say if they made a difference. This just sucks, I was really hoping for an improvement over the Tbolt.
kwkslvr, I will take the screenshot, then punch it in your face. Do you think I am exaggerrating? Do you think I felt like taking all the **** off my phone, reflash everything back to stock and relock it, then waste an hour at Verizon, then reroot and put all my **** back on, I have no time for that. My thunderbolt is the original day one issue by the way, I don't exchange things for no reason. I don't use Titanium for anything other than restoring certain apps that I have that are no longer in market, no data.
fillyo said:
I burned through my extended battery in 2 1/2 hours today, and 4g drops were ridiculous. I finally called tech support, and they told me to exchange for a new one. So, I got my second one, still getting 4g drops. My wifes Thunderbolt (my old phone) holds 4g full strenght in my house all day. I am highly disappointed in this phone. If Rezound gets s-off by January 15, I may be switching. It sucks, because I really like this phone other than the signal.
Also, when I talked to tech support, she said there is an update coming in March, which I also read elsewhere on these forums. Why would they wait until March, seems kind of wierd.
Click to expand...
Click to collapse
I haven't had problems with my GN, but I did find these two articles interesting regarding the whole 4G problems w/ some GN owners. I'm sure it isn't any condolence but...
1.http://www.droid-life.com/2011/12/2...accurate-than-others-there-may-be-no-problem/
2.http://www.droid-life.com/2011/12/2...gnal-indicator-to-better-match-other-devices/
What I find most disturbing is VZW "fix" for this is to just change/ fake what the signal actually is at and they aren't stating if the GN is correct or incorrect?!?! lol
By the way, when I got approval from Tech to exchange my device, she said there was an update coming in March in regards to the signal display issues, seems odd they would wait til March for an update. Just repeating what she said, nothing more.
Here is a speedtest with my signal strength, speeds are fine, and I am reading 101 dbm.
jcoddinc83 said:
I haven't had problems with my GN, but I did find these two articles interesting regarding the whole 4G problems w/ some GN owners. I'm sure it isn't any condolence but...
1.http://www.droid-life.com/2011/12/2...accurate-than-others-there-may-be-no-problem/
2.http://www.droid-life.com/2011/12/2...gnal-indicator-to-better-match-other-devices/
What I find most disturbing is VZW "fix" for this is to just change/ fake what the signal actually is at and they aren't stating if the GN is correct or incorrect?!?! lol
Click to expand...
Click to collapse
The fix might not be simply falsifying any data but perhaps correcting an issue where the software is improperly calculating it. Which of course could lead to a lot of other issues such as excessive power drain because the phone thinks it needs to increase the power to the antenna instead of leaving it alone or reducing it.
For anyone having an issue with their signal, just keep a close eye on the radio threads. As soon as a new one gets leaked, they'll post it up and you can try it out.
And it can take a while, for example, my thunderbolt didn't have a good radio until on that was leaked Fall of this year. There is no rhyme or reason to it. some radios work better for some and not so good for others.
Obviously, if the phone isn't usable for his area, march is a long time to wait for an official update for verizon. But typically this stuff gets leaked out before an official push anyway.
Anywho, JC. Thanks for the links.
No major problems here
I've been running my phone for 2 days here without any significant battery issues; at least none more that I expected based on battery size and playing time. I've ordered the extended battery for insurance, but I fully expect that to do what I need. My only complaint at this point is signal strength vs. other VZ phones I've seen sitting right next to me. I have being disappointed here, am I alone?
Feel free to take a swing, but I don't think it'll fix your GN. I'll be awaiting the screen shot.
The AnandTech article is completely correct. I experienced a similar thing with my iPhone back in the day. This is a GOOGLE phone with as little Verizon interference as possible. Carriers want their users to think that they have GREAT reception everywhere they go. Those numbers are typically fudged, it's nothing new, I promise. As far as 4G drop off to 3G goes, most LTE phones suffer from this. Your T-Bolt is an older device. I'm sure you can't possibly have forgotten the number of LTE-related issues that device was plagued with early on. I remember a buddy of mine returning his because as cool as 4G was, 10% battery drain an hour on LTE while sleeping was just plain unacceptable. The Bionic has had issues. Most likely ALL VZW LTE phones are going to initially have issues the way that LTE and CDMA are basically taped together with very non-sticky painters tape.
I've seen connectivity issues with my MiFi related to specific locations that I'm in (I'm a heavy traveler with work). Any "fix" will be purely for display purposes. The day that release hits will be the day I'll be on XDA trying to research how block the update notification. The GN is currently displaying true and accurate reception strength and I'm sure it's driving Verizon up the friggin wall.
Ok, I'll stop giving everyone a hard time. But really, if the device sucks in your area, I'd return it and wait for a fix. In all seriousness, as you now confirmed from flashing modems, no modem is gonna make THAT big of a difference overall. Constructively, I'd wipe the device, log in with my Google Account, install zero apps, and see what it does. If my battery life sucked, I'd take it to the Verizon store and ask for a new battery. If that battery sucked (like draining dead 3 hours in sleep mode) I'd take the device back and exchange it.
It's not that I'm calling you a liar, it's that typically that kind of behavior is faulty hardware. Having it twice in a row is abnormal. In all fairness, my first iPhone had a bad battery and died in 2 hours (permanently). My second iPhone would overheat and lock up. My third iPhone was "fine" other than the fact that it was an iPhone.
Did it leave a bad taste in my mouth? Yeah, sure, but I still accept the fact that it was a weird chain of events and that the vast majority are perfectly fine. What I'm saying, nicely, is that both your first and your second device are not normal. It's not Google's, Verizon's or Samsung's fault...well, Samsung's for putting together a few bad units, but you know what I mean.
Haven't said 2nd device has bad battery life, just 4g drops. Hoping battery life will be better on this one.
Sent from my HTC Flyer P510e using XDA App
I definitely think something is wrong with battery life. I bought the extended battery and my phone is at 20% in 4 hours with screen brightness at zero and light texting and a lil fb. I feel like the regular battery lasted longer than the extended one I might test that next.
Sent from my Galaxy Nexus using XDA App

Signal problems, what are my options?

As many, many other users of the galaxy nexus have reported, I am having some miserable signal problems. Obviously, CDMA nexus here.
I wish the issue was only that the signal on my phone is bad, but unfortunately it extends beyond that: my entire signal is lost at times. Usually it's intermittent and will happen 4 or 5 times a day for only 30 seconds at most at a time, but sometime (Usually late at night), it will lose its signal for even an hour or two, and I'll watch the battery plummet from as high as 54% to 0 as it searches for a signal the whole time.
I realize this is nothing new for some, but I almost feel like the problem went away for the whole world except for me, due to the low volume of threads related to the issue at all on the boards here. At least, recent ones.
What are my options? I don't really like the idea of trading in my nexus for a refurbished phone. Is 4.03 supposed to solve this problem? I had also read that rooting and flashing radios doesn't make much of a difference. To those of you with the CDMA nexus, what have you done to alleviate this problem? Or are you waiting patiently for an update?
Thank you in advance.
If bought new then return as faulty. Easiest solution.
sent from my Nexus Prime using XDA app
Daramue said:
I realize this is nothing new for some, but I almost feel like the problem went away for the whole world except for me, due to the low volume of threads related to the issue at all on the boards here. At least, recent ones.
Click to expand...
Click to collapse
The problem didn't go away. Most people had to make the decision to either live with it or trade it in on a RAZR or Rezound.
Daramue said:
What are my options?
Click to expand...
Click to collapse
You could:
1. Trade it in for another GNex, on the "hopes" that yours is defective.
2. Trade it in for something else.
3. Live with it & wait it out on the hopes that someday Verizon will ship updated radios that will help. Current rumors say that could still be a couple of months away...
I am on the option 3 plan.
The leaked 4.0.3 radios have had limited & mixed results. For those who they do help, they don't seem to do a whole lot. There are a couple of people who had really good luck. Pretty much the same story for those of us who got Hardware version 10 phones - Haven't noticed any appreciable difference between it and the 9 I got on opening day.
Good luck!
strongergravity, thank you, that was extremely helpful; I was curious to how my fellow Nexus bretheren were dealing with the issue.
If a potential update can fix the radio, then I too will stick with number 3 as you have. Call me a masochist, but this thing is just too nice to part with.
Thank you very much for the detailed response.
Daramue said:
strongergravity, thank you, that was extremely helpful; I was curious to how my fellow Nexus bretheren were dealing with the issue.
If a potential update can fix the radio, then I too will stick with number 3 as you have. Call me a masochist, but this thing is just too nice to part with.
Thank you very much for the detailed response.
Click to expand...
Click to collapse
I just saw your thread right after I created the exact same one today! I was just wondering what you ended up doing. No one has answered definitively as to whether or not this is happening on all phones. If an exchange will fix it, I would gladly go tomorrow. I know most phones are having trouble with the 3g/4g handoff but that is not the same issue we are having. What do you think!?
Mike
Same problems I've experienced. I'm on my second gnex, same issues.
Also I pulled speed tests next to other Verizon 4g phones (razor,rezound,TB) they all had significantly higher speeds than mine . I did multiple tests around our site, they had at least twice the speed as mine.
The razr pulled three times my speed most the time. 30+mb/s vs 10
The thunderbolt was around twice as fast downloads but uploads were even.
And the rezound was double on both uploads and downloads
I used the speed test app and speakeasy online.
Sent from my Galaxy Nexus using Tapatalk
Another comparison I did was turning on airplane mode on and off on all phones simultaneously. And switching 3g only on/off. To see which phones would latch on to 4g first.
Again the gnex was the slowest.
I really wish we received an update to fix this I love this phone!
Sent from my Galaxy Nexus using Tapatalk
I posted this earlier on another thread hoping it will get more views here.
So, I'm having the same exact problems but i did a log cat to see what might be culprit.
I have narrowed it down to this:
02-08 11:21:51.912 E/IMSFW (415): IIL: Disconnected from '7467' socket
still have no idea what can cause it yet.
also if you switch to 3g it seems it doesn't happen so maybe its a sim problem on verizons lte network end?
11:22:40.029 E/IMSFW (415): ImsSMSInterface: Registration failed, go for retrying if isim nounce present
that's what i found so if anyone can clarify and maybe see if it is really on Verizons end as this is the 4th phone that has had this problem
I will be going to verizon tomorrow to "try" and get a new 4g sim card and see if that helps somewhat.
that1techguy said:
I posted this earlier on another thread hoping it will get more views here.
So, I'm having the same exact problems but i did a log cat to see what might be culprit.
I have narrowed it down to this:
02-08 11:21:51.912 E/IMSFW (415): IIL: Disconnected from '7467' socket
still have no idea what can cause it yet.
also if you switch to 3g it seems it doesn't happen so maybe its a sim problem on verizons lte network end?
11:22:40.029 E/IMSFW (415): ImsSMSInterface: Registration failed, go for retrying if isim nounce present
that's what i found so if anyone can clarify and maybe see if it is really on Verizons end as this is the 4th phone that has had this problem
I will be going to verizon tomorrow to "try" and get a new 4g sim card and see if that helps somewhat.
Click to expand...
Click to collapse
I just went to the store and swapped out my 4g sim card... I dropped two calls on the way home from the store so I'm not sure it helped at all. Hopefully it didn't make it worse though!
I also checked my speeds and service against some other phones in the store and the Droid Razr destroyed my nexus and some other stock nexus that were there usually 12mpbs vs my 8 and 1mbps upload vs their 3.
Well I got my issues fixed today I was on tech support for an hour and he suggested to go to a store and get the sim card replaced. And that solved all my issues
Another problem I had was when using the headset for calling the person on the other line would here themselves. This has also gone away, I am so relieved I love this phone and did not want to abandone it.
Well, I did a bit of a test.
I kept my phone on 3g the whole day: Signal did not drop even for a single MOMENT in the entire day. Sure, there are times where it was bad, but my connection never entirely dropped. This leads me to believe that the problem lies with transitioning between 3g and 4g, or perhaps is just entirely related to 4g.
With the LTE network, I will have anywhere between 3% - 50% time with "no signal." It's extremely annoying and I'll always watch as my battery tanks extremely fast.
Maybe it's worth replacing the SIM card or at least, pulling it and putting it back in. Posting this here for others that are troubleshooting this same problem. I'll report back.

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.

Categories

Resources