My problem is that my OnePlus One phone is not found in Eclipse on my Mac even after trying things like activating USB debugging of course and even Menu>Storage>menu on the upper right corner>USB computer connection>check box MTP/PTP.
When i try adb devices it tells me that there is no device found.
I have tried two different cables (including stock cable).
It seems that with mac there are no drivers to install needed.
Thanks a lot for any help.
Sebastien
Thanks a lot for your answer Jiang YD.
Finally, i have tried again with the same conditions few days later and Android file transfer recognized my OPO.
My OPO activated the Debug Mode automatically.
And the best is that Eclipse recognize my OPO for debugging.
So everything works well but i don't really undestand why it didn't worked the first time.
It works with the stock cable.
Related
I am have issues using the remote debugging feature of the Chrome Developers tools with my Android device (LG Nitro running Android version 4.0.4). It was working perfectly several days ago but now my device never appears on the about:inspect page.
I have followed and carefully considered these instructions including the troubleshooting tips. I have also searched for the answer to my problem but have not been able to find anything that works.
I am using Chrome version 35.0.1916.141 on my Android device and version 35.0.1916.114 on my PC (Windows 7). Neither says any updates are available.
Please note:
I have enabled debugging on my Android device and the small bug icon appears in the menu bar at the top of the screen when the USB cable is connected.
I have installed the necessary drivers for my phone on my PC.
Chrome is open on both devices
"Discover USB devices" is checked
I have tried restarting both the computer and my phone several times
The only thing I have changed on my computer since the last time it was working was to download 64-bit Java. Could this have any effect? If anyone has any input or ideas, it would be much appreciated!
Sounds like you may have gotten lucky. Next time this happens, try this:
1) Unplug your device.
2) Revoke USB debugging in the Developer Tools.
3) In the command line:
adb kill-server
adb start-server
Plug in device and accept fingerprint.
Voila, it appears in Chrome again. I went through a lot of pain with random problems with my Galaxy S5 not showing up, I was pulling my hair out for hours trying to figure it out.
Update: After launching my Android application from Eclipse on my device, it suddenly showed up on the about:inspect page. I am not sure why it was not recognizing my phone before but it seems to be working now.
Hi I'm trying to compile a Titanium Android app directly on my Nexus 7 (2013, SDK 4.3) device but I can't see any 'Titanium on Android Device' option in the Run Configurations.
My device is in Developer mode, connected to the USB, detected by Android File Transfer (Mac OS X 10.9, Titanium 3.1.4), detected by adb...
I tried to restart adb, restart Titanium, plug and unplug the device, but I still cannot see the option.
I also tested all this with Titanium 3.1.3, with no success.
I have no clue of what's happening :/ any help would be appreciated. thanks
It may sound stupid, but my friend had similar problems with his Nexus and he changed the USB slot to which he plugged his device and it worked.
Try using a different cable. Most cables are only able to load the device, somehow. Not every micro-USB-cable is capable of sending data, correctly.
Again a reason why I don´t like to work in the android environment. No one checks whether software and hardware is working the way it´s supposed to. That´s why I love Apples restrictive "closed" system. No 1000 viruses and other crap.
Well, that was a bit confusing but I finally found such option inside a Project Explorer menu...
I have a problem debugging apps on my Samsung Galaxy S3, (GTI9300, I believe this is also known as the international version) from Eclipse.
The thing is, debugging actually worked for a time and then it just stopped working. I've tried quite a few things to make it work again. I'll describe my whole experience briefly, to keep you from suggesting things I've already tried, and save us all some time.
When I first got my phone, debugging didn't work. When I plugged in my phone, the system detected it, and I could use it almost like a storage drive (using Media Transfer Protocol or some such thing) But when I started Eclipse and tried to debug, the debugger didn't see the phone.
I googled some, learned that I had to install some specific driver. I honestly don't remember which driver it was, but I believe it was an official one (from Samsung's website). Once I installed this driver, Windows would no longer detect my phone as a storage device. But the debugger did see it, and I was able to debug a few simple apps that I'd made. I could easily live with this tradeoff.
Then I got busy with other stuff and set Android development aside. I came back to it this weekend - after 2 or 3 months - only to find that it no longer works. No matter what I do, the debugger does not detect my phone (Windows still won't detect it either).
I tried all the first aid solutions like restarting Eclipse, rebooting my computer and rebooting the phone. Just for the sake of completeness, I do have usb debugging enabled on my phone.
The only major change of the whole setup that I can think of is that my phone's OS has recently updated. I don't know the exact version it was before, right now it's Android version 4.1.2 (Kernel version 3.0.31-1160235, if this is useful to anyone). I tried plugging the phone into other computers, it gets recognized as a media/storage phone. I can't install the Android development tools and try debugging on any of these computers - I'm stuck with the one I've got.
I've tried reinstalling the usb drivers for my phone. It didn't help. In desperation (and against my better judgement) I tried installing Samsung's software, first AllShare Control, and eventually Kies. None of it helped. When I run Kies, it gives me the option of connecting through USB or via WiFi. However it won't detect my phone when I plug it in. When I click "Troubleshoot connection" (or some such thing, unfortunately Kies decided to use my native language instead of English) it starts reinstalling the USB driver. This process takes quite a while, and fixes nothing.
I'm basically out of ideas, I don't know what to try next. Any help would be appreciated.
I think I have done everything right but I cannot get Eclipse to recognize my plugged in running Samsung Tab-2. Below is what I have done. What have I done wrong?
1) I have instelled USB drivers and can move files from the tablet to the Windows XP computer.
2) I have enabled USB debugging on the phone
3) I have been debugging on a virtual device then sending the apd files over email to my tablet and phone. That works fine. Obviously, I have enabled that on the phone.
4) I set up Eclipse to always ask what device to debug on.
5) I plugged the tablet into the USB slot and it is recognized by Windows.
6) I read the instructions Here
7) I click debug and am faced with a blank list of devices under "Choosing a running Android Device". My tablet does not show up.
8) I find myself at wit's end (adventure reference).
9) I ask for help on Stackoverflow.
I think you should take a look at this answer. An identical issue was accepted at that post.
Hope it works to you!
Try a different MicroUSB cable, I have seen this affect the device showing up in Eclipse, even if the cable is working fine for everything else (even transferring files to/from that specific device).
If nothing works you can use adb over wifi by calling : adb connect "your ip adress". I am assuming the Tab runns Android ICS. You can enable Adb over wifi right under the USB debugging- menu point.
How many times have I called tech support and had them tell me to reboot windows? Well, the solution was to reboot windows. Nowhere in any of the installation instructions did I skip a step of rebooting but just thought I should try that.
I know this is a rather common question, but I tried all the solutions I found on other post and they didn't do the trick for me.
Basically, I have a Samsung Galaxy S, that worked fine with eclipse, so I was able to debug applications directly on my smartphone.
I tried 2 days ago since a lot of time, and the device is not recognized by the system, even lsusb can't find it.
I tried with a friend's smartphone, from a different brand, and it worked fine, so i guess it's something related to my smartphone, but I can't figure it out.
Debug is enabled on the phone, any other idea? My OS is Ubuntu.
You have to deleate the data where the debugs and the runs are stored
I don't know where it was because i had this problem last year.
But whene i deleted the data it works fine again
Edit :
Found it
C:\Users\UserName\.android
delete
debug.keystore
I guess Samsung Galaxy S drivers are not installed properly. Install pdanet software in your workstation while installing it will ask connect your mobile with usb then it will install drivers automatically. I think it will work for you. try this..From this link you can find the software