Friday, June 8, 2012

Possible cause/solution?

See posts 732 - 735 at http://code.google.com/p/android/issues/detail?id=24019

It was stated that a person who had the issue at home did not have the issue when they turned their phone on while at their office (about 14 miles away) - even after returning home.  The poster asks is there could be an authentication issue with specific equipment/towers & not with others since the issue does not seem to occur at the house if the phone was turned on while at the office...

I will ask him to test this scenario out to see if the issue returns if the GNex is turned on at the house and, then, if he can replicate the "solution" by turning the phone on near his office.

I am going to look for software that might let us identify specific towers (llama maybe) or equipment on those towers that might be causing the issue(s).

Has anyone had this issue in some locations/tower areas but not in others?

Updates to follow ...

7 comments:

  1. Yes, I've never had the problem happen when at my office in downtown Greenville, SC but it happens at my house frequently. That's what makes me think it's something hardware or configuration-related to the towers and the device.

    Any progress with Samsung?

    ReplyDelete
  2. Ben:

    I am delaying shipping my device to Samsung until I hear back from the engineer who has my trouble ticket at Verizon as I'm trying to exhaust one company at a time.

    So you never have it when at your office? Can you use Open Signal to get a list of the towers at each location-home v office? Having that list for Verizon may help. Heck, publish the list here! I don't have a location where my phone works... If I did I'd have a table with a list of towers where I never had the issue one one column, and a column with a list of towers where I did have the problem.

    Once you have that, I'd use NDT Mobile Client to see if network "stuff" differed between the two locations.

    That make any sense? I'm happy to provide links to those to apps, but they are in the Play store. I'm also willing to help find people to analyze all that data-such as Verizon, Samsung, & Google employees... :)

    ReplyDelete
  3. Downloaded Open Signal and it looks like I'm connected to one tower at work:
    Type: eHRPD - 3.75G
    Strength: 19asu, -75dBm
    CDMA SSID: 4419
    CDMA NID: 103
    CDMA SID: 139

    By the way, Verizon offered me the Rezound today. Not going to take it, but at least they offered something. May try to see if they will offer me the S3. I'm not convinced they can fix this issue.

    ReplyDelete
    Replies
    1. The Rezound is nice. To be honest, I'm weary of Samsung devices now. The Captivate (Galaxy S on AT&T) had a horrible GPS that, for all intents & purposes, never worked on my phone. Now the GNexus's "issue." HTC's new phones look real good to me at this point...

      Thank you for the work data. What about "home?" Any different?

      Delete
  4. Ted: Someone at code.google...24019 just stated Verizon agreed to replace a Galaxy Nexus with a Samsung Galaxy III-likely a lower RAM version ... Here is your chance. If you get one, do let us know how it works-especially call quality and GPS use! :)

    ReplyDelete
  5. I think any future "Google" product will not be an option due to their lack of communication and support for "their" device...

    ReplyDelete