Related
What you will need:
To be on Lollipop WITH root (go here if you need to flash the rooted ROM)
BusyBox to be installed (it should already be installed on the rooted ROM, if not then search the Play Store or use your favorite one)
A copy of Viper4Android v2.3.4.0 (Download from here)
A file browser that can access the /system partition and change permissions (I prefer ES File Explorer but you can use whatever you like)
Titanium Backup (or you can use the application manager in the Settings app)
Firstly, what you will need to do is use your file browser and create a folder called "Viper4Android" in your /system/priv-app/ folder. Set the permission for this folder to rwxr-xr-x or 0755, then paste your Viper4Android APK into the folder you created and set the permission for the APK to rwxrwxrwx or 0777, with root being owner and group for both folder and APK.
Secondly, what you will need to do is browse to /system/etc/ with your file browser and open the file init.qcom.post_boot.sh and at the very bottom of the file paste this:
Code:
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
It is imperative that you make sure you are using Unix line endings instead of anything else.
Thirdly, use Titanium Backup or the Application Manager to freeze SoundAlive, as all music apps will attempt to default to it. Also you may want to freeze the Adapt Sound app, as if you enable it will then be used over V4A.
Lastly, reboot your phone and then install the drivers and reboot one last time. I can confirm that it works on Play Music, and that it doesn't work on the stock Music player (however I believe there is a way to get it to work somewhere on the internet).
Problems:
Viper4Android fails at installing!
Click to expand...
Click to collapse
You are to create it as a system app, so follow the first step.
Viper4Android doesn't appear!
Click to expand...
Click to collapse
Make sure you followed the first step correctly and set the proper permissions.
Viper4Android still says Abnormal and Unsupported in the status!
Click to expand...
Click to collapse
Make sure you pasted the command into the init.qcom.post_boot.sh file and that you used Unix line endings, as using DOS or Mac line endings add extra characters that Android will try to parse as actual text.
Viper4Android says that BusyBox isn't installed!
Click to expand...
Click to collapse
This bug happens sometimes, I found the best way to beat it is to open your BusyBox app and just put it in the background and try the driver installation again.
I enabled everything and my music still sounds the same!
Click to expand...
Click to collapse
Make sure you freeze SoundAlive and Adapt Sound, as they will be used before Viper4Android, also you may need to put V4A into Compatibility mode to use with certain music players. Also you can't use the stock Music player (but I think there is a way somewhere on the internet).
My phone broke and won't boot!
Click to expand...
Click to collapse
Then you may want to wait until a recovery flashable zip is made, but at no point are the steps going to brick your phone, you can just boot to Safestrap or flash back.
Notes:
This process can probably be done very easily with a init.d script and a recovery flashable zip, but I currently don't have the time and don't want to risk screwing up someone's phone.
You can use any other Viper4Android mod, as long as it is v2.3.4.0, I prefer this version which looks very nice. You can extract the file from the zip attachment and just follow the steps here.
You do not need to have SELinux set to permissive, as even with using MultiSystem to set it to permissive, it still didn't work until the above command is used.
I haven't tested whether effects like convolver or DDC work, but they should.
Thanks to:
@ihancioglu for the code that allows it to work
@nappent for most of the steps needed to get it running
EXTRA:
Here is an init.d script that will do the bypass for you, however, you must have init.d support. As it stands right now, Walter.White's Lollipop ROM does not have init.d, if you want to enable init.d, you have to add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc.
Script: https://mega.nz/#!ZpIUCbrb!QONi8bWb1afE47_JnwxgpBcXoKFuPG3mpnyFX4r83G0
What process did you use to be able to write to the root. I can not gain root access even though i have su, busybox, and several other apps with root access. I have tried using ES File explorer with no success. It will not access the root of the device.
---------- Post added at 09:31 PM ---------- Previous post was at 08:35 PM ----------
100% verified and working. Big thanks!!!
Works perfectly. Thanks for this work around OP!
Any thoughts on using NuPlayer vs. AwesomePlayer in dev. options?
{
"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"
}
joshuaburnsjr said:
What process did you use to be able to write to the root. I can not gain root access even though i have su, busybox, and several other apps with root access. I have tried using ES File explorer with no success. It will not access the root of the device.
---------- Post added at 09:31 PM ---------- Previous post was at 08:35 PM ----------
100% verified and working. Big thanks!!!
Click to expand...
Click to collapse
Root Browser worked for me.
KTownGT said:
Any thoughts on using NuPlayer vs. AwesomePlayer in dev. options?.
Click to expand...
Click to collapse
I use NuPlayer, but to be honest I haven't seen or heard of any difference. Some guides say that disabling NuPlayer will allow V4A to work, but V4A has worked just perfectly fine with NuPlayer enabled.
Among other things, creating a recovery flashable zip has fallen through. I have come across a problem where I can't modify init.qcom.post_boot.sh from a recovery, be it SafeStrap or FlashFire. I have also discovered something else, init.d support was supposed to be included with Walter.White's Lollipop ROM, but his script encountered the same problem as me, it couldn't append to init.qcom.post_boot.sh. So right now anyone using his ROM does not have init.d setup, luckily, it can be very easily enabled. All you have to do is add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc and you are good to go. I have attached an init.d script to the main post that can make use of init.d and do the bypass.
Namelesswonder said:
I use NuPlayer, but to be honest I haven't seen or heard of any difference. Some guides say that disabling NuPlayer will allow V4A to work, but V4A has worked just perfectly fine with NuPlayer enabled.
Click to expand...
Click to collapse
Exactly why I asked... lol
Looks like it is only required when setting SELinux to permissive; which doesn't appear to be required. You literally saved me from going back to 4.4.2, just for V4A btw:good:
Namelesswonder said:
Among other things, creating a recovery flashable zip has fallen through. I have come across a problem where I can't modify init.qcom.post_boot.sh from a recovery, be it SafeStrap or FlashFire. I have also discovered something else, init.d support was supposed to be included with Walter.White's Lollipop ROM, but his script encountered the same problem as me, it couldn't append to init.qcom.post_boot.sh. So right now anyone using his ROM does not have init.d setup, luckily, it can be very easily enabled. All you have to do is add
Code:
/system/etc/init.d*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc and you are good to go. I have attached an init.d script to the main post that can make use of init.d and do the bypass.
Click to expand...
Click to collapse
Answers my second question about init.d. :good:
Have been debating whether to stay on Alliance or go back to OTA, seeing as how I don't use the customization settings & need NFC
KTownGT said:
Exactly why I asked... lol
Looks like it is only required when setting SELinux to permissive; which doesn't appear to be required. You literally saved me from going back to 4.4.2, just for V4A btw:good:
Answers my second question about init.d. :good:
Have been debating whether to stay on Alliance or go back to OTA, seeing as how I don't use the customization settings & need NFC
Click to expand...
Click to collapse
I originally stayed off of Lollipop for a month because I couldn't get V4A to work, but I tried to find a solution after people got it working on the Galaxy S6.
I made this guide because using MultiSystem to set SELinux to permissive did not fix the issue. It was like the policies for SELinux were still being enforced. Also, I made a mistake for the init.d code, it should be
Code:
/system/etc/init.d/*
. Currently stock rooted Lollipop is ok, with Xposed now working and Wanam just recently updated you can make stock usable now.
Namelesswonder said:
I originally stayed off of Lollipop for a month because I couldn't get V4A to work, but I tried to find a solution after people got it working on the Galaxy S6.
I made this guide because using MultiSystem to set SELinux to permissive did not fix the issue. It was like the policies for SELinux were still being enforced. Also, I made a mistake for the init.d code, it should be
Code:
/system/etc/init.d/*
. Currently stock rooted Lollipop is ok, with Xposed now working and Wanam just recently updated you can make stock usable now.
Click to expand...
Click to collapse
Same pretty much. It's painful going from using V4A & a USBDAC to straight LP.
working perfectly.. thanks
Works amazing jus one question the download from mediafire has two different apps both the same version which should I have installed
Works for me! Thanks.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Orion.Lamas said:
Works amazing jus one question the download from mediafire has two different apps both the same version which should I have installed
Click to expand...
Click to collapse
On V4A's website?
There should be an APK for before JB, and one for KK/LP. You should use the one that's like"V4A_FX_4.x.apk"
Sent from my iPad using Tapatalk
Thanks OP! Got it all working and the sound quality has definitely improved. Question though, in past versions I loved adjusting the IRSamples. Is that no longer a thing in this latest version?
Viper4android worked again!
Namelesswonder said:
What you will need:
To be on Lollipop WITH root (go here if you need to flash the rooted ROM)
BusyBox to be installed (it should already be installed on the rooted ROM, if not then search the Play Store or use your favorite one)
A copy of Viper4Android v2.3.4.0 (Download from here)
A file browser that can access the /system partition and change permissions (I prefer ES File Explorer but you can use whatever you like)
Titanium Backup (or you can use the application manager in the Settings app)
Firstly, what you will need to do is use your file browser and create a folder called "Viper4Android" in your /system/priv-app/ folder. Set the permission for this folder to rwxr-xr-x or 0755, then paste your Viper4Android APK into the folder you created and set the permission for the APK to rwxrwxrwx or 0777, with root being owner and group for both folder and APK.
Secondly, what you will need to do is browse to /system/etc/ with your file browser and open the file init.qcom.post_boot.sh and at the very bottom of the file paste this:
Code:
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
It is imperative that you make sure you are using Unix line endings instead of anything else.
Thirdly, use Titanium Backup or the Application Manager to freeze SoundAlive, as all music apps will attempt to default to it. Also you may want to freeze the Adapt Sound app, as if you enable it will then be used over V4A.
Lastly, reboot your phone and then install the drivers and reboot one last time. I can confirm that it works on Play Music, and that it doesn't work on the stock Music player (however I believe there is a way to get it to work somewhere on the internet).
Problems:
You are to create it as a system app, so follow the first step.
Make sure you followed the first step correctly and set the proper permissions.
Make sure you pasted the command into the init.qcom.post_boot.sh file and that you used Unix line endings, as using DOS or Mac line endings add extra characters that Android will try to parse as actual text.
This bug happens sometimes, I found the best way to beat it is to open your BusyBox app and just put it in the background and try the driver installation again.
Make sure you freeze SoundAlive and Adapt Sound, as they will be used before Viper4Android, also you may need to put V4A into Compatibility mode to use with certain music players. Also you can't use the stock Music player (but I think there is a way somewhere on the internet).
Then you may want to wait until a recovery flashable zip is made, but at no point are the steps going to brick your phone, you can just boot to Safestrap or flash back.
Notes:
This process can probably be done very easily with a init.d script and a recovery flashable zip, but I currently don't have the time and don't want to risk screwing up someone's phone.
You can use any other Viper4Android mod, as long as it is v2.3.4.0, I prefer this version which looks very nice. You can extract the file from the zip attachment and just follow the steps here.
You do not need to have SELinux set to permissive, as even with using MultiSystem to set it to permissive, it still didn't work until the above command is used.
I haven't tested whether effects like convolver or DDC work, but they should.
Thanks to:
@ihancioglu for the code that allows it to work
@nappent for most of the steps needed to get it running
EXTRA:
Here is an init.d script that will do the bypass for you, however, you must have init.d support. As it stands right now, Walter.White's Lollipop ROM does not have init.d, if you want to enable init.d, you have to add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc.
Script: https://mega.nz/#!ZpIUCbrb!QONi8bWb1afE47_JnwxgpBcXoKFuPG3mpnyFX4r83G0
Click to expand...
Click to collapse
I used link2sd to covert music & video players from system to user apps & viper4android worked greatly!
SilverStone641 said:
Thanks OP! Got it all working and the sound quality has definitely improved. Question though, in past versions I loved adjusting the IRSamples. Is that no longer a thing in this latest version?
Click to expand...
Click to collapse
Working here. Did you change the UI setting?
Sent from my SAMSUNG-SM-N900A using Tapatalk
hllah66 said:
I used link2sd to covert music & video players from system to user apps & viper4android worked greatly!
Click to expand...
Click to collapse
Good to know that is what you have to do to get V4A working on stock Music and Video Player. I don't know if that would bring up any issue, but nice find.
Works like a charm on AllianceROM Lollipop v9.1 Extreme Customisation 05.24.2015 :victory:
KTownGT said:
Working here. Did you change the UI setting?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Interesting. I don't have that option at all in my interface. I haven't adjusted any UI settings either. Is there another component that needs installing?
SilverStone641 said:
Interesting. I don't have that option at all in my interface. I haven't adjusted any UI settings either. Is there another component that needs installing?
Click to expand...
Click to collapse
Open V4A --> tap settings --> tap "UI Settings" --> Tap "Expert". Should have it after that
KTownGT said:
Open V4A --> tap settings --> tap "UI Settings" --> Tap "Expert". Should have it after that
Click to expand...
Click to collapse
MY HERO!! Thank you so much!! I've got all my favorite settings options back plus it sounds even better! Thank you!!
Namelesswonder said:
Good to know that is what you have to do to get V4A working on stock Music and Video Player. I don't know if that would bring up any issue, but nice find.
Click to expand...
Click to collapse
Hello...
How is that accomplished?
They can be detailed the activities necessary to achieve this?
Thanks!!!
Hey guys, i quite unfortunately own a galaxy a8 (a800i). It has almost no dev support. After rooting my phone, i tried converting an app to system(through limk2sd). It did but when i rebooted my phone the app disappeared! Had to manually locate the system files (yes they were there, including the apk) and delete them.
Again,tried it with titanium backup, didnt work out.
Also tried moving the folders manually and i took care to set the correct permissions, the app just wouldnt appear.
At last, after deleting all the system app data and files again, i finally placed the apk with correct permissions in the/system/app folder and rebooted my phone. The app was there but it was force closing.
I tried doing this with 4 different apps, to no avail.
I run stock firmware.
(please note- Although a800F and A800i have same hardware, a800i will not support the others custom recovery, root methods,kernels etc.)
Any devs who might be interested in this? Id be glad.
You need to create a folder with the same name as the apk and push the folder to system app.
Then put apk in the folder with same name
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
You need to create a folder with the same name as the apk and push the folder to system app.
Then put apk in the folder with same name
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Tried that too, been working on this since 2 days. Nothing seems to work. I have never encountered an error like this before on any other of my devices. All the pre installed system apps are odexed, and the one im trying is not, for obvious reasons. Do you think it has got something to do with the error?
abhinavparasher said:
Tried that too, been working on this since 2 days. Nothing seems to work. I have never encountered an error like this before on any other of my devices. All the pre installed system apps are odexed, and the one im trying is not, for obvious reasons. Do you think it has got something to do with the error?
Click to expand...
Click to collapse
Hmm missing Libs? Or the odex file itself?
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
Hmm missing Libs? Or the odex file itself?
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
No, the lib and the .dex file of the user app im trying to move to system is intact, all im trying to ask is that do you think the system is not accepting the converted app because it has a .dex instead of the regular .odex file which is the case with all system apps?
This assumption might be wild, but considering that i have never faced such an issue before in 10-12 android devices that i have owned in the past, it might be of some use.
abhinavparasher said:
No, the lib and the .dex file of the user app im trying to move to system is intact, all im trying to ask is that do you think the system is not accepting the converted app because it has a .dex instead of the regular .odex file which is the case with all system apps?
This assumption might be wild, but considering that i have never faced such an issue before in 10-12 android devices that i have owned in the past, it might be of some use.
Click to expand...
Click to collapse
Has nothing do do with it, if it's a "user app" as long if the app has all needed files in correct folder it should run. it should be working if it doesn't it might be any issue that the app won't run while in system/app
Sent from my SM-G903F using Tapatalk
So for now, we havnt arrive to any conclusion. All apps break if they are converted to system apps. Tried to do it via TB/Link2sd/various other tools and manually. App components are present in /system/app including the apk and lib, but the app wont appear anywhere on the phone.
abhinavparasher said:
So for now, we havnt arrive to any conclusion. All apps break if they are converted to system apps. Tried to do it via TB/Link2sd/various other tools and manually. App components are present in /system/app including the apk and lib, but the app wont appear anywhere on the phone.
Click to expand...
Click to collapse
That's because it has to be placed inside a folder with the same name as the app
Like /system/app/viper/viper.apk
It can't be /system/app/viper/base.apk
Also libs should be in
System/app/viper/lib/arm/*****.so
Hope this issue helps
Sent from my SM-G903F using Tapatalk
i did try this before. tried it again. It doesnt work. I was extremely careful with directries, app names, libs and permissions.
Like ive said iv done this countless times before on other devices, and it has always worked.
Something else i would like to mention- Thought the app shortcut doesnt appear anywhere, whenever i open the apk file (on my sd card) it says "do you want to update the app" which means the app is actually already installed. I click yes and the app is installed, app icon returns.
I open application manager and open up this app's settings. I get the option of "Uninstall updates" instead of uninstall apps which proves the first time i moved to system, the app became a system app but it disappeared. If i click uninstall updates, the app disappears again. If i try to integrate update with link2sd the app disappears any ways.
There is just no reason for this to happen! So basically im stuck with a phone which barely got a root method, doesnt have a custom recovery, has a enforcing kernel, and doesnt allow me to move apps to /system.
Do you think it might be possible to "flash" the app zip file via a custom recovery? (if we get one for a800i lol)
abhinavparasher said:
i did try this before. tried it again. It doesnt work. I was extremely careful with directries, app names, libs and permissions.
Like ive said iv done this countless times before on other devices, and it has always worked.
Something else i would like to mention- Thought the app shortcut doesnt appear anywhere, whenever i open the apk file (on my sd card) it says "do you want to update the app" which means the app is actually already installed. I click yes and the app is installed, app icon returns.
I open application manager and open up this app's settings. I get the option of "Uninstall updates" instead of uninstall apps which proves the first time i moved to system, the app became a system app but it disappeared. If i click uninstall updates, the app disappears again. If i try to integrate update with link2sd the app disappears any ways.
There is just no reason for this to happen! So basically im stuck with a phone which barely got a root method, doesnt have a custom recovery, has a enforcing kernel, and doesnt allow me to move apps to /system.
Do you think it might be possible to "flash" the app zip file via a custom recovery? (if we get one for a800i lol)
Click to expand...
Click to collapse
Well to be honest I did face same issue with Samsung s health I'm not sure what causes it, can be system related or something.
Don't you have spacex kernel which is set to permissive?
Sent from my SM-G903F using Tapatalk
The only difference is that it happens with me for every app lol.
I did hear about it but im pretty sure its for a800F. Anything related to a800F causes a bootloop in a800i. Someone on the forum tried the spacex kernel. Do you think you can make it compatible somehow?
If nothing works i might just compile a kernel with always_enforce set to false. Then i should be able to change the policy to permissive with seteneforce 0 command.
abhinavparasher said:
The only difference is that it happens with me for every app lol.
I did hear about it but im pretty sure its for a800F. Anything related to a800F causes a bootloop in a800i. Someone on the forum tried the spacex kernel. Do you think you can make it compatible somehow?
If nothing works i might just compile a kernel with always_enforce set to false. Then i should be able to change the policy to permissive with seteneforce 0 command.
Click to expand...
Click to collapse
Are you the dude that's going to test twrp?
I have built a permissive kernel for this device also.
You are welcome to try it.
Sure il try that too. Permissive kernel is something that many of us need. Infact i was gonna make it. Thanks for the effort!
You can pass me the flashable tar file. In the meanwhile, il test the recovery and get back to you.
abhinavparasher said:
Sure il try that too. Permissive kernel is something that many of us need. Infact i was gonna make it. Thanks for the effort!
You can pass me the flashable tar file. In the meanwhile, il test the recovery and get back to you.
Click to expand...
Click to collapse
Here you go, flash with odin or extract the boot.img from the archive and flash with TWRP.
SM-A800I_A800IXXU2AOL2 _boot
ashyx said:
Here you go, flash with odin or extract the boot.img from the archive and flash with TWRP.
SM-A800I_A800IXXU2AOL2 _boot
Click to expand...
Click to collapse
The kernel works perfectly! Root+ selinux set to permissive. Flashed the boot.img with the twrp recovery provided by @ashyx . The recovery as well as the kernel work with no issue whatsoever. The problem with the wifi did not occur this time. Must be related to the old kernel i flashed, it somehow changed the build.prop everytime i flashed something (Including the recovery)
Anyways, now we know that the kernel as well as the recovery works as it should.
I think you should make the post official, recovery as well as root+selinux set to permissive.
Thanks!
abhinavparasher said:
The kernel works perfectly! Root+ selinux set to permissive. Flashed the boot.img with the twrp recovery provided by @ashyx . The recovery as well as the kernel work with no issue whatsoever. The problem with the wifi did not occur this time. Must be related to the old kernel i flashed, it somehow changed the build.prop everytime i flashed something (Including the recovery)
Anyways, now we know that the kernel as well as the recovery works as it should.
I think you should make the post official, recovery as well as root+selinux set to permissive.
Thanks!
Click to expand...
Click to collapse
Released on XDA in Development section: http://forum.xda-developers.com/sam.../kernel-permissive-ll-5-11-kernel-sm-t3312817
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
:bump:
abhinavparasher said:
:bump:
Click to expand...
Click to collapse
Tried flashing your apps with twrp?
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
Tried flashing your apps with twrp?
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Yes, thats the only thing that works. This issue really garners my interest as i have never seen this happening before.
//Thank you all for 30k+ Views. You're amazing guys//
You want Android 8 with Viper4android to?
Thread created check my profile...
Hi,
at first im not responsible for anything that happens to your phone OK?
Fine Let's Start.
If you are on cm skip all until the cm section
Supported kernel list and known errors/bugs see second post
Step 1
- Flash full Factory Images.
- Install TWRP, remember you have to be decrypted.
Step 2
- Install Android 7 ROM by tupac4u / or any other rom / or leave stock
- Reboot //if nessesairy
Step 3
- Flash ElementalX's N Kernel.
- Flash Viper5.0_Stock.zip in Recovery / or any other viper
- Reboot.
Step 4
- Install driver.
- Open File Explorer and delete /system/vendor/etc/audio_effects.conf
- Reboot.
Step 5
- Set enforcing to permissive (You have to do it at every Reboot!).
- In Viper open Menu->FX-CompatibleMode->yes // you can try without, it may work
- Enjoy Viper.
CM Section
1. Flash arise sound mod ( link down below )
2. And IMPORTANT flash super su
3. Disable audio fx and reboot
SPOTIFY FIX
1. Download that file
https://drive.google.com/file/d/0BxyY1q0qeeeEeUFGT3JHeDZLZkE/view
2. Place it under /system/etc
3. Reboot
PURE NEXUS ONLY WORKS WITH BUILD 10/25!!!
If it worked leave a reply.
Alternative Download link for ARISE Viper here:
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Unsupported Rom/Kernel
Kernel:
- Stock
- Jolla
ROM:
F.A.Q.
Q: Spotify isn't working with that
A: Force enable Viper4Android and turn FX Mode to compatible. Then restart both applications.
Q: Why ElementalX Kernel?
A: That's the only Kernel who works with Viper except Stock kernel. Elite Kernel may also work but it hasent been updated since the Dev Previews.
Q: Is that also working with the stock rom?
A: Yup. Also works with (nearly) any stock based ROM.
Is there a definite way of checking if it's working? Not by sound?
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Sent from my Nexus 5X using Tapatalk
how to set permissive mode permanently?
Nightshadow931 said:
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Click to expand...
Click to collapse
I found that it isn't working on jolla Kernel and Stock.
Did you enable viper in app itself?
Not sure, but maybe you need to enable it on order to see 'processing'..
Did the installation of driver went well?
Sent from my Nexus 5X using Tapatalk
enzippo said:
how to set permissive mode permanently?
Click to expand...
Click to collapse
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Try some other app like play music, v4a won't work on all apps if they have their own equalizer.
Sent from my Nexus 5X using Tapatalk
Blinkiz said:
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Click to expand...
Click to collapse
For those who want to use Viper4android with Spotify change fx compatible Mode to compatible in Viper settings. Then Open Spotify and go to Settings->Equalizer that should bring up Viper. Select Force enable and close Viper and Spotify. Open up both again and Boom Viper is there.
How find Android 7 by tupac4u ??
EDIT.
I found him already
Did someone get it working with stock rooted ROM?
noidea24 said:
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Click to expand...
Click to collapse
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
trhacker01 said:
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
Click to expand...
Click to collapse
In gonna give it a try
Nightshadow931 said:
Did someone get it working with stock rooted ROM?
Click to expand...
Click to collapse
Me not
Thargorsson said:
In gonna give it a try
Click to expand...
Click to collapse
Nope it don't works
Thargorsson said:
Nope it don't works
Click to expand...
Click to collapse
thats how im running right now, just checked. only with the universal init.d though
noidea24 said:
thats how im running right now, just checked. only with the universal init.d though
Click to expand...
Click to collapse
Ur saying that permissive zip works with the universal init.d?
trhacker01 said:
Ur saying that permissive zip works with the universal init.d?
Click to expand...
Click to collapse
As long as the zip creates/places a file in the init.d to change selinux then i guess it should work
I've installed the newest Lineage OS, but I want to turn of "Double Tab to wake". But after one day, it automatically turned on again, but without showing it in the settings (showed that it's turned of). Now I have the question if there is any possibility to turn it off?
Thanks,
Philipp
The setting does not stick after the reboot. You have to enable it and disable it again. Then it should be really disabled until the next reboot.
Okay, thank you. I hope they will fix it soon
I think it may be because you flashed a custom kernel.
Some custom kernels break dt2w
barni090 said:
I've installed the newest Lineage OS, but I want to turn of "Double Tab to wake". But after one day, it automatically turned on again, but without showing it in the settings (showed that it's turned of). Now I have the question if there is any possibility to turn it off?
Thanks,
Philipp
Click to expand...
Click to collapse
Until they fix this you can use a script to disable it. Use init.d or any automate app to run the script at boot. It'll turn off the tap2wake.
#!/system/bin/sh
tap2wake=/proc/touchpanel/double_tap
echo "0" > $tap2wake
could you maybe tell me how to use this command? Sorry for that, but I am new in that and don't know what to do
barni090 said:
could you maybe tell me how to use this command? Sorry for that, but I am new in that and don't know what to do
Click to expand...
Click to collapse
Since you're new to this I'll give you the easiest way to do this.
1. Download the script from the link given below. (or use my last post's code to make a script yourself)
2. Put it in a folder in sdcard.
3. Install 'init.d scripts support' app from play store.
4. Open the app & tick 'try to aquire root privileges'. Grant root access.
5. Tick 'run scripts at boot time' option.
6. Set 'execution delay' to a desired time.
7. Select the folder you put the downloaded file.
Tap2wake disable script - http://www.mediafire.com/file/r4h5z8p1ez21jpi/tap2wakedis.sh
Done. Now every time you reboot, app will execute the scripts in the selected folder which contains our script to disable double tap2wake.
You can always execute the script using ini.d, su.d, tasker, macrodroid etc.
I have some problems with activating it, I've put the error message as attachment maybe you could look over it.
barni090 said:
I have some problems with activating it, I've put the error message as attachment maybe you could look over it.
Click to expand...
Click to collapse
I forgot to change the line ending to Unix. I edited the post check it again.
It's still not working, I used another app and it's telling me permission denied. But thank you for your help
barni090 said:
It's still not working, I used another app and it's telling me permission denied. But thank you for your help
Click to expand...
Click to collapse
Try the link again this time it should work. lol. I've added /bin/bash not /bin/sh. old habits. If you're using a terminal issue 'su' first then 'sh SCRIPT_PATH'.
worked now Thanks so much :victory:
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Nikish21 said:
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Best of luck. :good:
Would it work with los stock kernel?
impulsar said:
Would it work with los stock kernel?
Click to expand...
Click to collapse
No idea. I am using vegito kernel v7
riazul.islam20 said:
No idea. I am using vegito kernel v7
Click to expand...
Click to collapse
Vegito kernel by default supports dt2w right?
impulsar said:
Vegito kernel by default supports dt2w right?
Click to expand...
Click to collapse
Might be. But by default it was inactivated.
Is it possible to add screen of gestures in lenovo vibe k5
Is it possible to lock device by double taping...Just like dt2wake??
jometzz said:
Is it possible to lock device by double taping...Just like dt2wake??
Click to expand...
Click to collapse
Why not?
Just double tap on statue bar
riazul.islam20 said:
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Click to expand...
Click to collapse
It gets reset to 0 on reboot. Why?
afzalsayed96 said:
It gets reset to 0 on reboot. Why?
Click to expand...
Click to collapse
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
#!/system/bin/sh
echo 2 > /sys/android_touch/doubletap2wake
Click to expand...
Click to collapse
Android_touch
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Goutham47 said:
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Click to expand...
Click to collapse
the same here, please help
Please someone who says the correct way to do the procedure in Rom AOSP or LineageOS in 7.1.2
Someone using dt2w on oreo? Please share info if there's a way to activate it under oreo
nonline said:
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
Click to expand...
Click to collapse
bro...i m getting endless boot animation...what to do...??? plzz help