Develop Bugs

ADB + Windows 7 x86 problem

Hi,
I'm using latest froyo/eclair on nand, but have problems with adb and windows 7 x86. I've installed latest android sdk, connected my kaiser and then installed drivers. I can connect with adb but it disconnects and reconnects all the time. I cannot even install app or copy files. The same situation is on my second win7 installation.
This is rather not android build problem, but windows, because on the same laptop with ubuntu, adb works without such problems.
Anyone have some workaround for this? Maybe there should be other drivers used?

Same thing happens to me. It happened with his eclair build also. I wonder if it has to do with background processes running. I reinstalled froyo and nothing so far. Before I used to get the charging light go on and off all the time killing my battery.

Actually this happens on XP also, and has happened on every build I have used, I'm sure it's a driver or even hardware issue.
Since I very rarely use adb it's never really been an much more than an occasional annoyance.
I'm expecting to get a G1 delivered in the next few days, so I may be able to check the whole driver/hardware aspect in more depth.
My own workaround for this is simply to use an SD card reader and adaptor for moving files around between phone and computer, actually I find this almost as fast as adb, considering the time taken to set up adb, enter the commands, etc.

zenity said:
Actually this happens on XP also, and has happened on every build I have used, I'm sure it's a driver or even hardware issue.
Since I very rarely use adb it's never really been an much more than an occasional annoyance.
I'm expecting to get a G1 delivered in the next few days, so I may be able to check the whole driver/hardware aspect in more depth.
My own workaround for this is simply to use an SD card reader and adaptor for moving files around between phone and computer, actually I find this almost as fast as adb, considering the time taken to set up adb, enter the commands, etc.
Click to expand...
Click to collapse
It's not hardware issue,but rather windows drivers. Like I wrote earlier - it works ok on ubuntu...

voyteckst said:
Hi,
I'm using latest froyo/eclair on nand, but have problems with adb and windows 7 x86. I've installed latest android sdk, connected my kaiser and then installed drivers. I can connect with adb but it disconnects and reconnects all the time. I cannot even install app or copy files. The same situation is on my second win7 installation.
This is rather not android build problem, but windows, because on the same laptop with ubuntu, adb works without such problems.
Anyone have some workaround for this? Maybe there should be other drivers used?
Click to expand...
Click to collapse
Same problems for me with the Polaris.
Anyone this working with windows 7 x86?

I've given up trying to get it to work on both my machines, I get buy with the sdsplit app

Drivers

Can anyone get me the Epic 4G drivers? My Captivate connects easily, but I can't get this thing to connect to my PC for the life of me.

kennethpenn said:
Can anyone get me the Epic 4G drivers? My Captivate connects easily, but I can't get this thing to connect to my PC for the life of me.
Click to expand...
Click to collapse
What drivers are you looking for specifically? The ones for ADB or the ones to mount the sd card? There shouldn't be any needed specifically for the sd card, but if its not working, at least the phone comes with a microSD to SD converter. If its for ADB, try downloading and installing pdanet on your pc, that may work to install the proper drivers for adb. I obviously don't have an epic currently, but this is a trick I used to get adb working on my hero
Also, found these drivers, have you used them before?
http://drivers.softpedia.com/downloadTag/Samsung+Galaxy+S+Windows+Driver

Might have to wait for a dedicated driver come launch time.
This official Samsung website should have the driver available for download.
http://www.samsung.com/us/consumer/mobile/mobile-phones/sprint-phones/index.idx?pagetype=subtype

Galaxy S Drivers worked!
rufflez2010 said:
What drivers are you looking for specifically? The ones for ADB or the ones to mount the sd card? There shouldn't be any needed specifically for the sd card, but if its not working, at least the phone comes with a microSD to SD converter. If its for ADB, try downloading and installing pdanet on your pc, that may work to install the proper drivers for adb. I obviously don't have an epic currently, but this is a trick I used to get adb working on my hero
Also, found these drivers, have you used them before?
http://drivers.softpedia.com/downloadTag/Samsung+Galaxy+S+Windows+Driver
Click to expand...
Click to collapse
I was using the drivers from the Samsung Website on win 7 32bit.
Phone couldn't connect to ADB for some reason. I removed those drivers and went with the Galaxy S drivers you linked us to from SoftPedia. Success!
Thanks!

ADB not working

