8000 Releases · Astoritin/BloatwareSlayer · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Releases: Astoritin/BloatwareSlayer

Bloatware Slayer v1.4.3

22 Jun 11:59
6924cbc
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.4.3

  • Right/True slay mode will be shown in module description now.

Before this update, slay mode state showing on the module description is read in settings.conf.
That means in weird cases like 0 APP is dealt with Mount Bind method and 4 APP(s) is dealt with Make Node method.
Module description will show Hybrid even if only Make Node method is used before 1.4.3
However it is obviously not a right feedback since which mode Bloatware Slayer used depends on the real processing instead of setting in config file.

  • Optimize minor code

  • 现在模块描述中会展示正确/实际使用的模式。

在此更新之前,显示在模块描述中的模式取决于Bloatware Slayer 的配置文件 settings.conf 中的设定
这意味着在 1.4.3 之前,极端情况下(例如没有APP被 Mount Bind 方法处理,有4个APP被 Make Node 方法处理)模块描述仍会显示为复合模式 (Hybrid)
然而很显然,这样的反馈信息并不正确。在 Bloatware Slayer 的模块描述中,处理模式应该取决于实际过程中的所用的方法,而不是配置文件的设置。

  • 优化少量代码

Bloatware Slayer v1.4.2

18 Jun 16:48
1a36901
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.4.2

  • Now, The default timeout of judging device bricked is 120 seconds (2 minutes) always
  • Now, logging files located in /data/adb/bloatwareslayer/logs will be cleaned automatically as file counts reaching max value (30) during each time boot
  • The path of saving last worked target list changes: /data/adb/bloatwareslayer/logs/target_lw.conf/data/adb/bloatwareslayer/last_worked/target_lw.conf
  • Remove logs from action.sh, now log will not be generated as clicking on the action/open button
  • Fix a bug: Now, Bloatware Slayer will backup original target.conf properly as disabled "Auto update target list" feature
  • Fix a bug: Now, Bloatware Slayer will skip unmounting properly as disabled "Disable module as bricked" feature
  • Fix minor logic problems of brick rescue code
  • Remove large amount of useless codes to reduce module file size
  • Remove feature update module description as clicking on the remove/uninstall or disable button again since this feature is so useless

Whether Zygisk Next or Magisk's Denylist Enforcing status is enabled or not is NOT related to the running status (theme) of Bloatware Slayer.
This module only processes during system boot. Once finished boot, there is no operation for Bloatware Slayer to run in the background.
"Updating module description realtime" seems completely redundant. Thus, I've removed it and won't reverse this change anymore.

  • 判定设备变砖的默认倒计时统一为 120 秒 (2分钟)
  • 在启动过程中,/data/adb/bloatwareslayer/logs 中的日志会在文件数到达最大值(30)时被自动清理
  • 最近一次正确目标列表保存目录变更:/data/adb/bloatwareslayer/logs/target_lw.conf/data/adb/bloatwareslayer/last_worked/target_lw.conf
  • 移除来自 action.sh 的日志,现在在点击操作/打开按钮时不再生成任何日志
  • 修复一个bug: 现在当禁用"自动更新目标列表"功能时,Bloatware Slayer 会正确备份原版的 target.conf
  • 修复一个bug: 现在当禁用"变砖时自动禁用模块"功能时,Bloatware Slayer 会正确跳过 service.sh 的卸载操作
  • 修复部分救砖逻辑代码的问题
  • 移除大量无用代码以减小文件体积
  • 由于过于无用,功能:卸载/禁用模块时更新模块描述又双叒叕被移除了

无论启用与否,Zygisk Next 的遵守排除列表状态和 Magisk 的遵守排除列表状态都与 Bloatware Slayer 的运行状态(主题)无关。
本模块仅在开机过程中进行处理,开机完成后 Bloatware Slayer 并没有任何需要在后台运行的操作。
"模块描述实时刷新"这个功能就显得极其多余,因此我移除了,并且不会再撤销。

Bloatware Slayer v1.4.1

