Database Develop

[Module][v4.1] ViPER-FX **Discontinue**

COLOR="Red"]This thread will discontinue, Now I'm published my new mod's thread under Magisk, that mod includes Whole new ViPERFX app and many other mods and upcomings so From now everybody please follow this thread below:
[Module] ViPERFX
https://forum.xda-developers.com/apps/magisk/viperfx-t3667145[/COLOR][/SIZE][/B]
Introduction:
ViPER4Android is very popular audio mod around the world of Android and probably the best audio mod ever made. But there is so many complexity ViPER4Android couldn't go further through, so I wish "ViPER-FX" could be a project to let our beloved ViPER4Android step in advance. Original V4A details at ViPER4Android Official forum.
Modifications:
+ Based on ViPER4Android v2.5.0.5
+ New Material UI and Icon
+ App rotation enabled.
+ Default install as system app to prevent task kill.
in MIUI or some rom could be installed as user-app
for IRS compatibility [Experimental]
+ The zip edition includes apk.
Recommendation:
* Magisk Manager, Framework installed.
* Android 5.0+
* To update from ViPER-FX v4.0 (v4.0 only) first remove it.
How to install?
* Flash the zip using Magisk Manager or Custome recovery.
# Track this thread using the URL below.
URL: [url]http://forum.xda-developers.com/showthread.php?t=3535401[/URL]
Thanks To:
Code:
[user=4470081]@topjohnwu[/user] for Magisk Framework.
[user=3901724]@zhuhang[/user] and ViPER520 (Founders of ViPER4Android).
[user=4445176]@guitardedhero[/user] | [user=5704037]@repey6[/user] | [user=5210243]@exodius48[/user] | [user=6118476]@#mrk[/user]
for helping/support/testing.
...and those I forgot to mention.
I spend dedicated time, made pressure on brain and did hard work to make this perfect
If you like my post please hit Thanks and give a rate....
~~ Feel The power of ViPER-FX ~~
Contributors
metaspook
Version Information
Status: Stable
Current Stable Version: 4.1
Stable Release Date: 2017-01-13

The long waited finally come, will try this out.

the title is a bit misleading:
-this is not [Magisk], this is a [Module]
-it's not 100% clear if you packed the Magisk module or if you also offer a modded App (in thread description)
-it also has the same id as @topjohnwu 's module...
id=v4a
name=ViPER-FX
version=Base v2.5.0.5 | MKM v4.0
versionCode=3
author=ViPER’s Audio | Mod by Metaspook
description=ViPER-FX is a system wide audio enhancing software, modified edition of ViPER4Android.
support=https://www.androidfilehost.com/?w=files&flid=143525
donate=http://vipersaudio.com/blog/?page_id=95
Click to expand...
Click to collapse

@metaspook
Can you delete V4A app inside "\system\priv-app\ViPERFX" in next release? Because if V4A app installed inside /system/ there will be no sound improvement by IRS. Tested on my device running MIUI rom, dunno on other rom.
I use sepaker & many times change the IRS, but no sound improvement.

crusader727 said:
the title is a bit misleading:
-this is not [Magisk], this is a [Module]
-it's not 100% clear if you packed the Magisk module or if you also offer a modded App (in thread description)
-it also has the same id as @topjohnwu 's module...
Click to expand...
Click to collapse
Got it... actually I had to make this thread in short time making this of thread n sort it as well as possible is a bit hard something could be missing, but this thread will be more informative, well sorted soon...
Thank you.

exodius48 said:
@metaspook
Can you delete V4A app inside "\system\priv-app\ViPERFX" in next release? Because if V4A app installed inside /system/ there will be no sound improvement by IRS. Tested on my device running MIUI rom, dunno on other rom.
I use sepaker & many times change the IRS, but no sound improvement.
Click to expand...
Click to collapse
Do u'v installed Magisk n flash the zip through it?
B'cz this is a whole new way to dealing with system.
If u did but after that also don't work let me know.

metaspook said:
Do u'v installed Magisk n flash the zip through it?
B'cz this is a whole new way to dealing with system.
If u did but after that also don't work let me know.
Click to expand...
Click to collapse
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).

exodius48 said:
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).
Click to expand...
Click to collapse
OK I'll release next update separately..

I can't tell whether or how this differs from the existing V4A module offered by topjohnwu.

