yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] MMcCraryNJ:
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.
[Samsung Galaxy Nexus] eman3316@optonline.net:
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?
[Samsung Galaxy Nexus] KWKSLVR:
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.
[Samsung Galaxy Nexus] beekay201:
Food for thought: Apps have not been updated to work 100% with ICS?
[Samsung Galaxy Nexus] eman3316@optonline.net:
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!
[Samsung Galaxy Nexus] KWKSLVR:
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. :p

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.
[Samsung Galaxy Nexus] byrong:
I've thankfully been free of radio issues thus far on my GNex, but I want to thank you for this thread.

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!
[Samsung Galaxy Nexus] eman3316@optonline.net:
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.
[Samsung Galaxy Nexus] KWKSLVR:
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.
[Samsung Galaxy Nexus] KWKSLVR:
Another random thought. During that time period, I also had a BUNCH of random reboots.
[Samsung Galaxy Nexus] charlescom:
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 :)
[Samsung Galaxy Nexus] KWKSLVR:
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. :D
[Samsung Galaxy Nexus] KWKSLVR:
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. :D
[Samsung Galaxy Nexus] SirVilhelm:
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.
[Samsung Galaxy Nexus] KWKSLVR:
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.
[Samsung Galaxy Nexus] Woodk1:
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? :mad: ) - 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.
[Samsung Galaxy Nexus] charlescom:
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
[Samsung Galaxy Nexus] MMcCraryNJ:
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.
[Samsung Galaxy Nexus] Woodk1:
Why do they "pull the class action lawsuit??" Maybe because they were flat out lied to, by a company claiming to have "the most reliable 4G LTE service in the world"? And while no service is guaranteed to have "100% up time", I don't believe you are understanding what is going on - the phone is practically UNUSABLE - it knocks the user off the network, unknown to them - if they are in an accident and go to make a 911 call - GUESS WHAT?!?!??! SOOOOORRRRRRRY....YOUR DEAD!!!! - signed, Verizon Wireless. It makes me regurgitate in my mouth when I read the horror stories of Verizon transferring people to Samsung, saying "something must be wrong with your phone!" - IT'S NOT THE PHONE, IT'S VERIZON!!! And I'm not a customer of Samsung, paying $290 a month - I'M A VERIZON WIRELESS CUSTOMER. THEY should handle this, THEY should be responsible, THEY are the ones doing this with their poorly designed network! And you don't think anything is going to be done about it? Go read the official Verizon boards - search for LTE Lawsuit - it's forming - just wait.

I pay Verizon Wireless $290 a month, for 4 lines, and one of my lines can barely make a phone call, because of their poorly designed network. If it was only the GN this was happening too, I could certainly point at Samsung, BUT IT'S NOT. Go to ITWorld and search for the Razr Maxx article - dude LOVES the phone, but described TO A TEE, this problem - different manufacturer, different components. And if this forum wasn't locking people up until they post 10 times, I would prove to you, it is ALL Verizon's fault, because they EXACT same problem is happening to the Motorolla Razr Maxx.

And I switched her phone to 3G last night (CDMA)? GUESS, WHAT, NO disconnects from the system - now we are stuck with a slow phone, when we were told it would be 4G and lightening fast, on THE MOST RELIABLE LTE NETWORK.

What a joke!
[Samsung Galaxy Nexus] adrynalyne:
It probably is the most reliable LTE network. The problem is, reliability wise, none of them are. So now its just in reference to how much Verizon sucks vs. everyone else.

Currently, THEY ALL SUCK.

http://forums.att.com/t5/Network-Co...southern-california-since-friday/td-p/3048621

http://gigaom.com/mobile/verizons-lte-outage-problems-just-wont-stop/

MetroPCS has had LTE issues.

Cricket probably does too.

The early bird gets the worm.

Go ahead with a class action lawsuit. It will get nowhere, and even if Verizon settled, you will get a 5 dollar off voucher for your next phone. And LTE WILL STILL SUCK.

I make this prediction. Until we get to 2nd gen or later LTE radios in devices (and move to LTE-A), LTE is going to suck ass and be a gimmick to use on a short term basis for many people. So I would say nobody will see true LTE reliability at LEAST until some time in the next year or two.

Think about it. With 2nd gen radios, there will be one radio to rule them all. There will not be separate CDMA and LTE radios. This will likely help with battery issues TREMENDOUSLY. I wouldn't doubt switching from 3g to LTE would be quicker as well.

Once LTE-A rolls out, that in itself will help in many ways. Battery life should be better because LTE is used for everything and not different networks for voice and data.

Face it folks. We are early adopters and are seeing the growing pains. If you cannot live with it, switch to 3G or find another non-LTE carrier.
[Samsung Galaxy Nexus] Woodk1:
I think the issue here is, Verizon Wireless is treating this issue and operating like a "fly by night" business - WHAM, BAM, THANK YOU MAAM business.

They are offering no solutions, not even admitting that there is a problem - IT'S DISHONEST BUSINESS. You KNOW they know there is a problem and the only inkling we get, is from honest techs that are probably risking their jobs by admitting it. But all we are getting from "the front people" at Verizon is "Hmm..that's strange, we aren't getting any reports on that" which is a flat out lie and dishonest business. THIS is the company I'm married to for the next 2 years???? GREAT, JUST GREAT.

