Consider using ASC for decompilation

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

@deswanth12 is already working on this.

Since Oct 18, 2026.

  • #33 by @deswanth12 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
android

Research direction

The issue only proposes evaluating the ASC decompiler (linked in the issue) as a replacement for jadx, and names no files. Start by finding where the decompile step invokes jadx in the repository, then read the ASC README to see how it runs. Done would mean a measured speed and output comparison against jadx, plus a maintainer decision on whether to switch.

Written by the indexing model from the issue text.

Description

This might improve speed of decompile proces instead of using jadx:

https://github.com/MG1937/ASC

Dominant language
Shell
Stars
8k
Forks
902
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SimoneAvogadro/android-reverse-engineering-skill

All issues in SimoneAvogadro/android-reverse-engineering-skill

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.