Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not processing A14 #91

Open
Lazaro0051 opened this issue Mar 20, 2024 · 9 comments
Open

Not processing A14 #91

Lazaro0051 opened this issue Mar 20, 2024 · 9 comments

Comments

@Lazaro0051
Copy link

Screenshot_2024-03-20-15-02-06-960_com aam viper4android
Not processing in A14. Not sure what happened, used to work fine.

@griha41
Copy link

griha41 commented Mar 20, 2024

Mate first of all. No matter do you updated firmware or entire os (security patch or entire version OS update), the default vendor configuration will destroy your ViperFX patches with default files.

I solving just with simple way: after anykond of firmware update, I open up again the Magisk and installing over the the ViperFX, without any deinstallation or something. Just install over.

This action not ruining the ViperFX configuration, modules and etc, it's just reinstall all modules and patches on their placements and at the end I'm performing the system restart. After restarting - everything works well and without any issues.

Try it yourself and have fun. BUT if you not sure - make the backup of ViperFX settings somere else (for recovering) and do it every time when you updating the phone firmware.

Have fun and lots of pleasure!

@Lazaro0051
Copy link
Author

Thank you so much, mate. I did, but still the same. I've uninstalled and reinstalled, but the issue persists. ): don't know what else to try.

@griha41
Copy link

griha41 commented Mar 20, 2024

Thank you so much, mate. I did, but still the same. I've uninstalled and reinstalled, but the issue persists. ): don't know what else to try.

That's quite odd, I have 2 android 14 Phones (Samsung A13 & Samsung A52) and have no issues with starting ViperFX.

The settings page allow you to preset specific adjustments for the enabling of that mod.
Click Settings button (top right corner, the last one),
In opened activity there's 2 switches:

  1. Old mode (or something close to it, I'm sorry I have russian locale)
  2. Compatibility mode

Try those switches one-by-one like:
Disable all features (better test on headphones)
Disable all toogles and start music, try to work with EQ set Bass to low and Hight to higher levels.
If no luck - enable first and start over again.

At Compatibility mode - icon of ViperFX state would be gray out. So don't loose you time, try the same.
Maybe you'll able to find proper working mode for your phone.

OH DAMN, MAN DID YOU ENABLED THE FIRST TOOGLE AT SETTINGS LIST (FEATURES FOR YOU SOUND DEVICE)? I'm sorry for the caps, it's only for attention and nothing more

@Lazaro0051
Copy link
Author

Thank you for all your help, mate. I've done everything I could think about, but still not processing. And yes, I enabled the first toggle at settings list.
I think it's a problem with the newest version of HyperOS. Hopefully it gets resolved soon.

@griha41
Copy link

griha41 commented Apr 5, 2024

Thank you for all your help, mate. I've done everything I could think about, but still not processing. And yes, I enabled the first toggle at settings list.
I think it's a problem with the newest version of HyperOS. Hopefully it gets resolved soon.

Yes that's also might be an issue or even the base of issue...

@masleyko
Copy link

masleyko commented Apr 7, 2024

man i had same problem but now it works for me..
for some reason one setting insyatem was changed probably by update .. check images
Screenshot_20240407-151036_Settings~2
Screenshot_20240407-151103_Settings~3

@Lazaro0051
Copy link
Author

man i had same problem but now it works for me.. for some reason one setting insyatem was changed probably by update .. check images Screenshot_20240407-151036_Settings~2 Screenshot_20240407-151103_Settings~3

I tried this and still the same. I assume it has something to do with HyperOS. But thanks anyway, mate. 🫶🏻

@masleyko
Copy link

masleyko commented Apr 7, 2024

Then you are probably right .. im on CrDroid 10.2

@ralphnetto
Copy link

I was also having the same problem and I found a fix for that:

Disable "Immersive Sound" in HyperOS sound settings.

Screenshot_2024-04-30-23-21-51-304_org telegram messenger

Screenshot_2024-04-30-21-41-33-167_org telegram messenger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants