yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
I was wondering why this link for the newest and frequently updated commits is not in the OP:

https://github.com/kantjer/MagiskFiles

The one you link in the OP is very old and hasn't been updated in a long time:

https://github.com/TheComputerGuy96/MagiskFiles

I have it bookmarked when at home on my desktop, but have a difficult time finding it when on the road with other mobile devices,

Thanks
[Magisk] KelleyCook:
Good question… but its might be easier to change the "Update Channel" field in Magisk Manager to custom and type in the kantjer URL. Then you don't have to remember it again.
[Magisk] Ubimo:
See latest changelog.
[Magisk] laupuy:
Thanks kantjer :good:

Latest Magisk v15.3 (180112)

Latest Magisk Manager v5.5.4 (180112)

All is good.
[Magisk] ridobe:
[MENTION=3306843]kantjer[/MENTION] is not the OP for this. In fact, he's the third different source we've had. As a follower of this thread, I've had no problems keeping up. This is however, a problem for new posters trying these out for the first time. Maybe kantjer can take over the OP. The last post from [MENTION=2226076]stangri[/MENTION] says for anyone willing, can update the OP to reflect correct information. https://xdaforums.com/showpost.php?p=72803193&postcount=1064

Yeah, this is nice. Just add:

https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json

to the custom update channel in settings.
[Magisk] martyfender:
Thanks, I am actually on the stable, Magisk 15.3 but I like to follow topjohnwu's commit log and the corresponding new, unofficial builds to monitor any potential changes. Since you have added the link here, I can now easily add it to my mobile device bookmarks.

Thanks
[Magisk] laupuy:
Thanks kantjer :good:

Magisk v15.3 (180113)

Magisk Manager v5.5.5 (180113)

All is good here :)
[Magisk] Skittles9823:
Nice update worked fine for me. Seems to be using LibSU now as opposed to MagiskSU ? thanks [MENTION=3306843]kantjer[/MENTION]
[Magisk] martyfender:
I saw [MENTION=4470081]topjohnwu[/MENTION] s commit for this switch. Does any one know what will this change will mean for the benefit of Magisk? Magisk-v15.3.1-180121.zip and MagiskManager-v5.5.5.1-180121.apk, seem to be working fine on the only device I have tested it on An older version of the device in my signature, same hardware older IFWI and ROM version. Here is a pastebin link to the Magisk debug log as there are some errors. I'm not sure if they are of any significance, though.

https://pastebin.com/LfMHZfD2

Thanks
[Magisk] Skittles9823:
Yea. I'm unsure exactly of the new functionality/what may have been taken away, but there is extensive documentation in TopJohnWus git for LibSU. So if you'd like to have a bit of a read on it, thats the place to do it.
[Magisk] martyfender:
Thanks

Yes, I did read the commit, but since I am not a programmer, it means nothing to me.
[Magisk] Skittles9823:
Same, but even having a quick look at code/docs can give you a basic understanding of what it does.
[Magisk] DodoGTA:
MagiskSU still is MagiskSU, by the way

But I think that LibSU is similar to Chainfire's libsuperuser
[Magisk] Skittles9823:
Ahh, interesting. I'll have to wait for full release for TopJohnWu's full explication I guess then.
[Magisk] w20grippy:
What is that?
[Magisk] Skittles9823:
Check TopJohnWu's git for the commits.
[Magisk] KelleyCook:
Could someone add the topjohnwu/libsu repo to be a change trigger for rebuilding our nightly MagiskManager?

Thanks!
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] Thank You for doing these builds. Your latest build is working great on three of my devices, which are older versions of the device in my signature.

Just out of curiosity, how do you decide when you are going to do a new build?

Do you wait for [MENTION=4470081]topjohnwu[/MENTION] to make significant changes in his commits, or do you do them when you have some extra free time?

I'm looking forward to your next release.

Thanks
[Magisk] kantjer:
Current source isn't building for me. I'm getting a zip sign error. I haven't had time to look into detail into this issue.
[Magisk] martyfender:
Could it possibly be related to his updated crypo in his commits?
[Magisk] kantjer:
That's my guess
[Magisk] kantjer:
The build issue is fixed.
[Magisk] Sheetzie03:
Font, theme please?

Thank you
[Magisk] kantjer:
Font_ProductSans2 and Mono/Art theme
[Magisk] bountyman334:
Sweet..I thought I was the only guy|person who used Mono art...
[Magisk] uudruid74:
Hopefully this isn't too offctopic, but I figure the guys here would be familiar enough to know the answer.