Here's a novel idea Verzion - issue A STATEMENT - Issue a statement on the Galaxy Nexus. Give us a "we are working on this and have even moved techs from other departments to this as a priority and will issue a fix at the end of March.

That, or if you insist on still transferring people to Samsung, or pointing fingers at Google, allow YOUR CUSTOMER to switch to another model phone, instead of lying to them and promoting a failed network.
[Samsung Galaxy Nexus] adrynalyne:
Really though, what is an HONEST business? A bankrupt one? No company will be honest with its customers and say, "Our service is unreliable and flaky."

Verizon has said they have growing pains with their LTE network. Past that, they will likely not say much else.

A lot of what you are speaking about deals with CSRs. They likely are not lying when they say, "we have no reports about that." They can only see what their magical box with a keyboard connected shows them. They have no access to Network Operations.
[Samsung Galaxy Nexus] Woodk1:
Replacing my phone with another model, because these don't work and I bought it based on their "reliable LTE network" - that's gonna bankrupt Verizonwireless? THEY are the ones that won't allow switching to another model, simply because 14 days have gone by and "AHAHAHA!!...WE GOTCHA!..NAH, NAH, NAH" mentality. They could easily take this phone back, switch her to an iphone, and send the phone back to Samsung who would refund Verzion.

I AM A VERIZON WIRELESS CUSTOMER - I PAY $290 A MONTH and they won't take care of this?

And you know what the kicker is? The 14 day clock started ticking, the day I called in to have the first one replaced - THEY STARTED IT THEN, NOT WHEN I SIGNED FOR THE PHONE!!!!

"WE GOTCHA!..AHAHAHAHA - signed, Verizonwireless."

Read the threads - the thousands of people having this issue that have called in for help - so that's not being logged by Verzion and presented on the CSR screen? THAT'S VERIZON'S INTERNAL PROBLEM, NOT OURS!

I hope they get sued, I really, really do. Google "Verizon Wireless Sued" - that's dishonest, BAD BUSINESS, WHICH BY THE WAY???..

LEADS TO BANKRUPTCY.
[Samsung Galaxy Nexus] ATnTdude:
Agreed in principle, LTE hand-offs are unreliable. CS fallback is probably a huge issue, since it is a tack-on to the spec, which is why different carriers handle it differently. Verizon runs two radios simultaneously. AT&T will drop you to HSPA for the duration of your call. Fortunately, we won't have to wait for LTE-A, or even new phones, to take advantage of voice over LTE. VoLTE is fully compatible with the network Verizon has deployed and the handsets we currently own (some older handsets may need a firmware update though, anything from 2H2012 is already good according to VZ). It's just a matter of working out the kinks in IMS before deployment. People have far higher standards for voice than they do data and because of that it's taking time.

2nd Gen radios will, however, have much better power consumption due to a combination of optimizations and a die shrink from current 45nm chips to 28nm. Still, at this stage of the game, UMTS was much worse on batteries than LTE is.
[Samsung Galaxy Nexus] KWKSLVR:
Everybody needs to take a deep breath. Of course it's Verizon's fault. Who do you guys think are behind the radios? Verizon's LTE network is proprietary to Verizon. It's not Google's fault. It's not Samsung's fault. If your phone is truly "unusable" then send it back for a warranty replacement. I find that statement over kill unless it never connects to the network. I find mine very usable. I use it every day for work, for hours without problems. I streamed internet radio for over 4 hours today without a hiccup as well.

There is a line between discontent and mass hysteria. ;)
[Samsung Galaxy Nexus] charlescom:
If you truly have the time, please read my extensive post on page 2.

It is actually not a cake walk to get a warranty replacement.....

They literally tell you to wait....
[Samsung Galaxy Nexus] adrynalyne:
In which my response would be, ask for a manager and keep moving up the ladder of proverbial crap until something gets done about it. They cannot refuse warranty service if it is a warranty covered issue and you have not voided it.
[Samsung Galaxy Nexus] SnrSuave:
Not just a problem with 4G! Where I work I am not allowed to have my phone, so I keep it in my car and turned off. Earlier today, I got back in the car and left, turning my phone on. 20 minutes later I noticed my phone has not had a signal at all since turning it back on. It said "No Service". I have it set to CDMA only in the network settings...
[Samsung Galaxy Nexus] charlescom:
Oh, I figured that out long time ago. I pretty much talked to a local branch manager so as escalated customer service rep and network service rep including Tech Coordinator II, 4G LTE, Global, Network Extender, Voice and Data Technical Support and his manager as well.

Hahahahahahaha...you have no possible idea how many people i talked over the phone. Manager > manager of the manager > manager of the manager > boss sounding guy..

I've pretty much went up and down the ladder of VZW customer support for 4 months now....

Like I was saying, the answer right now is Wait....

I haven't screamed at them or sounded frustrated yet. Or threatened them with horror stories to get a replacement yet...Maybe that is what I should do to get a replacement device???

LOL
[Samsung Galaxy Nexus] adrynalyne:
I think the times for being nice and calm are over.

Go for the throat and don't look back.
[Samsung Galaxy Nexus] charlescom:
Yeah, when it comes down to it I'll take your awesome advice :D