3 ms·
And here's the promised emulator build (from aemubins gmail account that we use to distribute debug binaries like this): https://drive.google.com/open?id=1
by lfy_google 6y ago
And here's the promised emulator build (from aemubins gmail account that we use to distribute debug binaries like this):
https://drive.google.com/open?id=1sXEQcoiNpe3Lj8yeaKLasTjqlGQwy4Oi
If you still don't get symbols from that it should be possible to build the emulator itself on macos:
install repo from depot_tools https://www.chromium.org/developers/how-tos/install-depot-tools https://www.chromium.org/developers/how-tos/install-depot-to...
pip install absl-py
pip install urlfetch
mkdir emu
cd emu
repo init -u https://android.googlesource.com/platform/manifest -b emu-master-dev --depth=1
repo sync -qcj 4
cd external/qemu
python android/build/python/cmake.py
# run
objs/emulator -avd avdName -no-snapshot
Debugging:
# when it spins:
# method 1: go to activity monitor -> sample process, send over the result
# method 2: lldb
lldb
process attach --pid <pid-of-qemu-system-<arch>>
bt all #send it over
# method 3: guest process taking CPU
adb shell top
- kaixi 6y agoSorry, I'm not an expert. What am I supposed to do with the emulator-symbols.zip?
- lfy_google 6y agoReplace your current emulator install; delete $ANDROID_SDK_ROOT/emulator then unzip it there so theres $ANDROID_SDK_ROOT/emulator again. $ANDROID_SDK_ROOT, if not set, should be set to the SDK location in Android Studio > Preferences > Android SDK (SDK path will show up there). Set it in your ~/.bash_profile too so it's there next time for running the emulator from the command line. The AVD config.ini can be found in ~/.android/avd/nameofAvd.avd/config.ini .