Does MagiskHide use Linux namespaces? If not, what method is used?
[Magisk] DodoGTA:
It uses the setns() system call
[Magisk] martyfender:
I'm not sure about MagiskHide, but there are settings in Magisk Manager under Mount Namespace Mode for:

Global Namespace

Inherit Namespace

Isolated Namespace

I use Global Namespace as that is what was recommended by the Apps2sd author, for his app.

---------- Post added at 02:31 AM ---------- Previous post was at 02:18 AM ----------

The latest build is working great on my devices. I am contemplating setting up an building this myself. I am relatively new to Linux. I am using a hi speed, bootable bootable USB thumb drive with Linux Mint Mate. It has a persistent, casper-rw partition.

I have read topjohnwu's instructions to setup the build environment. Can you tell me the approximate disk space requirements to install Android Studio, Android Ndk, etc to build it? I have only 5GBs of free space on my persistent, 32Gb drive. I am loving Linux so much, that I am considering purchasing another harddrive to install Linux Mint to, for a more permanent solution.

By the way, are topjohnwu's lastest commits from yesterday in your latest build, as I don't see a changelog, which, I understand, for simplicity, you don't include, on github.

Thanks again, for these builds, I have it now on 4 devices and it is working well, so far.
[Magisk] uudruid74:
Are you sure it uses setns() to hide? It can't modify the namespace of an existing process, so I would think it would just be the namespace of the root process/shell itself that is modified. The only way I can think of to hide root using setns() would be to patch zygote. I just want to make sure I'm not missing something
[Magisk] dewois:
MagiskManager-v5.5.5.1-180127.apk

not working for me. The App stuck at the Magisk Logo

Edit: Log
[Magisk] RagingHarry:
Any additional information that could make it able to help you beside that it isn't working?

Logs, device and rom info, mods installed?
[Magisk] martyfender:
Try an uninstall and reinstall of the Magisk Manager. Apk only, to see if that helps.
[Magisk] dewois:
Not working
[Magisk] martyfender:
You should also provide the magisk debut log at: /data/adb/magisk_debug.log

For someone who is knowledgeable enough to troubleshoot it. That the log that is usually asked for in debug builds such as the official beta and the unofficial one we are both using.

UPDATE: one thing I just remembered, I had problems last week with the Magisk Manager that was similar to your: it either, one, froze at the splash screen or crashed.

I solved it by going into Android settings, apps and granted Magisk Manager storage permissions.

I don't understand why it does not ask for this permission on first launch, by default. Some actions in the manager do ask for permissions, but I now regularily go into app settings and set it and I never have the problem any more. I would be interested if this will work for you also.

I notice more problems with Magisk, in general, when a user is using Lineage. Am I wrong?
[Magisk] bggold:
I am on v15.3.1 (180201) and this morning when I sent into MM it said that Magisk was not installed. It seems that this has been an ongoing issue with all the different builds of possible the daemon crashing.

Root is still available and a reboot takes care of the issue.

Here is the log and hopefully there is some useful info.

Pixel 2 xl v8.1 Jan.

Thanks
[Magisk] laupuy:
A little word to thanks kantjer for new build 180205 :good:

Edit.

Update to 120206 :good:
[Magisk] SnakeByte:
Installed v15.3 on ZenFone 3 Laser (ZC551KL), stock 7.1.1, and all seems to work well, but every time i try to install a Module in Magisk, installation fails; Any module...

On the other hand, same version on Grand Prime (G530W) Lineage 15.1, after install the phone is laggy, almost unresponsive.
[Magisk] martyfender:
Is there a Magisk uninstaller that will work with your latest v15.3.1 (180211) build? I tried one I had on my system: Magisk-uninstaller-20180101.zip, in TWRP and it failed.

For the first time I had a failed boot with the new V15.4 beta and it is recommended in the beta thread that I uninstall Magisk and start over. I have not yet tried to uninstall from the Manager, it'self.

Unlike all of your builds for weeks, v15.4 beta failed to load the boot.img and booted to bootloader mode with an error message.

I'm not sure if it was [MENTION=4470081]topjohnwu[/MENTION] 's commits today that are the problem, as your builds and all betas and stables since 15.1 and newer, have worked great on my device.

UPDATE: Your lastest, v15.4 180213 is working great, also
[Magisk] laupuy:
Hi,

Thanks kantjer (and Magisk Team) for the new build!

Magisk v15.4 (180213)

Magisk Manager v5.6.0 (180213)

All is good :good:
[Magisk] SnakeByte:
Flashed Magisk v15.4 and install Magisk Manager 5.6.0... All good now. Thanks.
[Magisk] guest4711:
Installed the last builds

