Related
Alright, so the issue is... I have the SDK... and it won't work on either of the operating systems I run. I am running Ubuntu 9.10 and Windows 7, both 64bit. There are two main aspects I am after with it. Using DDMS to take screenshots and mess with stuff on devices, and the virtual Android system. On Ubuntu, DDMS comes up, but it shows my device as just ?????? and I am unable to do anything. I have already tried putting in the rules thing I found all over google, and it has done nothing. The correct IDs were in as well. On Windows, why I try to use it... it pops up with a command prompt screen for a split second and does nothing. On both Ubuntu and Windows, when I try to use a virtual device, all it does is crashes. This is with all different settings. So, is there anyone that can help me out with these issues? I just spent 3 hours of google searching to no avail. None of the fixes or anything I have found made any difference. Well... that's not true... one of them made DDMS not work at all... but that just needed to be restored. Any help would be appreciated. Thanks!
Update: Doesn't work on my gf's laptop which has Xp either... wtf DOES this run on?
I run the sdk on my win7 32 bit desktop. It runs in eclipse
So I'm getting worked up to do the apps to sd, got SDK installed on my PC. I have ROM manager installed and was on the edge of partitioning the SD card. Not knowing what I would lose if I did the partition (it wipes and formats the SD), I took a spare 2GB and cleaned it out. Empty. I powered off the Aria and installed the clean 2GB chip, powered up, and played with a few apps for a few minutes. I see no negative effects, in fact I see better performance. Assumed, anyway, in that my task killer shows more RAM available after a kill. The ignore list didn't change, so that is obviously in the Aria.
After tooling around, I checked the SD card using estrongs file explorer. Really nothing got added to the SD card.
I have followed this (http://www.youtube.com/watch?v=uVU8vQVKo6I) tutorial on the SDK ADB driver install...no luck. Windows could not find the driver. When I type "adb devices" I get no devices listed. Also, when I connected the Aria, and manually pointed the search to the "usb_driver" folder, it came up empty. I am in charge only and debugging is selected. (And rooted using Liberated R003)
Since I will need to use ADB in step 5 of http://forum.xda-developers.com/showthread.php?t=723483 I am stuck. At least I can pass the time by pulling out my hair wondering if the apps to sd is really worth it.
So I have messed with this a few times in the past two weeks and still no progress. I connect the Aria and no drivers found. I launch cmd and when I type ADB, I get android debug bridge 1.0.26. When I type ADB devices I get 'list of devices attached' but none are shown. I am in charge only and debugging is on. I type ADB shell and I get 'device not found.'
Apps to SD is a popular topic here, so can anyone help me figure out what I'm doing wrong or what I am missing? My internal storage is near max and need to do this.
Running liberated R010.
Sent from my (liberated) HTC Liberty using XDA App
Install HTC Sync. It includes USB drivers in the install. After it's installed just make sure it's not running. Then go through all the steps of connecting the phone and doing the "adb devices" command.
Will this HTC sync force any updates that would make changes to my ROM or root status?
No, it won't. Just make sure it's not running anyway (you could even uninstall it if afterwards if you want.) You're simply installing it for the USB drivers that are piggy-backed on the install.
I tried at least 3 installs of this HTC Sync and I am getting failures. HTC BMP USB Drivers install failure. I continued installation anyway. Hope that isn't what I needed.
Edit: launched Sync, selected Sync on the device. Aria says umable to find HTC sync on the PC. (But I got the desktop shortcut and Sync launched, which says "No device connected.") I deselected debugging and reconnected, prompted me to find drivers, which weren't found.
Progress! At least in that I had a successful HTC sync install on my 32 bit Vista notebook....more update later.
Sent from my (liberated) HTC Liberty using XDA App
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.
I keep encountering a problem when I try to connect using PC MODE. The driver never installs any which way that I try. Reinstalling drivers restarting computers... blah blah blah. I have tried different roms and they all have the same problem. It seems that only the stock rom works with the existing drivers. Does anyone else have this issue??? Any Help???
I recommend looking around for the drivers. They can be found all over the forums and the internet. I'll see if I can locate them and post a link.
Sent from my DROIDX using XDA App
If there are different drivers than the original ones I would appreciate the link. Thank you in advance.
zillahakzor said:
I recommend looking around for the drivers. They can be found all over the forums and the internet. I'll see if I can locate them and post a link.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
this needs to be in general
btw: try taking of usb debugging before connecting it in pc mode
Tried that already and I still have the same issue. Come on.. I can't be the only one out there with this problem. Also why should this be in "general" when it pertains to running custom roms. It's not like I am asking about how something works.
I think this is a legitimate issue with running custom roms i which i am surprised no one has addressed. Its not like I have not searched the forums. So if this problem is resolved then show me the sticky please!!
Funnyface19 said:
this needs to be in general
btw: try taking of usb debugging before connecting it in pc mode
Click to expand...
Click to collapse
Takiyon said:
Tried that already and I still have the same issue. Come on.. I can't be the only one out there with this problem. Also why should this be in "general" when it pertains to running custom roms. It's not like I am asking about how something works.
I think this is a legitimate issue with running custom roms i which i am surprised no one has addressed. Its not like I have not searched the forums. So if this problem is resolved then show me the sticky please!!
Click to expand...
Click to collapse
General because i just hooked mine up perfectly on windows using pc mode running liberty 1.5 therefore it isnt the ROM's fault making ANDROID development the wrong forum choice
try here
and read this and the following comments
also restart your computer and keep pressing F8 until a menu comes up press arrow down and click the one about not requiring signatures for drivers
Funnyface19 said:
this needs to be in general
btw: try taking of usb debugging before connecting it in pc mode
Click to expand...
Click to collapse
Agreed and done.
Thanks for the help guys. I'm not trying to be a ****. I will give it one more shot. At this point I don't know what to do. I have been pulling my hair out. I wanna use the liberty 1.5 rom but without the ability to dock my phone in PC mode it will be of no use.
Takiyon said:
I keep encountering a problem when I try to connect using PC MODE. The driver never installs any which way that I try. Reinstalling drivers restarting computers... blah blah blah. I have tried different roms and they all have the same problem. It seems that only the stock rom works with the existing drivers. Does anyone else have this issue??? Any Help???
Click to expand...
Click to collapse
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
well i turned off debugging. and nothing turned it on and nothing. Tried the drivers from that link that you guys posted and same thing. Could it be that I am using Windows 7? It's a clean install of Liberty 1.5 and I uninstalled the newer 4.8 drivers and installed the 4.6 drivers from the link. Restarted and still nothing. What am I doing wrong? if I restore my ROM back to the original stock everything works fine and I can sync with windows media and all that. The other way is a nogo. Help?
kdkinc said:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
Click to expand...
Click to collapse
The information below is what comes out of the event viewer. Maybe it is just a windows error. But after uninstalling and reinstalling the drivers why would it not work? Do I need to start deleting crap? I will try to install on another PC see if I have the same issue.
Edit--- Just tried it on another pc with a Fresh install if windows 7 x64. Installed drivers and same issue as below. What is so special about the stock ROM that allows the driver to function. is there an apk that the custom roms are missing? something must communicate with this driver and allow it to initialize. HELP!??
Log Name: System
Source: Microsoft-Windows-DriverFrameworks-UserMode
Date: 2/10/2011 4:14:44 AM
Event ID: 10111
Task Category: User-mode Driver problems.
Level: Critical
Keywords:
User: SYSTEM
Computer: TRAVELDESK
Description:
The device MTP USB Device (location MB810) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DriverFrameworks-UserMode" Guid="{2E35AAEB-857F-4BEB-A418-2E6C0E54D988}" />
<EventID>10111</EventID>
<Version>1</Version>
<Level>1</Level>
<Task>64</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2011-02-10T09:14:44.126129800Z" />
<EventRecordID>14712</EventRecordID>
<Correlation />
<Execution ProcessID="1028" ThreadID="1456" />
<Channel>System</Channel>
<Computer>TRAVELDESK</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<UmdfDeviceOffline lifetime="{3DA815A7-8803-4B06-936F-03E4D74D1746}" xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/DriverFrameworks/UserMode/Event">
<DeviceInfo>
<FriendlyName>MTP USB Device</FriendlyName>
<Location>MB810</Location>
<InstanceId>USB\VID_22B8&PID_41D8&MI_03\6&321BCAFE&4&0003</InstanceId>
</DeviceInfo>
<RestartCount>5</RestartCount>
</UmdfDeviceOffline>
</UserData>
</Event>
im not exactly sure whats wrong with just usb mode? you can move files on and off it fine and if anything is wrong it is probably some drive/code that is written in with blur/bloat that is removed, idk if it is just saying, maybe you can revert to stock delete moto drivers hook ur phone back up let it install and then root and maybe itll work then
I think you are on the right track. Considering that when I restore the stock rom from backup everything works fine. Drivers install and I can sync my music. Perhaps there is a part of blur that we can put back to fix this issue. I will experiment by taking the blur apks and installing one by one see how far I get. If anyone any better ideas please let me know.
Sent from my DROIDX using Tapatalk
Possible Solution - Help Needed
I think I may have stumbled onto something. While running the stock OS I disabled the StorageMonitorService.apk by renaming it and rebooting. Afterwards I get the same results. I think this apk controls/talks to the MTP Drivers. How do I get this apk from the stock rom to install on the liberty rom. How do I make sure it runs on startup. If this works I think we will be able to put it into all of the AOSP roms. I know it is one of the blur apps but for the extra functionality hardware wise I think it would be worth it. Has anyone even thought about doing this? If not then why?
Also another work around is to use Linux cuz it doesn't need any special drivers lol
Sent from my DROIDX using XDA App
I wish I could. Hard to break away from windoze. got too much invested in it.
Sent from my DROIDX using Tapatalk
I suspect you have the same problem as I do...there doesn't appear to be a 64 bit diag mode driver for the Droid X. If u try this on 32 bit Windows it will likely work.
Sent from my EVO on Cricket using XDA App
I'm so confused here, what seems to be the issue again? LoL. OP- you want to hook up PC mode from your phone but your computer seems to not want to. At least that's what I have gathered from all the posts and no one has suggested the Moto drivers lol
Motorola Drivers; every computer needs them for their Droid X to communicate properly with their PC. I use Moto Connect and why? Because any Motoroa device you hook will be auto-updated once the program is opened up and it also keeps all the drivers up to date.
Download Motorola 4.9.0 Driver with MotoConnect, download it, run the middle option on the bottom left hand corner and you should be all done. Your phone should now sync with your PC. I have used this with 32 and 64 bit Windows 7 computers. All older Windows based OSs' should work fine.
If that does not work, without reflashing the maderstock .340 and starting with a clean slate, the problem might be easy or hard to diagnose both pc and phone side.
Same here!!!!
I'm definitely encountering the same issues. I have installed the latest Motorola 4.9.0 drivers and even doing cleans and reinstalls to no avail.
What's even more odd is that I had recently replaced my phone because of rebooting issues. When I first got it and ran stock... no problems, it would install MTP just fine on both my desktop and laptop both running Win7x64. Once I restored a nandroid to my customized Liberty v1.0... it goes sour.
I even recently reformatted my desktop on a fresh install of Win7x64 and the problem occurs right away after installing the 4.9.0 drivers.
I'm pretty sure that it has something to do with the version being .340 since it only appeared after that. And possibly with ROMs that are based on .340.
I'm going to try Liberty v1.5 to see if it fixes it.
Ok I have found out that there is something in the blur stuff that is part of the stock rom that needs to be running otherwise the drivers on the pc side will not initialize. I have tried liberty 1.5 and it does not work however apex rom seems to have it working. I guess apex may solve me problem. Also for those that keep suggesting that the drivers are the issue. I appreciate it but that is not the issue when using custom roms. The issue is the blur software on the phone. It seems that you need some parts of it to make sure the phone hardware works 100%
If you want to test for yourself take the stock rom and disable blurstoragemanager.apk I think its called the motorola storage manager.
Sent from my DROIDX using Tapatalk
windows 7 64bit
have sum how rooted and installed magnus rom on my transformer...though the drivers show not installed...every time i turn it off and back on i get the installing drivers and it fails every time...really confused by this...device manager also shows mtp driver not installed with the exclamation point...but low and behold i am running a custom rom...does this sound rite ?
i get this all the time, also running win 7 64x, I don't know what the cause if it is...possibly poorly written drivers. I sometimes get this with my nook drivers and rarely with my evo drivers.. it happens quite frequently with my transformer. Mostly also the atb drivers..I wonder if I do a update with my windows will it help for the driver support or could it be my avg anti virus conflict possibly? I also might wonder if I install my service pck will it help. With 3 tablets and my phone..I rarely am on my i7 anymore.
make sure youre using 64 bit drivers, 32 bit drivers won't work on a 64 bit OS.