11 Jun 15:52
025f1fc
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.4.1

  • Add path redirection feature, which means adding /system prefix manually is not enforced anymore.
  • For example: Bloatware Slayer will process path /product/app/<Dirname> /priv-app/<Dirname> in target.conf.

NOTICE: You still need to add /system manually for unconventional Bloatware paths.
For example: you need to add /system prefix to /MzApps to make sure you need to process /system/MzApps , otherwise the paths will still be skipped.

  • Remove temporary file target_bsa.conf (cleared target list) generated by Bloatware Slayer automatically

  • Optimize the logic code of judging last worked target list

  • 新增路径重定向功能。这意味着不再强制手动添加 /system 前缀

  • 例如:Bloatware Slayer 会处理在 target.conf 中的 /product/app/<目录名>/priv-app/<目录名> 等目录

注意,对于非常规预装软件目录,你仍然需要手动添加 /system 前缀
例如:对于 /MzApps,你仍需要添加 /system 以确保你需要处理的是 /system/MzApps ,否则这类路径仍然会被跳过

  • 移除由 Bloatware Slayer 自动生成的临时文件 (整理过的目标清单) target_bsa.conf
  • 优化最后一次正确目标列表的判定逻辑

Bloatware Slayer v1.4.0

03 Jun 03:45
683fd4b
Compare
Choose a tag to compare
10000

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.4.0

  • Bloatware Slayer will recognize and show duplicate items information properly on module description
  • 现在会正确识别并在模块描述中显示重复项目的信息
  • Optimize and cleanup minor code
  • 优化和清理部分代码
  • SHA256: 1046c71243f0a3b0562d154aafb3fe375c96773c6c6f07a302b632d2c4336027

Bloatware Slayer v1.3.9

16 May 15:12
09ee209
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.3.9

  • Add last time worked target list features
  • 新增 最后一次正确目标列表 功能
    set last_worked_target_list=true in settings.conf
    settings.conf 中设定 last_worked_target_list=true
    Only available as disable_module_as_brick=false (the behavior logical is NOT compatible as enabling this option)
    仅当 disable_module_as_brick=false 时可用 (启用该选项时行为逻辑不兼容)
    Bloatware Slayer will restore target.conf boot successfully at the last time
    Bloatware Slayer 会恢复上次成功启动系统时的 target.conf 版本
  • Fix the bug as most of devices can NOT reboot (by reboot -f) as detecting being bricked
  • 修复当检测到设备变砖时,大多数设备无法重新启动 (通过 reboot -f) 系统的bug
  • Add X-plorer as open method for action.sh
  • 为 action.sh 新增 X-plorer 作为打开方式
  • remove command from module files su -c forever since su -c is not need anymore
  • 由于不再需要 su -c ,已彻底移除
  • minor code optimizing
  • 优化部分代码

Bloatware Slayer v1.3.8

07 May 15:11
ad187df
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.3.8

  • Optimize and cleanup minor code
  • 优化和清理部分代码
  • SHA256: 8bddc669b16e567d9ce5e4fa60d3cc761aa7da0fbb65abb361daa9518673f6b0

Bloatware Slayer v1.3.7

30 Apr 15:07
ad187df
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.3.7

  • Allow to disable inbuilt brick rescue by setting brick_rescue=false in settings.conf
  • 允许通过在 settings.conf 内设置条目 brick_rescue=false 以禁用内置救砖模式
  • Fix a bug which would ignore the last line of file target.conf before
  • 修复之前会忽略 target.conf 的最后一行条目的bug
  • Migrate brick rescue core code to fix the logical issue of updating module description
  • 迁移救砖模式的核心代码以修复更新模块描述的逻辑问题
  • SHA256: baf5e0d4c0d190a8907a06e75aa78c72e755d715ca004d018f012fbd35c64646

Bloatware Slayer v1.3.6

26 Apr 04:32
031314d
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

Changelog / 变更日志

