Hey there, very interesting app and I have some log output you might be interested in. I'm currently using an s22 SM-S901W on android 14 with system_app context in the commandline. I used this command just to try it out as uid 1000:
logcat -d | grep "dev.sanmer.pi" 09-09 10:58:22.971 6948 28045 I Finsky : [400] VerifyPerSourceInstallationConsentInstallTask.mt(247): PSIC verification started with installer uid: 1000 package name: dev.sanmer.pi, originating uid: -1
09-09 10:58:22.974 2352 2554 I PackageManager: Request from{dev.sanmer.pi}
09-09 10:58:22.991 2352 2553 I AASA_ASKSManager: initiating = dev.sanmer.pi, installer = dev.sanmer.pi
09-09 10:58:23.003 2352 2553 I AASA_ASKSManager: checking initiating = dev.sanmer.pi, installer = dev.sanmer.pi
09-09 10:58:23.005 2352 2553 I AASA_ASKSManager: installer::dev.sanmer.pi
09-09 11:01:05.887 6948 28962 I Finsky : [405] VerifyPerSourceInstallationConsentInstallTask.mt(247): PSIC verification started with installer uid: 1000 package name: dev.sanmer.pi, originating uid: -1
09-09 11:01:05.892 2352 2554 I PackageManager: Request from{dev.sanmer.pi}
09-09 11:01:05.908 2352 2553 I AASA_ASKSManager: initiating = dev.sanmer.pi, installer = dev.sanmer.pi
09-09 11:01:05.914 2352 2553 I AASA_ASKSManager: checking initiating = dev.sanmer.pi, installer = dev.sanmer.pi
09-09 11:01:05.917 2352 2553 I AASA_ASKSManager: installer::dev.sanmer.pi
09-09 11:02:13.872 6948 7020 I Finsky : [271] acqi.a(74): Installer package name of package com.sdet.fotaagent is dev.sanmer.pi
09-09 11:02:13.873 6948 7020 I Finsky : [271] acqi.a(74): Installer package name of package dev.sanmer.pi is com.google.android.packageinstaller
09-09 11:05:06.270 6948 30833 I Finsky : [432] VerifyPerSourceInstallationConsentInstallTask.mt(247): PSIC verification started with installer uid: 1000 package name: dev.sanmer.pi, originating uid: -1
09-09 11:05:22.248 2352 2554 I PackageManager: Request from{dev.sanmer.pi}
09-09 11:05:22.266 2352 2553 I AASA_ASKSManager: initiating = dev.sanmer.pi, installer = dev.sanmer.pi
So it looks like it was granted elevated privileges because it's uid certainly is not 1000 and also the system seems to have also verified that it's indeed a legit installer from checking other packages it's installed like the com.sdet.fotaagent package which is also a system app with uid 1000 so that may have kind of boosted it?? I'm not sure if I'm right but it might now be recognized as a "legitimate" installer in my system, if so that's pretty cool. Anyways, I just thought it was some different behavior I've never seen before and thought you wouldn't mind some different feedback for your app. Let me know if you need any other information or anything. Thanks again and hope this helps a bit with your development!
Hey there, very interesting app and I have some log output you might be interested in. I'm currently using an s22 SM-S901W on android 14 with system_app context in the commandline. I used this command just to try it out as uid 1000:
cat /storage/emulated/0/Download/app-release.apk | pm install -i dev.sanmer.pi -S 3921585
Here is the log output:
logcat -d | grep "dev.sanmer.pi" 09-09 10:58:22.971 6948 28045 I Finsky : [400] VerifyPerSourceInstallationConsentInstallTask.mt(247): PSIC verification started with installer uid: 1000 package name: dev.sanmer.pi, originating uid: -1 09-09 10:58:22.974 2352 2554 I PackageManager: Request from{dev.sanmer.pi} 09-09 10:58:22.991 2352 2553 I AASA_ASKSManager: initiating = dev.sanmer.pi, installer = dev.sanmer.pi 09-09 10:58:23.003 2352 2553 I AASA_ASKSManager: checking initiating = dev.sanmer.pi, installer = dev.sanmer.pi 09-09 10:58:23.005 2352 2553 I AASA_ASKSManager: installer::dev.sanmer.pi 09-09 11:01:05.887 6948 28962 I Finsky : [405] VerifyPerSourceInstallationConsentInstallTask.mt(247): PSIC verification started with installer uid: 1000 package name: dev.sanmer.pi, originating uid: -1 09-09 11:01:05.892 2352 2554 I PackageManager: Request from{dev.sanmer.pi} 09-09 11:01:05.908 2352 2553 I AASA_ASKSManager: initiating = dev.sanmer.pi, installer = dev.sanmer.pi 09-09 11:01:05.914 2352 2553 I AASA_ASKSManager: checking initiating = dev.sanmer.pi, installer = dev.sanmer.pi 09-09 11:01:05.917 2352 2553 I AASA_ASKSManager: installer::dev.sanmer.pi 09-09 11:02:13.872 6948 7020 I Finsky : [271] acqi.a(74): Installer package name of package com.sdet.fotaagent is dev.sanmer.pi 09-09 11:02:13.873 6948 7020 I Finsky : [271] acqi.a(74): Installer package name of package dev.sanmer.pi is com.google.android.packageinstaller 09-09 11:05:06.270 6948 30833 I Finsky : [432] VerifyPerSourceInstallationConsentInstallTask.mt(247): PSIC verification started with installer uid: 1000 package name: dev.sanmer.pi, originating uid: -1 09-09 11:05:22.248 2352 2554 I PackageManager: Request from{dev.sanmer.pi} 09-09 11:05:22.266 2352 2553 I AASA_ASKSManager: initiating = dev.sanmer.pi, installer = dev.sanmer.pi
So it looks like it was granted elevated privileges because it's uid certainly is not 1000 and also the system seems to have also verified that it's indeed a legit installer from checking other packages it's installed like the com.sdet.fotaagent package which is also a system app with uid 1000 so that may have kind of boosted it?? I'm not sure if I'm right but it might now be recognized as a "legitimate" installer in my system, if so that's pretty cool. Anyways, I just thought it was some different behavior I've never seen before and thought you wouldn't mind some different feedback for your app. Let me know if you need any other information or anything. Thanks again and hope this helps a bit with your development!