Database Users

[Problem] Adb won't show up devices whatever I do...

I Tried guides that try to solve this from everywhere, Including here,
I used latest version of the android usb-drivers that comes with the latest Android SDK (downloaded directly from google with the SDK download GUI thinggy).
Tried to uninstall all usb roots,
Tried force removal of driver using external app and re-installations
Tried different drivers from multiple locations,
And still, whatever I try - there is notihng on the "adb devices" list
"List of devices attached"
<CR>
<CR>
C:\.......>
Everything shows up okay, on first run of the adb the 'whatever' service starts and everything is fine
Device DOES appear properly on device manager "Android Composite ADB Interface".
Windows DOES the pnp beep whenever I check or uncheck the "Debugging mode"
This hapnned both on STOCK ROM (first or second software version of the phone released) and on latest Cyanogen 5.0.6
One thing I did noticed, "Android ADB Device" Either appear under "Android" type (usb debugging on) or under USB Controllers (When usb debugging is off).
Ho, I did not mentioned the phone, I'm talking about Nexus One.
Thanks for any help.

Amm, any ideas?

Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.

I take it your on Windows, so I might not be much help as I use Linux strictly but try to run the command prompt as Administrator (right click > run as I think) and then
adb kill-server
adb start-server
Not sure if that will help but I know in Linux you must start the ADB server as root in order to see the attached devices, so I assume in Windows you must start it as Administrator.

I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps

Beackman said:
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
Click to expand...
Click to collapse
I Ment just that when I said "Tried force removal of driver using external app and re-installations"
drew630 said:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Tried that just now, on windows I'm in the Administrators group, that should work... It doesn't :/
bmxrideher said:
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Click to expand...
Click to collapse
Good idea, but still no salvation :/

Try uninstalling the mass storage driver for the phone, this worked for me

Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed

Synestr said:
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Click to expand...
Click to collapse
No problem, lol, almost a month later. Glad I could help.

Naemion said:
No problem, lol, almost a month later. Glad I could help.
Click to expand...
Click to collapse
Hells to the yea, I now has root and rom and I am a happy boy!
Thanks again

hmm >.< nothing is working for me this laptop is not detecting my (Nexus S) device in ADB
windows sees it fine, drivers are installed (for normal mode and ADB mode), mass storage works,
but ADB Devices list shows up empty
2 other phone works just fine (SGS & XT720)
Update: went to another computer and it shows up properly.... (you just gotta "luv" windows )

Try installing htc sense from htc website even if running vanilla. It will install the driver properly. Then un-install sense and keep drivers. It's the only thing that worked for me.
Sent from my HTC Vision using XDA App

Device won't root. Cannot get the device "offline"

Hope this isn't a post that will really piss everyone off, but I'm not sure really where to go from here. Tried about 20 times. I run the loop command, it shows up for about 1 line and goes away.
I am still getting an Android 1.0 error of some sort. I've been reading about how to get this driver installed correctly. I uninstalled everything and started over (USBDeview, HTC Sync...The one for the Slide, SDK, Updated it with SDK Updater)
Windows 7 x64
Just went to Computer> right click> Manage> ABD Testing Interface....
I have a little yellow exclamation point next to this... Tried updating the driver. Not really sure though what driver I need or where it's at or the place I need to download it.
You ever feel like you've surfed cyberspace to the end of the megacluster? Yeah that's pretty much where I'm at frustrated, broken hearted, and wanting a one-click root procedure like the g1/mytouch.
Is it rude to wave money in developers faces for help? Does this make you feel like a stripper?
Ahhhh I'm just stuck.... Help would be so awesome.

I'm not a dev but I do feel like a stripper, but for unrelated reasons... Anyways. On my win7 64 I had to use pdanet and actually have the program running. For whatever reason when I tried closing pdanet it wouldn't work, so give that a shot. It also stopped the android 1.0 driver issues. I also gather from wes garners' twitter page he's working on a method of rooting that runs the adb scripts and **** for you. Maybe just wait it out.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

DaemionIX said:
Fermunky, I've been following your problem because I was having it too. What finally got it for me was, I formated a different sd card, put it in the phone, removed all software ( htc sync, pdanet) and removed all drivers I could find using usbdeview. Then rebooted with phone unplugged, installed pdanet following all their instructions, then the loop worked perfect. Good luck
Tl;dr version, i tried it all at the same time and it worked
Click to expand...
Click to collapse
That was on a win x64 system. Honestly I think it was the sd card, as weird as that sounds, because I tried all the usb stuff for about 4 hours to no avail, swapped out the sd card, rooted the first try.

