Skip to content

Comments

feat: Add desktop GUI#42

Open
prateek-who wants to merge 30 commits intoMorpheApp:devfrom
prateek-who:gui-update
Open

feat: Add desktop GUI#42
prateek-who wants to merge 30 commits intoMorpheApp:devfrom
prateek-who:gui-update

Conversation

@prateek-who
Copy link
Contributor

@prateek-who prateek-who commented Feb 6, 2026

The GUI update with most of the stuff. Some stuff might be broken, will keep fixing them as they appear. Also, please check the build.gradle.kts file once just to make sure I didn't mess up anything that the team might have added there.

Tired of using the old CLI? Not sure where to get what files to get the CLI running? Too busy to read the documentation? Worry not ladies and gentlemen, we present to you the Morphe GUI!

We got shiny new look coat of paint to suit your needs with more coming on the way!

home_screen

Select the patch you want to use, including stable and dev patches!

Patch_selection_screen

See all the patches that will be applied even before they are applied! Are you a power user and want to make small tweak to the final command? With one click copy, your command will be all yours to experiment with! Also, see the morphe team's most deselected patches and decide if you want to listen to them :)

patches_application_screen

See the patch getting applied in real time just like how it does on the mobile patcher!

patch_getting_applied

Directly install the app to your phone over ADB if you are plugged in to your computer and not worry about transferring the app and installting it again!

Untitled design

And in case you happen to be in a hurry want the entire process to be done ASAP, we got your back there too!

quickmode

Visit your nearest morphe github to grab your CLI's GUI

@prateek-who

This comment was marked as resolved.

@LisoUseInAIKyrios LisoUseInAIKyrios changed the title feat: GUI Update feat: Add desktop GUI Feb 6, 2026
@LisoUseInAIKyrios

This comment was marked as resolved.

@LisoUseInAIKyrios LisoUseInAIKyrios linked an issue Feb 6, 2026 that may be closed by this pull request
2 tasks
@prateek-who

This comment was marked as resolved.

@prateek-who

This comment was marked as resolved.

@prateek-who

This comment was marked as resolved.

@LisoUseInAIKyrios

This comment was marked as resolved.

@prateek-who

This comment was marked as resolved.

@LisoUseInAIKyrios

This comment was marked as resolved.

@prateek-who

This comment was marked as resolved.

@LisoUseInAIKyrios

This comment was marked as resolved.

@prateek-who

This comment was marked as resolved.

@prateek-who
Copy link
Contributor Author

Maybe we relocate the 'Code Preview' and the 'Suggested Deselected Patches' sections to the TopBar in the Patch Selection Screen? It's kinda looks ugly and cramped right now I feel. Will try to figure something out for this soon.

@LisoUseInAIKyrios
Copy link
Contributor

If code preview you mean the CLI command, then yes it can be at the top of the screen. It can be show if "expert mode" is enabled. The simplified mode setting can be inverted to "expert mode" and it's default off, to match Android Manager app.

Suggested deselected patches can be removed entirely. Patches already declare if they are default included, and we don't want hard coded patch preferences or anything else.

Ideally the only hard coded thing we should use, is a package name to app name lookup, so a human readable app name is shown and not the ugly package name. Eventually this will change so it's not needed, but for now it's ok.

@LisoUseInAIKyrios
Copy link
Contributor

The simple mode progress UI stub can be removed too since it's not easy to use with CLI text usage.

@prateek-who
Copy link
Contributor Author

prateek-who commented Feb 9, 2026

If code preview you mean the CLI command, then yes it can be at the top of the screen. It can be show if "expert mode" is enabled. The simplified mode setting can be inverted to "expert mode" and it's default off, to match Android Manager app.

Suggested deselected patches can be removed entirely. Patches already declare if they are default included, and we don't want hard coded patch preferences or anything else.

Ideally the only hard coded thing we should use, is a package name to app name lookup, so a human readable app name is shown and not the ugly package name. Eventually this will change so it's not needed, but for now it's ok.

Got it. I'll remove the suggested patches thingy entirely. Will integrate it into the patch card iteslf just like how mobile manager does it.

@prateek-who
Copy link
Contributor Author

The simple mode progress UI stub can be removed too since it's not easy to use with CLI text usage.

Do I do what the normal mode does and show the progress bar just spinning but no actual number?

@prateek-who
Copy link
Contributor Author

prateek-who commented Feb 9, 2026

Ok, it just says 'patching' now with a circular spinning icon, no progress or numbers and shows the latest text of the CLI in there like this:

Screenshot 2026-02-09 at 9 08 51 AM

@prateek-who
Copy link
Contributor Author

Was looking at adding this #26 . Saw your comment https://github.com/MorpheApp/morphe-patches/issues/336 on keeping them separate for the manager and the CLI. So, we add a flag that keeps only our needed lib and deletes other libs right? Or we could make this a GUI only option too and the Expert Mode gets the option to do this now since we are able to track the user device's architecture if they are connected over ADB (or give them an option to choose).
What do you think?

@LisoUseInAIKyrios
Copy link
Contributor

Rip-libs can be a cli argument. Can be something like --riplibs (architectures to keep, separated by commas)

--riplibs arm64-v8a,x86 strips all except for armv8 and x86.

I think this should be do-able by deleting subdirectories before apktool recompiles the app. Or remove before zipping the files into the final apk, or possibly even remove from the apk after it's created. Deleting before APKTool would be preferred if possible, but whatever is simplest may be the best.

@prateek-who
Copy link
Contributor Author

If a patch is not recommended the patches.mpp file sets "use" to false right? For youtube, only 2 out of the 61 patches have this field set to false,so naturally the gui auto selects the rest 59 and unselects those 2 and then lets the user decide what they want to do. However on the mobile patcher seems to deselect many more patches and shows only 54/61 selected. How is it doing that?

