Related
Hello, i bring to you the QuickRemote app for your AOSP Marshmallow rom, CM13 or any rom based on CM13 (Resurrection Remix, Bliss, AICP), you may ask, "Why would i want QuickRemote on my AOSP rom if MM has native IR support and Peel or Anymote works without all this mambo jambo?
Well, even though what i just said is true, no remote controller app has the learning method enabled, even on a stock rom, only QuickRemote can enable the IR receiver to learn a controller that does not appear on the device/manufacturers list.
So, that's the reason we want QuickRemote to work on our AOSP rom.
So, before anything, i would like to thank @hikarisei23 because in a comment of his post HERE i found the files for QuickRemote to work on MM wich leads to the second person i want to thank wich is @syndre who on said comment, posted the files that worked on MM, also @KronicSkillz who helped a lot to troubleshoot and also confirmed that the method i'm posting here works.
Well, this is it, after personally testing with: Resurrection Remix, AICP and Bliss, all of them MM amd CM13 based, all of them with the stock kernel and Lambda Kernel i'm confident enough to post it here, days of testing and troubleshooting and 3 different roms later.
So first, the mandatory disclaimer, im not responsible for any problem that may result from using my method and the files i'm providing you, either with your phone or your self-esteem, it's your responsibility to read, re-read and only do what you are comfortable with.
What you will need:
1. - The phone, this only has been tested with Lg G2 and Lg G3, this may or may not work on another LG phone with IR, you can try, but at your own risk.
2. - The Rom, this only have been tested with AOSP roms either CM13 or CM13 based roms, again, you can try in another rom but at your own risk.
3. - Obviously a Custom Recovery (twrp, cwm, philz)
4. - The three zips im leaving at the end of the post, QRemote_AOSP_MM.zip Fix_Part1.zip and Fix_Part2.zip.
5. - Maybe necessary or not, depending on your rom, Universal init.d from Playstore HERE and Selinux Mode Changer from HERE.
6. - Root Access.
Ok, once you checked and have everything needed, we have to make a little prep on your Rom before starting to flash the zips.
Rom Preparation 100% Needed
You need to set Selinux to permissive, here is where you may or may not need Selinux Mode Changer, First go into "About Device" on your phone settings and in the bottom you will find an indicator for Selinux state, if its "Permissive" you are good to go, some Roms and Kernels have this set to Permissive by default, if it's Enforcing, search in your Rom or Kernel settings, some of them have an option to set it to Permissive, if your rom does not have any option to change it, you will need Selinux Mode Changer, you install it and set Selinux to permissive, after reboot you can check in About Device again to see if it succeded, if it does not work, try again and check the original post, most of the answers are there, i cant give support for this app, also, this app needs root rights, and preferably two reboots after setting Selinux to Permissive.
Next you need to have init.d support, again, some roms have it, but at least for the test that me and the other users did, even though you are pretty sure init.d is enabled it's better to just install Universal init.d from the Play Store and enable init.d manually after doing so, reboot the system at least two times and grant Root access.
Installation!
Now we are ready to start flashing, reboot into recovery and RECOMMENDED, do a Nandroid Backup just in case, but at the moment no boot loops or any other problems had raised from flashing this, but again, just in case. After that, flash the first file: QRemote_AOSP_MM.zip, reboot your system and let it settle for a bit, 1 minute at least.
Now is the part where almost everyone has problems, you have to check in your Sdcard root for a log file named Qremote.log, if the file is there, it means init.d is enabled and in the file it will say if Selinux is Ok, if you don't have the file, check back the first two prep steps and try again.
Now if everything is going ok, is time for the second file, Fix_Part1.zip, reboot and let the system settle again, you may have some force close errors from QuickRemote or QuicksetSDK, its ok, you can try and check if QuickRemote is working, in allmost every case it will not work just yet, but you may have some luck.
Now, is the time to flash the third file, Fix_Part2.zip, again, reboot and let the system settle, now, you should have a working QuickRemote app on you AOSP MM Rom.
This are the steps, if you need more information about what all of this is doing and why you need Selinux and init.d, also why you need to flash 3 files, you can read the troubleshooting section where i explain what i understand about it.
TROUBLESHOOTING
Well, if you are here, it means that this didn't work as planned, so lets make this like a FAQ so you just search your problem and get the answer for it.
P.- I can't see QuickRemote on my app drawer. A: be sure that QuickRemote.apk is not showing as "com.lge...." and has the default green Android icon on your app drawer, sometimes and for reasons unknown to me, this happens for the first day or so, it will automatically change to QuickRemote and it will have the correct icon at least 5 hours after you installed it, it can take more time. A2: Maybe the flashing proccess was not successful, re-flash the file, it will automatically delete previously flashed files and install a new copy of them.
P. - I get force close messages for QuickRemote or QuicksetSDK after completing the proccess. A: try to run QuickRemote after the system settled, most of the times is 1 minute, in some roms and for reasons unknown to me, this messages will appear at boot but after the system settled, you will be able to run QuickRemote without any problem.
P. - QuickRemote opens up but no manufacturers are showing and it also gets really slow. A: this problem shows when either QuicksetSDK is not correctly installed or Selinux is not set to permissive, the solution for the first problem is in my 2 part fix, the version of Selinux included in the first zip, works great with MM but for some reason it will not work out of the box, i dont know if it's missing some files but it may or may not even show under system apps list on your settings menu, what my 2 part fix does is that, deletes the version of QuicksetSDK that the first flash installs and installs a temporary copy of QuicksetSDK wich i believe, writes information needed for QuicksetSDK to work properly, but this newer temporary QuicksetSDK apk, will allmost never work on MM, you can try but allmost every time it will not work, it will constantly force close, so the second fix zip, will delete this temporary QuicksetSDK and the folder it creates in your Sdcard root and install the previous version of QuicksetSDK again, and now, if everything went well, it will work as it's supposed to, i really dont know why exactly, but it works.
A2: the first thing you will notice when you switch to MM is that allmost every app will ask for permission to your Sdcard or camera or microphone wich in LP was not doing, since 4.3 Google is taking extra steps to ensure that you and your information are better protected one of this steps is Selinux (Security Enhanced Linux) wich, for putting it in simple terms, is like a sandbox for your system, only some trust-signed apps can get out of that sandbox and copy files etc... Into your system, those not-so privileged apps cant output anything outside the sanbox and thats why you need to disable or "set to permissive" Selinux, so QuicksetSDK can make the changes necessary for QuickRemote to do its work, it's true that now your system is in a degree "more vulnerable" but if you are a user of this forum, the odds to install something that will damage your system or jeopardize your information are minimal, you need to be really silly to fall for those "your system has problems" or "your battery is gonna explode if you don't install this app" ads that appear on your phone on the daily basis, so, dont worry, but at the same time, just be carefull and have some common sense, if there is a way for this to work with Selinux set to Enforcing, i will update it in the same second.
P. - QuickRemote force closes whenever i try to open it. A: this is caused by either a bad zip flash, or problems with Selinux or init.d, follow the previous answer and the first installation steps again.
P. - I can see QuickRemote and QuicksetSDK on my apps list, no force closes but still no manufacturers. A: Be sure init.d is enabled, i had problems with Roms that had "native init.d support" and emulated init.d will not work, the only way i got no problems with this was with Universal init.d, install that even though you are "pretty sure" your rom supports init.d, the 10QuickRemote.sh script on your init.d tries to get your country to see if you will use the app in, either Korean or any other supported language, it will also give some permissions to a file and it will check if Selinux is Permissive and finally, it will log this to a file called Qremote.log on the root of your Sd, if you have problems and you cant see the file, the problem is 99% most of the time, init.d.
P.- I don't want to flash three files, isn't there a simpler way? A: Unfortunately no, at this moment and after A LOT of testing etc... This is the only effective way i found.
P. - I'm afraid to set Selinux to permissive and leave the door open for all kind of bad ju ju and stuff to invade my sacred Android system, what can i do? A: Skip this hole thing, at the moment, the only way to make this work on AOSP MM is by doing the previous, just be careful, get some common sense and everything will be just fine.
Well, thats all i can think of right now, if you have suggestions, problems or a better way to make this work, please tell me in the comments or PM me, i'm glad to help as far as i can, i hope this helps, i leave you with the needed files and proof that it works.
QRemote_AOSP_MM.zip - MEGA - DRIVE
Great job
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).
Petrit Ziu said:
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).
Click to expand...
Click to collapse
I have not seen those force closes, i have to check, and as i said, the icon and name will eventually get right, for me was 5 hours, but it can be a hole day, and all by itself will set the icon and name correctly, if you have more problems, send me a logcat for this app, maybe we can find why it force closes
Logcat
Logcat
Added to index
[INDEX][LG G2] ROMs, Kernels, Guides and more
@Petrit Ziu after seeing the logcat i think the problem is StrictMode Policy, wich is a policy in android to keep unintentional writes to the system away from the main thread, so the animations, ui etc... Can keep a steady flow and your system runs smooth, because this app was never intended for AOSP and the app comes from Lollipop, i think that the right signatures are missing and Android sees the action of changing the name to a controller "invalid" so it closes the QuickRemote App, lets wait for newer versions of QuickRemote after Lg releases MM to more IR enabled devices to see what app works best, this is the best we can do with the resources we have
@Art Vanderlay Thanks
@Jc_master I think it's already perfect, just pointed an issue i found, but it's totally not a problem for me. Thanks
Sent from my LG-VS980 using XDA Free mobile app
@Petrit Ziu thanks, and dont worry, i'm no developer but i'm learning so much from this, it's good for me to see this problems and know why they happen, it's good to have feedback and even better this errors, if you didn't tell me, i would not know, my system does the same and i had no idea, i will update the post with this information
not work for me
I flashed it a lot of time and patched it and it will be not even work for me :/
I always get FC
D802 CM13 Nightlies
Potter92 said:
I flashed it a lot of time and patched it and it will be not even work for me :/
I always get FC
D802 CM13 Nightlies
Click to expand...
Click to collapse
Well, the only thing i can reccomend is that you use the latest TWRP for your device, you have to follow the steps exactly as i explained and use exactly the apps and files i explain, if that does not work i can just reccomend using another rom, Resurrection Remix for example, your logcat seems to show a problem with the apk itself, you cam try and decompress the files and manually copy and assign permissions to the files but i can't show you how, i lack time to do it
Works great, thank you!
Only issue I've had is the app crashes every time I try to rename a remote.
It works on the D801 (T-Mobile) Bliss rom 6.0.1
just confirming it.
Although I do get some force quit when editing the remotes name etc...
LG D802 CM13 nightlies - works!
Jc_master said:
@Petrit Ziu after seeing the logcat i think the problem is StrictMode Policy, wich is a policy in android to keep unintentional writes to the system away from the main thread, so the animations, ui etc... Can keep a steady flow and your system runs smooth, because this app was never intended for AOSP and the app comes from Lollipop, i think that the right signatures are missing and Android sees the action of changing the name to a controller "invalid" so it closes the QuickRemote App, lets wait for newer versions of QuickRemote after Lg releases MM to more IR enabled devices to see what app works best, this is the best we can do with the resources we have
Click to expand...
Click to collapse
Is there a fix?
MM is out for G3
Thanks
U can change name using SQLite Editor like this:
https://play.google.com/store/apps/details?id=dk.andsen.asqlitemanager
Database: /data/data/com.lge.qremote/databases/qremotesettings.db
Table: tblDevices
Petrit Ziu said:
Works great on Ressurection Remix 5.6.2. Well done.
Only issues I have are the force close when trying to edit the remote name, and icon and name of the app not showing correctly (which can be fixed with any custon launcher).
Click to expand...
Click to collapse
I can confirm this force close on rename issue as well
Eselter said:
U can change name using SQLite Editor like this:
https://play.google.com/store/apps/details?id=dk.andsen.asqlitemanager
Database: /data/data/com.lge.qremote/databases/qremotesettings.db
Table: tblDevices
Click to expand...
Click to collapse
That did it! Not necessarily a solution to the problem but a sufficient workaround for now
On CM13 working great but on exodus I can't manage it to work.
Any one have try it on exodus rom?
Eselter said:
On CM13 working great but on exodus I can't manage it to work.
Any one have try it on exodus rom?
Click to expand...
Click to collapse
Same here. Works on every rom I've tried but exodus. Something funky is happening with the quickset SDK as its present in priv-app or app (forget which one) but doesn't show up in installed apps. I have selinux set to permissive and init.d enabled.
Hello, how to uninstall this qremote? Because I have tried peel smart remote, and it's works great. And the remote (peel) so detail from LG qremote.
I am part of the team for Ainur Sauron, and I am here to present improved audio on the Le Max 2. Sauron has a userconfig which can be adjusted. Download the latest from there and place the attached file at /sdcard before installing. Make sure to remove the '.txt' at the end of the file too! Enjoy :victory:
Impedance is currently set to 16Ω which can be changed to whatever you desire. To set edit the attached sauron_useroptions file and change qc.impedance to whatever your headphones impedance is in Ohms multiplied by 1000 (eg. for 22Ω it would be 22000).
Tested by @I_Raptor_I on his x2, if it doesn't work just send me a log
EDIT: Attached the file
I did not know that anyone else was using Ainur Sauron on LeX2 It really improves the audio quality significantly on Oreo!
Quick question - why does it say "Axon 7" during installation procedure?
LazerL0rd said:
I am part of the team for Ainur Sauron, and I am here to present improved audio on the Le Max 2. Sauron has a userconfig which can be adjusted. Download the latest from there and place the attached file at /sdcard before installing. Make sure to remove the '.txt' at the end of the file too! Enjoy :victory:
Impedance is currently set to 16Ω which can be changed to whatever you desire. To set edit the attached sauron_useroptions file and change qc.impedance to whatever your headphones impedance is in Ohms multiplied by 1000 (eg. for 22Ω it would be 22000).
Tested by @I_Raptor_I on his x2, if it doesn't work just send me a log
EDIT: Attached the file
Click to expand...
Click to collapse
Hi, I download and flash the version MK II but can't see any app for setting my personal audio. How it works?
GaetanoS.89 said:
Hi, I download and flash the version MK II but can't see any app for setting my personal audio. How it works?
Click to expand...
Click to collapse
Hello GaetanoS.89, first things first uninstall the MK II Magisk module. Now place the given text file in /sdcard folder, then go and flash that module again, it should state that it has detected the user options text file and that's it.
I_Raptor_I said:
Hello GaetanoS.89, first things first uninstall the MK II Magisk module. Now place the given text file in /sdcard folder, then go and flash that module again, it should state that it has detected the user options text file and that's it.
Click to expand...
Click to collapse
I have not installed magisk n the smartphone.
Can you tell me how I can uninstall it?
Do I need magisk to let work this audio mod?
Thanks
GaetanoS.89 said:
I have not installed magisk n the smartphone.
Can you tell me how I can uninstall it?
Do I need magisk to let work this audio mod?
Thanks
Click to expand...
Click to collapse
Magisk isn't needed as it'll install with any configuration. All you need to do is placed the attched file at /sdcard (called Internal Storage) and rename it to sauron_useroptions (remove the .txt. at the end).
LazerL0rd said:
Magisk isn't needed as it'll install with any configuration. All you need to do is placed the attched file at /sdcard (called Internal Storage) and rename it to sauron_useroptions (remove the .txt. at the end).
Click to expand...
Click to collapse
Did it, and after What I have to do?
@Lazerlord: I tried your mod today by described method.
I copied "sauron_useroptions" into sdcard folder by TWRP file explorer.
Afterwards I flashed latest zip (17.03.) using TWRP. Everything was fine with it during this.
Wiped chache and dalvik and rebooted without any problems.
Result: No ringtone anymore, no message sound, but media sound works fine and was adjustable, no app or menue occoured in regard to your mod. I did not check more.
I could succesfully remove your mod by described method (flash again same file from TWRP)
After removal everything was fine as before :good:
My Phone: X829 with latest AEX 8.1 using Magisk 16.0
123Bart said:
@Lazerlord: I tried your mod today by described method.
I copied "sauron_useroptions" into sdcard folder by TWRP file explorer.
Afterwards I flashed latest zip (17.03.) using TWRP. Everything was fine with it during this.
Wiped cache and dalvik and rebooted without any problems.
Result: No ringtone anymore, no message sound, but media sound works fine and was adjustable, no app or menue occoured in regard to your mod. I did not check more.
I could succesfully remove your mod by described method (flash again same file from TWRP)
After removal everything was fine as before :good:
My Phone: X829 with latest AEX 8.1 using Magisk 16.0
Click to expand...
Click to collapse
Ah, well could you follow these instructions on the main thread which say "help to extend features". It'll help us fix those issues. :good:
How was the media sound though? Did it sound better according to you?
LazerL0rd said:
Ah, well could you follow these instructions on the main thread which say "help to extend features". It'll help us fix those issues. :good:
How was the media sound though? Did it sound better according to you?
Click to expand...
Click to collapse
I removed the "sauron_useroptions" from sdcard folder (as it was described in the file itself, that UO is not mandatory) and reflashed the zip-file again.
With this way everything works !
Will read a little bit the instructions now...
Generaly I have to say I am using Leeco CDLA as headphones atm which are extraordinary by themselves.
So maybe I will use adapter for 3,5mm jack whithin next days and try some user options. Leeco Loadspeaker judgement is difficult imho.
Also new AEX is very good ROM in regard to speaker sound I have to say.
On Oreo 8.1.0. PixelRevenge 15.1 works very well in music playback. He gave me a strange problem. I removed the system camera that I can not install anymore. I had to put another one. I have not tried calls and notifications yet
edit:- Notifications and ringtones ok. In-call audio worsened, the voice is less clear. In speakerphone there is a loud hiss that makes the speakerphone unusable
RISS23 said:
On Oreo 8.1.0. PixelRevenge 15.1 works very well in music playback. He gave me a strange problem. I removed the system camera that I cannot install anymore. I had to put another one. I have not tried calls and notifications yet
edit:- Notifications and ringtones ok. In-call audio worsened, the voice is less clear. In speakerphone, there is a loud hiss that makes the speakerphone unusable
Click to expand...
Click to collapse
We're working on a fix for the mixer_paths that'll correct notifications, ringtones, and other audio. I'm happy that you're enjoying music playback. However, the system camera app problem is nothing to do with Sauron it's probably a ROM issue, or possibly even a Magisk issue.
I've installed this Mod by using Magisk 16.0 (v5.6.4) on RR 6.0(22-03-18).
Before I did this I placed the file sauron_useroptions to /sdcard folder.
During the installation Magisk showed that the useroption file was found and used for the installation.
In Poweramp I get the message that there is a problem with app native libraries (libampffmpeg.so).
I don't know whether the error message has something to do with that, but the volume control in Poweramp after flashing this modul is faulty.
Just when the volume is set the half I can hear anything. The volume control steps seems to be broken, but just in Poweramp.(After uninstalling, the issue is gone, but the error message is still sthere)
In other Apps the volume control is normal.
Since I use RR 6.0(8.1) instead of RR 5.8.5(7.1.2) the speaker sounds cheap tinny - Ainur Sauron didn't help to solve this issue. I removed AudioFX, can this be the reason?
It's difficult to describe the issue "cheap tinny", but I think the audio drivers have problems to divorce the difference frequences.
On RR 5.85. the speaker was more "smooth" and the frequences were divorced much better.
Sorry for my bad english and the critic. I think I'm an individual case and other people don't have the problems which I have, but in my case, the Mod seems not to improve the audio quality.
Azubi96 said:
I've installed this Mod by using Magisk 16.0 (v5.6.4) on RR 6.0(22-03-18).
Before I did this I placed the file sauron_useroptions to /sdcard folder.
During the installation Magisk showed that the useroption file was found and used for the installation.
In Poweramp I get the message that there is a problem with app native libraries (libampffmpeg.so).
I don't know whether the error message has something to do with that, but the volume control in Poweramp after flashing this modul is faulty.
Just when the volume is set the half I can hear anything. The volume control steps seems to be broken, but just in Poweramp.(After uninstalling, the issue is gone, but the error message is still sthere)
In other Apps the volume control is normal.
Since I use RR 6.0(8.1) instead of RR 5.8.5(7.1.2) the speaker sounds cheap tinny - Ainur Sauron didn't help to solve this issue. I removed AudioFX, can this be the reason?
It's difficult to describe the issue "cheap tinny", but I think the audio drivers have problems to divorce the difference frequences.
On RR 5.85. the speaker was more "smooth" and the frequences were divorced much better.
Sorry for my bad english and the critic. I think I'm an individual case and other people don't have the problems which I have, but in my case, the Mod seems not to improve the audio quality.
Click to expand...
Click to collapse
I've heard from @I_Raptor_I that RR already has a loss in audio quality. I advise the use of another ROM and if the tinnyness persists use the attached Sauron zip.
The Poweramp problem is probably due to DVC (Direct Volume Control) in their FAQ they state it may cause issues with 24-bit or HQ audio. The native libraries issue is not related to Ainur as it doesn't touch that file.
About the audio. ROM (which Sauron edits) isn't the only thing that contributes. the HAL and kernel do too, so RR's bad audio may not be able to be fixed or corrected by Ainur but we'll take a look into it.
Ok guys, @LazerL0rd is kindly developing a very nice Oreo kernel for our Le Max 2 improving the speeds dramatically and most importantly audio, he has already optimized our Qualcomm DSP, expect a very nice audio experience on Oreo from now on so stay tuned and make sure to thank LazerL0rd for his hard work, he doesn't even have a Le Max 2 and yet he is spending hours making this kernel for us
Magisk viper?
I have installed viper on RR Oreo via magisk and audio quality is now on point with how it worked through flashing viper and Dolby Atmos on the nugart RR via twrp. There are a couple of things to consider though, viper must be activated before listening to music through your app, viper does not work over Bluetooth by default in viper meaning you must go to viper settings and set mode to compatibility from normal and then viper will work over Bluetooth. The last thing, and I can't remember if this was true on nugart but viper seams to only work with music that you have downloaded to your device and will not work with streaming music from the web.
mikedavo said:
I have installed viper on RR Oreo via magisk and audio quality is now on point with how it worked through flashing viper and Dolby Atmos on the nugart RR via twrp. There are a couple of things to consider though, viper must be activated before listening to music through your app, viper does not work over Bluetooth by default in viper meaning you must go to viper settings and set mode to compatibility from normal and then viper will work over Bluetooth. The last thing, and I can't remember if this was true on nugart but viper seams to only work with music that you have downloaded to your device and will not work with streaming music from the web.
Click to expand...
Click to collapse
To fix streamed music install universal deep buffer remover magisk module by @Zackptg5 , it's on the repo too.
I_Raptor_I said:
Ok guys, @LazerL0rd is kindly developing a very nice Oreo kernel for our Le Max 2 improving the speeds dramatically and most importantly audio, he has already optimized our Qualcomm DSP, expect a very nice audio experience on Oreo from now on so stay tuned and make sure to thank LazerL0rd for his hard work, he doesn't even have a Le Max 2 and yet he is spending hours making this kernel for us
Click to expand...
Click to collapse
Kernel released and in Havoc OS. Source is https://github.com/Havoc-Devices/android_kernel_leeco_msm8996. I'll update personal repo and both to 3.18.108 soon.
does it work on xiaomi mi 6 miui 9? Android 8.0
Wysłane z mojego MI 6 przy użyciu Tapatalka
LazerL0rd said:
Kernel released and in Havoc OS. Source is https://github.com/Havoc-Devices/android_kernel_leeco_msm8996. I'll update personal repo and both to 3.18.108 soon.
Click to expand...
Click to collapse
waitting for the update, thanks
Hi,
So whoever is using a custom ROM on Poco F1, has faced onething for sure after flashing Viper4Android or any other sound mod; and that is sound distortion when getting notifications.
I see a lot of people asking for a solution and until now we have all been telling them to either remove SoundFX folder from /Vendor/lib and /Vendor/lib64 or renaming the volumelistener.so in order for Viper to work properly.
While the above methods are correct, but it requires messing with the device manually and sometimes it becomes hard to revert back to the original state if necessary (read Bluetooth audio issue).
I have searched a lot for a solution which is more easy and can be resolved instantly if found any bug. And finally I have found a Magisk module which does exactly what we are seeking for.
The name of the Magisk module is NOTIFICATION HELPER REMOVER. It is available on Magisk repo or can be downloaded from here: https://zackptg5.com/android.php#nhr (credit goes to @Zackptg5).
Once downloaded, flash it on Magisk and when asked to choose in between volume up and down, press Volume Down and it will do the job for you. AML is not required. Once done, just reboot the device and send any message to your device and see. No more sound distortion!!
Basically, the module patches volume listener, but systemlessly. Which means you don't need to boot into twrp and mess with the Vendor partition. Anytime you wish to revert back to the original state, just uninstall the module and you are good to go.
I know the module has been there for quite sometime, but the reason of my post is to make people aware of it (since a lot of people actually don't know about it or overlook it).
Please note that I am not the developer of the module and if any credit is to be given, it should go to the developer himself.
If anyone still finds something wrong on this post, please let me know. I will rectify it immediately.
POCO F1 Fix Distorted Sounds Notifications issue on custom ROMs.
Rowdyy Ronnie said:
So whoever is using a custom ROM on Poco F1, has faced onething for sure after flashing Viper4Android or any other sound mod; and that is sound distortion when getting notifications.
................ rectify it immediately.
Click to expand...
Click to collapse
Good thread. :good: I confirmed on 26.12.18 that on POCO F1 this solution works. But people don't bother to read . :crying: and ask the same question everywhere.
Here was my post.. https://forum.xda-developers.com/showpost.php?p=78513504&postcount=195
SVR said:
Good thread. :good: I confirmed on 26.12.18 that on POCO F1 this solution works. But people don't bother to read . :crying: and ask the same question everywhere.
Here was my post.. https://forum.xda-developers.com/showpost.php?p=78513504&postcount=195
Click to expand...
Click to collapse
I feel the same way. Tired of telling the same thing on XDA and Telegram. Hope from now on, people just read this post and stop spamming XDA.
great job this works with dolby atmos too on android pie thanks
tinimc said:
great job this works with dolby atmos too on android pie thanks
Click to expand...
Click to collapse
Can you give me link for working one on Android Pie (Pixel Experience) in my case, or which module version in Magisk Manager. Thanks bro
https://www.google.com/amp/s/forum..../themes/dolby-atmos-android-9-0-t3874065/amp/ download dolby here and first you instal the fix from the thread install throught magisk v18
reboot
then install dolby atmos through magisk 18
and reboot
done its perfect for.me very loud sound
and on the headphones
and the fix works perfect i have no crackling sounds
im on pixel experience too eceything works perfect
and for a good suggestion use extreme kernel v8
its awsome battery life
tinimc said:
https://www.google.com/amp/s/forum..../themes/dolby-atmos-android-9-0-t3874065/amp/ download dolby here and first you instal the fix from the thread install throught magisk v18
reboot
then install dolby atmos through magisk 18
and reboot
done its perfect for.me very loud sound
and on the headphones
and the fix works perfect i have no crackling sounds
im on pixel experience too eceything works perfect
and for a good suggestion use extreme kernel v8
its awsome battery life
Click to expand...
Click to collapse
Thanks so much for all your tips. Cheers bro
Rowdyy Ronnie said:
Hi,
So whoever is using a custom ROM on Poco F1, has faced onething for sure after flashing Viper4Android or any other sound mod; and that is sound distortion when getting notifications.
I see a lot of people asking for a solution and until now we have all been telling them to either remove SoundFX folder from /Vendor/lib and /Vendor/lib64 or renaming the volumelistener.so in order for Viper to work properly.
While the above methods are correct, but it requires messing with the device manually and sometimes it becomes hard to revert back to the original state if necessary (read Bluetooth audio issue).
I have searched a lot for a solution which is more easy and can be resolved instantly if found any bug. And finally I have found a Magisk module which does exactly what we are seeking for.
The name of the Magisk module is called NOTIFICATION HELPER REMOVER. It is available on Magisk repo or can be downloaded from here: https://zackptg5.com/android.php#nhr (credit goes to @Zackptg5).
Once downloaded, flash it on Magisk and when prompted, press Volume Down and it will do job for you. Once done, just reboot the device and send any message to your device and see. No more sound distortion!!
Basically, the module patches volume listener, but systemlessly. Which means you don't need to boot into twrp and mess with the Vendor partition. Anytime you wish to revert back to the original state, just uninstall the module and you are good to go.
I know the module has been there for quite sometime, but the reason of my post is to make people aware of it (since a lot of people actually don't know about it or overlook it).
Please note that I am not the developer of the module and if any credit is to be given, it should go to the developer himself.
If anyone still finds something wrong on this post, please let me know. I will rectify it immediately.
Click to expand...
Click to collapse
Still experiencing crackLing sound and stutters on whatsapp voice notes.only. when its minimized or screen off
slimshouki said:
Still experiencing crackLing sound and stutters on whatsapp voice notes.only. when its minimized or screen off
Click to expand...
Click to collapse
I have the same exact issue
Tried two kernels and two vendors ( 9.1.3 and 9.1.10 ) and whenever whatsapp is minimzed or screen off I have cracking played sound
If dolby is disabled or uninstalled issue is gone
I started with notifc helper removal vol down then dolby 2711 version
I love dolby as it have louder and richier volume with simple config interface but whatspp voice notes are mandatory for me as well
I am on custom rom NOS with sphinclc kernel
Can anybody test and advise his results along with used ROM/Vendor/Kernel ?
Still crackling ringtone sounds on havoc rom
Possible solution
slimshouki said:
Still experiencing crackLing sound and stutters on whatsapp voice notes.only. when its minimized or screen off
Click to expand...
Click to collapse
I just have found something that works for me... Install Audio Modification Library and tthe crackling sound on whatsapp is gone ROM RevOs 9.5.1 MIUI 10 based!
Not working for me. I am on crdroid.
hownis the bluetoothnaudio does it work because with the vendor patches it stops working ?
vicmed94 said:
I just have found something that works for me... Install Audio Modification Library and tthe crackling sound on whatsapp is gone ROM RevOs 9.5.1 MIUI 10 based!
Click to expand...
Click to collapse
not working for me, I still have the problem with whatsapp . Im in the last version of xiaomi eu beta
When I try to flash notification helper, it is stuck. I have to restart the device.
So I went the route of deleting the soundfx files and now I can't use any type of sound modifiers like equalizers. How can I fix this?
I uninstalled viper and any other audio modules and still have sound distortion. help?
Rowdyy Ronnie said:
Hi,
So whoever is using a custom ROM on Poco F1, has faced onething for sure after flashing Viper4Android or any other sound mod; and that is sound distortion when getting notifications.
I see a lot of people asking for a solution and until now we have all been telling them to either remove SoundFX folder from /Vendor/lib and /Vendor/lib64 or renaming the volumelistener.so in order for Viper to work properly.
While the above methods are correct, but it requires messing with the device manually and sometimes it becomes hard to revert back to the original state if necessary (read Bluetooth audio issue).
I have searched a lot for a solution which is more easy and can be resolved instantly if found any bug. And finally I have found a Magisk module which does exactly what we are seeking for.
The name of the Magisk module is NOTIFICATION HELPER REMOVER. It is available on Magisk repo or can be downloaded from here: https://zackptg5.com/android.php#nhr (credit goes to @Zackptg5).
Once downloaded, flash it on Magisk and when asked to choose in between volume up and down, press Volume Down and it will do the job for you. AML is not required. Once done, just reboot the device and send any message to your device and see. No more sound distortion!!
Basically, the module patches volume listener, but systemlessly. Which means you don't need to boot into twrp and mess with the Vendor partition. Anytime you wish to revert back to the original state, just uninstall the module and you are good to go.
I know the module has been there for quite sometime, but the reason of my post is to make people aware of it (since a lot of people actually don't know about it or overlook it).
Please note that I am not the developer of the module and if any credit is to be given, it should go to the developer himself.
If anyone still finds something wrong on this post, please let me know. I will rectify it immediately.
Click to expand...
Click to collapse
HUGE THANKS! this method also works on redmi note 8 using GSI.
Help me
I used costum ROM and I heared noise in some games. Then I use the way you suggest, the noise on the games gone but the calls go on speaker when i answer them. Would you please guide me how to solve the problem?
thank you very much for your advice, cool! It works on Umidigi F1 with Evolution X 4.1 too.
Here are the steps to install viper with a Pixel 4 XL:
1. In magisk go to downloads, install the audio compatibility patch 1.7 3. Choose volume up for requested settings, although USB can be set as preferred.
2. Reboot
3. Install XDA Labs Viper. Do not open.
4. In magisk go to downloads, install the Audio Modification Library v2 4. Do not reboot.
5. Open Viper, let it install driver and it will reboot.
6. Go to app info for viper, disable battery optimization.
That’s it. Enjoy the audio bliss.
Thanks for this.
Questions;
- For step 1 in your OP (install the audio compatibility patch). Just want to make sure I'm using the correct patch. What version number? At the time of writing I see V1.7.3. Is that what you used?
Also, during installation of that patch, there are a number of vol up/down options that need to be chosen. What did you choose for;
- Do you want to skip audio_policy patching? (Original acp before became 3in1 module) Vol+ = yes, Vol- = no
- Would you like to skip notification_helper remover? Vol+ = yes, Vol- = no
- Would you like to skip usb policy patching for usb devs? Vol+ = yes, Vol- = no
- Use lib workaround? Only choose yes if you're having issues. Vol+ = yes, Vol- = no (recommended)
- For step 4 (install the Audio Modification Library). What is the version number? At the time of writing I see V2.4. Is that what you used?
pdfruth said:
Thanks for this.
Questions;
- For step 1 in your OP (install the audio compatibility patch). Just want to make sure I'm using the correct patch. What version number? At the time of writing I see V1.7.3. Is that what you used?
Also, during installation of that patch, there are a number of vol up/down options that need to be chosen. What did you choose for;
- Do you want to skip audio_policy patching? (Original acp before became 3in1 module) Vol+ = yes, Vol- = no
- Would you like to skip notification_helper remover? Vol+ = yes, Vol- = no
- Would you like to skip usb policy patching for usb devs? Vol+ = yes, Vol- = no
- Use lib workaround? Only choose yes if you're having issues. Vol+ = yes, Vol- = no (recommended)
- For step 4 (install the Audio Modification Library). What is the version number? At the time of writing I see V2.4. Is that what you used?
Click to expand...
Click to collapse
Thanks. Good questions.
It was 1.7.3 of the compatibility patch.
Volume up to all the options.
Version 2.4 is also correct.
I'll amend the guide to contain this information.
I didn't do the audio compatibility patch part. You reckon that could cause issues? If I were to reinstall, would uninstalling everything and starting from scratch be okay? So far viper does work.
Or you can grab V4A version 2.7, install it, do the drivers 3 or 4 times for it to actually take, profit. I have it working on my phone without any other steps.
likepeas said:
I didn't do the audio compatibility patch part. You reckon that could cause issues? If I were to reinstall, would uninstalling everything and starting from scratch be okay? So far viper does work.
Click to expand...
Click to collapse
As I understand it the audio compatibility patch enabled viper on USB output like for Android auto.
It also makes it so you don't have to reboot repeatedly to get the driver to stick (according to others).
Hello, I followed all the steps and I still getting "No audio driver found"
I got this
madscribblerz said:
Here are the steps to install viper with a Pixel 4 XL:
1. In magisk go to downloads, install the audio compatibility patch 1.7 3. Choose volume up for requested settings, although USB can be set as preferred.
2. Reboot
3. Install XDA Labs Viper. Do not open.
4. In magisk go to downloads, install the Audio Modification Library v2 4. Do not reboot.
5. Open Viper, let it install driver and it will reboot.
6. Go to app info for viper, disable battery optimization.
That’s it. Enjoy the audio bliss.
Click to expand...
Click to collapse
Hey OP, do you use Google maps navigation by any chance?
I have Viper working on my 4 XL as well, and with the installation of Audio Modification Library and Audio Compatibility Patch installed, I can get system wide equalization except for one thing, Google Map's voice direction audio.
I guess it's a minor problem but if I'm listening to music and Google is about to alert me the next turn, Viper stops processing and my music goes all flat while Google is speaking, and then for like a split second to a few seconds later after Google is finished speaking, Viper starts to kick in again.
I can't seem to figure it out for the life of me on how to get Viper to still process even when Google is speaking the next turn direction. Has anyone ran into this issue? Anyone managed to fix this?
Mine says "Enabled: No" and I can only sense any change on gain. When I use Bluetooth USB it still says "Speaker" in the notification box?
Last time I checked selinux must be on permissive for it to stick. Gonna try it out and I'll give you all my feedback.
Tested it out and need selinux permissive.
matssa said:
Tested it out and need selinux permissive.
Click to expand...
Click to collapse
Just curious, does your viper still process when using Google maps navigation while playing music? My viper cuts out whenever maps is about to speak the next turn direction, and right after it's done speaking, viper will kick back in either right away or a few seconds later. I did recall trying to switch to permissive but that didn't seem to work
bestgio said:
Just curious, does your viper still process when using Google maps navigation while playing music? My viper cuts out whenever maps is about to speak the next turn direction, and right after it's done speaking, viper will kick back in either right away or a few seconds later. I did recall trying to switch to permissive but that didn't seem to work
Click to expand...
Click to collapse
I don't use maps I only use Waze but without the audio so can't really tell. However I think I already had this issue, it's because it cant process some apps like when your on the phone with someone. If I use it I'll try to check
matssa said:
I don't use maps I only use Waze but without the audio so can't really tell. However I think I already had this issue, it's because it cant process some apps like when your on the phone with someone. If I use it I'll try to check
Click to expand...
Click to collapse
Did you follow the installation instructions from OP and then just switched selinux to permissive? I might just try redoing my installation just to see if that happens to be the magic trick
bestgio said:
Did you follow the installation instructions from OP and then just switched selinux to permissive? I might just try redoing my installation just to see if that happens to be the magic trick
Click to expand...
Click to collapse
Yup followed then switched selinux.
matssa said:
Tested it out and need selinux permissive.
Click to expand...
Click to collapse
Didn't do anything except install V4A version 2.7 and install the drivers until it took. Nothing else including selinux permissive. Works fine here.
matssa said:
Last time I checked selinux must be on permissive for it to stick. Gonna try it out and I'll give you all my feedback.
Click to expand...
Click to collapse
What do you mean by selinux needing to be on for it to stick? The processing? I ask because last night in my car the music didn't sound like it should. Opened V4A and flipped a toggle off then back on and all of a sudden the sound changed to what it should sound like. This happened at first on my Pixel 3xl, but later wasn't an issue at all. Not sure why.
gettinwicked said:
What do you mean by selinux needing to be on for it to stick? The processing? I ask because last night in my car the music didn't sound like it should. Opened V4A and flipped a toggle off then back on and all of a sudden the sound changed to what it should sound like. This happened at first on my Pixel 3xl, but later wasn't an issue at all. Not sure why.
Click to expand...
Click to collapse
It was for the installation of the driver in order to make it stick.
For the issue you're having, check the battery optimisation option and make sure it isn't on. I had this before and changing that fixed it.
matssa said:
Yup followed then switched selinux.
Click to expand...
Click to collapse
Tried doing this and unfortunately viper still didn't process maps navigation audio :/ Thanks for sharing though!
My viper installation was able to stick without the need of changing anything related to selinux, just audio compatibility patch and audio modification library did the trick for me (minus maps navigation ofc)
INTRODUCTION
*WARNING USE AT YOUR OWN RISKS*
Though the poco F1 has stereo speakers, the earpiece is sort of weak in comparison to bottom one and so the sound quality falls short when compared to other phones with dual speakers. With this guide, you can make your phone sound much balanced, immersive and better. Basically what it does is increase audio coming out from earpiece by using viper in combination with Dolby. Also this does not increases sound from earpiece beyond max level but instead reduces volume of bottom speaker slightly so it will not damage your speaker
REQUIREMENTS
Any custom rom with magisk and permissive SElinux
STEPS
1. Flash permissiver zip or use SElinux switcher to make SElinux permissive for Dolby module to work
2. Flash viper4a rootless zip in TWRP
3. Flash v4afx zip in magisk then reboot and test if Viper4A is successfully installed and working
4. Flash ACDB zip first in magisk then flash dolby audio zip and then reboot. You should now have moto audio app installed and working.
5. Put XHR WideFX irs file to main storage/Android/data/com.pittvandewitt.viperfx/files/Kernel
6. In Viper, enable convolver then choose the file to enable it.
7. For dolby, the default settings (smart audio) is great but personally I use film mode with surround sound and volume leveller enabled.
I have tested this in evolution X rom and it should work in other roms also. For stock rom it may require a custom kernel. If Dolby Atmos doesn't work then try Dolby Digital instead.
If you face issues like Dolby getting disabled automatically then heading to viper settings and switching Attach Audio Effects toggle or rebooting the system fixes it. If dolby app force closes then reflash it and clear catch after installation
DOWNLOAD
https://drive.google.com/folderview?id=1ublWcvZQ8QrQ0-uvMDlFTTEssLpcsoBC
its really sad there's no link :crying: hmmmm
new user not allowed to attach file / url original thread to their post ?
DOYANMAIN said:
its really sad there's no link :crying: hmmmm
new user not allowed to attach file / url original thread to their post ?
Click to expand...
Click to collapse
I updated the post with download link. XDA have a rule to not allow very new users from posting links or attachments. But by doing a few posts it allowed me to do so.
Geetesh Sonwani said:
STEPS
1. Install Audio Compability Patch first in magisk then reboot
Click to expand...
Click to collapse
Do you want to skip audio_policy patching? (Original acp before became 3in1 module)
Vol+ = yes, Vol- = no
Would you like to skip notification_helper remover?
Vol+ = yes, Vol- = no
Would you like to skip usb policy patching for usb dacs?
Vol+ = yes, Vol- = no
Should i skip this ? Or No ? Is this really matter ? because i really dont know what their usage for, so i just skip it
and also
on STEP 2, when i installing viper4a rootless in twrp it say done but i got red warning it say "unable to mount system"
so it is successfull or nah ? i confuse
i already installed v4afx via magisk ( STEP 3 ) and it working.
BUT
DOYANMAIN said:
on STEP 2, when i installing viper4a rootless in twrp it say done but i got red warning it say "unable to mount system"
Click to expand...
Click to collapse
It this thing ? should i ignore it since my viper4a working ?
DOYANMAIN said:
Do you want to skip audio_policy patching? (Original acp before became 3in1 module)
Vol+ = yes, Vol- = no
Would you like to skip notification_helper remover?
Vol+ = yes, Vol- = no
Would you like to skip usb policy patching for usb dacs?
Vol+ = yes, Vol- = no
Should i skip this ? Or No ? Is this really matter ? because i really dont know what their usage for, so i just skip it
and also
on STEP 2, when i installing viper4a rootless in twrp it say done but i got red warning it say "unable to mount system"
so it is successfull or nah ? i confuse
i already installed v4afx via magisk ( STEP 3 ) and it working.
BUT
It this thing ? should i ignore it since my viper4a working ?
Click to expand...
Click to collapse
On first choose no then select patch (new logic) then again choose no for notification helper and select remove volume listener library
Even if you skipped it wouldn't matter much because ACP is used just to fix audio not working in some apps and it does slightly enhances audio quality and volume.
For usb dac you can choose yes if you don't use wired headphones from usb c port
For viper though, you shouldn't get that warning
Maybe problem could be in your twrp
Manually mount system in twrp then try flashing again. If it didn't work you may have to reflash recovery
But you said that it is working? Did you tested the audio also? Because the magisk module only installs the app and some configs. The drivers are installed from recovery. You can also tap on the chip like icon button in viper and it should show the driver info and enabled as yes properly
Geetesh Sonwani said:
On first choose no then select patch (new logic) then again choose no for notification helper and select remove volume listener library
Even if you skipped it wouldn't matter much because ACP is used just to fix audio not working in some apps and it does slightly enhances audio quality and volume.
For usb dac you can choose yes if you don't use wired headphones from usb c port
For viper though, you shouldn't get that warning
Maybe problem could be in your twrp
Manually mount system in twrp then try flashing again. If it didn't work you may have to reflash recovery
But you said that it is working? Did you tested the audio also? Because the magisk module only installs the app and some configs. The drivers are installed from recovery. You can also tap on the chip like icon button in viper and it should show the driver info and enabled as yes properly
Click to expand...
Click to collapse
Yes even tho i got warning, but it properly working. I already use it like 6hour, all is working fine.
but when i installing Dolby Atmos, i got bootloop and force me to bootloader. but when restarting phone i can access twrp, just removing them in module via twrp everything is back normal.
but i think it doesnt support latest MIUI Global 11.0.4 ? i got stock MIUI11
Anyway, after wiping module via twrp my viper now doesnt have driver on the app. i already doing the exactly same step 1 - 3 to install viper and it didnt work rightnow. driver still doesnt work even tho i tried installing this many times.
I already go to viper4x thread, someone say need to overwrite 2 file ( post-fs-data.sh & sepolicy.rule ) but still doesnt fix driver.
maybe you know how to ? :laugh:
DOYANMAIN said:
Yes even tho i got warning, but it properly working. I already use it like 6hour, all is working fine.
but when i installing Dolby Atmos, i got bootloop and force me to bootloader. but when restarting phone i can access twrp, just removing them in module via twrp everything is back normal.
but i think it doesnt support latest MIUI Global 11.0.4 ? i got stock MIUI11
Anyway, after wiping module via twrp my viper now doesnt have driver on the app. i already doing the exactly same step 1 - 3 to install viper and it didnt work rightnow. driver still doesnt work even tho i tried installing this many times.
I already go to viper4x thread, someone say need to overwrite 2 file ( post-fs-data.sh & sepolicy.rule ) but still doesnt fix driver.
maybe you know how to ? :laugh:
Click to expand...
Click to collapse
Dolby Atmos is known to not work as of now in stock kernel or roms for many devices as it is still under development. You can try dolby digital instead
But are you getting the same error on twrp for viper? With system not mounting?
Unfortunately I don't have much idea for viper so I can help you till the limits of my knowledge only
Anybody make it work with Pixel Experience ROM 10.0'
Hi, I want to install it and I have Pixel Experience ROM 10.0 Official. I'm curious if anybody successfully instaled it on this ROM.
Thanks
Geetesh Sonwani said:
INTRODUCTION
Though the poco F1 has stereo speakers, the earpiece is kinda weak in comparison to bottom one and so it doesn't give that true stereo like audio performance (surround sound) compared to other phones with dual speakers. But with this guide, you can make your phone sound much balanced, immersive and better with Dolby Atmos and Viper. It actually feels like if the sound is coming towards you and not from the side
This requires the XHR WideFX irs. This is the only one I found till now which worked so perfectly with atmos after testing 500+ irs files.
REQUIREMENTS
Any android 9+ rom with magisk and permissive SElinux
STEPS
1. Install Audio Compability Patch first in magisk then reboot
2. Flash viper4a rootless zip in TWRP
3. Flash v4afx zip in magisk then again reboot and confirm if Viper4A is successfully installed and working
4. Flash Dolby Atmos zip file in magisk (you can download it from guitardedhero's post also for new version) and reboot. You should have both Dolby Atmos and Viper4A working at this point
5. Now to get that stereo sound effect, put XHR WideFX irs file in main storage/Viper4Android/Kernel folder
6. Open Viper and enable convolver then choose the same.
You can now test the sound and enjoy the stereo sound effect. It is best for gaming or while watching movies.
I have tested this in evolution X 4.0 rom and it should work in other roms also but I am not sure for OOS. For stock rom it may require a custom kernel. If it works in your rom then please comment down below so that others could also know it.
If you face issues regarding Dolby getting disabled automatically then heading to viper settings and switching Attach Audio Effects toggle or rebooting the system fixes it.
DOWNLOAD
https://drive.google.com/folderview?id=1E1ALAVIp82Cx36Dua1zCf8c5sWvt4z9m
Click to expand...
Click to collapse
puiocku said:
Hi, I want to install it and I have Pixel Experience ROM 10.0 Official. I'm curious if anybody successfully instaled it on this ROM.
Thanks
Click to expand...
Click to collapse
I have personally tested it in PE pie and Evo X 10 version. But this one should work in any android 10 based custom rom as long as you don't have any other audio mods installed conflicting it or else you may require AML also.
Geetesh Sonwani said:
I have personally tested it in PE pie and Evo X 10 version. But this one should work in any android 10 based custom rom as long as you don't have any other audio mods installed conflicting it or else you may require AML also.
Click to expand...
Click to collapse
Thank you, in that case I think too that should work fine with Pixel Experience 10.0 ROM.
Cheers
DOYANMAIN said:
Yes even tho i got warning, but it properly working. I already use it like 6hour, all is working fine.
but when i installing Dolby Atmos, i got bootloop and force me to bootloader. but when restarting phone i can access twrp, just removing them in module via twrp everything is back normal.
but i think it doesnt support latest MIUI Global 11.0.4 ? i got stock MIUI11
Anyway, after wiping module via twrp my viper now doesnt have driver on the app. i already doing the exactly same step 1 - 3 to install viper and it didnt work rightnow. driver still doesnt work even tho i tried installing this many times.
I already go to viper4x thread, someone say need to overwrite 2 file ( post-fs-data.sh & sepolicy.rule ) but still doesnt fix driver.
maybe you know how to ? :laugh:
Click to expand...
Click to collapse
+1.
Viper is working fine but after installing Dolby Atmos and rebooting i am stuck at Fastboot, had to remove the dolby module.
Is this related to Miui 11 or some selinux problem??
Please suggest some workaround.
Will this work on miui 11?
Ravindrasan said:
+1.
Viper is working fine but after installing Dolby Atmos and rebooting i am stuck at Fastboot, had to remove the dolby module.
Is this related to Miui 11 or some selinux problem??
Please suggest some workaround.
Click to expand...
Click to collapse
Looks like it doesn't work in miui as of now
But you can try dolby digital instead which is also good. Dolby Atmos is still like an early release and currently only works in custom roms and kernels
But remember to choose the IRS file in viper. That makes the earpiece work more balanced. Dolby is just to further enhance the sound quality.
Geetesh Sonwani said:
Looks like it doesn't work in miui as of now
But you can try dolby digital instead which is also good. Dolby Atmos is still like an early release and currently only works in custom roms and kernels
But remember to choose the IRS file in viper. That makes the earpiece work more balanced. Dolby is just to further enhance the sound quality.
Click to expand...
Click to collapse
Same is happening in Evolution X I'm stuck at bootloader..
It's not even working in a custom rom.
Works perfectly with Pixel Experience (Android9) + No Gravity Karnel.
Thank you, so wonderful!
Thanks for stereo convolver file, but dolby atmos giving bootloop on miui 11.0.6 android 10
I'm running Pixel Experience Plus Android 10 on my poco. I've managed to get V4A to work but when I flash Dolby Atmos and reboot the device and try to open it nothing happens and after some time and after 10-15 attempts of trying to open it a crash message appears. I also tried installing Dolby Digital Plus for Android Q but that crashes as well
naziraaqib3k said:
I'm running Pixel Experience Plus Android 10 on my poco. I've managed to get V4A to work but when I flash Dolby Atmos and reboot the device and try to open it nothing happens and after some time and after 10-15 attempts of trying to open it a crash message appears. I also tried installing Dolby Digital Plus for Android Q but that crashes as well
Click to expand...
Click to collapse
Make sure that SELinux is permissive as they will not work in enforcing
Flash permissiver zip file to fix it
I am also currently on PE+ latest and have not encountered any such issues
My recommendation is use Dolby digital instead as it is more stable (v7.2)
Geetesh Sonwani said:
Make sure that SELinux is permissive as they will not work in enforcing
Flash permissiver zip file to fix it
I am also currently on PE+ latest and have not encountered any such issues
My recommendation is use Dolby digital instead as it is more stable (v7.2)
Click to expand...
Click to collapse
I've used this setup on miui 11 eu version and it ran just fine also I had already set SELinux to Permissive uaing the SELinux Switcher. Also can you provide me with the link to dolby digital link. Thank you for your help.
naziraaqib3k said:
I've used this setup on miui 11 eu version and it ran just fine also I had already set SELinux to Permissive uaing the SELinux Switcher. Also can you provide me with the link to dolby digital link. Thank you for your help.
Click to expand...
Click to collapse
Here is the original thread -
https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192/amp/