I can see the logs below but I can not see the watch face on my watch.
Waiting for device.
Target device: motorola-moto_360-localhost:4444
Uploading file
local path: /Users/.../AndroidStudioProjects/WatchFace1/Wearable/build/outputs/apk/Wearable-debug.apk
remote path: /data/local/tmp/com.example.android.wearable.watchface
Installing com.example.android.wearable.watchface
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.android.wearable.watchface"
pkg: /data/local/tmp/com.example.android.wearable.watchface
Success
Waiting for process: com.example.android.wearable.watchface
I have waited for a long time but nothing happened.
Any ideas?
I see that the apk was successfully installed on the watch. If you long tap on the watch in order to select a watch face, do you see yours in the list? After selecting it you will be able to debug it.
Basically, what I assume it happens is that you install the watch face, but you don't actually run it.
you have to select your watchface from moto 360 by touch and hold on the screen of moto 360 then by swiping the watchfaces then you can debug your watchface.
Related
I'm working on an Ant build automating start/boot of a tvOS simulator, installs app in the running simulator and launch.
When I execute install-to-simulator command, many a time it appears that the simulator is not fully started yet, hence thrown an error like:
[exec] Unable to lookup in current state: Shutdown
I added a delay of 10 seconds between the start-simulator and install-to-simulator commands, but that solution isn't sufficient either.
How I can determine the state of a particular simulator? Or, how to ensure that the simulator is properly started and not in 'Shutdown' state anymore?
Initially I tried to find a solution with following command:
xcrun simctl spawn booted log stream
Unfortunately, I couldn't able to find much of an answer to my needs from the available options.
Thus, I chose to resort on following command:
// since I have simulator UDID already available
xcrun simctl list devices available | grep '$UDID'
This returns me a string output in following way:
Apple TV 4K (3rd generation) (Booted | Shutdown)
Therefore a string-check for "(Booted)" or "(Shutdown)" from the output value, does the job for me.
I'm trying to run GoCD on MacOS (10.12) for testing purposes. When I run both the server and the client apps, they do not provide any GUI output (they should show progress bars or a host configuration) and they quit a couple of seconds after starting.
When I try to run the apps from Terminal as:
/Applications/Go\ Server.app/Contents/MacOS/go-server
I get the following output:
Got directory: /Users/taatyyu1/Library/Application Support/Go Server [It exists]
and then the app quits.
How can I discover what is the issue of the apps not starting properly?
The logs of the apps are available in
~/Library/Application\ Support/Go\ Server/osx-app.log
and
~/Library/Application\ Support/Go\ Agent/osx-app.log
They contain the information from apps starting up and you can use them to figure out what goes wrong
my Visual Studio 2015 with Xamarin is not recognizing that my android emulator started, it was working just fine in the last days, and it just stopped after I restarted the computer today.
Here is the Output log:
1>Starting deploy API19-Intel_Atom ...
1>Starting emulator API19-Intel_Atom ...
1>C:\Users\Kyore\AppData\Local\Android\ANDROI~1\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd API19-Intel_Atom -prop monodroid.avdname=API19-Intel_Atom
1>Hax is enabled
1>Hax ram_size 0x20000000
1>HAX is working and emulator runs in fast virt mode.
1>emulator: Listening for console connections on port: 5554
1>emulator: Serial number of this emulator (for ADB): emulator-5554
It just get stuck in that line, the emulator starts normally, it is fast and I can open/close things without problems, so I have to press CTRL+BREAK to stop it:
1>Process was cancelled
1>Start emulator API19-Intel_Atom was cancelled.
1>Process was cancelled
Build has been canceled.
I tried to restart the computer, restarted VS, restarted ADB server, decreased emulator RAM and HAXM RAM, it always happen.
Try run Visual Studio with Administrator privilege.
"Run as Administrator"
If that's not working, try
Clear AVD cache, Xamarin cache.
Clean the project right click on solution in VS -> Clean Solution.
Delete bin/obj folders in you project folder manually for e.g.
../MyXamarinProject/bin, ../MyXamarinProject/obj
Create new Android Virtual Device
I'm using appcelerator studio version 4.6.0.201605201934
I'm using a nexus 6P, and windows 10
The phone has debugging enabled, and has MTP mode selected. File-Explorer detects the phone each time it is plugged in and tries to download photos from it.
I have put the google USB folder in the android/sdk/extras/google/usb_driver folder
I can see my device on the command prompt by going to the android/sdk folder
adb devices -l
HOWEVER when i go to appcelerator studio, it does not find the phone - the "run configurations" has an empty list of phones to choose from, and running it leads to it informing me that there is no device connected.
What am I doing wrong?
Have you tried to run the kill-server, and devices commands with the adb path?
In my case:
bash-3.2$ /Applications/Android/android-sdk-macosx/platform-tools/adb kill-server
bash-3.2$ /Applications/Android/android-sdk-macosx/platform-tools/adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
If this still doesn't solve your problem, try to add the Vendor ID of the device to the adb_usb.ini file, usually placed:
Windows: C:\Users\YourUser\.android
Mac OS: ~/.android
You can find the Vendor ID at the hardware info on Mac OS here: /Applications/Utilities/System Information
There is also a list of Vendor IDs at the android documentation: https://developer.android.com/studio/run/device.html
Your file will look, like this:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x18d1
I have been using Titanium for some time and I also have the same issue regardless of what device or USB port I use. I even have the issue with simulators.
So I do the following instead:
# Install the application (replacing the existing one if it exists)
adb install -r build/android/bin/YOURAPP.apk
# Run the application (you could also just open the application on your phone)
adb shell am start -n com.package.name/com.package.name.ActivityName
# Show logs
adb logcat "TiAPI:*" "*:S"
The adb tool can be found in windows 10 at this path
/Users/username/AppData/Local/Android/sdk/platform-tools/adb.exe
The activity name can be found in the build/android/AndroidManifest.xml file.
It's usually: YourAppNameActivity
More information about logcat can be found here:
https://logmatic.io/blog/a-how-to-guide-to-debugging-with-android-logcat/
https://developer.android.com/studio/command-line/logcat.html
I got android gingerbread source:
repo init -u https://android.googlesource.com/platform/manifest -b gingerbread && repo sync
Then, I built it：
lunch full_crespo-eng && make -j4
Then, I flash images:
fastboot flash system system.img && fastboot reboot
Then stuck at android screen, cannot boot the system up. Have you ever met this? What am I missing?
Build host: Ubuntu 12.04
Later edit: Fortunately I still can adb into the phone. I simply ps to list processes: I found it stopped at the point after zygote forking system_server. The system_server did not start other stuffs properly. Anybody saw this issue earlier? Any hint? Thank you
N
Solution: Get factory images, replace included system.img with the one just generated. Flash factory images.