The Android project doesnt deploy from Visual studio to Samsung Tab.
Initially the output shows deploying to device, after 2 minutes, it changes to Ready state and doesnt deploy even after 30 mins.
Below is the part of output I get repeatedly[couldnt attach whole output]. Can anyone help me why this happens? Thanks in Advance
[aot-compiler stdout] Added 0 methods from profile.
[aot-compiler stdout] Compiled: 0/0
[aot-compiler stdout] Executing the native assembler: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\Android
dk\aarch64-linux-android-as" -o C:\_release\100\aot\arm64-v8a\Rg.Plugins.Popup.dll\temp.s.o C:\_release\100\aot\arm64-v8a\Rg.Plugins.Popup.dll\temp.s
[aot-compiler stdout] Executing the native linker: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\Android
dk\aarch64-linux-android-ld" -Bsymbolic -shared -o C:\_release\100\aot\arm64-v8a\libaot-Rg.Plugins.Popup.dll.so.tmp C:\_release\100\aot\arm64-v8a\Rg.Plugins.Popup.dll\temp.s.o
[aot-compiler stdout] JIT time: 0 ms, Generation time: 8 ms, Assembly+Link time: 2638 ms.
[aot-compiler stdout] Mono Ahead of Time compiler - compiling assembly C:\_release\100\android\assets\ABC_Mobile.dll
[aot-compiler stdout] AOTID AD8A55E2-5D90-DBD2-20AA-0EB5F30CA8D6
[aot-compiler stdout] Using profile data file 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\Android\startup-xf.aotprofile'
[aot-compiler stdout] Added 0 methods from profile.
[aot-compiler stdout] Compiled: 16/16
[aot-compiler stdout] Executing the native assembler: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\Android
dk\aarch64-linux-android-as" -o C:\_release\100\aot\arm64-v8a\ABC_Mobile.dll\temp.s.o C:\_release\100\aot\arm64-v8a\ABC_Mobile.dll\temp.s
[aot-compiler stdout] Executing the native linker: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\Android
dk\aarch64-linux-android-ld" -Bsymbolic -shared -o C:\_release\100\aot\arm64-v8a\libaot-ABC_Mobile.dll.so.tmp C:\_release\100\aot\arm64-v8a\ABC_Mobile.dll\temp.s.o
[aot-compiler stdout] JIT time: 108 ms, Generation time: 139 ms, Assembly+Link time: 4334 ms.
[aot-compiler stdout] Mono Ahead of Time compiler - compiling assembly C:\_release\100\android\assets\Xamarin.Forms.Core.dll
[aot-compiler stdout] AOTID DDEE118B-BBA5-7A06-5B54-EE9EB049494A
[aot-compiler stdout] Using profile data file 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\Android\startup-xf.aotprofile'
[aot-compiler stdout] Added 801 methods from profile.
[aot-compiler stdout] Compiled: 1573/1574
[aot-compiler stdout] Executing the native assembler: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\Android
dk\aarch64-linux-android-as" -o C:\_release\100\aot\arm64-v8a\Xamarin.Forms.Core.dll\temp.s.o C:\_release\100\aot\arm64-v8a\Xamarin.Forms.Core.dll\temp.s
[aot-compiler stdout] Executing the native linker: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\Android
dk\aarch64-linux-android-ld" -Bsymbolic -shared -o C:\_release\100\aot\arm64-v8a\libaot-Xamarin.Forms.Core.dll.so.tmp C:\_release\100\aot\arm64-v8a\Xamarin.Forms.Core.dll\temp.s.o
[aot-compiler stdout] JIT time: 1298 ms, Generation time: 1109 ms, Assembly+Link time: 2990 ms..
the adb temp file content:
adb starting (pid 15236) --- adb I 05-09 11:59:41 15236 11944 main.cpp:62] Android Debug Bridge version 1.0.41 adb I 05-09 11:59:41 15236 11944 main.cpp:62] Version 30.0.4-6686687 adb I 05-09 11:59:41 15236 11944 main.cpp:62] Installed as C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.EXE adb I 05-09 11:59:41 15236 11944 main.cpp:62] adb I 05-09 11:59:41 15236 11944 auth.cpp:417] adb_auth_init... adb I 05-09 11:59:41 15236 11944 auth.cpp:152] loaded new key from 'C:\Users\name.android\adbkey' with fingerprint 69E79BFD0AF8309554998A71DE062E adb I 05-09 12:00:29 15236 14372 transport.cpp:325] A52R0GHX: read thread spawning adb I 05-09 12:00:29 15236 11976 transport.cpp:297] A52R0GHX: write thread spawning adb I 05-09 12:00:29 15236 11944 transport.cpp:1527] fetching keys for transport A52R0GHX adb I 05-09 12:00:29 15236 11944 auth.cpp:469] Calling send_auth_response adb I 05-09 12:00:29 15236 11944 adb.cpp:124] A52R0GHX: offline adb I 05-09 12:00:30 15236 14372 transport.cpp:329] A52R0GHX: read failed: Input/output error adb I 05-09 12:00:30 15236 14372 transport.cpp:810] A52R0GHX: connection terminated: read failed adb I 05-09 12:00:30 15236 11944 adb.cpp:124] A52R0GHX: offline adb I 05-09 12:00:30 15236 11944 transport.cpp:914] destroying transport A52R0GHX adb I 05-09 12:00:30 15236 11944 transport.cpp:400] BlockingConnectionAdapter(A52R0GHX): stopping adb I 05-09 12:00:30 15236 11944 transport.cpp:418] BlockingConnectionAdapter(A52R0GHX): stopped adb I 05-09 12:00:30 15236 11944 transport.cpp:283] BlockingConnectionAdapter(A52R0GHX): destructing adb I 05-09 12:00:30 15236 11944 transport.cpp:392] BlockingConnectionAdapter(A52R0GHX): already stopped adb I 05-09 12:00:32 15236 12392 transport.cpp:325] A52R0GHX: read thread spawning adb I 05-09 12:00:32 15236 15672 transport.cpp:297] A52R0GHX: write thread spawning adb I 05-09 12:00:32 15236 11944 transport.cpp:1527] fetching keys for transport A52R0GHX adb I 05-09 12:00:32 15236 11944 auth.cpp:469] Calling send_auth_response adb I 05-09 12:00:32 15236 11944 adb.cpp:124] A52R0GHX: offline adb I 05-09 13:17:48 15236 12392 transport.cpp:329] A52R0GHX: read failed: Input/output error adb I 05-09 13:17:48 15236 12392 transport.cpp:810] A52R0GHX: connection terminated: read failed adb I 05-09 13:17:48 15236 11944 adb.cpp:124] A52R0GHX: offline adb I 05-09 13:17:48 15236 11944 transport.cpp:914] destroying transport A52R0GHX adb I 05-09 13:17:48 15236 11944 transport.cpp:400] BlockingConnectionAdapter(A52R0GHX): stopping adb I 05-09 13:17:48 15236 11944 transport.cpp:418] BlockingConnectionAdapter(A52R0GHX): stopped adb I 05-09 13:17:48 15236 11944 transport.cpp:283] BlockingConnectionAdapter(A52R0GHX): destructing adb I 05-09 13:17:48 15236 11944 transport.cpp:392] BlockingConnectionAdapter(A52R0GHX): already stopped
The issue was resolved by unchecking Enable Startup Tracing inside the Android option, which sets AndroidEnableProfiledAot to false.
Related
I'm a newbie to Android Studio and I install Android Studio 2021.1.1 from scratch on Windows 10, but when I want to run the emulator, it just can't be launched with this error:
in the log located at C:\Users\xxx\AppData\Local\Google\AndroidStudio2021.1\log, I got some info as below. So can anyone help to figure it out?
2022-03-24 16:09:10,973 [ 826150] INFO - testKnownPluginVersionProvider - 'gradle' plugin missing from the offline Maven repo, will use default 7.1.2
2022-03-24 16:09:11,368 [ 826545] INFO - ativeWorkspaceModificationTask - NDK support for project 'Demo1' is disabled because the project doesn't contain any valid native configurations.
2022-03-24 16:09:27,095 [ 842272] WARN - vdmanager.AvdManagerConnection - Error setting permissions for C:\Users\xxx\temp\emu.tmp
2022-03-24 16:09:29,433 [ 844610] INFO - manager.EmulatorProcessHandler - Emulator: C:\Users\xxx\AppData\Local\Android\Sdk\emulator\emulator.exe -netdelay none -netspeed full -studio-params C:\Users\xxx\temp\emu.tmp -avd Nexus_6_API_30 -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
2022-03-24 16:09:39,317 [ 854494] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | Crash service did not start
2022-03-24 16:09:39,317 [ 854494] INFO - manager.EmulatorProcessHandler - Emulator:
2022-03-24 16:09:39,471 [ 854648] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
2022-03-24 16:09:45,515 [ 860692] INFO - manager.EmulatorProcessHandler - Emulator: INFO | Android emulator version 31.2.9.0 (build_id 8316981) (CL:N/A)
2022-03-24 16:09:45,515 [ 860692] INFO - manager.EmulatorProcessHandler - Emulator: Process finished with exit code -1073741819 (0xC0000005)
2022-03-24 16:09:45,515 [ 860692] WARN - manager.EmulatorProcessHandler - Emulator terminated with exit code -1073741819
2022-03-24 16:09:55,157 [ 870334] WARN - com.intellij.util.xmlb.Binding - no accessors for com.intellij.openapi.updateSettings.impl.pluginsAdvertisement.PluginAdvertiserExtensionsStateService$State
2022-03-24 16:09:55,188 [ 870365] INFO - rationStore.ComponentStoreImpl - Saving appClangTidySettings took 16 ms, FileTypeManager took 15 ms, PluginFeatureService took 15 ms, VcsApplicationSettings took 16 ms
2022-03-24 16:09:55,701 [ 870878] INFO - rationStore.ComponentStoreImpl - Saving Project(name=Demo1, containerState=COMPONENT_CREATED, componentStore=C:\N-20L6PF1KPTJU-Data\xxx\Documents\99.Self.Learning\00.Android)XDebuggerManager took 30 ms
For the permission under C:\Users\xxx\temp*, it has no difference if I set it to full-control or read-only.
I don't know exactly what's the rc, but when I tried Nexus 6 API 28, it works.
I launch my virtual device (10.1 Lollipop (5.1.1) XHDPI Tablet), but waiting long time (forty minutes or more) and nothing shows up, can anyone help me?
I can use API Level 19 with 10.1 KitKat (4.4) successfully, but Api Level 22 can't go into Launcher.
The following is my log from the Visual Studio Emulator for Android
0> 2017/4/25 下午 12:03:31 : [Informational] ===== Session Ended =====
0> 2017/4/25 下午 12:04:31 : [Informational] ===== Session Started =====
1> 2017/4/25 下午 12:04:31 : [Informational] Emulator manager version: 1.1.622.2
1> 2017/4/25 下午 12:04:31 : [Informational] Emulator manager plugin version: 1.1.622.2
1> 2017/4/25 下午 12:04:31 : [Informational] Microsoft Windows NT 10.0.14393.0 Windows 10 Pro
1> 2017/4/25 下午 12:04:31 : [Informational] Virtualization type: UnknownOrNotVirtual
1> 2017/4/25 下午 12:04:31 : [Informational] Virtualization Version: _asus_ - 1072009
1> 2017/4/25 下午 12:04:31 : [Informational] Virtualization Serial Number: gan0wu00086140b
1> 2017/4/25 下午 12:04:31 : [Informational] Virtualization Product: ux330ua
1> 2017/4/25 下午 12:04:31 : [Informational] Display Adapter 0: Name: Intel(R) HD Graphics 520, Version: 21.20.16.4550
2> 2017/4/25 下午 12:04:32 : [Informational] Reinitializing installed profiles.
2> 2017/4/25 下午 12:04:32 : [Warning] Platform config with ID FE19D391-E688-408B-B8CF-E523C4FC602E could not be found.
2> 2017/4/25 下午 12:04:32 : [Warning] Configuration file 'C:\Users\bin\AppData\Local\Microsoft\VisualStudioEmulator\Android\Containers\Local\Devices\10.1_Lollipop_(5.0)_XHDPI_Tablet.cfg' was not able to be initialized. The configuration will not be included as a part of the container.
2> 2017/4/25 下午 12:04:32 : [Warning] Platform config with ID FE19D391-E688-408B-B8CF-E523C4FC602E could not be found.
2> 2017/4/25 下午 12:04:32 : [Warning] Configuration file 'C:\Users\bin\AppData\Local\Microsoft\VisualStudioEmulator\Android\Containers\Local\Devices\7_Lollipop_(5.0)_XHDPI_Tablet.cfg' was not able to be initialized. The configuration will not be included as a part of the container.
2> 2017/4/25 下午 12:04:32 : [Informational] Installed profiles initialized. Devices: 4 Platforms: 2
2> 2017/4/25 下午 12:04:32 : [Informational] Reinitializing installable profiles.
2> 2017/4/25 下午 12:04:32 : [Informational] Installable profiles initialized. Devices: 38 Platforms: 5
3> 2017/4/25 下午 12:04:35 : [Informational] Waiting to launch device...
3> 2017/4/25 下午 12:04:35 : [Informational] Launching Device: 10.1" Lollipop (5.1.1) XHDPI Tablet
3> 2017/4/25 下午 12:04:35 : [Informational] Validating emulator arguments...
3> 2017/4/25 下午 12:04:35 : [Informational] Determining if emulator is already running...
3> 2017/4/25 下午 12:04:35 : [Informational] Preparing virtual machine...
3> 2017/4/25 下午 12:04:38 : [Informational] Launching emulator...
3> 2017/4/25 下午 12:44:57 : [Critical] Could not launch 'VS Emulator 10.1" Lollipop (5.1.1) XHDPI Tablet' device. Exit code 0.
3> 2017/4/25 下午 12:44:57 : [Critical] XDE Path: C:\Program Files (x86)\Microsoft XDE\10.0.10586.0\xde.exe
3> 2017/4/25 下午 12:44:57 : [Critical] XDE Arguments: /sku Android /displayName "VS Emulator 10.1\" Lollipop (5.1.1) XHDPI Tablet" /memSize 2048 /diagonalSize 10.1 /video "2560x1600" /vhd "C:\Users\bin\AppData\Local\Microsoft\VisualStudioEmulator\Android\Containers\Local\Devices\vhd\10.1_Lollipop_(5.1.1)_XHDPI_Tablet\image.vhd" /name "VS Emulator 10.1-inch Lollipop (5.1.1) XHDPI Tablet.bin"
3> 2017/4/25 下午 12:44:57 : [Critical] XDE Exit Code: Success (0)
I tried to install SonarQube on my laptop. But when I run the StartSonar.bat file, I get the following output:
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
jvm 1 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
jvm 1 |
jvm 1 | 2016.10.15 04:04:00 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory D:\sonarqube-5.6.3\temp
jvm 1 | 2016.10.15 04:04:00 INFO app[o.s.p.m.JavaProcessLauncher] Launch process[es]: C:\Program Files\Java\jre1.8.0_101\bin\java
jvm 1 | 2016.10.15 04:04:22 INFO app[o.s.p.m.Monitor] Process[es] is stopping
jvm 1 | 2016.10.15 04:04:23 INFO app[o.s.p.m.Monitor] Process[es] is stopped
wrapper | <-- Wrapper Stopped
I checked the logs, but I can't find anything. Maybe I misunderstood.
I had the same problem. I found out that I didn't have the rights to run Sonar in my computer. Had to go and ask someone from IT with administrator rights.
1-Please look into the sonar log not in command line console.
2-Basically this error comes when there is environment variable not set properly.
3-Please check the java version compatibility also.
I've just setup libfreenect2 on OSX 10.11.5 and I can successfully run the Protonect demo displaying RGB/IR/depth streams, but I'd like to use OpenNI/NITE for skeleton tracking as well.
I've followed the instructions in the repo's README file for OpenNI, but when I tried to run NiViewer I got this:
NiViewer
openDevice failed:
DeviceOpen using default: no devices found
Press any key to continue . . .
I'm currently going through libfreenect2 issues on github and documenting what I'm trying and the outcomes here. Any hints/tips are helpful.
What is the easiest way to setup and test OpenNI/NITE with libfreenect2 using a Kinect v2 on OSX ?
Turns out I was using NiTE 1.5 when I should've been using NiTE2.2
I simply copied libfreenect2-openni2.0.dylib from libfreenect2/build/lib to NiTE-MacOSX-x64-2.2/Samples/Bin/OpenNI2/Drivers/ then ran the SimpleUserTracker sample and it worked !
There is still a catch: samples that just print to the console run, but the ones that open a window and render don't work. No window is rendered, as if that thread is blocked somehow.
That is when I use the integrated Intel GPU. If I use the discrete nVidia GPU the app crashes:
./UserViewer
124095 INFO New log started on 2016-08-30 20:32:19
124114 INFO --- Filter Info --- Minimum Severity: VERBOSE
126001 VERBOSE No override device in configuration file
126029 VERBOSE Configuration has been read from '/Users/George/Downloads/Grouped/Projects/code+libs/NiTE-MacOSX-x64-2.2/Samples/Bin/OpenNI.ini'
126034 VERBOSE OpenNI 2.2.0 (Build 21)-MacOSX (May 29 2013 14:03:30)
126038 VERBOSE Using '/Users/George/Downloads/Grouped/Projects/code+libs/NiTE-MacOSX-x64-2.2/Samples/Bin/OpenNI2/Drivers' as driver path
126042 VERBOSE Looking for drivers in drivers repository '/Users/George/Downloads/Grouped/Projects/code+libs/NiTE-MacOSX-x64-2.2/Samples/Bin/OpenNI2/Drivers'
161329 INFO New log started on 2016-08-30 20:32:19
161447 INFO --- Filter Info --- Minimum Severity: VERBOSE
161457 VERBOSE Initializing USB...
166761 INFO USB is initialized.
286714 INFO New log started on 2016-08-30 20:32:19
286762 INFO --- Filter Info --- Minimum Severity: VERBOSE
286781 VERBOSE Initializing USB...
286804 INFO USB is initialized.
[Info] [Freenect2Impl] enumerating devices...
[Info] [Freenect2Impl] 7 usb devices connected
[Info] [Freenect2Impl] found valid Kinect v2 #20:16 with serial 500722542042
[Info] [Freenect2Impl] found 1 devices
5380695 INFO Found device freenect2://0
5380723 INFO Driver: register new uri: freenect2://0
5381065 INFO Device connected: Microsoft Kinect (freenect2://0)
5381101 INFO Device state changed: Microsoft Kinect (freenect2://0) to 0
5381115 INFO Driver: register new uri: freenect2://0?depth-size=640x480
5381123 INFO Device connected: Microsoft Kinect (freenect2://0?depth-size=640x480)
5381132 INFO Device state changed: Microsoft Kinect (freenect2://0?depth-size=640x480) to 0
5381139 INFO Driver: register new uri: freenect2://0?depth-size=512x424
5381149 INFO Device connected: Microsoft Kinect (freenect2://0?depth-size=512x424)
5381157 INFO Device state changed: Microsoft Kinect (freenect2://0?depth-size=512x424) to 0
[Info] [Freenect2Impl] enumerating devices...
[Info] [Freenect2Impl] 7 usb devices connected
[Info] [Freenect2Impl] found valid Kinect v2 #20:16 with serial 500722542042
[Info] [Freenect2Impl] found 1 devices
10381916 VERBOSE Trying to open device by URI '(NULL)'
10381940 INFO deiveOpen: freenect2://0
10381948 INFO Opening device freenect2://0
[Info] [Freenect2DeviceImpl] opening...
[Info] [Freenect2DeviceImpl] transfer pool sizes rgb: 20*16384 ir: 4*128*33792
[Info] [Freenect2DeviceImpl] opened
12312037 VERBOSE Initialize: Already initialized
12314810 INFO Device: createStream(depth)
12314892 INFO Freenect2Driver::Device: start()
[Info] [Freenect2DeviceImpl] starting...
[Info] [Freenect2DeviceImpl] submitting rgb transfers...
[Info] [Freenect2DeviceImpl] submitting depth transfers...
[Info] [Freenect2DeviceImpl] started
2016-08-30 20:32:31.847 UserViewer[7575:4995528] GLUT Warning: glutInit being called a second time.
[Info] [VTRgbPacketProcessor] avg. time: 19.633ms -> ~50.9346Hz
[Info] [VTRgbPacketProcessor] avg. time: 19.6306ms -> ~50.9408Hz
[Info] [VTRgbPacketProcessor] avg. time: 19.0744ms -> ~52.4262Hz
[Info] [DepthPacketStreamParser] 417 packets were lost
Segmentation fault: 11
How can I get past this issue ?
For reference here are the above notes as an aswer.
This is what I did to get OpenNI2/NITE2.2 skeleton tracking with libfreenect2 and it's OpenNI2 driver. I have:
compiled installed OpenNI2 via homebrew and compiled libfreenect2 with OpenNI2 support as per github repo's readme instructions
downloaded NITE2.2 (replacing Nite1.5 which I was missusing before)
copied the libfreenect2 OpenNI2 driver (ibfreenect2/build/lib/libfreenect2-openni2.0.dylib) to the Drivers folder where I needed to run NITE2 (e.g. NiTE-MacOSX-x64-2.2/Samples/Bin/OpenNI2/Drivers).
I have figured out the path was wrong by setting the log level to verbose in OpenNI.ini:
[Log]
; 0 - Verbose; 1 - Info; 2 - Warning; 3 - Error. Default - None
Verbosity=0
LogToConsole=1
LogToFile=1
[Device]
;Override=""
[Drivers]
; Location of the drivers specified by a relative path based on OpenNI's shared library or an absolute path.
; Path separator "/" can be used to be portable for any platforms.
; Default - OpenNI2/Drivers
Repository=OpenNI2/Drivers
Symon Kaliski followed the notes and wrote a brilliant Kinect 2 on OSX with skeleton tracking post using OpenFrameworks, be sure to check it out!
Also, once libfreenect2 is compiled with openni2 support it can even be used in Processing, simply drop libfreenect2-openni2.0.dylib in /Documents/Processing3/libraries/SimpleOpenNI/library/osx/OpenNI2 (on OSX):
Question Explaination
I am trying to running a program using cgal4.6.1, boost1.58.0, qt4.8.5 on my win32 PC with VS2010 ultimate. But when I build the solutions, there are errors happen as showing below. I've deploy the cgal etc well. I wondering how to solve this problem? I will appreciate for your solutions
Error Output
1>------ Build started: Project: qmat, Configuration: Debug Win32 ------
1>Build started 7/31/2015 4:07:00 PM.
1>InitializeBuildStatus:
1> Creating "Debug\qmat.unsuccessfulbuild" because "AlwaysCreate" was specified.
1>CustomBuild:
1> Moc'ing GLWidget.h...
1> The device is not ready.
1> Moc'ing medialaxissimplification3d.h...
1> The device is not ready.
1> Uic'ing medial_axis.ui...
1> The device is not ready.
1> Rcc'ing medial_axis.qrc...
1> The device is not ready.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(151,5): error MSB6006: "cmd.exe" exited with code 21.
1>
1>Build FAILED.
1>
1>Time Elapsed 00:00:00.40
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========