- Magisk v15.4 (180213)

- Magisk Manager v5.6.0 (180213)

on all my Sammy devices by updating from MagiskManager. No problems, even if /data is on f2fs... :good:

Thanks [MENTION=3306843]kantjer[/MENTION] for your continuous builds!
[Magisk] Didgeridoohan:
[MENTION=3306843]kantjer[/MENTION]

Are you doing anything at all when building Magisk that could make your unofficial build work where the official doesn't:

https://xdaforums.com/showpost.php?p=75573151&postcount=5163
[Magisk] kantjer:
The only thing I change is the versioning.

I build on Linux Mint 18.3, using NDK 15c

Using this Manifest and build script
[Magisk] PokemonTotalWar:
Is there a reason that the latest Manager builds seem to crash for me any time I try to install them? They won't even work if I wipe the data
[Magisk] PokemonTotalWar:
Here is what I'm pretty sure is the entire log
[Magisk] Bill720:
In the same boat; how'd you fix it?

I'm running into the exact same issue. Can you tell me where in the Kernel Adiutor app you found the option to enable logging?

UPDATE:

I installed KA-Mod Reborn and located the option to enable it under "misc settings" inside of "misc controls." Unfortunately, enabling it doesn't actually work. If I return to this page, the setting is off. "Apply on boot" has no effect.

The good news is that we know what the cause of the battery drain is. The bad news is that it does not seem possible to enable the feature required to keep Magisk from letting of the gas. Any ideas, or is it time to uninstall Magisk and switch back to SuperSu?
[Magisk] II_DiE_4:
Try this one in misc settings. If this doesn't work, then get a kernel that didnt disabled the logging.
[Magisk] Bill720:
No dice

The apophis one seems to behave exactly as the original KA Reborn. I'm on the stock kernel for the Moto X Pure Edition and would rather not have to fumble around with finding a different one.
[Magisk] bountyman334:
Am having the same problem with 3c toolbox and setting cpu settings at boot. it works with Supersu( and everything seems to move faster? don't know why)

s

is there any workaround for this... I tried changing the namespace to different one to see a diff... nothing
[Magisk] laupuy:
Thanks kantjer for new build :good:

Magisk 16.0 (180222)

Magisk Manager v5.6.1 (180222)
[Magisk] Bill720:
Magisk Daemon is a power vampire

So you're seeing a lot of excessive CPU use from Magisk Daemon as well? It's amazing how quickly one, seemingly-small, 5% CPU draw can drain the battery.
[Magisk] bountyman334:
I have to check on that. What I saying was that, I set my CPU And GPU to a certain gov and speed, and after reboot, it goes back to another level which i cant change. On SUPERSU it doesn't do that, I can config and it sticks.
[Magisk] Skittles9823:
What kernel app are you using? EXKM hasn't failed me in that regard.
[Magisk] Ace42:
Probably 3c or kernel auditor. I use EX so it's a non issue for me.
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] I'm glad to see that [MENTION=4470081]topjohnwu[/MENTION] made some new commits today.
[Magisk] kantjer:
Thanks I hadn't checked the git today. I will make a new build tomorrow. I'm now enjoying my Saturday evening :)
[Magisk] martyfender:
I'm glad to hear that you are enjoying your evening. As always, I look forward to your new release tomorrow.
[Magisk] bountyman334:
It was 3c... it turns out that I have modded\edited my init.qcom.post_boot.sh to reduce speeds to a certain level for battery life..I removed it.. Problem gone..

I attached the issue
[Magisk] laupuy:
Hi,

Thanks kantjer for new build :good:
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] , I want to thank you for all of your recent builds. They have worked great on the four devices I have them installed on. The four devices are the same as in my signature, just different ROM build numbers. I usually just update using the direct install method in Magisk Manager, with your custom update channel.

With Magisk Hide only enabled, they alway pass Safety Net and show the devices as certified in the Play Store, although it would never pass without it, when I used to use SuperSu. In my use case I don't use any apps that need this, but it is a nice to have this if I ever do need this capability.

Thanks Again.
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION], I see [MENTION=4470081]topjohnwu[/MENTION] has posted some new commits, today.
[Magisk] laupuy:
Thanks for the info, update done [emoji39]

Thanks kantjer [emoji106]

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk

Edit.

Update 28/03/2018 magisk 16.3 and manager 5.6.4 done!

Thanks :)
[Magisk] bggold:
I'm getting can't unpack boot.img error. Trying to update to 5.6.4. 1804328

All others worked fine.

Pixel 2 xl

