Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working (READ CAREFULLY)
TWRP doesn't work, at least the one by vache, THEREFORE INSTALL MAGISK ON ANDROID 11! Thanks (and sorry) to @Zainullahk1234 for signaling this problem on the guide
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATION (install magisk while on android 11)Ok let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
I SUGGEST INSTALLING MAGISK WHILE YOU ARE ON ANDROID 11 WITH TWRP!
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this "guide" comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first!
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALL
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
The aux output didn't work the first time, we have to tweak some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX (this needs a better solution)PREMISE: This works only if you don't need Bluetooth headsets because we are going to disable it I think (I'm not an expert)
Open Developer Options in settings.
Find Disable Bluetooth Hardware Offload and enable it
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Force headset switch (Huawei defaul...
Enable Use alternate way to detect headsets
That's it, reboot for safety measure.
If you know how to do this in a better way please help us below! I don't need bluetooth that much but it's better to have it than not.
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol.
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
bluetooth headset can fixed by going in develpers setting and turning on disable bluetooth a2dp hardware offload and that looks like this:
wesleyvanneck12345678 said:
bluetooth headset can fixed by going in develpers setting and turning on disable bluetooth a2dp hardware offload
Click to expand...
Click to collapse
Ye but that way aux/jack stops working for me
Tommy0000 said:
Ye but that way aux/jack stops working for me
Click to expand...
Click to collapse
heh i got both enbled and it works for me
wesleyvanneck12345678 said:
heh i got both enbled and it works for me
Click to expand...
Click to collapse
Ok! I'll try!
Wich one have you enabled?
disable Bluetooth offload in dev options
force switch in phh patches
alternate switch in phh patches
Maybe it's a coded not supported by my headset
Tommy0000 said:
Ye but that way aux/jack stops working for me
Click to expand...
Click to collapse
foudn the fix go to phh treble settings > misc features and enable use alternate way to detect headsets
Can you tell me, just to be sure what is enabled and what not? @wesleyvanneck12345678
Tommy0000 said:
Ok! I'll try!
Wich one have you enabled?
disable Bluetooth offload in dev options
force switch in phh patches
alternate switch in phh patches
Maybe it's a coded not supported by my headset
Click to expand...
Click to collapse
Tommy0000 said:
Can you tell me, just to be sure what is enabled and what not? @wesleyvanneck12345678
Click to expand...
Click to collapse
1 and 3 and also dont forget to enable disable Bluetooth offload in phh treble settings > misc features
wesleyvanneck12345678 said:
1 and 3 and also dont forget to enable disable Bluetooth offload in phh treble settings > misc features
Click to expand...
Click to collapse
Thanks, i'm going to update the guide!
It works for me too!
Tommy0000 said:
Thanks, i'm going to update the guide!
It works for me too!
Click to expand...
Click to collapse
btw you sayed bluetooth audio doesnt work it does work with same settings
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same settings
Click to expand...
Click to collapse
I hadn't enable offload fix in phh's patches menu, maybe it was that, maybe I forgot to turn on something else when I tried
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same set
wesleyvanneck12345678 said:
btw you sayed bluetooth audio doesnt work it does work with same settings
Click to expand...
Click to collapse
Click to expand...
Click to collapse
you have to enable this to for bluetooth audio phh treble settings > misc and then features force-disable A2DP offload
so that in develpers settings and treble settings has to be anbled for bluetooth audio for aux force switch in phh patches
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
View attachment 5464431
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
Holy crap thank you sooo much.. I love this pixel gsi 12 ROM running on moto g stylus 5g 2021..
Bluetooth and 2g only for calls and text were my only bugs...
Now Bluetooth works flawslesy with this guide...
Any fix for volte..
I tried to flash the Qualcomm zip fix but twrp error"arcititure unknown"'
Anyone???
Awesome ROM guys... keep up the great work .
jhjhjhjhjhjh said:
Holy crap thank you sooo much.. I love this pixel gsi 12 ROM running on moto g stylus 5g 2021..
Bluetooth and 2g only for calls and text were my only bugs...
Now Bluetooth works flawslesy with this guide...
Any fix for volte..
I tried to flash the Qualcomm zip fix but twrp error"arcititure unknown"'
Anyone???
Awesome ROM guys... keep up the great work .
Click to expand...
Click to collapse
With Bluetooth you mean Bluetooth headsets? You should try with patches for audio that i included in the guide, idk much about it tho :/
Tommy0000 said:
With Bluetooth you mean Bluetooth headsets? You should try with patches for audio that i included in the guide, idk much about it tho :/
Click to expand...
Click to collapse
Yes my Bluetooth before I found this guide my audio was choppy and distorted...now it's just like my stock ROM...I'm so happy now...thanks..
Viper and Dolby both working on with Bluetooth as well...loving it!!!!
Again I just need a volte fix...I have to turn off volte and the data turns to "E" then calls and text work fine...but on LTE/5g no calls or MMS.. I use a free text app for now as a work around...
jhjhjhjhjhjh said:
Yes my Bluetooth before I found this guide my audio was choppy and distorted...now it's just like my stock ROM...I'm so happy now...thanks..
Viper and Dolby both working on with Bluetooth as well...loving it!!!!
Again I just need a volte fix...I have to turn off volte and the data turns to "E" then calls and text work fine...but on LTE/5g no calls or MMS.. I use a free text app for now as a work around...
Click to expand...
Click to collapse
There is a volte fix in patches too i think, also to me the preferred data connection was 3g maybe try to change it
3g setting puts my phone in "E' Wich is 2g speeds basically..I get calls and MMS but slow data...I have a 5 g phone that supposed to have MMS and calls over LTE/NR....
Tommy0000 said:
There is a volte fix in patches too i think, also to me the preferred data connection was 3g maybe try to change it
Click to expand...
Click to collapse
jhjhjhjhjhjh said:
3g setting puts my phone in "E' Wich is 2g speeds basically..I get calls and MMS but slow data...I have a 5 g phone that supposed to have MMS and calls over LTE/NR....
Click to expand...
Click to collapse
Yes this doesn't work do some roms do give you 5g do its android 11
t
Tommy0000 said:
Hello everyone!
I'm happy to announce that I successfully installed android 12 on nairo, this guide comes with post install tweaks (that to me are the most important part)! I used a XT2075-3 Dual sim.
Warning: I don't take any responsibility if you brick your phone. This is just how I achieved this result. Read the guide in its entirety first! Back up everything with TWRP on an external drive.
I've tried 2 times and the first time it worked properly except for some things that we (thanks also to @wesleyvanneck12345678 ) have found a fix for:
THINGS NOT WORKING AND THINGS TO FIX ON POST-INSTALLNot working
TWRP didn't work, at least the one by vache, this still doesn't work but i personally don't care much because this rom comes with magisk preinstalled.
Post-install fixes
The clock and notification are behind the double hole punch, we'll need to fix the statusbar padding on post-install.
Audio routing needs some tweaks, we have to fix some things in developer options and phh's patches (thanks to @wesleyvanneck12345678 audio was a deal breaker for me and they helped me fix it)
AT THE TIME OF WRITING BLUETOOTH HEADSET DOESN'T WORK, if you can help on that let's discuss it on the comments[ SOLVED ] yay!
GSI INSTALLATIONOk let's start, actually before that i recommend backing up all partitions on a hard drive via twrp, it literally saved me from bricking my phone the first time so you should do it too.
First of all you should obviously unlock your bootloader, google is your friend on that.
Install Pixel Experience Alpha, I've used the arm64 vndklite version i'm not sure if it's the correct one but it worked. I followed this guide on how to install a gsi rom on a super partiton phone.
After installing the rom should work properly by itself, the audio works only through the speakers and the clock and notifications are under the double cutout cameras, let's see how to fix both.
POST-INSTALLAUDIO FIX
Open Developer Options in settings
Find Disable Bluetooth Hardware Offload and turn on the setting
View attachment 5464431
Reboot
Go in settings and find Phh Treble Settings
Open Misc features
Enable Use alternate way to detect headsets
Scroll down and find Force-disable A2DP offload and turn it on
That's it, reboot and both aux and bluetooth headset should work!
STATUSBAR PADDING FIX (portrait mode)View attachment 5464363
After installing Magisk we can fix the statusbar. Install this module in magisk manager by downloading the zip from XDA and selecting it from your download folder.
The installation of this module is unusual, when installing it will ask you to install some presets on the phone, use the volume buttons to choose the CUSTOM option (last one, not the pixel 5), this will create 5 text files in the storage of your phone.
Reboot if you want (idk if it's necessary but I did it anyway)
Use a file manager like total commander to navigate in your storage/emulated/0/com.logmd.n3o/ there will be 5 files.
Open the custom1left.txt, delete the number you see and write 240, save and close. 240 is the pixel distance from the left side of the screen, this size doesn't give me problems.
OPTIONAL: open the custom2left.txt and a different number like 260 if you want the clock more distant from the cutouts. Save and exit.
Open magisk manager and run the installation of the module again
Select the custom option another time, this time it will check the folder with the files we edited for new instructions.
Reboot
CRUCIAL if you are clumsy: connect the phone (with usb debug enabled) to a pc and with ADB run the command "adb devices" and tell the prompt on your phone to always grant permissions from that pc. This will help if you mess up the next steps by selecting a wrong option.
Once booted go to developer option in settings and find Display Cutout under Design settings.
!!!BE VERY CAREFUL NOT TO SELECT ANYTHING ELSE THAN N3O OPTIONS!!! Stock overlay display cutouts are bugged on android 12 and if you select one you will have to disable it via adb.
Select the option you we created earlier it will be called "N3O CST left custom1 (240px)"
That's it, check if it stays after reboot but there should be no problems.
View attachment 5464365
As you can see it works in the Notification panel too!
Ta-Da! (I guess) Let's have a conversation on this and find a fix for bt maybe lol. [SOLVED]
THANKS TO:
PIXEL EXP TEAM:@jhenrique09@phhusson@AndyYan@eremitein@poncesSTATUSBAR FIX:@LOGMDAUDIO FIX RESEARCHER :@wesleyvanneck12345678
Click to expand...
Click to collapse
when i installed it it didnt come with magisk?
im on arm64 ab
Zainullahk1234 said:
t
when i installed it it didnt come with magisk?
im on arm64 ab
Click to expand...
Click to collapse
Ohhh very weird, it happened to me once, try reinstalling system without wiping user data and using another date build, maybe they forgot to put it in :/
Related
This Guide helps on configuring the A.R.I.S.E. (Auditory Research in Sound Enhancement) Sound System, including Viper4ARISE, in your Axon 7. This fixes the low volume problem for the EU version of AXON 7 2017G and increases the quality in all the models. Among other features it reconstruct the signal for streaming audio, increasing the spectrum and bringing more detail to the sound. It is also compatible with Dolby ATMOS. The official thread is complicated since it offers a lot of different options. Here I try to provide an easy and straightforward guide for beginners. After a while you will be able to get into the universe of profiles, settings and extras explained in the official thread.
REQUIREMENTS:
- Since this package modifies your system partition, it requires unlocked bootloader and root.
- Another requirement is to have the Busybox patch. If your root method is not including it, just grab one of the many free Busybox Apps from Play Store.
WARNINGS:
- Since this module is not systemless, in case of an OTA upgrade you will need to reflash the stock system before performing an OTA upgrade, apply the upgrade and then reinstall the Sound System.
- Unfortunately there is no uninstaller so keep a backup of your system partition before proceeding with the installation.
DOWNLOADS:
For a safe installation begin using ARISE Deuteronomy 2.2.3 Patched. Some people likes better the sound athmosphere provide by this version. The latest stable release ARISE Deuteronomy 2.3.3 and other versions can be found in the official thread. However 2.2.3 patched has proven to be very stable and fully compatible with our device. Later on you can test upgrading to the current or another release.
Since ARISE Sound Systems rewrites the audio configuration depending on your settings, you may need the Dolby ATMOS add-on too to recover this feature.
You'll have to flash it using TWRP recovery 3.0.3 or Flashfire app.
INSTALLATION:
STEP 0: Ensure you have a backup of your system partition and you have downloaded the ARISE Sound System to the internal or external storage of your phone.
STEP 1: Disable Dolby ATMOS.
STEP 2: Flash ARISE Sound System version 2.2.3 patched either using TWRP or Flashfire.
STEP 3: Reboot, play some music, open Viper4ARISE, activate the master switch for your headset and enjoy. Save your current configuration in the hamburger menu before testing new settings. You can also tune the phone speakers, bluetooth and external USB DAC settings.
STEP 4 (Optional): If Dolby ATMOS is not working after applying the patch, Flash the Dolby ATMOS add-on.
TROUBLESHOOTING:
- If ask for driver installation then Open your favorite file explorer and go to: /vendor/etc and rename audio_effects.conf to audio_effects.conf.bak, reboot and follow step 3 again.
- Ensure you have unlocked the system partition by typing reboot disemmcwp in the system or TWRP terminal or ADB shell. and repeat from step 1.
MY SETTINGS:
My recommendation is to leave Dolby ATMOS disabled unless you are watching a movie or concert. You do not have to disable Viper4ARISE when using Dolby ATMOS, however do never mix surround or spatial processing in both, it will be a mess. I share my general settings as an starting point, however you can experiment with all the parameters to find the sweet spot for your gear. Do not forget to save your current configuration in the hamburger menu before testing new settings, it is hard to remember the detailed configuration afterwards:
Check that the Headset HiFi setting in your Phone settings is set to Super. and for Viper4Arise set:
Master Power ON
Spectrum Extension ON (only for low quality streaming)
- Strength: 0.2
Dynamic System ON (Headset Only)
- Listening Device: Common Earphone v2
- Dynamic Bass: 18% for acoustic music and high dynamic range sources, up to 29% when listening dance/electronic
ViPER Bass OFF (only activate it if your headphones require extra Bass. In my case I have it disabled).
- Bass Mode: Natural
- Bass Frequency: 40hz
- Bass Boost: 13dB
VIPER Clarity ON (It can bring up pretty good detail to the sound).
- Clarity Mode: Natural
- Clarity: 6dB
Master Gate (Limiter)
- Channel Pan:0%
- Output Gain: 2.3dB (set more if you want more output volume without making quantization noise audible)
- Limit Threshold: 0dB
After setting it, just toggle the master switch several times to hear the difference. You will realize how much quality can be extracted from this excellent Axon 7 hardware.
How was your experience?
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
vyurdin said:
Hello, I'm having issues having viper to download drivers, for some reason, I am unable to rename audio_effects.conf with either es file explorer or root explorer despite es file explorer saying renamed successfully but it wouldn't change or show after reboot. I made sure they both have root permission. I have also checked if I have busybox installed but it came with systemless root. Root Switch shows selinux is set to permissive. So i'm scratching my head trying to figure out what the issue is.
PS. forgot to mention my bootloader is also unlocked.
Click to expand...
Click to collapse
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Loader009 said:
Did you ever do a "reboot disemmcwp"?
If not, turn on usb debugging, connect the phone to your computer and do a "adb reboot disemmcwp".
This disables the write protection on /system.
Click to expand...
Click to collapse
It works now, thanks! luckily I didn't have to edit that file.
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
nupi said:
Did anyone get it to work on Cm13? For me the driver fails to load with status abnormal, both with stable and alpha of Deuteronomy
Click to expand...
Click to collapse
Change the Selinux to Permissive on boot.
reV17 said:
Change the Selinux to Permissive on boot.
Click to expand...
Click to collapse
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
Unfortunately I don't believe it'll work if you put it back to enforcing.
tele_jas said:
I love this mod, but every once in a while (like at least once or twice a day) I have to disable/ re-enable V4a or restart my phone because something goes wrong with it and it turns off (but shows it's on), like the driver unloads? So, I came back to the stock Dolby Atmos.
Click to expand...
Click to collapse
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have: the bootloader unlocked, F2FS filesystem, root, Xposed (all 9 modules working) and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
nupi said:
I shall try that. Can I put it back to enforcing after boot? I really dislike running devices on permissive...
Click to expand...
Click to collapse
You can try setting up V4A in enforcing mode using this guide.
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Killerdog said:
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Did you try xposed 87? November security patches broke the earlier versions
nupi said:
Did you try xposed 87? November security patches broke the earlier versions
Click to expand...
Click to collapse
i try updating xposed inside the app. update is ok, but if i activate any module it bootloop at next reboot.
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Killerdog said:
for me it doesn't work, it ask for install drivers every time i reboot, and for no reason selinux don't stay to permissive after reboot (with selinuxmodechangerv3.2).
so i have abnormal statuts in viper4arise.
i try with stock b06, stock b08 and stock b09, it never work for me (maybe is because of b09 bootstack).
i also cannot use xposed framework anymore with b09, i can install it but if i activate any mod and reboot my phone bootloop.
Click to expand...
Click to collapse
Try rooting your device using this method. The root includes Xposed (I have 8 modules up and running) and everything should be working. Probably using HelsAx7 as the base ROM could solve your problem.
tele_jas said:
> I used the latest 2.3.3, flashed it twice in the past month (also tried an older one, but not sure which one)? Also flashed just V4a, with the same issue
> I'm running Z.A.D. Mix7 (V.3) ROM
> Xposed is installed for status bar changes only, and re-orientated volume
> I did do the disemmcwp (had to do this for my font and emoji changes to stick)
> I was one of the few that have the actual ZTE unlocked bootloader, then I followed DrakenFX thread on how to root.
But... the reason I went to ARISE, was because I wanted to use my favorite music player, n7 music player..... Which isn't compatible with Dolby Atmos. So, the issue may have been with n7? I'm currently trying to decide between XenoAmp and Double Twist Cloud Player as my player of choice. I also used PowerAmp for about 4 years, even ran the beta (build 703) up until about 3 months ago, but am tired of the same Gingerbread style UI it's had for the past 3 or 4 years.
So, that's where I'm at.... I may try it again without n7?
Click to expand...
Click to collapse
PowerAmp and Player PRO are the best in sound quality, the second is even better. And both seem to be working fine with Viper4ARISE. What kind of source are you playing (bandwidth and bitdepth)?
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Teet1 said:
This makes my music sound sweet! I don't know if anyone experienced this but my phone has 0% sleep and is always 100% awake and heats up like an oven after flashing this I restored my backup and it's okay now
Click to expand...
Click to collapse
You can use wake lock detector to check what's wrong. The package is pretty stable. Could you please provide some more info (device, ROM, root method, media player, ARISE version, Viper4A configuration...)?
Oki said:
Dolby ATMOS is meant for movies or concerts. Music sounds horrible with Dolby ATMOS.
I have been using this mod for about a week now in this device without any issue. I have tested the three proposed versions, and I have, the bootloader unlocked, F2FS filesystem, root, Xposed and SafetyNet below this sound system.
What ROM are you using? Have you unlocked your system partition by doing a reboot disemmcwp in the terminal or adb shell? What version of ARISE Sound Systems are you using? How did you root your phone? Perhaps we could help you on this.
Click to expand...
Click to collapse
I'm wondering if you can help me with another issue I'm experiencing since I last posted here. My battery started draining really fast since I flashed the audio patch, I'm aware that's normal for viper but this is abnormal since the battery drains when the phone is not in use and it tends to stay warm. I have never had this issue when I had viper on my note 4.
The steps I have done for my phone:
Root method by jcadduono’s official thread in your safety net guide with success.
Done all steps with safetynet steps from above with success.
And I did the audio upgrade from this thread with success by using your preferred one.
And that's when my phone started draining more than it usually does for viper and being slight warm when not in use. I have already done a wipe before I did all these methods.
EDIT: Someone already mentioned the issue I'm having and I did not see that on mobile. I'm running all of those on A2017U stock rom running on b29 for additional info. I used stock music player, usb audio player pro (eXtream Software Development) for external dac and Equalizer + (DJiT) which i rarely use. I'll install wakelock detecter and ill report back what I find.
Hello Everyone,
This is a collection of modules and a 1 flashable zip to enable aptX and aptx-HD on Oreo ROMs that doesn't have them...
the original files are taken from OnePlus OOS Oreo ROM, this should work (one of the options) on any OReo ROM, it may also work on N Roms but that's is not tested.
all modules flash the lib files to different places (or to all places), please the options, and select what is appropriate to you.
Bug reporting.
if you're going to report any issue please attach a log (the log should be taken before enabling Bluetooth and should record it being enabled and then being connected to an aptX enabled device)
Updated on January 6th 2018:
- 3 Magisk Modules added Description bellow for each.
- all 3 modules are based on the latest 1500 (15.0) Magisk template.
- APTX-enabler.zip is not a Magisk Module it's a recovery flashable zip, Description bellow.
should Works On All Oreo Roms.
Requirement:
-Root
-Root file manager
-Recovery (TWRP) for flashable Zip
A- Manual Installation:
1- download & extract the zip attached. ( APTX-enabler)
2- copy the files from System/vendor/lib64 folder to same place on your device, 0644 permission to both.
2- copy the files from System/lib and System/lib64/ folders to same place on your device, 0644 permission to both.
3- open build.prob in a text editor (or through the file manager) and add the following line at the end of it.
Code:
persist.bt.enableAptXHD=true
persist.service.btui.use_aptx=1
persistent.bt.a2dp_offload_cap=sbc-aptx-aptXHD
5- reboot
B- Flashable Zip Installation
1- reboot to TWRP
2- flash APTX-enabler.zip
3- reboot
C-Magisk Module
1- Download one of the 3 modules (discretion bellow)
2- install through Magisk manager
3- reboot
Modules Description:
A- aptX-HD_OreoEnablerOOS.zip , add the lib files only to System/vendor/lib64/ , some Roms like OOS Oreo Roms only require that for aptX to be enabled, it's not only for OOS other Roms use that too, if you don't know Use option C.
B- aptX-HD_OreoEnabler2.zip , add the lib files to system/lib and system/lib64 only... some roms like Nitrogen doesn't require to add any Libs on the vender folder, if not sure also use Option C.
C- aptX-HD_OreoEnabler.zip, this will add the lib files to ALL possible places, insuring that no matter what ROM you have aptX works...if you don't know which folder your ROM uses either ask the Rom Dev or use this option.
Old lib Files and modules can still be found on the following folder
https://drive.google.com/open?id=1aJQiFlzFgQmDJb08QZ_NMLUc0eKqBPry
Credits to
@Riku Azhurlar for initial flashable zip
@simonsmh for the Initial Magisk Module
@bmg1001 & @ossito2012 for initial aptx files
OnePlus for Current aptX lib files
theduke7 said:
Hello Everyone,
The latest beta of Android Oreo doesn't have AptX support like the previous bet a builds (because of compatibility Issue)
It only plays on SBC, so until OnePlus brings it back, i found a work around but it requires ROOT.
The files provided, are from a Magisk module port to Nexus 6P ...thanks to @ossito2012 for providing the file
Click to expand...
Click to collapse
I appreciate the mention but I would like to say that I did no actual work, I merely tripped over it while looking for information about aptx in the XDA Forums, this dev named @bmg1001 hooked me up with zip file.
Remember you will need aptx capable BT headphones to see it switch from SBC to aptx. I would like to say I have a picky ear but there is not much improvement over SBC going to AptX, I think because the earbuds I have are cheap. The LDAC codec is much better but the Sony headphones that have that capability are crazy priced.
ossito2012 said:
I appreciate the mention but I would like to say that I did no actual work, I merely tripped over it while looking for information about aptx in the XDA Forums, this dev named @bmg1001 hooked me up with zip file.
Remember you will need aptx capable BT headphones to see it switch from SBC to aptx. I would like to say I have a picky ear but there is not much improvement over SBC going to AptX, I think because the earbuds I have are cheap. The LDAC codec is much better but the Sony headphones that have that capability are crazy priced.
Click to expand...
Click to collapse
yes i always forget to mentioned the earbuds part... OP3 here have LDAC support , but as you said the headphones are very expensive..,
thanks for you reply, i'll the dev name to credit.
If you go into developers options under Bluetooth audio codec and enable optional codecs it turns on apt hd and ldac turns on aptx without this.
Edit: I see what you're saying now when I actually connected the Bluetooth headphones I saw you can't change those options so I'm going to use the instructions thanks.
Thanks.. It worked.. You. Are Awesome...
Last time I tried a flashable zip (Someone posted a thread) on OpenBeta 24 (Android 7.1.1) but that time flashable zip didnt worked for me... But this time doing manually worked like a charm.. Thanks man
info2shail2010 said:
Last time I tried a flashable zip (Someone posted a thread) on OpenBeta 24 (Android 7.1.1) but that time flashable zip didnt worked for me... But this time doing manually worked like a charm.. Thanks man
Click to expand...
Click to collapse
yes i tested that too, it's an old port but it has N API files, so they wouldn'e work...
i was lucky i found the Oreo files
Glad it helped
Yes.. I know.. Thats y i said i tried on openbeta 24.. OB24 was on Android N 7.1.1 and even after that didnt worked for me.. But manually doing with your zip worked for me.. Thanks again
theduke7 said:
yes i always forget to mentioned the earbuds part... OP3 here have LDAC support , but as you said the headphones are very expensive..,
thanks for you reply, i'll the dev name to credit.
Click to expand...
Click to collapse
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
jokerpappu said:
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
Click to expand...
Click to collapse
I had said the same thing until I connected my Bluetooth headphones. It won't let you change from the default codec when connected. Which is what this is a work around for.
beeree7 said:
I had said the same thing until I connected my Bluetooth headphones. It won't let you change from the default codec when connected. Which is what this is a work around for.
Click to expand...
Click to collapse
When u connect Bluetooth headset it automatically detects and uses best settings for it. When i connected my aptx enabled device it auromatically chose aptxhd. When i connected a normal Bluetooth device with no aot3x ldac it automatically chose sbc. It seems to work like that. U cant change it afterward it takes the setting automatically
jokerpappu said:
When u connect Bluetooth headset it automatically detects and uses best settings for it. When i connected my aptx enabled device it auromatically chose aptxhd. When i connected a normal Bluetooth device with no aot3x ldac it automatically chose sbc. It seems to work like that. U cant change it afterward it takes the setting automatically
Click to expand...
Click to collapse
it's not working, OnePlus disabled the codec itself , that's why when you add those files to the lib folder, they don't over right anything... there's bug reports about it
https://forums.oneplus.net/threads/open-beta-25-bluetooth-aptx-is-not-working.656630/
so OnePlus said they temporarily disabled the codec, before adding those files, download a log app and see if it enables Aptx while pairing.
and i personally assisted the OnePlus BugHunters team collecting Logs for the issue...
your theory is right, in the future it should work automatically or with forced selection, at it's current state if you play any file it defaults to SBC only (try it)
I know that this thread is specifically for those running Oreo Open Beta. However, would it be safe to flash this for those running the most up-to-date OxygenOS (4.5.1)? Please let me know if you can. Thanks.
jokerpappu said:
Aptx is there if u choose enable optional codec. Look at the screenshot below. I know it shows aptx hd bt i have tried it with aptx compatible bluetooth headset and it works
The screenshot is without using any mod. Default oos oreo
Click to expand...
Click to collapse
You need to learn a lot more... Your screenshot missing bluetooth connected icon...
sorry wrong reply, never-mind this
B4oE said:
I know that this thread is specifically for those running Oreo Open Beta. However, would it be safe to flash this for those running the most up-to-date OxygenOS (4.5.1)? Please let me know if you can. Thanks.
Click to expand...
Click to collapse
the files are Oreo specific, if you search the forums, you'll find ones for Nougat and i think there's also a magisk module
jokerpappu said:
When i connected my aptx enabled device
Click to expand...
Click to collapse
Could you reveal what's your aptx enabled device?
Flashable Zip
@theduke7 heres a flashable zip for ya. since i was bored and had nothing better to do
Riku Azhurlar said:
@theduke7 heres a flashable zip for ya. since i was bored and had nothing better to do
Click to expand...
Click to collapse
thanks m8, added to OP with credit
i want to report that it works in nexus 6
using oreo rom
cDroid v4 had aptx working for nexus 6
so when i move to another rom it was not working
after flashing this it works again
can someone make magisk version for this
and'' call it aptx enabler for oreo '' for example
If aptx works for you you will see 4 options
If it's not working you will see 3 only
In the Bluetooth settings
A lot of people have complained about stuttering in between App switching and gaming. This guide helps you disable Dynamic refresh rate through MagiskHide Prop Config, which is easier than setting it manually and safer to disable if it doesn't work.
Disclaimer: Disabling Dfps (Dynamic refresh rate) will degrade battery life with prolonged use. According to my personal testing, battery life (SOT) decreased by 10-18% on average. Only use for short periods of time.
Click to expand...
Click to collapse
Requirements:
- Unlocked and rooted with Magisk v21.0.
- busybox-ndk.
- MagiskHide Prop Config installed (used often to pass safetynet CTS but can be used to set custom Props).
Instructions:
1- Run SU in your terminal of choosing.
2- Run props.
3- choose option 5 "Add/edit custom props".
4- choose n "New custom prop".
5- type in:
Code:
ro.vendor.dfps.enable
6- Default value should be true, type in false to disable.
7- choose 2 "post-fs-data".
8- choose n, don't reboot yet.
9- choose n again to set another prop.
10- type in:
Code:
ro.vendor.smart_dfps.enable
11- Default value should be true, type in false to disable.
12- choose 2 "post-fs-data".
13- Reboot.
Only tested on stock MIUI. Try at your own risk!
It works on MIUI eu 12.0.3.0.
No stuttering anymore !
Thanks man !
Do this affect to battery performance?
Segamalaga said:
Do this affect to battery performance?
Click to expand...
Click to collapse
Yes. For me i get 1 hour less of SOT. That means if i get 7-9 hours on average, with this mod i get 6-8 hours instead.
Doesn't this mess with L1 ? Damn , I need to back up my persist img
Joakin2k said:
Doesn't this mess with L1 ? Damn , I need to back up my persist img
Click to expand...
Click to collapse
NOPE. It doesn't mess with L1 certification or any for that matter. This is a systemless "vendor" modification not "persist", and as such very easily uninstallable. See attached screenshots.
Also the payoff/difference is huge if you're a power user. Try consistent 120Hz vs. stuttering 120Hz (sometimes drops to 30Hz) and you will notice immediately.
Slim K said:
NOPE. It doesn't mess with L1 certification or any for that matter. This is a systemless "vendor" modification not "persist", and as such very easily uninstallable. See attached screenshots.
Also the payoff/difference is huge if you're a power user. Try consistent 120Hz vs. stuttering 120Hz (sometimes drops to 30Hz) and you will notice immediately.
Click to expand...
Click to collapse
Excellent explanation ! , I don't care for battery (if is not something out of control) I charge my phone always twice a day, I read that even Xiaomi EU and MIUI MIX has this issue ...
Going back to stock or EU for performance, aosp based are very green in performance...
Any Rom recommendation ?
Is there a way to set the refresh rate to 90hz and disable the dynamic refresh rate after that?
Joakin2k said:
Any Rom recommendation ?
Click to expand...
Click to collapse
I've tried all the custom ROMs available for our device and recommend stock for now. Since all of them are based on stock kernel anyway, they're all MIUI ROMs in my opinion, but you can't blame devs for choosing to patch Stock MIUI when we don't even have Device sources released. TWRP for the same reason, Dynamic partitions are scary.
Skeuomorphic said:
Is there a way to set the refresh rate to 90hz and disable the dynamic refresh rate after that?
Click to expand...
Click to collapse
As far as i know, refresh rate is handeled by an Activity:
Code:
com.xiaomi.misettings/.display.RefreshRate.RefreshRateActivity
which handels Dfps. In turn Dfps handels the frequencies in between 30Hz-120Hz depending on the process(Activity) on the forground.
I can't use my pc for a week atleast (broken from tinkering too much) to find a workaround, but good news! Theoretically, this guide should also work in custom roms with 90Hz option in settings app. Try it on a custom ROM and share your experience with us. [at your own risk ofc]
Thanks for taking your time to answer sir
Will this still work if i set the display to 60hz?
I'm having problems hiding magisk manager(no magisk hide), I already turn off dynamic hz thx to you , changed device fingerprint for pixel 4(want certification)... But when I want to hide magidk manager (a Bank app can see it -already marked in hide-) it says some error , I don't know if it's the Miui security app , this never happened on AOSP, I'm on stock poco X3 , root + props hide config + vanced ... Any tip ?
olujnap316 said:
Will this still work if i set the display to 60hz?
Click to expand...
Click to collapse
Yes. Setting 60Hz in the Settings app will set it to a constant 60Hz, conversely setting it to 120Hz will set it to a constant 120Hz as well.
Joakin2k said:
I'm having problems hiding magisk manager(no magisk hide), I already turn off dynamic hz thx to you , changed device fingerprint for pixel 4(want certification)... But when I want to hide magidk manager (a Bank app can see it -already marked in hide-) it says some error , I don't know if it's the Miui security app , this never happened on AOSP, I'm on stock poco X3 , root + props hide config + vanced ... Any tip ?
Click to expand...
Click to collapse
This is a fairly famous problem with Magisk Manger hiding and SELinux enforcing, but easily solvable. Do the following:
1- Go to Play store and turnoff Play Protect scanning (interferes with magisk manager repackiging itself aka Hiding).
2- Force stop Manager.
3- Open Manager again and choose another name and apply.
4- Profit.
If this still doesn't work, try this:
5- Go back to step 2 and then open terminal.
6- Type SU.
7- then set SELinux to permissive by inputting:
Code:
setenforce 0
8- continue with step 3
9- then set SELinux back to enforcing by inputting in terminal:
Code:
setenforce 1
10- Done
Man... Worked Flawlessly... Never had that issue on AOSP roms.
Thanks ! no need to turn on/off selinux enforcement.
But , really, thanks for your attention and detail , I'm impressed Sr
To make things easier and more risk free, i have attached a config file to automate this process. New steps are even easier! Do the following:
1- Install the aforementioned modules.
2- unzip the attached .zip file to the root of internal storage.
3- Reboot.
New settings should've been applied successfully after reboot and the config file will delete itself.
Slim K said:
To make things easier and more risk free, i have attached a config file to automate this process. New steps are even easier! Do the following:
1- Install the aforementioned modules.
2- unzip the attached .zip file to the root of internal storage.
3- Reboot.
New settings should've been applied successfully after reboot and the config file will delete itself.
Click to expand...
Click to collapse
Does this mean that the manual method enables back the dynamic refresh rate after every reboot? Which this conf will solve by placing the conf file at the root of internal storage before rebooting the phone?
Skeuomorphic said:
Does this mean that the manual method enables back the dynamic refresh rate after every reboot? Which this conf will solve by placing the conf file at the root of internal storage before rebooting the phone?
Click to expand...
Click to collapse
The Manual method as well as this method both persist through reboots. Only difference is the complexity of the initial setup, but that's it.
Great tutorial.any good guide to debloat safely without root
Doesn't seem to work there, checked with the power monitor, and it still switch between 120/90/60/30/1 fps depending on the app/menu I'm in
CaPicote said:
Doesn't seem to work there, checked with the power monitor, and it still switch between 120/90/60/30/1 fps depending on the app/menu I'm in
Click to expand...
Click to collapse
Can you provide me the following?:
1- MIUI vers. (i.e 12.0.3.0 QJGEUXM)
2- Go to terminal a run su and then:
Code:
getprop ro.vendor.smart_dfps.enable
-Output should be false, if it's true, then you didn't set it right.
I think a lot of people mix up framerate and refresh rate. Just an FYI, the thing that should be of interest is the refresh mode in power monitor. Check these screenshots, the circled value should stay at 120Hz consistently. Another screenshot I provided below without this mod shows 60Hz encircled when device not touched(which we don't want). The value on the right side of it (also in screenshots) is the framerate provided from the app (process) and indicates the actual frames displayed on the screen, if the screen isn't changing or moving, then there is nothing to display 120 frames about and will drop to 1 fps, which is completely normal.
Version for Marshmallow is available here: https://forum.xda-developers.com/t/...zation-for-old-touchwiz-mm-framework.3372401/
Version for Nougat is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-n-framework.3692391/
Version for Oreo is available here: https://forum.xda-developers.com/t/...stomization-for-touchwiz-o-framework.3749479/
Version for Pie is available here: https://forum.xda-developers.com/t/...-14-customize-samsung-oneui-24-05-20.3908114/
Version for Q is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-2-0-30-12-20.4044757/
Version for R is available here: https://forum.xda-developers.com/t/...customize-samsung-oneui-3-x-14-03-21.4212051/
Firefds Kit [ S ]
Xposed module for Samsung S devices.
Known working devices:
Galaxy S20
Galaxy S20
Galaxy S10
Features
The module has the following features:
Fake system status to Official
Custom advanced power menu options:
Power off
Restart
Emergency mode
Recovery (with custom text)
Download
Data mode switch
Screenshot
Switch User (when multi user is enabled)
SystemUI restart
Flashlight
Screen Recorder (requires Samsung screen recorder app installed)
Disable restart confirmation
Enable performing power menu reboot / power off actions only after unlocking secure lock screen (stock behavior)
Disable display of power menu when secure lockscreen is locked
Change default behavior of reboot to reboot to recovery
Replace Reboot to Recovery icon with system default restart icon
Enable call recording and call recording settings
Replace add call button instead of call recording and adding record by menu option
Clock Size option
Enable Call ID and spam protection option
Enable Screen Record tile and Settings options
Enable screen record while in call
Enable additional advanced hotspot settings option
Hide VoLTE icon in status bar
Hide persistent USB connection notification
Hide persistent charging notification
Enable block phrases in messages app settings
Enable native blur on notification panel pull down
Enable multi user toggle
Set max user value selector
Show seconds in status bar clock toggle
Show AM/PM for seconds on clock toggle
Show clock date on right of clock toggle
Add date to status bar clock options
Enable fingerprint unlock on reboot toggle
Enable biometrics unlock on reboot toggle
Add network speed menu to show network speed in the status bar
Data icon symbol selection (4G, LTE, 4G+, 4.5G)
Show Data usage view in quick panel
Double tap for sleep
Hide NFC icon
Disable Bluetooth toggle popup
Disable sync toggle popup
Disable high level brightness popup
Hide carrier label
Carrier label size selection
Disable loud volume warning
Disable volume control sound
Disable low battery sound
Screen timeout settings
NFC behavior settings
Auto MTP
Disable camera temperature check
Enable camera shutter sound menu
Disable call number formatting
Disable SMS to MMS threshold
Force MMS connect
Bypass exchange security (currently not working)
Disable signature check
Disable secure flag
Attention
This version was tested by the community and not by me, as I don't have an Android 12 Samsung device.
THERE COULD BE BUGS/CRASHES/BOOTLOOPS, but it's pretty stable.
Please upload any xposed logs when you encounter any issue. I can't help you without the logs!
Installation
To install this module you need the following apps and modules installed on your device:
Magisk v24.0 and above - https://github.com/topjohnwu/Magisk/releases
Option 1 - Zygisk
LSPosed Magisk Zygisk Release module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Option 2 - Riru
LSPosed Magisk module v1.8.2 and above - https://github.com/LSPosed/LSPosed/releases
Riru Magisk module v25.0.0 and above - https://github.com/RikkaApps/Riru/releases
Download
Directly from LSPosed Manager or from Github : https://github.com/Xposed-Modules-Repo/sb.firefds.s.firefdskit/releases
Source Code
https://github.com/Firefds/FirefdsKit/tree/S
Known Issues
A lot has changed since Android 11. Since I don't have an Android 12 device all tests have been done with various testers. THERE MAY BE UNKNOWN ISSUES!!
Some features are removed on purpose. Since GravityBox has been working on Samsung Oreo devices without much issues, I only implemented features that need special Samsung coding.
Reporting Issues
When reporting an issue, please include Xposed logs and screenshots if any. Reporting should be done through Github - https://github.com/Firefds/FirefdsKit/issues
External Libraries
The project uses the following libraries:
https://github.com/rovo89/XposedBridge
https://github.com/rovo89/XposedMods/tree/master/XposedLibrary
Samsung framework libraries which are used for compile only
EdXposed Whitelisting
Users who want to use EdXposed's whitelist feature should whitelist the following apps:
Android System - android
Call - com.samsung.android.incallui
Call Settings - com.samsung.android.app.telephonyui
Camera - com.sec.android.app.camera
Contacts - com.samsung.android.contacts
Email - com.samsung.android.email.provider
Firefds Kit - sb.firefds.s.firefdskit
Messaging - com.samsung.android.messaging
MTP Application - com.samsung.android.MtpApplication
NFC - com.android.nfc
One UI Home - com.sec.android.app.launcher
Settings - com.android.settings
Smart Capture - com.samsung.android.app.smartcapture
Software Update - com.wssyncmldm
System UI - com.android.systemui
Credits
This module wouldn't have been here without the following people:
RikkaW - Creator of Riru Magisk module, which provides a way to inject codes into zygote process
@rovo89 - Creator of the original Xposed framework APIs
solohsu and MlgmXyysd - Creators of the EdXposed Magisk module and Installer that made all of this possible
@C3C076 - Creator of GravityBox Xposed modules, which I learnt a lot from
@wanam - Creator of the original XTouchWiz module, which this module is based on.
@topjohnwu - Creator of Magisk
@AbrahamGC - For the Extended Power Menu - Pie - Odex framework Smali guide
Big thank you to @m8980 and @ianmacd for testing countless versions and sending xposed logs
Telegram
Announcements and pre release versions - https://t.me/firefdskit
This is a moded version of Wanam's XTouchWiz:
https://github.com/wanam/XTouchWiz
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
okij said:
Hi @firefds, thanks a lot for releasing your module for Android 12! Highly appreciated!
Also thanks to @m8980 and @ianmacd for doing the testing!
The module is working very well on my S10e, although I have to admit that - since I'm on a custom ROM - I don't need all features and only use the Double Tap For Sleep function and the Advanced Power Menu.
There's one optical issue in the Advanced Power Menu that I would like you to fix: The additional icons for Recovery Mode, Download Mode and Restart SystemUI don't match the style of the original Samsung icons for Power Off and Restart, i.e. they have a different line thickness and use a font that's not consistent with the look of One UI 4.0.
I made a screenshot of how it looks with the current icons and an edited version of the screenshot of how IMHO it should look like, please see attached files.
For this I extracted the three PNG images from the res folder of your APK and edited them to match the look of One UI 4.0: I combined the shape of the restart icon, the colour of the original icons and added the Letters "R", "D" and "UI" with the Google Sans font, which is the standard system font of Android 12.
I attached the edited PNG images, so you can easily put them into your module.
I hope that you like the new icons and am looking forward for an updated version of your module. Thanks!
Click to expand...
Click to collapse
Thanks! This looks great! I'll add it to the next version
firefds said:
Thanks! This looks great! I'll add it to the next version
Click to expand...
Click to collapse
Thanks! I'm glad you like it and look forward to the next version.
IIRC Firefds Kit 11 uses the same icons (I have been using it until I switched to Android 12 two months ago), so you might use the new icons there too.
Thanks.
All my devices now bootloop with NoClassDefFoundError: com.android.systemui.BasicRune
Any chance we could add those whitelists to LSposed "Recommended"? Exactly the most important call recording check is missing.
Btw if LSposed 1.7.2 is installed, Riru can be uninstalled? -> looks like Sui uses Riru, so no switching.
In the end, I could leave Firefds enabled if I don't change anything, luckily call recording is on by default.
Thanks for the update for Android 12. Everything working good on my A52s 5g. Hope that one day you can add the ability to adjust the height of the navigation bar. That was available in the gravitybox app but there is no upgrade for 12 yet and not sure there will be which is why I've asked here... appreciate your efforts though.
Is there an easy way to fix bootloop in case something went wrong?
donkeyman1234 said:
Is there an easy way to fix bootloop in case something went wrong?
Click to expand...
Click to collapse
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me delete it worked and I didn't have to disable lsposed modules or the magisk
Kuba1996 said:
You can go in twrp to /data/ app/ then sort folder of date and first one should be folder with firefds app and for me it worked and I didn't have to disable lsposed modules or the magisk
Click to expand...
Click to collapse
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
donkeyman1234 said:
Thanks, but I mean if no twrp I can't boot into the phone, only stock recovery . Is there anything I can do( not factory reset)?
Click to expand...
Click to collapse
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root without custom recovery?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
You can look at last post here and try do something like that. Mabye try in recovery choose "update from adb" and try erase with adb command (your directory: riru-core). Or try use this but I dont think it will work
[Tool][Aroma] Magisk Manager Recovery Tool V2.5
Warning: It's not a Magisk module! Description This is a Magisk module management tool that can be used in Recovery mode. It's based on Aroma Installer. You can manage almost everything in Magisk with this tool. You can manage installed modules...
forum.xda-developers.com
Kuba1996 said:
Do You have oem unlock and debbuging on? If yes You can install twrp. Or mabye try sideload something like recovery arome file manager (possible working only in twrp). How You root witchout custom recovery?
Click to expand...
Click to collapse
I used magisk patched AP file to root. There is no twrp for s22u.
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Also You can flash in odin patched ap and rest of file but with HOME_CSC not CSC
Check this:
donkeyman1234 said:
I used magisk patched AP file to root. There is no twrp for s22u.
Click to expand...
Click to collapse
Had the same issue with my s22u. I reflashed through odin. Gonna try and flash this module again with magisk bootloop protector. fingers crossed.
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Hello,
Thank you for A12 update.
So nice to have your magic on this version.
I would also love to see the ability to adjust navbar, and the possibility to move cursor with buttons in navbar like in GravityBox.
For me, Force MMS to connect isn't working on BeyondRom 4.1.
Is it working for others ?
I am using LSPosed zygist latest version and safety net 2.2.1
nishantgupta107 said:
Update
Did try flashing it 2 more times, it is causing bootloop after enabling any option and restarting.
Recovered by disabling all magisk modules from adb.
Hope there will be a fix soon.
Click to expand...
Click to collapse
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
doggydog2 said:
Yup, currently the rule is don't do any change. I tried do partial changes, but no luck. I simply keep it running with default settings. Also bootloop recovery wasn't that fun, it did kill some OS settings I hardly noticed - i had to walk through all the settings.
Click to expand...
Click to collapse
Yes, some os settings did get reset. Not sure why. But now I'll wait for a stable release (I have reflashed it now 5-6 times)
Arobase40 said:
You can install Magisk Bootloop Protector module...
It will disable Magisk modules when bootloop occurs.
Click to expand...
Click to collapse
Thanks. I did install, but it did not work, the phone kept rebooting, reflash was my last resort.
Bootloop
S10 plus UI 4.1 A12
LSPosed-v1.8.0-6482-zygisk
I have owned LG V30/40/50 primarily for music listening. The downside was to activate the high impedance mode (for earphones under 50 ohm), one had to go through various processes involving adapters and cables. The other option for rooted devices was to edit the MIXER_PATH_TAVIL.XML file. That triggered the high gain output permanently.
For V60, that option is not directly available. The reason is that /vendor/etc/mixer_path.xml is located in super partition making the file not editable. So you could only force the high impedance mode by using adapter or cable option till now.
Using Magisk, I have written two modules that will allow you to substitute the system file and put your phone in high impedance mode permanently. Magisk simply loads the edited files as the effective ones (disabling the system file). You will notice increase in volume/gain when you enable/disable DAC in sound settings.
So I have Viper 4 installed with my module without any problem producing enhanced sound output from V60.
INSTALLATION:
1. Download the attached modules. Do not make any changes.
2. Save it on your phone.
3. Go to Magisk module page and choose install from storage option.
4. If you already have AML installed then uninstall that first.
5. Direct Magisk to the file you just downloaded. Now install AML first.
6. Reboot.
7. Install the Mixer.zip second (for high impedance effect) with Magisk.
8. Reboot.
Enjoy!
This module makes V60 more likable for listening to music. As you said, the new partition structure that is implemented in V60 made it impossible to edit the relevant files un-editable. Of particular value is your AML that does not make any sacrifices when listening in high impedance. Fantastic job!
I was myself thinking of undertaking a similar project but you delivered.
I think that as Android evolves, it is becoming more and more like iOS in terms what you can and can't customize. Thanks to John Wu for creating Magisk! He has extended the customizable life of Android.
I have been looking for a way to force my V60 in high impedance mode to get a boost in volume. There is no solution anywhere on web. I find the solution using an adapter or a cable very inconvenient. Not to mention that using them degrades the audio quality.
You have helped many of us music lovers (who have been looking for a permanent solution) by these modules. They work like charm. I haven’t found any problem so far. V60 sounds better than V50 in high impedance mode with full power of DAC.
As much as I love V60 for many reasons, the lack of triggering high impedance mode was a bummer. Now we are all set to enjoy this excellent phone from every angle.
Thanks man.
THANK YOU so much for this. works beautifully. but how did you get viper4 to work on the v60? i can't seem to figure it out
Actually it is not difficult at all. Since you have already installed the module for high impedance mode, all you need is the Viper 4. I suggest that you install this version of Viper 4. The reason is it is newer.
INSTALLATION:
1. Download the Viper 4.
2. Save it on your phone.
3. Install it as a Magisk module.
4. Reboot.
5. Once rebooted, you activate Viper by turning on the "Master limiter" in the app and configuring your desired options.
P.S.: If you don't want to add any other audio modules (like Dolby ATMOS etc.) then there is no need to install the AML module that is on this page. You can keep it (if desired) but it is not needed.
omg ur a legend! uve given me a 2 eargasms. every single guide says to install the viper4 apk... not the module... thanks again. btw which music player do you use?
Glad to know that you are enjoying the full potential of LG V60 in terms of music! I have the built-in music player that is in V60. The reason is it uses the inherent DAC in the best way. But I also have USB Player Pro.
Most of my music listening is streaming services. And V60 rocks just as much.
Please let us know should you need any help. We are a big and happy family here at XDA.
wondering if you could help me with this issue. i can't seem to get xposed edge and physical buttom master control to work on lsposed. they both install fine with no errors but they just dont work. i also have gravitybox on lsposed which does work so im not sure what the issue is
I don't use the apps that you are referring to. So I am not the right person to guide you in the right direction. However, I hope someone in the forum can help you.
Have you searched the XDA relating to your problem? Maybe it has been discussed earlier somewhere else.
yeah i figured it all out. thanks again
Awesome. Enjoy the best phone for audio listening — V60.
I`m unable to install the AML module. It says: Installation failed! Unsupported / Unknown image format. I also extracted the AML zip file with the same error message when installing. I would be very grateful if you could help me please.
Are you installing it as a Magisk module? I just tested it. It installs and works totally fine.
I`m sorry but I`m a complete noob when it comes to this. This is the very first time I do this. Where should I download Magisk app from. My Magisk app when installed has MODULES section at the bottom completely greyed out, so I cannot select it and under Magisk section up top I`ve got the following:
Installed N/A
Zygisk NO
Ramdisk YES
Under APP section:
Latest 25.2 (25200) (33)
Installed 25.2 (25200)
Package com.topjohnwu.magisk
So it looks like the Magisk app is installed, but not the Magisk itself. Where should I get the Magisk from?
You have to root your V60 that starts with unlocking the bootloader first. The process is well documented in this forum.
Thanks so much! I`ve heard about rooting, but I`ve never done it before. People say, that you might end up with a brick, if rooting process isn`t successful.
No worries.
Royaltiger said:
I have owned LG V30/40/50 primarily for music listening. The downside was to activate the high impedance mode (for earphones under 50 ohm), one had to go through various processes involving adapters and cables. The other option for rooted devices was to edit the MIXER_PATH_TAVIL.XML file. That triggered the high gain output permanently.
For V60, that option is not directly available. The reason is that /vendor/etc/mixer_path.xml is located in super partition making the file not editable. So you could only force the high impedance mode by using adapter or cable option till now.
Using Magisk, I have written two modules that will allow you to substitute the system file and put your phone in high impedance mode permanently. Magisk simply loads the edited files as the effective ones (disabling the system file). You will notice increase in volume/gain when you enable/disable DAC in sound settings.
So I have Viper 4 installed with my module without any problem producing enhanced sound output from V60.
INSTALLATION:
1. Download the attached modules. Do not make any changes.
2. Save it on your phone.
3. Go to Magisk module page and choose install from storage option.
4. If you already have AML installed then uninstall that first.
5. Direct Magisk to the file you just downloaded. Now install AML first.
6. Reboot.
7. Install the Mixer.zip second (for high impedance effect) with Magisk.
8. Reboot.
Enjoy!
P.S.: Audio Modification Library (AML) has been modified to accomodate this module. Now you can use this module with all audio modules in high impedance mode!
Click to expand...
Click to collapse
Will this work on the v50?
If you are fully rooted then V50 allows to fully edit the MIXER_PATH_TAVIL file directly.