Hi my brother has a Desire HD just liek mine and is unlocked rooted and hboot just like mine but he cannot connect his phone to the PC if he put the phone into bootloader it doesnt recognise it, if he puts it in fast boot it doesnt recognice it..
Debugging is on stay awak is on.
We are using windows 7 and installed XP as a virtual environment to see if that helped but when connedted it said it was connected to 02mmc ccid but doesnt allow him to do anything.
He has no option to select media storage from handset..
He has managed to flash a new rom and kerna by taking out the memory stick and putting it directly into the comp. Then he boots to recovery and flashes from the but he cannot use the sync or any ADB commands.
Could anyone please help..

HI,
you need the windows driver for android system
you can download it from the SDK GUI

bearing in mind myine works perfectly fine on the exact same laptop would it still be the driver

Are you using 3 uk rom. I had a crazy job trying to get adb working..
I followed the guides and pushed all the right buttons and no joy. Does fastboot work, might be worth seeing if you get anythong from that...
I fixed it by flashing a different Rom (kingdom 1.0) - This maybe coincidence and I might be talking rubbish, but it worked for me.

A possible alternative for MTP (on Windows): an adb-provider for Windows powershell

Posting this in the Galaxy Nexus forums, since this seems to be one of the few devices which right now has no mass-storage mode.
Everyone seems to hate on MTP, for both the right and the wrong reasons.
With MTP not really being very accessible from the command-line, I find myself using "adb shell ls", "adb push" and "adb pull" quite a lot. It works out OK, but it's not very fluent, especially for batch operations.
So I want something which does batch-operations fluently too. And since I know .NET, I figured a Powershell-provider should be doable.
I envision you should be able to do something like the following:
Code:
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\Users\josteink> cd ADB:
PS ADB:> copy \sdcard\*.* C:\backup\
etc.
So before I start wasting my time on this, I figured I'd poll the mood. Is anyone else interested in this, or is the Windows-crowd already feeling comfy with the tools they have?

I'm comfortable with the regular tools i have, and MTP is working fine for me.

A few may want it because of the issues that they have with MTP. Personally I prefer MTP over mass storage.

I think it would be a very cool experiment. The idea of getting access to files on my device opens up some neat scripting possibilities! My stupid Xoom also uses MTP.
Sent from my Galaxy Nexus using xda premium

im having some trouble installing the MTP driver for my galaxy nexus on Win XP
I tried PDANet for the phone driver but I can't seem to get the MTP to work properly on XP, n i couldnt find any driver for MTP. On the other hand, the driver installed itself on my other platform thats running Win7...

I just use adb with the push and pull statements as I always have. I never really used MTP or USB or whatever back in the days with my OG. I'm fairly certain however that the average user would not use adb however! (nor would they be on xda however!)

MTP works well enough on Windows and even on osx. Whenever I do use command line its fairly simple and batching commands up as needed is also simple enough.
I'm not sure there's huge value in another way to transfer on windows, but if its something you need, then just do it.
I think a more useful project might be a file manager that uses adb instead of mtp. You could add shell extensions to it too. Something like that would have a lot more broad appeal.

It's already been done: Droid Explorer
http://de.codeplex.com/

pascanu said:
It's already been done: Droid Explorer
http://de.codeplex.com/
Click to expand...
Click to collapse
Nice, but windows only again :/
MTP works well enough on windows, and support will probably only get better. Its other platforms that are a pain.

If you want, you can use AirDroid to manipulate your files on a Wifi Network!

jairmoreno said:
If you want, you can use AirDroid to manipulate your files on a Wifi Network!
Click to expand...
Click to collapse
I use AirDroid for media files. those non-media files or large data files, I prefer WiFi File Explorer PRO, which is better than AirDroid.

mingtaoh said:
im having some trouble installing the MTP driver for my galaxy nexus on Win XP
I tried PDANet for the phone driver but I can't seem to get the MTP to work properly on XP, n i couldnt find any driver for MTP. On the other hand, the driver installed itself on my other platform thats running Win7...
Click to expand...
Click to collapse
Do you have WMP12 installed?
I had a hard time finding XP driver for GN, and I once read somewhere that WMP12 includes the driver needed
I installed it then plugged in my GN, and after loading for a while XP recognized it as a MTP device and I can move files to and from GN
Hope it works for you
Sent from my Galaxy Nexus using Tapatalk

Not done yet, not by any means, but I have started.
Following is a screenshot of actual running code
The syntax will become better after a while. Just for now I'm working on bolting the technical bits together and learning how Powershell components are built

