USB connection issues - android

I am trying to run my android app in my samsung device GT-S6012. I use Windows 7 Home Basic. The driver is installed properly. As soon as I connect the mobile using USB cable, for some seconds "adb devices" shows my phone. But then I get a message USB connection error, windows is unable to detect the device and USB is malfunctioning.
I tried uninstalling/re-installing driver, but no luck. I tried Google on this topic but nothing solved my issue.. Can Anyone let me know how can I fix it

windows is unable to detect the device and USB is malfunctioning
Highly unlikely. Unless your USB connector in your Samsung device is broken, USB cable is dead, or USB port in your computer is not functioning. If it's not, you can enable ADB to work with your device by doing the following:
Install the Samsung Universal USB drivers for mobile devices (which I assume you have done already).
If ADB did not ACK/started. First, open a command prompt (since you use Windows) at \android-sdk\platform-tools\ directory and type adb kill-server to kill ADB. Then, type adb start-server to start ADB. Finally, type adb devices to see if ADB has recognised your devices.
See here for a list of ADB commands you can use with Android.

Related

Why is the adb command not listing my device?

Lenovo A606
Android 4.4.2
OSX El Capitan
Developer mode is on
USB debugging is on
I already added the Android Tools Directory to PATH
When running adb devices on the command line, it just returns a blank list.
How can I make my laptop recognize my phone in order to test my code on a physical device?
If you find it out, let me know lol
There are so many possibilities. In order of importance:
Drivers are not installed for your device.
Even if the drivers are not installed, your USB port may not supply enough power to the device. Try changing port.
Even if the drivers are installed your USB Cable may be buggy. Try changing it.
Your ADB process may be not synced. Try with the following commands. abd kill-server and then adb start-server.
You may be running more than one adb processes.
Try restarting Android Studio / Eclipse / ...
Try restarting your computer.
Try cleaning the computer allowed to use your device from Settings and re-connect again your device.
Did you enable the developer mode and enable depuration?
Throw your computer, with USB cable and USB device through the window. Just kidding lol.
Possibly your usb cord is just a charger? When you plug in your phone can you see your pictures? If not maybe try a different connector.

Unable to connect to my android device via ADB

Sorry for the nooby question, I am having trouble sorting this out using the web.
I am trying to simply connect my device to my pc via adb to debug my application.
My device is rooted. Adb debugging is enabled. I downloaded an adb running application and started ADB.
Now i am trying adb connect ip:5555. and keep on getting "unable to connect to ip:5555" ...
Same happend when i try to connect via usb.
c:\>adb connect 192.168.20.191:5555
unable to connect to 192.168.20.191:5555
Help...?
EDIT:
C:>adb devices
List of devices attached
06fecaa1 unauthorized
Launching Cordova
Open Node.js / CMD
Point to "the directory where you have located your source folder" >>> C:\Projects\RJX
Enable Wifi
Turn on Developer Option under settings
Enable / Check USB Debugging Option under settings (Google if cannot find this option)
Enable / Check the MTP Option under settings (Google if cannot find this option)
ADB Commands
adb kill-server
adb start-server
//plug off cable from mobile and plug in again if you connected your device earlier
//Uninstall the application from mobile if you already installed. (if necessary)
adb tcpip 5555
adb connect "ip" //adb connect 192.192.2.128
adb devices //to check device details
cordova run android --device
if this steps are not worked, try to close the cmd and do it again. Sometimes it needs some refresh.
**Android devices version 4.0.4 and after should be no problem if you follow these steps.
I will assume you are able to understand adb connect / ip's etc I won't bore you with that
but there are two lame "gotcha's"
THE GENYMOTION GOTCHA
genymotion WRECKS a lot of this sometimes.. I am sorry but it does.. it has a "I know what I am doing I am taking over" mentality.. sadly it doesn't know what it's doing :-P often you have to turn off genymotion for the adb->usb to work.. basically connect phone FIRST ... make sure it's there in eclipse (adb kill-server / start server if needs be ), then AND ONLY THEN then genymotion AFTER
THE OOPS [/facepalm] GOTCHA
check that your phone it isn't in Windows merely as a "Camera" - go to My Computer and look. If it looks like this pic it's that you're not running Samsung Kies(/disabled because it's annoying) the phone still goes "blub bling" when you plug it in, it may be connected via wifi so have a LAN ip but it is NOT really "connected" to ur PC. instead run/download/update this (with phone disconnected) then make sure Kies is happy AND MAKE SURE MTU is enabled
This error happened to me when PC was (accidentally) NOT in the same network as Android. When I logged on Android to the same WIFI network as PC it now works perfect and I don't have this problem.
The answer here is that it's not listening on the correct (default) port. So you need to set the TCP/IP port to 5555. Connect your device via USB and issue the following command in cmd (terminal):
adb tcpip 5555
Following this your adb connect should work fine, e.g.:
adb connect 192.168.0.n
Hope this fixes it for you.
This happened when I was previously connected with one device (e.g. apps2fire) and then tried using adb command from another machine. I rebooted the Android device and then tried again and received the prompt to allow the connection as I would have expected.
First, check your ip address in your device, then following this command.
adb kill-server
adb tcpip 5555
adb connect [your-ip-address]:5555

