Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Java

Posted by Bunyod Kh
Bunyod Kh
10,221 Points

Problem: 'HAXM is not working and emulator runs in emulation mode'

I had these errors:

resize2fs 1.42.13 (17-May-2015) The filesystem is already 140800 (4k) blocks long. Nothing to do! .. .. .. HAXM is not working and emulator runs in emulation mode .. ..

Emulator is running but android is not loading? What does it mean above mentioned lines?

1 Answer

Steve Hunter
Steve Hunter
57,712 Points
Steve Hunter
Steve Hunter
57,712 Points

Hi there,

Have a read thorugh this post and reinstall your HAXM accelerator. That might fix this.

If not, shout back!

Steve.

Bunyod Kh
Bunyod Kh
10,221 Points

Thanks. I've installed Genymotion. Default em. was headache for me. Other question: is it possible to use newer versions of Android in Geny or we can only choose from its list?

Bunyod Kh
Bunyod Kh
10,221 Points

And by the way another question. sorry.

I'm getting these messages in the logcat :

02-11 07:06:28.574 1394-1394/? E/OpenGLRenderer: Getting MAX_TEXTURE_SIZE from GradienCache 02-11 07:06:28.582 1394-1394/? E/OpenGLRenderer: Getting MAX_TEXTURE_SIZE from Caches::initConstraints()

What does it mean? App is working but I don't know how it is affecting to the work of the app.

Steve Hunter
Steve Hunter
57,712 Points

The default emuator is a pain, yes. Genymotion works far more smoothly!

You should be able to use all SDK versions in the emulator - you will need to ake sure you've downloaded the right ones, though.

And the random warnings and errors that you see, such as texture stuff, won't affect your app. The emulator emulates everything that a phone can do. It doesn't just sit there waiting for your app to run, so you'll see a constant scroll of messages in the Logcat. When you run your app, the Logcat should be filtered to just messages generated by your app so you know what's going on.

Steve.