momomok said:
Do you have WMP12 installed?
I had a hard time finding XP driver for GN, and I once read somewhere that WMP12 includes the driver needed
I installed it then plugged in my GN, and after loading for a while XP recognized it as a MTP device and I can move files to and from GN
Hope it works for you
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm using winxp so I dont think I can install WMP12, but I have WMP 11 installed should I uninstall and reinstall it again?

Still quite a bit of way to go, but at least now "Get-item" parses stuff 100% correctly, and I have "ls" working too

After a bit more work (and learning some more powershell)
I now have rooted devices like (SDCARD) working correctly as well
Edit: It seems rooted devices act a bit wonky and should be looked into, but now I can add CD to the list of things working too.

So im guessing this is the reason i cant access my backed up apks on my sd card?

xzombiex66 said:
So im guessing this is the reason i cant access my backed up apks on my sd card?
Click to expand...
Click to collapse
Yeah. That doesn't work over MTP.

Post moved to new thread

Jumped in on this late-- looks like you decided to go forward -- I think there is a need for a powershell provider for MTP. ADB can get information to/from the device, but not in any way that powershell likes... It would be great to have the MTP system mountable as a psdrive. You can 'adb shell ls /sdcard/... ' but what you get back has to be captured and parsed. It's frustrating that MTP is a file system that can be browsed graphically but not as a true file system available to the entire OS (and the command line/powershell). Although I'm getting the impression from my reading elsewhere that the storage is entirely ext fs and Windows has never played nice with Linux-ish file systems.

Win7 64bit pc does not Recognize A100 tab

I have previously have installed drivers for 3 android devices and never had a problem except now. Neither my pc or my laptop (both win7 64bit) can recognize it. I've tried changing ports (could not change cables because I do not have an extra micro usb cable), I have installed and uninstalled several times on both computers. I've even tried to see if it ewas a compatibility issue with the 64 bit sytem but when I went into setup.exe properties there was not a compatibility tab. I bought this refurbished from Walmart so Acer no longer covers it under warranty. I did buy a 2 year extended warranty that I can use as a last resort.
Is the micro usb cable suppose to seat flat against the body of the Acer a100 or can you see a portion of the metal part of the plug? Also, should I be able to wiggle the usb plug back and forth. Any assistance with this would certainly make my day. I have been working with this for 2 days now.

I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium

[email protected] said:
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Yes, I did download from Acer. I finally went back and reviewed the paper work that came with Tab and found that the company that refurbished for Walmart has a 90 day warranty. I have emailed there warranty support service, hopefully I will hear something from them tomorrow. The only thing I have not tried is a different usb cable which I will pick up tomorrow at good old Radio Shack. If that does not fix the problem then the problem must be in the Tab. I have installed drivers for 3 other android device on the same pc's and never had a problem. Tomorrow is going to be a busy day for me. Dealing with this issue, going to the dentist and I am suppose to get the new Vizio Co-Star so I will be setting that up and then learning how to operate it and seeing what its potential is.

[email protected] said:
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Would it be possible to install clockworkmod and root and install the rom over wifi? I not sure how to do it but, I am sure there is someone that has done this before.

lartomar2002 said:
Would it be possible to install clockworkmod and root and install the rom over wifi? I not sure how to do it but, I am sure there is someone that has done this before.
Click to expand...
Click to collapse
Only if you have adb over network, which stock doesn't have, so no you can't do that, has to be USB.
Tapatalked from my Galaxy S II.

pio_masaki said:
Only if you have adb over network, which stock doesn't have, so no you can't do that, has to be USB.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Da*n, Oh well, back to the drawing board.

lartomar2002 said:
I have previously have installed drivers for 3 android devices and never had a problem except now. Neither my pc or my laptop (both win7 64bit) can recognize it. I've tried changing ports (could not change cables because I do not have an extra micro usb cable), I have installed and uninstalled several times on both computers. I've even tried to see if it ewas a compatibility issue with the 64 bit sytem but when I went into setup.exe properties there was not a compatibility tab. I bought this refurbished from Walmart so Acer no longer covers it under warranty. I did buy a 2 year extended warranty that I can use as a last resort.
Is the micro usb cable suppose to seat flat against the body of the Acer a100 or can you see a portion of the metal part of the plug? Also, should I be able to wiggle the usb plug back and forth. Any assistance with this would certainly make my day. I have been working with this for 2 days now.
Click to expand...
Click to collapse
I also have this problem with two Computers,Windows 7 64 Bit and Windows 8 Consumers Preview 64 Bit. Many Hours Lost trying but still unable to find a fix. It has to be a Security Issue possibly with an Exploit in the USB Driver Software. My Resolution was to Break Out the Old Trusty Dell XP Laptop. Copy and Pasted the Same Downloaded Files to a USB Drive and used them on the XP Laptop and in Less then 5 Minutes Successful Root !

