Maria Sophia wrote:
In desperation, here's a summary of the problem, in a nutshell:
a. I can't figure out how to turn a thousand lines like this:
package:/data/app/~~0H1-2NstdUVjAZffiA36og==/com.wemagineai.voila-eUnm7DkWz754o5t0a88gdA==/base.apk=com.wemagineai.voila
b. Into this (without knowing the name of the package ahead of time)
/data/app/~~0H1-2NstdUVjAZffiA36og==/com.wemagineai.voila-eUnm7DkWz754o5t0a88gdA==/base.apk
c. Can you?
Just for the record, if parsing doesn't work on the command line,
then it won't work in batch either... (as that's even harder).
Stefan Ram wrote:
You can remove the
@echo off
to get more context about where this message is coming from.
Thanks Stefan, as this should run on anyone's Windows box with Android.
My Android is connected over Wi-Fi via the adb connect script.
I just saw this, so I'll just post my latest version, but it's still
saying "The system cannot find the drive specified" for some reason.
Yesterday, the chain of events was such that:[snip]
1. Stefan Ram posted a warning that Android APKs can leak location
Message-ID: <locations-20260805220107@ram.dialup.fu-berlin.de>
2. I then showed how use Win10 to determine if any apps leaked recently
Message-ID: <1150g5v$1lsp$1@nnrp.usenet.blueworldhosting.com>
3. But I then spent hours trying to confirm if any of my APKs "can" leak
A. Windows can tell you if a device "has" leaked in the past time frame
B. And, Windows can tell you if a device "can" leak in the future...
Specifically, how do we turn this:
package:/data/app/~~0H1-2NstdUVjAZffiA36og==/com.wemagineai.voila-eUnm7DkWz754o5t0a88gdA==/base.apk=com.wemagineai.voila
Into this (without knowing the name of the package ahead of time)
/data/app/~~0H1-2NstdUVjAZffiA36og==/com.wemagineai.voila-eUnm7DkWz754o5t0a88gdA==/base.apk
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 4 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 497102:27:32 |
| Calls: | 182 |
| Files: | 744 |
| D/L today: |
65 files (9,837K bytes) |
| Messages: | 73,659 |