Is USB access under Windows 8 working (ICS)?

[rseiler]

I'm not having much luck getting USB access to work reliably under Windows 8 RTM.

I've tried the official driver from late last year, the one posted elsewhere here that's just a few months old, and the one from Windows Update that's even newer. That newest one works best, but it's still flaky:

For example, both the phone and SD drive show up, but then a minute later Windows will popup a message saying that there's a problem with the SD drive. There isn't, because it does the same thing with another SD card, and there's no problem on a Win7 machine. (There was also no problem with GB and a beta version of Windows 8, so I think ICS may be the main culprit here.)

Then it'll be recognized again for a random amount of time, before popping up the error, etc., etc.

I thought it might have something to do with MTP, so I switched to GB-style mass storage, and surprisingly it was no better.

The phone just doesn't want to stay recognized by the system for very long. Is anyone using both ICS and Windows 8 with success?

 

[thenameisnigel]

Yes, but you have to install the driver BEFORE you plug it in. Otherwise, you'll have to wipe your OS and start over. Windows 8 installs a generic Android driver that is know to cause crashes and failures when usb is used.

And two, how did you get your RTM to activate? My MSDN key won't activate as they've taken the servers down to prepare for the final release. As well as the automated system due to piraters.

Sent from my SPH-D710 using Android Central Forums

 

[rseiler]

Is there a thread here or elsewhere about the Win8 driver, at least the older one, where these issues are discussed? I looked and didn't find much. The one made available in MU/WU a couple weeks ago, which is listed as a Vista/Win7/Win8 driver (same driver for all platforms), sure looks like the real thing.

I installed the downloadable Samsung driver before plugging it in, though I've never heard of a situation where you'd have to wipe an OS because of a driver. Drivers can be rolled back/uninstalled. I'd use another machine before wiping a PC for a phone!

Which driver are you using then, the 2012 one from Samsung.com, or the one from a few months ago taken from the Kies installer? Listing the the version # as shown in Device Manager would be helpful so that I could focus on that one.

But I think it's less of a driver issue than an ICS one, since that's when my problems started. I was OK with even the Consumer Preview and GB (2012 driver), but as soon as I moved to ICS (I have the stock downloaded one, not CM10 like you, which is a notable difference, I think), still with the 2012 driver and still with Consumer Preview (at the time), things got weird and have continued the trend with my new Win8 install.

I activated on the first day without incident. Try calling the automated tel no for activation.

 

[thenameisnigel]

Is there a thread here or elsewhere about the Win8 driver, at least the older one, where these issues are discussed? I looked and didn't find much. The one made available in MU/WU a couple weeks ago, which is listed as a Vista/Win7/Win8 driver (same driver for all platforms), sure looks like the real thing.

I installed the downloadable Samsung driver before plugging it in, though I've never heard of a situation where you'd have to wipe an OS because of a driver. Drivers can be rolled back/uninstalled. I'd use another machine before wiping a PC for a phone!

Which driver are you using then, the 2012 one from Samsung.com, or the one from a few months ago taken from the Kies installer? Listing the the version # as shown in Device Manager would be helpful so that I could focus on that one.

But I think it's less of a driver issue than an ICS one, since that's when my problems started. I was OK with even the Consumer Preview and GB (2012 driver), but as soon as I moved to ICS (I have the stock downloaded one, not CM10 like you, which is a notable difference, I think), still with the 2012 driver and still with Consumer Preview (at the time), things got weird and have continued the trend with my new Win8 install.

I activated on the first day without incident. Try calling the automated tel no for activation.

You should've downloaded and installed Kies. The stupid thing about Windows 8 is once a driver installation fails once, it will not try again. Ever. You'll have to manually do it in Device Manager. I reported that bug on the MSDN network , and I'm trying to find a bypass to one-time-driver thing. The only thing that I can recommend at the moment is re-installing your OS which is probably not the best route as NO ONE , can activate the OS at the moment. I talked to one of the reps.

 

[rseiler]

I have tried the Kies driver though didn't install the whole package (all the stuff that's not the driver).

I guess I haven't noticed that Win8 doesn't try to install a driver after failing once (is there a link over there for the issue, as I want to learn more about it?), but I'm used to dealing with Device Manager directly, so that shouldn't be an issue. Getting the driver installed isn't really the problem.

Before I upgrade to the next ICS ROM, maybe I'll try going back to GB for a while. I bet it works just fine, since as I mentioned, it was working before without any worry over the driver (on Win8 Consumer Preview). If things then went wrong merely by moving to ICS, then I would think ICS has a lot to do with what's happening.

 

[rseiler]

I've made some progress on this, though I don't know what did it exactly since I somewhat carelessly did these very close together. Listed in increasing order of likelihood:

1) Installed an even newer driver than I had before. I know that this alone didn't help.
2) From a Win7 machine, upgraded from FF18 to FI27. Since the driver never mattered before, and ICS was when all my troubles started, this is a top suspect.
3) Though it could have been that I then upgraded to an even newer version of the chipset driver (I have Sandy Bridge), one that's updated for Win8. I did this by extracting it and then going into Device Manager and updating anything in "System devices" and "Universal Serial Bus controllers" that had a 4-digit alphanumeric sequence at the end of the line (these are Intel devices).

 

[thenameisnigel]

It works but you have to install the driver before you plug it in ..

Sent from my Epic 4G Touch using Tapatalk 2

 

[rseiler]

Yes, you'd mentioned that before, and I had, but this apparently was a different issue.