Android adb is unable to find Teclast G18 tpad for on mac os

Android adb can't detect Telcast G18 tpad for mac os. I've run
adb kill-server
to stop the adb daemon and run
adb start-server
to restart the adb daemon. But still failed to make adb recognize it?
According to this discussion on the google group, I am trying to modify the adb_usb.ini file by appending the correspondance device usb vendor id.
But how can I know which usb vendor id should I use? Fortunately, I managed to google a list of vendors for usb drivers here, in which case here, the usb device vendor id is:
vendor TECLAST 0x071b Teclast
I faced the similar problem with Teclast P79HD tablet PC built on Intel CPU. My Windows7 desktop detected the tablet which was connect via USB as an unknown USB device and I could not update its driver. The only program that helped me to revive the tablet was Adb_Run_v.3.78.65 by Vitaly Shipilov. You can download this program anywhere in the Internet. It's free.
You should act in the following way:
Install Adb_Run_v.3.78.65 on your Windows desktop.
Restart your PC.
Click Adb Run icon to start the program, then exit from the program. You should start it to start adb server. After that you will see adb.exe process via the Task Manager.
Go to Setting of your tablet, then Storage -> USB computer connection (additional settings) and check 'Media device (MTP)' in 'Connect as' section. Then connect your tablet to PC via USB cable.
After that your PC will detect the tablet as Media device (MTP). You will see the unit in the Device Manager as Android Phone. Now you can transfer files but you cannot use the tablet in debug mode when USB is connected. To resolve this problem you should act as it is described on the page:
Configuring Your Android* USB Debug Connection
See the second half of this article 'To install the Android USB debug driver on Windows 7, 8 or 10'. The driver which helped in my case was 'Android Composite ADB Interface v.4.0.0.0 [23.05.2014]' by Google, Inc. And I checked 'Camera (PTP)' in 'USB computer connection' instead of 'Media device (MTP)'. After this procedure Android Studio began detecting my tablet right and I was able to use it in debug mode.

Android - adb tools not finding device

I just did a factory data restore so that I could use my phone for testing.
But now I am trying to use the adb tool to put a new .apk on the device using my usb, and it says device not connected.
The phone is displaying this message: MTP: server status: connecting to computer...
But it is never able to fully connect.
I tried to go to Wireless & Networks, and enable Internet pass-through, but that option is also "Turning on..." for the last 5 minutes.
Any idea why I am not able to connect?
What kind of device is it? Make sure you have the development USB settings set under Settings, Development. Also ensure it's not a USB Drive but in USB Debugging mode.
Furthermore, if it's a device driver issue, here is an article for the HTC Thunderbolt and Windows/Eclipse:
http://www.nodans.com/index.cfm/2012/2/1/Getting-USB-Device-Drivers-Working-for-HTC-Android-Development
For OSX, Motorola has a USB Link DMG, I'm not sure about HTC though.
Maybe you show give us more information, like
What OS are you using (Windows, Mac, Ubuntu)
Is USB debugging switched on?
Did you restart the adb server
$ adb kill-server
$ sudo adb start-server
* daemon not running. starting it now *
* daemon started successfully *
$ adb devices

