My environment is
Windows 10 Home Single Language 21H1
VS2019 Community 16.11.7
Android Emulator 30.1.5
HAXM 7.5.6
I can run Android 9.0 (API 28) in Android Emulator.
But I can't run Android 10.0 (API 29) and Android 11.0 (API 30) in Android Emulator. The emulator will start then stop by itself, no error message.
Following is my Android 11.0 (API 30), others are set as default.
Base Device: Pixel 2 (+ Store)
Processor: x86
OS: R 11.0 - API 30
I need to test in Android 11.0. What cause the error and how to fix it?
Update 2021-12-01
I've try following steps.
Change from fastboot.forceFastBoot to fastboot.forceColdBoot. Not working.
Reduce hw.cpu.ncore from 4 to 1. Not working.
Reduce hw.ramSize from 1536 to *768. Not working.
I've try start the emulator from command, and here is what I got:
"C:\Program Files (x86)\Android\android-sdk\emulator\emulator.EXE" -partition-size 512 -no-boot-anim -feature WindowsHypervisorPlatform -avd pixel_2_r_11_0_-_api_30 -prop monodroid.avdname=pixel_2_r_11_0_-_api_30
emulator: WARNING: Crash service did not start
Active code page: 65001
WARNING: unexpected '-prop' value ('monodroid.avdname=pixel_2_r_11_0_-_api_30'), only 'qemu.*' properties are supported
Failed to open /qemu.conf, err: 2
HAX is working and emulator runs in fast virt mode.
Active code page: 65001
C:\Program Files (x86)\Android\android-sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: error while loading state for instance 0x0 of device 'goldfish_pipe'
deleteSnapshot: for default_boot
VCPU shutdown request
emulator: Saving state on exit with session uptime 255 ms
Thanks
Related
I am facing this issue where I was working fine with Visual Studio Code, installed some extensions, and then my terminal is frozen (blank screen). I am not able to type anything inside terminal.
The image below shows how my terminal looks:
I even tried uninstalling VS Code (as well as all the extensions), updated Windows, and then reinstalled the fresh copy of VS code. But the problem is still there.
I tried some suggested methods in other threads to make the terminal work again, but the terminal problem does not go away.
Some of the suggested solutions that I already tried are:
Re-installing VS Code, updating, and restarting VS Code as well as Windows.
Changing the default Command Line Shell from CMD to Powershell and git bash and back again
Adding a new Command Line Shell
Resizing the terminal window
Zoom In/Out of the terminal
checked the "Use legacy console" option in Powershell options
changed Change inheritEnv to true as "terminal.integrated.inheritEnv": true
Inside the terminal window, Pressed Ctrl + c and hit enter
changed the explorer kind in VS Code form inherited to external "terminal.explorerKind": "external"
changing the renderer type from auto to DOM, canvas forth and back "terminal.integrated.rendererType": "canvas"
System Info:
Windows 10, version 1909
VS Code Info:
Version: 1.44.2 (user setup)
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T16:36:23.138Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 6.2.9200
Output of code --log trace:
https://justpaste.it/673hy
Output of code --version
1.44.2
ff915844119ce9485abfe8aa9076ec76b5300ddd
x64
Output of code --status
Version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T16:36:23.138Z)
OS Version: Windows_NT x64 6.2.9200
CPUs: Intel(R) Core(TM) i5-4200U CPU # 1.60GHz (4 x 2295)
Memory (System): 7.93GB (2.87GB free)
VM: 0%
Screen Reader: no
Process Argv: --log trace
GPU Status: 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
CPU % Mem MB PID Process
0 105 13036 code main
0 84 9172 shared-process
0 38 9916 utility
0 213 11576 window (Settings - adv_exe_6 - Visual Studio Code)
0 22 3760 winpty-process
0 7 7652 console-window-host (Windows internal process)
0 7 8760 C:\WINDOWS\System32\cmd.exe
0 20 6228 winpty-process
0 7 232 console-window-host (Windows internal process)
0 44 10196 C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
0 78 7988 extensionHost
0 64 2840 electron_node tsserver.js
0 35 10444 electron_node typingsInstaller.js typesMap.js
0 60 13140 "C:\Users\ITKHAN\AppData\Local\Programs\Microsoft VS Code\Code.exe" "c:\Users\ITKHAN\AppD
ata\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\jsonServerMain" --node-
ipc --clientProcessId=7988
0 42 14272 electron_node tsserver.js
0 22 9492 winpty-process
0 68 5716 C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
0 7 5724 console-window-host (Windows internal process)
0 11 12124 watcherService
0 7 14004 console-window-host (Windows internal process)
0 22 13552 winpty-process
0 7 10100 console-window-host (Windows internal process)
0 7 11960 C:\WINDOWS\System32\cmd.exe
0 143 13760 gpu-process
0 15 14188 electron-crash-reporter
Workspace Stats:
| Window (Settings - adv_exe_6 - Visual Studio Code)
| Folder (adv_exe_6): 8 files
| File types: js(4) stackdump(1) html(1) css(1)
| Conf files:
I would really appreciate if someone could help me in debugging this issue. Thanks.
Here's a video that helped me find a way to solve this issue.
I unchecked the compatibility mode in VS Code properties where it says Run this program in compatibility mode for:.
But this made the terminal open in an external window instead of being integrated in VS Code whenever I opened an new terminal inside VS Code.
So I also disabled the Conpty for Windows terminal inside VS code settings > Terminal > Inegrated:Windows Enable Conpty
"terminal.integrated.windowsEnableConpty": false
The interesting point to note here is that this solution didn't work for me when this problem first arose. At that time, I had my VS code with all the extensions installed. After updating Windows, reinstalling fresh copy of VS code without any extensions, this solution did do the trick for me.
So, the underlying issue was probably with the outdated Windows, or some extensions that I had installed.
I switched off git.autorefresh in the settings. In VS code, go to file --> Preferences ---> settings and in the search bar type git.autorefresher; then, uncheck whether auto refreshing is enabled. under Git:Autorefresh:
This way worked for me.
As I had the same problem but a different reason for it:
I had these lines in the ~/.zshrc file, which was added by the angular cli. Removing it resolved the issue
# Load Angular CLI autocompletion.
source <(ng completion script)
See also https://code.visualstudio.com/docs/supporting/faq#_resolving-shell-environment-fails
Whenever I try to create a new virtual device in Android Device Manager from Visual Studio, I get the following error:
AVD CREATION ERROR: AVD failed to create with error : AVD Manager has returned non-zero exit code: 1. Please check logs for more information.
From logs, I found the following snippet which is probably the error:
[18-05-12 10:45:44.76] [AvdManager.CreateAvd] AVD Manager has returned non-zero exit code: 1
Command: C:\Program Files (x86)\Android\android-sdk\tools\bin\avdmanager.batcreate avd -n my_device -k system-images;android-25;google_apis_playstore;x86 --tag google_apis_playstore --abi x86 -d Nexus 5X --sdcard 100M
Details: Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.<init>(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.<init>(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.<clinit>(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.AvdManagerCli.run(AvdManagerCli.java:213)
at com.android.sdklib.tool.AvdManagerCli.main(AvdManagerCli.java:200)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
... 5 more
It happens no matter whatever configuration or version of Android I use.
Details:
OS: Windows 10 Professional x64
Processor: Ryzen 1700
Uninstalling all other versions of JAVA SDK except SDK 8 done the work for me.
My current JAVA SDK's:
I have an Xamarin Android project. Now I cannot get the app started in the emulator anymore. After building the solution the emulator starts but the app is never deployed.
The output window in Visual Studio shows this:
Starting deploy EmulatorName ...
Starting emulator EmulatorName ...
C:\Users\USERNAME\AppData\Local\Android\Sdk\tools\emulator.EXE -partition-size 512 -no-boot-anim -avd EmulatorName -prop monodroid.avdname=EmulatorName
emulator: WARNING: Crash service did not start
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x40000000
HAX is working and emulator runs in fast virt mode.
Emulator EmulatorName is running.
Waiting for emulator to be ready...
Deploying EmulatorName ...
Build started.
...
Using "AndroidZipAlign" task from assembly "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MS
PackagedResources:
obj\Debug\android\bin\packaged_resources
SDCardDirectory:
External: False
ManifestTemplate: obj\Debug\android\AndroidManifest.xml
EnableInstantRun: False
InstantRunForceUploadApk: True
AndroidSdkPath: C:\Users\username\AppData\Local\Android\Sdk
AndroidNdkPath: C:\ProgramData\Microsoft\AndroidNDK64\android-ndk-r13b
JavaSdkPath: C:\Program Files (x86)\Java\jdk1.8.0_112
Found AndroidSdk at C:\Users\username\AppData\Local\Android\Sdk
Found AndroidNdk at C:\ProgramData\Microsoft\AndroidNDK64\android-ndk-r13b
Found AndroidTools at C:\Users\username\AppData\Local\Android\Sdk\tools
DEBUG RunShellCommand emulator-5554 getprop
TASK: GetProperties getprop completed?:[dalvik.vm.dex2oat-Xms]: [64m]
[dalvik.vm.dex2oat-Xmx]: [512m]
[dalvik.vm.heapsize]: [256m]
[dalv...
I can't get a simple app to run on watchOS 3 and it's driving me CRAZY!
I'm running with Xcode 8.
Recreate scenario: Create a newiOS app (defaults to deployment target 10), add WatchOS project (3.0). Try to compile.
I get:
Could not AOT the assembly (MT3001)
Changing Build link to "Don't Link" on all three projects and downgrading to target 8.4 and Watch OS 2.2 results:
Error MT1006: Could not install the application on the device: Sent message error( error : 0xe800002d).
Changing to target 10, but keeping Watch OS 2 finally gets compiled and installed on the phone and deployed on device, but debugger either:
A. Never manage to connect over Wifi to the watch (stuck at "waiting for the app to connect on port 10000)
B. Get the following error:
Launched watch application 'com.XXX.testwatch.watchkitapp' on 'Apple Watch' with pid 270
Exception: Xamarin.Hosting.MobileDeviceException: Send Message Error (error: 0xe800002d)
at Xamarin.Hosting.RealDevice.StartSession () <0x118c24dd0 + 0x0009d> in :0
at Xamarin.Hosting.DebugService+c__AnonStorey6.<>m__0 (System.Object v) <0x118c24450 + 0x000cf> in :0
[MVID] 703d5be3b466420882f6cb97c41b6723 0,1
What am I doing wrong here?
I've submitted a bug report To Xamarin. They confirmed. You need to modify the default compilation to disable the incremental build.
i've followed this in order to flashbuilder 4.6 to use air sdk 3.4. no problems, or hiccups with the update.
the only problem is when i try to debug a mobile project using this sdk, either for android or ios i get the following error:
Process terminated without establishing connection to debugger.
invalid application descriptor: Unknown namespace:
http://ns.adobe.com/air/application/3.4
Launch command details: "C:\Program Files (x86)\Adobe\Adobe Flash
Builder 4.6\sdks\4.6.1\bin\adl.exe" -runtime "C:\Program Files
(x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.1\runtimes\air\win"
-profile mobileDevice -screensize 640x920:640x960 -XscreenDPI 326 -XversionPlatform IOS "C:\Users\joao\Adobe Flash Builder 4.6\teste34\bin-debug\teste34-app.xml" "C:\Users\joao\Adobe Flash Builder 4.6\teste34\bin-debug"
i've also got this problem.
following is what i've done:
1:create a new empty mobile application and debug it runs
2:open the new app's '{appname}-app.xml' file , find the 'xmlns' property in application root node for example
<application xmlns="http://ns.adobe.com/air/application/3.1">
3:replace the row of your old application
So i think the problem is your air sdk can not support the 3.4 version