Has anyone gotten Viper 4 Android to work with the pixel 6 pro yet? If not, are there alternatives? Any guides to doing this would be appreciated! I searched but didn't find much.
Android 12 (Viper4Android)
Has anyone managed to get Viper4Android working on the latest beta of Android 12? The usual methods don't work (makes sense, since its a new OS). Just curious. I like Android 12 so far, but might roll back to 11 if I can't get Viper going...
forum.xda-developers.com
Followed the guide in that thread and got it installed and seems to be working, any recommendations on the profiles for the speakers or the pixel buds a?
FabricatorGeneral said:
Seguí la guía en ese hilo y lo instalé y parece estar funcionando, ¿alguna recomendación sobre los perfiles para los altavoces o los botones de píxeles?
Click to expand...
Click to collapse
norteDon't put much Bass on the speakers because they over time deteriorateBass on the speakers because they over time deteriorate
For those that don't want to change their kernel to permissive due to security reasons, I used this method and is working fine for me. Legacy mode needs to be toggled on.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Lughnasadh said:
For those that don't want to change their kernel to permissive due to security reasons, I used this method and is working fine for me. Legacy mode needs to be toggled on.
Viper4Android
Anyone get this working yet?
forum.xda-developers.com
Click to expand...
Click to collapse
i didnt have to change to permissive. the 2nd. file is a Android 12 fix, i believe if you use the fix you do not have to change to permissive....
AndroidAddict420 said:
i didnt have to change to permissive. the 2nd. file is a Android 12 fix, i believe if you use the fix you do not have to change to permissive....
Click to expand...
Click to collapse
I was referring to the method linked in Post #2 where they said they changed their kernel to permissive. The Android 12 fix file is from another thread which you started and posted the file it. You might want to add a link to your post so people know what "fix" file you are talking about since it's not in this thread, lest people might get confused about what you are talking about.
Or maybe I'll just link it here...
Interested in a Working Formula to get Viper4Android Working? (ROOT)
Viper4Android for Google Pixel 6/6 Pro and most other devices on Android 12... It the time of testing this Method, it worked in November 2021 and December 2021 builds for my Google Pixel 6.... 1) Make sure your BL is unlocked and you are...
forum.xda-developers.com
I installed by using the method I had to do for OP8T. Install Audio_Modification_Library Magisk Module (DO NOT REBOOT) -> Install Viper Magisk Module (DO NOT REBOOT) -> Open Viper App (this forces a reboot) -> Remove Audio_Modification_Library. It works great for me in apps like AIMP, but in apps like YouTubeVanced have never worked for me.
card13 said:
I installed by using the method I had to do for OP8T. Install Audio_Modification_Library Magisk Module (DO NOT REBOOT) -> Install Viper Magisk Module (DO NOT REBOOT) -> Open Viper App (this forces a reboot) -> Remove Audio_Modification_Library. It works great for me in apps like AIMP, but in apps like YouTubeVanced have never worked for me.
Click to expand...
Click to collapse
Strange it doesn't process with YouTubeVanced for you. It should. Have you tried giving this mod a shot?
EDIT: Actually I think the version located at John Fawkes site is newer than the XDA one, so adding that link.
Audio Compatibility Patch (Formerly Universal deep_buffer Remover) [MMTEx]
This fixes music and streaming apps (Spotify, Pandora, etc) that aren't processing audio effects for various equalizer applications through the modification of audio policy. Starting with v1.6 USB_policy patcher (upp) and Notification_helper...
forum.xda-developers.com
John Fawkes Playground
@Lughnasadh I'm not currently using the Compatibility Patch. It's mainly because last time I did on the OnePlus phones, my Bluetooth audio would get fubar'd and require a Factory Reset to fix.
Thanks to the community, the Viper4android works for me on Pixe6 PRO, BUT I am unable to activate any VIPER-DDC , Headset correction profiles loading takes no effect, tried a few I see them active but no change in sound. Previously my OnePlus 8Pro worked fine with the same version (Android 12). Does anyone experience similar issue ? Can you please try and let me know.
ansher said:
Thanks to the community, the Viper4android works for me on Pixe6 PRO, BUT I am unable to activate any VIPER-DDC , Headset correction profiles loading takes no effect, tried a few I see them active but no change in sound. Previously my OnePlus 8Pro worked fine with the same version (Android 12). Does anyone experience similar issue ? Can you please try and let me know.
Click to expand...
Click to collapse
I don't have answer for your question, perhaps go to their Telegram group to ask for help as you may have more chance there.
I do have something for your consideration. I used V4A for longer than I can remember but it must be over 10 years. However, seems the developer has already quitted the project for quite sometime, the driver has never been updated in the past 7-8 years, we are lucky that it is still working with A12. But everything has an end, I tried it on A13 Beta and it doesn't work with it. If you search the web, you properly going to find that so far no one is able to make it work with A13. The A13 is already in beta 4 and official release could be sometime in next month, unless you are going to give up to update to A13, you better start to find something to replace V4A, my choice is JamesDSP but you may find something better suit your needs.
I prefer presets because I don't know what I'm doing. I ended up moving to PowerAmp and am usually pleased with the sound. If only the developer would enable roor features, man that would be cool.
Thanks acwcanada for the suggestion. I looked at the thread and so far may stick with Android 12 (those crazy audiophiles ) because I could not find 2 key features available in Viper4Android.
1. Headphone frequency response correction (VIPER-DDC or AutoEQ in Wavelet). This feature does not even work for me in Pixel 6 pro A12L , workaround: install wavelet and use its AutoEQ feature.
2. Dynamic System feature of Viper4Android creates bass subharmonics using reference frequencies and algorithm (selectable by choosing headphone type), so it can inject them in the music making it feel much richer and restores lack of low frequencies without "booming" effect created by other bass boosters. So far nothing in this word can beat this Viper4Andoid's feature.
Some good news folks: Viper4Android and Wavelet can be stacked and work in tandem .
Perhaps going to write James to consider the above, unless I missed it.
Cheers and thanks Team !
Related
Hi folks,
Did anyone get viper4android (XHiFi or FX) working on the G4? I tried the normal lollipop version but it screws up the camera; video recording fails within 1 second, probably due to some ALSA config or whatever (I'm no expert). I did see some closed thread (audio-engine-absolute-sound-project-t3015180"]http://forum.xda-developers.com/android/software/audio-engine-absolute-sound-project-t3015180[/URL]) on TASP where @ahrion did his best to make an all-in-one package for install on newer devices. I will see how that goes, but I'm more hoping on someone chiming in to tell me how to do it instead of reinventing the wheel so to speak...
- update -
Just tried the TASP package found elsewehere on the internet (13b version) and that seems to work, except for the permissive mode which doesn't stick to permissive. I'm running v10b (or 10c depending how you look at it) and it seems the adb su 0 setenforce 0 command doesn't work like it did on 10a?
So last step, I'm stuck on is setting SELinux to permissive... Iet's google some more
Don't you need to be rooted for viper to work? That's 1 of the main reasons I want root
Sent from my VS986 using Tapatalk
Yes and I have root. It's definitely SELinux, setenforce 0 does the trick until reboot...
https://www.dropbox.com/s/vri6pb4vb38bhsu/viper_v2.3.4.0_-_remove_fx_build_fix.zip?dl=0
Gesendet von meinem LG-H815 mit Tapatalk
Thanks, interesting... but, what exactly am I flashing with this? Looks like a modified viper installer, but does it also take care of SELinux?
Who made this ? I want to see if there is any updates,working good for me !
I thought you couldn't permanently change SELinux to permissive on Android 5 unless you were using a custom firmware like AOSP.
leijonasisu said:
I thought you couldn't permanently change SELinux to permissive on Android 5 unless you were using a custom firmware like AOSP.
Click to expand...
Click to collapse
You thought right.
There's an app on Fdroid called "SeLinux Mode Changer" that'll set the SeLinux state to permissive on every boot. But Google doesn't like the app, so it randomly remembers you to remove the app.
About gave up for months, then it clicked in my mind when i saw a post mention to make sure all other audio apps redirect eq to viper, and if not, change them. Even if you dont use a certain audio player app, change it too.
Problem is, i could not get the lg music app (which i never use) to change the equalizer to viper, it just had it's own default settings, so i ignored it. So i decided to revisit the lg app, and froze the app with link2sd, i also froze the lg video app too, just in case. Rebooted and now viper sees NEON and i can even run without compatibility mode (which did not work consistantly for me) .
I tried all steps to get this to work, not sure what other things are needed for everyone else, but i tried moving viper to system, installed selinuxmodechanger, maybe this can be uninstalled now, i have no idea. I have no plans to fix what isnt broken and find out myself, so just try freezing lg music app for starters.
Hope it works for you, if so, let the community know what steps you had to do!
involver said:
Hi folks,
Did anyone get viper4android (XHiFi or FX) working on the G4? I tried the normal lollipop version but it screws up the camera; video recording fails within 1 second, probably due to some ALSA config or whatever (I'm no expert). I did see some closed thread (audio-engine-absolute-sound-project-t3015180"]http://forum.xda-developers.com/android/software/audio-engine-absolute-sound-project-t3015180[/URL]) on TASP where @ahrion did his best to make an all-in-one package for install on newer devices. I will see how that goes, but I'm more hoping on someone chiming in to tell me how to do it instead of reinventing the wheel so to speak...
- update -
Just tried the TASP package found elsewehere on the internet (13b version) and that seems to work, except for the permissive mode which doesn't stick to permissive. I'm running v10b (or 10c depending how you look at it) and it seems the adb su 0 setenforce 0 command doesn't work like it did on 10a?
So last step, I'm stuck on is setting SELinux to permissive... Iet's google some more
Click to expand...
Click to collapse
Any chance you have a link to download TASP 13B? I absolutely cannot find it on the official dev page. Maybe I am blind.
I've sent you a PM with the link
involver said:
Yes and I have root. It's definitely SELinux, setenforce 0 does the trick until reboot...
Click to expand...
Click to collapse
Enable Init.d on your rom and put a script with the following lines in it in the /etc/init.d folder.
#!/system/bin/sh
setenforce 0;
That should set SELinux to permissive at runtime.
Hi - thanks for your tip, but I've moved on to the V10 and then to the OP3 since then
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Firebuster said:
So I have been trying to get LDAC or apt-X working on my razer phone but it has not worked. I am on the latest stock ROM rooted with magisk (via ADB not TWRP) and with the rayglobe magisk module installed but it just stays on AAC. My headphones are Sony WH-1000XM2 and LDAC was working when using the resurrection remix ROM from the development thread but I had to uninstall the ROM due to instability and no sign of progression. Any help would be appreciated.
Click to expand...
Click to collapse
They locked it down somehow I think. I have 2 threads in here asking for help but no one seems to be able to help me. For added reference, here is the error produced even when all the files are added with root to enable aptx or ldac
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aac
to
Code:
persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptXHD
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
ClubRaptor said:
I installed the magisk aptx&aptxHD module and modified /system/vendor/build.prop then aptx got working.
(I couldn't test with aptxHD or LDAC cos I have no compatibe device with them.)
to
This is the same parameter the magisk module set to /system/build.prop.
To guess, LDAC will may work if an appropriate value set to the prop.
Click to expand...
Click to collapse
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Firebuster said:
This worked to enable switching to them however now Bluetooth just crashes. I changed it to persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-ldac
Edit:
Some interesting notes. I tried a few steps to debugging including readding AAC to the list which did nothing but if I only add aptx then the Bluetooth app no longer crashes however no sound plays so I'm guessing it's the lib files that are not correct? I just used the aptx package in magisk so if there's any other that I'm missing or other suggestions that would be useful
Click to expand...
Click to collapse
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
manor7777 said:
I still can't get it to switch to aptx (the one I want) or ldac. It still falls back to SBC usually or aac if I'm on a different speaker. Any idea what I'm doing wrong? I'm on slot a on my device, rooted with magisk and I have tried multiple aptx modules. Is there a specific build.prop editor you use? Both my speakers and headphones support it and work with other devices and I'm still getting the error I replied with above (page one)
I'm an experienced rooter, so don't be afraid to fully explain any steps I may be missing out!
Click to expand...
Click to collapse
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Firebuster said:
I used root explorer and changed the build.prop entries in system\vendor\. In the first place I used the root essentials build.prop editor which shows a different build.prop. other than that I literally just edited that line and that allowed me to change it. I can't think of anything else I did other than install a bunch of library files which I'm guessing you found the same ones as me because it was very limited on what was available and up to date
Click to expand...
Click to collapse
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
manor7777 said:
OK, awesome. You rock. That got it to select aptx - now my 2nd problem, no audio! I can see in dev options and bt settings that it's showing aptx, but I get no audio (well, I get an almost click click click noise) then my Bluetooth adaptor for my headphones crashes. And it forces my headphones to turn off. I tried 3 different magisk modules for the library files, any ideas - I was getting SBC audio before
Click to expand...
Click to collapse
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Edit: seems to be looping these messages in catlog
Firebuster said:
Sounds like the same problem I am having. Aptx doesn't work and aptx HD and LDAC just crash Bluetooth. Genuinely have no idea where to go from here. It must be a driver or library file. Real shame it's not working.
Click to expand...
Click to collapse
OK, so last night and this morning I have been just messing with things. I no longer crash my headphones and force them to turn off, but I still have no audio over aptx - though at least it's not crashing my headphones (Bluetooth in the phone was always OK). There is one error I'm getting and I'm not sure if its related of not, but is to do with a buffer failing to release. See my screenshots of logs (just documenting here for reference)
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
hatemosphere said:
so basically i went your path a few days ago and dropped that idea. please post updates if you manage to get aptx\aptx hd\ldac working (Razer Phone + Sony WH-1000 XM2)
Click to expand...
Click to collapse
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
manor7777 said:
Cc @Firebuster
So, I might be an experienced rooter (no 1 click toolkits here) I am NOT a developer. I've tried a combination of a bunch of things to try and get this to work, and nothing has!
I did however get it to work by installing a GSI (basically a rom) to the device, but even that was painful to get working (well, installed). Now running AOSP 8.1 GSI w/gapps and I flashed magisk for root. I then installed the Aptx magisk module from the built in repo and it works perfectly fine. Not sure if It's something in razer software as I'm technically more up to date now so it's not like I was using the wrong drivers.
Can't find a decent dolby atmos I can install that will work along side v4a, all the magisk modules are for android 7 or 6.
Otherwise that's the only way I have found so far, sorry guys! - benefit is, other than AOSP's ****ty camera app (use the gcam port instead), literally everything works fine, and I even get stronger vibration on a GSI
Click to expand...
Click to collapse
Yeah I might move onto that too. To try to fix the Bluetooth issues. I can only assume razer excluded some of the functionality but since it's baked into android 8 I don't see why they would remove it.
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
linuxct said:
Razer and their development team is already informed about this issue, and they have correctly addressed it, and all the Bluetooth issues (which were a few), in the upcoming update MR2. No ETA.
Click to expand...
Click to collapse
so i've just got a new update and now i'm wondering if we should try this again...
hatemosphere said:
so i've just got a new update and now i'm wondering if we should try this again...
Click to expand...
Click to collapse
Go ahead, I can't since I'm on a Pie GSI.
If anyone has an LDAC BT Headset please give this a try.
cc @Firebuster
Great news, I just spent 2 hours updating my phone, with flashing back to stock because the OTA did not want to update me since I had Magisk, then putting everything back like before.
The update did not change anything.
Tried to do my research on issues with the Razer phone before getting it, but I guess this is just one of those things you don't comprehend until actually having the device in your hands. I came from a Oneplus One on Lineage OS and am comfortable with flashing (but no experience with GSI yet).
My razer phone is stock and not rooted. Anything I can do to contribute to test getting Apt-X working? The settings says my phone is up to date (build number OPM1.171019.011-RZR-180803.6033).
Got the official Pie installed - no LDAC nor AptX still.
cubeover said:
Got the official Pie installed - no LDAC nor AptX still.
Click to expand...
Click to collapse
you installed the official pie update for the razer phone 1?
So recently @guitardedhero release and version of Dolby atmos for android Pie and i was excite about it but it only for for android pie only,so i try downgrade back to 9.0.17 but apparently the mod cause the phone go straight to crashdump mode and like hour ago he release couple more version but i was already on android 10 but after messing around with flash script i was able flash it on OOS10 imma attach the file i mod here for specific only for OOS10 only since this the only version that work flawless on OOS10 other test version i try they either force close the app or audio loss, highly recommended flash it along with Ainur Narsil---haven't test with other mod yet but in my opinion Dolby itself already better
https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
UPDATE: latest dolby re-port by reiryuki fixes full brightness issue working on (maybe)all custom rom available now for Oneplus 6t and maybe other device has FOD custom rom ! please head to his github repo link below for the download!
Download
Credit:
@guitardedhero (for The Port)
-Me (for testing and mod the file to work on OOS10)
-Reiryuki for the fix and new port
-Dolby (for Dolby Atmos)
_BГ@ckθut said:
So recently @guitardedhero release and version of Dolby atmos for android Pie and i was excite about it but it only for for android pie only,so i try downgrade back to 9.0.17 but apparently the mod cause the phone go straight to crashdump mode and like hour ago he release couple more version but i was already on android 10 but after messing around with flash script i was able flash it on OOS10 imma attach the file i mod here for specific only for OOS10 only since this the only version that work flawless on OOS10 other test version i try they either force close the app or audio loss, highly recommended flash it along with Ainur Narsil---haven't test with other mod yet but in my opinion Dolby itself already better
https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
Credit:
@guitardedhero (for The Port)
-Me (for testing and mod the file to work on OOS10)
-Dolby (for Dolby Atmos)
Click to expand...
Click to collapse
Can u help me why it would not open and crashing. I'm on iOS 10.3.0
tswb said:
Can u help me why it would not open and crashing. I'm on iOS 10.3.0
Click to expand...
Click to collapse
You had any sound mod install? And what magisk version you had?
I have install the Dolby atoms only and no audio mod. Latest magisk 20.3 and I try to set the storage it won't open the permission.how to get granted permission to the storage.
tswb said:
I have install the Dolby atoms only and no audio mod. Latest magisk 20.3 and I try to set the storage it won't open the permission.how to get granted permission to the storage.
Click to expand...
Click to collapse
Like dolby ask you to granted storage permission or magisk? Cause dolby not require to Grant any permission as far as i know!there is couple people has successful installed it without any issue so far
tswb said:
I have install the Dolby atoms only and no audio mod. Latest magisk 20.3 and I try to set the storage it won't open the permission.how to get granted permission to the storage.
Click to expand...
Click to collapse
Use Magisk 20.1 try it and test if works then update to Magisk 20.3 done
Mervingio said:
Use Magisk 20.1 try it and test if works then update to Magisk 20.3 done
Click to expand...
Click to collapse
OK I will try it. Thanks
it works this is the good news, the bad news is that my bluetooth then stops working, it can no longer be switched on
tswb said:
OK I will try it. Thanks
Click to expand...
Click to collapse
did you find a chance to try it ?
i wonder we loose modules or not after we downgrade to 20.1 ?
also dolby still works when we upgrade back to 20.3 ?
Can it work simultaneously with Dolby digital plus?
Also do I need to install anything (AML)?
lazye53 said:
Can it work simultaneously with Dolby digital plus?
Also do I need to install anything (AML)?
Click to expand...
Click to collapse
Give it a try! Haven't has time to test yet but i guess it should work!
the_poseidon said:
did you find a chance to try it ?
i wonder we loose modules or not after we downgrade to 20.1 ?
also dolby still works when we upgrade back to 20.3 ?
Click to expand...
Click to collapse
I got working on 20.1 but i notice the Bluetooth not working after I install the zip file.
tswb said:
I got working on 20.1 but i notice the Bluetooth not working after I install the zip file.
Click to expand...
Click to collapse
If you remove module Bluetooth is not longer working
Well guy there is a news testing zip... currently at work now but ill test it after work and let you guy know! I still using the same zip and don't has any problem with Bluetooth or anything but ill update the new zip here a little bit!
https://forum.xda-developers.com/an...-atmos-axon-7-oreo-port-t3740508/post81515331
I was reading through a lot of that thread and it looks like it's still based for pie and there was a section in there saying that you have to change your build prop setting to SDK level 28 if you are on oxygen 10 and Android 10 you'll be SDK 29 so I was getting force closes and I took a big risk when do the build prop edited my SDK level 228 and went straight into a bootloop. So I had to actually do a factory reset. I then restore from twrp, but I screwed up and restored everything what I should have just done a system and data restore only because then I did a soft brick and had to use the MSM tool and start all over again at Android 9! Lol.. so I know guitardedhero was making special media files for audio library they were . so extensions... I'm going to keep digging because on Android 10 I've got ice sound working which is an Asus driver and I can even change the four configurations as well as the 11 different sound profiles fall through terminal emulator. I also have a flashable DTS 2.0
groovemetal81 said:
I was reading through a lot of that thread and it looks like it's still based for pie and there was a section in there saying that you have to change your build prop setting to SDK level 28 if you are on oxygen 10 and Android 10 you'll be SDK 29 so I was getting force closes and I took a big risk when do the build prop edited my SDK level 228 and went straight into a bootloop. So I had to actually do a factory reset. I then restore from twrp, but I screwed up and restored everything what I should have just done a system and data restore only because then I did a soft brick and had to use the MSM tool and start all over again at Android 9! Lol.. so I know guitardedhero was making special media files for audio library they were . so extensions... I'm going to keep digging because on Android 10 I've got ice sound working which is an Asus driver and I can even change the four configurations as well as the 11 different sound profiles fall through terminal emulator. I also have a flashable DTS 2.0
Click to expand...
Click to collapse
Yeah that what im concerned about to change the builprop SDK to 28 instead of that i change a code on the zip so it bypass the SDK check to able it flash on SDK 29....it was a test but apparently i didn't has any problem about a Bluetooth or anything! And there is couple people successful flash it as well but imma caught up with lastest zip and lemme see if i could mod it to work on OOS 10!and yep by default it only support Android pie only! So imma try troubleshooting as much as possible before releasing it!
Updated to latest Dolby Atmos 0.727 zip and it attached on the first page... I'll leave 0.64 zip there just in case anyone need it! And once 727 zip it work without any problem on 10.3.0 for me at least (testing on AAC,LDAC even aptx HD) but let me know
groovemetal81 said:
I was reading through a lot of that thread and it looks like it's still based for pie and there was a section in there saying that you have to change your build prop setting to SDK level 28 if you are on oxygen 10 and Android 10 you'll be SDK 29 so I was getting force closes and I took a big risk when do the build prop edited my SDK level 228 and went straight into a bootloop. So I had to actually do a factory reset. I then restore from twrp, but I screwed up and restored everything what I should have just done a system and data restore only because then I did a soft brick and had to use the MSM tool and start all over again at Android 9! Lol.. so I know guitardedhero was making special media files for audio library they were . so extensions... I'm going to keep digging because on Android 10 I've got ice sound working which is an Asus driver and I can even change the four configurations as well as the 11 different sound profiles fall through terminal emulator. I also have a flashable DTS 2.0
Click to expand...
Click to collapse
I would like to personally apologise to you for posting information that caused much frustration and inconvenience for you.
That was irresponsible of me to state workarounds to circumvent a restriction I implemented without knowing the risks that could be involved and not just taking out the restriction myself.
Thank you for sharing your experience. If I had not seen it just now, I would have still assumed such an action you took to be harmless.
I did remove this restriction many versions ago after learning that many were having success on Android 10 and the latest zip a couple hours ago seems to provide a much higher success rating and the support for existing audio mods and their effects seems to now be in place if you ever get an itch to try again without needing to do any hacky, ill-advised stuff like what I said last week.
:good:
My Bluetooth stops working after flashing. Reflash of OOS was necessary to get it back.
I have successfully put together a method to get Dolby Digital Plus and Viper4Android running on Redmi Note 8 Pro. Firstly I am rooted on 11.0.6 Global and using LR-TWRP as recovery. On another note I have tried nearly every recovery on this Forum but the only one that doesn't give me a black screen the LR-TWRP.
1. First you need to get the Android running in Permissive mode. For me the Magisk module DID NOT work. To get permissive I found a file on another forum that someone was using on other Redmi devices. It works perfectly with no flaws. Boot into TWRP flash Permissiver_v4_2.zip. And boot back into the device.
***Note.. If you upgrade rom using TWRP as I did from 11.0.2 to 11.0.6. You will have to reflash this file to get everything running properly.
2. Open Magisk and flash ViPER4Android_FX-v2.7.1.0(2710).zip. Reboot device and the open V4A. You should be prompted to install driver. Do so and reboot if prompted to, I don't remember for sure if it makes you or not.
3. Open Magisk and flash 2.1Audio_Modification_Library-v2.4.zip and then reboot.
***NOTE.. Only this version of Audio Modification I have had luck with getting this to run. I updated this file after having everything completely setup and working and it broke V4A and Dolby. Had to uninstall and reinstall this version..
4. Boot into TWRP, NOT Magisk and flash Dolby_Digital_Plus_v.6.5.zip
5. On reboot confirm everything is working. For me it is working flawlessly. Below is a link to the files you will need.
DOWNLOAD
Gonna try this now because the previous tutorial about v4a does work but the moment I plug in my earphones, the status changes to "abnormal"
djgilquirino said:
Gonna try this now because the previous tutorial about v4a does work but the moment I plug in my earphones, the status changes to "abnormal"
Click to expand...
Click to collapse
That is likely due to your phone not being in permissive mode. I've seen that guide as well. I took my past knowledge of getting Viper + Dolby to work and came up with this solution. Being in permissive mode is required for both apps to function
I just found out the reason why my V4A doesn't work when I plug in my headset/earphones. To all those who use poweramp and set your output to "Hi-Res Output", make sure your sample rate is set to 48khz. Setting it to 96khz and up changes the status on V4A to abormal and won't work.
Thanks bro. It is working for me as well you made my day..
rraghava10 said:
Thanks bro. It is working for me as well you made my day..
Click to expand...
Click to collapse
Awesome my dude!! Glad I could help. I'm new to writing guides but love this device and would like to encourage its development as much as I can.
When I flash V4A it functions properly however my SIM card is no longer recognize. When I uninstall V4A my sim is restored. What's up with that?
chugs said:
When I flash V4A it functions properly however my SIM card is no longer recognize. When I uninstall V4A my sim is restored. What's up with that?
Click to expand...
Click to collapse
That is extremely weird. Never heard of anything like that before. Just a couple thoughts but do you have BusyBox installed through Magisk and have your phone set to permissive already?? Also what MIUI version are you running. I have tested this successfully on 11.0.2 and 11.0.6 Global.
I'm still down on 10.4. I haven't been convinced to move to 11
Worked perfectly from EEU (EU) rom moved to 11.0.6 (Global)!
Thank you very much!
alejandromujica.rsm said:
Worked perfectly from EEU (EU) rom moved to 11.0.6 (Global)!
Thank you very much!
Click to expand...
Click to collapse
Your welcome and that's awesome.. Glad I could help bro!
https://ibb.co/YLt7r7s result miui global 11.0.2 err
anasfanani said:
https://ibb.co/YLt7r7s result miui global 11.0.2 err
Click to expand...
Click to collapse
You are not permissive. That is the exact error I got before I found the file I reference to flash to get 'permissive'. To check your status go to terminal and first 'su' to get root. Then type 'getenforce'. Make sure your device is showing permissive. If this is notthe problem I would be surprised. Let me know and I will help you work the problem..
bpawnz said:
You are not permissive. That is the exact error I got before I found the file I reference to flash to get 'permissive'. To check your status go to terminal and first 'su' to get root. Then type 'getenforce'. Make sure your device is showing permissive. If this is notthe problem I would be surprised. Let me know and I will help you work the problem..
Click to expand...
Click to collapse
Thanks. The problem is in selinux magisk module. I uninstalled and install other selinux app from https://github.com/MrBIMC/SELinuxModeChanger and its works
anasfanani said:
Thanks. The problem is in selinux magisk module. I uninstalled and install other selinux app from https://github.com/MrBIMC/SELinuxModeChanger and its works
Click to expand...
Click to collapse
Awesome. The file I reference will change se status from boot. That app I think you have to set it after every reboot if I remember correctly. Regardless I'm glad you got it working. FYI.. Dolby won't show up as an installed app if your not running permissive as well. I know that from trial and error. Glad you got it working!
Steps work. Will confirm if this is any better than standalone V4A
[Update]
Yup. Definitely way better sound quality comparing to the previous methods i used. Also thanks for sharing permissiver.. The previous way i used to change SELinux was a massive pain in my neck. (Global phone on 11.0.2 Global ROM) Looking to see how v4a will fare in upcoming custom ROMs.
Do we have any dual speaker audio sound mod for our note 8 pro global?
+1 to dual speaker mod!
bpawnz said:
Awesome. The file I reference will change se status from boot. That app I think you have to set it after every reboot if I remember correctly. Regardless I'm glad you got it working. FYI.. Dolby won't show up as an installed app if your not running permissive as well. I know that from trial and error. Glad you got it working!
Click to expand...
Click to collapse
Dolby digital is not working after android 10 update... need the version update
Dear all, please note and be aware, this mod will not work on android 10 because
1. dolby digital version is not supported as i stated earlier..
2. when we change SE linux to permissive, phone becomes laggy and many secured application will not work... i have personally tried that may be because of high security of android 10.. i think we will need a custom rom
Hi, I did some experiments with the GSI PIXEL EXPERIENCE ALPHA that might interest some developers.
It works properly as is on nairo (moto g 5g plus) except for a few things.
- TWRP recovery gets broken, i think we need a newer version for this phone to work with android 12.
- The audio doesn't get routed in any way (i've tried with apps) to the aux output (headset).
I would take care of this problems if i had knowledge, if anyone can help it's welcome for sure, thanks in advance!
Tommy0000 said:
Hi, I did some experiments with the GSI PIXEL EXPERIENCE ALPHA that might interest some developers.
It works properly as is on nairo (moto g 5g plus) except for a few things.
- TWRP recovery gets broken, i think we need a newer version for this phone to work with android 12.
- The audio doesn't get routed in any way (i've tried with apps) to the aux output (headset).
I would take care of this problems if i had knowledge, if anyone can help it's welcome for sure, thanks in advance!
Click to expand...
Click to collapse
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
wesleyvanneck12345678 said:
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
Click to expand...
Click to collapse
Thank you very much, i'll try it, i don't get yor first sentence, is it broken for everyone? (english isn't my first language)
wesleyvanneck12345678 said:
1 share the gsi twrp is broken for even on a android 11 gsi as for audio
1. Go to developer options, find something like "Disable A2DP offload", turn it on and restart your device.
2. After the restart head back to settings, head to Phh Treble settings, then misc and enable "Force headphone switch" and
Click to expand...
Click to collapse
It worked without forcing headphone switch, tysm! Now i'm working to get some padding on the status bar if i'm able to
Tommy0000 said:
It worked without forcing headphone switch, tysm! Now i'm working to get some padding on the status bar if i'm able to
Click to expand...
Click to collapse
if make cutout work send it phhusson
wesleyvanneck12345678 said:
if make cutout work send it phhusson
Click to expand...
Click to collapse
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Tommy0000 said:
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Click to expand...
Click to collapse
share it with me am waiting for fix to long with gsis
Tommy0000 said:
I successfully made one with nonsense notch, idk if i can send phh the apk the module created, i used the customleft script at 240 px
Click to expand...
Click to collapse
you cant send it to him but i didnt know mudule but can you share it with me
Sure! I've used nonsense notch to create an overlay at 240 pixel from the left of the statusbar, it doesn't work on landscape mode but it's fine for me.
Idk if it works by just inserting it in /system/product/overlay and unzipping it and then maybe installing the apk(?) (Mine it's in a folder that's why i made a zip file)
Overlays are really tricky, i recommend following the guide for the module instead of doing this.
After installation you can go to dev options and under simulate screen cutout you can choose the one you created *DO NOT CHOOSE THE STOCK OPTIONS ON ANDROID 12 THEY WILL SOFTLOCK YOUR PHONE*
I will create a guide on the fixes for gsi roms with your audio tweaks and this one, thank you again, let me know if you succeed!
Again, you shoudl really create one yourself on the custom mode of this module https://forum.xda-developers.com/t/module-n3o-no-nonsense-notch-overlay.4226413/
I created a guide to install everything https://forum.xda-developers.com/t/...s-nairo-and-some-post-install-tweaks.4364963/
Tommy0000 said:
Sure! I've used nonsense notch to create an overlay at 240 pixel from the left of the statusbar, it doesn't work on landscape mode but it's fine for me.
Idk if it works by just inserting it in /system/product/overlay and unzipping it and then maybe installing the apk(?) (Mine it's in a folder that's why i made a zip file)
Overlays are really tricky, i recommend following the guide for the module instead of doing this.
After installation you can go to dev options and under simulate screen cutout you can choose the one you created *DO NOT CHOOSE THE STOCK OPTIONS ON ANDROID 12 THEY WILL SOFTLOCK YOUR PHONE*
I will create a guide on the fixes for gsi roms with your audio tweaks and this one, thank you again, let me know if you succeed!
Again, you shoudl really create one yourself on the custom mode of this module https://forum.xda-developers.com/t/module-n3o-no-nonsense-notch-overlay.4226413/
Click to expand...
Click to collapse
thank you very much it works and it even does my games without a black bar
wesleyvanneck12345678 said:
thank you very much it works and it even does my games without a black bar
Click to expand...
Click to collapse
Ye it's very fortunate it stops working when landscape! I quite like that non-feature