Cool. I'd like to try this out. I just had some questions:
1. What do these commands do:
Code:
/data/magisk/sepolicy-inject --live -s mediaserver -t mediaserver_tmpfs -c file -p read,write,execute
/data/magisk/sepolicy-inject --live -s audioserver -t audioserver_tmpfs -c file -p read,write,execute
2. Why are the following folders blank?
Code:
system/etc
system/lib/soundfx
system/vendor/etc

oreo27 said:
Cool. I'd like to try this out. I just had some questions:
1. What do these commands do:
2. Why are the following folders blank?
Click to expand...
Click to collapse
1. It helps to keep Viper FX alive in SELinux enforcement.
2. Into these directories necessary files will be extracted or pulled from original /system.
Thanks to wanna know. :good:

metaspook said:
1. It helps to keep Viper FX alive in SELinux enforcement.
2. Into these directories necessary files will be extracted or pulled from original /system.
Thanks to wanna know. :good:
Click to expand...
Click to collapse
Oh. I didn't think to check in the update-binary. It feels like this is a complicated script for sure:
Code:
# Push files
unzip -oq $ZIP "system/*" -d $MODPATH
unzip -pq $MODPATH/system/priv-app/ViPERFX/ViPERFX.apk assets/libv4a_fx_jb_$DRVARCH.so > $MODPATH/system/lib/soundfx/libv4a_fx_ics.so
ui_print "[OK] Pushing files."
# Config files modification.
for X in /system/etc/audio_effects.conf /system/etc/htc_audio_effects.conf /system/vendor/etc/audio_effects.conf; do
cp -af $X $MODPATH$X
sed -i '/v4a_fx {/,/}/d' $MODPATH$X
sed -i '/v4a_standard_fx {/,/}/d' $MODPATH$X
sed -i 's/^libraries {/libraries {\n v4a_fx {\n path \/system\/lib\/soundfx\/libv4a_fx_ics.so\n }/g' $MODPATH$X
sed -i 's/^effects {/effects {\n v4a_standard_fx {\n library v4a_fx\n uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b\n }/g' $MODPATH$X
done; ui_print "[OK] Config modification."
Does this mean that if I uninstall this mod, Viper is completely uninstalled without any changes present in my entire device? If so, it's a pretty good implementation.

Nice! Works just fine on my Nexus 6. Will this be submitted to the Magisk repo? Would be useful to have it in the manager...

oreo27 said:
Oh. I didn't think to check in the update-binary. It feels like this is a complicated script for sure:
Code:
# Push files
unzip -oq $ZIP "system/*" -d $MODPATH
unzip -pq $MODPATH/system/priv-app/ViPERFX/ViPERFX.apk assets/libv4a_fx_jb_$DRVARCH.so > $MODPATH/system/lib/soundfx/libv4a_fx_ics.so
ui_print "[OK] Pushing files."
# Config files modification.
for X in /system/etc/audio_effects.conf /system/etc/htc_audio_effects.conf /system/vendor/etc/audio_effects.conf; do
cp -af $X $MODPATH$X
sed -i '/v4a_fx {/,/}/d' $MODPATH$X
sed -i '/v4a_standard_fx {/,/}/d' $MODPATH$X
sed -i 's/^libraries {/libraries {\n v4a_fx {\n path \/system\/lib\/soundfx\/libv4a_fx_ics.so\n }/g' $MODPATH$X
sed -i 's/^effects {/effects {\n v4a_standard_fx {\n library v4a_fx\n uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b\n }/g' $MODPATH$X
done; ui_print "[OK] Config modification."
Does this mean that if I uninstall this mod, Viper is completely uninstalled without any changes present in my entire device? If so, it's a pretty good implementation.
Click to expand...
Click to collapse
1. The code I wrote looks a bit complicated but its for to reduce the size of the module (you can see I didn't packed the driver separately, codes are extracts those from the apk) and for more task will be done in less lines.
2. Yes.. obviously that's why using Magisk framework is so useful. It wont change anything in /system while installing nor in uninstalling your /system would be intact.

Didgeridoohan said:
Nice! Works just fine on my Nexus 6. Will this be submitted to the Magisk repo? Would be useful to have it in the manager...
Click to expand...
Click to collapse
Thanks... yes I wish also soon.

exodius48 said:
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).
Click to expand...
Click to collapse
Actually I pushing the apk into the system cause if Viper install as user app in data, 3rd party or internal app killer kill it and Viper looses to output the effect even also when remove from recent list. but I have an idea if its just happens with your MIUI rom... can you give me your ROM's 'build.prop" file ???