@LisoUseInAIKyrios
Copy link
Contributor

The Android Manager still auto selects all patches with use == true, so it includes 59 patches like CLI does.

But it will remember the last selected patches if using expert mode. Maybe you already patched using expert mode and excluded some patches?

@prateek-who
Copy link
Contributor Author

The Android Manager still auto selects all patches with use == true, so it includes 59 patches like CLI does.

But it will remember the last selected patches if using expert mode. Maybe you already patched using expert mode and excluded some patches?

Ah, that's probably it.

@prateek-who
Copy link
Contributor Author

Rip-libs can be a cli argument. Can be something like --riplibs (architectures to keep, separated by commas)

--riplibs arm64-v8a,x86 strips all except for armv8 and x86.

I think this should be do-able by deleting subdirectories before apktool recompiles the app. Or remove before zipping the files into the final apk, or possibly even remove from the apk after it's created. Deleting before APKTool would be preferred if possible, but whatever is simplest may be the best.

Added --riplibs like you said here. Right as it re-aligns the apk and before the signing it, it rips the libs that the user doesn't want. Right now it does it only for youtube. Will test and add reddit too since reddit says universal too. Size seems to be dropping by 50% for youtube.

@LisoUseInAIKyrios
Copy link
Contributor

Please make a separate PR with riplibs. Can merge that now.

@prateek-who
Copy link
Contributor Author

Add the CLI changes to the new PR, this PR has those changes and the GUI changes that riplibs needs. I am hoping I did it right here too? Those files won't cause nay conflicts in the future when this merges with dev branch right?

@LisoUseInAIKyrios
Copy link
Contributor

Correct there shouldn't be problems after riplibs PR is merged.

Comment on lines 375 to 384
// Show full architecture names for clarity
val formatted = archs.map { arch ->
when (arch) {
"arm64-v8a" -> "arm64-v8a"
"armeabi-v7a" -> "armeabi-v7a"
"x86_64" -> "x86_64"
"x86" -> "x86"
else -> arch
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can remove this left over code

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have the App Info Card rework in the pipelines. But will remove this code for now

@Parsa307
Copy link
Contributor

this is an good idea, btw it won't be morphe cli anymore. there would be an method to use cli instead of gui?

@LisoUseInAIKyrios
Copy link
Contributor

Existing terminal CLI still works exactly how it always has. The GUI is shown if the CLI jar is opened like an app (double click from file explorer).

@kitadai31
Copy link

kitadai31 commented Feb 12, 2026

#42 (comment)
Ok, it just says 'patching' now with a circular spinning icon, no progress or numbers and shows the latest text of the CLI in there like this:

How about showing log text in a multi lines text box like RVX Builder?

Currently, there is still a lack of information on the patching screen.

Benefits of showing logs:

  • CLI should be more advanced than Manager
  • It's easier to know which patches have been applied
  • Progress becomes clearer (decoding, patching, compiling, etc)
  • When a problem occurs, you can check the error

@prateek-who
Copy link
Contributor Author

It already does this in the expert mode. I had made that change only for the simplified mode

@kitadai31
Copy link

Oh, I didn't know expert mode. I'm sorry.

Btw, "Rebuilding APK..." log is not shown in Quick Patch mode
This makes it appear as if the progress is stuck on the last patch while rebuilding APK (Like "Applied: Custom branding")

@prateek-who
Copy link
Contributor Author

Ok, I see this issue. Will fix this. If a patch takes longer than like 5 secs, I plan to put a message that says "Hold on.... this is taking longer than usual" but you are right on rebulding part. I'll fix that part

@LisoUseInAIKyrios
Copy link
Contributor

Do any patches take more than 5 seconds? On my somewhat newish mid grade laptop every patch runs in less than 2 seconds. Some patches are less than 1/10 of a second.

The majority of the patching time is APK processing itself (decoding, compiling, signing).

@prateek-who
Copy link
Contributor Author

prateek-who commented Feb 12, 2026

None do, it's just the last rebuilding that takes a bit of time. Maybe adding that message might give the user assurance that it is still running.

@prateek-who

This comment was marked as resolved.

@LisoUseInAIKyrios

This comment was marked as resolved.

@prateek-who

This comment was marked as resolved.

@prateek-who

This comment was marked as resolved.

@LisoUseInAIKyrios

This comment was marked as resolved.

Better patching logging Simplified version.
Added --force for unsupported versions.
Added a button for --continue-on-error to allow gui users to continue patching even when if a patch throws an error.
@prateek-who
Copy link
Contributor Author

Oh, I didn't know expert mode. I'm sorry.

Btw, "Rebuilding APK..." log is not shown in Quick Patch mode This makes it appear as if the progress is stuck on the last patch while rebuilding APK (Like "Applied: Custom branding")

try patching now. It should properly show the stages in the simplified version

@prateek-who

This comment was marked as resolved.

@LisoUseInAIKyrios

This comment was marked as resolved.

LisoUseInAIKyrios and others added 4 commits February 15, 2026 13:16
added fixes from other branches and new mini theme
Added a better offline mode experience for the user.
Minor UI improvemments to the patches and patchselection screens.
Added some updates from other branch (but not all, might lack some functionality that are present in other branches)
@prateek-who
Copy link
Contributor Author

Could you check once just in case I properly merged everything. Seems right me (it was 90% accepting the incoming changes)

@LisoUseInAIKyrios
Copy link
Contributor

CLI usage seems to be working. json file works as expected. I didn't check GUI but it should be ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: Simplify the usage of CLI by improving UX

4 participants