I'll give all this a try. Do you use PDANet with or without HTC Sync? I was pretty tired last night when I tried and eventually gave up.
Hence all the stripper references.
I have an extra SD Card from my original Mytouch. I'll give it a try and let you know how it goes.

2Noob4U said:
I'll give all this a try. Do you use PDANet with or without HTC Sync? I was pretty tired last night when I tried and eventually gave up.
Hence all the stripper references.
I have an extra SD Card from my original Mytouch. I'll give it a try and let you know how it goes.
Click to expand...
Click to collapse
Just pdanet

Alright I'll give it a whirl. I'll let you know how it goes.
-------------------------------------
Sent via the XDA Tapatalk App

Took me a day to figure this out too. Uninstall all the drivers then install pda net and reboot .. you must reboot .. then try the process . I wasn't rebooting after removing drivers and it wouldn't work until I did ..
-------------------------------------
Sent via the XDA Tapatalk App

You should really have looked at the other thread on this already. Any driver will work, as long as you can get "adb devices" to show your phone when the phone is booted normally. Whats worked for many others, especially myself after 4 days of trying, was using a different, freshly formatted SD card. Good luck.

To no avail!
Just tried again. Tried without rebooting the computer the first time and "offline" would hang for a little longer than before. Still wouldn't stay. Should I have tried recovery a few more times? (I did try about three times.)
Uninstalled and reinstalled everything. Then tried "loop". "offline" doesn't even show up. Tried an old SD card too after I reformatted it. Does it matter the size of the SD card?
fermunky- I've been following your posts pretty regularly and I think I'm having the same problem. Yes I do have ADB devices showing up if the phone is on normally and running through the SDK. Had a problem for a while where it wouldn't recognize the device, but it does now.
C:\>cd android\tools
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 device
If I do figure this out I want to post up a step-by-step in this thread of what exactly I did to make it easier on people like myself.

It goes like this
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
HT05PPS07559 offline
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
C:\Android\tools>GOTO TOP
C:\Android\tools>adb devices
List of devices attached
Is there a way to catch it offline?

It is a hit or miss deal. Some times it works, some times it doesn't. I ran into the issue while rooting mine and just kept at it till I succeeded. One plus is that after you root you never have to worry about it not detecting the device properly.

