I can load a device and run tests (load an app with the client) with Samsung Remote Test Lab, but I cannot get the Remote Debug Bridge to work with Android Studio.
adb connect localhost:xxxx says connected, but the device does not appear in Android Studio.
Has anyone gotten it to work?
The issue was Samsung themselves. Works fine now.
Related
I want to debug my Android app for some bug that happens only on some Samsung devices so I tried using Samsung Remote Test Lab.
But I want to debug using adb or Android Studio and the Web Client the devices launch here doesn't seem to have ever heard of such thing.
There is some adb documentation for some Java Client that you would download as JNLP but I cannot find how to download that file? I tried Windows and Mac, a few devices, on Chrome and Firefox too.
Was the debug feature just dropped or what am I missing?
I am working on an Ionic app from a few years back, Ionic CLI 4.4.0, in VSCode (1.65.0). I finally got the environment working again. I can build it to the Android device (Samsung A21s). I could not get the usual Samsung USB driver to work with my device (could be the USB port) but found I can deploy via WiFi. I can attach to the device via WiFi, and get the debug output, but all breakpoints are "unbound" so I cannot step through the code.
Any pointers? Thank you.
I connect to RC android device with running bridge app. And run on Android Studio emulator DJI SDK based application. I connect to the bridge app using:DJISDKManager.getInstance().enableBridgeModeWithBridgeAppIP("192.168.10.102");connection is successful. But DJISDKManager.getInstance().startConnectionToProduct(); don't working. I can't get product.
If I don't use bridge app than DJISDKManager.getInstance().startConnectionToProduct(); works as it should and I can get product.
Problem solved. I launched the bridge app on another device(tablet with Android 4.4.2) and it worked. Before that, I was running the bridge app on phone with Android 6.0.1.
You have use either debug or normal but you are using both 1 and than 2.
For Debug :
DJISDKManager.getInstance().enableBridgeModeWithBridgeAppIP("192.168.10.102");
Normal :
DJISDKManager.getInstance().startConnectionToProduct();
link.
Sample
I have a Samsung S3 running 4.4.3 and I have been using it with Xamrine IDE without issues. As soon as I connect the USB to my Win 7 laptop the IDE shows the device on the list and I"m able to debug and upload code to it. It works.
My wife recently bought the same brand and model phone (Samsung S3) but hers runs 4.4.2. When I connect her phone to the same laptop nothing happens. IDE doesn't see it although the Win OS recognize it and I"m able to upload files to the phone.
I"m using googles USB driver. I did a search and I found the following driver from Intel that's specific for connecting to android.. I applied the driver from Intel but I'm still can't connect to 4.4.2. I restarted the IDE (but didn't restart the computer) but to no avail. Again, the only difference that I can tell between my phone and hers is version number - mine is 4.4.3 which works with Xamarin IDE and hers is 4.4.2 which does not.
Anyone have any ideas of what I can do to make 4.4.2 work with Xamarin IDE?
Thanks in advance.
Hello Android Enthusiasts,
I am in a funny situation which, it seems, I am stuck in. I have been developing simple Android apps on Eclipse and running on the emulator just fine. But recently my attempt to install and run them on a real device (Samsung Galaxy Y) failed again and again.
I stopped the emulator and plugged my real device to the computer with a USB cable. As soon as I did that, I would see the "Installing device driver software" notification and it would complain that the driver for the Abstract Control Model, ACM, was missing.
A few times I ignored the notification and tried to launch an app on my phone. But Eclipse would simply ignore my read device, start the emulator, and run the app on it instead.
I know it is not an Eclipse issue. But how do I get around this USB issue which seems a common problem on Samsung devices based on comments left by many on various sites?
Thanks.
you need to install the appropriate USB driver for your android device Go through this link first Setting up a Device for Development and Installing a USB Driver