HAXM not working on Core 2 Duo Macs: installs, but won't start images (black screen)

HAXM not working on Core 2 Duo Macs: installs, but won't start images (black screen)

 

HAXM 1.1.0 is not loading x86 atom image on fresh Yosemite install (core 2 duo): it goes straight to a black screen.

I can run ARM images, but when I try to run an Atom x86 image (android 4.4.2, nexus 5 clone), it goes to a black screen and sits there doing nothing. The emulator output reports "HAX is working and emulator runs in fast virt mode" before going to the black screen emulator window.

Never had an older version of HAXM installed, so don't think its the "old haxm verison doesn't work on mavericks/yosemite" problem.

Details about my setup:

  • "AVD_for_Nexus_5", Android 4.4.2, Atom x86
  • Hardware: 2.8 GHz Core 2 Duo (Macbook Pro 17, mid2009)
  • Fresh install of Yosemite, no virtualization software installed besides HAXM
  • HAXM 1.1.0 for "10.9 and above" installed, downloaded from Intel's webiste yesterday
  • GPU: have tried both enabled/disabled with no effect: black screen either way

Any ideas?

36 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Try HAXM 5.1 (1.1.1). It should work with Atom x86 system image.

Thanks for the suggestion, I realized I am actually using HAXM 1.1.1 already, so I am actually having this problem with HAXM 1.1.1.... sorry for the confusion.

-Seth

I'm finding the same thing here, also on a Core 2 Duo, using HAXM 1.1.1. Nothing I do will get the emulator to give me more than a blank screen. The log says HAXM is working, but then the emulator just seems to stall. Works fine without HAXM—if I take a working ARM AVD and change it to Intel, I just get a black screen in the emulator and Android never starts. I've tried a lot of different settings.

Any ideas? I've got an app I need to take a variety of different-screen-sized screenshots in, and not being able to use HAXM is making it an extremely painful process :)

Thanks,

Matt

 

(Erroneous post removed.)

Thank you so much for getting back to me on this Matt!

How much RAM are your AVDs set to use?

I tried reinstalling with the memory turned down to 1024, but unfortunately I still get a black screen. It does seem like there may be issues with HAXM on Core 2 Duo machines?

anyway, thanks again for following up on this... a promising lead even if it didn't work in the end :-)

-Seth

Ah, no—sorry, it didn't work for me, either, which is why I quickly tried to delete that last post. (When I couldn't find a "delete", I changed the "Status" to "Not Published". I didn't realise that it would change back to Published for no readily apparent reason...)

 

