Assigned
Status Update
No update yet.
Comments
th...@gmail.com
Same issue here
vi...@google.com
vi...@google.com
Same issue here
th...@gmail.com
Me too.
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x60000000
Failed to open vm 3
Failed to create HAX VM
No accelerator found.
failed to initialize HAX: Invalid argument
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x60000000
Failed to open vm 3
Failed to create HAX VM
No accelerator found.
failed to initialize HAX: Invalid argument
th...@gmail.com
Same problem here
hi...@google.com
hi...@google.com
Hi all,
Thanks for bringing this to our attention. We are working with Intel on how to fix it, and have reproduced the problem in-house as well. Currently there doesn't seem to be a simple workaround. It also looks like macOS 10.13 added new security features that block kernel extensions such as HAXM without explicit user intervention, so we will need to streamline the install part as well.
In the meantime, we've tested Hypervisor.Framework which seems to work on 10.13. Try running the emulator on Canary channel 26.1.x (API 25/26 recommended) with Hypervisor.Framework; put the text "HVF = on" in ~/.android/advancedFeatures.ini (create this file if it doesn't exist already).
Frank
Thanks for bringing this to our attention. We are working with Intel on how to fix it, and have reproduced the problem in-house as well. Currently there doesn't seem to be a simple workaround. It also looks like macOS 10.13 added new security features that block kernel extensions such as HAXM without explicit user intervention, so we will need to streamline the install part as well.
In the meantime, we've tested Hypervisor.Framework which seems to work on 10.13. Try running the emulator on Canary channel 26.1.x (API 25/26 recommended) with Hypervisor.Framework; put the text "HVF = on" in ~/.android/advancedFeatures.ini (create this file if it doesn't exist already).
Frank
so...@google.com
so...@google.com
(x86 32-bit images only on that for now, as well)
so...@google.com
Worked perfect, thanks
so...@google.com
Thanks, Frank. Life is good again!
so...@google.com
A further investigation from google side revealed something abnormal with the device file created by Intel HAXM. It is expected that HAXM will create a device file representing VMs under "/dev/hax_vm/vmXX" where XX is VM ID. However, on high sierra, the device file created is put under "/dev/hax*/vmXX". The "*" here definitely suggests something unusual, which is not a typical file or directory name. Since there should be changes to HAXM binary so far, High Sierra should be changing something that HAXM should be adapted to.
Hope this could be a hint for Yu Ning for further investigation.
Hope this could be a hint for Yu Ning for further investigation.
ki...@gmail.com
Could you please provide some step-by-step instructions on how to enable Hypervisor.Framework? Adding "HVF = on" in ~/.android/advancedFeatures.ini didn't have any effect for me, I'm still getting "failed to initialize HAX: Invalid argument"...
so...@google.com
That's weird, can you supply the faulting AVD's config.ini?
You'll need to run it on a 32-bit x86 AVD, as we don't support running Hypervisor.Framework on 64-bit x86 AVD's currently.
Here is what I do:
1. Go to AVD Manager
2. Create a new AVD (API level 25 or 26 recommended):
a. "Create Virtual Device" > "Next" (Nexus 5X should be selected)
b. Image description: should be "Android 7.1.1" or "Android API 26" images in there that are not grayed out; if not, click the "Download" link and try the process again.
c. Make sure it is a x86 (not x86_64) image.
3. Finish the AVD creation process (Default settings should work)
4. Start the AVD (hit the "play" button on the AVD manager for the AVD you just created).
You'll need to run it on a 32-bit x86 AVD, as we don't support running Hypervisor.Framework on 64-bit x86 AVD's currently.
Here is what I do:
1. Go to AVD Manager
2. Create a new AVD (API level 25 or 26 recommended):
a. "Create Virtual Device" > "Next" (Nexus 5X should be selected)
b. Image description: should be "Android 7.1.1" or "Android API 26" images in there that are not grayed out; if not, click the "Download" link and try the process again.
c. Make sure it is a x86 (not x86_64) image.
3. Finish the AVD creation process (Default settings should work)
4. Start the AVD (hit the "play" button on the AVD manager for the AVD you just created).
Description
What
User experience
What type of Android issue is this?
Other issue
What steps would let us observe this issue?
What did you expect to happen?
Open angle preferences
What actually happened?
Angle preferences didn't open
What was the effect of this issue on your device usage, such as lost time or work?
Did not observe, or no opinion
When
Time and frequency
When did this happen?
Nov 15, 2024 7:00 AM GMT+05:30
How often has this happened?
Every time
Where
Component
Suggested component: <not visible> (1630575)
Build and device data
- Build Number: google/cheetah_beta/cheetah:15/BP11.241025.006/12620009:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 244433035 (24.44.33 (260400-694629214))
System App (Updated)
Android System WebView
com.google.android.webview
Version 677803942 (131.0.6778.39)
System App (Updated)
Network operator: Dialog
SIM operator: Dialog
Network operator: Sri Lanka Telecom Mobitel
SIM operator: Sri Lanka Telecom Mobitel
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)https://developer.android.com/preview/feedback#feedback-app .
To learn more about our feedback process, please visit