[MODULE] App Systemizer for Magisk v9-v14 -- DEPRECATED

Search This thread

guideahon

Member
Nov 30, 2016
16
5
Hi, i have an LG G5, i installed the app but the companion app is not there, also, i found a bug while trying to move "gboard", app systemizer deletes itself and returns all apps to normal status
 

Zeuszoos

Senior Member
Aug 9, 2012
1,078
208
Hi,

Please forgive my ignorance (no, not a noob, just new to Magisk).

I have the App Systemizer app installed and an app I'd like to use it with, Cerberus & Greenify (Greenify4Magisk is Deprecated). But I don't know what to do with the Mod. How do I actually use it to make the apps Privileged System Apps (Priv-App)?

Is it something you use a Terminal app to do? I'm totally clueless here! But I am good with Android, so if you would please give me one example and tell me what you're using to do it, I will understand it.

Btw, I'm running Oreo v8.0 with the new (Stable) Magisk v18.1

Phone: LG V20 (H910), which is the AT&T model, but it's Unlocked and I have MetroPCS (now "Metro by T-Mobile).

Thank You for Your Time,
 

yochananmarqos

Inactive Recognized Contributor
Feb 15, 2013
3,375
2,519
github.com
Google Pixel 3
Google Pixel 7
Hi,

Please forgive my ignorance (no, not a noob, just new to Magisk).

I have the App Systemizer app installed and an app I'd like to use it with, Cerberus & Greenify (Greenify4Magisk is Deprecated). But I don't know what to do with the Mod. How do I actually use it to make the apps Privileged System Apps (Priv-App)?

Is it something you use a Terminal app to do? I'm totally clueless here! But I am good with Android, so if you would please give me one example and tell me what you're using to do it, I will understand it.

Btw, I'm running Oreo v8.0 with the new (Stable) Magisk v18.1

Phone: LG V20 (H910), which is the AT&T model, but it's Unlocked and I have MetroPCS (now "Metro by T-Mobile).

Thank You for Your Time,
This module is no longer updated, use Terminal App Systemizer: https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851

Sent from my Pixel using XDA Labs
 

Ash225

Senior Member
Nov 15, 2017
187
35
Does this module moves the app to system partition? Or uses some trickery to trick the system that the app is indeed a system app.
 

dan60

Senior Member
Jun 14, 2016
54
6
Does this module moves the app to system partition? Or uses some trickery to trick the system that the app is indeed a system app.
I had systemized an app. Then I uninstalled the module. The app I had systemized became user's again. So your second approach seems to be closer to what happened with me. P.S.: I'm referring to the latest version of terminal app systemizer.
 
Last edited:

Piereligio

Senior Member
Jan 13, 2012
305
804
Roseto degli Abruzzi
Hm now this is weird. I'm on magisk 18.1, and when I give su and then systemize, it says module not installed. The module instead is installed and enabled, I also rebooted the phone. Maybe it's because magisk 18.1 isn't supported yet?
 
Is it possible to actually move the apps to /system/app in order to save space?

My internal SD card has only 3.7GB of usable space (practically I only have about 2GB, even with a debloater applied) but my system partition has 1.3GB free which would be useful to install apps on.
My device is old and entry-level so no updates are gonna come out to it anymore. I have searched for the past week and no methods that I have found work with Magisk.

Please help me... I do not know what to do.
 
Last edited:

xcurtx

New member
Jul 7, 2019
2
0
'- Copying zip to temp directory
- Installing Busybox_for_Android_NDK-1.30.1.zip
Archive: /data/user/0/com.XLei.b07.j5wwjpS/cache/install.zip
inflating: install.sh
inflating: module.prop

Busybox Installer Script
by osm0sis @ xda-developers

Mounting...
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory
mount: can't read '/etc/fstab': No such file or directory

Extracting files...
Archive: /data/user/0/com.XLei.b07.j5wwjpS/cache/install.zip
creating: META-INF/
creating: META-INF/com/
creating: META-INF/com/google/
creating: META-INF/com/google/android/
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: README.md
inflating: busybox-arm
inflating: busybox-arm64
inflating: busybox-mips
inflating: busybox-mips64
inflating: busybox-x86
inflating: busybox-x86_64
inflating: install.sh
inflating: module.prop

