Develop Reference

OnePlus One not found in Android Studio on Mac

I have a strange problem while developing in Android Studio on mac and i am using OnePlus one. While debugging if a call come on my mobile adb disconnect my device and don't show it again. Help me to solve this permanently.
Only solution that i have found and which works is in following step:
Restart mac
disconnect cable from mac and OnePlus One
Kill adb server
start adb server
Revoke developer certificate and turn off developers option.
restart onePlus One
Turn on OnePlusOne and connect device with mac
Open Android Studio
Enable developer option and then enable debugging option
After I follow these steps, fingerprint dialog show and once I allow that dialog, device starts to show.
This process is time consuming. I am facing this problem on mac.

Putting the phone in airplane mode seems to have temporarily fixed the issue for me. I still need to look at the logs and figure out what is wrong, but there seems to be a bug in the latest 5.x updates for the OPO.

Are you using EasyTether? If yes, you can disable it by using the following command:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
If that does not work, open System Information utility and check your device manufacturer ID (Vendor ID). Copy that and paste it into your adb usb config by using
echo 0x9d17 >> ~/.android/adb_usb.ini
Then restart your macbook and mobile phone and try if it works.

There are several reasons your phone may not be getting detected properly, in my case it showed my phone in My Computers, and also asked me if I allowed my PC to debug on my phone. Yet it wasn't showing the phone in the android studio adb devices drop down menu.
All I did was, go to
Tools>Android>Enable ADB Integration
and it found my device. This is once I had installed my OPX driver that shows as a disk in My Computers and also Samsung USB driver. I'm talking about Windows here but the solution applies to Android Studio on any platform. So thought I should share.

No active compatible AVD's or devices found. --- getting this message only for SAMSUNG Devices

I am new in android development. I have downloaded Android SDK + eclipse. and did the settings as mentioned here. I am using two mobile sets i) Micromax canvas A11 and ii) SAMSUNG Galaxy S3. For Micromax it is working properly. I can able to run my hello world application in micromax. But same app is not working in SAMSUNG. It gives me this error message
[2014-06-09 13:03:14 - SamsungOne] No active compatible AVD's or devices found. Relaunch this configuration after connecting a device or starting an AVD.
what to do... please help. And I have to develop application for SAMSUNG S3 only. And I referred other posts of stackoverflow. but getting the same error.
In device manager it is showing like this ....

If you want to run your applications in samsung mobiles you need to install samsung kies in your PC. Download kies from here
Some devices will automatically installs device drivers in your pc when you connect to pc but some are not. So that is why we need to install pc sync to test our applications.
To enable USB debugging (only for Android v4.2 and above) :
Go to Settings → More → About Device Scroll down to Build Number Tap it repeatedly (tap 7 times). See the Developer options menu under Settings → More
See this video for installing kies and this for enable debug mode.

Please Enable your Debuging mode on in your device,
To Enable to debugging mode >> go to Developer option in settings
And Download Samsung-Andorid-USB-Driver from here
http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
Hope it will worked for you

My Samsung is an honest piece of.... er, brick, considering it doesn't even properly connect to USB anymore. Beforehand, when it didn't think it's charging when it isn't, and think that my computer is a car dock; I had to manually link it to the PC so that it would be detected. The way you do that is by downloading the drivers, specifically this one: http://forum.xda-developers.com/showthread.php?t=2645355
What also helped was installing these drivers using the command 'pnputil -i -a filename.inf'
http://forum.xda-developers.com/showthread.php?t=1514942
And what you need to do is, restart your computer, then when you plug the device in, it will detect it as an UNKNOWN DEVICE because Samsung Drivers are terrible. When this happens, go to Control Panel -> Device Manager -> Other Devices -> Unknown Device -> Update Driver Software -> Browse my computer -> Let me pick from a list -> See all drivers -> Samsung -> select the one for usb phones.
That should fix the problem. KIES never helps.

Got it..
In your mobile Goto
Setting -> About -> (touch on Build Number 7 times continuously) -> then come back to Developer Option -> Enable USB Debugging
USB Debugging option was not coming for me. Above Android v4.2 they have hidden USB Debugging option.
Got this from youtube

Win7 x64 Bluecove

