APK Downloader
·6 min read

Installed an APK but There's No App Icon: Launcher Entry, Work Profile, and Hidden-App Checks

The installer says success, yet nothing appears on your home screen or in the app drawer. That rarely means the install failed. Use pm path, resolve-activity, and user checks to tell apart a missing package, an app with no launcher Activity, and an app installed into a work profile or hidden by the launcher.

androidapklauncherwork profiletroubleshootinggptoapk

The install finished, Android said "App installed", and then you go back to the home screen and there is nothing there. The usual reaction is to download the APK again and reinstall it. In most cases the package is already sitting on the device just fine — what is missing is either a launcher entry or the user space you are looking in.

Separate the cases first. It saves a lot of pointless reinstalling.

Four different kinds of "I can't find it"

SymptomWhat actually happenedFastest check
Not listed in Settings → Apps eitherThe package never landedadb shell pm path com.example.app returns nothing
Listed in Settings, absent from home screen and drawerInstalled, but no visible launch entryadb shell cmd package resolve-activity --brief com.example.app returns no result
Listed in Settings, visible only after switching spacesInstalled into another user or profileadb shell pm list users shows multiple users, or the phone has a Work / Private space tab
Icon existed before, disappeared after an updateDisabled, hidden, or stale launcher cacheThe package shows up in adb shell pm list packages -d

Only the first row needs a new download. Reinstalling ten times will not produce an icon in the other three.

Layer 1: Ask the package manager, not your eyes

With adb connected:

adb shell pm path com.example.app

A path like /data/app/.../base.apk means the install succeeded and confirms the exact package name. No output, or Error: package not found, means it genuinely is not installed.

If you are unsure of the package name, list third-party packages only:

adb shell pm list packages -3

The -3 filter is far shorter than the full list. In the UI, use Settings → Apps → Show all / Show system and search by app name or version.

Only when this layer fails should you go back to the download stage: incomplete file, signature mismatch, or an install rolled back midway. For those, see APK download 403, 404, and mid-transfer failures and the safe APK download checklist.

Layer 2: Does the package even have a launcher entry?

Android does not create an icon for every installed package. The launcher looks for an Activity declaring android.intent.action.MAIN together with android.intent.category.LAUNCHER in AndroidManifest.xml. Without that declaration, an app installs perfectly and still never appears in the drawer.

Let the platform resolver answer:

adb shell cmd package resolve-activity --brief com.example.app

A result prints the package plus Activity class. no result or empty output means there is no launchable main Activity.

Apps that legitimately have no icon:

  • Service-only apps — keyboards, live wallpapers, accessibility services, notification listeners. Their switches live in Settings, not on the home screen.
  • Plugins, extensions, font packs, data packs that only work inside a host app.
  • Component packages exposing just a content provider or a broadcast receiver.
  • A split APK set where only the base was installed and the feature module carrying the UI is missing — visible in Settings, but it fails on launch.

For these, look under Settings → Keyboards, Accessibility, or Wallpaper. A keyboard with no launcher icon is completely normal.

One related but different case: an accessibility toggle that is greyed out after sideloading is Android 13+ Restricted Settings, a permission-layer policy rather than an entry-layer problem. See Android Restricted Settings explained.

Layer 3: Which user space was it installed into?

A single phone can hold several users, each with its own app list and home screen. Work profile, guest mode, Private Space, and app cloning are all wrappers around that mechanism. A package installed in the main user will not show up in the work profile drawer, or the other way around.

adb shell pm list users
adb shell pm list packages --user 0
adb shell pm list packages --user 10

A numeric ID such as --user 10 usually maps to the work profile. If the package appears under only one user, switch to that space.

Vendor naming varies, so use this map:

Vendor / ROMFeature that hides appsWhere to check
Xiaomi / HyperOSApp lock, hidden apps, Dual apps, Private spaceSettings → Apps → App lock / Privacy protection
OPPO / ColorOS, OnePlusHide apps, Private Safe, App clonerSettings → Permissions & privacy → Hide apps
vivo / OriginOSAtomic Privacy System, App cloneSettings → Atomic Privacy System
Samsung One UISecure Folder, Hide applicationsHome screen settings → Hide apps; or inside Secure Folder
Stock Android / PixelWork profile, Private Space (Android 15+), Guest"Work" tab at the top of the app drawer; Settings → System → Multiple users

A classic trap: you open the APK from a file manager inside the work profile, so the install happens in the work profile, then you go looking on the personal home screen. No reinstall is needed — open it in the right space, or copy the APK back to the main user and install there.

Layer 4: The launcher is hiding it

Package present, entry present, correct user — now it is a launcher problem:

  • Search the app drawer. If the name is found but no icon renders, the icon cache or icon pack is at fault.
  • Try a different launcher. Temporarily switch to the stock launcher or a third-party one; an icon appearing there confirms the original launcher's data is stale.
  • Clear the launcher cache. Settings → Apps → your launcher → Clear cache. Clearing *data* resets your home layout, so screenshot it first.
  • Check the hidden apps list. Many launchers have one, and a single accidental tick removes an app from the drawer.
  • Icon packs. After switching icon packs, some launchers show nothing for apps with no matching icon resource. Disable the pack to confirm.

Layer 5: Disabled or policy-hidden

pm list packages -d lists disabled packages:

adb shell pm list packages -d

If your package is in there, re-enable it:

adb shell pm enable com.example.app

Typical causes: device admin or enterprise MDM policy, parental controls, vendor "deep sleep" or auto-disable of unused apps (Android 12+ on some ROMs), or simply having disabled it manually earlier. The icon normally returns immediately.

When to stop looking and start worrying

No icon plus any of the following means you should not keep hunting for a launch entry:

  • Standby drain or background data spikes, from a package name you do not recognise;
  • Accessibility, notification access, SMS, or overlay permissions requested;
  • The APK did not come from a source you deliberately chose.

No icon plus a permanently resident background process is one of the most common shapes of a malicious package — it was never meant for you to tap. Uninstall it:

adb shell pm uninstall com.example.app

Verifying the signature and permission list before installing is far cheaper than investigating afterwards; see the APK signature verification guide. If drain and wake-ups are already visible, Battery draining after you install an APK walks through the five cause classes.

One-line decision list

  • pm path empty → genuinely not installed; go back to download and verification.
  • resolve-activity empty → no launcher entry by design; find the toggle in Settings.
  • pm list users shows several users → switch to the work profile / private space / clone.
  • Package in pm list packages -d → pm enable it.
  • Drawer search finds it but no icon renders → clear launcher cache or drop the icon pack.
  • Everything checks out but drain and traffic persist → uninstall, do not keep looking for an icon.

The order matters. Start with "is the package there", not "reinstall it once more". Almost every "installed but no icon" report is a deviation in the entry, user-space, or launcher-display layer — not a failed install.