Extra blocking via PM

[HanabishiRecca]

It will be good to add true blocking mode with root. Which actually disables activities/services/intents in the system.
Like it's done in MyAndroidTools, LuckyPatcher etc. (After using this tools such components appear in AppManager as disabled.)

[MuntashirAkon]

It will be good to add true blocking mode with root.

Assuming you're talking about pm or Shizuku mode, Intent Firewall is actually far more better than the one you're proposing. See FAQ.

[HanabishiRecca]

Thanks for clarifying 😅

[HanabishiRecca]

@MuntashirAkon hello again. That's the thing why I asked about blocking. Now I collected some data. Seems like IFW not always can block an intent.

For example, I'm blocking this:

The app still shows ads:

But when I'm disabling this intent via e.g. MAT (pm method I suppose):

Intent doesn't work and ad disappears:

Am I get something wrong? Can you test this too?

[MuntashirAkon]

Am I get something wrong? Can you test this too?

I can't seem to reproduce it. After you apply blocking via IFW, you may have to restart the application or invalidate cache. When you block using pm method, this is done by default. The ad might appear because it was stored in the cache or memory.

[HanabishiRecca]

Tried to even reboot the whole device. Also when I enabling intent back in MAT, ad is also immediately turns back. Regardless it's still blocked in AM.

[MuntashirAkon]

Also when I enabling intent back in MAT, ad is also immediately turns back. Regardless it's still blocked in AM.

That not an issue as described in the FAQ.

Tried to even reboot the whole device.

Check if the blocking is really applied by visiting /data/system/ifw/<your package>.xml

You've also failed to mention the AM version you're currently using.

[HanabishiRecca]

That not an issue as described in the FAQ.

I mean AM block doesn't work even after pm block.

Check if the blocking is really applied by visiting /data/system/ifw/.xml
You've also failed to mention the AM version you're currently using.

Sure. Latest AM Pre-release 2.5.21.
/data/system/ifw/com.buak.Link2SD.xml file is present and have a such content:

<rules>
<activity block="true" log="false">
  <component-filter name="com.buak.Link2SD/com.google.android.gms.ads.AdActivity"/>
</activity>
</rules>

Btw there are no any mentions of IntentFirewall or ifw_intent_matched events in the logcat. So I suppose this rules just don't work for some reason. And I found a clue here:

This directory is often /data/system/ifw/, but not always.
you can find the correct directory using the getSystemSecureDirectory() method

But in your app as I can see the path is hardcoded:

AppManager/app/src/main/java/io/github/muntashirakon/AppManager/rules/compontents/ComponentsBlocker.java

Line 62 in 77e18a3

static final String SYSTEM_RULES_PATH = "/data/system/ifw/";

Maybe my firmware just has the different IFW folder path?

[HanabishiRecca]

Hmm, seems like no. Some rules are definitely working. I can block app main activity and it won't launch.
Also I enabled IFW logging and confirmed that

I ifw_intent_matched: [0,com.buak.Link2SD/.Link2SD,10109,1,NULL,android.intent.action.MAIN,NULL,NULL,270532608]

But no matches for ads intent. Very weird 🙃

---

Fixed path maybe still need to be replaced by the function? Just as an compatibility improvement feature. I can create a new issue for it.

[MuntashirAkon]

Fixed path maybe still need to be replaced by the function?

Documentation on Android source suggests that either /data/system/ifw (currently used) or /data/secure/system/ifw (used up to Android M) path can be used.

What's the Android version that you're using?

But no matches for ads intent. Very weird 🙃

There could be other unknown factors at play here. But I can't seem to reproduce it on my device. Advertising doesn't seem to be working at all. Can you try an app called Call Meter 3G so that we can both be on the same page. If the findings are indeed correct, then it will be a very good finding.

[HanabishiRecca]

What's the Android version that you're using?

10 (Q). LineageOS 17.1 (official for my device), so the system is very close to AOSP.

Can you try an app called Call Meter 3G so that we can both be on the same page.

Ok. Blocking the ad here also doesn't work.

[MuntashirAkon]

Ok. Blocking the ad here also doesn't work.

There must be some reason behind this (my suspect is IPC). Anyway, I think it's safe to conclude that it's better to disable these components using both IFW and PackageManager at the same time. So they will remain blocked in case the app enables them. Another idea would be to run a job service now and then to ensure that the components blocked in AM are actually blocked.

[HanabishiRecca]

Anyway, I think it's safe to conclude that it's better to disable these components using both IFW and PackageManager at the same time.

Yes. Really not much of existing apps re-enabling intents. Also being visually in sync with other blocking tools is good too.

[MuntashirAkon]

It's definitely something to do with IPC. I've set SELinux to permissive and IFW isn't working even after I've set it to enforcing again. I'll file a report in the Google Bug Tracker (although there's hardly any chance that this issue will be addressed). They've also neglected my other issue on app ops. They only like the easy-to-fix bugs.

[MuntashirAkon]

Really not much of existing apps re-enabling intents.

People usually blocks components from the dodgy apps, not just from the innocent-looking apps containing AdActivity.

Anyway, thank you for your detailed investigations on this matter. This issue is now closed via 4732500 and 58ca805. Job service is related to #61 and will be addressed there.

[HanabishiRecca]

Anyway, thank you for your detailed investigations on this matter. This issue is now closed via 4732500 and 58ca805.

My respect, sir!