Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Also fellow S22U Snapdragon owner here (S908N). I've been seeing you around the threads as I am also trying to get Viper working on this thing. Hope you find a way to get it working, I hope you'll share the steps if you can make it work. Best of luck.
If you want an accelerated progress you might have to put a bounty on this.
ffp. said:
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Click to expand...
Click to collapse
Okay, I got JamesDSP working now. Had to install AML, and then install JameDSP with the Huawei installation method. I'm gonna try to flash Viper on see if that does anything.
Fireburito said:
Okay, I got JamesDSP working now. Had to install AML, and then install JameDSP with the Huawei installation method. I'm gonna try to flash Viper on see if that does anything.
Click to expand...
Click to collapse
I tried that too. I can get Jamesdsp to work, but it is way inferior to V4A. At least I couldn't get a good bass from it.
I know several other users that want that too. It would be nice to have someone who knows the working of V4A to help or at least a S21 SD owner to share his files and codes, maybe we can copy them.
What you mean by bounty? I ambwilling to try anything for this to work and I will not stop until we make it. The main reason I rooted this damn thing was to get V4A.
ffp. said:
I tried that too. I can get Jamesdsp to work, but it is way inferior to V4A. At least I couldn't get a good bass from it.
I know several other users that want that too. It would be nice to have someone who knows the working of V4A to help or at least a S21 SD owner to share his files and codes, maybe we can copy them.
What you mean by bounty? I ambwilling to try anything for this to work and I will not stop until we make it. The main reason I rooted this damn thing was to get V4A.
Click to expand...
Click to collapse
Yeah, before I couldn't even get JamesDSP to work, so just having it now as some form sound mod is semi-okay. I'm trying to use that to piggyback off to install Viper, but to no avail.
I think it's something with the Huawei install method that got it working ? As installing with the normal method before just made the app crash. The module files in JamesDSP correctly targeted the sku-taro folders too, unlike Viper.
A bounty is basically you post a reward amount to any dev that can get Viper working on our SD S22U, it will at least get some experienced and knowledgeable people onboard trying to figure it out instead of us grasping at straws.
Fireburito said:
Yeah, before I couldn't even get JamesDSP to work, so just having it now as some form sound mod is semi-okay. I'm trying to use that to piggyback off to install Viper, but to no avail.
I think it's something with the Huawei install method that got it working ? As installing with the normal method before just made the app crash. The module files in JamesDSP correctly targeted the sku-taro folders too, unlike Viper.
A bounty is basically you post a reward amount to any dev that can get Viper working on our SD S22U, it will at least get some experienced and knowledgeable people onboard trying to figure it out instead of us grasping at straws.
Click to expand...
Click to collapse
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.
ffp. said:
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.
Click to expand...
Click to collapse
No idea tbh, I saw one guy post a bounty to get viper working on snapdragon s21 ultra, and it was claimed, but that was mostly it. I don't participate in these forums much so don't know about the specifics.
I have seen a few posts about snapdragon S21U with viper on one ui 4, but whatever methods they were using didn't work on s22u iirc, probably because those phones started with android 10, 11, whilst S22U is android 12 out of the box.
ffp. said:
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Click to expand...
Click to collapse
Well did you figure it out?
ffp. said:
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Click to expand...
Click to collapse
All that you should need is root, your device set to permissive mode, install V4A and let it install the drivers when it prompts you the first time you open V4A(grant V4A superuser/root permissions).
Can you confirm that you are properly rooted with correct permissions and r/w properly set?
Can you confirm your device is actually in permissive mode?
I will add that you could also use Wavelet
Wavelet: headphone specific EQ - Apps on Google Play
Headphone specific equalization with lots of customizability
play.google.com
Made by the same developer whom made Viper4Android. There are reports saying It provides the same level of quality.
Droidriven said:
All that you should need is root, your device set to permissive mode, install V4A and let it install the drivers when it prompts you the first time you open V4A(grant V4A superuser/root permissions).
Can you confirm that you are properly rooted with correct permissions and r/w properly set?
Can you confirm your device is actually in permissive mode?
Click to expand...
Click to collapse
Yes, i have root, however S22U do not havr system rw. I can change things via magisk, though.
No, i didn't manage to get it to work. I'm using james dsp, which is pretty good if correctly set.
I had custom kernel (obligated, to have unofficial TWRP installed) with SElinux permissive mode permanently - V4A still did not work on my s22u model S908E (snapdragon; stock A12) - Kept getting driver install loop everytime I opened V4A app.
According to Dr. Ketan (see link message), V4A will not work on s22u Snapdragon models regardless of SElinux being permissive or enforcing.
Awaiting new development/ resurrection of this beloved sound Mod (s22u speakers suck, coming from a buttery smooth ROG-3).
GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX
Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.
github.com
Fytdyh said:
I will add that you could also use Wavelet
Wavelet: headphone specific EQ - Apps on Google Play
Headphone specific equalization with lots of customizability
play.google.com
Made by the same developer whom made Viper4Android. There are reports saying It provides the same level of quality.
Click to expand...
Click to collapse
they didnt make viper for Android. He had no part in the development of the so driver that makes the sound change. Viper520 did and I still dont understand why he walked away and has never came back. Dewitt just made some changes to the apk file. I can assure you he hasnt got a clue on how to make a sound driver. Technically james dsp is a so file sound driver that he did make.
I have a new tab s8 plus on one ui 4.1.1 right now and I can't believe viper wont work with a permissive kernel even. I like you guys got jamesdsp to work by installing as Huawei device and thought maybe that would correct the problem with viper and it didnt.
I do believe system RW would make the difference and I know the developer for the S8 tablet is working on making a twrp and a rw file that will work on that. I thought the s22 ultra was able to make RW now with the RW file. You would have to find the twrp tab s8, s8+, s8 ultra thread and go onto their telegram where DR. Keaton also hangs out and see if it works on the s22 ultra because its working on some devices. I was thinking s22 ultra and fold 4. I don't know how long until the tab s8 will have it and I hope you guys read this look into and try it and get viper4android working. So god speed
James dsp installs a lib64 driver into the system when you use Huawei setting. Normally the sound driver installs in the lib folder instead. I dont think its possible with viper
Huawei install
/data/adb/modules/ainur_jamesdsp/system/vendor/lib64/soundfx/libjamesdsp.so
Normal install
/data/adb/modules/ainur_jamesdsp/system/vendor/lib/soundfx/libjamesdsp.so
I do believe system RW will allow viper to work
Im almost 95 percent sure s
ffp. said:
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.
Click to expand...
Click to collapse
Have you made your system read/write yet? Im 95 percent certain that the problem. Im on android 13 on my poco f3 and now viper wont install and it says Error Could not mount system read write s22 ultra is able to be rw with Dr. Keaton's stuf I believe
It worked?
amar100 said:
It worked?
Click to expand...
Click to collapse
I couldn't figure it out you want to try mine?
amar100 said:
It worked?
Click to expand...
Click to collapse
What device do you have any details please
ScarletWizard said:
The 64 bit version of viper has been released. If you're on Android 13 on a 74 bit soc. You gonna need the new v4a 64
Click to expand...
Click to collapse
What are you talking about? Where's the 64bit version
Yes
Techguy777 said:
I couldn't figure it out you want to try mine?
Click to expand...
Click to collapse
Yes Pls
Related
Here is a complete guide on how to get V4A stock and V4A Sony Beats Edition working on your Samsung Galaxy S7 Device. Please note I have tested this personally on my own S7 Edge SM-G935F and it is working 100%. There was a few bumps along the way to get everything working and if it wasn’t for @guitardedhero help and everyone else involved I wouldn’t have figured it out. There were similar tutorials HERE and HERE that offered some insight but didn' provide a fully working procedure so I put together my own guide that will work for sure.
You will need a rooted device for this to work (SuperSU by @Chainfire CF-AUTO-ROOT) and a working recovery TWRP version 3.0.0 or above found HERE
As usual please backup all your data and files (internal and external SD cards) as mistakes can be made and things don’t always go as planned
0. In your SuperSU app go to setting and deselect/un-tick “Mount namespace separation” (this is causing issues with the installation process on this and other devices)
1. Install BusyBox by Stephen (Stericson) with the default settings of /su/xbin
2. Install the latest version of Viper4Android (currently 2.4.0.1) from the official website - LINK or if you prefer use the older version as it has been favored for providing better quality. (Do not open just yet, only install)
2.3.4.0 with its Super Quality driver is absolutely superior to 2.4.0.1 and its driver in every aspect, it's almost not even fair. I promise you, this build will absolutely blow your mind, especially when used with the ViPER|Audio™ Audiophile™ 4.0 Profile @guitardedhero
3. Make sure Viper4Android has write permissions (this should be on as default but check just in case) Settings -> Applications -> Application manager -> V4A -> Permissions -> and make sure all available options are enabled.
4. Freeze the stock Sound Alive or Adapt Sound app using Titanium Backup.
5. Open up Root Explorer (or your preferred root browser) and change the system to MOUNT R/W
6. Go to root/system/etc/ and rename the file audio_effect.conf to audio_effect.conf.backup
7. Download the modified audio_effect.conf from HERE and copy it to /system/etc/ and /vendor/etc/
(This last location will have no files, it may be skipped?)
8. Set permissions of the new files to rw-r-r (0644) (important! Or you may have boot loops)
9. Change your system back to MOUNT R/O and exit.
8. Restart your device in recovery and flash THIS FILE HERE and reboot (I didn’t perform any wipes)
9. Once your device reboots, open up V4A and grant root permissions and install the requested drivers.
10. Reboot once again and this should be it…
You should now have V4A working on your device
If you feel the stock V4A isn’t giving you the correct audio niche or experience then consider changing to ViPER|Atmos™ 4.8.1 Sony™ Beats™ Edition by @guitardedhero – (I have not tested other editions found here on the OP Thread, they may or may not work… any volunteers ??? )
FLASH THIS FILE TO GET STARTED ViPERAtmos 4.8.1 Sony Beats Driverless.zip
Once your phone reboot you will have a new looking V4A icon and upon opening it should work but your Dolby Atmos app will keep crashing until you FLASH THIS FILE dap_r6.5.zip - Fresh Dolby Atmos App file.
And here is a quick guide written by @guitardedhero to enable the Audiophile profiles...
I don't recommend others to flash without an acceptable backup to restore as this build drops compatibility big time for some devices resulting in no in-call volume for example. It is the custom version I built for my Nexus 6 ViPER|Atmos™ Audiophile™ rom and is just absolutely incredible!
Post-install instructions:
In v4a:
Menu > Show Notification (disable through notification shade if you wish)
Menu > Ui Setting > Expert
Menu > Save Effect Profile > As New Effect > Stock
Download and extract ViPERAudio Audiophile Profile 4.0 zip from the OP attachments section or HERE.
Search in:
/data/media/legacy/ViPER4Android/Profile
and
/storage/emulated/0/ViPER4Android/Profile
until you find the Stock folder you just saved earlier.
Take note that this is your working v4a directory.
Copy the Kernel and Profile folders in the ViPERAudio Audiophile folder you extracted earlier and paste them into the /ViPER4Android folder of your working v4a directory. Compare the folder and file permissions to the Stock folder and files and set them to the same permissions if necessary.
In v4a:
Menu > Load Effect Profile > Audiophile 4.0
Recommended Dolby Atmos™ Settings:
Music tab highlighted at the top
Open or Flat EQ preset
All three effects at the bottom turned Off except for Dialogue Enhancer if it sounds good to you.
Troubleshooting and additional steps will be written here shortly...
Please find all needed and extra files bellow...
REVISED - ViPERAudio_audio_policy_S7_Edge.zip has been added...
First! :highfive:
I've got one more goodie, provide me your stock /system/etc/audio_policy.conf and I'll provide ViPER4Android processing like you guys have never seen! (heard)
Fantastic tutorial from which many will certainly benefit! @themoto
Great job! :good:
guitardedhero said:
First! :highfive:
I've got one more goodie, provide me your stock /system/etc/audio_policy.conf and I'll provide ViPER4Android processing like you guys have never seen! (heard) :good:
Click to expand...
Click to collapse
ill post it shortly, still fixing up this guide and correcting everything...
GODSPD said:
ill post it shortly, still fixing up this guide and correcting everything...
Click to expand...
Click to collapse
:good:
find it bellow
guitardedhero said:
:good:
Click to expand...
Click to collapse
Here is my original file from the the Galaxy S7 Edge SM-G935F found inside the .rar file
GODSPD said:
Here is my original file from the the Galaxy S7 Edge SM-G935F found inside the .rar file
Click to expand...
Click to collapse
audio_policy.conf
guitardedhero said:
audio_policy.conf
Click to expand...
Click to collapse
my mistake, here is the right file...
GODSPD said:
my mistake, here is the right file...
Click to expand...
Click to collapse
Here you go, friend!
Feel free to add this to your OP, a flashable audio_policy for you and your friends! :good:
Thanks! 2 questions..
1) what's the battery drain like compared to without v4a?
2) how do we fully revert back to stock and remove v4a?
Thanks for this guide, kinda got stuck at step 5 though, couldn't figure out how to mount r/w using es file explorer with root? When I tried to change the filename of audio_effects.conf it said task failed which is because I didn't mount r/w I assume
You made my day man
2.3.4.0 is way better than 2.3.4.1 by miles.
I have GS5 besides my 7 edge and the reason i kept it around is the sound quality, i always favored it to listen to music over my 7 edge and just figured out the reason; 2.3.4.0 is installed on my GS5.
GS5 -----> drewer
Sent from my SM-G935F using Tapatalk
GODSPD said:
ill post it shortly, still fixing up this guide and correcting everything...
Click to expand...
Click to collapse
Is there any difference between your thread and this one ?
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
I see you've linked the other 2 posts in your op. It may have been better to just include the additional information in that thread, only a suggestion
sawdoctor said:
Is there any difference between your thread and this one ?
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
I see you've linked the other 2 posts in your op. It may have been better to just include the additional information in that thread, only a suggestion
Click to expand...
Click to collapse
the op had added some profile and kernel for v4a. and also dolby atoms
relax24 said:
Thanks! 2 questions..
1) what's the battery drain like compared to without v4a?
2) how do we fully revert back to stock and remove v4a?
Click to expand...
Click to collapse
1) Battery drain - I haven't noticed any significant changes on my device
2) If you install the apk just uninstall it and unfreeze your Sound Alive
3) and undo any changes
sawdoctor said:
Is there any difference between your thread and this one ?
http://forum.xda-developers.com/s7-edge/how-to/guide-viper4android-enforcing-stock-t3337148
I see you've linked the other 2 posts in your op. It may have been better to just include the additional information in that thread, only a suggestion
Click to expand...
Click to collapse
The first guide didn't provide a fully working method, try it and it will keep asking you to reinstall drivers, the second was designed for the S6 and provided a different method, here it is covered 101% plus additional sound mods, profiles, Atmos, and much more.
GODSPD said:
The first guide didn't provide a fully working method, try it and it will keep asking you to reinstall drivers, the second was designed for the S6 and provided a different method, here it is covered 101% plus additional sound mods, profiles, Atmos, and much more.
Click to expand...
Click to collapse
No problem thank you for your reply??
Sent from my SM-N920C using Tapatalk
hookguy said:
Thanks for this guide, kinda got stuck at step 5 though, couldn't figure out how to mount r/w using es file explorer with root? When I tried to change the filename of audio_effects.conf it said task failed which is because I didn't mount r/w I assume
Click to expand...
Click to collapse
just try it with root explorer app from the store, the second you open it it has that option displayed in the top right hand corner, you cant miss it...
Any reason why the audio sounds high pitched/faster after installation?
El Maestro said:
You made my day man
2.3.4.0 is way better than 2.3.4.1 by miles.
I have GS5 besides my 7 edge and the reason i kept it around is the sound quality, i always favored it to listen to music over my 7 edge and just figured out the reason; 2.3.4.0 is installed on my GS5.
GS5 -----> drewer
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
How did you install 2.3.4.0?
When I download the zip I can't flash it, and It is not possible to install the apk's inside it either
This is a flashable zip that enables init.d scripts to run depending on the root method you have installed.
To uninstall, just flash the zip again and it'll restore everything to how it was before
If magisk:
Boot scripts will be installed that will run all exectuable scripts in init.d as post-fs-data except any that end in '-ls' which will be run as late start. Also note that if you're trying to create the init.d folder, the original directory when using magisk is actually /sbin/.core/mirror/system/etc. It goes without saying that this could break safetynet (honestly though, just copy your script to /sbin/.core/img/.core/service.d or post-fs-data.d instead and set permissions to 0755 rather than creating an init.d directory - using the in-house magisk solution is always the better option. Magisk users have almost no reason to create an init.d directory)
The rest of this is for non-magisk/supersu installs
Otherwise: the boot img and part of the system will be modified to enable init.d support.
What it does:
Search for sysinit in any rc file. If found and seclabel is intact and equal to target seclabel for my init rc script, then that seclabel will be set to permissive in sepolicy if needbe instead of using my solution
If sysinit with seclabel isn't found, a custom rc file and system/bin/script file will be installed and sepolicy will be patched accordingly to add init.d support. Init.d scripts will be run the same way as with magisk installs above
Adds magiskpolicy to sbin. It's more up to date and complete than setools so why not?
If there is an error on unpacking your boot image, check the binary inclusion section here to see if your device needs one: https://github.com/osm0sis/AnyKernel3#-binary-inclusion
If it does, place it in addon/AnyKernel3/tools/arm (or x86 - whichever your architecture is - probably arm)
I am not responsible for any oddities that happen to your device because of this, use common sense. For example, if you know your device has a weird boot img, check first.
BACKUP BOOT AND SYSTEM PARTITIONS BEFORE FLASHING
Compatibility: Any device magisk is compatible with
Confirmed working (boot img method):
Nexus 5x
Verizon LG G2
Oneplus 3/3T
Oneplus 5T
Nexus 9
Redmi Note
Zuk Edge
Axon 7 (A2017U)
Nexus 5
SM-N900T
SM-T350
LeEco Pro 3
Confirm your device works and I'll add it to the list!
Special thanks to: @osm0sis, @CosmicDan, @Ricky Divjakovski, @JustArchi
Source: https://github.com/Zackptg5/Init.d-Injector
Download
Good stuff :good:
Good idea with the removal of other/old init.d capabilities. It's annoying that so many ROM's/kernels claim to have init.d but they're fake or hacky (well, I guess the sepolicy injection is pretty hacky too lol). You might also want to consider looking for install-recovery hijack method of init.d and disabling that too - shouldn't be too hard, just check if the file exists in known locations and grep for init.d. The harder part though is what to actually *do* if found - probably best to comment-out the line that contains "run-parts" and/or "init.d" rather than erase the whole file.
CosmicDan said:
Good stuff :good:
Good idea with the removal of other/old init.d capabilities. It's annoying that so many ROM's/kernels claim to have init.d but they're fake or hacky (well, I guess the sepolicy injection is pretty hacky too lol). You might also want to consider looking for install-recovery hijack method of init.d and disabling that too - shouldn't be too hard, just check if the file exists in known locations and grep for init.d. The harder part though is what to actually *do* if found - probably best to comment-out the line that contains "run-parts" and/or "init.d" rather than erase the whole file.
Click to expand...
Click to collapse
Good idea, I'll look into that. Thanks!
Will try this soon on Honor 8 Pro and report back.
Quick update to v1.1
Just bought a used nexus 9 and found that the boot partition layout for it and other nvidia tegra devices is different from typical android devices. So I added support for nvidia tegra devices
So github screwed with my EOL again and converted a few of the files to windows eol which broke everything. I just fixed it and reuploaded v1.1 with the fixes so just redownload it and flash away. Thanks to @dmgZero for finding the issue
Just updated to v1.2. I added support for pixels and nexus5x/6p avb-signing. I haven't been able to test it out myself as my bullhead doesn't even need signing to work so any feedback would be great. Also updated the OP on how to modify this for any weird boot imgs you may have
Edit: No point in spamming the thread with another post: updated to v1.3. Just adds capability to remove any init.d stuff present from install-recovery.sh. Thanks to @CosmicDan for pointing it out
Works fine on Redmi Note (a MediaTek Helio X20 device) running MIUI 9 (Android 6.0).
One tiny detail, maybe just do an mkdir /system/etc/init.d after the patch succeeds, if it doesn't already exist. I could imagine that some other zips could check for the existence of this folder for a simple way to determine if init.d is supported.
CosmicDan said:
Works fine on Redmi Note (a MediaTek Helio X20 device) running MIUI 9 (Android 6.0).
One tiny detail, maybe just do an mkdir /system/etc/init.d after the patch succeeds, if it doesn't already exist. I could imagine that some other zips could check for the existence of this folder for a simple way to determine if init.d is supported.
Click to expand...
Click to collapse
Sweet, I already have that in the sysinit script but it would make more sense to move that to the installer so I'll put that into the next version. Thanks!
Is that supposed to work systemlessly?
You should probably add Samsung to the weird/hexed/Satan kernels. Tried flashing your zip and recovery came back with Invalid Partition upon failure, my device is a Galaxy Note 5 running RR 7.1.2. I do love the idea and your work though bro. Thanks.
Metabolic12 said:
You should probably add Samsung to the weird/hexed/Satan kernels. Tried flashing your zip and recovery came back with Invalid Partition upon failure, my device is a Galaxy Note 5 running RR 7.1.2. I do love the idea and your work though bro. Thanks.
Click to expand...
Click to collapse
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
I completely understand, I wasn't gonna ask you to include my kernel regardless that's rather selfish, and I did follow your guide in the OP to get it to work. I was just suggesting maybe add Samsung kernels next to LG in your OP. Great work bro, thank you.
Zackptg5 said:
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
Click to expand...
Click to collapse
---------- Post added at 02:58 AM ---------- Previous post was at 02:51 AM ----------
I'm a retard, I read the OP wrong earlier. Disregard the adding Samsung part ha.
Zackptg5 said:
I tried to originally but it was basically impossible to detect all bootimg types and they need extract binaries which if I included them all, would make the zip over 70mb. I updated the op a few days ago with instructions on how to add support for weird boot imgs (it's basically adding a few files to the zip)
Click to expand...
Click to collapse
sscheib01 said:
Is that supposed to work systemlessly?
Click to expand...
Click to collapse
The boot img is not part of the system partition so that's systemless. However, it installs an addon.d script and modifies the sysinit and install_recovery files if present which are on the system. It won't break safetynet if that's what you're wondering
Zackptg5 said:
The boot img is not part of the system partition so that's systemless. However, it installs an addon.d script and modifies the sysinit and install_recovery files if present which are on the system. It won't break safetynet if that's what you're wondering
Click to expand...
Click to collapse
I thought *any* System modification trips the Safety net?
I use the Universal Safetynet Bypass module for Magisk so it doesn't bother me, but curious.
Sent from my Redmi Note 4 using Tapatalk
CosmicDan said:
I thought *any* System modification trips the Safety net?
I use the Universal Safetynet Bypass module for Magisk so it doesn't bother me, but curious.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
That's what I thought initially too but I've found lots of system modifications doesn't break safetynet such as editing the hosts file. Modifications to the zygote such as xposed framework for sure break safetynet but I'm not sure exactly which system modifications would. Other than testing them myself, I'm not really sure what would break it. I've found that you can completely alter parts of the system like with arise sound systems which adds a whole slew of libs and other modifications and safetynet still won't break (I found through my work there that having the system mounted as rw via a boot script will trigger safetynet but you can even go so far as to mount it as rw, make your changes, and then remount it as ro before boot completes and safetynet will still pass). It's weird man
Zackptg5 said:
That's what I thought initially too but I've found lots of system modifications doesn't break safetynet such as editing the hosts file. Modifications to the zygote such as xposed framework for sure break safetynet but I'm not sure exactly which system modifications would. Other than testing them myself, I'm not really sure what would break it. I've found that you can completely alter parts of the system like with arise sound systems which adds a whole slew of libs and other modifications and safetynet still won't break (I found through my work there that having the system mounted as rw via a boot script will trigger safetynet but you can even go so far as to mount it as rw, make your changes, and then remount it as ro before boot completes and safetynet will still pass). It's weird man
Click to expand...
Click to collapse
Kind of makes sense actually.
Hosts is in etc right, nothing in there is executable. So I imagine any changes to etc won't trip it because nothing in there would mess with device security. Sound mods... Well yeah they ADD libs but they don't replace any do they? They just add sound filters through the mixer configs in etc.
So I guess it makes sense. Sysinit is just added to xbin or whatever and I guess that doesn't trip it. But if you replaced, say, dex2oat with a proxy script to intercept oat generation, then it would definitely trip it.
Sent from my Redmi Note 4 using Tapatalk
Is it really needed??
I want to flash Dolby Atmos for Redmi Note 4, but init.d support is needed as mentioned by developer.
I tried Dolby Atmos without it sound is loud and great
I can't understand, why init.d is still needed?
Can anyone explain here?
amit.tiger12 said:
Is it really needed??
I want to flash Dolby Atmos for Redmi Note 4, but init.d support is needed as mentioned by developer.
I tried Dolby Atmos without it sound is loud and great
I can't understand, why init.d is still needed?
Can anyone explain here?
Click to expand...
Click to collapse
If it's working, then you don't need it or already have it. Init.d support is needed for Dolby if you are not using magisk or supersu and you have selinux set to enforcing
Zackptg5 said:
If it's working, then you don't need it or already have it. Init.d support is needed for Dolby if you are not using magisk or supersu and you have selinux set to enforcing
Click to expand...
Click to collapse
That's with respect to Dolby, what does it provide as a general point of view? What is it's significance?
Explain if you've enough time or just throw a link, it will help out.
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.
October release is available with or without root
Made a few changes as far as adding in some apk's to hopefully make it stable for everyone.
Besides that, the usual with normal default font BUT lots more choices in the font section.
Enjoy!
*if anyone has solid reasons to remove any apk files i've put back please let me know as some I should not have been removing and others... not so sure
I will no longer be able to provide new copies of this after the October security patch. I no longer own an A8 2018 and without a device to test the work, I do not feel it is appropriate to continue the project. I'd like to thank everyone that participated and I hope you enjoyed using it! If anything changes in the future that will allow me to provide the latest edited firmware, I will definitely be providing it here for you. I am using an S7 now so if you own one and like this work, there shall be downloads available there similar to this one. (Already testing).
Anyone that would like to continue on their own or have access to files used in making it I will try to include as much as possible from the link provided below by the end of October. There is currently a slightly outdated set of files and instructions (from June I believe) on how I made it already available.
Thanks Again!
Oct Security patch zip ready for download
Available with or without root AND with or without exo font - also an attempt to allow printing feature version. "Attempt" meaning I've placed a set of apk files into a separate and clearly labelled zip on the main download page that may allow proper use of the feature which has not been validated as operational by me or any other user. The "print fix" zip is rooted with exo font
This was made ONLY for the SM-A530W! Please do not use if not W (Canadian) variant. Check your phone info before attempting to flash
All ROMS/extras here:
https://drive.google.com/drive/folders/12Vwzn1CxNdT-ISsrOnSL4D353Nr14iRb?usp=sharing
The ROM will function very well and does not require any special patches, kernels, etc except obviously TWRP
Any additional issues you face with added mods most likely will need to be addressed with the creator
*Built by Superr's Kitchen*
Over 100 apps removed
***Find my mobile and pop-up asking to store lockscreen info removed- BE AWARE reduced ability to locate lost device!***
retro shutdown qmg
Overloaded notifications and ringtones
Oreo Weather (pie weather is a serious downgrade)
August Security release
FM tuner and App Lock (Next Radio may now be used starting from July 2019). Gee, THANKS SAMMY! What took you so long? Was it the polar bears?
Goofy selfie stickers that are funny... and creepy *big thanks to hadesRom genius Corsicanu for the find*
Other typical CSC changes
If your plan has wifi calling, turn it on/off once in phone settings to "break in" the qs tile
Dedicated Screen Recorder access in launcher with no shortcut style appearance (if deleted may be re-enabled with activity launcher as shortcut)
Chrome can be safely disabled at any time if desired and auto replaced with system webview
dm-verity + force encrypt already removed
Magisk rooted
Installation is easy as pie
BACK UP FIRST!
Wipe caches, data, system. Internal may be safely wiped and give the "freshest" install but is optional. Then flash away.
Once flash completes, just reboot.
-*Usage*-
You are free to use any ideas/changes included in the zip. In fact, I encourage you to do so. I've mostly pieced together work from other very difficult projects to create this. Nobody has asked me to add, remove or alter anything contained within this page or in shared downloads. Their work is everywhere and it's what made this possible.
Built with Superr's Kitchen
Some screens to sample below. yay
nobody home
empty
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Ok. I can't really suggest anything other than the obvious.
But you've let it boot once before trying, and are adding the apk as well after flashing magisk in twrp?
Hard to figure that one out. If you're using Magisk, i am assuming.
burnt_31 said:
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Click to expand...
Click to collapse
Have you tried 19.1 you may need to flash twice.
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
burnt_31 said:
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
Click to expand...
Click to collapse
I know exactly what you mean. I do it all the time.
Nice you got it going. It's pretty lame if you don't root this. I just cut it up and added a couple things and they can be taken out, except radio and the recorder.
Curious if i got it right. If you're on anything other than VMC, is call recording and other micro features working? All the cscfeature xml files are decrypted so you can see what was done.
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
burnt_31 said:
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
Click to expand...
Click to collapse
It is 168 hours no reboots and rmm did work that rmm was for Oreo.
I think his would be fine but no guarantees.
Custom kernel 2.0 flash twice.
Light rom works without issue make sure you flash magisk.
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
fabian_barrios said:
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
Click to expand...
Click to collapse
Yeah bud. If you unzip the attached file, you can place it in /system/priv-app/ and make sure the permissions are set correctly for the folder and apk. Compare with other apps in the directoty and make it the same.
Then get the activity launcher app from the play store. Use that to make a link for it.
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
boominboodhoo said:
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
Click to expand...
Click to collapse
okay thanks for that. It is probably from my csc edits. I can adjust for freedom and hope it makes a difference.
Anything else to mention about it? What you did before flashing, are you using latest twrp, root or non root.... anything at all
no-verity... favourite snack... p.i.n. number(s)... oops sorry not the last two. My mistake. TOO MUCH info. Disregard.
Do a search on xda for rooting your model for the correct version of twrp. U will need no verify no encript. I used the latest Magisk to root. Supersu did not work. I used twrp for the A8 plus and had problems. Get the right one. It's a great rom. https://www.google.com/amp/s/forum....ery-twrp-3-2-2-0-galaxy-a8-2018-t3818201/amp/
I am looking at the csc for FMC and it appears i have doubled an entry. I need to go over all of them to see if i've done it elsewhere. I will have 2 updated ones hopefully late tonight. (Takes forever to upload).
Not sure if that is the cause but i will definitely adjust it.
Quick question in regards to your Rom. I been using it for a while now. Its the best one I can find, I did post a few times at the start. By any chance, did u get adoptable storage working? I know Samsung removed it in Pie. I tried root essentials but still no luck. Thus is not my first time rooting or installing roms. I started with the HTC 1. Lol. So far, u have the best rom for the A8 2018. Its nice and clean. Almost compares with lineage in my opinion. Thanks again. And by the way, I am Canadian.
Thanks
Hey i appreciate the gesture but even though i "made" this, i did it because of other people. SuperR is an invaluable tool. Then you got magisk, the twrp recovery and heck even give ol' Sammy some credit, haha. All i did was spend time learning everything from this site. I can't stress that enough. I still have not paid for superR and i am going to see how i can right after this.
ANYWAY!
Your question. I've never attempted it but i am very certain there's a magisk module that'll do it.
It involved formatting sd to ext 4 or 3. So i will get on it. Got a few 64 gig cards to spare. If you have a computer, grab the superR linux distro. I've run it on 32 bit machines. K... pay superr... adopt a card heheh.
I will look again in the magisk module section. And I give everybody right now credit for all their hard work and sharing it amongst all of us. Thank you. Thank you. I love modding my phones and I could not do it without everybody's help. All my PC's are 64bit.
Nice. If you need any help just ask. Just bought the kitchen.
I'll have something very soon. Mexico's pie has the classic csc folder of old. I think we should unify with some fiesta pie zip ui sorta thingy... um rom.
I don't know if this is the right place to ask or if it already has been or not, but is there any possible way to get 32 bit apps to run in some type of compatibility mode or something like that? For the most part the majority of my old apps came over from my old phone, however there are some apps I have and used regularly which are not compatable with this phone and I am not sure if the developers are still active or not. I'm assuming the answer is no, or would require root if it were possible and rooting is out of the question for me because I have Verizon. I am expecting to be SOL but figured it was worth asking about here.
This question has been asked and discussed in length, try search
I will not be rude and the short answer is no. Apps on the play store had roughly 2 years to switch 64 bit. For s**ts and giggles I did try to do a search with zero results.
If the devs are still active and they havn't updated to 64bit by now then they are a lost cause.
No Google's heads up to devs gave them ample amounts of time to switch all their apps from 32bit over to 64bit. Tough shiz if the devs didn't take the arning seriously and switched their apps over whenthey had the cance to do so. I'm genuinely curious of 32bit compatibility is a concern and/or a necessity for you why you would buy a smartphone that doesn't support it? I really don't see how that makes much sense when you could have chose from a lot of other new flagships with 32bit support in tact.
Get a Galaxy S22 Ultra, Motorola Edge 30 Ultra or OnePlus 10 Pro. It's likely next year's flagships of any brand will be 64 bit only, so the forced shift is coming.
I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.
I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there would be a way around it but obviously not.
This might be of some help to run 32 bit apps you want:
GitHub - ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com
Interesting I will have to check this out
Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (
I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo.
VergeDX said:
Not working for my Pixel 7 Pro, version 13 (TD1A.221105.001) : (
I dirty flash patched init_boot.img, and replace Magisk app to initial version of that repo
Click to expand...
Click to collapse
Remove "stock' magisk
Install the patched magisk apk
Patch the stock init boot with the patched magisk apk
Flash the new patched init boot
on a clean install it works for me (beta: cheetah-t1b3.221003.008)
lunacies said:
I did not even know this was a thing prior to buying the phone and don't remember seeing anything posted about it until after I got the phone and google'd and found people talking about it on reddit but I did not find anything on here going into detail about it.
I never stated it was a "necessity" and I have no idea if the developers are active or not. They are older apps that are not overly popular that everyone uses however they were things I used on a regular basis and have no idea how I would even check to have known if they were 32 or 64 bit until I got the new phone and they didn't work and wouldn't let me install them. It's not the absolute end of the world, it's just an inconvenience and means I need to try and find replacements or reach out to the devs but it doesn't hurt to ask here because I figured there wld be a way around it but obvio
Click to expand...
Click to collapse
That's what I meant by and or sorry if me misinterpreting what you meant
bhammler said:
on a clean install it works for me (beta: cheetah-t1b3.221003.008)
Click to expand...
Click to collapse
I've compiled Magisk with the supplied patch from the repo and it isn't working for me. I've verified that the init does include the changes to override ro.zygote, however none of the Zygote processes start as the adb server never starts up, and well it doesn't boot.
Tested with the modified Magisk APK from the repo, same deal.
Strange that a clean install is necessary.
don't bother with a clean install, after I've installed some Mgaisk modules, I had a bootloop ;-)
It's nice to see there may be an option and I hope it works for everyone else. I am stuck with a Verizon phone so rooting is out of the question for me and I figured something like this would require root but hopefully other people are successful in getting it to work.
This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.
Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?
Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com
hahimot483 said:
Wouldn't it be easier to just patch build.prop with a magisk module instead of patching the boot image?
Pixel7_32bit_helper/patch.diff at main · ThomasKing2014/Pixel7_32bit_helper
Contribute to ThomasKing2014/Pixel7_32bit_helper development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
No as I discuss here.
Namelesswonder said:
Didn't sleep, I have gotten closer, but Magisk modules aren't going to be the solution.
The earliest Magisk allows you to modify properties is after the post-fs-data trigger, which is well inside the init.rc. This is problematic because the property needs to be set before init.rc is even read.
Using a Magisk module to replace the init.rc with something else also isn't possible, since Magisk doesn't setup the overlays until well into the boot process.
This replacing is necessary because init.zygote64_32.rc actually has the secondary zygote service disabled, so the file needs to be modified to enable it, or with control over init.rc just stuffing a custom zygote service into it.
I don't think slipstreaming a modified init.rc and init.zygote64_32.rc into the ramdisk in init_boot will work since they would be overwritten once the system partition mounts. Could just modify the system partition, but that'll be for another day.
Click to expand...
Click to collapse
Gerr1 said:
This works now, the problem was not the modules. If you enabled the zygisk in the 24 manager app than you got stuck in the bootlogo „G“. It’s fixed now, there is a new 25 magisk patched manager app that works with zygisk enabled. All my 32 Bit apps working now.
Click to expand...
Click to collapse
Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.
Namelesswonder said:
No as I discuss here.
Does it? I tried with building my own 24300, 25200, and 25205 and the result was the same on all of them. I didn't remove all modules and kept Zygisk on, so I guess I will have to try completely deleting all Magisk data.
Click to expand...
Click to collapse
Yes it works now with the new magisk Manager APK.