• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Galaxy Nexus Watering Hole

Hello all.. Glad to see you all again!! A couple of questions.. I hope they haven't been answered.

1. I can't sync with facebook. Anyone else have that problem or know a solution?

2. How is everyone else's battery life?? Only had one good full charge, so I'm hoping today will be better but It seems to suck up some juice.
 
Good morning Nexlings!

As some of you are aware, my Nexi are sitting in a Verizon bag 'til Christmas, taunting me. I need your help. I need some ideas to make the next 9 days bearable.
 
halon said:
Hmm? Typed "fastboot oem unlock" and all I get is "waiting for device".
Click to expand...


Make sure 'fastboot devices' shows your phone connected. If not, the Samsung drivers are probably not setup correctly. And of course the phone has to be in bootloader mode.
 
woodraskam said:
Interesting.....so 4.0.1 had wifi tether enabled?

Edit: Cause I'm pretty sure these images are available...anything you noticed good?
Click to expand...

They are available, at least on Droid-Life somewhere. I don't know, I'm on 4.0.2 and I did a speed test this morning. 7MB down, 11MB up. That seems pretty decent to me.
 
Thought I figured out the bootloader earlier? Something so easy and it's not working. Not sure what I'm forgetting to do?

Ugh...
 
skr8ness said:
2. How is everyone else's battery life?? Only had one good full charge, so I'm hoping today will be better but It seems to suck up some juice.
Click to expand...

Mine is so-so. I've been playing with it a ton, though, and I always have the brightness set to full.

But I've probably been getting maybe 4 hours, and that's on extended battery!

I don't know how BMX said he was getting 6 hours with downloading tons of gigs at the same time. I think that was BSing.

Oh well.
 
halon said:
Hmm? Typed "fastboot oem unlock" and all I get is "waiting for device".
Click to expand...

kk4df said:
Make sure 'fastboot devices' shows your phone connected. If not, the Samsung drivers are probably not setup correctly. And of course the phone has to be in bootloader mode.
Click to expand...

I had the same issue, and had a unknown device in Device Manager called Android 1.0 -- here is what I did.

I went to Properties > Update Driver. Navigated until it let me pick the driver myself and then I went to ADB devices. You should see Google (Motorola?) and Samsung. Choose Samsung and then choose the one dated 11/25/2011 -- that should install the correct driver and then the device should be recognized in bootloader mode.

Let me know if that helps / makes sense. Not sitting in front of computer right now so hard for me to remember exactly. Also try looking through the comments on Droid Life about the bootloader unlock, some helpful stuff in there.
 
Good morning! So I was finally able to get my phone around 10 PM once I got to the store after my 13 hour work day. They still had some! Luckily there are so many Verizon stores/resellers around that there was bound to be one in the area.

All in all, I am blown away by this phone. Keep in mind, I'm coming from an Eris, so anything would be great. But after being thoroughly unimpressed by the TBolt/Bionic/Razr/Rezound (I was eligible to upgrade in January) I was a bit skeptical that this could live up to all of our hype. Yet it does. So smooth, so fast. Everything that everyone has already covered, and then some. The battery life may be an issue - but I can't really test that until the honeymoon phase is over and I actually use the phone like I normally would instead of playing with it constantly.

RazorSharp said:
EDIT: By the way, did anyone else immediately cut off the stupid VCAST tag from the charger cable?? No Verizon bloat for me, thanks.
Click to expand...

I just laughed when I saw that tag on there. Had to stick it that close to where you plug it in, huh Verizon? Couldn't let VCast die?
 
halon said:
Thought I figured out the bootloader earlier? Something so easy and it's not working. Not sure what I'm forgetting to do?

Ugh...
Click to expand...

Sorry to hear you're having problems. I do know that I ran into a situation where it would say "waiting for devices" on the command window, but I forgot what I did to fix it.

Dammit, I suck at training or explaining. I'm never picked to train here at work because they know I suck. I basically fly by the seat of my pants, and I never write anything down or remember what I did! :(





On another note, I figured out what was wrong with the crappy pictures. It's Google's fault. If you sync contacts with Google, they will always restore at crappy resolution. I had to manually go in and edit the pictures with normal pictures in my gallery, and now they're great. I just exported the contacts to the "SD" partition, then transferred that file (.vcf) to my computer. If I ever need to switch phones, I'll just import that file to my new phone. I'm not going to sync with Google anymore, except for emails.




I also heard that there is a specific Netflix HD app (the market app won't stream in HD) floating around somewhere here. I'll try it out.
 
Oh, also, my Beautiful Widgets weather/clock app won't update my city even though I have the refresh and geolocation on. Anyone else having an issue? Or can recommend another clock/weather widget that will auto update? Sadly, I kind of miss the Sense clock/weather widget.
 
LiQUiDBuD said:
Unfortunately, the facility is 60+ miles from my house. Exploring the options...
Click to expand...

Quoting myself.

Verizon doesn't allow FedEx Hold at Location until at least one delivery attempt has been made. Argh!

My last resort is to leave an authorization note attached to the front door and cross my fingers.

Otherwise, I won't get my Nexus goodness until Monday at the earliest.

Par for the course with this release, it continues to be my own personal fiasco.

It's a shame that Verizon doesn't use UPS Next Day delivery. FedEx Express is so unreliable and inconsistent.
 
Stigy said:
I had the same issue, and had a unknown device in Device Manager called Android 1.0 -- here is what I did.

I went to Properties > Update Driver. Navigated until it let me pick the driver myself and then I went to ADB devices. You should see Google (Motorola?) and Samsung. Choose Samsung and then choose the one dated 11/25/2011 -- that should install the correct driver and then the device should be recognized in bootloader mode.

Let me know if that helps / makes sense. Not sitting in front of computer right now so hard for me to remember exactly. Also try looking through the comments on Droid Life about the bootloader unlock, some helpful stuff in there.
Click to expand...

I have 11/25/2011. When I type in "adb devices" I get the serial number. Earlier this morning when I opened an command window the c prompt had "android-sdk-windows..." after it, but now it doesn't. Either way I still get "waiting for device".
 
RookTheKlown said:
Yeah, I guess the 4G around here isn't as good as I'd hoped. I noticed I had quite a few bars as I was passing by Providence Place last night, but other than that it's been shoddy at best. That said, I'm sure it'll get better in time.

Regardless of the limited 4G in RI, I still couldn't be happier with this phone. It's everything I imagined and then some. Showed it to a few friends at work, whom all got jealous and now can't wait for their upgrades.

Now I just need a dock for at work.
Click to expand...

yea I am still happy with the phone but I was really looking forward to 4G....I am sure we will get better coverage overtime but for now....eh. I am also looking for a dock, one that doesn't plug into the micro usb just the pins on the side for charging so I can put it next to my bed and maybe another for work not sure yet.
 
Had a scare this morning. My precious is being FedEx'd to me here in AZ from Cali. It left Cali yesterday around 4pm. I was thinking awesome! It should be in town late last night. Woke up this morning and checked and it said it was in Memphis! :eek: WTF!

Checked again when I got to work and it left Memphis at 1am and got here at 4am. Sigh of relief!
 
You must log in or register to reply here.
Back
Top Bottom