This APP's will only work on Official Samsung TouchWiz Kitkat Rom I9190/92/95
U Can flash it using any recovery, i recommend (CWM)
I am not responsible if your mom gives you a slap in the face, because you are modifying your phone
WARNING: YOUR WARRANTY IS VOID IF YOU CONTINUE
ALWAYS PERFORM A NANDROID BACKUP, PLEASE DO IT!
THIS ZIP WILL DEBLOAT/DELETE/DESTROY MANY APPS IN YOUR SYSTEM (INCLUDING KNOX)
YOU NEED A FULLY BOOTED DEVICE, CONFIGURED EVERYTHING (THIS IS A MOD, NOT A ROM)
(DO NOT TRY TO USE IT IN ANY CUSTOM ROM LIKE CM11 AND OTHERS)
Installation
PERFORM A NANDROID BACKUP
1. Download to your computer or phone and put it in your SD-Card.
2. Reboot in Recovery Mode.
3. Choose Install Zip
4. Search were you put the ZIP file.
5. Flash it normally (May take a while)
6. Wipe cache and dalvik cache (do not perform a full wipe/factory reset)
6. Reboot and Enjoy!
What is included
*S5 Touchwiz Launcher + Magazine + PullUp
*S5 Accuweather App
*S5 Message App
*S5 SFinder
*S5 QuickConnect
*S5 Radio App
*S5 Music App
*S5 Video Player
*S5 Settings App + Search
*S5 Lockscreen Effects
*S5 Memo 2
*S5 Translator
*S5 Travel
*S5 WatchON
*S5 SVoice
*S5 Voice Note
*S5 Browser
*S5 My Files.
*S5 Boot Animation
*S5 SystemUI (Status Bar)
*S5 Optical Reader
*S5 Gallery
*S5 InCallUI
*S5 Calculator
*S5 Download Manager
*S5 Task Manager
*S5 GeoLookup
*S5 Easy Launcher
*S5 Video Cutter
*S5 Magnifier Widget
*And more will come...
Known Issues
>. You can't turn ON (UPSM) ultra power saving mode
>. Messages app may not work in 9192
>. InCallUI and Phone may not work in 9192
>. SView with some layout problems
>. If you get FC in Weather App, clear app data in application manager.
>. You tell me!
Contributors
@EngelDMT
@ploiki
@kokobenjamin
@rrgrrg
Changelog
Code:
AIO V2 Beta 1
ADD A lot S5 Apps for testing (See the top list)
UPD Update some internals app's to XXU1ANGF
FIX SecSettings (PersonalMessage) missing S5 xhdpi images and icons.
FIX Notification bar sometimes distorted
Beta 9.2
FIX Missing Option "Personal Message" in SecSettings.
Beta 9.1
ADD Universal SecSettings for I9190/92/95
ADD Universal SystemUI for I9190/92/95
Beta 9
FIX Memory leak in SecSettingsProvider
FIX Hearing FC in Accessibility
FIX Notification Bar Color Transparency
FIX Tab view FC in Settings
FIX Memory leak in SystemUI
FIX Missing (Motions and Gestures)
FIX FC in Ringtone Chooser
UPD Strings to (es-US) in ScreenShots
ADD Voice Control
ADD Power in Settings
ADD Optimized S5 Accuweather for S4 Mini
Beta 8
FIX GPS Icon changed or Missing in SystemUI
FIX SystemUI Strings Fixed
FIX Layout fix in Settings
Beta 7
SRC script: cleaning and reorganizing code for deleting old odex/apk files
FIX Keyguard: Missed Calls and Unread Messages
FIX Keyguard: Layout in PIN Unlock.
Beta 6
SRC cleaning and reorganizing code for deleting odex files
ADD QuickConnect.apk
ADD QuickConnectInteraction.apk
ADD SFinder.apk
Beta 5
ADD binary scrips in ZIP to to delete/remove only the unnecessary .odex files automatically.
REM Remove Ripple Effect on Lockscreen effects (SecSettings.apk) because its unstable.
Beta 4
ADD SystemUI.apk (S5 Notification Interface)
FIX Shortcut of BatterySaving in SystemUI.apk
Beta 3
FIX Lockscreen doesn't display the weather
ADD KeyGuardWidget.apk
FIX You can't turn off dual clock, and when you're in roaming area
Beta 2
FIX Wi-Fi Direct (Icon Missing)
FIX FOTA Update in About Phone gives FC in Settings
ADD FotaClient.apk
ADD SyncmlDM.apk
ADD KeyGuard.apk to FIX loosing lockscreen effects when rebooting
Beta 1
FIX Wi-Fi Direct
FIX Data Usage Settings
FIX In sounds config, volume config doesn't work
FIX FC of Settings when reboot.
Experimental Release
-Initial Test
ADD SecSettings.apk
ADD SecSettingsProvider.apk
ADD SettingSearchProvider.apk
LINK (AIO S5 Apps V2 Beta 1) (With SystemUI.apk)
https://www.androidfilehost.com/?fid=23622183712473997
MD5: 83416dbdbdb1bf036a3ca969a9609f09
File Size: 365.3 Mb
Always do a Nandroid backup BEFORE using this MOD
If you like this POST just give me a Thanks.
EngelDMT said:
This APP will only work on Official Samsung Kitkat Rom
U Can flash it using any recovery, i recommend (CWM)
I am not responsible if your mom gives you a slap in the face, because you are modifying your phone
ALWAYS PERFORM A BACKUP OF THE FOLLOWING APP IN PRIV-APP IN SYSTEM FOLDER
SecSettings.apk
SecSettingsProvider.apk
(DO NOT TRY TO USE IT IN ANY CUSTOM ROM LIKE CM11 AND OTHERS)
Installation
1. Download to your computer or phone and put it in your SD-Card.
2. Reboot in Recovery Mode.
3. Choose Install Zip
4. Search were you put the ZIP file.
5. Flash it normally
6. Reboot and Enjoy!
Benefits:
1. New Lockscreens Effects. (See below)
2. Grayscale and others configuration for PowerSaving
3. U Can turn Torch (Camera Light) with pressing Volume UP when screen is OFF.
4. U Can ADD Wallpapers for SView.
5. U Can turn on One Handle Operation (No Fully Compatible)
6. Search Button in Top Right for easy find any configuration.
7. Fully Compatible with TouchWIZ Launcher of S5
8. Screen Gestures for made an Screenshot.
Issues
1. Wi-Fi Direct doesn't work
2. Data usage doesn't work
3. In sounds config, volume config doesn't work (U can use the volume buttons normally)
4. Software update in About Phone Doesn't work (root users dont care this )
5. Lockscreen effects work but when you reboot it change automatically to "no effect" (U Can chage it again and dont reboot your phone :angel: )
6. The Search button at the top of Config App doesn't work. (FIXED) Thanks to @jhon_8 :good:
7. When reboot Config App give FC but it work normally after that. (FIXED) Thanks to @jhon_8 :good:
8. Lockscreen doesn't display the weather
9. You can't turn off dual clock, and when you're in roaming area, there are 2 clocks in lockscreen, when you go to customize personal message, to got only one clock.
10. You can't turn ON (UPSM) ultra power saving mode
11. Aplication manager, battery are not fitted to the screen (Width)
12. AirGesture (Never Will Work) No Sensors In hardware of S4Mini and variants.
LINK
https://mega.co.nz/#!jJ0FWBAA!i8JKIdyFMXZ3aGcnP1p6QJeS9t69OvhLNkmAR-C7reM
If you like this POST just give me a Thanks.
Click to expand...
Click to collapse
will it work with dual sim variant of s4 mini??
adityapal said:
will it work with dual sim variant of s4 mini??
Click to expand...
Click to collapse
server busy or wrong link ?
adityapal said:
will it work with dual sim variant of s4 mini??
Click to expand...
Click to collapse
Yes, it will work in I9192 but u can test it, and give us your opinion, remember do a backup first.
Luca TIR said:
server busy or wrong link ?
Click to expand...
Click to collapse
I'll update to new server soon. Maybe Mega doesn't work good to provide files and stuff.
PD: I add a mirror of MediaFire
EngelDMT said:
Yes, it will work in I9192 but u can test it, and give us your opinion, remember do a backup first.
I'll update to new server soon. Maybe Mega doesn't work good to provide files and stuff.
Click to expand...
Click to collapse
ok, perfect. but the menu for ultrapowersaving works? i find the option by the apex action/setting shortcut and work fine, comprensive the white/black screen mode
now the best for our cell will the statusbar complete-like s5
Luca TIR said:
ok, perfect. but the menu for ultrapowersaving works? i find the option by the apex action/setting shortcut and work fine, comprensive the white/black screen mode
now the best for our cell will the statusbar complete-like s5
Click to expand...
Click to collapse
The UPSM Ultra Power Saving Mode doesn't work, Only grayscale.
By the way... I recently add a mirror (MediaFire)
ery very very nice!!!
Thank you:laugh::laugh::laugh::laugh:
it worked on i9192 but the sim settings are gone else everything works fine
on my device, after flashing, settings program not work and get a fc
my is i9195 - 4.4 spanish no-brand kitkat whit root
Luca TIR said:
on my device, after flashing, settings program not work and get a fc
my is i9195 - 4.4 spanish no-brand kitkat whit root
Click to expand...
Click to collapse
if you are in odex rom delete .odex file of sec settings n sec settings provider
adityapal said:
if you are in odex rom delete .odex file of sec settings n sec settings provider
Click to expand...
Click to collapse
yes, it works now. thank you
but...the icons? most of the menu are whitout icons, only a little white point
Luca TIR said:
yes, it works now. thank you
but...the icons? most of the menu are whitout icons, only a little white point
Click to expand...
Click to collapse
U can attach an screenshot? ... The issue you mention is weird...
To correct the error volume and brightness, open files:
"preference_dialog_brightness" and replace
<SeekBar android:id="@android:id/default_loading_view"
on
<SeekBar android:id="@android:id/seekbar"
"preference_dialog_ringervolume" and replace
first <SeekBar android:id="@id/ringer_volume_seekbar"
on
<SeekBar android:id="@android:id/seekbar"
im waiting for a working 100% version :silly: ... little bugs to fix
EngelDMT said:
U can attach an screenshot? ... The issue you mention is weird...
Click to expand...
Click to collapse
Luca TIR said:
Click to expand...
Click to collapse
finally found: it caused by xposed - per app setting [resolution at 210 dpi]
ploiki said:
To correct the error volume and brightness, open files:
"preference_dialog_brightness" and replace
<SeekBar android:id="@android:id/default_loading_view"
on
<SeekBar android:id="@android:id/seekbar"
"preference_dialog_ringervolume" and replace
first <SeekBar android:id="@id/ringer_volume_seekbar"
on
<SeekBar android:id="@android:id/seekbar"
Click to expand...
Click to collapse
i will made few test on this, i will post if it works.
Luca TIR said:
Click to expand...
Click to collapse
This is weird, did you have any system modification of icons or any that affect system icons?
PD: NVM, i see you fixed. =)
fix dual clock
fix volume
fix brightness
https://yadi.sk/d/juHfvD1naqN8j
ploiki said:
fix dual clock
fix volume
fix brightness
https://yadi.sk/d/juHfvD1naqN8j
Click to expand...
Click to collapse
seems like you're not a junior at all ! thanks for bug fixing :good: just these 3 bugs and we can have a stable settings app
Lockscreen effects work but when you reboot it change automatically to "no effect"
Wi-Fi Direct doesn't work
Data usage doesn't work
Aplication manager, battery are not fitted to the screen (Width)
Click to expand...
Click to collapse
ploiki said:
fix dual clock
fix volume
fix brightness
https://yadi.sk/d/juHfvD1naqN8j
Click to expand...
Click to collapse
Lol i spend 2 hours searching framework-res.apk for decompiling to fix this ussue... anyway i will, test, and update first post and give you credits for the fix...
PD: IT WORKS!
rrgrrg said:
seems like you're not a junior at all ! thanks for bug fixing :good: just these 3 bugs and we can have a stable settings app
Click to expand...
Click to collapse
Yep, 3 step less to have an stable Settings =)
Substratum
- if you are here, that means you know that substratum is based on the system of layers of Sony, and it was added to works in custom ROMs that runs android 7.0 from LineageOS to any based ROMs on it.
- this thread aims to those having a s2 phone (gt-i9100...maybe other variants as well) with problems installing a layer in substratum or substratum itself.
**Installing Substratum
1- Download substratum from play store.
2- Go to settings>apps>substratum and enable all permissions.
3- go to settings>apps, and press the 3 dots menu(or the gear icon in top right corner).
4- scroll down and choose "special access"
5- add permission to substratum in every permission possible.
6- force stop substratum(DON'T CLEAR THE DATA) then start it.
****Installing Overlays
- there are two ways to install layers in substratum.
(1) first way
1- download in install your theme from play store or if you have an apk.
2- select the theme in substratum.
3- Mark your desired overlays.
4- press on the brush icon and select build & install.
wait a few minutes (restarts often the system ui) and ready! your theme is applied
-I use the other method and I've never failed.
(2)second way
1- install your theme as a normal apk or from play store.
2- open substratum and choose the theme.
3- Mark your desired overlays.
4- click on the brush icon and select build & update.
P.S: Once compiled go to OVERLAY LIST and mark the layers that you apply
Warning: if you use this method and want to apply layers make sure you have unapplied already applied layers, (this is done by checking which you will remove and then press on the icon brush and Press disable selected) ...
______________________________________
other data:
- If you want to apply a layer to the system only (i.e navigation bar, status bar and other system stuff), apply the layer "system UI" layer, and "Android system" layer only.
Credits goes to:
@MigoMujahid for helping in design and the substratum installation guide.
F.A.Q
Q: Some layers fail and doesn't install correctly?
A: open the section of the parts of the ROM that has overlays applied to, and select which gives you the error, then click the three points at the top, select "disable installed overlay", also select "clean installed overlay" and finally uninstall theme now reinstall the theme and try to apply it.
Q: I have fear, substratum didn't request access to root after open the app, and I don't want to fall in bootlop?
A: this OK to confirm that substratum recognizes well the root, go to substratum settings and where it says system verification sure that say rootless.
Q: i need to know more about Substratum?
A: If you are looking for info about Substratum, please go to the announcements thread.
Q: how do i make a logcat?
A: you can create a logcat using Catlog app from playstore, or by usung this guide.
All right reserved to "Nathan Chancellor" for this guide.
Q:
how to delete a culprid overlay that bootloop our device?
A: There are 3 ways provided thanks to @Troubadour666 ?
(1) From TWRP, delete the /data/app/"substratum.theme.name.folder"/*.* <---- where was installed the lastest overlay apk (generaly android or systemui overlay) that can give FCs of SystemUi app or bootllop device at next reboot.
-------------------------------------------------------------------------------------
(2) While you have your systemui FCs, if you have a wifi access to your device folders tree, without rebooting it, you can only delete the lastest overlay idmap file on your /data/resource-cache/ folder and instantly FIX the systemui FCs issue.
(maybe with some adb command shell you can do that without rebooting, i ignore the command at the moment, but i'm sure its possible)
Then, always without rebouting, you can safely/quietly open your substratum app on the overlays installed list and uninstall again the culprid overlay (finaly this step concern the APK on data/app) by ticking it and unsing the brush icon.
-------------------------------------------------------------------------------------
(3) You can use a zip that exist on G+ Substratum and flash it on TWRP to clean all the overlays in one pass. you will be safe at next boot.
More F.A.Qs coming....
MigoMujahid said:
F.A.Q
Q: Some layers fail and doesn't install correctly?
A: open the section of the parts of the ROM that has overlays applied to, and select which gives you the error, then click the three points at the top, select "disable installed overlay", also select "clean installed overlay" and finally uninstall theme now reinstall the theme and try to apply it.
Q: I have fear, substratum didn't request access to root after open the app, and I don't want to fall in bootlop?
A: this OK to confirm that substratum recognizes well the root, go to substratum settings and where it says system verification sure that say rootless.
Q: i need to know more about Substratum?
A: If you are looking for info about Substratum, please go to the announcements thread.
Q: how do i make a logcat?
A: you can create a logcat using Catlog app from playstore, or by usung this guide.
All right reserved to "Nathan Chancellor" for this guide.
More F.A.Qs coming....
Click to expand...
Click to collapse
I forgot forgot this :silly:
Excellent thread that start here !
thanks
Question :
- how to delete a culprid overlay that bootloop our device ?
* From TWRP, delete the /data/app/"substratum.theme.name.folder"/*.* <---- where was installed the lastest overlay apk (generaly android or systemui overlay) that can give FCs of SystemUi app or bootllop device at next reboot.
** While you have your systemui FCs, if you have a wifi access to your device folders tree, without rebooting it, you can only delete the lastest overlay idmap file on your /data/resource-cache/ folder and instantly FIX the systemui FCs issue.
(maybe with some adb command shell you can do that without rebooting, i ignore the command at the moment, but i'm sure its possible)
Then, always without rebouting, you can safely/quietly open your substratum app on the overlays installed list and uninstall again the culprid overlay (finaly this step concern the APK on data/app) by ticking it and unsing the brush icon.
*** you can use a zip that exist on G+ Substratum and flash it on TWRP to clean all the overlays in one pass. you will be safe at next boot.
hope i was clear, thanks.
Troubadour666 said:
Excellent thread that start here !
thanks
Question :
- how to delete a culprid overlay that bootloop our device ?
* From TWRP, delete the /data/app/"substratum.theme.name.folder"/*.* <---- where was installed the lastest overlay apk (generaly android or systemui overlay) that can give FCs of SystemUi app or bootllop device at next reboot.
** While you have your systemui FCs, if you have a wifi access to your device folders tree, without rebooting it, you can only delete the lastest overlay idmap file on your /data/resource-cache/ folder and instantly FIX the systemui FCs issue.
(maybe with some adb command shell you can do that without rebooting, i ignore the command at the moment, but i'm sure its possible)
Then, always without rebouting, you can safely/quietly open your substratum app on the overlays installed list and uninstall again the culprid overlay (finaly this step concern the APK on data/app) by ticking it and unsing the brush icon.
*** you can use a zip that exist on G+ Substratum and flash it on TWRP to clean all the overlays in one pass. you will be safe at next boot.
hope i was clear, thanks.
Click to expand...
Click to collapse
Excellent
Thanks bro, i will add it to the F.A.Q
Troubadour666 said:
Excellent thread that start here !
thanks
Question :
- how to delete a culprid overlay that bootloop our device ?
* From TWRP, delete the /data/app/"substratum.theme.name.folder"/*.* <---- where was installed the lastest overlay apk (generaly android or systemui overlay) that can give FCs of SystemUi app or bootllop device at next reboot.
** While you have your systemui FCs, if you have a wifi access to your device folders tree, without rebooting it, you can only delete the lastest overlay idmap file on your /data/resource-cache/ folder and instantly FIX the systemui FCs issue.
(maybe with some adb command shell you can do that without rebooting, i ignore the command at the moment, but i'm sure its possible)
Then, always without rebouting, you can safely/quietly open your substratum app on the overlays installed list and uninstall again the culprid overlay (finaly this step concern the APK on data/app) by ticking it and unsing the brush icon.
*** you can use a zip that exist on G+ Substratum and flash it on TWRP to clean all the overlays in one pass. you will be safe at next boot.
hope i was clear, thanks.
Click to expand...
Click to collapse
Excellent my bro
This is very important
Thank you very much
Viper4android: How to install it properly
This is something I've been meaning to write up for a long time now. All over XDA I see people have trouble with getting Viper4android working and I thought this might shed some light on the issue.
There are many zips out there that will install viper but most of them have other sound mods rolled into it and I prefer viper only. I find that most of the others often distort the sound a little, but with Viper4android only, the sound is just perfect for my tastes.
What you need:
- A root file explorer (RootExplorer, EsFileExplorer, etc.)
- Root (obviously)- Either Magisk or SuperSU
- If using Magisk you'll need a Permissive kernel. My kernel works with certain models and is permissive.
- If using SuperSU you can use enforcing, but will need an extra file that I'll cover later on.
- Some good music to listen to.
This method is really not much of revelation since it's actually on the Viper4android thread itself, but almost everyone tries to let the install the drivers automatically. Do not let the app install the drivers for you. It will install the old driver and it doesn't include the Neon driver.
First things first. We need to do a little cleanup just in case there are already some viper files or drivers partially installed.
Viper4android has three places in which it installs:
/system/lib/soundfx/
/system/etc/audio_effects.conf
/system/app/Viper4android.apk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Using your root explorer go to /system/lib/soundfx/ and look for any old V4A files and delete them. It should look like this, libv4a_fx_ics_X86.so. Also check in your system/app/ and check to see if you have the old viper app and if so delete that too (the newest version is 2.5.0.5). Note: if you already have the app installed you can go to the settings menu and select uninstall drivers and it should remove everything for you. Then just double check to make sure. Then uninstall the app unless it's the newest version and placed in /system/app/.
Once we have everything cleaned up it's just a matter of placing the right files in the right spot. I've attached a zip that has everything you will need in it. It is not a flashable zip. Just unzip it to get to the necessary files.
1. Place the Viper4android app in /system/app (no extra folder necessary) and change the permission to 0644 or rw-r-r
2. Place the .so files in /system/lib/soundfx/ and change permission to 0644 or rw-r-r
3. If you don't have any other sound mods installed you can swap out my audio_effects.conf file for yours and set permission to 0644 or rw-r-r, but if you do that back up your original file just in case (just rename the original to audio_effects.bak). If you do have other sound mods installed you'll want to add the following red lines to you existing audio_effects.conf file.
Code:
# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {
[COLOR="red"]v4a_fx {
path /system/lib/soundfx/libv4a_fx_jb_NEON.so
}
#NECESSARY FOR XHIFI
v4a_xhifi {
path /system/lib/soundfx/libv4a_fx_jb_X86.so
}[/COLOR]
# This is a proxy library that will be an abstraction for
# the HW and SW effects
proxy {
path /system/lib/soundfx/libeffectproxy.so
}
# This is the HW implementation library for the effect
offload {
path /system/lib/soundfx/libaudioeffectoffload.so
And...
Code:
# }
# ...
# }
effects {
[COLOR="red"]v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
#NECESSARY FOR XHIFI
v4a_standard_xhifi {
library v4a_xhifi
uuid d92c3a90-3e26-11e2-a25f-0800200c9a66
}
}[/COLOR]
soundalive {
library proxy
uuid 05227ea0-50bb-11e3-ac69-0002a5d5c51b
libsw {
Placement is everything with this. If there's an extra space or missing a space you'll will get the "drivers are not installed" error when opening the viper app. It took me several tries in the beginning to get the audio_effects.conf part of this right, but it will work when everything is correct.
4. This step is dependent on your setup. If you are using a permissive kernel this is not necessary. If you're using SuperSU with an enforcing kernel you'll need to flash the ViPER4Android-supolicy.zip that is included in the attached zip file.
Original instructions are here, but nobody seems to see them including myself for the longest time.
Now if everything is in place properly you should get this:
It should work with any music player (I mostly use Spotify), YouTube, video players, etc.
Enjoy.
Credits:
@viper520 -for creating Viper4android
@zhuhang - for co-founding and continuing to maintain Viper4android
If anyone knows the identity of who created the ViPER4Android-supolicy.zip let me know. I would love to be able to give proper credits on that as well.
Thanks Mate Nice thread
Hi kevintm78, I have some questions.
1. In your Driver Status screen shoot you have Processing:Yes, I have Processing:No, what does that mean for me?
2. It is said to install or move Viper to System/app, does System/priv-app location achieve the same as System/app?
3. I've heard it said that using DDC and Convolver together is not adviseable, is this true?
4. where can I find/download more DDC profiles?
5. I'm on a Note 4 Android version 6.0.1 Rom: NEMESIS REFINED N7 port, on odd occasions after using the built-in "Smart
Manager app, viper's profile folder contents sometimes disappear, although the DDC and Kernel folders will remain intact.
Would you have ant idea why this happens? That said, I have found that if I delete the Cache and Data of the Smart Manager app, the Viper Profile folder contents will remain more often but as mentioned, they will disappear
6. On rare occasions the "Load effect profile" List would be in alphabetical order, is there a way to force this?
I would appreciat your thoughts and help for the questions mentioned.
Many Thanks for Your tutorial.
asia559571 said:
Hi kevintm78, I have some questions.
1. In your Driver Status screen shoot you have Processing:Yes, I have Processing:No, what does that mean for me?
2. It is said to install or move Viper to System/app, does System/priv-app location achieve the same as System/app?
3. I've heard it said that using DDC and Convolver together is not adviseable, is this true?
4. where can I find/download more DDC profiles?
5. I'm on a Note 4 Android version 6.0.1 Rom: NEMESIS REFINED N7 port, on odd occasions after using the built-in "Smart
Manager app, viper's profile folder contents sometimes disappear, although the DDC and Kernel folders will remain intact.
Would you have ant idea why this happens? That said, I have found that if I delete the Cache and Data of the Smart Manager app, the Viper Profile folder contents will remain more often but as mentioned, they will disappear
I would appreciat your thoughts and help for the questions mentioned.
Many Thanks for Your tutorial.
Click to expand...
Click to collapse
You're very welcome. I think I can help with some of your questions.
1. For processing, it will say no unless there's something playing. Try playing a song and then checking it again.
2. You can use priv-app if you'd like. The only difference between the two is that priv-apps are given more system permissions than just /system/app. The results should be the same though with either one.
3. I've been using them together and haven't noticed any negative impact. I'll see if I can find out more on that though, but you should be fine.
4. I think what you're looking for is IRS packages. You can find out more about it here. You can also download the starter IRS packs here. Viper4android has depricated they're XHFI features so I'm not sure that more DDC profiles are helpful anymore (though I could be completely wrong about that.) Most of the other DDC profiles I've found are at least a few years old now.
5. That's strange that they are being removed. Are the folders empty? Maybe that's why they are being removed. Try downloading the IRS starter pack, unzip it, and move the whole folder to the Viper4android/kernel folder on your sdcard. To get that folder to show up just press on the Convolver setting and it should create those folders for you. That's about the only reason I could think of as to why they are being removed.
Thank you by the way for asking those questions. That's something I need to cover a little more thoroughly. I definitely will expand on this topic if it looks like people are interested.
Thank you so much it works! but only for certain music player, i tried it with Phonograph and Samsung's stock music player and it works.
It doesn't work with spotify. I did the exact step you mentioned. I using note 4 exynos eRobot v33. any ideas why?
damadikaz said:
Thank you so much it works! but only for certain music player, i tried it with Phonograph and Samsung's stock music player and it works.
It doesn't work with spotify. I did the exact step you mentioned. I using note 4 exynos eRobot v33. any ideas why?
Click to expand...
Click to collapse
That's strange, Spotify is kind of the only music player I use. What does the driver status say when Spotify is playing? Did it say it's processing while the music is playing?
kevintm78 said:
That's strange, Spotify is kind of the only music player I use. What does the driver status say when Spotify is playing? Did it say it's processing while the music is playing?
Click to expand...
Click to collapse
I've attached the screenshot. pls check it.
I just check it with another streaming music player called Joox, V4A doesn't work either.
but when I play any local music files even using Solid File manager V4A works.
thnx for the explaination sir.. i have a question, why V4A not "active" after reboot..? i have to manually open the app to make it work every time after reboot.. thnx..
Same problem here. N910c with erobot v33 rom with native viper, magisk, permissive kernel, etc. And still, no processing with Spotify or deezer. Local files are processed.
Deleted
Danielreo said:
Same problem here. N910c with erobot v33 rom with native viper, magisk, permissive kernel, etc. And still, no processing with Spotify or deezer. Local files are processed.
Click to expand...
Click to collapse
Try to freeze soundalive
1.Install Viper as system App & start up app and load preferred version of driver
2.Update build.prop: root/system/build.prop
## ViPER4Android Build.prop Tweaks
lpa.decode=false
lpa.releaselock=false
lpa.use-stagefright=false
tunnel.decode=false
Nothing of the above worked here.
Even before the suggested configs, I realized that the bluetooth mode is processing like a charm. Phone speaker and headset still not.
I've followed your step by step (twice), and V4A still asks me to install the drivers...
I placed the apk on system/priv-app (the 1st attempt was on system/app), put the .so files on system/lib/soundfx, replaced the audio.conf on system/etc, changed the permissions exaclty to rw-r-r, then used TWRP Recovery mode to install the SU Policy - even though I have a selinux changer.
On Default Storage, the only option I have to set is "/storage/emulated/0/", not sure if this matters (I think it doesn't, probably it's just where it'll save your profiles etc).
Tried restarting the phone, to see if it would detect, tried to switch compatible/normal, deactivated selinux (using v4a dev mode), tried to change the permissions to rwx-rx-rx... nothing worked. V4A still asks me for the drivers.
It does work, however I install it, but only on compatible mode, and not with Spotify LOCAL synced files - which is a great issue to me.
PS.: I have NoozXoide installed here - cause it's the only one which also works with local files on Spotify. I've already tried to unninstal it and redo all the procedures, though...
OH, also, should I deactivate Android stock Audio effects app?
Can you help me please OP?
mateusonego said:
I've followed your step by step (twice), and V4A still asks me to install the drivers...
I placed the apk on system/priv-app (the 1st attempt was on system/app), put the .so files on system/lib/soundfx, replaced the audio.conf on system/etc, changed the permissions exaclty to rw-r-r, then used TWRP Recovery mode to install the SU Policy - even though I have a selinux changer.
On Default Storage, the only option I have to set is "/storage/emulated/0/", not sure if this matters (I think it doesn't, probably it's just where it'll save your profiles etc).
Tried restarting the phone, to see if it would detect, tried to switch compatible/normal, deactivated selinux (using v4a dev mode), tried to change the permissions to rwx-rx-rx... nothing worked. V4A still asks me for the drivers.
It does work, however I install it, but only on compatible mode, and not with Spotify LOCAL synced files - which is a great issue to me.
PS.: I have NoozXoide installed here - cause it's the only one which also works with local files on Spotify. I've already tried to unninstal it and redo all the procedures, though...
OH, also, should I deactivate Android stock Audio effects app?
Can you help me please OP?
Click to expand...
Click to collapse
Are you using magisk or supersu? Also, I've recently found a secondary spot for the libs and audio-effects.conf if using certain port roms. If using a stock rom that's enforcing, I would supersu and the su policy file.
If it is a stock rom I never had to freeze or uninstall anything to get it fully working. But I can help you get it going if you're still up for it.
kevintm78 said:
Are you using magisk or supersu? Also, I've recently found a secondary spot for the libs and audio-effects.conf if using certain port roms. If using a stock rom that's enforcing, I would supersu, and I flashed the su policy file.
If it is a stock rom I never had to freeze or uninstall anything to get it fully working. But I can help you get it going if you're still up for it.
Click to expand...
Click to collapse
Thank you very much for replying mate!! :angel: And sorry for misinforming.
I have a Moto G4 Plus (XT1360) with stock Android 7.0 (never rooted this device before - but I used V4A back in 2015, in a s.g. 4 mini), TWRP, Elemental X, supersu and busybox, if that matters... It was supposed to be enforcing, but I also got SELinuxModeChanger. I tried installing V4A on both system/apps & system/priv-apps. Oh, and I'm listening through headset.
I tried several combinations to try to "trick" the app, tried install drivers > deleted them, tried not to install, tried not to install > use on compatible mode/normal, tried install > renamed the .so provided here ones as the original isc... tried all again restarting my phone between steps, tried all the mentioned them then reflash supolicy, tried all and killing the selinux on dev-mode before playing songs, tried the Build.prop Tweaks... nothing worked, every time I open V4A, it asks to install the drivers. And it does work afterwards, but only on Compatible, and with Spotify, and not the local files, neither Youtube etc.
I was taking a look on the apk with ES exp, I know **** about android, but there seems to be 4 .so files inside... would there be any way to reference all the 4 on audio.conf?
Oh, I shoul mention I also tried all that I mentioned above, but replacing the files with the 4 ones I extracted from the apk between steps etc - it didn't ask for install drivers when I started it! But again, only worked on Compatible, etc...
I did some research - and got nothing -, saw some people mentioning to freeze Sound Alive, or even delete it. As I mentioned, the stock eq I got is Audio Effects, but I also saw sometimes soundalive on audios.conf... but again, I know **** about Android :/
Tks to be trying to help!
mateusonego said:
Thank you very much for replying mate!! :angel: And sorry for misinforming.
I have a Moto G4 Plus (XT1360) with stock Android 7.0 (never rooted this device before - but I used V4A back in 2015, in a s.g. 4 mini), TWRP, Elemental X, supersu and busybox, if that matters... It was supposed to be enforcing, but I also got SELinuxModeChanger. I tried installing V4A on both system/apps & system/priv-apps. Oh, and I'm listening through headset.
I tried several combinations to try to "trick" the app, tried install drivers > deleted them, tried not to install, tried not to install > use on compatible mode/normal, tried install > renamed the .so provided here ones as the original isc... tried all again restarting my phone between steps, tried all the mentioned them then reflash supolicy, tried all and killing the selinux on dev-mode before playing songs, tried the Build.prop Tweaks... nothing worked, every time I open V4A, it asks to install the drivers. And it does work afterwards, but only on Compatible, and with Spotify, and not the local files, neither Youtube etc.
I was taking a look on the apk with ES exp, I know **** about android, but there seems to be 4 .so files inside... would there be any way to reference all the 4 on audio.conf?
Oh, I shoul mention I also tried all that I mentioned above, but replacing the files with the 4 ones I extracted from the apk between steps etc - it didn't ask for install drivers when I started it! But again, only worked on Compatible, etc...
I did some research - and got nothing -, saw some people mentioning to freeze Sound Alive, or even delete it. As I mentioned, the stock eq I got is Audio Effects, but I also saw sometimes soundalive on audios.conf... but again, I know **** about Android :/
Tks to be trying to help!
Click to expand...
Click to collapse
Do you have an etc folder in /system/vendor/ ? Some roms have another audio_effects.conf in that location or maybe it's in another location. I have to be honest I'm not familiar with many other kinds of phones besides samsung.
The instructions I'm using are the ones taken from the viper4android thread itself and works with at least this phone with no other steps necessary. Maybe you can find some hints in that thread but I'm thinking that the conf file is either in another location or its different from samsung's version so it's not being found.
The other lib files inside the app aren't necessary. They are just there for different android versions. One set is for ICS and below and the other is for JB and above. The app installs the ICS drivers by default which is why I like using this method instead.
If you want, upload your original audio_effects.conf file. I'll try and modify it for you and see if we can figure out why the drivers aren't being found.
kevintm78 said:
Do you have an etc folder in /system/vendor/ ? Some roms have another audio_effects.conf in that location or maybe it's in another location. I have to be honest I'm not familiar with many other kinds of phones besides samsung.
The instructions I'm using are the ones taken from the viper4android thread itself and works with at least this phone with no other steps necessary. Maybe you can find some hints in that thread but I'm thinking that the conf file is either in another location or its different from samsung's version so it's not being found.
The other lib files inside the app aren't necessary. They are just there for different android versions. One set is for ICS and below and the other is for JB and above. The app installs the ICS drivers by default which is why I like using this method instead.
If you want, upload your original audio_effects.conf file. I'll try and modify it for you and see if we can figure out why the drivers aren't being found.
Click to expand...
Click to collapse
Wow, that was right on spot! I had another audio_effects conf on vendor/etc. So, I replaced it with yours.
I removed the excessive .so I put on the lib/soundfx, and let only the jb and, later, the ics file.
Now, Viper asks me to install the drivers even after I've already let it install and rebooted :/ and for some reason, it doesn't work both on normal nor compatible mode (ok, as expected, since it's asking to install etc). I checked to see if it had rewrite anything on audio_effects.conf, but it didn't in neither of the files, on system/etc nor vendor/etc. They were still pointing the libraries to the jb files, and v4a did install the ics files on system/lib/soundfx, either way...
It gets weirder and weirder.
UPDATE: I got V4A to work once I commented the jb drivers lines, and re-included the ics path reference on audio_effects.conf at vendor/etc. It's not asking me to install the drivers again, anymore, but it's still not working with local synced files... I tried leaving it pointing to 2 paths, and tried including v4a_neon or something like that, so I could reference the 2 most important drivers, but it only works with v4a_fx pointing only to the ics file, and everything else is ignored.
UPDATE 2: I opened the backup I've mentioned below, and unfortunately I'm pretty sure I haven't done the backup and it is actually your file before I do any mod.
I'm sending you what I THINK is my backup but it might be just a backup of yours before I changed some stuff just to test (I replaced my modified files by copying the original one I had on downloads after testing, I got back to yours version on both /etc), sorry. (don't think so, though)
@kevintm78 hey OP, you there?
kevintm78 said:
Viper4android: How to install it properly
This is something I've been meaning to write up for a long time now. All over XDA I see people have trouble with getting Viper4android working and I thought this might shed some light on the issue.
There are many zips out there that will install viper but most of them have other sound mods rolled into it and I prefer viper only. I find that most of the others often distort the sound a little, but with Viper4android only, the sound is just perfect for my tastes.
What you need:
- A root file explorer (RootExplorer, EsFileExplorer, etc.)
- Root (obviously)- Either Magisk or SuperSU
- If using Magisk you'll need a Permissive kernel. My kernel works with certain models and is permissive.
- If using SuperSU you can use enforcing, but will need an extra file that I'll cover later on.
- Some good music to listen to.
This method is really not much of revelation since it's actually on the Viper4android thread itself, but almost everyone tries to let the install the drivers automatically. Do not let the app install the drivers for you. It will install the old driver and it doesn't include the Neon driver.
First things first. We need to do a little cleanup just in case there are already some viper files or drivers partially installed.
Viper4android has three places in which it installs:
/system/lib/soundfx/
/system/etc/audio_effects.conf
/system/app/Viper4android.apk
View attachment 4308261
View attachment 4308262
View attachment 4308263
View attachment 4308264
View attachment 4308265
Using your root explorer go to /system/lib/soundfx/ and look for any old V4A files and delete them. It should look like this, libv4a_fx_ics_X86.so. Also check in your system/app/ and check to see if you have the old viper app and if so delete that too (the newest version is 2.5.0.5). Note: if you already have the app installed you can go to the settings menu and select uninstall drivers and it should remove everything for you. Then just double check to make sure. Then uninstall the app unless it's the newest version and placed in /system/app/.
Once we have everything cleaned up it's just a matter of placing the right files in the right spot. I've attached a zip that has everything you will need in it. It is not a flashable zip. Just unzip it to get to the necessary files.
1. Place the Viper4android app in /system/app (no extra folder necessary) and change the permission to 0644 or rw-r-r
2. Place the .so files in /system/lib/soundfx/ and change permission to 0644 or rw-r-r
3. If you don't have any other sound mods installed you can swap out my audio_effects.conf file for yours and set permission to 0644 or rw-r-r, but if you do that back up your original file just in case (just rename the original to audio_effects.bak). If you do have other sound mods installed you'll want to add the following red lines to you existing audio_effects.conf file.
Code:
# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {
[COLOR="red"]v4a_fx {
path /system/lib/soundfx/libv4a_fx_jb_NEON.so
}
#NECESSARY FOR XHIFI
v4a_xhifi {
path /system/lib/soundfx/libv4a_fx_jb_X86.so
}[/COLOR]
# This is a proxy library that will be an abstraction for
# the HW and SW effects
proxy {
path /system/lib/soundfx/libeffectproxy.so
}
# This is the HW implementation library for the effect
offload {
path /system/lib/soundfx/libaudioeffectoffload.so
And...
Code:
# }
# ...
# }
effects {
[COLOR="red"]v4a_standard_fx {
library v4a_fx
uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b
}
#NECESSARY FOR XHIFI
v4a_standard_xhifi {
library v4a_xhifi
uuid d92c3a90-3e26-11e2-a25f-0800200c9a66
}
}[/COLOR]
soundalive {
library proxy
uuid 05227ea0-50bb-11e3-ac69-0002a5d5c51b
libsw {
Placement is everything with this. If there's an extra space or missing a space you'll will get the "drivers are not installed" error when opening the viper app. It took me several tries in the beginning to get the audio_effects.conf part of this right, but it will work when everything is correct.
4. This step is dependent on your setup. If you are using a permissive kernel this is not necessary. If you're using SuperSU with an enforcing kernel you'll need to flash the ViPER4Android-supolicy.zip that is included in the attached zip file.
Original instructions are here, but nobody seems to see them including myself for the longest time.
Now if everything is in place properly you should get this:
View attachment 4308290
It should work with any music player (I mostly use Spotify), YouTube, video players, etc.
Enjoy.
Credits:
@viper520 -for creating Viper4android
@zhuhang - for co-founding and continuing to maintain Viper4android
If anyone knows the identity of who created the ViPER4Android-supolicy.zip let me know. I would love to be able to give proper credits on that as well.
Click to expand...
Click to collapse
This worked for me.
You did not mention where to insert the audio_effects.contf file ... this file should be placed in the /vendor/etc
also you did not state that we would have to install the app after placing it in the /system/app.
Thanks once again