sk8rbebop said:
It is a hit or miss deal. Some times it works, some times it doesn't. I ran into the issue while rooting mine and just kept at it till I succeeded. One plus is that after you root you never have to worry about it not detecting the device properly.
Click to expand...
Click to collapse
Am I doing it right overall though.
1. Switch out SD card right before getting into recovery so there is absolutely nothing on the SD Card. (I've noticed if you let it boot it puts a LOS.DIR file or something of that sort.
fermunky had a similar problem and said once he installed everything a certain way he got it "offline" right away.
Is there a step-by-step I should be trying? Maybe another post I haven't read yet?
I'll keep trying, but it's kind of seeming like a lost cause. I've only been trying 2 days (Ha ha) After I surpass 4 days or so I'll give up and wait for Wes for the hook up.
Money for him!

Ultimate fix for device detection!!!
Uninstall EVERY driver (USBdeview) for anything android, i mean everything.
Installl HTC SYNC for espresso(any other software, PDAnet, Android Explorer.... needs to go). Dont let any drivers install while the phone is on!
Power off the phone and then plug your usb into it (phone needs to be usb debugg on and in sync mode).
Boot phone into the bootloader and the only driver it will install is the ADB driver which , without loop or multiple recovery boots or anything the phone will be detected.
I tried EVERY method in these forums and this worked perfect , went straight to pushing files, and only took 20 minutes to get it all the way to slidemeroot2. works great and everytime i need clockwork i can push the update without the problem of the device not being detected even after all the other drivers installed when i rebooted the phone. It seems that the other drivers were killing the adb function???? dunno, but i no longer have an undetected device, ever!
Also, i suggest if you want to get back into clockwork easily, plug in the phone while in normal operation mode and the adb reboot recovery that joker.
Hope this helps some, and thanks to all that have gotten us this far.

Thanks
mtjnkee said:
Uninstall EVERY driver (USBdeview) for anything android, i mean everything.
Installl HTC SYNC for espresso(any other software, PDAnet, Android Explorer.... needs to go). Dont let any drivers install while the phone is on!
Power off the phone and then plug your usb into it (phone needs to be usb debugg on and in sync mode).
Boot phone into the bootloader and the only driver it will install is the ADB driver which , without loop or multiple recovery boots or anything the phone will be detected.
I tried EVERY method in these forums and this worked perfect , went straight to pushing files, and only took 20 minutes to get it all the way to slidemeroot2. works great and everytime i need clockwork i can push the update without the problem of the device not being detected even after all the other drivers installed when i rebooted the phone. It seems that the other drivers were killing the adb function???? dunno, but i no longer have an undetected device, ever!
Also, i suggest if you want to get back into clockwork easily, plug in the phone while in normal operation mode and the adb reboot recovery that joker.
Hope this helps some, and thanks to all that have gotten us this far.
Click to expand...
Click to collapse
Haven't tried this yet.
Do it in a few hours. I've been at this all day and need some food and beer! Beer always makes computer/smartphone problems disappear.

sorry to be "that guy" but there are already 5 threads about this issue also, there is a questions and answers thread that this should have been posted in instead.

Straight to "recovery" not "offline"!
Ok is this good or bad? It's not what the video nor website says, but it's different and different is good!
Just lists the HT........ recovery over and over??? Can I start everything from here?
Dude if this works I'll buy you a beer!

I'd be glad to move it.
HighRidas said:
sorry to be "that guy" but there are already 5 threads about this issue also, there is a questions and answers thread that this should have been posted in instead.
Click to expand...
Click to collapse
No biggie man. Just wanna figure it out and you can move this at will if you like.

If you have it in recovery, hit volume up and power. It should display the recovery menu. Try pushing the update file over.
-------------------------------------
Sent via the XDA Tapatalk App

sk8rbebop said:
If you have it in recovery, hit volume up and power. It should display the recovery menu. Try pushing the update file over.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Tried... It wouldn't push said failed

Then it is an issue with your PC. Do what mtjnkee said and uninstall everything Android. Then use HTC Sync's drivers.

ADB Server Out Of Date - rooting

Hi everyone, since the root thread is so bogged down, I thought I'd try posting a new thread. I couldn't find anyone else that was getting the same messages as me, and I suspect they are what's preventing me from getting root.
Whenever I start steps 1, 2, or 4 I get a constant stream of "ABD server is out of date. Killing..." and sometimes a "ADB server didn't ACK"
Any ideas?

adrianoftyriel said:
Hi everyone, since the root thread is so bogged down, I thought I'd try posting a new thread. I couldn't find anyone else that was getting the same messages as me, and I suspect they are what's preventing me from getting root.
Whenever I start steps 1, 2, or 4 I get a constant stream of "ABD server is out of date. Killing..." and sometimes a "ADB server didn't ACK"
Any ideas?
Click to expand...
Click to collapse
The "ADB server is out of date. Killing..." is not a real problem. It just means that there is still an instance of the ADB server running but not active/connected anymore and it should kill the server and start a new instance.
If you get the "ADB server didn't ACK" though it might mean that your X10 deivce isn't properly connected or something. Make sure it's plugged into USB and you are using the same USB bus, also make sure that USB Debugging is enabled on the phone.

Mod. edit: not dev related, moved to general

what concerns me is that I'm getting the error CONSTANTLY... as if it's killing its own process, then starting it again.

I had the same problem. I forgot that I added the adb.exe from the AndroidSDK folder to the Windows path variable. I solved it with deleting the adb files from the "step" folders in the rooting folder so it used the existed adb command, worked without problems then.
Sent from my X10i using Tapatalk

Well, I deleted the adb.exe files, and then nothing worked, it just said adb was not a recognized command. Still haven't got root. Ugh.

No one else has any suggestions??

adrianoftyriel said:
No one else has any suggestions??
Click to expand...
Click to collapse
Did you checked in Taskmanager if there is a second adb process running already ? If so kill it and try again.

I checked and couldn't find one. I just finished rooting on another machine. I finally gave up on my laptop doing it.
Sent from my X10a using XDA App

Restart your pc, and retry, that's works for me!

starfishguts said:
Restart your pc, and retry, that's works for me!
Click to expand...
Click to collapse
Buddy, have you checked the date of the post you have just replied to.

[Q] Cannot get adb to connect to Nook Color

Ok I've researched this to death and tried in on both Windows 7 and osx 10.6.6 to attach using adb and install a couple of .apk's and the same thing happens on both platforms - NOTHING :-(.
You would think this would be pretty basic, but I am missing something somewhere.
Summary:
1. Am running the stock rooted b&n rom.
2. Can access both the internal and SD cards on the nook on both windoze and
osx. Eliminates cables, drivers etc...
3. Debug is selected in the nookstools settings
On both OSX and Win 7 installed the latest version of the Android SDK - both installs provided me with the platform-tools directory from which I will initiate all adb commands. So far so good...
on mac: ./adb devices returns:
$ ./adb kill-server
$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
$
As you can see I never get any device information returned, does not matter if Im on Windows or mac - same response.
Just for grins I downloaded the wireless app and tried to connect adb that way...no luck...
I could go into everything that i have tried over the last 24 hours...but that would also be pointless.
Bottom line...assuming this is something simpleI am just missing. Assuming since the symptoms are the same on both platforms that the issue lies on the nook but for the life of me I cannot find it.
Assuming if I cannot figure this out I will slowly go insane..my next step is to flash either froyo or honeycomb rom and see if this helps with the problems. Of course I MUST have the market available to me or I will not b able to load any .apk's.
Hpe Im in the right place. Any guidance is GREATLY appreciated.
Love this little Nook....BG

I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
YMMV, but it solved that issue fo me.

Who Swami - It Worked
Swami,
I fall to my knees and bask in your knowledge: It WORKED!
I knew it was something simple, there is not a post on the entire Internet in any forum I have ever found (and I may have searched them all!) that mentions superuser needs to be running for adb to be able to communicate with the device. I wonder if this is a nook issue only. Will test on my wife's Epic this evening and post the results tonight.
My sanity now restored I bid you all a hearty SEE-Ya!
-BG

Omg I actually helped someone!
Glad it worked for ya I'm sure you felt the same relief I did when I finally stumbled across that fix.. I was pulling my hair out for hours LOL

Thanks Once More
As was I such a simple fix you would think I would have thought about permissions on the client side , such is life and tech thats why we all hang together.
Must say I was going to purchase the iPad 2 when it came out (NEVER buy 1st gen Apple) but now I'm not so sure...LOVING my Nook.

themirthfulswami said:
I know this will sound stupid, but I had this same problem and the only way I found to fix it is to adb while I have the superuser app running.
Click to expand...
Click to collapse
I'm not sure if this is related but I *think* that what made it work for me was to freshly enable the Debugging USB mode immediately before connecting the USB cable. Maybe that also triggered the Superuser app??? It's always the small things in life that make us smile

my problem is a little different.... I have sd cards with honeycomb (no market) and froyo (market and other apps). I can see the NC in adb with both, but honeycomb shows the device offline... and adb cannot talk to it. froyo show the device online and I can use adb. Both honeycomb and froyo show up in windows too.
I can't find anything that talks about getting the NC to show online to adb.

Same Problem
I have the same problem of trying to get my nook recognized. The only thing I can see different between my setup and the instructions on NookDevs was that they said I should see Android ADB Composite Interface on my Device Manager. Mine reads Android ADB Interface.
Tried the Superuser and the USB Debugging with no luck. Just really trying to get this set up so in case I need to factory reset. Because the 8x method manually is way too hard.

Have you guys read though this thread?
http://forum.xda-developers.com/showthread.php?t=910008&highlight=ADB
it worked for me like a charm.

that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.

I had intermittent ADB success with my Mac. After installing the ADB Wireless app there have been no problems.

Seaweedbrain said:
that thread didnt work for me..
i tried lots more ways. just not able to get my nook (running honeycomb) online.
adb devices
just shows a serial code and says offline.
what do i do?
i want to install the G-apps.
Click to expand...
Click to collapse
nvm
i connected my nook to the back of the cpu.
for some reason, it seemed to work fine.
it read the device as online.
got the g-apps

[Q] What's the micro usb port for?

Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq

It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.

Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?

don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.

I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was

I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq

Drivers from acer website.

I have adb installed should this not be enough?

You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.

I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq

I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6

I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium

Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq

don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.

If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App

gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.

I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.

sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.

Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try