bug: some app that have finished installing always show as uninstalled.

[weigeloveu]

Bug description

Programs that have finished installing always show as uninstalled.like YouTube telegram,not all app just those two for now

Version of Morphe (Manager) and the app you are patching

All the version ,now is 1.23.0 dev1

Morphe logs

[morphe.txt](https://github.com/user-attachments/files/29438420/morphe.txt)

Acknowledgements

• I have checked all open and closed bug reports and this is not a duplicate.
• I have chosen an appropriate title.
• All requested information has been provided properly.
• The bug only affects using Morphe (Manager)

[LisoUseInAIKyrios]

Did you install the patched app outside of Morphe Manager?

I've never experienced this issue.

[weigeloveu]

Did you install the patched app outside of Morphe Manager?

I've never experienced this issue.

I installed the app via Morphe using Shizuku. Even after I deleted the app from Morphe and repatched it, it still doesn't work.

[MarcaDian]

Try pressing the Delete button on the screenshot, or delete the saved original APK in Morphe's settings, this will also clear the app card (database entry), and then try again.

If that doesn't help, export the key and settings and patch selections, clear the app data, then import everything back.

[weigeloveu]

Try pressing the Delete button on the screenshot, or delete the saved original APK in Morphe's settings, this will also clear the app card (database entry), and then try again.

If that doesn't help, export the key and settings and patch selections, clear the app data, then import everything back.

Thank you all for your responses and attempts to help. Regarding my issue, I’ve confirmed that it occurred while trying to install YouTube and Telegram using Morphe Manager and Shizuku. Even after deleting the app cards related to Morphe and reapplying the patches, the apps continued to appear as not installed.

I’ve tried the methods suggested by @MarcaDian, uninstall the app and restore the key and settings. all apps shows not patched yet But when i patch the youtube the problem persists.

Thank you all for your help!

[MarcaDian]

Please upload the logs during installation. Your link is not working.

[weigeloveu]

Please upload the logs during installation. Your link is not working.

morphe_logcat.txt

[MarcaDian]

Do you have a PC to do a full logcat to identify the problem?

[weigeloveu]

Do you have a PC to do a full logcat to identify the problem?

i have a mac mini m4,idk how to do a full logcat does it have a guide?

[LisoUseInAIKyrios]

https://github.com/MorpheApp/morphe-documentation/blob/main/docs/morphe-resources/questions.md#40-capture-logs

Install adb, verify adb is authorized with adb devices, then do the adb/grep command listed in that link.

[weigeloveu]

https://github.com/MorpheApp/morphe-documentation/blob/main/docs/morphe-resources/questions.md#40-capture-logs

Install adb, verify adb is authorized with adb devices, then do the adb/grep command listed in that link.

'''
platform-tools % ./adb logcat | grep 'morphe:|AndroidRuntime'
06-29 22:13:19.882 30040 30184 I AndroidRuntime: VM exiting with result code 0, cleanup skipped.
06-29 22:16:03.118 5236 5236 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 10419 <<<<<<
06-29 22:16:03.128 5236 5236 I AndroidRuntime: Using default boot image
06-29 22:16:03.128 5236 5236 I AndroidRuntime: Leaving lock profiling enabled
06-29 22:16:03.359 5236 5236 D AndroidRuntime: Calling main entry app.morphe.manager.patcher.runtime.process.PatcherProcess
06-29 22:16:55.626 2817 2865 I AndroidRuntime: VM exiting with result code 0, cleanup skipped.
06-29 22:18:22.369 5236 5303 I AndroidRuntime: VM exiting with result code 0.
'''
I repatched the app on Morphe and reinstalled it, but it doesn’t seem to capture any usable logs.

[LisoUseInAIKyrios]

try
./adb logcat | grep 'morphe|AndroidRuntime'

(no : after morphe)

[weigeloveu]

./adb logcat | grep 'morphe|AndroidRuntime'

logcat_2026-06-29_22-40-23.txt

Sorry, I’m not very familiar with coding — I just copied the commands from the documentation, and I’m not sure why an extra colon appeared. But none of that matters now; I’ve already extracted the full log on my phone using another method. Thanks to everyone for the help.

[MarcaDian]

I tried to run your log and some details through AI analysis tools, and the result is that this is a system behavior of Color OS, and at the moment I don't know how to solve it. Has this happened before?

Details

  Thanks for the logcat — it captured the install flow and the root cause is clearly visible. This is a ColorOS /
  Android 16 system-level install failure with Shizuku silent install of renamed packages, not a regression in
  v1.23.0-dev.1.

  What the logcat shows

  For each of the three install attempts (22:30, 22:34, 22:38), the sequence is identical:

  22:30:47.553  D/Morphe Install          Starting Shizuku install for app.morphe.android.youtube
  22:30:47.553  D/Morphe SessionInstaller installShizuku: app.morphe.android.youtube_20.51.39.apk (95484854 bytes)
  22:30:52.847  D/ActivityThread          Package [app.morphe.android.youtube] reported as REPLACED, but missing
  application info. Assuming REMOVED.
  22:30:52.876  D/ActivityThread          Package [app.morphe.android.youtube] reported as REPLACED, but missing
  application info. Assuming REMOVED.
  22:30:52.915  D/ActivityThread          Package [app.morphe.android.youtube] reported as REPLACED, but missing
  application info. Assuming REMOVED.
  22:30:53.037  D/Morphe Install          Shizuku install successful

  Why the "Uninstalled" badge appears

  That Assuming REMOVED line comes from android.app.ActivityThread.handlePackageBroadcast(). When the system broadcasts
  ACTION_PACKAGE_REPLACED, ActivityThread tries to re-read ApplicationInfo for the package via PMS. PMS returns null
  (the package is reported as replaced but has no usable ApplicationInfo), so ActivityThread invalidates its LoadedApk
  cache and treats the package as removed.

  So the actual chain is:
  1. Shizuku calls PackageInstaller.Session.commit() and receives STATUS_SUCCESS from the system → that's why we log
  Shizuku install successful
  2. But PMS on ColorOS never finalizes the ApplicationInfo for app.morphe.android.youtube
  3. ~100 ms later, pm.getPackageInfo("app.morphe.android.youtube") returns null
  4. isAppDeleted evaluates to true (no PM entry + saved APK on disk + installType != SAVED) → the "Uninstalled" chip on
   the home card and the "App was uninstalled outside the Morphe" banner in the app info dialog

  This is the system / OEM lying about install success. Manager wrote the DB row in good faith because Shizuku reported
  the session as successful.

  Why developers can't reproduce it

  This requires the specific combination:
  - ColorOS / OxygenOS on Android 16 (SDK 36) — your device is OnePlus PJD110 on SDK 36
  - Shizuku as the installer
  - A renamed target package (app.morphe.android.*, not the stock package name)

  YT Music Morphe likely works because either the rename behaves differently, or ColorOS doesn't treat its package the
  same way (different launcher entry / different cleanup heuristic). On stock Android / GrapheneOS / LineageOS we don't
  see this.

  Common OnePlus/OPPO mechanisms that can do this:
  - Phone Manager → App Cleanup / Smart Freeze silently freezes or removes apps that are not in a whitelist immediately
  after install
  - Game Space / App Encryption hides packages that weren't installed via the official installer
  - Power Manager "auto-stop unused apps" on Android 16 has become more aggressive

  Workarounds to try

  1. Settings → Phone Manager / Battery / Privacy → disable any auto-cleanup, smart freeze, "auto-disable unused apps",
  and add app.morphe.android.youtube (and the Telegram patched package) to the whitelist
  2. Open the patched app from the launcher immediately after install, before ColorOS gets a chance to freeze it
  3. Try Standard installer instead of Shizuku — the system dialog goes through a different code path and OEM cleanup
  heuristics may not trigger
  4. If you have root, use Mount install — it bypasses the issue entirely because it doesn't register a separate renamed
   package

  Suggested manager-side mitigation

  We could add post-install verification in InstallViewModel.performShizukuInstall (and the standard installer success
  path) to poll pm.getPackageInfo(targetPackageName) for a short window after Shizuku reports success. If it stays null,
   surface a real install error and skip the DB write, instead of silently leaving a phantom row that then shows up as
  "Uninstalled" on the home screen. This would not fix the underlying ColorOS issue, but it would stop the misleading UI
   state and give you an honest failure message.

[weigeloveu]

I tried to run your log and some details through AI analysis tools, and the result is that this is a system behavior of Color OS, and at the moment I don't know how to solve it. Has this happened before?

Details

I've had this issue since I started using Morphe. Not all apps have this issue. Currently, only YouTube and Telegram have this issue with the apps I use.

[MarcaDian]

Also can be related #598

@zjns Hi, have you had a similar problem? I think your PR has a similar root problem with ColorOS