Recent content by machx0r

I have no control over Samsung but am doing what I can to protect the license and provide a fair option to everyone involved. I could just abandon the project entirely but instead I continue to invest in keeping the app functional. All other options appear to just be giving up *shrug*

And just like that Alliance Shield X gets their license revoked as well. Reading their forums it sounds like their solution is to remove package disabling from their application all together. The situation sucks but Samsung is the problem and I will continue to fight to keep a package disabler...

The system periodically checks that the license is still valid. I don't have insight on the inner working of the Knox system but any good licensing system would treat an expired cached result the same as a an unlicensed or revoked result.

Google restricts both the number of refunds and promo codes I am able to process. Then there is the issue of the amount of time available to handle either of these. I'm working within the bounds of the limitations presented to me and as such I made the business decision to be very clear...

The license is cached by the system. Give it a few days and the system will prompt you to activate the license and you'll receive an error.

Unfortunately this is the case. Working on an alternative distribution method but Samsung seems to be cracking down hard and I'm running out of partner accounts...

I was actually setup like this to begin with. I know Samsung is familiar with Package Disabler Pro (and has been for much longer than me since they were around first) yet they had a version remain in the Play Store through multiple license revocations of mine. I believed this was due to the fact...

I'm honestly not sure what brings their attention to me as the same version of Package Disabler Pro remained in the Play Store through multiple version of my application. At first I thought it was the free vs. paid aspect but that is obviously not the case. That said I am playing with the idea...

Makes sense and confirmed: 1|beyond1q:/ $ pm disable com.sirma.mobile.bible.android/com.youversion.ui.about.AboutActivity Security exception: Shell cannot change component state for com.sirma.mobile.bible.android/com.youversion.ui.about.AboutActivity to 2 java.lang.SecurityException: Shell...

I haven't looked into the ADB method but isn't it just opening a shell and using `pm` to disable applications? If so this is how CCSWE App Manager (Root) works [via an `su` shell locally on the device] so it should be possible to disable application components as well assuming there isn't a...

CCSWE App Manager has a blacklist and it used to be more comprehensive. In fact the first time license was terminated I was blocking almost everything Samsung specific. Both myself and an attorney friend of mine have contacted Samsung to argue that my application was not in violation of their...

I'm very open regarding the status of my application with Samsung. It violates their license agreement, just like any other Package Disabler distributed to consumers, and they will kill it at some point. Users have the option to assume this risk and purchase the application or not and I hide...

I can't speak on what Samsung specifically does to terminate a license. What I do know is that when they terminate mine the entire Samsung Partner account is terminated. Then if I try to register the old package on a new account it is rejected. So either the license validation checks the account...

The issue can't be resolved in that version as Samsung revoked the license and a license is tied to a specific package.

There was another version in the links listed until today. Unfortunately Samsung terminated both my and Package Disabler Pro's licenses today (maybe a little sooner for PDP)... Who knows when I'll be able to fix it. The core issue is that a Samsung Partner Account is required to generate Knox...