Levo help · For your kind of Mac

For Android developers: Gradle, emulators, SDK images

Android work leaves large folders in your home directory and inside every project. Most are caches and build output that a build recreates. Levo doesn’t need a built-in list of them: your agent looks, and Levo checks what it finds.

What Levo looks for

What’s ticked and what’s only listed

Caches and build output are the regenerable kind, so they can be ticked. Emulator devices, system images and the Gradle dependency store are listed but left for you to tick: they’re slow or large to download again, and an emulator holds its own app data.

Daemons and builds in progress

Gradle keeps daemons running after a build, and they hold memory. If your Mac is slow, open Free memory, CPU and GPU: your agent marks an idle daemon as safe to quit and a daemon in the middle of a build as leave it. Folders a running build is using show as locked until it finishes.

Projects Levo has never heard of

Unusual setups still work. If a folder is called build, sits next to a project, is ignored by git and hasn’t changed in weeks, your agent can say so and give a reason, and Levo verifies the path before it shows up as a row. See How Levo decides what’s safe.

A good routine

  1. Run Analyse now from the popover footer and wait for the list.
  2. Untick any project you’re about to build, then pick a cleanup level. Careful takes only what a build recreates.
  3. After the clean, your next build downloads dependencies again if you cleared the Gradle store. Keep it ticked off when you’re working offline.