Installing...
Using architecture: arm
umount: can't unmount /dev/tmp/su: No such file or directory
Using path: /dev/tmp/su/xbin

Cleaning...

Creating symlinks...

Unmounting...
umount: can't unmount /system: Device or resource busy
umount: can't unmount /data: Device or resource busy
umount: can't unmount /cache: Device or resource busy

Done!'

What am i doing wrong and how do i fix it?
 

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,802
Gone
Google Nexus 4
Nexus 6
Yes. Just tried on lineage os 16. Works fine

---------- Post added at 07:19 AM ---------- Previous post was at 07:17 AM ----------

Is there any way to desystemize back the same app which I had systemized using this module?.

You sure you're using this module? It's been long discontinued...

I'm guessing you're using this:
https://forum.xda-developers.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851

If so there's an option to revert systemised apps in the module menu.
 
  • Like
Reactions: yochananmarqos

teddywcn

New member
Jan 10, 2011
4
0
Ho Chi Minh
Add allow-in-power-save when systemized

Dear All,
I am using App Systemizer to systemize my application. It is very perfect :angel:.
Before, I modified /etc/permissions/platforms.xml to add tag allow-in-power-save for my application.
I didn't know how to achieve the same with App Systemizer.
Could you point me a way?
Thanks you very much
Phuoc
 

Keule-Tm

Senior Member
Oct 3, 2016
389
153
Berlin
Samsung Galaxy S10
Dear All,
I am using App Systemizer to systemize my application. It is very perfect :angel:.
Before, I modified /etc/permissions/platforms.xml to add tag allow-in-power-save for my application.
I didn't know how to achieve the same with App Systemizer.
Could you point me a way?
Thanks you very much
Phuoc
1. This module is dead (just look at the title of this thread: it's for Magisk v9..v14; to date we're on 19).
2. It's totally not meant to alter any XML file. How did you get that idea?
 
Last edited:

teddywcn

New member
Jan 10, 2011
4
0
Ho Chi Minh
1. This module is dead (just look at the title of this thread: it's for Magisk v9..v14; to date we're on 19).
2. It's totally not meant to alter any XML file. How did you get that idea?
Thanks you for your reply.
In my case, it still works perfect.
Are there any module to replace it?
When we systemize an application, this module generates a permission file and mount it into /etc/permissions
so if it allow to add into this file a tag for whitelist app.
Best regards
Phuoc
 

Keule-Tm

Senior Member
Oct 3, 2016
389
153
Berlin
Samsung Galaxy S10
In my case, it still works perfect.
Are there any module to replace it?
Yes, there's "Terminal App Systemizer"; have a look in Magisk manager to find it.
When we systemize an application, this module generates a permission file and mount it into /etc/permissions
so if it allow to add into this file a tag for whitelist app.
Well, I stopped using this module, I can't help you there. Plus, I don't understand what you try to achieve. Is it a power saving feature? If so, you could have a look e.g. at FDE.AI (flash & forget powersaving module).
 

