What happened to @VR25's modules in the repo? Today I looked but his most excellent modules are gone from the repo. Good thing I downloaded them a few days ago, so I'm wondering if there's a reason for the modules' disappearance?
He didn't have time to update them to the new template before the repo purge. I'm sure he'll update and resubmit when time permits...
The modules will be back.
Don't ignore
VR25 said:
The modules will be back.
Click to expand...
Click to collapse
Sir I am working with a recovery project. I added magisk manager in the recovery by the help of your code. I also gave credit to you. I am asking the permission that can I release the project or I did a wrong step.
Related
Hello everyone!
I created a fork of the Magisk Module Template to facilitate the development of Magisk modules!
The current changes are:
Install app in /data/app
Scheduled changes:
Installation in /system if Magisk is not detected
Installation in /system if the module developer sets it up
AROMA included with easy configuration
Module installation in module (in common/module)
If the module developer enables a specific option, the template identifies the cpu architecture and installs the specific files (put by the developer in common/arc/<name-architecture>)
If the module developer enables a specific option, the template identifies the phone model (ro.product.device) and installs the specific files (put by the developer in <common/phone/phone-model>)
The Complete guide with technical explanation is available here: https://github.com/PurifyOS/magisk-module-template/blob/master/README.md
Repo for clone template: https://github.com/PurifyOS/magisk-module-template
reserved
reserved
Reserved
Reserved
I was just looking through your repo on GitHub and suddenly there's this thread. Looks really interesting. Gonna be interesting to follow... :good:
Didgeridoohan said:
I was just looking through your repo on GitHub and suddenly there's this thread. Looks really interesting. Gonna be interesting to follow... :good:
Click to expand...
Click to collapse
Thanks
Have any plan to make a Xposed SDK25 ARM64 Magisk Systemless for AEX or AOSP please ? waiting for it
洛城天使 said:
Have any plan to make a Xposed SDK25 ARM64 Magisk Systemless for AEX or AOSP please ? waiting for it
Click to expand...
Click to collapse
For aosp xposed work
Ainur JamesDSP is now available in Magisk Manager. Thanks to the devs for their great work. Enjoy!
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
Yikes. I wonder if AML doesn't support Pixel yet. I will look into it and add a note to the OP. Thanks for the heads up.
biribiribiri said:
Not working on pixel xl with magisk 14.3. Repeatedly showing the app has shut down unexpectedly. And then my system started an automatic factory wipe (good thing I forced shut down before the wipe started)
Click to expand...
Click to collapse
By the way, were you running any other audio mods at the time?
s8m said:
By the way, were you running any other audio mods at the time?
Click to expand...
Click to collapse
no
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
yung40oz84 said:
I am getting a blank screen when opening jamesDSP upon flashing and rebooting. Then if I got to recovery and wipe cache and dalvik and reboot it just does a constant FC, over and over. I provided a log through ADB. I am running ABC ROM, Android O, Angler. As you can also see I have audmodlib and ainur audio as well. Also, before I wiped cache and dalvik and the JamesDSP screen was just blank it did show in notification. Basically, Not working at all here. Thanks for the work bud. The first link is the constant FC with ADB, and the second link is Matlog with the blank JamesDSP screen when opening.
https://haste.blamealexcruz.com/WoNVF1m7XX.swift
https://haste.blamealexcruz.com/8EdpzPLtrU.pl
Click to expand...
Click to collapse
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
s8m said:
Thanks - very helpful! Looking quickly at your logcat this may be related to libjamesDSPImpulseToolbox.so being placed inside /system/lib/ instead of /system/lib64/ (my device is ARM64 but accepts /system/lib/). I'll look into a workaround and update this in next build.
Click to expand...
Click to collapse
Great! Looking forward to it.
When users provide logs...
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users.
Click to expand...
Click to collapse
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
s8m said:
I'm confused... this is built off a fork of your AM3D repo but my fork is not your repo. V1.1-beta is the version I created. Like the OP says I created this module, combining your AML/Unity framework and james34602's JamesDSPManager.
If you are working on a JamesDSPManager module that is news to me (hence why I made this module). If you are working on a module that is also v1.1-beta that is quite a coincidence! Are you saying you don't want other devs building off of your AML library and sharing with the community? I thought that was welcome (you are planning a template after all) but I will remove this module if you would rather control development.
Click to expand...
Click to collapse
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
ahrion said:
Ahhhh. I didn't check the GitHub repo. I thought you just built the thread with my GitHub repo (which I submitted through Magisk).
That's so weird lol.
You're good then, but using the latest sources will cause things to be wonky with the current stable version of the other mods. It will cause FC all day.
False alarm. Sorry about that! I'm still gonna make a thread for this however.
Click to expand...
Click to collapse
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
s8m said:
OK no worries! That's a good point that using unreleased sources can cause other unwanted problems. I will take this down if you are creating a separate thread. It's probably better for everyone if you are able to manage the development of AML modules.
Click to expand...
Click to collapse
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Since you're looking from outside, in. Was Unity easy to configure for you? The entire point for AML is to link everything to together for Magisk. Then we created Unity to be an all in one installer. Any AML modules are encouraged and welcome. Ainur is running AML currently.
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
s8m said:
Yeah I must say Unity is really well done. I've only ever done very simple Magisk modules (for personal use) so I may not be the best judge, but there wasn't much learning curve at all with Unity. The way the patching and multi-arch handling is set up is really intuitive and logical. This module was really simple to create compared to your ViPER4Android module but it was nice not to have to think about modifying the install-binary or add custom sed commands. All in all - #impressed !
Click to expand...
Click to collapse
Awesome. You can thank @Zackptg5
Another addition is SETools-inject for Android, that functions like sepolicy inject that MagiskSU/SuperSU have. Essentially, it allows rootless and other forms of root to also use it via init.d. As of yet, no one has actually used SETools for this.
We've also added init.d patching, for rootless and other root methods. Essentially, ramdisk will be automatically patched for AML system modules to use init.d (even if your rom didn't support it before). So init.d patch for all Android versions, MM/N+, has been added. Currently nearly all (if not all) init.d support is broken.
ahrion said:
I already submitted this to the repo. Why are you posting our module as yours? V1.1 is BETA. There's a reason why it is unreleased.
Please have this thread removed. You're going to cause issues for other users, which is already happening.
Click to expand...
Click to collapse
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
24imelqui said:
I hope your mod will be in the repo soon, topjohnwu has been very picky with your soubd mods.
Click to expand...
Click to collapse
It's not that he has been picky. It's just it takes some time to get approved.
Topjohnwu is a busy man.
BTW, Unity allows system mode installation natively if Magisk is not installed, includes addon..d as well.
Magisk is not required for any Unity zips.
ahrion said:
It's up to you man. I submitted the stuff yesterday to the Magisk repo, along with a V4A as well as Unity Xposed.
Click to expand...
Click to collapse
It may be a dumb question, but does your Ainur JamesDSP module require Ainur or can it run independently without Ainur installed?
Please stop putting template=1500 in your props. you can not install even when V15 is installed. it throws an error saying saying please install magisk 15+. you have to put minMagisk=1500. i know wireguard installer 1.1 did this and Systemless_TZData did this. thank you very much and happy holidays and new year to all
"minMagisk=1500" is also in the actual module-template, so if the update to new template is done properly it should be not a problem.
Nevertheless, the change could be stated clearly or magisk can accept it silently (at least for some time).
According to the release post for v15.0 and the 1500 template, "template" and "minMagisk" should both work...
Great find!
Didgeridoohan said:
According to the release post for v15.0 and the 1500 template, "template" and "minMagisk" should both work...
Great find!
Click to expand...
Click to collapse
I did not read this.
Didgeridoohan said:
According to the release post for v15.0 and the 1500 template, "template" and "minMagisk" should both work...
Great find!
Click to expand...
Click to collapse
yes your right. it says it should accept either but when i changed the two modules mentioned from template to minMagisk they both installed with no problems but using template they both gave me the error please install magisk 15+.
@Didgeridoohan already mentioned this issue in the magisk slack-group, so it should be fixed in the next beta/release. Unfortunately until this will be pushed, you have to stick with minMagisk.
And as written before: great find.
Twitter Emojis is BACK!!
Since the original author of the Magisk module for the Twitter Emoji, doesn't maintain it anymore, i decided to maintain it myself.
So here come Twemoji-Remastered!
A Twitter Emoji module maintained for Magisk!
You can view the source of this Magisk module right there
Reserved #1
Here you can find all of the previous and latest version of Twemoji-Remastered in the Release section of my GitHub repo
Reserved #2
Why is this module still Twemoji 13.1, as Twitter has released 14.0?
I'm aware of Twemoji being on release 14, but the upstream didn't updated the package yet, and the script to do it from source is atm very very broken, and i don't have time to fix it atm.
Also they still haven't "officially" updated the emoji to the 14th version yet.
Also atm i don't think it urgent to do it since it just emojis.
Edit: now it is
(Do NOT use this one with the latest magisk) Twemoji-Remastered-14.0.2 is out!!
You can also download it from the GitHub repo
Twemoji-Remastered-14.0.2 is out (again) !!
I've cleaned up the module and it now only compatible with Magisk v20.4+ and above.
You can also download it from the GitHub repo
Just FYI, I've been maintaining the Twemoji module for years on my GitHub at CrystalCommunication/Twemoji-systemless. I hadn't bothered to post it anywhere because I only started maintaining it for my personal phone, but other GitHub users started using the package I maintain, so I started offering automatic updates as well.
CrystalCommunication said:
Just FYI, I've been maintaining the Twemoji module for years on my GitHub at CrystalCommunication/Twemoji-systemless. I hadn't bothered to post it anywhere because I only started maintaining it for my personal phone, but other GitHub users started using the package I maintain, so I started offering automatic updates as well.
Click to expand...
Click to collapse
Cool i guess, well i continued to maintain the orginal twemoji module that was on XDA
The last several versions of Fox Magisk Module Manager has been crashing for me and the app has no way of reporting issues. And the dev is not on GitHub any longer.
Anyone else having the same problems? Are there any other module managers?
Same here.It just started today
A few weeks ago I was having problems with it. The, I saw on the github page that the project was transferred to a different repo with a different developer. So, I installed the build from the new repo and it work for a while and now it is crashing every time I open it. It does have a report feature now though when it crashes.
The old repo is here: https://github.com/Fox2Code/FoxMagiskModuleManager
Scroll down and they link you to the new repo here:
The new repo is here: https://github.com/Androidacy/MagiskModuleManager
The new one seems to still be having some issues though.
Today it happened here as well and the reporting function is outgreyed. Is there any alternative? It showed strange behaviour: it tried (unsuccessful) to use the camera, check the sensors and asked for tracking
It also stopped working for me and gives me an error...
synesthete said:
A few weeks ago I was having problems with it. The, I saw on the github page that the project was transferred to a different repo with a different developer. So, I installed the build from the new repo and it work for a while and now it is crashing every time I open it. It does have a report feature now though when it crashes.
The old repo is here: https://github.com/Fox2Code/FoxMagiskModuleManager
Scroll down and they link you to the new repo here:
The new repo is here: https://github.com/Androidacy/MagiskModuleManager
The new one seems to still be having some issues though.
Click to expand...
Click to collapse
Hasn't worked for me since v1.1
Last night I installed the latest arm64 v8a build here:
Androidacy Downloads Center
Welcome to the Androidacy downloads web app, your one stop place to download past and present versions of Androidacy software.
www.androidacy.com
This is the site linked from the new GitHub repo. So far, it is working for me.