DONT UPDATE Package Disabler Pro if you want to AVOID the OTA

[andoxviii]

Yes uninstall 6.4 first!

---------- Post added at 02:34 PM ---------- Previous post was at 02:28 PM ----------

I just loaded the 6.3 version APK to my public OneDrive account
Click here guys:
https://1drv.ms/u/s!AsOG_vH3x0TjjwSHw5M9FflyJ-Fx

 

[borijess]

Anyway to make a backup of the apps you have disabled? I don't want to go through disabling 170 apps.

 

[ooMoo]

Please pm me and i will send you a link to the apk on my phone

 

[ooMoo]

Anyway to make a backup of the apps you have disabled? I don't want to go through disabling 170 apps.

I believe you can export the disabled apps to an xml file? That might do what you need

 

[emike09]

Not seeing com.samsung.firmware.sensorhub on my Sprint N7, is there an alternative or am I missing it somehow? I was able to disable everything else.

 

[friedbars]

Dammit, I forgot to uncheck auto update and now I got a new version. So we first uninstall the newest version and place this apk in Samsung folder and just install it?

 

[JarkMackson]

What has been posted several times already. I personally have disabled
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm

and most importantly

com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp

I cannot guarantee anything obv but this seems to do the trick for most people

I have a Verizon N7 and I don't have the last two, even after manually trying. Did I miss something?

---------- Post added at 04:45 PM ---------- Previous post was at 04:43 PM ----------

I have a Verizon N7 running 6.3 and I don't have either of these:

com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp

Did I miss something? I tried entering them manually too.

 

[borijess]

Does the att version have these two lines?

 

[nabbed]

What has been posted several times already. I personally have disabled
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm

and most importantly

com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp

I cannot guarantee anything obv but this seems to do the trick for most people

Question:
do you know if disabling any of these packages going to trip Knox or disable Samsung Pay?

 

[borijess]

Just got another update for the app.

 

[dark-fiction]

What has been posted several times already. I personally have disabled
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm

and most importantly

com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp

I cannot guarantee anything obv but this seems to do the trick for most people

You can't forget the Samsung Push Service:
com.sec.spp.push
And I would disable automatic updates from settings and automatic security policy updates from the security menu as both of these and push service could be used as attack vectors by Samsung.

---------- Post added at 11:37 PM ---------- Previous post was at 11:33 PM ----------

Question:
do you know if disabling any of these packages going to trip Knox or disable Samsung Pay?

It doesn't for Knox, I've done it and no issues, only Rooting will do that. Don't have Samsung pay in Canada so can't confirm on second point, but probably not.

 

[hoursenghong]

So they're really pushing dead-end update now, and yet my local hasnt done anything with note 7 yet. Still waiting..... Probably until my note exploded then maybe they say "ah, we dont swap for that brick. Bye"

 

[Amazingfoxx]

Can I get the apk plz. Thank you. I've paid for it.

 

[ooMoo]

Can I get the apk plz. Thank you. I've paid for it.

I've sent you a PM

 

[Manumanu787]

Guys if you're not sure which packages have been disabled
1) check what version of Package disabler you have. You MUST have version 6.3 in order to be able to remove the necessary packages
2) if you don't have version 6.3 uninstall whatever version you have, then install version 6.3 from any of the link you may get (I got mine with a simple google search) and it will activate automatically if you have purchased the app legally. Make sure you have the auto-updates disabled in the google play store !
3) tick all the packages I have listed earlier. to answer a previous comment "And I would disable automatic updates from settings and automatic security policy updates" they are disabled already if you disable package com.policydm as I wrote. As for Samsung push the only thing they can push are annoying messages but I doubt they could push anything harmful to the phone. However disable it indeed as well.

4) For those who are adb shell savy, start a shell window after connecting your phone via USB (make sure you have USB debugging activated of course..........) and use command
adb shell pm list 'packages' -d
to check which packages are indeed disabled. You should see the ones we've been talking about at the very least (and maybe some others in addition).

---------- Post added at 01:24 PM ---------- Previous post was at 01:07 PM ----------

A quick word : I received yesterday a message by a member called Tossero with a link to a version 6.3 of Package Disabler Pro.
If you receive the same message be careful on which link you click : click on the direct download one, because the green "download" link leeds to a file that is
1) not an APK but an EXE inside a RAR
2) loaded with viruses
guys beware of so-called versions 6.3 of the app. always check for viruses

 

[ooMoo]

If you need the app just pm me and i will send a link

 

[Cr4z33]

Isn't there a simple adb command to disable packages manually?

Yes, but it's easier by using this.

 

[HarlyFan]

I just uninstalled 6.5 and reinstalled 6.3 APK and none of the packages that need to be blocked are even showing anymore. I even tried to manually disable them and it just says that the package is missing. Anyone have any suggestions?

 

[nabbed]

Yes, but it's easier by using this.

I tried this.
Got a little confused.
The initial pop-up says "This device doesn't support block mode. We'll hide/disable instead."
Then I hid/disabled some apps. And confirmed that they were indeed taken care of by rerunning the app.
Now, here's a confused part:
when I do "adb shell pm list packages", it doesn't list them anymore. So, does this mean that hide/disable is even more severe than block?
And does block really mean "disable" app from the app drawer?
When I do "adb shell pm list packages -d", it shows apps I "disabled" from the app drawer.
So the terminology must be reversed:
Debloater's "block" equals Android's "disable app."
While Debloater's "hide/disable" equals something even more severe.

Is this correct?

EDIT:
On the other hand, this is more confusing now.
I restarted the phone, reran the app to verify that settings stuck. Then looked at Applications setting in Settings of the phone.
The apps that were "hidden" by Debloater appear to be still running.
For example, FWUrgentUpdateTSP, which is com.samsung.android.firmware.tsp, is still running. At least according to Settings.
What's going on?

Update:

"hide" prevents the packages from ever loading into physical memory. They are still there, but they cannot be executed by the system.
So, this indeed works.

 

[Cr4z33]

I tried this.
Got a little confused.
The initial pop-up says "This device doesn't support block mode. We'll hide/disable instead."
Then I hid/disabled some apps. And confirmed that they were indeed taken care of by rerunning the app.
Now, here's a confused part:
when I do "adb shell pm list packages", it doesn't list them anymore. So, does this mean that hide/disable is even more severe than block?
And does block really mean "disable" app from the app drawer?
When I do "adb shell pm list packages -d", it shows apps I "disabled" from the app drawer.
So the terminology must be reversed:
Debloater's "block" equals Android's "disable app."
While Debloater's "hide/disable" equals something even more severe.

Is this correct?

Sorry I can't help you, but I am sure that you will find the answers in the Debloater topic.





Sent from my Samsung Galaxy S7 edge with stock Samsung Marshmallow firmware