Wrong USB cable many hours lost !

Get Started | Login

Discussion Forums > Android Studio, Errors, Installing, Configuring

Replies: 1 Views: 71

Macker Aspiring developer Posts: 11 Reg: May 25, 2013 Clarecastle 7,610	confirm \| cancel 09/30/13 08:23 AM (12 years ago) Wrong USB cable many hours lost ! Yesterday I spent three hours trying to get my Samsung S3 to show up in the list of devices in Eclipse - had been working smoothly the day before. For some reason I could only compile/Run As on an emulator. All the phone settings were correct, such as 'allow USB debug'. In the Eclipse console I was getting the messages: Android Launch! adb is running normally. but then it was hanging on: Performing <appname>.BT_activity_root activity launch Much head scracthing ensued ... Finally, I recognised that the mircro USB cable hanging from the front of my PC had been changed by one of the kids - I swapped it out for the Samsung cable supplied with the phone and all worked ok ! The 'offending' cable was ok for charging the S3 and some communications with Eclipse but obviously has some slighlty different pin-ou (or I guess it could be faulty). NOTE-TO-SELF: As with all debugging, look for the simple solution first. Title Comments Yesterday I spent three hours trying to get my Samsung S3 to show up in the list of devices in Eclipse - had been working smoothly the day before. For some reason I could only compile/Run As on an emulator. All the phone settings were correct, such as 'allow USB debug'. In the Eclipse console I was getting the messages: Android Launch! adb is running normally. but then it was hanging on: Performing <appname>.BT_activity_root activity launch Much head scracthing ensued ... Finally, I recognised that the mircro USB cable hanging from the front of my PC had been changed by one of the kids - I swapped it out for the Samsung cable supplied with the phone and all worked ok ! The 'offending' cable was ok for charging the S3 and some communications with Eclipse but obviously has some slighlty different pin-ou (or I guess it could be faulty). NOTE-TO-SELF: As with all debugging, look for the simple solution first.

MacApple Apple Fan Posts: 4675 Reg: Oct 25, 2010 USA 61,150	09/30/13 12:30 PM (12 years ago) Good story! Swapping out always a good idea. Have lost hours in a similar fashion. Comments Good story! Swapping out always a good idea. Have lost hours in a similar fashion.

Login + Screen Name Required to Post Login to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.