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

Galaxy Nexus Watering Hole

woodraskam said:
Then replug in your device and when it asks to install, (Select Manually find folder) point it to the folder where you unzipped the above driver download. It shouldn't matter where you extract it. I did it under the android sdk folder in a new folder call GNex Drivers
Click to expand...
It doesn't ask to install...I uninstalled the SAMSUNG ADB interface driver, replugged it in, and it auto installs...Doesn't prompt me to manual install.

I try to update the drivers manually with the naked drivers and there isnt an "android_winusb" file to try and replace it with in the naked drivers folder. Do I select ssudadb instead? That is the only one it allows me to select, but prompts me not to do it because it can cause harm or something...
 
tluley51 said:
It doesn't ask to install...I uninstalled the SAMSUNG ADB interface driver, replugged it in, and it auto installs...Doesn't prompt me to manual install.

I try to update the drivers manually with the naked drivers and there isnt an "android_winusb" file to try and replace it with in the naked drivers folder. Do I select ssudadb instead? That is the only one it allows me to select, but prompts me not to do it because it can cause harm or something...
Click to expand...

I used that one, and ignored the windows warning. When I did it though, windows was able to scan the whole extracted directory and chose one for me.
 
If you have the drivers installed it should be easy to see if it's the right ones. Continue following the unlock tutorial and after you run the "adb reboot bootloader" command, run this command "fastboot devices" if a device shows up, it's installed correctly.
 
woodraskam said:
I used that one, and ignored the windows warning. When I did it though, windows was able to scan the whole extracted directory and chose one for me.
Click to expand...

Alright that seemed to work, but when I CMD 'adb devices' I still get "'adb' is not recognized as an internal or external command"
 
I know this may sound dumb but do you have debugging set to ON in the phone. Adb won't recognize it without that set right. Also adb will not work outside of the main environment. (Boot loader/recovery/booting...)
 
tluley51 said:
Alright that seemed to work, but when I CMD 'adb devices' I still get "'adb' is not recognized as an internal or external command"
Click to expand...

you need to open your command prompt into the same folder as the adb.exe file.

Usually under adroid sdk/platform-tools

spelling might not be 100%, i'm going off of memory. Fastboot.exe must also be in this same folder.
 
I sure do love sleeping in!

woodraskam said:
you need to open your command prompt into the same folder as the adb.exe file.

Usually under adroid sdk/platform-tools

spelling might not be 100%, i'm going off of memory. Fastboot.exe must also be in this same folder.
Click to expand...

You can also add platform-tools to your Environment PATH, but CMDing at the folder is probably better anyway.
 
zx10droid said:
ok, so the speaker level wass frustrating me a little bit and went ahead and got volume+, for $1 i figured it was worth a shot. i know there was some debate over whether it really worked or not, but for me, it works like a charm! best "mod" yet haha, i just put it on +4 to keep it safe for now, but definitely a solution for those who arent happy with the speaker volume
Click to expand...

Volume+ doesn't show up in the market for me. Weird.

Can you tell me who the developer is?

All I see is Volume Control, but i don't think that's it.


EDIT:

nevermind, found it!

But it says it ONLY works for GB-running phones. Is that the same one you got?
 
So the phone fell out of my sweat pant pocket today and onto a patch of concrete. :( Got a couple of noticeable scratches on the bezel and backside... Can't even get through the first week without damaging the device! And now I'm gonna be stuck with it for 20 months... Ughhhhh. Other than that, my experience with the GNex has been fantastic!
 
HanSolo said:
Volume+ doesn't show up in the market for me. Weird.

Can you tell me who the developer is?

All I see is Volume Control, but i don't think that's it.


EDIT:

nevermind, found it!

But it says it ONLY works for GB-running phones. Is that the same one you got?
Click to expand...

yes, thats the correct one. the icon looks like a volume knob on a guitar amp or something... works fine even on ICS
 
AndroidsOfTara said:
I was using Launcher Pro Plus on my OG Droid with its awesome calendar widget.

Unless I'm being an idiot and can't figure it out, the stock calendar widget with ICS is rather lame. I'd like to see far more than just the current day.

I'm now using Pure Calendar Widget on my Gnex, but it's fairly ugly and lacks the functionality of the Launcher Pro one.

So... does anyone have any suggestions for a functional and attractive calendar widget?
Click to expand...


I like Pure GRID calendar Widget. It is by the same developeras Pure Calendar but I like the various views.
 
iSyntac said:
So the phone fell out of my sweat pant pocket today and onto a patch of concrete. :( Got a couple of noticeable scratches on the bezel and backside... Can't even get through the first week without damaging the device! And now I'm gonna be stuck with it for 20 months... Ughhhhh. Other than that, my experience with the GNex has been fantastic!
Click to expand...

I am actually considering getting a case, something I usually don't do, because this phone is so wide and slippery and I'm afraid it's only a matter of time before it slips out of my hand. It's really a problem when I try to use it one-handed.
 
You must log in or register to reply here.
Back
Top Bottom