Izzyb914 said:
I also have this problem with two Computers,Windows 7 64 Bit and Windows 8 Consumers Preview 64 Bit. Many Hours Lost trying but still unable to find a fix. It has to be a Security Issue possibly with an Exploit in the USB Driver Software. My Resolution was to Break Out the Old Trusty Dell XP Laptop. Copy and Pasted the Same Downloaded Files to a USB Drive and used them on the XP Laptop and in Less then 5 Minutes Successful Root !
Click to expand...
Click to collapse
I was at Radio Shack and bought a cable for $20.00, what a rip-off I could have gotten the same cable for $4.95 from Monoprice. Anyways that was the problem and now the pc sees the device.

You can download an Ubuntu Live CD for free, and boot from it without needing to reformat / repartition your hard disk. In other words you don't need to install it, just reboot run the commands you need, take the disc out, boot back to windows and done.
I put together this package that simply includes adb and fastboot, it will install them automatically and allow you to run them with ease.
Download here:
android-cmdline-tools.zip
Instructions:
Boot into your Live Ubuntu CD (or other distro)
Download the above package
Open your terminal emulator (i.e. Gnome Terminal, Konsole, Terminator, etc) do the following:
Code:
cd /tmp && unzip ~/Downloads/android_cmdline_tools.zip
*If you downloaded to a different location you need to correct the path, I used ~/Downloads as it is the typical download location on linux for Chrome and Firefox.
After the file is unzipped you should have the android-cmdline-tools directory in /tmp/android-cmdline-tools
Now lets install adb and fastboot:
Code:
cd android-cmdline-tools && sudo bash ./install-linux.sh
(may request your password if you are on a live cd then it shouldn't, however if it does leave it blank, otherwise you should type your users password)
This will prompt you to make sure you wish to install. Enter Y to install, any other key to abort
If this succeeds, you will now have adb and fastboot ready to run on your device
On linux you shouldn't need any special drivers for these tools to work with the A100 so this package is a small convenient download that is quick to install and use the tools, and should come in handy for usage via Live CD/DVD to access your A100 or most other android devices through adb/fastboot
Good luck and hope this helps!

linuxsociety said:
One quick solution would be to grab an Ubuntu Live CD download and reboot your computer into the Live installation, download the adb and fastboot files for linux. You usually can get them in packages aimed at flashing recovery so you don't have to download the entire Android SDK. Ubuntu shouldn't have a problem seeing your A100 without the need for any drivers or modifying any .ini files. This is an alternative, so that you don't have to wipe your Win7 install. just keep a Live CD for linux laying around, they usually come in handy!!
Actually now that I am thinking of it I'll just make a package named A100-cmdline-tools.zip that contains both adb and fastboot for both windows and linux. Maybe it will come in handy for some of you guys
Click to expand...
Click to collapse
Bought another micro usb cable and that fixed the problem. But I am going to use your suggestion and burn a Live CD to have around. Thanks

lartomar2002 said:
Bought another micro usb cable and that fixed the problem. But I am going to use your suggestion and burn a Live CD to have around. Thanks
Click to expand...
Click to collapse
edited that post, made a Linux android-cmdline-tools.zip package that includes both adb and fastboot and will install them for you. May be a handy .zip file to keep laying around for your PC, small size and easy for a quick download too if your on Live CD. I also have the Windows adb.exe and fastboot.exe files as well as the required .dll's in the zip, I just haven't made an installer for windows (yet - will be install-windows.sh) .

linuxsociety said:
edited that post, made a Linux android-cmdline-tools.zip package that includes both adb and fastboot and will install them for you. May be a handy .zip file to keep laying around for your PC, small size and easy for a quick download too if your on Live CD. I also have the Windows adb.exe and fastboot.exe files as well as the required .dll's in the zip, I just haven't made an installer for windows (yet - will be install-windows.sh) .
Click to expand...
Click to collapse
Where do I d/l from?

lartomar2002 said:
Where do I d/l from?
Click to expand...
Click to collapse
where it says download here, and then provides the link or I'll just provide it in this msg too: http://beta.androidfilehost.com/?fid=9390062577138008179

linuxsociety said:
where it says download here, and then provides the link or I'll just provide it in this msg too: http://beta.androidfilehost.com/?fid=9390062577138008179
Click to expand...
Click to collapse
Duh! Sometimes I can be so dense.