I'd be interested to know how many time "hate" and "Verizon" were used in the same sentence .
I'd be interested to know how many time "hate" and "Verizon" were used in the same sentence by Han.
Fixed it.
Upvote
0
I'd be interested to know how many time "hate" and "Verizon" were used in the same sentence .
Yikes! That does not sound good.
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"?Oh, I'd be sending that puppy back in a heart beat! I'm still knocking on wood, but I haven't had any reboots on my replacement phone, and only had maybe 4 or 5 on the first Nexus I had.
I'd put a large bet on the winner being "Everyone needs to calm down."I'll bet a repeated-phrase analysis of the pre-release thread would prove interesting.
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 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."
Hi guys and gals, wanted to drop in and say hello. For those that are still having the "one-way audio" issue with their Galaxy Nexus (Nexi?) devices, please Star the issue on Google's web site. I've done a little digging and read plenty of people are having this problem and replacing the device does not fix the issue. The link is here. Thanks, and GO GIANTS!!
Ugh, new handset, no one way audio issues for first two weeks and then today...happened ten minutes into a call.
Ugh, new handset, no one way audio issues for first two weeks and then today...happened ten minutes into a call.
That sucks. Any idea when the new unit was manufactured? Wondering if Sammy is making any corrections as time goes by.
About one way calls -
...
Anyway, it's just a thought.
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.
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.
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.
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.
http://androidforums.com/verizon-galaxy-nexus/478164-when-your-gnex-manufactured.html
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.
http://androidforums.com/verizon-galaxy-nexus/478164-when-your-gnex-manufactured.html
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.
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!
No, no, no, nooo.
Adam Lambert to Replace the Late Freddie Mercury in Queen
Adam Lambert to Sing With Queen | Music News | Rolling Stone
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.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.