I'm trying to use Bluecove for an application I'm writing. Version 2.1 of the jar didn't work, so a little Google showed me that it had always had issues with x64, so I turned to the latest 2.1.1 "snapshot", and I still get that the bluecove_x64 dll is missing. Am I doing something wrong, or should I just look for another API?

I encountered this problem after installing a vendor's bluetooth stack and management utilities. My java app which used bluetooth worked fine before this, after the install I got the bluecove_x64.dll not found error. After much searching, I reverted to an earlier system checkpoint (before I tried installing the "newer" bluetooth) and all was back to normal.
On another system, the toshiba bluetooth software had already been installed. I did a system checkpoint (in case the following was to not work), then went into the device manager, and uninstalled every "device" under bluetooth. Be sure to check the "delete driver software" box too, or they will come right back.
After this, the bluetooth device will appear to be gone. Go to the top of the tree, right click, and do "scan for hardware changes". This should install the Microsoft generic bluetooth drives which then work (for me) just fine on Win7_x64. If this doesn't install them, then you may try searching for a download, or another stack.

Why can't OSX detect android Galaxy S for USB debugging?

I searched for similar questions on this issue but found none related to Mac OSX.
Situation:
Trying to test android apps on a Galaxy S (Details below) but Mac is not detecting the device. Tried all the things below and have wondered whether this might be a driver issue (which I've heard things about for Samsung USB debugging).
Questions:
1) Are samsung drivers required for android USB debugging?
2) And are they available for Mac OSX?
3) Any other reasons OSX might not detect device for usb debugging?
Things I tried:
Enabled USB Debugging # Settings >> Applications >> Development >> USB Debugging
Enabled Tethering # Settings >> Wireless and network >> Tethering >> USB
Tethering
Set Tethered mode # Settings >> USB connection >> Tethered mode
Attempt to detect devices via ./adb devices (from platform
tools dir)
Verified that "Unknown Sources" is checked # Settings >> Applications >> Unknown Sources
Verified that device is connected to Mac
Restarted phone
Restarted mac
Added various device / product ids to adb_usb.ini
Did ./android update adb (which does adb kill-server / start-server)
Using:
Samsung Galaxy S (4G) with Sprint
Mac OSX 10.6.8
Eclipse Classic 3.7.1

Have you tried connecting the phone using a powered USB hub? I haven't tried it yet but found this blog post that suggests it may help for Samsung Galaxy devices.
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/

Go to Tethering select and then deselct USB Tethering and you are done.
this worked like a charm.

make sure that you plugin your device in the usb ports on the mac itself, not on the keyboard usb-ports.

Well I tried all kind of stuff for a phone that was working yesterday but not today. Finally replacing the cable between the phone and my mac solved the issue.

