Describe a description of the new feature
In the App Details Activity, AppManager lists component names under:
- Activities
- Services
- Receivers
- Providers
These entries are currently selectable (copy/share) but not tappable.
They are fully‑qualified class names that could be opened directly in the CodeEditor.
On the App Info screen this concept was already start with
Source directory and data directory you can tap to jump into it's file path.
and the MainActivity - That is launched when tapped on.
Mini Sidefeature request on that:
Can we change that and make it instead to jump to the Mainactivity in the Activities tabs?
So the user may decide to launch it from there .
Okay an example:
Provider
com.pairip.licensecheck.LicenseContentProvider
That is kind of 'misused' by to google to enforce "Play Integrity".
So instead of just disabling this crap that otherwise kills the app incase it was not install via Play Store and so bypassing
"Get This App From Play"
Describe the solution you'd like
it would be extremely useful if tapping this entry opened the corresponding class directly in the CodeEditor (Java mode), without breaking the existing copy/share behavior.
A direct jump from App Details → CodeEditor would make this workflow much faster and more intuitive.
Proposed Behavior
When tapping a component entry:
- Resolve the FQCN
com.foo.Bar → vfs://<dex-id>/com/foo/Bar.class
- Open the file directly in the CodeEditor (Java mode)
Important:
The existing behavior must remain intact:
- Short tap → open in CodeEditor
- Long press → select text (copy/share)
Same as links in a browser
Why this is feasible
AppManager already has:
- a VFS exposing classes.dex contents
- a CodeEditor with Java mode
- logic to resolve paths inside VFS
- UI elements that support both click and long‑press
Only a small integration layer is missing:
- a click handler in AppDetailsActivity
- a FQCN → VFS path resolver
- an intent to open CodeEditor
Additional context
This idea came up while exploring better integration between the file manager and the code explorer.
Making component names tappable would turn many currently “dead” entries into powerful navigation shortcuts for reverse engineering and debugging.
Describe a description of the new feature
In the App Details Activity, AppManager lists component names under:
These entries are currently selectable (copy/share) but not tappable.
They are fully‑qualified class names that could be opened directly in the CodeEditor.
On the App Info screen this concept was already start with
Source directory and data directory you can tap to jump into it's file path.
and the MainActivity - That is launched when tapped on.
Mini Sidefeature request on that:
Can we change that and make it instead to jump to the Mainactivity in the Activities tabs?
So the user may decide to launch it from there .
Okay an example:
Provider
com.pairip.licensecheck.LicenseContentProviderThat is kind of 'misused' by to google to enforce "Play Integrity".
So instead of just disabling this crap that otherwise kills the app incase it was not install via Play Store and so bypassing
"Get This App From Play"
Describe the solution you'd like
it would be extremely useful if tapping this entry opened the corresponding class directly in the CodeEditor (Java mode), without breaking the existing copy/share behavior.
A direct jump from App Details → CodeEditor would make this workflow much faster and more intuitive.
Proposed Behavior
When tapping a component entry:
com.foo.Bar→vfs://<dex-id>/com/foo/Bar.classImportant:
The existing behavior must remain intact:
Same as links in a browser
Why this is feasible
AppManager already has:
Only a small integration layer is missing:
Additional context
This idea came up while exploring better integration between the file manager and the code explorer.
Making component names tappable would turn many currently “dead” entries into powerful navigation shortcuts for reverse engineering and debugging.