Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

Android Build a Simple Android App Getting Started with Android Running the Fun Facts Project

kabir k
PLUS
kabir k
Courses Plus Student 18,036 Points

My FunFacts app doesn't show up in the AVD of the emulator

At 00:37 of the Running the FunFacts Project video, my FunFacts app doesn't show up in the AVD of the emulator, after pressing Run

Does anyone know how to fix this problem?

I saw the following texts in red in the Android Monitor at the bottom of the Android Studio, after pressing Run, could that have something to do with the FunFacts app not showing up in the AVD?

05-01 21:57:50.474 1888-1913/com.google.android.gms.persistent E/LevelDB: LevelDB[] leaked, don't forget to call close()

05-01 22:25:52.872 1137-1931/? E/Drm: Failed to find drm plugin

Thanks.

2 Answers

Gnani Pasupula
Gnani Pasupula
3,915 Points

Post your code , so that i could see the problem

Gnani Pasupula
Gnani Pasupula
3,915 Points

I think you should wait for some time , the default emulator is slow.Use Genymotion , it is fast.

kabir k
kabir k
Courses Plus Student 18,036 Points

I would like to use the default emulator but thanks, anyway.

Dennis Brown
Dennis Brown
28,742 Points

I had this exact issue with React-Native and the AVD, usually because Gradle was impatient, and would timeout on slow devices/system. In my experience it would not show the timeout error unless you ran the compiler with the debug flag, so it would look like all was fine. You can manually run debug with gradle to see the exact error.

./gradlew <project folder> --debug

I'm not sure where yours compiles the apk to, but with the device open on the home screen, you can always send the compiled apk to the device without having to recompile it every single time. Here is the folder Gradle uses with RN, but it may be a little different but close.

adb install android/<project folder>/build/outputs/apk/<apk file>

I'm sorry that I cannot provide a concrete answer, and I really helps someone in some way; I wanted to at least try to shed some light on the question.