USB driver problems happens under Windows.
For MacOS, I had nothing to do : ADB found my device.
You don't need tethering : it's for sharing an Internet connection.
USB Debugging is needed. Also make sure you authorize your Galaxy to use Unknown sources (# Applications -> Unknown sources (it's a check box)).

This happens all the time with lots of phones. Two things that have worked for me are (1) type "adb kill-server" at the command line, or (2) try another cable.

This may sound crazy, but I tried every suggestion on this page except what finally worked:
Use the Samsung USB cable that comes with the S7 (my S6 cable worked too)
Every other USB cable I tried did not work. I don't know exactly why (USB 2 vs 3?), but that is what worked for me.
Of course, make sure USB debugging is turned on, and yada yada yada, but I did all that and still NOTHING. The moment I plugged in the USB cable that came with my S7 I got the RSA fingerprint message, and confirmed USB debugging, and the device showed up in Android Studio when I clicked Run.
HTH
--jsp

Go to
Settings
Wireless and Networks
USB Utilities
Detach the USB cable
Select Connect Storage To PC
Reconnect your USB cable to your phone.
Source: Galaxy S II Forums - Help, Mac won't recognize my galaxy S 2

This is what worked for me on Samsung Duos:
Go to settings > More > About device(at the bottom)
On that about device screen go to bottom and touch 6 times on the "Build number" (un till it doesn't display any notice)
Then visit again to settings > More and it will display developer options before the about device. Click on developer options and tweak options as you need.
Now on the mac, click on run button in android studio, it will display the connected device.
Resource: http://www.geekygadgetworld.com/3303/enable-developer-option-samsung-galaxy-grand-duos

I spent a night fighting this problem with my Doogee DG350, which runs the Chinese MTK chipset which has issues with USB on OS X. I found the solution was to run ADB in TCP/IP mode and then connect wirelessly:
adb tcpip 5555
adb connect 192.168.1.10:5555
adb devices
it's actually a bonus, cos you can dispense with the USB cable and debug wirelessly. Not looking back

None of these things worked for me. I'm running 4.4.2 on an LG VS450PP, trying to connect to a Mac laptop running OS X 10.10.5. Neither MTP nor PTP worked at all, even after following all the suggestions listed here and elsewhere on SO. I only got the RSA message when I chose the Internet option from the USB settings (and then I chose Ethernet).
After that, it was golden.

The connection via tcpip has a potential to work. However, the port 5555 is probably not available. I know this can work because I have an app on my Android called "Synctunes Wireless" which syncs' my itunes on my desktop wirelessly via tcpip and using port 4444. So I used the ip address and this port showing on this app and I can see this device in my Eclipse. Only thing is that the device type is unknown so the "OK" button is still disabled. So this has potential to work. Just have to find the right port number or maybe something else that is missing.

If anyone still has this problem and looking for a solution, what helped me is to install Smart Switch app. After that my Samsung device finally showed up

So i did some research because the same thing happened to me.
If the simple solution doesn't work you should check if you installed knox when you first launch your phone.
If you did install knox the only way for you to activate usb debugging would be to reset your phone back to factory config in order to deactivate knox (aka not installing it again), apparently you don't have the option to unistall knox on recent phones.

I know it is ridiculous but do make sure your phone's got a SIM card!

To activate the USB debugging on Samsung Galaxy S go to Menu -> Settings -> Applications -> Development -> Check "USB debugging".

Android Debugging with Eclipse on my HTC Evo: Augh!

I've turned on USB debugging. I have the latest HTC Sync and android SDK components. I'm using Eclipse 3.5 on windows XP. I'm running Android 2.2, and am asking for 2.1 as the minimum in the debugger. I work in Eclipse/Java just about every day, and have for several years. I'm even writing an Eclipse plugin at work as I type this.... neither Eclipse nor Java are new to me by quite a stretch.
When I start a debug session for the "Skeleton App" sample project, I can see my Evo, and the activity launches (with any freshly saved changes), should I select it.
BUT: my breakpoints are ignored, and logCat doesn't see my app's output(see comments below).
*W*hat a *T*errible *F*ailure (As the api so artfully puts it)!
(oh look... a formatting bug. Looks like bold text wants white space to function properly 10/15/2010)
I have tried different android connection types (charge only, disk drive, HTC Sync, and USB tethering) to no avail. I've tried Eclipse 3.6 for a bit before yielding to the inevitable and reinstalling 3.5. I monkeyed with the emulator for a while but ran into a different set of issues (I had to reboot the emulator every time I wanted to make a change... Eclipse's auto-build/hot-swap has me spoiled).
Is there something I can add to (or remove from) the AndroidManifest.XML to deal with this? A magical incantation perhaps? Must I pray towards San Jose three times a day on a rug woven from kernel gurus' vast and scruffy beards? Is my Evo not Kosher? Must I be "sky clad" while debugging? Shall I teach my laptop to genuflect?

Have you followed all the points from here ? You need to set a flag in the manifest and also enable debugging on the actual device.

I found the solution to the debugger issue. Google comes through again:
I found an IOException hiding in my DDMS log: Address family not supported by protocol family: bind
Googling for that, plus "android" turned up the answer in the first link. Windows Vista specifies "localhost" as ":::1", but android doesn't really support IPv6 yet. Changing localhost to "127.0.0.1" resolved the issue.
This is defined in c:/windows/system32/drivers/etc/hosts. I needed to run notepad "as admin" in order to save the changes.

I also have an HTC Evo 4G, and have been having the same debugging problems with Eclipse Helios (3.6). I just learned to use this debugger a day or two ago, and it worked fine. I noticed that there was an automatic Android OS update in the last day or two, also. Perhaps this is just a coincidence.
BUT - my beard was indeed scruffy yesterday, as you suggest, and the debugger was working. I've since shaved. Bad idea, apparently.
Butt seriously - I powered down both Evo and computer (HP running Vista), removed battery from both, then started over. Same result, that is, no debugging.