Description
overwrites system sound files with silent sounds
Changelog
Battery / Camera
Code:
v1.0.0
- initial release
Source
Battery
Code:
https://github.com/f4bio/magisk-silencer-battery
Camera
Code:
https://github.com/f4bio/magisk-silencer-camera
@f4bio hello mate, do you think you could update the modules to the Magisk Module Template v4 and issue it to the Magisk repo? Also, tried installing the battery silencer on magisk 13.3 and it just wouldn't work, as soon as I install this module Magisk Manager crashes and when I reopen it all my modules are gone :/ tried twice and failed twice. not sure if it's something about my setup or an issue with compatibility of the module with the latest magisk.
de.er said:
@f4bio hello mate, do you think you could update the modules to the Magisk Module Template v4 and issue it to the Magisk repo? Also, tried installing the battery silencer on magisk 13.3 and it just wouldn't work, as soon as I install this module Magisk Manager crashes and when I reopen it all my modules are gone :/ tried twice and failed twice. not sure if it's something about my setup or an issue with compatibility of the module with the latest magisk.
Click to expand...
Click to collapse
Of course. I'll get right on it.
Which phone/rom are causing troubles for you?
I'll just flashed some of them on my h850/flumics/magisk13.3 without problems.
But, I will look into it asap
f4bio said:
Of course. I'll get right on it.
Which phone/rom are causing troubles for you?
I'll just flashed some of them on my h850/flumics/magisk13.3 without problems.
But, I will look into it asap
Click to expand...
Click to collapse
I'm on LG G2 and Resurrection Remix, however, I just clean flashed the latest version followed by magisk and your module installed correctly this time. Still, if you could get it added into the magisk repo that'd be really cool. Thanks
Hi, just report that this DO NOT work on Pixel 3.
Related
Hello, What is the rom with working android pay?
Pure Nexus - Doesnt work with magisk
Lineage doesnt work at all - rooted or not
Dirty Unicorns works, however apps crash.
Trying nitrogen os now
Any advice?
Thanks
.me said:
Hello, What is the rom with working android pay?
Pure Nexus - Doesnt work with magisk
Lineage doesnt work at all - rooted or not
Dirty Unicorns works, however apps crash.
Trying nitrogen os now
Any advice?
Thanks
Click to expand...
Click to collapse
Works for me with PureNexus and Magisk v12. Just make sure you turn on Magisk Hide.
liquidzoo said:
Works for me with PureNexus and Magisk v12. Just make sure you turn on Magisk Hide.
Click to expand...
Click to collapse
Tried a couple of times - worked with 11.x
I have no idea what I am doing wrong.
On latest Lineage with Franco Kernel + Magisk and passing safetynet. I have my card set up successfully with Android Pay but I haven't had a chance to actually test it, but I am definitely passing SN. Netflix shows up on Play Store as well.
I did a complete wipe, installed Lineage + Gapps, booted phone, then shut down phone and installed Franco Kernel, booted, shut down and then installed Magisk. I kept booting after flashes to check if Safetynet was being passed. It was not until I installed Magisk and used Magisk hide.
Google Strock Rom + ElementalX Kernel + Magisk 12.0 with suhide also works
.me said:
Tried a couple of times - worked with 11.x
I have no idea what I am doing wrong.
Click to expand...
Click to collapse
Don't enable Magisk busybox on Pure Nexus. There'll be a conflict with the ROM's busybox and it breaks Magisk Hide.
Because of issues like this (and others), busybox will no longer be included in Magisk starting with the next version.
Didgeridoohan said:
Don't enable Magisk busybox on Pure Nexus.
Click to expand...
Click to collapse
^This! Can confirm and I am running PN with Magisk, Android Pay works, Netflix appears in Playstore.
I've been using Android Pay with Pure Nexus & magisk for the past several months w/o any issues.
Didgeridoohan said:
Don't enable Magisk busybox on Pure Nexus. There'll be a conflict with the ROM's busybox and it breaks Magisk Hide.
Because of issues like this (and others), busybox will no longer be included in Magisk starting with the next version.
Click to expand...
Click to collapse
Thanks - I am beta testing v13 - hopefully it will work.
Cheers
Works with Dirty Unicorns / Magisk 12 .... I've noticed some form of weird volume issue where my volume lowers to reallllly low levels... so I'm looking for another ROM where it works and that has SmartBar Navigation customization.
Using PN latest ROM, with Magisk Hide enabled. Never had any problems, because it passes safety net every time
Can't reboot after installing modules
If you have updated Magisk from v13.3 and Magisk Manager v5.1.1 you might come across this issue. The solution is to clear data for the Magisk Manager (busybox integration has been updated and needs to be reloaded).
After clean install of beta 14 --> magisk 14.000 problem persists.. (im only using unified hosts adblock module)
Any idea for fix?
It has been mentioned a dozen times already.
Why don't you make a search before posting?
Just reflash 13.3 from recovery and this is it.
Just wait for a compatible Xposed module.
Unleashed by ONEPLUS 3T rooted
oTeMpLo said:
Can't reboot after installing modules
If you have updated Magisk from v13.3 and Magisk Manager v5.1.1 you might come across this issue. The solution is to clear data for the Magisk Manager (busybox integration has been updated and needs to be reloaded).
After clean install of beta 14 --> magisk 14.000 problem persists.. (im only using unified hosts adblock module)
Any idea for fix?
Click to expand...
Click to collapse
Did you try clearing data for the Manager? Logs?
RASTAVIPER said:
It has been mentioned a dozen times already.
Why don't you make a search before posting?
Just reflash 13.3 from recovery and this is it.
Just wait for a compatible Xposed module.
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
What? What Xposed module? Did you read before replying?
Didgeridoohan said:
Did you try clearing data for the Manager? Logs?
What? What Xposed module? Did you read before replying?
Click to expand...
Click to collapse
What's your issue pal?
You didn't like the word "module"?
Xposed's version is creating the problem.
Unleashed by ONEPLUS 3T rooted
RASTAVIPER said:
What's your issue pal?
You didn't like the word "module"?
Xposed's version is creating the problem.
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
No issue... I just didn't see the OP mentioning anything about Xposed, that's all. And I haven't seen Xposed causing the "can't reboot after installing module" problem before... But Xposed can cause a lot of problems, that's true.
Didgeridoohan said:
No issue... I just didn't see the OP mentioning anything about Xposed, that's all. And I haven't seen Xposed causing the "can't reboot after installing module" problem before... But Xposed can cause a lot of problems, that's true.
Click to expand...
Click to collapse
I font have can not boot probelm..
I have Reboot never complete s.. problem! And its there with 13.3 too..
Mybe coised by unified hosts 2.9 modul...
Sent from my ONEPLUS A3003 using Tapatalk
oTeMpLo said:
I font have can not boot probelm..
I have Reboot never complete s.. problem! And its there with 13.3 too..
Mybe coised by unified hosts 2.9 modul...
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
This thread is getting more and more confusing.
Are you saying that your device isn't booting after installing the Unified Hosts module?? That's a different issues than the one you wrote about in the OP (the text from my troubleshooting guide about not being able to reboot after installing a module)...
I have no issues installing the Unified Hosts Adblock module (v2.9) on my OP3T.
You're gonna have to provide a lot more details about your setup. And logs.
Didgeridoohan said:
This thread is getting more and more confusing.
Are you saying that your device isn't booting after installing the Unified Hosts module?? That's a different issues than the one you wrote about in the OP (the text from my troubleshooting guide about not being able to reboot after installing a module)...
I have no issues installing the Unified Hosts Adblock module (v2.9) on my OP3T.
You're gonna have to provide a lot more details about your setup. And logs.
Click to expand...
Click to collapse
it BOOTS FINE!
in does not REBOOT (restart) -after some time (rebooting is endless..) have to forcepower off!! and unified host is the only module i am using... in Magisk
unistaling magisk .. phone reboots fine.
EDIT:
(ok its magisk alone.. endless reboot) again.. mybe have to disable Systemless hosts ? -- will try next...
in my experience, magisk v14 does not create magisk.img, which makes modules fails to install.
i have to clean flash 13.3 and upgrade to 14 beta directly via twrp, then it works even via magisk manager
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
recepo1 said:
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
Click to expand...
Click to collapse
working fine here. maybe a root/magisk issue.
bober10113 said:
working fine here. maybe a root/magisk issue.
Click to expand...
Click to collapse
What rom are you on and which version of magisk are you running?
recepo1 said:
What rom are you on and which version of magisk are you running?
Click to expand...
Click to collapse
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
bober10113 said:
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
Click to expand...
Click to collapse
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
recepo1 said:
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
Click to expand...
Click to collapse
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
bober10113 said:
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
Click to expand...
Click to collapse
Thank you appreciate your help i will give it a try
I have tried everything for hours to get viper4android to work with no avail until now. Go to the xda download page and select the beta version. Boom. It works. I know you might have long forgot this or already figured it out but I had to share
old legacy magisk module has been working for months and months.
Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you
urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!
For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.
One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.
The latest OTA update made my phone bootloop if i re-flash magisk patched init_boot image...
After I asked Stock users, it looks like it's a GrapheneOS june update + Magisk specific issue.
Do someone else also have this issue?
Phone boots normally, then reboot to recovery instead of reaching lock screen.
For now, I re-flashed panther-factory-2023061402 init_boot.
Have you tried Magisk canary version? or maybe GrapheneOS doesn't like june update and newest Magisk and you need to either go back down to stable Magisk or an older version of Magisk?
Actually, after re-reading your OP, a module might be the cause of the bootloop -- I've recently seen similar behavior from other members where device bootloops or crashes during/right-after loading & starting up -- if you were on the stock ROM I would suggest you loading up in Safe Mode to see if it is a module issue; I don't know anything about GrapheneOS so I don't know if it offers anything similar. I wonder if the adb command to remove modules at boot would work....
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Albirew said:
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Click to expand...
Click to collapse
knew it....
glad I helped get you there!