Thanks
[Magisk] bggold:
After reboot stuck at bootloader screen. Could not fastboot twrp and computer showed my pixel 2 xl as a Samsung device.

Dirty flashed fixed and reflashed 180328 without issue.

Do have ElementalX and twrp flashed with magisk.

Must have been a glitch.

Thanks
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] I'm glad to see that [MENTION=4470081]topjohnwu[/MENTION] is back at it again with some new commits today.
[Magisk] rxk:
Is magisk working on GAlaxy s9+ (SM-G965F)?
[Magisk] martyfender:
The last information I saw, was, no, not yet. You might want to check your device forums, though.
[Magisk] oreo27:
I see some new commits on the repo today. :)
[Magisk] laupuy:
...And a new magisk by kantjer is out!

https://github.com/kantjer/MagiskFiles

Thanks :good:
[Magisk] oreo27:
Thank you! :)
[Magisk] martyfender:
Has anyone else experienced: Magisk is not installed in the Magisk Manager and loss of root, after a few hours or a day or so, on the last three unofficial builds; 180415, 180421 and 180422?

Because of this I reverted my 4 devices to the official 16.3 beta and installed the 180422 Magisk Manager, because of the crash bug when refreshing the downloads section.

And yes, I realize: "These might be very unstable builds, especially in the early stages of development."

Hopefully this problem will be fixed in future commits. Builds in the past few months previous to these have worked without issue on my 4 devices, all the same hardware.
[Magisk] oreo27:
No such issues on my device. I am on the latest unofficial build. I've also seen significant improvements in the booting process. My device would occasionally boot with no baseband or get stuck in the boot animation with 16.3. I haven't experienced the same in my limited time testing the latest build.

---------- Post added at 02:27 PM ---------- Previous post was at 01:56 PM ----------

Just wanted to ask. I wanted to try building it myself but I'm getting an error for the "app" submodule.

https://github.com/topjohnwu/MagiskManager/tree/267395bfa2b5077717aadcc3cdd0634443fbad03

It doesn't exist. How were you able to build it? :confused:
[Magisk] kantjer:
I pull the source files using a manifest, that way I don't run the risk of linking to non-existing commits.

https://github.com/kantjer/magisk_manifest
[Magisk] BustedFly:
I think in a few builds is a bug. It break the sound like ringtone.

I try it with your builds and the last beta. With the beta it works normal but with your build not.

Problem (no logs, sorry):

I install SM 2.8 on s7 edge SM935F with full wipe..... When phone is booted up no ringtone..... No notifications sound.... Everything is on silent. Reboot.... All silent again.... After a few times... The sound is ready.....

With the last beta no problem.

Hope this can be fixed from the Maggi Dev :)
[Magisk] kantjer:
Happend to me a few times with the last few builds.

Hasn't happend with yesterday build sofar.

---------- Post added at 09:03 ---------- Previous post was at 09:00 ----------

Sound is working fine for me.

If it's device specific we need to wait until [MENTION=4470081]topjohnwu[/MENTION] fixed it in the source code.

I'm not messing with the code, just build as it is (except for versioning stuff)
[Magisk] oreo27:
Edit 1 - No need to re-install the manager. Simply reflash/restore stock boot img and flash this Magisk over that. It'll work with the official manager. This works way better than 16.4 in my limited testing experience.

New commits at https://github.com/topjohnwu/Magisk/commit/25703c175070f2a506154add59b9dc409db186fb. Built this by basing a Travis CI build from [MENTION=2226076]stangri[/MENTION]'s repository and with a bunch of help from [MENTION=3306843]kantjer[/MENTION].

This is untested. FLASH AT YOUR OWN RISK. You'll need to uninstall/re-install Magisk Manager from within the zip since this is not signed with the same key.

https://github.com/0reo27/travisTest/releases/download/16.5-25703c1/Magisk-v16.5-25703c1.zip

I WILL PROVIDE ZERO SUPPORT on this.
[Magisk] martyfender:
Forgive me, but doesn't [MENTION=3306843]kantjer[/MENTION] 's latest build, today, include the same fixes, if not, what is different about your builds. No criticisms, just asked for clarification.

Thanks
[Magisk] oreo27:
It should contain the same, correct. No differences functionally as far as I know. Mine is built without using the --release flag so it should be larger in size. I'd go ahead and download his. Just provided that earlier since he didn't upload his release right away.

P.S. I recall you having issues with <=16.4 which I also encountered. This build fixed some issues in installation for me.
[Magisk] martyfender:
Yes, I had issues loosing root with 16.3 180422 and maybe a couple of previous builds. 16.4 180429 and 180506 have been solid, so far. For some reason the official 16.3 did not have that issue, during the brief time I reverted to it.

