Xt907 rooted. Ss installed. I created a rom slot, backed up, and installed to stock slot.
Everything works fine but after a few reboots I lose init.d. I'm using rage-m, I update busybox and supersu after every install, and i use xposed (xblast, gravity box, and xui).
Any ideas? I lose the custom governors and schedulers as well.
Because I was losing the governors I thought somehow the kernel itself was being replaced somehow. Upon further inspection, I found that the governors and schedulers were actually an init.d script with library modules (which makes sense considering they were lost with init.d). After some trial and error I discovered that upon updating the included busybox (1.21.0) with busybox pro to the xbin or bin folder I will lose init.d support. Really curious as to why that is. Anything to do with symlinks?
infinite.galaxi said:
Xt907 rooted. Ss installed. I created a rom slot, backed up, and installed to stock slot.
Everything works fine but after a few reboots I lose init.d. I'm using rage-m, I update busybox and supersu after every install, and i use xposed (xblast, gravity box, and xui).
Any ideas? I lose the custom governors and schedulers as well.
Click to expand...
Click to collapse
You can try to install Pimp my ROM and turn init.d on
It seems that Busybox 1.22.1 is the culprit. Reverting to 1.21.1 leaves init.d intact. Thanks ^ tho pimp my rom looks cool. I want dat Bravia doe. v4a ftw!
Related
I'm running rooted 2.1 stock. Is there any way of getting this to work with init.d? I'm trying to get AFWall+ to autostart and apply on boot, and selecting for it to prevent leaks on startup appears to be the only way of doing it, but this works with an init.d script.
is there someone who succes in the installation of this app?
when i open it,it ask if i want to install the drivers and stuck and after few seconds it crash
someone can help me with this ?
Many guys use this and there already was enough discussions, there are even seperate threads created with tutorials, use search for once[emoji14]
I managed to get Viper4Android working this way:
First off, I use stock with systemless root and xposed so the many security features included in stock made it a bit tricky. If you use a custom rom with a custom kernel, it's likely a bit easier.
I flashed my stock image from the google website
I flashed a custom kernel and then Supersu and then the lolliviper zip from this thread: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed busybox from the play store, opened the busybox app and let it install.
I disabled selinux enforcing using the app from this thread:
http://forum.xda-developers.com/showthread.php?t=2524485
Then I ran viper4audio and installed the driver from the app
Then I rebooted into twrp and used the terminal to delete /system/etc/audioeffects.conf and rebooted.
Voila, working Viper4android.
exad said:
I managed to get Viper4Android working this way:
First off, I use stock with systemless root and xposed so the many security features included in stock made it a bit tricky. If you use a custom rom with a custom kernel, it's likely a bit easier.
I flashed my stock image from the google website
I flashed a custom kernel and then Supersu and then the lolliviper zip from this thread: http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
I installed busybox from the play store, opened the busybox app and let it install.
I disabled selinux enforcing using the app from this thread:
http://forum.xda-developers.com/showthread.php?t=2524485
Then I ran viper4audio and installed the driver from the app
Then I rebooted into twrp and used the terminal to delete /system/etc/audioeffects.conf and rebooted.
Voila, working Viper4android.
Click to expand...
Click to collapse
By the way, you can run a supolicy script for media server instead of disabling selinux because that would increase security risks and don't you mean audio_effects.conf in vendor? IMO better to add v4a entries than delete it, it's there for a reason I would think
hinxnz said:
By the way, you can run a supolicy script for media server instead of disabling selinux because that would increase security risks and don't you mean audio_effects.conf in vendor? IMO better to add v4a entries than delete it, it's there for a reason I would think
Click to expand...
Click to collapse
Yes! Thanks for the corrections! I haven't done it in a while! ?
I have the No-Limits Marshmallow ROM, works great. Have Phoenix kernel. Busybox is installed as is Trickster Mod for kernel control. I use the Stericson Busybox Installer which I've used for years.
But after installing this new ROM, which is very close to TW Stock, I have a problem with Trickster Mod, it keeps telling me Busybox not installed correctly. Trickster Mod refuses to run!
But Busybox seems to be installed, no other root apps are complaining. So I removed Tickster Mod, now use ROM toolbox to control CPU speed, scheduler and governor.
Anyone else have this problem?
Try to install BusyBox Busy on rails
The cpu scripts in the aroma installer sets preferences for the kernel. I assume these scripts hold their settings. Does this mean you don't need a kernel manager to set up profiles such as, Performance, Balanced, & Battery Saver? Also, how do I use other scripts without going back to the aroma installer? I tried the command su - c/fc_profiles and it doesn't do anything.
Using XT1575 24.49-18-4 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
dkeepitabuck said:
The cpu scripts in the aroma installer sets preferences for the kernel. I assume these scripts hold their settings. Does this mean you don't need a kernel manager to set up profiles such as, Performance, Balanced, & Battery Saver? Also, how do I use other scripts without going back to the aroma installer? I tried the command su - c/fc_profiles and it doesn't do anything.
Using XT1575 24.49-18-4 /w Systemless Root, Systemless Xposed, & Frankenclark 0.14
Click to expand...
Click to collapse
The scripts hold their settings. I never dug into how it is applied with Frankenclark, but I suspect whatever you pick during the aroma installer gets run as an init.d script each boot.
My favorite way to apply different scripts on android is an app called Root Browser. If I touch ghostpepper.sh in Root Browser one of the options is Execute with a run as root checkbox in the dialog. It is pretty fast and easy. I think kernel adiutor can execute scripts too, but it is less straightforward and I don't tend to use it.
I wanted to install Viper4android on stock 7.0 march but was unable to do so after following 2-3 different methods. Is there anyone successfully using viper4android on stock? And if not successful them suggest any other sound mod fully working and compatible with stock 7.0 march. I am rooted, elementalX 1.04 + busybox also installed :silly:
You intent with Viper4Aprise?
most of these require permissive selinux and i dont want to do that.
Why? I dont know for what flash permissive, what Is this?
JassyelZ said:
Why? I dont know for what flash permissive, what Is this?
Click to expand...
Click to collapse
selinux can be "enforcing" which is more secure or "permissive" which is less secure. V4A does require permissive kernel generally.
so anyone found a working sound mod for stock rom with selinux enforcing?
nitish_namdev said:
so anyone found a working sound mod for stock rom with selinux enforcing?
Click to expand...
Click to collapse
I've got ARISE running on my device (NPJS25.93-14.4, ElementalX, magisk v13). Note, I'm just running the core modules, any other addons I do not know if you need to tweak further. I have not changed ElementalX's SE Linux permissions, and running 'su getenforce' in a terminal returns as 'enforcing'.
My setup: XT1642, updated to NPJS25.93-14.4, ElementalX, magisk v12/v13 (think if you have SuperSU, should be okay too).
1) Downloaded ARISE Magnum Opus from here: https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709 (I currently have the 05/06 build). The download link is the Magnum Opus TM. Also, as I'm using magisk, I downloaded the magisk compatibility module. https://forum.xda-developers.com/an...y-research-t3379709/post71569390#post71569390
2) To configure ARISE before flashing, I extracted arise_customize.prop to /sdcard, and configured install.core to = true, install.v4a_2.5.0.5= to be true (and later found out I needed delete.deep_buffer to = true). Saved the ARISE customise file (I've uploaded my prop file if you want to see my modifications. If you wish to use this file, delete the .txt in the file name so the extension is .prop).
3)Rebooted to TWRP. Backed up. Flashed ARISE Magnum Opus - as configured, it should flash the 2.5.0.5 core module and delete the deep buffer (without deleting deep buffer, I found that ARISE did not process output).
3a)After ARISE, flashed the magisk compatibility module (if you're on SuperSU, you may not have to flash this). With magisk v13, this does not trigger Safety Net.
4)Wipe cache/Dalvik and reboot.
5)As I'm using Poweramp, I had to go to Poweramp Settings > Audio > Advanced Tweaks and disable Direct Volume Control. Also, I disabled the main Equalizer.
Now, ARISE processes headphone output as per the ARISE settings.