- Saved searches
- Use saved searches to filter your results more quickly
- adb: error: no devices/emulators found #1969
- adb: error: no devices/emulators found #1969
- Comments
- no devices/emulators found when trying to use ionic cordova run android —device
- Saved searches
- Use saved searches to filter your results more quickly
- error: no devices/emulators found #1692
- error: no devices/emulators found #1692
- Comments
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adb: error: no devices/emulators found #1969
adb: error: no devices/emulators found #1969
Comments
Environment
- OS: Windows 8.1 Pro
- scrcpy version: 1.16
- installation method: Windows release
- device model: Realme X2
- Android version: 10
Describe the bug
I get this on starting scrcpy.exe
adb: error: failed to get feature set: no devices/emulators found ERROR: "adb push" returned with value 1
tried running adb devices : the list of devices comes up blank
Phone is connected via USB(to transfer files) & USB debugging is enabled.
I read the FAQ for this issue, where it says I may need some drivers for Windows; but I checked in the Device Manager and found that the driver software is up to date. And I’m able to transfer files between the phone and pc as usual.
Can someone help me?
The text was updated successfully, but these errors were encountered:
no devices/emulators found when trying to use ionic cordova run android —device
When I run: ionic cordova run android —device I get this output:
BUILD SUCCESSFUL in 5s 42 actionable tasks: 42 up-to-date Built the following apk(s): C:\Users\K-PC\myApp\platforms\android\app\build\outputs\apk\debug\app-debug.apk native-run.cmd android --app platforms\android\app\build\outputs\apk\debug\app-debug.apk --device [native-run] ERR_NO_DEVICE: No hardware devices found. Not attempting emulator because --device was specified. [native-run] [native-run] More details for this error may be available online: [native-run] [native-run] https://github.com/ionic-team/native-run/wiki/Android-Errors [ERROR] An error occurred while running subprocess native-run. native-run.cmd android --app platforms\android\app\build\outputs\apk\debug\app-d. exited with exit code 1. Re-running this command with the --verbose flag may provide more information.
I checked to see if the device was listed using native-run android —list and I get this output:
Errors (!): ERR_UNSUITABLE_API_INSTALLATION: No suitable API installation found. More details for this error may be available online: https://github.com/ionic-team/native-run/wiki/Android-Errors Connected Devices: No connected devices found Virtual Devices: No virtual devices found
I have Android Studio installed, I have two virtual devices in my AVD manager:
I want to deploy the APK onto the device connected to my laptop, not these emulators but its strange to see that it hasn’t even recognised the emulators inside my AVD manager
How can I fix this issue? I hope I have given enough detail.
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error: no devices/emulators found #1692
error: no devices/emulators found #1692
Comments
- Please check that no similar bug is already reported. Have a look on the list of open bugs at https://github.com/anbox/anbox/issues
- Make sure you are running the latest version of Anbox before reporting an issue. Update snap to latest: snap refresh —devmode —edge anbox
- Make sure you have debug logs enabled:
sudo snap set anbox debug.enable=true - Reproduce the error while debug logs enabled.
- Run the anbox logs collection utility and attach the tar file.
sudo /snap/bin/anbox.collect-bug-info
Not sure how I’m supposed to attach this. - ** Please paste the result of anbox system-info below:**
version: 4 snap-revision: 186 cpu: arch: x86 brand: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz features: - aes - sse4_1 - sse4_2 - avx - avx2 os: name: Ubuntu version: 20.04.1 LTS (Focal Fossa) snap-based: true kernel: version: Linux version 5.4.0-56-generic (buildd@lgw01-amd64-025) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #62-Ubuntu SMP Mon Nov 23 19:20:19 UTC 2020 binder: false ashmem: true graphics: egl: vendor: Mesa Project version: 1.4 (DRI2) extensions: - EGL_ANDROID_native_fence_sync - EGL_CHROMIUM_sync_control - EGL_EXT_buffer_age - EGL_EXT_create_context_robustness - EGL_EXT_image_dma_buf_import - EGL_EXT_image_dma_buf_import_modifiers - EGL_IMG_context_priority - EGL_KHR_config_attribs - EGL_KHR_create_context - EGL_KHR_create_context_no_error - EGL_KHR_fence_sync - EGL_KHR_get_all_proc_addresses - EGL_KHR_gl_colorspace - EGL_KHR_gl_renderbuffer_image - EGL_KHR_gl_texture_2D_image - EGL_KHR_gl_texture_3D_image - EGL_KHR_gl_texture_cubemap_image - EGL_KHR_image - EGL_KHR_image_base - EGL_KHR_image_pixmap - EGL_KHR_no_config_context - EGL_KHR_reusable_sync - EGL_KHR_surfaceless_context - EGL_EXT_pixel_format_float - EGL_KHR_wait_sync - EGL_MESA_configless_context - EGL_MESA_drm_image - EGL_MESA_image_dma_buf_export - EGL_NOK_texture_from_pixmap - EGL_WL_bind_wayland_display gles2: vendor: Intel Open Source Technology Center vendor: OpenGL ES 3.2 Mesa 18.0.5 extensions: - GL_ANDROID_extension_pack_es31a - GL_ANGLE_texture_compression_dxt3 - GL_ANGLE_texture_compression_dxt5 - GL_APPLE_texture_max_level - GL_EXT_blend_func_extended - GL_EXT_blend_minmax - GL_EXT_buffer_storage - GL_EXT_clip_cull_distance - GL_EXT_color_buffer_float - GL_EXT_compressed_ETC1_RGB8_sub_texture - GL_EXT_copy_image - GL_EXT_discard_framebuffer - GL_EXT_disjoint_timer_query - GL_EXT_draw_buffers - GL_EXT_draw_buffers_indexed - GL_EXT_draw_elements_base_vertex - GL_EXT_frag_depth - GL_EXT_geometry_point_size - GL_EXT_geometry_shader - GL_EXT_gpu_shader5 - GL_EXT_map_buffer_range - GL_EXT_multi_draw_arrays - GL_EXT_occlusion_query_boolean - GL_EXT_polygon_offset_clamp - GL_EXT_primitive_bounding_box - GL_EXT_read_format_bgra - GL_EXT_robustness - GL_EXT_separate_shader_objects - GL_EXT_shader_framebuffer_fetch - GL_EXT_shader_integer_mix - GL_EXT_shader_io_blocks - GL_EXT_shader_samples_identical - GL_EXT_tessellation_point_size - GL_EXT_tessellation_shader - GL_EXT_texture_border_clamp - GL_EXT_texture_buffer - GL_EXT_texture_compression_dxt1 - GL_EXT_texture_cube_map_array - GL_EXT_texture_filter_anisotropic - GL_EXT_texture_format_BGRA8888 - GL_EXT_texture_rg - GL_EXT_texture_sRGB_decode - GL_EXT_texture_type_2_10_10_10_REV - GL_EXT_unpack_subimage - GL_INTEL_conservative_rasterization - GL_INTEL_performance_query - GL_KHR_blend_equation_advanced - GL_KHR_blend_equation_advanced_coherent - GL_KHR_context_flush_control - GL_KHR_debug - GL_KHR_no_error - GL_KHR_robust_buffer_access_behavior - GL_KHR_robustness - GL_KHR_texture_compression_astc_ldr - GL_KHR_texture_compression_astc_sliced_3d - GL_MESA_shader_integer_functions - GL_NV_draw_buffers - GL_NV_fbo_color_attachments - GL_NV_image_formats - GL_NV_read_buffer - GL_NV_read_depth - GL_NV_read_depth_stencil - GL_NV_read_stencil - GL_OES_EGL_image - GL_OES_EGL_image_external - GL_OES_EGL_sync - GL_OES_compressed_ETC1_RGB8_texture - GL_OES_copy_image - GL_OES_depth24 - GL_OES_depth_texture - GL_OES_depth_texture_cube_map - GL_OES_draw_buffers_indexed - GL_OES_draw_elements_base_vertex - GL_OES_element_index_uint - GL_OES_fbo_render_mipmap - GL_OES_geometry_point_size - GL_OES_geometry_shader - GL_OES_get_program_binary - GL_OES_gpu_shader5 - GL_OES_mapbuffer - GL_OES_packed_depth_stencil - GL_OES_primitive_bounding_box - GL_OES_required_internalformat - GL_OES_rgb8_rgba8 - GL_OES_sample_shading - GL_OES_sample_variables - GL_OES_shader_image_atomic - GL_OES_shader_io_blocks - GL_OES_shader_multisample_interpolation - GL_OES_standard_derivatives - GL_OES_stencil8 - GL_OES_surfaceless_context - GL_OES_tessellation_point_size - GL_OES_tessellation_shader - GL_OES_texture_3D - GL_OES_texture_border_clamp - GL_OES_texture_buffer - GL_OES_texture_cube_map_array - GL_OES_texture_float - GL_OES_texture_float_linear - GL_OES_texture_half_float - GL_OES_texture_half_float_linear - GL_OES_texture_npot - GL_OES_texture_stencil8 - GL_OES_texture_storage_multisample_2d_array - GL_OES_vertex_array_object - GL_OES_vertex_half_float - GL_OES_viewport_array
Please describe your problem:
Tried to install F-Droid with adb install F-Droid.apk
error: no devices/emulators found adb: error: failed to get feature set: no devices/emulators found - waiting for device -
What were you expecting?:
It to install.
Additional info:
I’ve verified the kernel modules are loaded already.