Is not working for me, IS activated on Magisk Modules Install,
But V4A say "Install/Update now?", Samsung S5 G900m, Is rooted using SuperSU 2.79, Latest Magisk Manager/Installer,
I Installed this V4A why magisk "Refuses" to open Modules download page "No Modules Found", And i have to download manually from internet. (SafetyNet says RED, Root and Magisk is green in Magisk Manager)
V4A is installed as System App, And SELINUX is Permissive,
I Try to change V4A to user APP, But not working;

metaspook said:
Actually I pushing the apk into the system cause if Viper install as user app in data, 3rd party or internal app killer kill it and Viper looses to output the effect even also when remove from recent list. but I have an idea if its just happens with your MIUI rom... can you give me your ROM's 'build.prop" file ???
Click to expand...
Click to collapse
Yes you're right. But on MIUI (especially MIUI 8 on my device) i can control it. We can lock app into taskbar and turn off MIUI optimization for selected app by turn off background restriction. Those will prevent MIUI kill running app.
build.prop file attached. :good:

metaspook said:
1. The code I wrote looks a bit complicated but its for to reduce the size of the module (you can see I didn't packed the driver separately, codes are extracts those from the apk) and for more task will be done in less lines.
2. Yes.. obviously that's why using Magisk framework is so useful. It wont change anything in /system while installing nor in uninstalling your /system would be intact.
Click to expand...
Click to collapse
This is pretty good. I installed this and it's working great. Just a quick question, I don't suppose it can work on phone calls as well? I was looking to get my bluetooth volume increased.

oreo27 said:
This is pretty good. I installed this and it's working great. Just a quick question, I don't suppose it can work on phone calls as well? I was looking to get my bluetooth volume increased.
Click to expand...
Click to collapse
Not sure about it... Test urself, look can work or not

[MODULE] DisableMultiUserMod (build.props) v1.3 (for Magisk 14.0)

Thats my first productive creation for XDA, so dont be to hard to me
I don't like to have features, which I never use, so I always disable or remove everythink i dont need.
On my custom roms I always diable the multi user mode by adding the following line to the build.prop:
Code:
fw.max_users=1
I was annoyed to edit this file after each ROM update.
So I created this module. It just adds the above mentioned line to the build.prop.
It is really simple, but now I don't need to edit the build.prop.
Maybe for someone this can be useful.
It works with:
- Android 6.x (Tested on OnePlus X and OnePlus 3 with CM13)
- Android 7.x (Tested on LOS 14.1 and OxygenOS 4.5.x)
v1.3: Update to Magisk Template 1400 (14.0).

Looks good but I would change the modid to something other than template. This is in the config.sh file and defines the folder it uses under /magisk. Anyways I used your zip as a template for my own build.prop edits that I will post shortly. I'll throw a little credit your way too.

Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643

dima-82 said:
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.

FHC1998 said:
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
Click to expand...
Click to collapse
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).

dima-82 said:
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
Click to expand...
Click to collapse
It depends on the device, I originally tested on a few, and some needed this line.
For instance, I tested your module on my device (ZenFone 2 laser) and it worked perfectly without the line, but on my friend's ZenFone 2 it kept showing the UI even though not allowing creating more users.

@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk

mp3deviant721 said:
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?

dima-82 said:
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
Click to expand...
Click to collapse
The build I'm running is 7.1.1. Haven't tried 7.1.2 yet. Yes on the "nightly" build.
Sent from my ONEPLUS A3000 using Tapatalk

@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.

Here is the module on my device :silly:

dariomrk said:
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Click to expand...
Click to collapse
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.

dima-82 said:
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
Click to expand...
Click to collapse
Oh, I didn't see that, I will check if it does the exactly same thing (probably yes)...
---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------
Just checked it out, and yes it does the exactly same thing

Please I need multiuser enable magisk module​ for Android 6

dima-82 said:
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
Here

Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)

I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?

dima-82 said:
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
Click to expand...
Click to collapse
Yes have other 5 modules

