Hi all,
I have downloaded Android SDK and the Eclipse plugin under my Win7 Ult.
The problem that I am facing is that Eclipse is unable to deploy any app that I create. I have tried the same under Ubuntu and it was working fine.
After couple of hours of inspection I noticed that the adb doesn't recognize my emulator when running my app using Eclipse.
After closing eclipse and killing all the related SDK tools I started the adb process then started the emulator. Still the adb doesn't recognize my AVDs that are running through the emulator.
Now when I first run the emulator and then start the adb process then adb would recognize the emulator.
So did anyone faced the same problem??
Any help appreciated
I'm having the exact same problem.
Downloaded Eclipse. the sdk. avds. and everything else. have read every single other thread about this issue that is online. I'ts been 5 hours trying to find a solution.
is there an area in the preferences that specifically dictates app to avd transfer options? there has to be!
so what is it please?
any help appreciated.
I am trying to get a development environment setup and running into all sorts of problems with ADB when I have an actual device attached to the system. I am using eclipse and can use the emulators with no problems, until I attach an actual device to the system. At that point, even when trying to debug on the emulator, ADB keeps crashing. I can start a debug session on the actual device, but if I try to switch to the DDMS view, ADB crashes.
I am running on windows 7 and have even go so far as to do a complete reinstall of the system and only install the development tools only to have this problem show up again. I can't believe that this is normal, how could anything get developed with this type of issue?
I have been searching for answers and not been able to find anything helpful. I restart ADB only for it to immediately crash again. All the software is updated to the most recent versions. This problems occurs on both my desktop and laptop so don't think it is a hardware issue with my systems. Only thing really in common is the device, my EVO.
Any help would be appreciated. This is driving me nuts. I need to get this working for some projects but I feel like I am pounding my head on a brick wall trying to get it to work.
If this isn't the best place for this thread, could you please point me in the right direction? Thanks.
First navigate to where adb is located within cmd prompt.. [depends on what tutorial you followed if any at all] Either C:\android-sdk-tools\tools or if you used the .exe installer then itll be in your Program Files\android\android-sdk-tools\platform-tools\.. when you are in the directory of the adb location in cmd prompt runt the following code.. "adb devices" to see if adb is working at all.. it sounds like it might be a ROM issue unless adb is missing files it needs which i ran into that problem.
jr10000 said:
First navigate to where adb is located within cmd prompt.. [depends on what tutorial you followed if any at all] Either C:\android-sdk-tools\tools or if you used the .exe installer then itll be in your Program Files\android\android-sdk-tools\platform-tools\.. when you are in the directory of the adb location in cmd prompt runt the following code.. "adb devices" to see if adb is working at all.. it sounds like it might be a ROM issue unless adb is missing files it needs which i ran into that problem.
Click to expand...
Click to collapse
ADB is working fine like this. My phone shows up in the devices command. I can shell to it. Push/Pull files. All with no problems. It's not until I try running a debug session from eclipse (either in the emulator or on the device) that it crashes.
No one here that can help?
To the best of my knowledge, you either use the Emulator OR the phone.
At least that's what I do. Before I plug in my phone, I shut down any Emulator(s) that I might be running.
Also make sure to eject phone (Mac) or stop the device (Windows).
Never had a problem.
Rootstonian said:
To the best of my knowledge, you either use the Emulator OR the phone.
At least that's what I do. Before I plug in my phone, I shut down any Emulator(s) that I might be running.
Also make sure to eject phone (Mac) or stop the device (Windows).
Never had a problem.
Click to expand...
Click to collapse
The problem is I can't use EITHER when the phone is connected. So even if I wanted to debug on the phone, I can't.
i have the same problem, and it drives me crazy, i can't get a specific reasong, once i uninstalled google upadter and the adb works fine, second time i uninstalled Google chrome and it work fine until yesterday, today it is back to crashing, i dont know what else to do
Edit: my problem started after upgrading to android 2.3
NoEnd said:
i have the same problem, and it drives me crazy, i can't get a specific reasong, once i uninstalled google upadter and the adb works fine, second time i uninstalled Google chrome and it work fine until yesterday, today it is back to crashing, i dont know what else to do
Edit: my problem started after upgrading to android 2.3
Click to expand...
Click to collapse
I have pretty much given up on getting it to work right. I have a linux box that I set up the development environment on and it is working fine there. I'm thinking it could be something with 2.3 also. Going to see if I can find the 2.2 and do the setup with that.
edboston said:
I have pretty much given up on getting it to work right. I have a linux box that I set up the development environment on and it is working fine there. I'm thinking it could be something with 2.3 also. Going to see if I can find the 2.2 and do the setup with that.
Click to expand...
Click to collapse
Try going into your sdk/tools folder and setting adb to run as administrator, expecially for win 7 (leave it open then go back to eclipse). I had the same problem and I also closed the emulator when debuging on the device.......don't know, but maybe it will work for you also. Good luck!
awrnsmn said:
Try going into your sdk/tools folder and setting adb to run as administrator, expecially for win 7 (leave it open then go back to eclipse). I had the same problem and I also closed the emulator when debuging on the device.......don't know, but maybe it will work for you also. Good luck!
Click to expand...
Click to collapse
No luck. Eclipse reported it couldn't run adb because it needed elevated. Thanks for the suggestion.
yeah tell me when ever found a soultion for the problem, it seems that it's a small problem
is your windowsOS 64??
NoEnd said:
yeah tell me when ever found a soultion for the problem, it seems that it's a small problem
is your windowsOS 64??
Click to expand...
Click to collapse
Yes it is. But I do have the 32bit version of all the development system. I have an extra drive on my system that I can try installing the 32bit version of Windows 7 on and see if I have any better luck with that.
edboston said:
Yes it is. But I do have the 32bit version of all the development system. I have an extra drive on my system that I can try installing the 32bit version of Windows 7 on and see if I have any better luck with that.
Click to expand...
Click to collapse
please do and reply back
NoEnd said:
please do and reply back
Click to expand...
Click to collapse
Just tried running it on 32bit windows. Same problems. ADB crashing.
edboston said:
Just tried running it on 32bit windows. Same problems. ADB crashing.
Click to expand...
Click to collapse
there must be a problem with the phones???
mine is Desire HD
Rom Revolution HD
NoEnd said:
there must be a problem with the phones???
mine is Desire HD
Rom Revolution HD
Click to expand...
Click to collapse
I had someone suggest it could be a custom rom or kernel issue. I am running an evo with a custom rom and kernel. I'm not sure where the adb part is implemented but I might be able to try stock later this week. Strange that it works fine on my linux box with the custom. Probably the linux version of adb is more robust and can handle the errors better.
I'm having similar issues on Windows 7 32 and 64 bit. I'm using the 2.3 tools.
The interesting thing is that ADB only crashes when I try to run (not debug) one particular application (one I wrote) inside Eclipse. I have 3 other projects that work just fine, no crashing.
Even with the one app, it starts out working ok, then it'll start crashing when I try to run it, and then it'll crash anytime eclipse is up and that program is running on the phone!
Completely wiping the data partition fixes it for a while, but that's obviously a crappy solution.
Wiping the Cache/Dalvik Cache doesn't do anything.
Wiping the data for the com.android.debugtool (is this even related to ADB? seems too coincidental) doesn't do anything.
Uninstalling, or just killing my app on the phone, stops the crashing, until the program is installed, or starts, again.
Turning off and on USB Debugging a few times seems to sometimes help, but only for a while.
Rebooting also can help stop the crashing for a while, but not every time.
I turned the logging in eclipse up to verbose, but I don't see anything in the console window that seems to offer any clues.
Is the problem with ADB, or with DDMS? (DDMS is what eclipse runs to do everything on your device, DDMS then calls ADB). Because without eclipse open, adb works fine. Or is it a specific command send to ADB through DDMS? Is there any way to find out exactly what DDMS is doing with ADB?
Does anyone know if there's another "debugging" cache on the phone somewhere that, if cleared, may fix the crashing?
Scott
edboston said:
I had someone suggest it could be a custom rom or kernel issue. I am running an evo with a custom rom and kernel. I'm not sure where the adb part is implemented but I might be able to try stock later this week. Strange that it works fine on my linux box with the custom. Probably the linux version of adb is more robust and can handle the errors better.
Click to expand...
Click to collapse
Okay. Tried it with the stock ROM/Kernel with the same results. ADB crashing.
Delvorak said:
I'm having similar issues on Windows 7 32 and 64 bit. I'm using the 2.3 tools.
The interesting thing is that ADB only crashes when I try to run (not debug) one particular application (one I wrote) inside Eclipse. I have 3 other projects that work just fine, no crashing.
Even with the one app, it starts out working ok, then it'll start crashing when I try to run it, and then it'll crash anytime eclipse is up and that program is running on the phone!
Completely wiping the data partition fixes it for a while, but that's obviously a crappy solution.
Wiping the Cache/Dalvik Cache doesn't do anything.
Wiping the data for the com.android.debugtool (is this even related to ADB? seems too coincidental) doesn't do anything.
Uninstalling, or just killing my app on the phone, stops the crashing, until the program is installed, or starts, again.
Turning off and on USB Debugging a few times seems to sometimes help, but only for a while.
Rebooting also can help stop the crashing for a while, but not every time.
I turned the logging in eclipse up to verbose, but I don't see anything in the console window that seems to offer any clues.
Is the problem with ADB, or with DDMS? (DDMS is what eclipse runs to do everything on your device, DDMS then calls ADB). Because without eclipse open, adb works fine. Or is it a specific command send to ADB through DDMS? Is there any way to find out exactly what DDMS is doing with ADB?
Does anyone know if there's another "debugging" cache on the phone somewhere that, if cleared, may fix the crashing?
Scott
Click to expand...
Click to collapse
your reply can be summarize in few points:
1- its a library or code you used in that app that crashes ADB.exe (as u said only this app)
2- it maybe an app in the phone, the apps i suspect is SU(for rooted phones) or Whatsapp(because it's runs a service that stops as soon as the USB mode activated)
i hope this Thread doesn't die, because it's the only one on the WEB.
One thing I checked between the v7 and v8 of the SDK is adb.exe is the same version in each of these. So the thought about the DDMB being a possible culprit is a good possibility. Because outside of eclipse debugging, I have no problems with ADB at all.
so i transferred my music from my laptop to my tab, but while looking at my music on the tab it all of a sudden exits and asks me to either force close or report. Anyone have any idea why this could be happening? I thought all was good once i got the files to tranfer, but then this happened...
could you try reproducing the issue with logcat running?
Sure, would you mind explaining how to do that though? Not wuite sure what logcat is... Appreciate all the help! Hope to get this squared away.
yeah, I figured I would have to do that but I hate writing out instructions just to find out that the person already knows everything I had to say.
I'll write this assuming you're using windows.. hopefully that's not a mistake
this may be a lot more work than you're willing to do and it may not give any useful results. you're certainly more than welcome to try it though.
for a much easier, but less helpful method, skip to the end.
first, install the adb driver. there is a link floating around somewhere to just the driver, but I can't find it so you're probably better off just installing samsung kies. this will install the drivers for you.
http://www.samsung.com/ca/support/m...softwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
then, you'll need to download the android sdk.
http://developer.android.com/sdk/index.html
download it, open the sdk manager and then let it install it's stuff. all you really need is "Android SDK Platform-tools, revision X." I believe the most recent revision is 5, but it doesn't really matter.
now, open a command prompt. in windows 7, you can just hit start and then type cmd. in xp or vista I believe if you have to use start->run or windows key + r, then type cmd and click run.
from here, change directory to the platform tools folder of your sdk. most likely something like this
Code:
cd C:\Program Files\android-sdk-windows\platform-tools\
though it will depend on where you installed your sdk
now go into settings->applications->development and check "usb debugging" on your tablet. after that is done, connect it to your computer with usb and type
Code:
adb devices
if something shows up, your device is recognized. otherwise.. ask for help, I guess
finally, type
Code:
adb logcat -c
adb logcat
and then try to reproduce the error. this will give you tons of information about what's going on in the system. hopefully, it will give you some idea why it is crashing.
Note: the "-c" will clear all previous logs
now, for the short version.
In the android market, download "Android Terminal Emulator"
attempt to reproduce the error then open the terminal emulator and type
Code:
logcat &
this will show you all logs since the last reboot, assuming you haven't cleared them with "logcat -c." It might be a good idea to use "logcat -c" before you start trying to reproduce the error.
hope that helps,
Sam
First of all cant thank you enough for trying to help out. So i went with the second option as to limit my chances of having to ask more questions...yeah about that. With option 2 i could not run the "logcat -c" and after reproducing the error and running "logcat &" i get a permission error... Ideas? Thanks again!
hard to say, man.. what does the error say exactly?
Thanks to vbrtrmn's post about his problem on the Q&A forum, I realized I lost the use of SU with todays update. I don't know why (maybe someone else can shed light on this or if this), but it did more than just that, it also broke ADB!
I don't know much about ADB so I am approaching this with limited knowledge, but I hope it helps. I do not take responsibility for any problems you may have!
Also please note that these are not instructions on getting adb and su working from scratch (although they could easily be adapted to do so)
OK! So after some messing around, I was able to get ADB and, in turn, SU working again.
First thing you'll have to do is plug the OUYA into your computer via USB and delete all the OUYA drivers from your Device manager. From what I could tell, the OUYA stopped showing up as an Android Phone ADB Composite device (hence the ADB problem). After you delete the drivers, unplug the OUYA and then follow steps 5-12 (windows) on this website: https://devs.ouya.tv/developers/docs/setup .
Once you get to step 13, you don't actually have to hit the Have Disk button, just select ADB Composite Device from that screen (it appeared for me, may not for you, you might have to follow their directions). This will take you to step 14 and 15 on that webpage.
After that is done, then head over to the original instructions on this forum, found at: http://forum.xda-developers.com/showthread.php?t=2272266
The only thing you should have to do is step 4 under HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES, assuming you already have the files in place.
This SHOULD give you access to SU and any apps that require it once again. To check, go to Make on your OUYA and open the Superuser app. If it asks for root permission, it worked.
The only problem I ran into is that the OUYA is now only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know) on my computer. Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
Again, I know very little about the drivers, adb, and/or su so if I got anything wrong, please let me know!
EDIT: Make sure to try hard resetting the OUYA before trying this. While it didn't work for me, that's what fixed vbrtrmn, but he was not on Windows.
JLCollier2005 said:
EDIT: Make sure to try hard resetting the OUYA before trying this. While it didn't work for me, that's what fixed vbrtrmn, but he was not on Windows.
Click to expand...
Click to collapse
I was using a Mac .. Hard boot both the OUYA and Mac, seemed to fix my issue. Not sure why exactly, killing adb should have done it, oh well.
The OTA update did wipe out my settings in build.prop for wireless adb.