I enabled debugging over bluetooth on my Moto 360
and enabled Android Wear app on my Nexus4.
Status displays target : disconnected
Forwarding the port from my computer shows the status host will be changed to connected, but the target status remains disconnected.
I toggled debug via the bluetooth switch which had no effect.
My phone is a Nexus 4. Is there a problem with my phone or the Moto 360?
I eventually managed to get it working. The issue seems to be related to having paired your device with an emulator first. Take a look at this post to see how I fixed it: http://melix.github.io/blog/2014/10/android-moto360.html
open the applications settings, search for the Android Wear application, then force stop it
clear its data and cache
Search for Google Play Services
Click on Manage space. Delete all data.
reboot your phone
reset your Moto 360
Pair watch with phone
Following the instructions from android.com https://developer.android.com/training/wearables/apps/bt-debugging.html to setup debugging and it should work now.
Done.
I tried it on a Sony z1.
It succeeded without any problems.
So, maybe it's not supported perfectly in Nexus 4.
If you have the same problem, I suggest using another device.
I fixed without factory reset with these steps
-Force stop android wear application and clear cache
-Disconnect emulator on android wear app
-Forget emulator on android wear app
-Connect your real device via bluetooth
-Open debugging over bluetooth
Make sure that debugging options are also active in android wear device
Run this commands in command window:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
Related
I am trying to create a layout for our teams channel tab app but when running the app locally and inspecting it as a mobile device, teams throws an error that the browser is not supported.
Can anyone point me in the correct direction to develop my app for mobile use or how I can view the mobile app from the VS Code Teams Toolkit debugging tools?
I have tried to run the app in chrome and in MS Edge browsers and use the inspector device emulators in both but get the same error. I have also tried connecting via my local machine's IP /the FE port 53000 and also have had no luck there.
I used directly my mobile device (android) with Teams App installed for debugging teams custom tab (both phone and tablet worked fine). Connect your android device to your laptop/desktop (using USB), and then on the phone:
Enable USB debugging
Enable "Developer Preview" in Teams options
In the desktop chrome, navigate to chrome://inspect/devices and you should see your device there in the list available for inspection/debugging. You could probably also connect using local WIFI (?), but I have not tried that. Also never tried that with Edge, so not sure if it works.
https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/developer-tools#access-devtools-from-an-android-device
It's not possible to debug a Teams tab on iOS using Windows (or Mac). Using Dev Tools, we can debug Teams tab in desktop and Android clients.
Ref Document: https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/developer-tools
I developed a simple application on Kony and while launching the application it shows the message "Waiting for device". How can I solve it?
Just "wake" your device by unlocking it, touching its screen or going to home screen.
This message is shown when there are no devices/emulators connected to install the application.
You can check if any device/emulator connected by using the below command in Windows command prompt.
adb devices
If the above command lists any device/emulator then you wont see the error.
If the physical device is already connect via USB, the you can check whether the developer option and USB debugging is enabled in you android device.
How to enable developer option?
Hope this helps!
I've started yesterday afternoon studying WP7, so be patient.
I've just created my first test app, registered as developer on AppHub, connected my phone with Zune, registered my phone in my AppHub profile (I can see it in my devices section) and compiled my app.
When I try to transfer my app into phone (using Application Deployment Tool as described here) I get an error that can be traslated as
Unable to connect to device because it's locked by pin
But my device has not any pin (or I don't know to have one) and it doesn't show anything on screen.
What could/should I do?
UPDATE:
Zune is running: if I try I get the error
I close Zune and run WPConnect: my device is connected but the error is the same
When deploying the app, make sure the phone screen is unlocked.
Additinal info: If you are developing from Desktop PC, sometimes connecting from front USB panel wont work.
You can't deploy while the screen lock is active, so try swiping up the lock screen before deploying.
I have installed the Android SDK and I noticed that the WiFi button is not enabled in the emulator. I want to know, whether this functionality available on Emulator or not, and why. I have been looking for a convincing answer for a long period.
There is no WiFi chip inside emulator, so the button cannot be pressed.
Emulator already has a network connection routed through your host PC, so WiFi is not really needed.
I am pretty new to WinMo development. I managed to write my first app, debug it via the emulators but I failed to run the debug session on my physical phone.
I connected my phone to the development PC via ActiveSync, but that alone did not make my phone show up on the list among the selectable emulators. Is there anything I need to do before this would work?
Alternative: I want to program with the G-sensor and the bluetooth capabilites of the phone. Is there a way to play with them via emulators? How on earth do you shake an emulator? :)
After you hooked up and confirmed that ActiveSync is working, you should be able to select the "Mobile Device" form the target list. It is not listed by name, it simply is the only entry not ending in emulator.