Related
Found this thread on the HTC Hero section for it's open GL will this work for our wildfire?
http://forum.xda-developers.com/showthread.php?t=899801
Yea I flashed it, noticed an improvement in playing angry birds...i think.
Sent from my HTC Wildfire using XDA App
Will it work on cm7 nightlies kevin?
Sent from my HTC Wildfire using XDA App
Yeah
Sent from my HTC Wildfire using XDA App
Yes it works with just about every ROM, but, in my view, I can't see any benefit. (I dont play Angry Birds, and, the rest of the games and LWP's don't show any benefit).
How do you do this?
Just flash it like a rom?
Well, that's what I initially did. Flash the ZIP in Post #49 in that thread. But, on reading that complete thread, I guess you have to edit the build.prop file in /system (Using Root Explorer / ADB Push Pull).
However, this is where I cant get it to work. WHenever I add the 2 lines in Root Explorer and Save Changes, the phone reboots. If I use ADB, even after pushing, when I check the same file using build.prop, no changes are visible, (The opengles.version automatically reverts back to 65536 and the line which enabled hardware acceleration of the UI is gone) and, ASI only shows OpenGL 1.0 due to this
Well, I have no idea what I am doing wrong, will try it out again and see..
I'm a newb with this.
Could someone possibly make a bit more explained guide?
Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Updated: (ADB Commands Copy - Pasted from another post by kevin2516. Thanks mate )
*Make sure ADB is installed on your system and it is working. There are many guides available to install ADB, so I wont be going into that.
*Start Command Prompt (cmd), Browse to your "Tools" folder into your SDK
*Use the ADB Pull Command adb pull /system/build.prop
*This will now be saved to your tools folder. Edit is using Wordpad / Notepad++ (Not Notepad) as follows:
*Locate a line which starts with dalvik. (The first one, there are 3 of them)
Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save it.
* Push it back to System using the ADB Push Command: adb push build.prop /system/build.prop
* Reboot ADB using the adb reboot command
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.
With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
bgx said:
With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
Well, I took your flashable ZIP, removed the build.prop it contained, and replaced it with the build.prop of CM7 Nightly 2. Then, I tried flashing it, still no change.
Now, I have no idea whether I am 'allowed' to change flashable ZIP's like that or not, but, from what it is looking like, I am still unable to get this working on CM7NB2. I'll probably try making a flashable ZIP from scratch later as I get time.
bgx said:
I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
If it's simple enough, it would be nice if you could tell how to do a flashable zip (or yourself make a one suitable for CM6/7 ). I just want to test these libraries on CM7, any help is appreciated
Don't expect nothing special, I'm not a dev!
3xeno said:
Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Then, locate a line which starts with dalvik. (The first one, there are 3 of them)
* Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save and Exit
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.
Click to expand...
Click to collapse
But it's not working for CM7?
Where can i find FLashable zip? I don't understand where is post #48
Even if i find, i have read, that it's not working? Or working?
You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).
3xeno said:
You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).
Click to expand...
Click to collapse
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/
vilks said:
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/
Click to expand...
Click to collapse
Which is exactly what I said in the CM7 thread. No one here has till date, found verifiable gains, with using OpenGL on the Wildfire. Everyone reports the same thing, that there is no or absolutely negligible (Which I think is just a mind thing) change in gaming / intensive applications performance.
If you are looking for ROM's wit inbuilt OpenGLES Support, WildPuzzle has a flashable ZIP, and DS and DK Roms provides it inbuilt in its latest version. For the others, the manual method has to be followed.
I'm a HUGE fan of V4A, so I finally got it to work, and today I'll share with You how to get to work.
Make sure that You have root and TWRP or Phillz installed
Download V4A from PlayStore
Download BusyBox(Stericson) and install it to System/xbin(Su/bin directory probably would work too)
Install V4A drivers.
Rename SoundAlive_31_M folder in System/Priv-App to something else or cut and paste it somewhere else.
Flash this file Click here!
In V4A change mode to compatibility.
Done!
Thanks to MaximumEntropy for his file.
Additional info:
6.0 beta
SuperSu 2.66 beta
V4A 2.3.4.0
i have given this a go as per your guide but is still not working on 6.0.1?
It's just acting like it did before v4a installed audio effects don't make a difference any help anyone?
thanks
iNeoTom
Likewise here, in driver status it says it is supported and that neon is enabled but it is not processing or enabled overall. I've tried changing to compatibility mode and normal mode without any change.
Thanks a lot, works flawlessly on 6.0.1!
To get it working I had to replace the audio_effects.conf in system/etc with the one arter97 posted here http://www.arter97.com/browse/S6/M/ViPER/ set the right permissions and reboot. Got a system FC at first but then seems to work flawlessly. Good luck! :good:
This worked! S6 noble ROM 6.0 Thanks!!
delete
Overall I love the Pixel XL, but with all of my previous Android phones having Root access, I have always run Viper4Android, and in my opinion the sound quality output of the stock Pixel is awful by comparison. So, my primary reason to use the awesome work done by those who brought us bootloader unlock and Root, is to be able to use Viper4Android.
With the changes to Pixel partitions and overall structure, as well as the method of Root, so far I have not been able to get Viper4Android working. This thread will be a place for us to discuss what we have tried, learned, and hopefully figure out a solution! I do think that what ever needs to be done to get it working will be the same for both the Google version of the Pixel (XL) and the Verizon version, as the method of Root is the same for both as well as the overall structure for the partitions and images.
So far, after unlocking bootloader, and then using the Root method, I have not gotten Viper4Android to even detect root. This was with stock kernel, and no other changes to any audio files or other settings. I did install a couple of apps (Titanium Backup, Solid Explorer) to validate Root was working. I also tried installing BusyBox, which seemed to install just fine, but no change to Viper.
I am not very up to speed yet on how systemless root may be a factor in this, the Pixel XL is the first device I have had with it. Anyway, I will keep plugging away at some things and post what I learn.
once there is a custom recovery, it will be very easy to flash packages that will make viper work..
search XDA for the Arise Sound mods
What error are you getting? I'm getting a bad BusyBox error. I fixed the I/O error by renaming audio_effects.conf.
Sent from my Pixel XL using Tapatalk
sionicion said:
What error are you getting? I'm getting a bad BusyBox error. I fixed the I/O error by renaming audio_effects.conf.
Click to expand...
Click to collapse
Viper4Android cannot detect root. See screenshot.
mrhds said:
Viper4Android cannot detect root. See screenshot.
Click to expand...
Click to collapse
I got that error when viper was in priv-app, make sure you set the kernel to permissive. I do it by going into the terminal app and entering the commands su, to gain root, setenforce 0, to switch to permissive, getenforce, to make sure it's permissive.
Sent from my Pixel XL using Tapatalk
To make viper work we have to use the same trick that is used for adaway but with all the files needed by viper which is:
- Move the files to /su
- Make copies of the files viper needs to change, make the changes and copy the modified ones to /su
- Create a /su/su.d/60viper with mount binds on all the files
Or have a modified version of Viper that could read from /su or /system_root instead.
exadeci said:
To make viper work we have to use the same trick that is used for adaway but with all the files needed by viper which is:
- Move the files to /su
- Make copies of the files viper needs to change, make the changes and copy the modified ones to /su
- Create a /su/su.d/60viper with mount binds on all the files
Or have a modified version of Viper that could read from /su or /system_root instead.
Click to expand...
Click to collapse
That's nothing I can figure out but it does confirm my thoughts that viper is having trouble because there is no /system and instead a /system_root. I guess we'll have to wait it out until someone patches viper. Or someone figures out that trick and posts a guide for it.
Sent from my Pixel XL using Tapatalk
I did it! I can't believe it! Viper is working!
So I was googling manual installs of Viper and came across Arise, somebody said you just have to paste the contents to system if you can't flash. That's what I've been doing kinda but it wasn't working before. Anyway I got Arise and went into the zip and into the Leviticus folder and pasted the contents where I believed they belonged. I got some errors so I had to use FX and ES File Explorer together, to rename files, copy files over, etc. I copied over the files to the folders underneath /system_root/system/, except su and su.d. su is just /su in my file apps. Although I think the permissive script is in the wrong spot since I still had to manually run the setenforce 0 command.
Doing it manually this way avoids Viper wanting to install a driver, it's just ready to be powered on, avoiding I/O and busybox errors. Leviticus 1.3 is what I used from the Arise website since I couldn't find any other download and it was on the header of the website.
Now if I could just figure out how to increase sound output. The mixer_paths.xml is different slightly, the digital volumes are like digital mix volumes, and changing their values doesn't seem to have an effect. I still have to play around with that, I might just wait for someone else to discover what values alter the headphone sound output. But at least I made progress! Hope this helps some people out.
Sent from my Pixel XL using Tapatalk
Viper is working!!
@Mentalmuso posted his work on a script that takes care of permissive, busybox issues, etc.! Thanks a ton! I downloaded the zip package, ran the script and it works! Here is the link:
http://forum.xda-developers.com/pixel-xl/themes/mod-weta-audio-t3491179
@sionicion: I was about to test out your route as it looked promising, but then noticed the other post
quick question... (this may be stupid)
If you root - get viper working
can you then unroot and be good as far as safetynet and stuff?
Or does viper ALWAYS need root?
I'm trying to warm up to the idea of not rooting this phone and maybe doing android pay.
So much stuff that I used to use root for isn't needed anymore (culminating with the "autotools" addon for tasker)
But I just don't know if I can live without viper, it makes such a huge difference.
Thanks,
I've learned to live without it. It's tough as Viper is really good but I really grew tired of coming up with workarounds for an app that isn't even maintained anymore. Fiddled around with the stock eq in Play Music for awhile before I was satisfied.
Yea, I really miss Viper too but not sure if I want to root anymore. The only reason I use Viper is for the volume boost for my BT earbuds when watching mkv files in MX Player. For some, all mkv files play at a pretty low volume. Viper is able to increase it substantially. I sitll haven't found a non-root substitute for this problem yet. If anyone can advise on an app that does volume boost for BT headsets, that would be greatly appreciated.
Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...
wakram001 said:
Dear brother's I have facing issue with viper4android fx, I have installed from magisk module and install driver but it show status-abnormal, I have seen many videos on youtube and check XDA thread but still same issue.
Pls help me...
Click to expand...
Click to collapse
Use the guide as in that post (the same can be also found in the XDA V4A general thread):
zgfg said:
There is actually an easier way to fix Viper4Android, follow the original post where the fix was described:
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
ViPER4Android FX By pittvandewitt and MrWhite214 Introduction Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look...
forum.xda-developers.com
In other words, replace (use TWRP or root explorer like MiXplorer)
/data/adb/modules/ViPER4AndroidFX/post-fs-data.sh
with the attached file (download and unzip) and reboot
Still make sure that Legacy mode in V4A Settings is enabled
AML module makes no harm but it's not needed (unless you install additional audio modules like mi9tpbitrate320.zip)
---
In case of installing V4A from scratch:
- install ViPER4Android_FX-v2.7.2.1.zip from Repo (through Magisk) and reboot
- open Viper4Android app and let it install the driver, it will reboot
- replace post-fs-data.sh as above and reboot once again
- open Viper4Android app and enable Legacy mode in its Setrings
- also, don't forget to enable Master limiter for e.g. speaker or headphones
Check the driver status, it must show Status Normal (and Processing Yes when playing nusic)
---
I have Xiaomi.eu A11 beta and I regularly update every week when they release (by dirty flashing their new MIUI zip release, wiping Dalwik and Cache and by flashing the new boot img patched by Magisk)
Up to the two weeks ago I had to re-do the relatively complicated procedure for V4A as was described in this thread upon every Xiaomi.eu update
Since two weeks ago when I replaced the post-fs-data.sh as described above, I just dirty flash Xiaomi.eu, apply root/Magisk, and my V4A continues to work as my all other installed Magisk modules (and root apps), with no needs to fix the V4A driver anymore
PS: This 'new' method with the modified post-fs-data.sh is specifically useful for Magisk Canary 22006 since Magisk 22006 has a known bug with processing the sepolicy.rule files (also in /data/adb/modules/ViPER4AndroidFX), and hence the 'old' method from this thread does not work with Magisk 22006 - but the 'new' method does work (I currently use that Magisk 22006)
Click to expand...
Click to collapse
Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.
wakram001 said:
Can AML fix this issue...
I can't understand which files I replace.
I am a bigner user of magisk.
Click to expand...
Click to collapse
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
zgfg said:
In the thread I gave you the link, use of AML was also described. But I'm no more using AML and cannot/won't support you about
In my previous post there is s link to my post with the guide using post-fs-data.sh (sorry, I'm not going to send the link again)
Click on that post and inside you will find post-fs-data.zip.
It was described in details, so once again but only shortly here:
- download the zip, extract post-fs-data.sh
- use your favorite root File Manager (like MiXplorer - google on XDA to find its thread and installation if needed) or use TWRP, Advanced, its File Manager (again, google if needed to learn how to use).
Anyway, those skills and tools will be useful for you in future if you decided to go with Magisk, its modules, etc
- go to /data/adb/modules/Viper4Android FX and rename the existing post-fs-data.sh to post-fs-data.bak (just in case) and paste instead the post-fs-data.sh you extracted from my zip (see screenshot)
-reboot
- open V4A app, go to its settings and enable Legacy mode (again, see the screenshots in my post with the guide)
Click to expand...
Click to collapse
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
wakram001 said:
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Dear brother
I have understood what you said, but I can't find zip file from your previous post, one more thing v4a fx working with legacy mode, but when I close legacy mode it cannot support.
Thanks for replying on my post.
Click to expand...
Click to collapse
Zip attachement was there, you have to go to that post and scroll down through the whole post, it was the last attachement (scrollshot below, click to open and scroll down, it's very long)
Do not read just my post there but study the whole thread and you will see that bobod made it working without Legacy mode on Mi 9T (Pro or not Pro). Google for the general V4A thread on XDA and you will see that most of users/phones can only work with Legacy mode. If you don't like, don't use V4A. Btw, what's wrong with, besides that is called 'legacy'
Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...
wakram001 said:
Dear brother
Still I can't find the zip file, I have goes through whole post and I can't get zip files.
I request you to pls upload once more....
Thanks for guidance...
Click to expand...
Click to collapse
Go back to my first answer in this thread (post #2), answer to your original question about V4A.
Click on to the cited post there, to JUMP INTO
When you jumped to that other thread and the post there, scroll down till the end of the long post where ATTACHMENTS begin
CONTINUE SCROLLING through all atrachements, skip three screenshots and CLICK on the ZIP (last attachement) to start downloading
Really so hard?
Has anyone been able to use v4afx on 13? It keeps asking to install the drivers.
Basically you have to remove everything from V4A first like in Magisk and the app itself. After the reboot you do the installation process again with Magisk but do not open V4A yet.
Put the attached file into /data/adb/modules/ViPER4AndroidFX and overwrite it if necessairy.
Now reboot and it should work with legacy mode on.
To make it work, v4a must "patch" audio_effects.xml file, but there is a problem, because earlier androids up to OOS11 have it stored in /vendor/etc, and it patched it without problem. OOS12 and 13 have that file too in this location, but it's generic file, don't contain Dolby Atmos, Nokia Ozo processing, Dolby VQE (message enhancer), and system don't use it...
From OOS 12, oneplus decided to store and use this file in /odm partition, exactly in /odm/etc.
V4a don't have possibility to patch it, that's why it tries to install "driver" again and again.
One more info.
mount -o bind /vendor/etc/audio_effects.xml /odm/etc/audio_effects.xml from post-fs-data.sh will replace that file in odm, and yes, it will work, but it also will kill your Dolby Atmos, OZO processing, VQE, because this file in /vendor/etc don't contain them.
Thanks for the input. I will give it a shot.
Idk if u have looked thoroughly, but I made a guide to install V4A: https://forum.xda-developers.com/t/...tall-viper4android-for-oneplus-8-pro.4388799/
Instead of using these weird files and workarounds to install V4A...
I would suggest downloading DDC and kernel files which can be found on my XDA thread.
Just download them and extract the .zip file only
Then download, install V4A repackaged, reboot and done
Try installing V4A repackaged: https://github.com/programminghoch10/ViPER4AndroidRepackaged/releases
The weird file you're referring to is from dorimanx himself.
[APP] [FIX] 100% working Viper4Android for Android 10-11-12 devices
If you are someone like me who encountered countless problems while installing Viper4Android on your Android 10 or 11 device and have no idea what to do then you are in the right place. Just download and install the apk from the attachment below...
forum.xda-developers.com