Debugging in Android device over wifi without rooting [duplicate]

This question already has answers here:
Run/install/debug Android applications over Wi-Fi?
(41 answers)
Closed 6 years ago.
Is there any possible way to debug or run android apps from eclipse to my Sony Tablet S over wifi rather than USB without rooting the device?
There are ways to do it, if the device is rooted. However, I am seeking the solution in a device that is not rooted.
Disconnect device from usb then tell it to listen on 4455
adb tcpip 4455
restarting in TCP mode port: 4455
connect to the device using a specified ip:port. my device is using wifi
adb connect 192.168.1.103:4455
connected to 192.168.1.103:4455
now do normal adb commands over tcp like
adb shell
when your done, you can put it back in USB mode
adb usb
restarting in USB mode
After a bit of dabbling with testing I successfully managed to connect a Sony Tablet S over ADB following this procedure, when both the computer and the tablet were on the same wifi network. I used an Xperia T as a tethering point between a laptop and the Tablet S. I followed the same procedure on an Xperia Tablet S and an Xperia S as well.
Connect the Sony Tablet S through USB to a computer, make sure you have ADB debugging enabled on the tablet.
On the computer, execute "adb devices", verifying the tablet is showing up in the list of available devices.
Execute "adb tcpip [port]" while the tablet is connected to the computer, verifying you get a response "restarting in TCP mode port: [port]"
Disconnect from the device from the computer it was connected to.
From a host located on the same wifi network, execute "adb connect [ip to device]:[port]", verifying you get a response "connected to [ip to device]:[port]"
In the end I launched Eclipse, created a test project and tried launching the project. The project installed and launched automatically from Eclipse. I also tested this for debugging and that worked equally well.
Finally After lots of search, here is the consolidated, short tutorial about "Wireless Debugging with Android without rooting" your android phone.
Steps:
Make sure your Phone and your PC/Laptop is connected in the same network.
Find your Android Device's IP Address: Go to Settings > About Phone > Status. Note down it.
Ping Test: Lets first check if your phone is accessible from your PC/Laptop to do this ping your Android Device and check its response. See Notes if ping is unsuccessful.
e.g: ping 192.168.1.55
Connect your Android Device Via USB in USB Debugging Mode.
Open command prompt and cd into <Android SDK Folder>\platform-tools directory and run the following commands.
adb tcpip 5555
adb connect DEVICE_IP_ADDRESS_HERE:5555
If you want to switch back to USB mode, use the following command.
adb -s DEVICE_IP_ADDRESS_HERE:5555
Disconnect Android Device from USB. If everything is fine, you can Wirelessly debug your Android Apps!
Notes:
If ping is unsuccessful, Make sure Wireless (WiFi) devices and wired devices are not isolated. If Isolated, you need to disable isolation. Router Mfgrs calls it as AP Isolation. There will be a setting in Router's Wireless Configuration page. I have D-Link Router, I unchecked the Enable MultiAP Isolation setting in Wireless Basic Setup Page.
I personally felt this method of connecting is taking more time.. so, I configured my android device so it uses static IP like 192.168.1.55 to connect to my router and I made a windows batch file like below,
#echo off
cd C:\AndroidSDK\platform-tools\
echo make sure your your Phone is connected in USB Debugging Mode.
pause
adb kill-server
adb tcpip 5555
adb connect 192.168.1.55
pause
so, every time I have just need to plug in my device, and double click the batch file and all done automatic :P !
(No root required) There is one best, easy and with UI method for Android Studio
IntelliJ and Android Studio plugin created to quickly connect your Android device over WiFi to install, run and debug your applications without a USB connected. Press one button and forget about your USB cable.
just install plugin Android WiFi ADB
Download and install Android WiFi ADB directly from
Intellij / Android Studio: Preferences/Settings->Plugins->Browse Repositories
.
Remember! for first time to initialize the device you must have to connect using usb
Alternatively, you can download the plugin from the JetBrains plugin site and install it manually in: Preferences/Settings->Plugins->Install plugin from disk.
for more information read here https://github.com/pedrovgs/AndroidWiFiADB

Categories

Resources