• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

android_htc

Senior Member
Feb 24, 2011
433
192
Samsung Galaxy S20 FE
The only way it could have happened afaik is when:
1. You installed the module
2. You've rebooted and then selected some apps to be systemized in the companion and/or didn't reboot after the module was installed
3. You've unchecked the module in magisk manager and then rebooted

What happens under the hood in step 1 or 2 is that the module creates the magisk_merge image with systemized apps only which is then merged into the default magisk image on reboot. So you'd end up with the module folder with the systemized apps, but without the module.prop which is necessary for Magisk Manager to fetch the module information.

If that sounds like scenario which has unfolded, I can fix that bug. If the list of steps was drastically different from described -- please let me know.
Thanks for the explanation...You are correct about the scenario. Uninstall error, I must have unchecked the module and also selected it for removal.

Your test module works well on it's own and systemizes all installed apps from your appslist.conf list.

Please fix the description bug "no info provided"; it occurs after a restart once module is fully active and remains thereafter.

Unfortunately, appsystemizer app does not work; sometimes it save the selected option and prompts to reboot, or it just loops. However, any apps ticked do not systemize after reboot..
 
Unfortunately, appsystemizer app does not work; sometimes it save the selected option and prompts to reboot, or it just loops. However, any apps ticked do not systemize after reboot..

It might very well be an issue with my module trying to juggle two lists which confuses companion app.

I would appreciate if you could test attached, I've tried to fix the bug when the the module is removed when magisk_merge image is created, thus killing the module.prop file.

Again, I myself have not tested this.
 

Attachments

  • AppSystemizer-12.0.6.zip
    12.1 KB · Views: 76
  • Like
Reactions: android_htc

android_htc

Senior Member
Feb 24, 2011
433
192
Samsung Galaxy S20 FE
It might very well be an issue with my module trying to juggle two lists which confuses companion app.

I would appreciate if you could test attached, I've tried to fix the bug when the the module is removed when magisk_merge image is created, thus killing the module.prop file.

Again, I myself have not tested this.
Yes, this fixes the module.prop issue.
Hope you guys can resolve the issue with the companion app soon.
Edit: hope you can fix the installation error message as well.. as it can be confusing for users!
 
Last edited:

android_htc

Senior Member
Feb 24, 2011
433
192
Samsung Galaxy S20 FE
I must have missed something -- which installation error message?
See screenshot...this happens and has been on last few updates when installing via magisk manager. And, re-opening magisk manager again shows the module has actually installed..hence the message is misleading.
 

Attachments

  • SmartSelectImage_2017-06-06-20-59-28.png
    SmartSelectImage_2017-06-06-20-59-28.png
    46.3 KB · Views: 312
  • Like
Reactions: stangri
See screenshot...this happens and has been on last few updates when installing via magisk manager. And, re-opening magisk manager again shows the module has actually installed..hence the message is misleading.

Anything in the magisk log when this pops up? Not sure if it'd help, but please try attached.
 

Attachments

  • AppSystemizer-12.0.6.zip
    12.1 KB · Views: 78

android_htc

Senior Member
Feb 24, 2011
433
192
Samsung Galaxy S20 FE
Anything in the magisk log when this pops up? Not sure if it'd help, but please try attached.
No, nothing in the magisk log.
This version still gives the installation error toast message..and it also failed to systemize the installed apps as per the list.
Edit: ignore the last comment, I forgot to remove the companion app before installing the test module
 

Attachments

  • magisk_error_20170607_131951.log
    12 KB · Views: 8
Last edited:

israelisraeli

Member
Jul 4, 2015
15
1
sorry if it have been asked before, but i couldn't find the answer
i tried to systematize greenfly (via companion app) and ended up in a boot loop
how can i solve the boot loop without losing data?
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,972
13,453
Gothenburg
Google Nexus 4
Nexus 6
sorry if it have been asked before, but i couldn't find the answer
i tried to systematize greenfly (via companion app) and ended up in a boot loop
how can i solve the boot loop without losing data?

Flash the Mount Magisk script from this thread in TWRP: https://forum.xda-developers.com/apps/magisk/collection-magisk-modules-v2-t3575758

After that you can use the TWRP file manager to remove the module (it's in /magisk).

Edit: Oh yeah! Forgot about the Module Uninstaller by @veez21. That's a great tool to use. You'll find a link to it in the same thread above.
 
Last edited:
  • Like
Reactions: stangri

israelisraeli

Member
Jul 4, 2015
15
1
Flash the Mount Magisk script from this thread in TWRP: https://forum.xda-developers.com/apps/magisk/collection-magisk-modules-v2-t3575758

After that you can use the TWRP file manager to remove the module (it's in /magisk).

Edit: Oh yeah! Forgot about the Module Uninstaller by @veez21. That's a great tool to use. You'll find a link to it in the same thread above.

first of all thanks for the quick response!
iv'e deleted the folder /magisk/Appsystemiser
rebooted to be kindly greeted by the same boot loop...
 

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,972
13,453
Gothenburg
Google Nexus 4
Nexus 6
first of all thanks for the quick response!
iv'e deleted the folder /magisk/Appsystemiser
rebooted to be kindly greeted by the same boot loop...

In that case I'd flash the Magisk uninstaller and possibly restore my stock boot image. If that doesn't work, I'd dirty flash my ROM.
 

psychoela

Senior Member
Dec 21, 2014
369
155
OnePlus 7 Pro
not ETA just share:(

Sent from my Nexus 6 using XDA Labs
 

Attachments

  • Screenshot_20170613-231542.png
    Screenshot_20170613-231542.png
    150.3 KB · Views: 390
  • Screenshot_20170613-231641.jpg
    Screenshot_20170613-231641.jpg
    321.3 KB · Views: 388
  • Screenshot_20170613-231655.jpg
    Screenshot_20170613-231655.jpg
    248.3 KB · Views: 384
  • Screenshot_20170613-231716.jpg
    Screenshot_20170613-231716.jpg
    198.1 KB · Views: 382

Link_of_Hyrule

Senior Member
Oct 12, 2010
2,060
769
Ogden, Utah
www.ubermicrostudios.com
Having issues on my tablet getting google play services messed up I'm not sure if it's the new version of systemizer in combination with the latest beta of Magisk or what. I ended up just uninstalling it. Hopefully another beta of Magisk fixes the issues it is Magisk and not the 12.0.6 version of the module.

Sent from my Nexus 7 using Tapatalk
 
  • Like
Reactions: stangri

24imelqui

Senior Member
Jan 24, 2016
638
170
Cebu City
12.0.5 with companion app is working with the latest Magisk-v13.0(96f8efc), previous beta will get stuck on brand splash screen after flashing 12.0.5 via magisk . Zenfone 2 RR N 5.8.3
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 72
    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.