Prepare v8

CHANGELOG.md

@@ -1,3 +1,11 @@
+## Custom Fork v8
+- Rename VERBOSE_LOGS to verboseLogs to better differentiate Advanced Settings from Build Fields or System Properties
+- Improve replace list to also allow file paths replacing/hiding systemlessly
+- Improve migration script and add optional verboseLogs entry to output
+- Improve replace list to automatically comment out any overlay APK config.xml entries systemlessly
+- Update default/example app replace list for more ROM spoof injection methods
+- Fix retaining disabled ROM apps through module updates in some scenarios
+
 ## Custom Fork v7
 - Fix non-/system ROM spoof injection app replacement
 - Add missing XiaomiEUInject-Stub to the default/example replace list
@@ -6,12 +14,4 @@
 - Spoof init.svc.adbd to DroidGuard by default to further hide USB Debugging
 - Improve hiding from detection by user apps
 
-## Custom Fork v6
-- Improve migration script to be more portable, e.g. for desktop use
-- Add custom function to hack global props without increasing the change counter
-- Add missing Xiaomi, Realme and SELinux global props
-- Add customizable example.app_replace.list file to replace conflicting custom ROM apps
-- Improve VERBOSE_LOGS to be any json entry, and dump full Build fields at 100
-- Change DroidGuard prop spoof hooking method to Dobby for now
-
 _[Previous changelogs](https://github.com/osm0sis/PlayIntegrityFork/releases)_

README.md

@@ -98,7 +98,7 @@ You can read module logs using one of these commands directly after boot:
 
 `adb shell "logcat | grep 'PIF/'"` or `su -c "logcat | grep 'PIF/'"`
 
-Add a "VERBOSE_LOGS" entry with a value of "0", "1", "2", "3" or "100" to your custom.pif.json to enable higher logging levels; "100" will dump all Build fields, and all the system properties that DroidGuard is checking.
+Add a "verboseLogs" entry with a value of "0", "1", "2", "3" or "100" to your custom.pif.json to enable higher logging levels; "100" will dump all Build fields, and all the system properties that DroidGuard is checking. Adding the entry can also be done using the migration script with the `sh migrate.sh --force --advanced` or `sh migrate.sh -f -a` command.
 
 ## Can this module pass MEETS_STRONG_INTEGRITY?
 

module/module.prop

@@ -1,7 +1,7 @@
 id=playintegrityfix
 name=Play Integrity Fork
-version=v7
-versionCode=70001
+version=v8
+versionCode=80000
 author=osm0sis & chiteroman @ xda-developers
 description=Fix CTS profile (SafetyNet) and DEVICE verdict (Play Integrity)
 updateJson=https://raw.githubusercontent.com/osm0sis/PlayIntegrityFork/main/update.json

update.json

@@ -1,6 +1,6 @@
 {
-    "version": "v7",
-    "versionCode": 70000,
-    "zipUrl": "https://github.com/osm0sis/PlayIntegrityFork/releases/download/v7/PlayIntegrityFork-v7.zip",
+    "version": "v8",
+    "versionCode": 80000,
+    "zipUrl": "https://github.com/osm0sis/PlayIntegrityFork/releases/download/v8/PlayIntegrityFork-v8.zip",
     "changelog": "https://raw.githubusercontent.com/osm0sis/PlayIntegrityFork/main/CHANGELOG.md"
 }