Genymotion Wifi not supported by VirtualBox version?

Hey garuda folk,

I have been using Genymotion as a phone replacement (so all stuff is on one device). It’s been one year the last time but now when I try to use Genymotion, it cannot connect to Internet.

I have been searching and found a support answer which says, this could be due to Genymotion not yet supporting VirtualBox ≥7.1.

Does anyone have the same problem? I cannot register on Signal.

Maybe you have additional experience in running Android apps on Garuda Linux and could suggest a good working alternative?

FYI:

System:
  Kernel: 6.11.8-zen1-2-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=11d26dd1-3904-490b-9e30-1b11c6731dc0 rw rootflags=subvol=@
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
  Desktop: KDE Plasma v: 6.2.3 tk: Qt v: N/A info: frameworks v: 6.8.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
  Type: Detachable System: SHIFT product: SHIFT13mi v: N/A
    serial: <superuser required>
  Mobo: SHIFT model: SHIFT13mi-pcb v: 06 serial: <superuser required>
    part-nu: 0752454247011 uuid: <superuser required> UEFI: American Megatrends
    LLC. v: 5.19 date: 01/13/2023
Battery:
  ID-1: BAT0 charge: 23.8 Wh (100.0%) condition: 23.8/53.9 Wh (44.1%)
    volts: 13.2 min: 11.6 model: Intel SR 1 SR Real Battery type: Unknown
    serial: <filter> status: full
CPU:
  Info: model: 11th Gen Intel Core i5-1135G7 bits: 64 type: MT MCP
    arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
    process: Intel 10nm family: 6 model-id: 0x8C (140) stepping: 1
    microcode: 0xB8
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB
    desc: 4x1.2 MiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 2181 min/max: 400/4200 scaling: driver: intel_pstate
    governor: powersave cores: 1: 2181 2: 2181 3: 2181 4: 2181 5: 2181 6: 2181
    7: 2181 8: 2181 bogomips: 38707
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
    alternate: xe arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
  Device-2: Orbbec 3D USB 2.0 Camera driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:3
    chip-ID: 2bc5:051e class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_x11 driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: BOE Display 0x08dd built: 2019 res: 1920x1080
    hz: 60 dpi: 166 gamma: 1.2 size: 294x165mm (11.57x6.5") diag: 337mm (13.3")
    ratio: 16:9 modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.7-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Xe Graphics (TGL GT2)
    device-ID: 8086:9a49 memory: 15.18 GiB unified: yes
  API: Vulkan v: 1.3.295 layers: 4 device: 0 type: integrated-gpu name: Intel
    Xe Graphics (TGL GT2) driver: mesa intel v: 24.2.7-arch1.1
    device-ID: 8086:9a49 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
    (LLVM 18.1.8 256 bits) driver: mesa llvmpipe v: 24.2.7-arch1.1 (LLVM
    18.1.8) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:a0c8 class-ID: 0403
  Device-2: Orbbec 3D USB 2.0 Camera driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:3
    chip-ID: 2bc5:051e class-ID: 0102 serial: <filter>
  API: ALSA v: k6.11.8-zen1-2-zen status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.2.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 00:14.3
    chip-ID: 8086:a0f0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: vboxnet0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:6 chip-ID: 8087:0026
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0000
Drives:
  Local Storage: total: 953.87 GiB used: 240.75 GiB (25.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lexar model: SSD NM6A1 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: V1.25D temp: 34.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 48.14 GiB size: 48.14 GiB (100.00%)
    used: 45.94 GiB (95.4%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
  ID-2: /boot/efi raw-size: 501 MiB size: 500 MiB (99.80%)
    used: 588 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p6 maj-min: 259:5
  ID-3: /home raw-size: 280.27 GiB size: 280.27 GiB (100.00%)
    used: 194.82 GiB (69.5%) fs: btrfs dev: /dev/nvme0n1p8 maj-min: 259:7
  ID-4: /var/log raw-size: 48.14 GiB size: 48.14 GiB (100.00%)
    used: 45.94 GiB (95.4%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
  ID-5: /var/tmp raw-size: 48.14 GiB size: 48.14 GiB (100.00%)
    used: 45.94 GiB (95.4%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:6
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.09 GiB used: 10.2 MiB (0.0%)
    priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 3.91 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p9 maj-min: 259:8
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 31.09 GiB
    used: 10.03 GiB (32.3%)
  Processes: 341 Power: uptime: 4h 25m states: freeze,mem,disk
    suspend: s2idle avail: deep wakeups: 1 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 12.42 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 256
    default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 2455 libs: 575 tools: pamac,paru Compilers:
    clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: Bash v: 5.2.37
    running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
  System install date:     2023-04-30
  Last full system update: 2024-11-16
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            

Thank you a lot.

Okay, I apparently had selected VirtualBox as the hypervisor (emulation base) in the Genymotion settings.

VirtualBox does not work anymore. It needs to be QEMU (which also came with my Gamer version of Garuda).

Here is my explanation how to change the hypervisor:

Summary:

  • use shortcut CTRL+,
  • choose “Hypervisor” tab
  • at the bottom choose QEMU as hypervisor (it actually is the sensible default, I had update problems with QEMU last year, so after my data crash I setup Genymotion with VirtualBox back then)

Now, Wifi connection works.

Thank you for making Garuda reality. It’s great!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.