Emulator setup and usage in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

Emulator Screen Resolution Impact

You run your Android app on an emulator with a very small screen resolution. What is the most likely visible effect on your app UI?

A UI elements automatically scale perfectly with no clipping or scrolling

B UI elements appear larger and some content may be clipped or require scrolling

C The app crashes immediately due to unsupported resolution

D The emulator shows a blank screen with no UI

💡 Hint

Think about how smaller screens affect layout and visibility.

When the emulator screen is small, UI elements appear bigger relative to the screen size, causing clipping or scrolling. Automatic perfect scaling is not guaranteed.

❓ lifecycle

intermediate

Emulator Network Connectivity

If your Android emulator is running but shows no internet connection, which of these is the most likely cause?

A The emulator is running an unsupported Android version

B The app code has a bug preventing network calls

C The host computer has no internet connection or the emulator network is disabled

D The emulator screen resolution is too low

💡 Hint

Check the emulator and host network settings first.

The emulator uses the host computer's network. If the host is offline or emulator network is disabled, the emulator won't have internet.

🔧 Debug

advanced

Emulator App Installation Failure

You try to install your APK on the emulator but get an error saying "INSTALL_FAILED_CPU_ABI_INCOMPATIBLE". What is the cause?

A The emulator has insufficient storage space

B The APK is corrupted

C The emulator is not running

D The APK was built for a CPU architecture not supported by the emulator

💡 Hint

Think about CPU types and emulator compatibility.

This error means the APK's CPU architecture (like ARM) does not match the emulator's CPU (like x86).

❓ navigation

advanced

Emulator Screen Rotation Behavior

You rotate the emulator screen from portrait to landscape. What happens to your running app by default?

A The activity is destroyed and recreated, triggering lifecycle methods

B The app crashes due to unsupported orientation

C Nothing changes; the app stays in portrait mode

D The emulator resets and closes the app

💡 Hint

Consider Android activity lifecycle on configuration changes.

By default, rotating the screen causes the activity to be destroyed and recreated to apply the new layout.

🧠 Conceptual

expert

Emulator Snapshots and State

You save a snapshot of your emulator with your app running. After closing and restarting the emulator from that snapshot, what is true about your app state?

A The app resumes exactly where it left off, including UI and data in memory

B The app restarts fresh, losing all unsaved data

C The emulator boots but the app is not running

D The emulator snapshot only saves the OS state, not the app state

💡 Hint

Think about what emulator snapshots capture.

Snapshots save the entire emulator state including running apps and their memory, allowing exact resume.