You installed / activated only this very one module and got a bootloop?
Before I created this module I edited the build.prop manually. And if you make a mistake there, you will get a bootloop as well.
May be your OS does not support this property.
I tested on my devices only, and it worked always.
Eventually you can try an other module from @FHC1998, which should do the same:
https://forum.xda-developers.com/showpost.php?p=71936097&postcount=3

jhobc said:
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
Click to expand...
Click to collapse
You could eventually try this mod:
https://forum.xda-developers.com/apps/magisk/module-single-user-mod-t3639486#post73160966 by @seebz

please delete thread

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?

[EOL][MOD] BlackenedMod v3.1 (Pixel 3 / Pixel 3 XL)

Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex in the past about the general idea of creating something else that follows what he started with his PK's Tuning Script for Pixel 2 (XL) but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
These scripts is created with the goal of improving both battery life and performance on our Pixel 3 (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with all of you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Note: These scripts is not recommended to be modified or customized by the user.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting these scripts fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the scripts
3) Move the scripts to the following location;
/data/adb/service.d and give it the following & needed file permissions (0775)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for all generations of released Pixels!
Credits:
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2019-01-06
Last updated: 2019-10-25

Note: The changelogs have been strictly moved to the release posts.

Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?

freebee269 said:
Thank you for this, I will give it a try. I was hoping someone would come up with a script that we can use to automate whatever we want at the kernel level. I feel like this could make the stock kernel much better as far as battery life and performance. I know you said use whatever kernel, but Do you recommend using the stock kernel for this?
Click to expand...
Click to collapse
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:

On 2xl there was a file wich showed that mod works. How about 3 xl?

I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?

xFirefly93 said:
Of course. BlackenedMod is universal across the whole Pixel 3 (XL) line-up, so it will work more than perfect with stock kernel, if that is what you are using!
:highfive:
Click to expand...
Click to collapse
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?

blaze9090 said:
On 2xl there was a file wich showed that mod works. How about 3 xl?
Click to expand...
Click to collapse
Gordietm said:
I remember on the pixel 2 XL there would be a file formed internal storage that showed that the script was working. That doesn't seem to happen on this device?
Click to expand...
Click to collapse
For now, you have to manually create a folder in your internal storage named "logs" (without quotes) because of some security kind of thing that Google have addee which prevents "automatically" created folders to even be made at all.
Otherwise the specific output log, that tells you if the script could execute or not, won't be generated because of a non-existing path / folder.
I will though look around for a possible workaround and see if it can be added directly within the BlackenedMod script for maximal flexibility directly on-the-fly.

freebee269 said:
i was using proton kernel. so i went back to stock kernel through fastboot. upon booting the white google splash screen popped for about 1 sec then my phone rebooted and i got the your device is corrupt screen. i then rebooted to bootloader and loaded twrp img file. i then rooted the stock kernel with magisk. after that i still got the your device is corrupt message but i was able to continue after that and it booted up fine. so looks like you dont want to do this on stock kernel that is not rooted. heh.
Click to expand...
Click to collapse
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.

Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk

gaseoso said:
Installed in Pixel 3 with Botleggers and Proton V10, at the moment everything is perfect, thanks for the work! I will report results!
Enviado desde mi Pixel 3 mediante Tapatalk
Click to expand...
Click to collapse
Enjoy!

xFirefly93 said:
You need Magisk (=root) and the Busybox Magisk module for even being able to use BlackenedMod.
Click to expand...
Click to collapse
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?

freebee269 said:
it looks like my phone keeps saying my device is corrupted. i've restarted 2 times and both times it says that and you cant get past that screen unless you hit continue. any ideas how to get this to work without the phone doing that?
Click to expand...
Click to collapse
Try with clean flashing stock firmware.

*Deleted*

xFirefly93 said:
Try with clean flashing stock firmware.
Click to expand...
Click to collapse
that worked. i backed up my current system image and data in twrp. then did the flash-all.bat without -w. then went back into twrp and rooted the stock kernel. then went back into twrp and restored my backup. thanks a lot. will report back on how its gone after a couple days.

Telegram:
Not for going off-topic far too much now but..
If you want to hang out a little, try previews / betas of BlackenedMod for Pixel 3 (XL) before they are officially released or just want to meet a lot of awesome people from every possible corner of the woeld - then join the official Telegram group, fully dedicated to the P3(XL) line-up here.
:highfive:

Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?

