Unity is now deprecated. It's recommended to switch to MMT-Ex unless you absolutely need your mod to work in non-magisk environments
This is a developement thread for Unity (Un)Installer
Unity Installer allows the install/uninstall of a mod on any device regardless of root solution (or lack thereof) in use.
Compatibility:
Magisk 19+
Supersu
Rootless
Any other root solution (Like LOS Su)
See the Github Wiki for how to make your own unity module
Upgrading from v3.3 to v4.0? See here
Downloads
XDA:DevDB Information
Unity Installer, Tool/Utility for the XDA Community Apps
Contributors
ahrion, Zackptg5
Source Code: https://github.com/Zackptg5/Unity
Version Information
Status: Stable
Current Stable Version: v5.0
Stable Release Date: 2019-12-30
Created 2017-03-26
Last Updated 2020-01-04
[No message]
[No message]
I have BT's issue installing this module on Pure Nexus for Kenzo/Kate (SD650)
ExEdd said:
I have BT's issue installing this module on Pure Nexus for Kenzo/Kate (SD650)
Click to expand...
Click to collapse
You must have installed other modules, probably my deep_buffer Remover because this module does NOT touch your bluetooth settings. This module is simply a framework for other modules to utilize and edit audio policy and audio effect files on your system.
ahrion said:
You must have installed other modules, probably my deep_buffer Remover because this module does NOT touch your bluetooth settings. This module is simply a framework for other modules to utilize and edit audio policy and audio effect files on your system.
Click to expand...
Click to collapse
I not have other modules or mods, only install Magisk and then AudModLib (downloaded through Magisk Downloads), when I reboot my device after install the module BT crash
ExEdd said:
I not have other modules or mods, only install Magisk and then AudModLib (downloaded through Magisk Downloads), when I reboot my device after install the module BT crash
Click to expand...
Click to collapse
Don't know what to tell you man. All this mod does is copy certain configs to a magisk directory and then magisk symlink them to your system.
The only thing I can think is that you have a boot.img compatibility issue with magisk.
Good news guys. I finally found a fix for AM3D and Dolby Atmos to work 100% in enforcing on both MagiskSU/SuperSU, Magisk OR System install.
This will be available in the AudModLib v1.3 update I will be pushing soon. I'll obviously fix any more bugs or make any other additions in the meantime.
ahrion said:
Good news guys. I finally found a fix for AM3D and Dolby Atmos to work 100% in enforcing on both MagiskSU/SuperSU, Magisk OR System install.
This will be available in the AudModLib v1.3 update I will be pushing soon. I'll obviously fix any more bugs or make any other additions in the meantime.
Click to expand...
Click to collapse
I can't wait! I really think that is going to make everything work . I prefer the SeLinux to be enabled with it my responsibility to flip if it didn't automatically. Looking forward to it!
JohnCorleone said:
I can't wait! I really think that is going to make everything work . I prefer the SeLinux to be enabled with it my responsibility to flip if it didn't automatically. Looking forward to it!
Click to expand...
Click to collapse
You wont need it anymore i only enabled permissive because of my mods i wont need it after this
ahrion said:
You wont need it anymore i only enabled permissive because of my mods i wont need it after this
Click to expand...
Click to collapse
But it does spoof being enabled correct?-Because I get a Google Services warning to uninstall SELinux changer
JohnCorleone said:
But it does spoof being enabled correct?-Because I get a Google Services warning to uninstall SELinux changer
Click to expand...
Click to collapse
So this won't be an app, this will be as part of the script. It essentially makes a few things permissive and allows the appropriate things to be activated, those that effect AM3D and Atmos.
Hi. Thanks for the mod. If I download and install through magisk or even download through magisk I get installation error. Doesn't say why. I'm on Z5C Nougat and fully rooted. Thanks Kam
[UPDATED] Audio Modification Library
v2.3:
- Script addition to allow various audio mods working with SELinux Enforcing
- Remove (audmodlib)service.sh and replace with pos-fs-data(.d) audmodlib.sh, which should fix when root may be lost upon installing certain mods
Download
Previous Changelogs (Audio Modification Library):
HTML:
v2.2:
- Added audmodlib.sh post-fs-data.d script
- Fix selinux injection script to work for MagiskSU/SuperSU (system and systemless)
- Install script fixes
v1.1:
- Hotfix for bootloop issues on some devices
v1.0
- Initial Magisk release
ahrion said:
This is my Magisk framework called Audio Modification Library that allows that installation of multiple audio mods without having compatibility issues
Click to expand...
Click to collapse
This is so very timely. There is a demand for this.
How do I install this on Xiaomi Redmi Note 3 PRO?
mvarejao said:
How do I install this on Xiaomi Redmi Note 3 PRO?
Click to expand...
Click to collapse
Are you kidding me?
Just get an iPhone.
ahrion said:
Are you kidding me?
Just get an iPhone.
Click to expand...
Click to collapse
No I'm note, because I dont know and understand those things but thanks any way for you help
mvarejao said:
No I'm note, because I dont know and understand those things but thanks any way for you help
Click to expand...
Click to collapse
You don't know how to flash a zip or install Magisk?
My friend, why are you in this forum?
ahrion said:
You don't know how to flash a zip or install Magisk?
My friend, why are you in this forum?
Click to expand...
Click to collapse
Go easy on the guy... He's obviously new and inexperienced and probably here to learn...
@mvarejao You should probably do a whole lot of reading before continuing.
Go to your device forums. You'll most likely find a lot of useful information there, among other things threads like this (where you'll find lots of resources and reading material): https://forum.xda-developers.com/redmi-note-3/how-to/xiaomi-redmi-note-3-sticky-roll-t3528728
Related
The first builds of Lineage are out for the shamu finally!
download.lineageos.org
How do I get rid of the ugly watermark across my screen?
The link to the nightly version doesn't work
Link to nightly worked fine for me. Haven't flashed yet, but it downloaded, albeit slowly.
https://download.lineageos.org/shamu
How to remove this cm to lineage migration build background ?
People who have the watermark did you flash the nighly or experimental?
From my understanding the experimental build is only used for migration from CM and will have that watermark no matter what, the nightly build should have no water mark. I believe they posted this info on their site.
You're supposed to flash nightly over experimental. Just read the instructions...
Dopamin3 said:
People who have the watermark did you flash the nighly or experimental?
From my understanding the experimental build is only used for migration from CM and will have that watermark no matter what, the nightly build should have no water mark. I believe they posted this info on their site.
Click to expand...
Click to collapse
can confirm - no watermark at nightly building!
Strange how everytime I try to download the nightly it fails. No matter what browser I use
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
MartinN6 said:
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
Click to expand...
Click to collapse
You mean permissive, but you can use stock kernel enforced, a bit tricky, you need to root with supersu, latest beta sr3 runs fine. Superuser from los page doesn't recognize viper4a for root at all. I flashed latest arise and supersu, reboot, viper4a still not recognized for root, uninstall viper4a driver, supersu recognize viper4a now, confirm it. Reboot to recovery and reflash latest arise. Now it's working.
If you want Dolby too you have to use blackbird kernel and stay permissive.
coremania said:
You mean permissive, but you can use stock kernel enforced, a bit tricky, you need to root with supersu, latest beta sr3 runs fine. Superuser from los page doesn't recognize viper4a for root at all. I flashed latest arise and supersu, reboot, viper4a still not recognized for root, uninstall viper4a driver, supersu recognize viper4a now, confirm it. Reboot to recovery and reflash latest arise. Now it's working.
If you want Dolby too you have to use blackbird kernel and stay permissive.
Click to expand...
Click to collapse
Thanks for advice!!
And yes of course - sorry - I mean "permissive"
I flashed "Viper4Android_Cleaner_v1_3_Android_7x.zip" and than "ViPER4Android_2.5.0.5_guitardedhero.zip"
... and it works without any trouble ...
MartinN6 said:
Thanks for advice!!
And yes of course - sorry - I mean "permissive"
I flashed "Viper4Android_Cleaner_v1_3_Android_7x.zip" and than "ViPER4Android_2.5.0.5_guitardedhero.zip"
... and it works witout any trouble ...
Click to expand...
Click to collapse
Good, if it works that easy, but there was something about the cleaner, don't remember right now exactly, but it breaks something. May it was dolby.
Edit: using the cleaner always kills cast connection, that's why I didn't use it anymore
MartinN6 said:
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
Click to expand...
Click to collapse
Kernel Adiutor Mod should let you toggle that (requires root) under the Misc Controls tab. I would imagine the ad-filled subpar original Kernel Adiutor from the Play Store would too but I wouldn't recommend using that.
Is there an updater built in or do we flash all updates? Reading in other threads that ppl get a update notification when a new build is available. I'm on experimental cuz the nightly link didn't work when I tried last night
Dopamin3 said:
Kernel Adiutor Mod should let you toggle that (requires root) under the Misc Controls tab. I would imagine the ad-filled subpar original Kernel Adiutor from the Play Store would too but I wouldn't recommend using that.
Click to expand...
Click to collapse
Thanks!
I got it and it (Kernel Adiutor mod) works great!
Now AdAway works again (need SElinux permissiv) - that's very good!
Guys, whats your baseband or radio? My proximity sensor isn't working properly on LineageOS...
MartinN6 said:
Thanks!
I got it and it (Kernel Adiutor mod) works great!
Now AdAway works again (need SElinux permissiv) - that's very good!
Click to expand...
Click to collapse
How did you get those SOFT keys from. Pixel
hashtag_harsh said:
How did you get those SOFT keys from. Pixel
Click to expand...
Click to collapse
sorry I don´t understand what you mean with "SOFT keys" ?
Edit: Aah now I know!
Yes, it's from the mod - link next post! ->
hashtag_harsh said:
How did you get those SOFT keys from. Pixel
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/themes-apps/cool-pixel-mod-android-7-1-1-t3532951
Here you go
---------- Post added at 19:57 ---------- Previous post was at 19:54 ----------
LeroViten said:
Guys, whats your baseband or radio? My proximity sensor isn't working properly on LineageOS...
Click to expand...
Click to collapse
Latest
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Can someone help with me proper zip files to install this mod on Lineage OMS Silesh ROM?
Help yourself.
zeomal said:
Help yourself.
Click to expand...
Click to collapse
Thanks bro, but that's the viper4Android, but I'm looking for specific Viper4Arise module
Satzz said:
Thanks bro, but that's the viper4Android, but I'm looking for specific Viper4Arise module
Click to expand...
Click to collapse
Download and install the ZIP as necessary from the page. Viper4Arise requires no additional configuration, other than setting SELinux as permissive (su set enforce 0).
Here's the main ARISE page: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 and the Android File Host link is https://www.androidfilehost.com/?w=files&flid=59044 where you can download the various ARISE systems.
I'm currently running Silesh's Lineage OMS 05/02 build on an XT1642. I downloaded the 2.3.3 Deuteronomy sound system, booted into TWRP recovery and flashed the zip, alongside SuperSU v2.79 SR3 beta (from https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133). It's working and I've not had to change SELinux thus far (left at enforcing).
Thanks so much, it was really helpful
Sent from my Moto G4 Plus using Tapatalk
I am creating this guide for Magisk v13 and working modules. Please let me know if there are additional ROMs that this guide works with, but I am trying to keep the steps as simple as possible.
Magisk Installation Instructions:
Download Latest PureNexus / PA ROM and follow those instructions
Boot into the ROM and go through the initial set up, at this point verify that SafetyNet is passing. If it is not you may need to factory reset and re-install your ROM.
Reboot into TWRP
Flash the attached modified Magisk-v13-Pixel (from Goodwin_c)
Flash the attached verified boot signer (from Chainfire)
Reboot the System
Uninstall the version of Magisk Manager that shows up in the drawer
Install the attached version of MagiskManager_v13_new5.apk (from Goodwin_c)
Open Magisk Manager (you may need to wait a bit, I had to clear it from my recents a few times before it launched and asked for file system permissions)
Go to the app settings and tick on Magisk Hide
Re-run SafetyNet and verify it's passing
Working Modules
I will create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
Modules I have modified to work with Pixel:
Emoji One - systemlessly replaces emojie font with Emoji One.
Tethering Enabler - enables tethering on phones where it is disabled by the manufacturer/provider.
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
mac796 said:
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
Click to expand...
Click to collapse
These still looks like the ones @goodwin_c created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
uodii said:
These still looks like the ones @goodwin_c created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
Click to expand...
Click to collapse
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
mac796 said:
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
Click to expand...
Click to collapse
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
chadgauth said:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
Click to expand...
Click to collapse
That's cool maybe I'll give it another shot.
chadgauth said:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
Click to expand...
Click to collapse
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?
It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
uodii said:
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?
It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
Click to expand...
Click to collapse
Yeah, I haven't tried Titanium backup, I'm using Solid Explorer and Greenify with root and they seem to work alright. I am still using new1, I will update to new5 and play with Titanium to see if I can get it to backup and reinstall an app
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
I'm very interessted about how to modify modules to work with Pixel device !
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
Only custom rom? Anyone tried on stock image?
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?
I just want to keep updated to his modification.
I have been using his modified Magisk v12, but finding it from RR thread.
There is no way to know if it is updated or not.
The zip failed to flash for me. Couldn't unpack boot image.
Pixel running PN 7.1.1, twrp RC1.
maflin18 said:
The zip failed to flash for me. Couldn't unpack boot image.
Pixel running PN 7.1.1, twrp RC1.
Click to expand...
Click to collapse
Try TWRP RC2
TENN3R said:
Only custom rom? Anyone tried on stock image?
Click to expand...
Click to collapse
The stock image should most likely work, if it works for you or someone else in this thread let me know and I'll update the OP.
y2kbugleung said:
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?
I just want to keep updated to his modification.
I have been using his modified Magisk v12, but finding it from RR thread.
There is no way to know if it is updated or not.
Click to expand...
Click to collapse
I'll update the post date in brackets when I make updates here. Goodwin_c does not have his own thread, so I've just been monitoring his android file host account. The original poster has not updated or maintained his guide from the RR thread, so I created a new one to be as up-to-date as possible and include modules as I modify them.
foski said:
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
Click to expand...
Click to collapse
I've included both of those. I basically have been using beyond compare to compare the arise module that works with pixel to other modules and re-zipping them and testing with my device.
I see. Thanks.
Btw do you know the difference between v1 and v5 apk?
It seems MagiskHide is gone on v5?
I have tried Magisk-V13 on Pixel-XL with stock ROM.
I haven't tried it with stock kernel, since SafetyNet won't pass (as far as I understand).
Tested with Elemental-X + MagiskManager-v1, SafetyNet does not pass. App always says "cannot use Play service"
Tested with Kirisakura-Rebase-1.36 + MagiskManager-v1, SafetyNet passes.
MagiskManager-v5 does not come with MagiskHide, so I assume it cannot handle SafetyNet.
Both MagiskManager v1 and v5 loads very slowly.
Before the UI could be used normally (it means Magisk is loaded?), ROOT cannot be obtained.
So those boot-up root-required action would probably fail.
Hi everybody,
I want to show you how to install Viper4android on your phone running developer preview 3 or later with Android O.
IM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE!!
First download the zip from Androidfilehost or from below.
Zip
https://www.androidfilehost.com/?fid=673368273298967857
Busybox
https://www.androidfilehost.com/?fid=961840155545578665
Extract it to any folder, you will have two files now, a Viper4android App and a flashable Viper4android zip.
Reboot into recovery and install the zip, I also recommend a custom kernel like the Jolla Kernel which already has Android O support for loudness control (for my Nexus 5X).
Boot normally install BusyBox and launch Viper4android.
Select install drivers, grant root permission and wait until it is installed.
If a IO Error occurrs don't worry it'll work anyway.
Reboot and open any file manager.
Delete the Viper4android folder in "/system/priv-app".
Delete "/system/vendor/etc/audio_effects".
Install Viper4android app you downloaded before.
Reboot once again and open Viper4android - driver are working now.
Tested on my Nexus 5X with Android 8 developer preview 3.
Leave a like if it helped.
Reserved
Kindly share BusyBox APK.. as play store busy box unable to work.. can't install properly..
vijaygogawale said:
Kindly share BusyBox APK.. as play store busy box unable to work.. can't install properly..
Click to expand...
Click to collapse
Ok
Done Androidfilehost link is uodated
Thargorsson said:
Ok
Done Androidfilehost link is uodated
Click to expand...
Click to collapse
App installed.. but busy box not installed.. error
vijaygogawale said:
App installed.. but busy box not installed.. error
Click to expand...
Click to collapse
Which device do you have and which Android kernel, android version etc... I need Basic information.
Thargorsson said:
Which device do you have and which Android kernel, android version etc... I need Basic information.
Click to expand...
Click to collapse
Device Angler,
Kernel Stock,
Android 8 DP3,
vijaygogawale said:
Device Angler,
Kernel Stock,
Android 8 DP3,
Click to expand...
Click to collapse
Systemless root?
And which supersu
Thargorsson said:
Systemless root?
And which supersu
Click to expand...
Click to collapse
Magisk v13,
vijaygogawale said:
Magisk v13,
Click to expand...
Click to collapse
Aha I've only tested with latest supersu that might be the problem.
Try the 2.82 version.
Thargorsson said:
Aha I've only tested with latest supersu that might be the problem.
Try the 2.82 version.
Click to expand...
Click to collapse
Will try and report back
vijaygogawale said:
Will try and report back
Click to expand...
Click to collapse
Good. btw did you deleted the old Viper4android folder and installed the new app as user app? And changing enforce to permissive also fix some problems.
Thargorsson said:
Good. btw did you deleted the old Viper4android folder and installed the new app as user app? And changing enforce to permissive also fix some problems.
Click to expand...
Click to collapse
Working now, phonograph not supported.
vijaygogawale said:
Working now, phonograph not supported.
Click to expand...
Click to collapse
Cool
Anybody get this working on Pixel XL (Marlin) on 8.0 - Sept security release? SuperSu 2.82 - SR4
jbirdyRazr said:
Anybody get this working on Pixel XL (Marlin) on 8.0 - Sept security release? SuperSu 2.82 - SR4
Click to expand...
Click to collapse
Hows the exact process you wen through?
I have not implemented yet. Was wondering if anybody else had. Now using SuperSu 2.82-SR5 and TWRP 3.1.1.0. Now that TRWP works now without having to fastboot, I will try this mod. If I get it working I will let you know.
Ah k
I went through the entire procedure including deleting the system app and installing the io fix version.
The app tells me that drivers are working but i there is no difference in sound.
Turing Master power on and off dosen't seam to make any diffrence. What is going on?
snehgada said:
I went through the entire procedure including deleting the system app and installing the io fix version.
The app tells me that drivers are working but i there is no difference in sound.
Turing Master power on and off dosen't seam to make any diffrence. What is going on?
Click to expand...
Click to collapse
Which device, Rom and kernel? And also which music player are you using? Also try enabke developer options in Viper and select disable selinux and/or enable FX compatibility mode.
This threat will be for useful magisk modules for our great sagit. More helpful will be modules not present in magisk repo
I'm starting first:
1.Debloater v13.4 - Debloating MIUI Apps
2.Google Sans MOD Font v1 - Different Font
3.Mi 6 ALL in One Mod by Danilo v1.5 (dan3840) - Couple of mods specially for Mi6 (round corners, 1080p,120fps etc.)
4.YouTube Vanced black themed v13.18.54 - Best YouTube black (noAd) mod
1.Xposed systemless by rovo89 for Xposed framework
2.Enable camera2api by zanglang for enabling the GCam support
3.Icebox plugin for speedup the Ice box's freezing and defrosting
1. Enable camera2api (for google camera hdr+)
2.Dolby Atmos Classic (Better and louder sound)
pCloudsp said:
1.Xposed systemless by rovo89 for Xposed framework
2.Enable camera2api by zanglang for enabling the GCam support
3.Icebox plugin for speedup the Ice box's freezing and defrosting
Click to expand...
Click to collapse
Which sdk using are you for mi 6?
(When I Try install xposed, my mi 6 stuck bootloop)
Destiny97 said:
1. Enable camera2api
2.Dolby Atmos Classic
Which sdk using are you for mi 6?
(When I Try install xposed, my mi 6 stuck bootloop)
Click to expand...
Click to collapse
sdk25 xposed 89.2 systemless
disable resource hook first
pCloudsp said:
sdk25 xposed 89.2 systemless
disable resource hook first
Click to expand...
Click to collapse
How can I do that?
I found in xposed settings! Thank You!
Are you guys using Xposed on Oreo? If yes, what sdk version and settings? I get stuck on bootloop even when I disable resource hooks.
Sent from my MI 6 using Tapatalk
brwolfgang01 said:
Are you guys using Xposed on Oreo? If yes, what sdk version and settings? I get stuck on bootloop even when I disable resource hooks.
Click to expand...
Click to collapse
I use the sdk 27 90.0-beta1 i suppose beta 3 will work too but idk why i haven't updated it ?
You should disable resource hook before flashing the zip and use the compatible apk it was called xposed magisk apk easy to find
ArinAbdul said:
I use the sdk 27 90.0-beta1 i suppose beta 3 will work too but idk why i haven't updated it [emoji28]
You should disable resource hook before flashing the zip and use the compatible apk it was called xposed magisk apk easy to find
Click to expand...
Click to collapse
Oh you mean I need to flash Xposed via this app instead of Magisk?
Sent from my MI 6 using Tapatalk
brwolfgang01 said:
Oh you mean I need to flash Xposed via this app instead of Magisk?
Click to expand...
Click to collapse
No you need to install the apk then flash thr zip I flashed it in twrp do the same as mine worked fine also before booting i wiped dalvik cache
pCloudsp said:
sdk25 xposed 89.2 systemless
disable resource hook first
Click to expand...
Click to collapse
What Dobly module version are you using?
zeCosta said:
What Dobly module version are you using?
Click to expand...
Click to collapse
Is there even a difference apart from interface?
pi4a7a said:
Is there even a difference apart from interface?
Click to expand...
Click to collapse
I dont know. Im looking for a version that works on mi 6. I tryed couple ones and it didint work.
zeCosta said:
I dont know. Im looking for a version that works on mi 6. I tryed couple ones and it didint work.
Click to expand...
Click to collapse
try the classic one
zeCosta said:
What Dobly module version are you using?
Click to expand...
Click to collapse
Actually both le pro 3 and le max 2 are working. But if you want to install viper and dolby together, you will need to install old version of VIPER.
pCloudsp said:
Actually both le pro 3 and le max 2 are working. But if you want to install viper and dolby together, you will need to install old version of VIPER.
Click to expand...
Click to collapse
You can use arise so you can both have dolby and viper (yes the latest 2.5.0.5 one) plus the magisk compatibility module with the mod. Just configure install options in arise_customize.prop file then flash the zip. And you can try, add/delete other mods (included in arise) by creating other arise_customize.prop files and reflash the same zip to do it too.
I use FRONTCAM_PORTRAIT_FIX. It has officially turned my phone into a Pixel.
mahdif62 said:
I use FRONTCAM_PORTRAIT_FIX. It has officially turned my phone into a Pixel.
Click to expand...
Click to collapse
That a magisk module? Hand it over.
pi4a7a said:
That a magisk module? Hand it over.
Click to expand...
Click to collapse
Here you go: https://forum.xda-developers.com/mi-6/themes/support-gcam-hdr-mi6-t3758876/post75777225#post75777225
Anyone can tell me how can Google DNS module help us?
pi4a7a said:
Anyone can tell me how can Google DNS module help us?
Click to expand...
Click to collapse
i flashed this module today. its working ( at least for me ) but ping time become so bad about 400ms. my ping time with my internet provider is about 25ms.