What had actually happened was that turning the memory down to 1024 meant that my test AVD was too big to run under HAXM at all, so it had dropped back to software emulation without me realising. My joy at seeing the Android logo appear was crushed about ten minutes later when I realised the Android logo was *still* there because the software emulator was so slow that the phone was still booting. :(

So, no, no joy here. I'm afraid I've given up for now; I'm postponing my Android work in favour of iOS for a while.

Matt

Matt, are you using Windows or Mac? I'll see if there's a way to report an issue/defect in HAXM, but would be good to isolate if its a processor issue, or if its a processor+OS issue. Probably everyone else has upgraded to newer processors :-P

Quote:

Seth N. wrote:

 

Matt, are you using Windows or Mac? I'll see if there's a way to report an issue/defect in HAXM, but would be good to isolate if its a processor issue, or if its a processor+OS issue. Probably everyone else has upgraded to newer processors :-P

(I thought it was worth repeating my SO answer here!)

I'm on a 2009 iMac: iMac 10,1; Intel Core 2 Duo 3.06GHz; Yosemite.

Matt

I booted my mac (2009 MacBook Pro 17", core 2 duo 2.8 GHz yosemite) into Windows 7, and HAXM seemed to work there with the same hardware. So the issue seems to be:

HAXM 5.1 does not work on Core 2 Duo Macs (running yosemite?)

-Seth

I'm experiencing the same exact problem. ARM images work, x86 and x84-64 images don't.

I'm on Yosemite 10.10.1 on a MacBook Pro (13-inch, Mid 2010). Latest Android Studio and HAMX 1.1.1.

Intel: Help?

Same problem exists for me too.  Yosemite 10.10.1 on MacBook Pro 15-inch, Late 2008.

However, I was able to get a Nexus 4 arm configuration to work.  Nexus 5 or above wont work for me.

I've renamed the thread to be clearer, but to clarify for an Intel people that may view this (how do we file a defect report?), I've looked up all the Macs involved so far, and they are all Core 2 Duo machines.

I tried booting my Core 2 Duo into Windows directly, and HAXM /does/ seem to work there, so the issue is with Core 2 Duos running OSX.

The issue may well be with the nexus 5 avd?  Have you tried changing the skin setting to  WVGA800? Even if this doesn't work, I suggest trying a different AVD to see if it gives the same results.

Hi Colleen,

Thanks for responding! I'd started to think I'd never get back to Android development...

I've just tried with the WVGA800 skin. As before, HAXM seems to launch fine, but the emulator never gets further than a blank screen, even if I leave it for several minutes (CPU is idle.) Gist of the console output here. I've tried it with and without the "Host GPU" option checked; results are the same.

I've also just tried with an AVD based off the stock '4.7" WXGA by Generic' definition, choosing Android 5.0.1/Intel Atom (x86)/WXGA800 skin. Same results. I've tried with other definition, skins, and settings.

Let me know if you need any more info.

Cheers,

Matt

Try reading thru the various solutions to that message here http://stackoverflow.com/questions/3073046/waiting-for-home-android-process-acore-to-be-launched - especially the 2014 ones. I know you've done some of them, but there might be something you didn't try.

I have tried ALL of these (different AVDs, different GPUs, different GPU settings, etc), this issue seems like it may occur on all OSX Core 2 Duos.

The only "fix" I've found is either:

- Use a core i5/i7 Mac

OR

- Boot the core2duo mac into windows

-Seth

This has been escalated within Intel as a bug and developers will be looking at the issue.

I have tried all the solutions and permutations as well, experiencing the issue exactly as Seth does. No x86 image will work under OS X 10.10.1 on my MacBook Pro (13-inch, Mid 2010, Core 2 Duo). Arm images work, but they are appallingly slow.

I'm having the same issue on Mavericks, 10.9.5, so its not isolated to Yosemite.  I'm also on a old Core2 Duo processor (late model 2009 macbook pro).

Installed IntelHAXM_1.1.1_for_10_9_and_above.dmg, and v 5.2 of the Android HAXM component.

 

Hello guys I'm also having the same issue on Yosemite, 10.10.1. I own a MacBook Pro (mid 2009) with a 2.26 Ghz Intel Core 2 Duo processor.

I also have installed the latest Intel HAXM_1.1.1_for_10_9_and_above.dmg, and the Android HAXM component.

What happens is that when I run the emulater I get:

/Users/chrisCole/Library/Android/sdk/tools/emulator -avd Nexus_5_API_21_x86 -netspeed full -netdelay none
HAX is working and emulator runs in fast virt mode
emulator: emulator window was out of view and was recentered

 

And the emulated screen of the AVD is plain black; I really need to start developing my app and this is bug quite a bummer! 
:((((

Another Core 2 Duo widow...

Today I "upgraded" to the latest Android Studio and HAXM has stopped working for me too. It used to work fine before the "upgrade" :(

Mac mini - Mid 2010
2.4 Ghz Intel Core 2 Duo
8GB Memory
OSX 10.9.5
HAXM 1.1.1 (latest)
Latest Android Studio, SDK, etc.

Same, symptoms as first post with any x86 image (32 bit); output reports "HAX is working and emulator runs in fast virt mode" before going to the black screen emulator window.

As a quick fix, is there anywhere I can download the old versions of HAXM? I'm am positive I could find one that works because it was working just before the upgrade today. So I know my hardware and setup is capable of working just fine.

Thanks
 

 

I'm having the same issue:

Mac osx 10.10.1

Macbook pro early 2008

2.5GHz intel  core 2 duo

4G memory

Android studio 1.0.1

AVD Nexus 5 API 21 x86 google APIs x86

AVD Ram 1024k (hax is configured by default to 1G) on macs with 4G so adjust AVD in Advanced to 1024k so would run in x86 mode.

With Memory monitor - it goes through:

1) No Connected Devices on

2) Emulator unknown emulator -5554 [offline]

3)  No Connected Devices

Last message:

HAX is working and emulator runs in fast virt mode

One person reported that they first saw the problem when "upgrading" to HAXM 1.1.1 - does anyone know where to pick up a version of HAXM which works with the dual core 2 duo?

johnh...

Hi,

I am having this issue as well. On a Macbook Pro (15" 2009) running 10.9.5 that USED to work with HAXM (was a while ago, don't know what changed)

I am also having this issue on my 2006 Mac Pro also running 10.9.5.

Both say HAX is working and emulator runs in fast virt mode

and no errors in dmesg I believe loading the driver.

:(

This is a known issue and HAXM driver will not support emulating a 64 bit system image on Intel systems based on Core microarchitecture. Please refer to release notes.

For the issue on 32bit, we are debugging it and will provide solution when ready

Quote:

Tao Wang (Intel) wrote:

This is a known issue and HAXM driver will not support emulating a 64 bit system image on Intel systems based on Core microarchitecture. Please refer to release notes.

For the issue on 32bit, we are debugging it and will provide solution when ready

As far as i've read these are the hardware requirements for HAXM to work on a Mac (https://software.intel.com/en-us/android/articles/installation-instructi...):

  • Intel® VT-x

    • According to Wikipedia (sigh...), this feature gives x86 virtualization capabilities to the processor, and in the same article it says that if you type on the (Mac) terminal the following command and you get "VMX" this means that you have this feature.

      $ sysctl machdep.cpu.features
    • Here is the article: http://en.wikipedia.org/wiki/X86_virtualization#Intel_virtualization_.28...
  • Intel® EM64T
    • ​This simply means that you have an Intel 64-bit processor.
  • Execute Disable Bit
    • This is a security feature.

I have a late 2009 Macbook Pro and according to the documentation, this machine should have any of two processors:

  1. Intel® Core™ 2 Duo (P7550), product page: http://ark.intel.com/products/42014/Intel-Core2-Duo-Processor-P7550-3M-C...
  2. Intel® Core™ 2 Duo (P8400), product page: http://ark.intel.com/products/35569/Intel-Core2-Duo-Processor-P8400-3M-C...

The P8400 processor clearly shows that it has the Intel® VT-x feature but the P7550 has a legend that says that it depends on the "order", which means that you may need to test it by yourself on your particular machine.

To find out which processor you own type on the terminal:

$ sysctl -n machdep.cpu.brand_string

On my case:

MacBook Pro Late 2009 Specs

Which means that my system has Intel's x86 virtualization feature. But maybe HAXM just fails on a "safe way" validating the P7550 processor on the machine and maybe P8400 processors don't suffer of this condition.

Can anyone please post their processor model to see if this only happens to the P7550 processor?

My processor is:

Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz

@Tao Wang: my issue is running 32-bit images (and reading the comments, almost everyone is having trouble with 32-bit images, I think everyone knows 64-bit images won't work on core2duo).

-Seth

@Tao Wang: I finally found the Release Notes you where talking about.... They are in the zip when you download the package from here: https://software.intel.com/en-us/android/articles/intel-hardware-acceler...

Never read them before because HAXM was automatically installed alongside the Android SDK located here: http://developer.android.com/sdk/index.html

Here it says: HAXM driver does not support emulating a 64 bit system image on Intel systems based on Core microarchitecture (Core, Core2 Duo etc.). All systems based on Nehalem and beyond are supported. (Corei3, Core i5 and Core i7 machines).

I've recently formatted my computer from a scratch from Mavericks to Yosemite, and I've used to run the Android emulator on my previous installation (I ignore if it was using HAXM but it was an old installation).

Also I will like to know (I'm sure many will do) if future HAXM releases will ever support Core microarchitecture to see if we should invest in a new laptop.

It would also be great that you add to the requirements of the HAXM download site EXPLICIT notice that Core microarchitectures form Mac are not supported anymore, and maybe so in the Android SDK download page, so you can save A LOT of time to many of us who are out there investigating why the emulator on our computer doesn't work.

Quote:

Tao Wang (Intel) wrote:

This is a known issue and HAXM driver will not support emulating a 64 bit system image on Intel systems based on Core microarchitecture. Please refer to release notes.

For the issue on 32bit, we are debugging it and will provide solution when ready

 

Been facing the same problem in my macbook white (mid 2010) which is running 2.4 GHz Intel Core 2 Duo.

It seems like most of the users who facing "black screen" when running emulator are using Core 2 Duo.

Glad to found this thread and do keep us posted once there are any updates.

Thanks for your hard work Mr. Tao Wang :)

 

Is there any progress on this issue? I have an macbook air with core 2 duo, and I'm not able to run the android studio emulator at the moment. Greatly appreciate an update.

Intel HAXM hotfix 1.1.2 for Mac OS X is already available.

Quote:

Ionel Mitel (Intel) wrote:

Intel HAXM hotfix 1.1.2 for Mac OS X is already available.

Macbook white 2010 2.4ghz Core2Duo. It reboot but it could be just a bad avd configuration. Anyway really happy to finally see the android logo, thanks for the fix guys!

Could you post here your AVD configuration?

Nevermind, tried again and it worked. Good job guys.
BTW my avd conf: Nexus 5 API 22, Google API x86, gpu host yes, ram 1024mb (SD card the same).

Great! good Information i have a similar problem, thanks!

Quote:

Alessio B. wrote:

Nevermind, tried again and it worked. Good job guys.
BTW my avd conf: Nexus 5 API 22, Google API x86, gpu host yes, ram 1024mb (SD card the same).

Leave a Comment

Please sign in to add a comment. Not a member? Join today