Gordietm said:
Will you eventually have different versions for different kernels or are you keeping the mod universal for the pixel 3 XL?
Click to expand...
Click to collapse
I am keeping it universal with everything good / great / greater than greatest from every kernel organized in the same package and place.

so i followed instructions, got it all done, rebooted, i'm good to go? don't need to do anything just set it up and go right?

Is there a way to tell if this is working?

[MOD][FIX] Audio Bitrate Increase For Poco X3 NFC

Disclaimer :
Code:
I am not responsible for any damage to your device!
Use this mod at your own risk!
What's this?
This mod increases the audio bitrate on video recording from a disgraceful 96kbps to a respectable 320kbps. Thus, giving a richer, more pleasing audio quality.
Still confused? Click here for a better explanation
Requirements :
- A rooted phone with magisk installed
- An opened mind (important!)
Contributors :
@Jt380p
@Slim K
* NOTES * (READ) :
- Not all ROMs are compatible with this mod, you might end up in a bootloop. YOU HAVE BEEN WARNED!
Download :
https://drive.google.com/file/d/1wr-p7puOL8nYb1wj1AyVbh9XmMp5kRKI/view?usp=sharing (Flash with magisk manager)
Source :
https://forum.xda-developers.com/Mi-9/themes/magisk-audio-bitrate-increase-t3927810
Audio files provided by @Slim K
Thanks to :
@Slim K
@topjohnwu for Magisk
Created : 7/11/2020
Last updated : 7/11/2020

reserved

Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:

Slim K said:
Just tried it on stock MIUI with stock camera and Gcam. Works like a charm. Ty :good:
Click to expand...
Click to collapse
For me it works on Stock, but not on Urnyx05 GCam. Thanks Dev.

Lineage android 11 will benefit from it, or that is already implemented in them?

So which ROMs are not compatible?

Aki-to said:
So which ROMs are not compatible?
Click to expand...
Click to collapse
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.

Slim K said:
This mod uses magisk module template to replace a file in vendor folder. A tip for beginners using such a mod is to inspect it to know what it does. For example in the root of the module zip you will find the folder system, which has the needed folders/files path for replacement. If you open install.sh in text viewer, you would read the line :
Bash:
set_perm $MODPATH/system/vendor/etc/media_profiles_vendor.xml 0 0 0644
That should tell you which file it is and their permissions. Now open the same path on your ROM and look for that file, if it exists, then it should work. Although not every camera app (e.g gcam) uses that file.
Click to expand...
Click to collapse
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
This mod is also so extremely tiny, you could pretty much make these changes manually. Just take care of permissions and replace the file, that's it. It's even less complicated than working with /etc/fstab, it seems.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.

Aki-to said:
Thanks, this was very helpful.
Indeed, it seems like a very easy set of scripts, did not expect that. However, the only thing I could not find is where the default functions are actually called, though I assume these are generic functions that are always called by Magisk, no matter which module is being installed.
Click to expand...
Click to collapse
You assume correctly. The path to the functions can be usually found in /data/adb/magisk/util_functions.sh on your device.
Perhaps I should release a couple of mods myself, if mod devs are getting such a Magisk Module template thing, anyway, which pretty much does all the work, already.
Click to expand...
Click to collapse
Why write code twice when it already exists and works for everyone.

Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.

nike1973 said:
Hello, could someone please confirm if it works on firmware xiaomi eu 12.0.4. stable, thank you very much.
Click to expand...
Click to collapse
Yes it works

Thank you. Works on MIUI EU 12.0.6.

Eu 12.0.6, super stabilization (on stock camera) crashes when module is active.

I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!

Anyone tried on Xiaomi.eu rom?
Running 12.0.8.

Hi!
gkhnkaanyrtc said:
I flashed it to the phone. The stock camera app still records audio at 127kbps. Does not save with 320kbps!.I use Indonesian stable miui 12/android 10. please Help!
View attachment 5272691View attachment 5272693
Click to expand...
Click to collapse
Hi! I have the same problem ... Did you fix it? I use Miui 12.0.1 with Android 11

320kbps should be the default, I wonder why the f**k Xiaomi gives us 96kbps.

Does it work in Pixel Experience rom on Surya?