Challenge 3: Reading a Real Logcat Filter — Solution Walkthrough

1. With the Challenge 1 app running and producing lifecycle logs, open
   the Logcat panel at the bottom of Android Studio.
2. In the search/filter bar at the top of Logcat, type: MainActivity
   (matching the tag used in Log.d("MainActivity", ...)).

// What this filter changed:
// The Logcat output narrows from a constant, noisy stream of system-level
// messages (from every process running on the emulator, not just this
// app) down to ONLY the lines whose tag matches "MainActivity" — in this
// case, exactly the six lifecycle log lines this app produces, with
// everything else hidden.

3. Clear the tag filter, then use the log-level dropdown (usually showing
   "Verbose" by default) and change it to "Warn."

// What this filter changed:
// Now Logcat shows only messages logged at Warn level or higher (Warn,
// Error, Assert) — the Log.d(...) calls from Challenge 1 disappear
// entirely, since Debug is a LOWER severity than Warn. Only genuine
// warnings/errors from ANY running process remain visible.

Notes:
- Tag filtering and level filtering can be combined (a specific tag AND
  a minimum level) — this combination is the normal way to debug a
  specific screen's behavior without scrolling through thousands of
  unrelated system log lines.
- In a real debugging session, starting broad (just a tag filter) then
  narrowing further (adding a level filter) once a rough problem area is
  identified is a natural workflow.