1.3.6

  • As detecting update flag, module description will be ceased automatically
  • 当检测到更新时,会自动停止更新模块描述
  • Add debug flag/option to provide more details
  • 新增 debug 标识符/选项以提供更多细节
  • Fix some logical loophole
  • 修复部分逻辑漏洞
  • SHA256: c969207da6d429593dfda1e8cb0153eda2bb8b5564665a083df3d89d94ac75a7

Bloatware Slayer v1.3.5

20 Apr 01:10
29fa78b
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.3.5

  • Initial support for blocking bloatwares deployed via APEX components
  • Notes:
  1. Due to the particularity of APEX-based bloatwares, custom paths are currently the only option (i.e. You need to specify the full path and folder names alone are not supported).
  2. Since APEX-based bloatwares is compressed into .apex or .capex files and verified/uncompressed during Android startup, blocking this type of bloatwares requires your Root solution to support MN (Make Node) mode. Otherwise, blocking will not be possible.
  3. Because a single .apex or .capex file might contain multiple components, blocking one component could lead to the disappearance of several components after a reboot. This is a characteristic of APEX-based bloatwares. Please think carefully before adding it to the target list.
  4. Bloatware Slayer will automatically check whether your device supports MN mode. You don’t need to modify slay_mode and can still choose your preferred mode.
  • Enhanced the root-hiding capability of MB (Mount Bind) mode. Bloatware Slayer will umount itself by default now.

  • Fix the problem where MR mode couldn’t be switched/corrected to MN mode under KernelSU/APatch

  • The status of Magisk and Zygisk Next for DenyList Enforcing will no longer be displayed when the real-time update module description function is disabled

  • Refactored a large amount of code

  • SHA256: 9b8e4b5d48ffa1c9a8ba9edd3287904cb1a1042ed8942f7d1e528df1568c8df5

  • 初步支持屏蔽以 APEX 组件方式安装的预装软件

  • 注意:

  1. 由于APEX类预装软件的特殊性,目前仅支持自定义路径(也就是说,你需要指定完整的路径,不支持仅文件夹名);
  2. 由于APEX类预装软件被压缩成 .apex 或者 .capex 文件,在 Android 启动时验证并解压,屏蔽APEX类预装软件需要你的 Root 方案支持MN (Make Node,节点创建) 模式,若不支持则无法屏蔽;
  3. 由于 .apex 或 .capex 可能包含多个组件,可能你只是想屏蔽一个组件,但是重启后几个组件都不见了,这是APEX类预装软件的特性,请再三斟酌是否需要加入目标列表
  4. Bloatware Slayer 会自行检测设备是否支持 MN 模式,你无需修改 slay_mode , 仍可选择你想要保持的模式
  • 增强 MB (Mount Bind,挂载绑定) 模式的隐藏 Root 能力:现在,Bloatware Slayer 在 MB 模式下,默认情况下会自我 umount
  • 修复 KernelSU / APatch 下无法将 MR 模式切换到 MN 模式的问题
  • 当检测到实时更新模块描述功能被禁用时,不会再显示 Magisk 和 Zygisk Next 的遵守排除列表的启用状态
  • 重构大量代码
  • SHA256: 9b8e4b5d48ffa1c9a8ba9edd3287904cb1a1042ed8942f7d1e528df1568c8df5

Bloatware Slayer v1.3.3

13 Apr 03:36
6ab48cd
Compare
Choose a tag to compare

Bloatware Slayer / 干掉预装软件

A Magisk module to remove bloatware in systemless way / 一个无需修改 system 分区即可移除预装软件的 Magisk 模块

1.3.3

  • Introduce update module description realtime back
  • 重新引入实时更新模块状态
  • Add new features: showing DenyList Enforcing status for Magisk and Zygisk Next
  • 新功能:为 Magisk 和 Zygisk Next 展示对应的“遵守排除列表”状态
  • Try to fix the issue of detetcting root solutions and multiple root solutions
  • 尝试修复检测 Root 方案和多重 Root 方案的问题
  • SHA256: 732e23203fee29e337a1d2209eb081f637aca65da49d8c731aaf7bd102c7175d
0