Galaxy Nexus Watering Hole

Last Updated:

  1. BabyBlues

    BabyBlues Trouble Just Finds Me! VIP Member

    I'd be interested to know how many time "hate" and "Verizon" were used in the same sentence by Han.

    Fixed it.

    EarlyMon and OfTheDamned like this.
  2. RazorSharp

    RazorSharp Well-Known Member

    I mean, my concern is that if I send mine back and get another, it'd be even worse! Then what do I do? Go back and say "uh, actually, can I get the first one back"?
    I'd put a large bet on the winner being "Everyone needs to calm down."
    EarlyMon and OfTheDamned like this.
  3. IHateMyTreo

    IHateMyTreo Well-Known Member

    Do you think the manufacture date makes a difference? There was a thread in the GN forum, but nothing new has been posted there in over two weeks.
  4. AntimonyER

    AntimonyER AF Addict VIP Member

    Um, I am going to go with "ninja'd"
    CaptainRon and OfTheDamned like this.
  5. AntimonyER

    AntimonyER AF Addict VIP Member

    Or perhaps "XX,000?"
  6. Copacetic

    Copacetic Well-Known Member

    Ugh, new handset, no one way audio issues for first two weeks and then today...happened ten minutes into a call.
  7. IHateMyTreo

    IHateMyTreo Well-Known Member

    :( That sucks. Any idea when the new unit was manufactured? Wondering if Sammy is making any corrections as time goes by.
    EarlyMon likes this.
  8. vandyman

    vandyman Well-Known Member

    I am LOL from Early's and OTD's comments.

    EarlyMon likes this.
  9. Lucky Armpit

    Lucky Armpit Well-Known Member

    Holy crap, me too. I went quite some time without that problem and it happened three times today. Things like that make me wonder if it's a carrier/regional issue. I see a lot of NC people - especially on the Eastern side of the state such as you and I - having this problem. I'm not saying it IS a carrier problem, but things like that make me go hmmmmm.
    EarlyMon likes this.
  10. EarlyMon

    EarlyMon The PearlyMon Moderator

    About one way calls -

    Obviously, I don't have an answer, but I want to float an idea or two and then let you cats decide if this has any merit.

    The Evo 3D was widely reviewed as having bad call quality. We didn't care, with a return guarantee, we bought them anyway and found the results varied, mostly in the 3D's favor. So, we got into tweaking, etc etc.

    But one day, I noticed that iHeartRadio force close (a problem we suffering increasingly), tied to when one of the bloatware games woke up, looked around, and then went supposedly to sleep.

    But what really happened was that bloatware was using what we call in programming shared memory and it wasn't using it correctly. I rooted and uninstalled that and found that not only did iHeartRadio stop force closing, my call quality shot up through the roof and has been great ever since.

    So - last I heard, you cats don't have a crappy bloatware problem.

    BUT - three things: 1) the phone is just an app in Android and may be getting its audio services memory abused by something else, 2) there was a known hardware issue with the radios in the CDMA model that Google fixed with a software process to bump the radio (think: like a heartbeat) to keep the radio working properly so therefore software service integrity is mega-important to your VZW Gnex, and 3) you might be able to pool your talents and monitor your phones to see if you can find some app or service either starting or shutting down that corresponds to the timing of the onset of the one-way call problem.

    I recommend System Tuner, and I will caution that it's not for the casual user.

    I might suggest that if a few of you, a little more computer-inclined, were to start, you might try the record feature under its Task Mgr (you can see the results under Analyzer after finishing a recording), and let it monitor for hours. See if the periodic activities from apps or processes correspond to time of trouble. Strongly suggest you try some brief recordings first to work through the tool's mechanics, say multiple 5 to 15 minute runs (and note there are settings strewn about for what it records).

    In addition, System Tuner also features a very, very good system log reader (aLogcat to those more Android savvy of such things). And for offline viewing, there's no substitute for the aLogcat app, free in the Market, where you can freeze the log and then use menu, share, to mail it to yourself.

    Being a chiphead, I got by with the free version of System Tuner and then also monitoring via adb when I was looking for things. I don't even want to try to explain how and what I did, nothing personal, but if you don't already know, this isn't the time to learn.

    So, if my idea has merit, I'd recommend the paid version of System Tuner - and be forewarned that I might have a bad idea and any investment in that app could be something that you might regret spending on for no results, so please try the free version and see if my idea makes sense first.

    And even if you have an app force closing, that might be the symptom and not the problem, remember my iHeartRadio would force close when it was a bloatware game at fault for everything.

    Hope this helps, we can noodle a little bit here and if a few of you want to give it a go, please make a support thread in the VZW Gnex forum, and tell me the link here if you'd like me to kibitz on your efforts.

    Thought I'd mention it all here first, because I wanted to start with you cats who know me well enough to know a little of how I think and how easy I am to talk to about things.

    Anyway, it's just a thought.

    PS - if this path is taken, really good idea for everyone to specify all the build info they have on their phones' hardware and software in that hypothetical monitoring thread.
  11. Copacetic

    Copacetic Well-Known Member

    No, there is no date on it anywhere. It is the original baseband .09 as was my last phone. I have made it two weeks before this started, but that was about the same on the original handset. It is frustrating, I am going to follow up with Lucky Armpits suggestion.
    EarlyMon likes this.
  12. Copacetic

    Copacetic Well-Known Member

    This is kind of what I have been thinking. It would seem that something is not playing nice and your idea and example are good starts. I have been studying logs filed in "Android System Info"whenever this happens and have not found any patterns. I am going to go over your suggestion more carefully and see if this is something I think I can do. Thanks for your input!
    EarlyMon likes this.
  13. EarlyMon

    EarlyMon The PearlyMon Moderator

    Log monitoring hint - reset your phone, and write down the start-up time. Then you can relate relative times when they may appear in the logs to real time.

    Also, sharing an add-on app inventory is helpful to look for common clues, and maybe best if there is as much rom commonality as possible.
  14. Copacetic

    Copacetic Well-Known Member

    Sorry its happening to you as well, it is very frustrating. I also am suspicious of the carrier side, the one i had today was at 4:54 20 sec. Curious if any of your three happened at that time. The call was incoming from a land-line phone in Clover, SC at 4:50 . I am south of you on OKI.
  15. Copacetic

    Copacetic Well-Known Member

    Lol, I just did that when I pulled the battery to see if there was a date code under the battery. The funny thing was it erased the old logs that I was going to screen save to see if you recognized anything. Oh well, maybe next time. The other thing of note is the new log started on 12/31 until the phone was completely reset then jumped to the current date and time 1:16 seconds into the log. It was a little confusing at first, but I think it coincided with the clock reset. Thanks for your input!
    EarlyMon likes this.
  16. IHateMyTreo

    IHateMyTreo Well-Known Member

    sounds like it doesn't matter when the phone was built. But if you're interested, there is a Samsung registration site that will tell you when it was manufactured.
    mistermojorizi and EarlyMon like this.
  17. Copacetic

    Copacetic Well-Known Member

  18. vandyman

    vandyman Well-Known Member

    Its funny that you bring this up. My build date is 11-25-11 and I purchased the Gnex on release day (12-15-12).

    ^^^ So we all were going crazy in the pre-release thread why VZW was taking so long to release the GNex. And the whole time it looks like it was
    a supply problem. If the phone was built in Korea on 11-25-11, it would take a few days to package it and than ship.:rolleyes:
    EarlyMon likes this.
  19. EarlyMon

    EarlyMon The PearlyMon Moderator

    Ok, ever since you posted this, I've wanted to respond with some positive encouragement but have been inhibited that I'd come across sounding like Mr. Big WhoopDeDoo. Anyway, I'm not going to sweat that, and just spit out what I have to say and hope that my credit is good enough to be read as I hope to be, even if I screw up the wording and come across wrong.

    Your idea about tying it to the regional carrier characteristic - bravo. A general thing running throughout my life's work has been in testing things - and you've taken a HUGE step there, putting you in a system tester class:

    Look for any factors and put them out there. Never hold back, never second guess yourself, put the ideas for factors out there, because you can always dismiss the bad ones later, but you might hit the right one early and forget it if you don't put it out there. So, bravo!

    The next step is just as hard:

    Be flexible about how you look at ideas and causes behind them.

    That sounds mega-simple, but is WAY tricky, and group feedback and brainstorming REALLY helps.

    For example - if it's regional, what might change? What could VZW be doing on a regional basis to make the problem worse? Instead of first puzzling that out, as a pro tester, my first step is to not change the idea, just turn it on its ear:

    If VZW is doing something different on the tower signals in that region, what processes might change on the phone, despite having to guess about the towers? OR: Are there other factors in that region that might affect processes on the phone?

    And right away, my instincts kick in - lot of people in that region, lot of services under demand - what if it's based on a software priority for syncing data via the internet during peak loads in that region that is causing a conflict with the phone software that ought be at higher priority?

    Right away, I would look for two volunteers to compare during a peak time in a similar location in the region, one with all syncing off, the other with it all on, and then make repeated test calls for a hour or two (just to the home phone, "mary had a little lamb" calls) and see if the idea could be correlated.

    Just an idea to illustrate because sometimes, simple experiments are the best.

    It may interest you Nexicans to know that we had a slew of Froyo adoption problems for the Evo 4G at the end of July/beginning of August 2010, and we worked together like this in our device forum here, nailed our problems, and came up with a simple flow of 1-2-3 things to do that got virtually everyone out of hot water with their early Froyo adoption.

    We put it into one thread, it took the whole group working together, but the power of teamwork came through and we won. It wasn't any one person or type of person that made that effort happen - it was the group, just saying to heck with it, this phone is not going to beat us.

    Welcome, and way sorry I didn't warn about that! :p Android is Linux, so the logging is there - but without a hard drive and lots of space, logs don't accumulate like desktop Linux. :eek:

    BTW, and this is MEGA IMPORTANT on sharing logs:

    Please don't copy and paste logs into your posts! :eek: :eek: :eek:

    Please instead copy them into a txt file (up to about 56kB) and attach that, or into something that you can save a PDF and attach that, or into a series of text files that you zip and attack the zip.

    The key to log analysis is being able to read and search. Long logs (and they will get long quickly) simple swamp page formatting here, and letting the gang download and search/examine logs on the desktop is MUCH better. If you're using Windows, WordPad is best for viewing them, just copy the log from your mail into a WordPad doc, and save it as txt. ;) :)
  20. mistermojorizi

    mistermojorizi Well-Known Member

    vandyman and EarlyMon like this.
  21. EarlyMon

    EarlyMon The PearlyMon Moderator

    PS - Goes without saying that if you cats want to pursue the path I'm suggesting, we mods and guides can move or even copy posts out of here into that suggested testing/ideas thread.

    Again - I'm not telling anyone what to do or even what they should do (I don't believe in shoulding all over people ;) :D), I'm just giving an idea on how to organize if some of you cats want to give that idea a shot. :)
    BabyBlues likes this.
  22. OfTheDamned

    OfTheDamned The Friendly Undead VIP Member

    Just a thought on the silent call issue.

    I've had a few audio apps get rather choppy once the screen shuts off. Possible that the same bug affecting output could affect input or transmission in the similar circumstances.
    EarlyMon likes this.
  23. AndroiDad75

    AndroiDad75 Well-Known Member

    Anyone know of an app that will let me connect to my WHS to watch some of my movies that are stored on it?
  24. EarlyMon

    EarlyMon The PearlyMon Moderator

    +1 great observable!

    I would submit that it's more than WAY possible.

    Android = Linux + Dalvik Virtual Machine + apps

    All apps run inside the Dalvik Virtual Machine and use Linux library services.

    The common base of Linux library library services is what makes Android apps compact and efficient. The heavy lifting is done by tried and true GNU/Linux utilites.

    And all it takes to send things a little south is for an app to abuse how it is using those services.

    So, unlike an iPhone or a BlackBerry or Win phone, with Android, the phone app doesn't bloat up and include everything it needs - and since audio is involved in a call, several Linux library services package the audio before it gets to the radios.

    And in Linux, audio is just audio. It wont care if it's for listening to Ethel Merman belting out There's No Business Like Show Business! or for voice processing to call a pal.

    In other words, parts is parts.

    That abusive game software that bloated my 3vo - sound effects for the game.

    I'm going to bet that the root cause here will end up being a forehead-slapping, Oh yeah, that was obvious! once it's found. And I think the trick is to turn over stones until it is.

    Show of hands as an on-going example of my tester methodology - how many here suffering the call problem are using their phones as a music player that day? Video player? Web media player?

    Sorry if I'm hogging the discussion, I promise I'll lay back a bit now. :)
    ryancmatchett, jmar and OfTheDamned like this.
  25. vandyman

    vandyman Well-Known Member

    I am starting believe that ICS is having problems running the hardware on the few devices that run it. It would seem so with no updates to fix the current issues.
    ICS is all new and everyone thought that the Razr and the Rezound would have officially had ICS at this point.

    My point is that we maybe wanting for an ICS polishing and that would mean 4.1.0 as the rumors grow on.;)
    Lets face it 4.0.3 is not doing much.

Share This Page