Essentially, you are just using a different way to build it: Travis CL? Also, I notice you changed the version to 16.5, even though [MENTION=4470081]topjohnwu[/MENTION] has not changed it in his commits. However, that probably makes sense since it is newer than his last beta release. I am tempted to try your build, but I am probably better off just sticking to my current 180506 build. If I do try your builds later, is there a custom update channel for it to be set in the Magisk Manager to do it through there, or would I need to flash it in TWRP?

Thanks
[Magisk] oreo27:
Right on! I'm using a remote server (Travis CI) based on [MENTION=2226076]stangri[/MENTION]'s previous work. I would imagine that [MENTION=3306843]kantjer[/MENTION] is using his own physical or virtual system. Right. I just named it 16.5 because it contains commits later than 16.4. I also appended a commit string to know which commit I'm currently at. Sadly, I haven't done an update channel yet. It's actually a simple JSON file that I could copy and replace with my link but I never meant for my builds to be used by people other than me. I just posted it here earlier since there were no updates yet. I would advise that you stick to katjer's latest build as it should contain the same exact commits. :)

I'm actually quite happy with the this particular commit as it seems to have solved my "stuck at boot animation; I have to force restart" issue which I've had since I purchased my device. 16.4 without this commit was plain not working for me at all. Module installations would fail and other such weird behavior.
[Magisk] kantjer:
Root loss was fixed with this commit.

I'm thinking of skipping version numbers altogether and only use the build date.

Some users seem to be focused on version number, actually they don't mean anything. I can make a build with any number I like, doesn't make the build better or newer.
[Magisk] oreo27:
Haha. Yeah. It's an argument to build.py. I'll actually take your advice on my personal builds as well. Have you tried the latest commits on your device? It runs so good on my device. :) Except for Magisk Manager which crashes every so often.
[Magisk] kantjer:
I overwrite build.py versioning in my build script, so it's easy to change it to whatever I want it to be.

No MM crashes for me since the last few builds.
[Magisk] Renovatio_ edi:
Any one can fix random losing root
[Magisk] martyfender:
I had that happen on the last 2 builds before 180506. On 180506, I don't have that issue. Are you also having it happen on 180506?

https://github.com/kantjer/MagiskFiles
[Magisk] martyfender:
Has anyone else tried flashing Magisk Modules in TWRP, with the latest build?

When I flash, for example, the cloudflare4magisk module, I get an error 1 and it fails. Installing it in the Magisk Manager module section or download section works fine, though.

I am not sure when this started, as it has been a while since I tried flashing a module in TWRP.
[Magisk] martyfender:
[MENTION=4863028]oreo27[/MENTION] A few hours ago I. for the first time, installed the build you released today and so far, it is running great.

I first uninstalled the Magisk Manager 5.7.0 180506 [MENTION=3306843]kantjer[/MENTION].

The first time I tried to flash it in TWRP I got a failure with an error 1 message. And I believe that was after I used a Magisk uninstaller zip. I went back, mounted the system in TWRP and tried again and it succeeded.

My TWRP version is 3.1.0-0, the latest compiled for my device, if that makes a difference.

On a second Nextbook Ares 8A, I booted to TWRP, mounted system and installed your zip without using the unistaller and it succeeded. I'm not sure if removing the Magisk Manager on the first device had a negative effect or if mounting the system is what did the trick.

I did a second test on that second device, and flashed your zip again. It failed twice again and only succeeded once I mounted the system in TWRP.

The error I received was that it could not mount system. So mounting it manually solved it. I am in no way implying that it is a problem with your build. I thought someone might have an idea why this is happening, though. I usually use the direct install method in the Magisk Manager, also, with no problems.

Thanks
[Magisk] oreo27:
You sure picked the wrong time to try my build. :) Currently, Magisk is not building correctly:

https://travis-ci.org/0reo27/travisTest/builds/378417182

So I tried to git reset it to an older commit. However, this seems to have produced a different Magisk Installer from the one I had in that point of the repository. Perhaps the reset is not working as expected.

Try to uninstall Magisk and re-download the release from my repo. I've since manually replaced the zips from ones in my hard drive which were produced previously.
[Magisk] kantjer:
Same here, build is failing when building the BusyBox binaries.
[Magisk] Didgeridoohan:
[MENTION=4863028]oreo27[/MENTION] [MENTION=3306843]kantjer[/MENTION]

The building system was rewritten this weekend. You might want to take a look at that...

https://github.com/topjohnwu/Magisk/commit/c6d2bf577f4f8b181370e53610799d2f67cc6099