Top Liked Posts

  • There are no posts matching your filters.
  • 73
    Instead of including the third party APK files in the magisk modules/repo, this module, developed by @loserskater and me, systemizes user-installed apps systemlessly thru magisk. Another benefit of systemizing the user-installed apps is that if you uninstall magisk, your settings for the apps will be retained. If you originally install any of the apps above thru an app-specific magisk module (like Pixel Launcher magisk module for example), then when magisk is uninstalled or disabled, app settings will be gone.

    If you're on Oreo ROM, you will need this add-on developed by @yochananmarqos: https://forum.xda-developers.com/apps/magisk/module-privileged-permission-whitelist-t3670646

    This module requires installation from Magisk Manager, not recovery.

    This module might lead to your device stuck on logo or booting to recovery, I gather it might be a kernel issue -- the closer you're to stock firmware/kernel the more likely it is to work. If it fails, try the "Terminal App Systemizer" instead.

    Important links:

    NOW IN OFFICIAL MAGISK REPO!

    11.0.6: This is the last "classic/simple" version I could get from github, (11.0.6) which might fail on the larger APKs but doesn't include magisk partition resizing code which might cause problems. It also does NOT include a companion app.

    12.0.5: This is the latest "stable" version with the companion app. Based on pre-"magisk 13" template (version 3), but seems to work with magisk 13.

    14.0.0: This is the 12.0.5 version migrated to 1400 template (released with magisk 14). Not tested by me, so use at your own risk (but please post back wherever it does/does not work).

    The source code (with history) is available here if anyone wants to continue development: https://github.com/stangri/AppSystemizer
    13
    @stangri
    It took rebooting three times (see attached logs) after updating for it to work properly. Why was the app removed in favor of the appslist.conf?

    I can't comment on why it took 3 times, possibly result of me not using the template 4.

    The reasons I've tried to do without the app were two-fold:
    1. To allow easy app updates without updating the module.
    2. (Mostly) to limit the use scenarios, as some of them were resulting in unexpected behavior which were very difficult to replicate.

    Sadly, the move away from the app resulted in an even more complicated code of the module (because now it had to support its own config list + app's config list if the app was installed separately from the module).

    As version 12.0.5 seem to have worked the best for a lot of people, I've rewinded to the commit for 12.0.5 (so it includes @loserskater's app again), updated the template to v4 + PR #27 (fix for /cache installed magisk) and tried my best to update the module code to the changes in magisk/magisk template. Result of it is an attached module version 12.0.8.

    I've tested an upgrade from 12.0.7 to 12.0.8 with a single systemized app (Pixel Launcher) and it worked. However, upgrade from versions 12.0.6/12.0.7 with a lot of apps systemized might not go smoothly. I appreciate you using 12.0.6 and 12.0.7, but if you have apps other than Pixel/Action Launchers systemized with those versions, please delete the old module and reboot first.

    I would *hugely* appreciate if people test 12.0.8 (especially those for whom 12.0.7 didn't work) and post back.

    I'd like to push a stable version to the repo before I cease further development.
    12
    Alright time for another test!
    The main thing is that we can now systemize ANY app regardless of size. Although didn't test games or anything ridiculously large but it should still work!
    A few fixes in the companion app as well including reboot actually writing the config file.
    You can check out the sources for a complete rundown:
    AppSystemizer commits
    Companion app commits

    Only install through Magisk Manager! Flashing in recovery doesn't work at the moment but we're looking into it.
    10
    I did notice a bug with apps not showing selected when closing and opening the app. Sometimes if there is already a magisk-merge.img the script won't copy over the files correctly. I believe this is due to the magisk-merge img already being created with not enough space. A reboot should fix that problem.

    Attached is the 12.0.3 version with the latest app. I've also tried to fix the bug mentioned above.

    PS. Unrelated to the message above, but prompted by a few recent posts: I'll keep repeating it in every post I guess: any report of things not working as intended is useless without magisk log. If it takes more than one reboot to systemize apps -- save magisk log before and after reboot.
    9
    12.0.4

    I've looked into the installation from recovery issue and while it might (to an extent) work on some phones/recoveries, the default shell in recovery is very limited comparing to the shell when the phone is booting/booted up. So I gave up on trying to figure out how to have the module install from recovery.

    However, now there's a big fat warning and the proper error on attempt to install the module from recovery. Just to make sure I do not misdetect installation from recovery (or an otherwise incompatible shell) I'd appreciate feedback from a wide number of users on 12.0.4. All my devices are LOS14.1, so if you're running any other flavour of Android (stock, AOSP, older versions) please post wherever an upgrade to/install of 12.0.4 worked or not.

    Just this one time, no magisk log on error is needed, if you get an error from Magisk Manager on installation, please post as much information as possible about your ROM.

    There's no fix on missing companion app on the Marshmallow ROMs yet.