Hi guys. I managed to enable Dual Speaker Mod on OnePlus 3/3T on OxygenOS and Android 9 and 10.
Changelog:
v1.0
- First release for Pie
v2.0
- fixed for OxygenOS Pie
- support for custom Android 9 & 10
- Magisk Module
LINK (MIRROR): Google Drive
or Magisk Repo!
Installing:
1. Install module in Magisk Manager
2. Reboot and profit
Please test and report if you having issues here or on Telegram
Reserved
Thank you ! A Magisk module is possible ?
lutherkingmartin said:
Thank you ! A Magisk module is possible ?
Click to expand...
Click to collapse
Soon!
Sent from my OnePlus3T using XDA Labs
Tested it on latest havoc ROM with OP3. Sadly it doesn't work
mrfrantastic said:
Tested it on latest havoc ROM with OP3. Sadly it doesn't work
Click to expand...
Click to collapse
hello, yes doesn't work havoc os latest version. OP3T.
@mrfrantastic @acceslevel are you using another mods like Viper4Android, Dolby or both combined with AML?
For me is working even with Viper4Android installed.
Sent from my OnePlus3T using XDA Labs
IonutGherman said:
@[email protected] are you using another mods like Viper4Android, Dolby or both combined with AML?
For me is working even with Viper4Android installed.
Click to expand...
Click to collapse
Nope, none of them or anything audio related. Also no EdXposed.
Maybe someone else with OP3 can confirm my report.
IonutGherman said:
Hi guys. I managed to enable dual speaker mod on OnePlus 3T (didn't tested on OnePlus 3, but I think is working) with HavocOS 2.7 build 01.08.2019 and is working good. It should work with ROMs based on LineageOS, didn't tested on OxygenOS since LOS team changed some things in mixer_paths_tasha.xml.
Version 1.0
- first release for Pie
LINK (MIRROR): URL
Installing:
1. First backup your original mixer_paths_tasha.xml by renaming it to mixer_paths_tasha.xml.bak
2. Copy mixer_path_tasha.xml (modded one) to /system/vendor/etc
3. Reboot and profit
Please test and report if you having issues!
Magisk version coming soon!
Click to expand...
Click to collapse
In my custom rom already have this file ??? don't know why ( skydragon OS )
baba duy said:
In my custom rom already have this file ??? don't know why ( skydragon OS )
Click to expand...
Click to collapse
Replace mixer_paths_tasha.xml with the modded one.
Sent from my OnePlus3T using XDA Labs
IonutGherman said:
Replace mixer_paths_tasha.xml with the modded one.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
i can't dowload it dead link
baba duy said:
i can't dowload it dead link
Click to expand...
Click to collapse
Try downloading from XDA
Sent from my OnePlus3T using XDA Labs
What are the lines you have changed/ added to the xml?
Ofcourse I can compare, but it would help me for making a script to modify the original xml without replacing it.
Hope you are willing to share your knowledge!
Not working on my OnePlus 3, any media won't play after replacing this with my original xml file.
One of my two sim cards also stopped working.
Workings on oneplus 3 with havoc latest version. Thanks
ShayantanS said:
Workings on oneplus 3 with havoc latest version. Thanks
Click to expand...
Click to collapse
I am also on latest HavocOs. Are you sure it's working?
mrfrantastic said:
I am also on latest HavocOs. Are you sure it's working?
Click to expand...
Click to collapse
Yes bro... 100%. I covered the bottom speaker to check and also brought the earpiece close to ears, it worked.
Only thing which I did was didn't do the .bak option and instead copied the original to main folder and replaced the original with modified one.
ShayantanS said:
Yes bro... 100%. I covered the bottom speaker to check and also brought the earpiece close to ears, it worked.
Only thing which I did was didn't do the .bak option and instead copied the original to main folder and replaced the original with modified one.
Click to expand...
Click to collapse
I used a different file explorer and now it works. I used Total Commander before, fyi.
mrfrantastic said:
I used a different file explorer and now it works. I used Total Commander before, fyi.
Click to expand...
Click to collapse
I will improve the script and will make a Magisk module, but now I don't have time because I work 2 jobs and I am all the time tired and not in the mood to script something.
Confirm that using a root file explorer application, any media content will fail to load, but using the TWRP inbuilt file manager it works just fine. Havoc 2.8
Thanks a lot!
Related
Hey Guys!
I actually have been looking for a way to get Viper4Android working today. And i actually found a method to do it. By luck, OnePlus posted the Oxygen 3.0 based on android 6.0.1 today. This version of android is compatible with the newest version of Viper4Android. This version actually comes without an equalizer like 2.2... but oh well. I liked viper way better anyway.
Just wanted to give my 2 cents to the forum.. just wanted to let people know there is opportunity here to enjoy better music while you are waiting for CM 13 like me =)
How i got it to work:
- First install Oxygen 3.0 with a custom TWRP created for Oxygen 3.0 (see this url: link to oneplus forums)
- Secondly, use the custom made SuperSU (credits to @Yash98) = this link
- When the phone is updated and rooted, you can install BusyBox through the app store. After you did that download the APK of Viper on your phone via the original XDA thread
- Don't run it yet. Download SELinuxModeChanger via the original XDA thread.
- Change the mode to permissive, go back to Viper and install the drivers. It'll ask you for a reboot, do so. After the reboot open Viper4Android and press the 3 dots on the right high corner. Examining the driver status would show that the driver is enabled. If it's not. Try to empty the google music cache & removing the data (i did so somewhere in the process).
Hope this can make anybody happy. I'm an audiophile so i'm more than happy.
- Shakaraja.
The new Beta of OxygenOS 3.0 does NOT come with any audio enhancements, so you may even flash packages of audio mods, as I did
MaxtremePL said:
The new Beta of OxygenOS 3.0 does NOT come with any audio enhancements, so you may even flash packages of audio mods, as I did
Click to expand...
Click to collapse
Can you share the audio mods you used?? Thanks
---------- Post added at 10:43 PM ---------- Previous post was at 10:42 PM ----------
shakaraja said:
Hey Guys!
I actually have been looking for a way to get Viper4Android working today. And i actually found a method to do it. By luck, OnePlus posted the Oxygen 3.0 based on android 6.0.1 today. This version of android is compatible with the newest version of Viper4Android. This version actually comes without an equalizer like 2.2... but oh well. I liked viper way better anyway.
Just wanted to give my 2 cents to the forum.. just wanted to let people know there is opportunity here to enjoy better music while you are waiting for CM 13 like me =)
How i got it to work:
- First install Oxygen 3.0 with a custom TWRP created for Oxygen 3.0 (see this url: link to oneplus forums)
- Secondly, use the custom made SuperSU (credits to @Yash98) = this link
- When the phone is updated and rooted, you can install BusyBox through the app store. After you did that download the APK of Viper on your phone via the original XDA thread
- Don't run it yet. Download SELinuxModeChanger via the original XDA thread.
- Change the mode to permissive, go back to Viper and install the drivers. It'll ask you for a reboot, do so. After the reboot open Viper4Android and press the 3 dots on the right high corner. Examining the driver status would show that the driver is enabled. If it's not. Try to empty the google music cache & removing the data (i did so somewhere in the process).
Hope this can make anybody happy. I'm an audiophile so i'm more than happy.
- Shakaraja.
Click to expand...
Click to collapse
Thanks for the detailed guide... Will test now thanks
anees167 said:
Can you share the audio mods you used?? Thanks
Click to expand...
Click to collapse
Divine Beats by Royal Seeker (DolbyDigital+ version) located at:
http://theroyalseeker.github.io/
In order for this mod to work you need permissive SElinux
I'm not able to install custom recovery it just gets stuck at the one plus logo. And when I reboot normally it gets back to stock recovery. Any solution plz
Did you disable boot to stock recovery and also you may have to fastboot recovery
Can I reduce the loudest sound of OxyGenOS3 with Viper4Android?
I have distorted sound using the v4a. How fix it?
Bluetooth doesn't work when V4A drivers is installed.
Anyone can solved this problem?
Thanks, got it working. Don't notice too much difference in sound, but maybe I just haven't foudn the right settings yet.
It dosent work getting distorted sound
viper4android install than sound break problem is fix?
mohamm3edadam said:
I'm not able to install custom recovery it just gets stuck at the one plus logo. And when I reboot normally it gets back to stock recovery. Any solution plz
Click to expand...
Click to collapse
You need the TWRP version meant for H2OS. You will find it in any H2OS based ROM thread.
Skick3 said:
Can I reduce the loudest sound of OxyGenOS3 with Viper4Android?
Click to expand...
Click to collapse
Yes, there are options. Find gain controls and tweak them to your preference.
ras_fyah said:
I have distorted sound using the v4a. How fix it?
Click to expand...
Click to collapse
Akhil701 said:
It dosent work getting distorted sound
Click to expand...
Click to collapse
If you still are on OOS 2.2.x then V4A will not work. This fix is specifically meant for OOS 3.
If you are on OOS 3, then try reflashing OOS 3 with a clean flash. This might fix it, but only if you are on OOS 3.
mvha said:
Bluetooth doesn't work when V4A drivers is installed.
Anyone can solved this problem?
Click to expand...
Click to collapse
Did you install the right drivers? And also check if you set the SELinux mode to Permissive.
locxFIN said:
Thanks, got it working. Don't notice too much difference in sound, but maybe I just haven't foudn the right settings yet.
Click to expand...
Click to collapse
Search XDA Forums for V4A profiles and use a preferred profile according to your type of music.
whwhdtk5689 said:
viper4android install than sound break problem is fix?
Click to expand...
Click to collapse
Only if you have flashed the latest beta of OOS 3. This fix is OOS 3 specific and DOES NOT APPLY TO OOS 2.
arch_geek said:
Only if you have flashed the latest beta of OOS 3. This fix is OOS 3 specific and DOES NOT APPLY TO OOS 2.
Click to expand...
Click to collapse
yes. i'm oos 3.0 MM.
wow i'm install now viper4android !
thank you !
arch_geek said:
Did you install the right drivers? And also check if you set the SELinux mode to Permissive.
Click to expand...
Click to collapse
You've Got a Point. I have installed wrong version of V4A. Now working all. Thank You
Sorry for the noob question and if I'm posting at the wrong place. When you first install OOS 3.0 it's not rooted right? How do I root it? Thanks for the help.
shakaraja said:
Examining the driver status would show that the driver is enabled. If it's not. Try to empty the google music cache & removing the data (i did so somewhere in the process).
Click to expand...
Click to collapse
Hm i had the same problem. Driver Status was false.
My Workaround was i clicked in Viper many Menus up an down. Lock Effect Mode disable to speaker. UI Setting to Expert and suddenly the Driver Status was True.
No cleaning data. I didn´t installed google play music.
With Viper4Anroid on OO2 Oxygen3 the sound are definitly noiser and better. (Master Gain (Limiter) / Output Gaine -20db)
Thx for the hint with these app.
_Epix_ said:
Sorry for the noob question and if I'm posting at the wrong place. When you first install OOS 3.0 it's not rooted right? How do I root it? Thanks for the help.
Click to expand...
Click to collapse
How to root your phone. You find it in these guide
> http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568
Last time I used viper was the nexus 4 days almost 2 years ago... They have improved the audio (most likely new audio hardware on OP2) but yh it sounds a lot better then stock oxygenOS 3 it does the job till Maxxaudio is back
MaxtremePL said:
Divine Beats by Royal Seeker (DolbyDigital+ version) located at:
http://theroyalseeker.github.io/
In order for this mod to work you need permissive SElinux
Click to expand...
Click to collapse
Thank you soooo much! This did the trick. I was so frustrated with the MM update until you saved my ears with this suggestion. :good:
_Epix_ said:
Sorry for the noob question and if I'm posting at the wrong place. When you first install OOS 3.0 it's not rooted right? How do I root it? Thanks for the help.
Click to expand...
Click to collapse
If you flashed OOS 3, it is highly likely that the build was not a pre-rooted build. To root follow this guide at this link :
http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568
anees167 said:
Last time I used viper was the nexus 4 days almost 2 years ago... They have improved the audio (most likely new audio hardware on OP2) but yh it sounds a lot better then stock oxygenOS 3 it does the job till Maxxaudio is back
Click to expand...
Click to collapse
Actually V4A can be tweaked to sound better than MaxxAudio. Try XtremeMUSIC mod by androidexpert35. It includes V4A as an addon.
Link to the above mod is here: http://forum.xda-developers.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951
&roid said:
Thank you soooo much! This did the trick. I was so frustrated with the MM update until you saved my ears with this suggestion. :good:
Click to expand...
Click to collapse
Try XtremeMUSIC mod. Link: http://forum.xda-developers.com/android/software/mod-beatsaudio-e-xloud-installer-t3029951
OnePlus seems to have enabled aptX codecs in the new OB5/14 for the OnePlus 3/T.
For those of you who don't want to wait until the stable release and also would rather not flash the open beta, @Chaosgod27 has extracted the related files for use in the stable release. These files can be placed within OOS 4.1.X to enable aptX mode. These files are different from the old aptX-enabling files that were broken in OOS since updating to 7.1.1.
Edit: It seems there's some issues with the stacks. Playback does use aptX, but music is playing at a slightly higher pitch and faster than it should be.
I've dug around through the files in the new open beta and found the files myself. It seems there were a few missing before. The issue with the raised pitch and fast playback should be gone now.
Flashable Zip (through custom recovery, does not require Magisk): View attachment 4121507
Magisk Module (same thing, just systemless): View attachment 4121508
There was an issue before with some missing files that caused playback to run too fast and with a higher pitch. That has been fixed now. If anyone flashed the old Magisk module, I would advise you to download the new one in the OP and flash over it. I've also included a flashable zip for those of you who aren't using Magisk.
Anova's Origin said:
There was an issue before with some missing files that caused playback to run too fast and with a higher pitch. That has been fixed now. If anyone flashed the old Magisk module, I would advise you to download the new one in the OP and flash over it. I've also included a flashable zip for those of you who aren't using Magisk.
Click to expand...
Click to collapse
Thanks a million
Thank you, I have installed it but it seems to have a lot more problems (noise/cracking as in packets lost or something) than the previous version that I was using and which I got from here:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
Is there any way to uninstall this version and return to "old default" (from where I can get back to the aptx version from above)?
xclub_101 said:
Thank you, I have installed it but it seems to have a lot more problems (noise/cracking as in packets lost or something) than the previous version that I was using and which I got from here:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
Is there any way to uninstall this version and return to "old default" (from where I can get back to the aptx version from above)?
Click to expand...
Click to collapse
If you used the Magisk module, simply delete the module and reboot.
If you flashed the regular zip, you'll have to dirty flash your ROM to restore to default.
Hi @Anova's Origin, how do i know if this mod is working or not?
Vixiebalistic said:
Hi @Anova's Origin, how do i know if this mod is working or not?
Click to expand...
Click to collapse
Use a logcat app (Catlog / Matlog) and search for an aptx entry in the recorded logs after you connected your aptx capable device via Bluetooth to your aptx enabled phone...
You should be able to find something if it's working, otherwise it wouldn't show any aptx entry
Sent from my OnePlus3T using XDA Labs
Edit 2: Nevermind, it's working now. Idk what the problem was.
Didn't work for me on OOS 4.1.6 on Oneplus 3T I can't turn on Bluetooth. Anyone else having this problem? Also, have the drivers been updated in a newer OB?
Edit: I am using magisk v13.3
vini2710 said:
Didn't work for me on OOS 4.1.6 on Oneplus 3T I can't turn on Bluetooth. Anyone else having this problem? Also, have the drivers been updated in a newer OB?
Click to expand...
Click to collapse
Nope... Working fine here with op3t 4.1.6. Did u make back up before flashing?
Vixiebalistic said:
Nope... Working fine here with op3t 4.1.6. Did u make back up before flashing?
Click to expand...
Click to collapse
I used magisk so no worries (v13.3)
Edit: It's working. Yay! Thank you for the good work with this module!
how about op3T 4.1.7? Is it work?
qwealan said:
how about op3T 4.1.7? Is it work?
Click to expand...
Click to collapse
It works flawlessly for me on OOS 4.1.7 on my op3t
Sent from my ONEPLUS A3003 using Tapatalk
Anyone, test Magisk module with lineageOS Rom ?
vinicentus said:
It works flawlessly for me on OOS 4.1.7 on my op3t
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I use Magisk Module on OOS4.1.7 but i cant use aptX (use catlog search "aptx" ). are you use zip flash or use Magisk too?
qwealan said:
I use Magisk Module on OOS4.1.7 but i cant use aptX (use catlog search "aptx" ). are you use zip flash or use Magisk too?
Click to expand...
Click to collapse
I am using magisk (v14)
Working on OP3T with OOS 4.5.1 + Magisk 14.0. Those libs where updated to show battery for devices in OB15, update needed.
Thanks very much! Looking for this about a week long and finally solved
My device is OP3T, with H2OS V3.5 stable, no magisk
can I share this to oneplusbbs.com?
ABOUT
This flashable zip is to help those who want stock audio of OxygenOS in custom ROM
REQUIREMENT
-TWRP
INSTALLATION
-Reboot to recovery
-Flash zip file
-Enjoy and press thanks
DOWNLOADS
HERE
CREDITS
mattsby for the audio template
ungeeked for constant motivation and always answer my stupid questions lol
dheeraj (dhlalit11) for helping me
rkrohan for giving me hope
ravish_919 for being my tester
Version Information
Status: Stable
Last edited: 11/3/2018
Created 15/5/2017
CHANGELOG
OxygenOS Audio
15/5/2017 -- V1.0 -- Initial release
16/5/2017 -- V1.7 -- Now you don't need to delete audio folders manually + permission fixed
14/10/2017 -- V2.0 -- Added OnePlus 5 audio
4/2/2018 -- V3.0 -- Added Open Beta 31/22 audio from OnePlus 3/T
11/3/2018 -- V3.1 -- Fixed flashing issue
Click to expand...
Click to collapse
Samsung Galaxy S8 Audio
20/5/2017 -- V1.0 -- Stock Audio Samsung Galaxy S8 released
Click to expand...
Click to collapse
LG G6 Audio
28/5/2017 -- V1.0 -- Stock Audio LG G6 released
8/6/2017 -- V2.0 -- Renamed files in Stock Audio LG G6
Click to expand...
Click to collapse
Reserved 2
Nice but for what need this? Every Custom Rom have Audio.
Schrotty35 said:
Nice but for what need this? Every Custom Rom have Audio.
Click to expand...
Click to collapse
This is just for those who prefers OxygenOS audio instead of custom ROM
DragonSlayer240 said:
ABOUT
This flashable zip is to help those who want stock audio of OxygenOS in custom ROM
REQUIREMENT
-Root is pre-requisite
-Root explorer e.g. Solid Explorer
-TWRP
INSTALLATION
-Open Solid Explorer and grant root
-Go to root/system/media
-Delete audio folder
-Reboot to recovery
-Flash zip file
-Enjoy and press thanks
DOWNLOADS
HERE
CREDITS
@mattsby for the audio template
@ungeeked for constant motivation and always answer my stupid questions lol
@dheeraj (dhlalit11) for helping me
@rkrohan for giving me hope
Version Information
Status: Stable
Created 15-5-2017
Click to expand...
Click to collapse
wow!!! cool, awesome!!! thanks.
---------- Post added at 09:49 ---------- Previous post was at 09:46 ----------
Schrotty35 said:
Nice but for what need this? Every Custom Rom have Audio.
Click to expand...
Click to collapse
i think is the all media sound from oos, is it right?
notification,ringston, ui...
spaziomilano said:
wow!!! cool, awesome!!! thanks.
Click to expand...
Click to collapse
Thanks for supporting!
spaziomilano said:
i think is the all media sound from oos, is it right?
notification,ringston, ui...
Click to expand...
Click to collapse
yep it is
DragonSlayer240 said:
Thanks for supporting!
yep it is
Click to expand...
Click to collapse
Awesome, I'm always on RR and always put manually different sounds from OOS... with your work it's so simple now[emoji5]
Envoyé de mon ONEPLUS A3000 en utilisant Tapatalk
thank you mate
Sent from my ONEPLUS A3000
escorpion_sw said:
thank you mate
Sent from my ONEPLUS A3000
Click to expand...
Click to collapse
sure no prob haha
spaziomilano said:
Awesome, I'm always on RR and always put manually different sounds from OOS... with your work it's so simple now[emoji5]
Envoyé de mon ONEPLUS A3000 en utilisant Tapatalk
Click to expand...
Click to collapse
Haha sure no prob... I also always had to do it every time I flash another ROM or dirty flash the same ROM... Thanks God I'm not the only one who needed this haha
DragonSlayer240 said:
Haha sure no prob... I also always had to do it every time I flash another ROM or dirty flash the same ROM... Thanks God I'm not the only one who needed this haha
Click to expand...
Click to collapse
Please move this to the themes, apps, and mods section please. Doesn't belong here.
good job OP this will come in handy
dzimr said:
good job OP this will come in handy
Click to expand...
Click to collapse
Thanks!
@DragonSlayer240 Hi! There is an easier way of deleting the file. Just put the names of the audio files or whole recovery in updater-script.
Here you have a documentation: https://source.android.com/devices/tech/ota/inside_packages
You should focus on delete and delete and delete_recursive. After deleting these files use package_extract_dir to extract your /system and set_metadata_recursive to fix the permissions.
It's really easy and users of your mod wouldn't have to use Solid Explorer etc.
Stock Audio V1.7
New update guys! Stock Audio V1.7 is up
Now you don't need to delete audio folders manually
Fixed permission
Click to expand...
Click to collapse
Thanks ungeeked , ravish_919 and eagleeyetom for helping
DragonSlayer240 said:
New update guys! Stock Audio V1.7
Thanks @ungeeked , @ravish_919 and @eagleeyetom for helping
Click to expand...
Click to collapse
Awesome!!! It just simplified my installation of Remix Resurection with OOS audio. thanks:fingers-crossed:
spaziomilano said:
Awesome!!! It just simplified my installation of Remix Resurection with OOS audio. thanks:fingers-crossed:
Click to expand...
Click to collapse
Haha no prob! Glad I could help you
Does it works only on 3T or for other devices also??
Sent from my YU Yureka using XDA Labs
Has anyone gotten Viper4Android working on their Galaxy S9+ yet? If so, on which ROM or OS version?
UPDATE: I've found that this version of ARISE works perfectly on my S9+, here are my working arise_customize.prop settings:
I installed this over a ROM using Magisk, so I made sure to include the core and the magiskcompatibility module first.
I then selected ViPER4Arise 2.5.0.5, and didn't install anything else.
Yes, it is working great on LightROM on my S9+
VICosPhi said:
Yes, it is working great on LightROM on my S9+
Click to expand...
Click to collapse
I see LightROM includes Dolby Atmos, did it also then include v4a or did you flash a specific v4a package?
I flashed the V4A zip file via TWRP that I had downloaded from one of the S8 forums when I had S8 and it worked fine
VICosPhi said:
I flashed the V4A zip file via TWRP that I had downloaded from one of the S8 forums when I had S8 and it worked fine
Click to expand...
Click to collapse
Slick, thanks man! I'll give that a shot, I still have the Arise installer that used for my S8 myself so I'll see if that takes
Sent from my Galaxy S8 using XDA Labs
benmeroff said:
Slick, thanks man! I'll give that a shot, I still have the Arise installer that used for my S8 myself so I'll see if that takes
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
Yes that was it, the ARISE package. It works
Sent from my SM-G965U1 using Tapatalk
Hi
I have good sound with viper ?
I use version for magisk and is not good. Volume is poor
Its possible To give me one link of your viper ?
Thanks
VICosPhi said:
Yes that was it, the ARISE package. It works
Click to expand...
Click to collapse
So I've tried using the ARISE Magnum Opus 20170724 installer I had, but on any stock-based ROM it just bootloops the system. Which one works for you? I can see now I was several ARISE versions behind but would prefer not spend time waiting for my rather sizeable Nandroid to restore between testing versions if at all possible lol...
Sent from my Galaxy S8 using XDA Labs
I haven't tried it on stock yet. Maybe try a custom kernel first then try flashing it.
Sent from my SM-G965U1 using Tapatalk
It would be amazing if we could figure out which version of Viper works on the S9+ and maybe some simple steps..
babyboy3265 said:
It would be amazing if we could figure out which version of Viper works on the S9+ and maybe some simple steps..
Click to expand...
Click to collapse
benmeroff said:
Has anyone gotten Viper4Android working on their Galaxy S9+ yet? If so, on which ROM or OS version?
UPDATE: I've found that this version of ARISE works perfectly on my S9+, here are my working arise_customize.prop settings:
I installed this over a ROM using Magisk, so I made sure to include the core and the magiskcompatibility module first.
I then selected ViPER4Arise 2.5.0.5, and didn't install anything else.
Click to expand...
Click to collapse
Sent from my Galaxy S8 using XDA Labs
benmeroff said:
So I've tried using the ARISE Magnum Opus 20170724 installer I had, but on any stock-based ROM it just bootloops the system. Which one works for you? I can see now I was several ARISE versions behind but would prefer not spend time waiting for my rather sizeable Nandroid to restore between testing versions if at all possible lol...
Sent from my Galaxy S8 using XDA Labs
Click to expand...
Click to collapse
i find flashing (smeejaytee - feelthebeats toolbox) from (ARISE+Deuteronomy+2.94+Modular+AROMA) fixes 9/10 issues faced after the magnum opus installation,
ive been using this method for a while now and not really had any problems, just a long winded process installing it all but havnt found A simpler method yet, hope this helps
Which versions of viper did you install? I have a lg g7 with snapdragon 845th in the magisk modules occur again and again sound problems with the volume. as described by a user here in the thread.
Sony92 said:
Which versions of viper did you install? I have a lg g7 with snapdragon 845th in the magisk modules occur again and again sound problems with the volume. as described by a user here in the thread.
Click to expand...
Click to collapse
I just tried flashing this and made sure to install the FeelTheBeats script that YZFR90 recommended in the Aroma installer, and after rebooting and disabling SELinux within Viper4Android settings (after enabling developer mode) it works perfectly for me on Magisk so far.
YZFR90 said:
i find flashing (smeejaytee - feelthebeats toolbox) from (ARISE+Deuteronomy+2.94+Modular+AROMA) fixes 9/10 issues faced after the magnum opus installation
Click to expand...
Click to collapse
OK thanks. because with the viper modules directly from magisk, i only have problems of sound and volume
install the zhuhang version via magisk
that is all
exocetdj said:
install the zhuhang version via magisk
that is all
Click to expand...
Click to collapse
I have only the problems with the volume and the bad quality.
benmeroff said:
I just tried flashing this and made sure to install the FeelTheBeats script that YZFR90 recommended in the Aroma installer, and after rebooting and disabling SELinux within Viper4Android settings (after enabling developer mode) it works perfectly for me on Magisk so far.
Click to expand...
Click to collapse
its not working.
the viper4arise apk crashes
Sony92 said:
its not working.
the viper4arise apk crashes
Click to expand...
Click to collapse
If you haven't already, I'd make sure any other V4A Magisk modules or APKs are all uninstalled, then try reinstalling just that ZIP.
Sent from my Galaxy S9+ using XDA Labs
Installation fails. ends with error 2xx
It may be that viper is not completely compatible with the snapdragon. I'm really restless. have already tried several versions
Update: NFC payments has been fixed in Los 17.1 (and probably in all other ROMs) so this module is no longer required.
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
Click to expand...
Click to collapse
Havoc OS added it in the latest build (20202602) too I think in the future all ROMs will include the fix from NOS sources.
Thanks to NOS devs and to you guys! :good:
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
Click to expand...
Click to collapse
Great! But... Where is the module?
mvalda01 said:
Great! But... Where is the module?
Click to expand...
Click to collapse
Lol!
I accidentally created a duplicate thread and the attachment was in the other thread.
I've now added to the OP.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24[/QUOTE
Hai bill,
I have problem with NFC. Now iam using Havoc OS 10 v3.3 QQ2A.200305.003.
So i just flash this patch via twrp for problem solving?
I use redwolf recovery, is it possible to flash this module? And do I have to install the magisk before or can I install this module without the magisk?
Click to expand...
Click to collapse
uutucherenz said:
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24[/QUOTE
Hai bill,
I have problem with NFC. Now iam using Havoc OS 10 v3.3 QQ2A.200305.003.
So i just flash this patch via twrp for problem solving?
I use redwolf recovery, is it possible to flash this module? And do I have to install the magisk before or can I install this module without the magisk?
Click to expand...
Click to collapse
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Click to expand...
Click to collapse
Can you recommend a forum to discuss lineage on oneplus3 / 3T? And the link to download ROM Lineage OS?
Click to expand...
Click to collapse
uutucherenz said:
Can you recommend a forum to discuss lineage on oneplus3 / 3T? And the link to download ROM Lineage OS?
Click to expand...
Click to collapse
Check out the threads in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development and make sure you read the first post (OP - original post) in the thread your interested in.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Click to expand...
Click to collapse
Hai bill,
What are the steps to install this NFC patch fix? I tried to install it directly via redwolf recovery but failed, "error: 1" ...
Click to expand...
Click to collapse
uutucherenz said:
BillGoss said:
Hai bill,
What are the steps to install this NFC patch fix? I tried to install it directly via redwolf recovery but failed, "error: 1" ...
Click to expand...
Click to collapse
I've always flashed it using the TWRP mentioned in the OP of the Los 17.1 thread (aka SAR TWRP) https://forum.xda-developers.com/on...ageos-17-0-oneplus-3-3t-t3990061/post80652281
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
FWIW, definitely don't flash this on top of an LOS ROM; caused a bootloop for me that I couldn't get out of, had to clean wipe and start over. My own darn fault for not reading everything through the first time or making a backup first, just a warning for others :silly:
Click to expand...
Click to collapse
Joshmccullough said:
BillGoss said:
FWIW, definitely don't flash this on top of an LOS ROM; caused a bootloop for me that I couldn't get out of, had to clean wipe and start over. My own darn fault for not reading everything through the first time or making a backup first, just a warning for others :silly:
Click to expand...
Click to collapse
I've updated the OP to say that the module is no longer needed.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse