Can't seem to Activate Android Subsystem on VMWare

About the question you’re submitting

Have you searched the community for a relevant issue? (use “x” to select)

Similar issues found

Detailed description

  1. Clearly state your question(s)
    A:Android Subsystem does not activate on my Fujitsu Lifebook A Series A555 on VMWare.
    It has SSE4.2 support and even so I can’t activate it, the installation is in animation and is iin animation on the launch button. So, I closed the Subsystem and Continued on to GApps hoping that it will work.The installation of Gapps is completed successfully(kind of,seen some errors in gapps logs).After the reboot, the “Android” app has an overlay of a loading screen. Behind it I can see the lauch button. In the launcher I don’t see any Google Apps.
    .

  2. Provide specific configuration and firmware version details
    CPU:Intel Core i3-5005U
    GPU:Intel HD Graphics 5000
    RAM & Storage:4GB DDR3 1600mhz(allocated 3.0GB), 1TB HDD (allocated 40GB)
    FydeOS Version:FydeOS 16, Stable Branch running on BIOS firmware

  3. Include detailed logs
    To obtain the logs, enter /var/log/messages in the Chromium browser and locate the relevant log fragment. Copy and paste it here.
    Logs:2023-06-11T08:58:19.979646Z INFO generate_camera_profile[9222]: Starting to generate media profiles
    2023-06-11T08:58:20.446748Z ERR arc-setup-precreate[9193]: ERROR arc-setup: [safe_fd.cc(598)] Failed to unlink “media_profiles.xml”: No such file or directory (2)
    2023-06-11T08:58:20.447266Z ERR arc-setup-precreate[9193]: ERROR arc-setup: [safe_fd.cc(138)] Owner uid is 0 instead of 603
    2023-06-11T08:58:20.497270Z ERR arc-setup-precreate[9193]: ERROR arc-setup: [safe_fd.cc(598)] Failed to unlink “platform.xml”: No such file or directory (2)
    2023-06-11T08:58:46.227074Z WARNING secanomalyd[2221]: Bus::SendWithReplyAndBlock took 25101ms to process message: type=method_call, path=/org/chromium/SessionManager, interface=org.chromium.SessionManagerInterface, member=RetrieveActiveSessions
    2023-06-11T08:58:46.227250Z ERR secanomalyd[2221]: Failed to call method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: object_path= /org/chromium/SessionManager: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    2023-06-11T08:58:46.227336Z ERR secanomalyd[2221]: CallMethodAndBlockWithTimeout(…): Domain=dbus, Code=org.freedesktop.DBus.Error.NoReply, Message=Error calling D-Bus method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    2023-06-11T08:58:46.227424Z ERR secanomalyd[2221]: Error making D-Bus proxy call to interface ‘/org/chromium/SessionManager’: Error calling D-Bus method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    2023-06-11T08:59:14.747520Z INFO kernel: [ 4039.788945] psmouse serio1: VMMouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
    2023-06-11T08:59:15.373290Z INFO kernel: [ 4040.393585] psmouse serio1: resync failed, issuing reconnect request
    2023-06-11T08:59:40.416884Z ERR session_manager[945]: ERROR session_manager: [android_oci_wrapper.cc(133)] Timed out to wait on run_oci exit
    2023-06-11T08:59:40.416969Z INFO session_manager[945]: INFO session_manager: [system_utils_impl.cc(130)] Sending signal 9 to PID -9145 as UID 4294967295
    2023-06-11T08:59:41.112313Z INFO session_manager[945]: INFO session_manager: [upstart_signal_emitter.cc(50)] Emitting stop-arc-instance Upstart signal
    2023-06-11T08:59:41.432911Z ERR patchpaneld[2237]: ERROR patchpaneld: [arc_service.cc(400)] ArcService was not running
    2023-06-11T08:59:41.466621Z WARNING secanomalyd[2221]: Bus::SendWithReplyAndBlock took 25036ms to process message: type=method_call, path=/org/chromium/SessionManager, interface=org.chromium.SessionManagerInterface, member=RetrieveActiveSessions
    2023-06-11T08:59:41.466651Z ERR secanomalyd[2221]: Failed to call method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: object_path= /org/chromium/SessionManager: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    2023-06-11T08:59:41.466669Z ERR secanomalyd[2221]: CallMethodAndBlockWithTimeout(…): Domain=dbus, Code=org.freedesktop.DBus.Error.NoReply, Message=Error calling D-Bus method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    2023-06-11T08:59:41.466683Z ERR secanomalyd[2221]: Error making D-Bus proxy call to interface ‘/org/chromium/SessionManager’: Error calling D-Bus method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    2023-06-11T08:59:41.708140Z ERR session_manager[945]: ERROR session_manager: [session_manager_impl.cc(2084)] Starting Android container failed.
    2023-06-11T08:59:41.708329Z ERR session_manager[945]: ERROR session_manager: [dbus_util.cc(13)] CreateError(…): Domain=dbus, Code=org.chromium.SessionManagerInterface.ContainerStartupFail, Message=Starting Android container failed.
    2023-06-11T08:59:57.309042Z INFO periodic_scheduler[2212]: crash_sender: running /sbin/crash_sender
    2023-06-11T08:59:57.669446Z INFO periodic_scheduler[2212]: crash_sender: job completed
    2023-06-11T09:02:44.471402Z INFO ml_service[3891]: SIGKILL sent to the worker process: 4
    2023-06-11T09:05:26.577079Z INFO kernel: [ 4411.620094] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600
    2023-06-11T09:05:34.858125Z INFO kernel: [ 4419.900772] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600
    2023-06-11T09:05:39.344103Z INFO kernel: [ 4424.385185] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600
    2023-06-11T09:05:39.567442Z INFO kernel: [ 4424.570918] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600
    2023-06-11T09:05:40.622119Z INFO kernel: [ 4425.664184] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600
    2023-06-11T09:05:59.998068Z INFO kernel: [ 4445.040827] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600
    2023-06-11T09:10:01.702104Z INFO kernel: [ 4686.744263] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600
    2023-06-11T09:10:15.385741Z INFO run_oci[10665]: INFO run_oci: [run_oci.cc(550)] Starting container arc-rec
    2023-06-11T09:10:15.727056Z INFO run_oci[10665]: INFO run_oci: [run_oci.cc(809)] Container arc-rec running
    2023-06-11T09:10:24.269119Z NOTICE kernel: [ 4709.311768] Chromium OS LSM: sb_mount Mounting a filesystem with ‘exec’ flag requires CAP_SYS_ADMIN in init ns obj=“/vendor” pid=11259 cmdline=“mount -o ro -t auto /dev/block/bootdevice/by-name/vendor /vendor”
    2023-06-11T09:10:24.269150Z NOTICE kernel: [ 4709.311777] Chromium OS LSM: sb_mount dev=/dev/block/bootdevice/by-name/vendor type=ext3 flags=0x8001
    2023-06-11T09:10:24.272159Z NOTICE kernel: [ 4709.314098] Chromium OS LSM: sb_mount Mount path with symlinks prohibited obj=“/system/product” pid=11261 cmdline=“mount -o ro -t auto /dev/block/bootdevice/by-name/product /product”
    2023-06-11T09:10:24.272177Z NOTICE kernel: [ 4709.314106] Chromium OS LSM: sb_mount dev=/dev/block/bootdevice/by-name/product type=ext3 flags=0x8001
    2023-06-11T09:10:24.272179Z NOTICE kernel: [ 4709.314630] Chromium OS LSM: sb_mount Mount path with symlinks prohibited obj=“/system/product” pid=11261 cmdline=“mount -o ro -t auto /dev/block/bootdevice/by-name/product /product”
    2023-06-11T09:10:24.272184Z NOTICE kernel: [ 4709.314636] Chromium OS LSM: sb_mount dev=/dev/block/bootdevice/by-name/product type=ext2 flags=0x8001
    2023-06-11T09:10:24.273079Z NOTICE kernel: [ 4709.315386] Chromium OS LSM: sb_mount Mount path with symlinks prohibited obj=“/system/product” pid=11261 cmdline=“mount -o ro -t auto /dev/block/bootdevice/by-name/product /product”
    2023-06-11T09:10:24.273096Z NOTICE kernel: [ 4709.315392] Chromium OS LSM: sb_mount dev=/dev/block/bootdevice/by-name/product type=ext4 flags=0x8001
    2023-06-11T09:10:24.274194Z NOTICE kernel: [ 4709.316109] Chromium OS LSM: sb_mount Mount path with symlinks prohibited obj=“/system/product” pid=11261 cmdline=“mount -o ro -t auto /dev/block/bootdevice/by-name/product /product”
    2023-06-11T09:10:24.274213Z NOTICE kernel: [ 4709.316118] Chromium OS LSM: sb_mount dev=/dev/block/bootdevice/by-name/product type=squashfs flags=0x8001
    2023-06-11T09:10:24.274215Z NOTICE kernel: [ 4709.316920] Chromium OS LSM: sb_mount Mount path with symlinks prohibited obj=“/system/product” pid=11261 cmdline=“mount -o ro -t auto /dev/block/bootdevice/by-name/product /product”
    2023-06-11T09:10:24.274217Z NOTICE kernel: [ 4709.316928] Chromium OS LSM: sb_mount dev=/dev/block/bootdevice/by-name/product type=fuseblk flags=0x8001
    2023-06-11T09:13:25.840304Z ERR /usr/bin/shill[1025]: dhcpcd[9181]: eth0: renewing lease of 192.168.148.135
    2023-06-11T09:13:25.846402Z ERR /usr/bin/shill[1025]: dhcpcd[9181]: eth0: sending REQUEST (xid 0xce8abe70), next in 4.6 seconds
    2023-06-11T09:13:25.901002Z ERR /usr/bin/shill[1025]: dhcpcd[9181]: eth0: received ACK with xid 0xce8abe70
    2023-06-11T09:13:25.901092Z ERR /usr/bin/shill[1025]: dhcpcd[9181]: eth0: acknowledged 192.168.148.135 from 192.168.148.254
    2023-06-11T09:13:25.901465Z ERR /usr/bin/shill[1025]: dhcpcd[9181]: event RENEW on interface eth0
    2023-06-11T09:13:25.936246Z ERR /usr/bin/shill[1025]: dhcpcd[9181]: status changed to Bound
    2023-06-11T09:14:19.090923Z INFO run_oci[10665]: INFO run_oci: [run_oci.cc(1142)] Container arc-rec finished
    2023-06-11T09:14:19.874150Z INFO kernel: [ 4944.916514] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600
    2023-06-11T09:14:20.113067Z INFO kernel: [ 4945.155278] EXT4-fs (nvme0n1p3): re-mounted. Opts:
    2023-06-11T09:14:20.579482Z INFO kernel: [ 4945.614033] EXT4-fs (nvme0n1p3): re-mounted. Opts:
    2023-06-11T09:14:21.376871Z INFO kernel: [ 4946.406802] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=600

What happens if you create a new account and try this again?

I’ll try and keep you updated

No, the subsystem did not launch even if I in a different user. Same symptoms as the topic.

Any updates?