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.

Practice

1. What is the main purpose of using an emulator in Android development?

easy

A. To test apps without needing a physical device

B. To write code faster

C. To create app icons

D. To publish apps to the Play Store

Solution

1. Step 1: Understand what an emulator does

   An emulator simulates a device on your computer so you can run and test apps without a real phone or tablet.

2. Step 2: Identify the main use in development

   Developers use emulators mainly to test apps quickly and safely before using real devices.

3. Final Answer:

   To test apps without needing a physical device -> Option A

4. Quick Check:

   Emulator purpose = Testing without device [OK]

Hint: Emulators simulate devices for testing apps [OK]

Common Mistakes:

• Thinking emulator speeds up coding
• Confusing emulator with publishing tools
• Assuming emulator creates app graphics

2. Which tool in Android Studio do you use to create a new emulator?

easy

A. Build Variants

B. Logcat

C. AVD Manager

D. Device Manager

Solution

1. Step 1: Recall Android Studio tools

   Android Studio uses AVD Manager to create and manage virtual devices (emulators).

2. Step 2: Match tool to function

   AVD Manager is the official tool for creating emulators; Logcat is for logs, Build Variants for build types, and Device Manager is a newer interface but AVD Manager is the standard.

3. Final Answer:

   AVD Manager -> Option C

4. Quick Check:

   Emulator creation tool = AVD Manager [OK]

Hint: AVD Manager = Android Virtual Device creation [OK]

Common Mistakes:

• Confusing Device Manager with legacy AVD Manager
• Selecting Build Variants for emulator setup
• Thinking Logcat manages emulators

3. Consider this Kotlin code snippet to launch an emulator from Android Studio:

val avdName = "Pixel_5_API_33"
// Command to start emulator
Runtime.getRuntime().exec("emulator -avd $avdName")

What will happen when this code runs?

medium

A. The app will crash due to syntax error

B. The emulator named Pixel_5_API_33 will start

C. Nothing happens because emulator command is invalid

D. The emulator will start but with default device

Solution

1. Step 1: Understand the exec command usage

   The code uses Runtime.exec() to run a shell command that starts the emulator with the given AVD name.

2. Step 2: Check command correctness

   The command "emulator -avd Pixel_5_API_33" is valid to launch that specific emulator if it exists.

3. Final Answer:

   The emulator named Pixel_5_API_33 will start -> Option B

4. Quick Check:

   Runtime.exec with valid command = emulator starts [OK]

Hint: Runtime.exec runs shell commands like emulator start [OK]

Common Mistakes:

• Assuming syntax error in Kotlin string
• Thinking emulator command is invalid
• Believing default device starts instead

4. You try to start an emulator but get an error: "emulator: ERROR: Unknown AVD name". What is the most likely cause?

medium

A. The AVD name is misspelled or does not exist

B. Android Studio is not installed

C. Your computer does not support emulators

D. You forgot to write Kotlin code

Solution

1. Step 1: Analyze the error message

   The error says the AVD name is unknown, meaning the emulator cannot find a device with that name.

2. Step 2: Identify common causes

   This usually happens if the AVD name is typed wrong or the emulator was never created with that name.

3. Final Answer:

   The AVD name is misspelled or does not exist -> Option A

4. Quick Check:

   Unknown AVD error = wrong or missing emulator name [OK]

Hint: Check AVD name spelling if emulator fails to start [OK]

Common Mistakes:

• Assuming Android Studio is missing
• Blaming hardware support without checking AVD
• Thinking Kotlin code affects emulator name

5. You want to test your app on different Android versions without buying devices. How can you use the emulator to do this effectively?

hard

A. Install the app on a physical device instead

B. Change the app code to support all versions without testing

C. Use only the latest Android version emulator for all tests

D. Create multiple AVDs with different Android versions and device profiles

Solution

1. Step 1: Understand emulator flexibility

   Emulators let you create many virtual devices with different Android versions and screen sizes.

2. Step 2: Apply this to testing strategy

   By creating multiple AVDs, you can test your app on various Android versions without physical devices.

3. Step 3: Evaluate other options

   Changing code without testing risks bugs; using only latest version misses older compatibility; physical devices cost more.

4. Final Answer:

   Create multiple AVDs with different Android versions and device profiles -> Option D

5. Quick Check:

   Multiple AVDs = test many Android versions [OK]

Hint: Use multiple AVDs for testing different Android versions [OK]

Common Mistakes:

• Skipping tests on older Android versions
• Relying only on physical devices
• Ignoring emulator device profiles