Emulator crashes on load() about android_env HOT 7 CLOSED

@AdamIshay could you solve this issue on your system?

from android_env.

Hello @AdamIshay, could you check the locations of the Android Emulator, SDK and its associated tools (adb etc)? They're usually on your home directory, but it looks like you're passing /path/Android/Sdk/emulator/emulator which normally doesn't seem like a valid path. Please see https://github.com/deepmind/android_env/blob/main/docs/emulator_guide.md#ready-to-use and https://github.com/deepmind/android_env/blob/main/docs/instructions.md#create-the-environment.

from android_env.

@kenjitoyama thanks for your input. so "../Android/Sdk/emulator/emulator" is not the correct path? Got this same path from https://github.com/deepmind/android_env/blob/main/docs/instructions.md#create-the-environment

from android_env.

Hello @ouya99, normally the emulator is installed in the home directory, so using a relative path is probably not right as the working directory of the binary may change depending on the script location. It's better to use an absolute path.

from android_env.

python3 run_random_agent.py --avd_name='Pixel_XL_API_30' --android_avd_home='/home/username/.android/avd' --android_sdk_root=/home/username/Android/Sdk/ --emulator_path=/home/username/Android/Sdk/emulator/emulator --adb_path=/home/username/Android/Sdk/platform-tools/adb --num_steps=1000 --task_path=/home/username/Dev/android_env/examples/pong_default.textproto

@kenjitoyama this code solves the issue mentioned here. I think @AdamIshay had missed the error message stating that a directory (avd or sdk) had not been found. Yet now I am getting another error

E0622 00:49:36.111660 140665491404608 adb_controller.py:202] self._adb_shell.before: b"adb server version (39) doesn't match this client (41); killing...\r\n* daemon started successfully\r\nadb: device 'emulator-15414' not found\r\n" E0622 00:49:36.111877 140665491404608 adb_controller.py:203] Could not start ADB shell. Try 1 of 20.

from android_env.

@kenjitoyama ok, got it working after fixing adb version mismatch (hint: just remove the global adb installation, one is enough)

Thank you. You might close the issue

from android_env.

@ouya99 cool, thanks for confirming. I'll close the issue for now given that the OP was probably using the wrong path to the required files.

from android_env.