Description
This module is my port of Crossbreeder, the old version was designed for Android 4.4 and below. So if you try use it on Android 5.0 and above, you will have some problems with it.
But now I have fixed that problem, and have changed some of the script; which was out-of-date. I have also added some new features of my own.
Details
For those who want to know what is this mod for, here are the details:
Random/Frandom tweak
Remove /dev/random as it's blocking . Link it to non-blocking /dev/urandom. Since /dev/random is blocking and designed to protect us from Quantum alien cryptographers with mathematical certainty and urandom is non blocking pseudo-random device that most apps and OSs are using anyway and with Haveged running, is as secure anyway as it's very difficult to empty the entropy pool faster than Havege can replenish it. Pre ICS devices have a lot to gain with this but ICS+ devices show visible gains too.
Haveged/Entropy tweak
Modulate OS entropy levels for lag reduction ala Seeder. The whole OS reads either /dev/random or /dev/urandom and both need entropy. However this mod uses a completely different, lightweight and efficient random number generator called Havege . This sharply reduces cpu consumption and corresponding battery life loss compared to Seeder. It also does a better job at keeping entropy levels high hence your device is more responsive. It doesn't run in a CPU intensive loop either. The extend queue functionality has also been added to CrossBreeder. See here for another rationale favouring Havege compared to Rngd - ( Look for the limitations)
Fix "Only position independent executables (PIE) are supported" problem on Android 5.0+ device
Here is how to fix it :
1. Install the Hex Editor.
2. Open the file in Hex Editor.
3. Find the 17th number, if the number is 02, change it to 03.
4. Save the file, that's it !
[Add-on 1] Dynamic Z-RAM/LMK
This tweak will automatic find how much ram do you have, how much ram do you left, then according to these value to set zram/lmk size.
[Add-on 1] Dynamic Power Saving
Here is the original post, I found this feature in Feradroid v0.24
A little translate:
DynBS can significantly reduce power consumption without shutting down the main functionality of the Android device (such as Wi-Fi, Bluetooth, mobile Internet, screen brightness, background processes) by reducing unnecessary high-frequency CPU when not needed.
Magisk Busybox Restorer
This module will let the busybox can be used externally at Magisk v15+
By linking the busybox in /data/adb/magisk to /sbin
Only support Magisk v15+
Trouble Shooting
1. Stuck at the boot stage
---> Reboot again ---> Not work? ---> Flash it again to uninstall it.
2. Application keep crashing after installed this module
---> Just disable Dynamic LMK.
3. CTS Profile miss match
---> Enable all the ways that you can hide the magisk, if its not work, then you can try Universal SafetyNet Fix
4. Any problem about CPU frequency, like your device become so slow, or become warmer, etc.
---> Disable DynBS can fix the problem
5. How to open the setting menu?
---> Open terminal, and type "cbconf" can open it.
6. The phone shows the message of rebooting/turning off but after 30 mins ,the process is not finished
---> Try to forced shutdown
7. Busybox-ndk failed because of install CrossBreeder
---> Try to use mine busybox
This module only test on my HTC One M7 running latest Slim 7.1.2 with Magisk 15.3
Not tested with Android 8.0+ yet.
If you want to install any add-on, you must install the main mod first.
Credit
1. Crossbreeder ( https://forum.xda-developers.com/showthread.php?t=2113150 ) - For most of files
2. FeraDroid Engine ( https://forum.xda-developers.com/an...beta-feradroid-engine-v0-19-ultimate-t3284421 ) - For the Governor Tweak
3. Dynamic Power Saving ( http://4pda.ru/forum/index.php?showtopic=620736&st=1120 )
Github Link
I'm on Lineage OS, OnePlus 3T, Radioactive Kernel, and for some reason whenever I enable this module, it breaks Root (MagiskSU). I'm not sure if this is a known problem, but if not, now you know. ;P
Yea it breaks safetynet for me when I enabled it on magisk. Though for the mod itself that seems to be working great, don't know if it's placebo but I am noticing a little less "lag" on some apps.
Finally, was searching for any information on this module, and got nothing except the original. Any reason why it took so long for a thread to be created about it?
loocool2 said:
Finally, was searching for any information on this module, and got nothing except the original. Any reason why it took so long for a thread to be created about it?
Click to expand...
Click to collapse
I messaged Rorsch about making a thread for their module a couple of days ago, so I assume the thought just didn't occur to them to make a thread. But now it's all good because there's a thread for it
Breaks Root? Try this
ht#tps://drive.google.com/open?id=0B1nFPsNMRIiiYzlsbWxxazlPUkk <------- Remove #
Test on Slimroms 7.1.2 / HTC ONE M7
Rorsch_X1 said:
Breaks Root? Try this
ht#tps://drive.google.com/open?id=0B1nFPsNMRIiiYzlsbWxxazlPUkk <------- Remove #
Test on Slimroms 7.1.2 / HTC ONE M7
Click to expand...
Click to collapse
Seems to be working! Although it's not 100% stable, it's better than having a totally broken Root.
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
edoardotavecchio said:
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Maybe... but we could just try something easier... ;P
What tweaks have you got? Like; are you using other Magisk modules? Have you changed your build.prop via an app like L Speed, or something like that? Have you made any kernel tweaks? What CPU governor are you using?
It sounds like something CB is trying to modify is conflicting with something else.
edoardotavecchio said:
This module gets me stuck in a strange bootloop everytime: I've tried 0.3a version some a week's ago and now with 0.8b. Phone seems to be booting, it passes Google splash screen, there's that little vibration that means the phone's booting right and then it gets stuck in there. Which logs should I provide to be helpful? Maybe last-kmsg?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Maybe you have too many file in the /system or installed too many modules
It will take a lot of time on the mount stage
Send me your magisk log
nan0s7 said:
Maybe... but we could just try something easier... ;P
What tweaks have you got? Like; are you using other Magisk modules? Have you changed your build.prop via an app like L Speed, or something like that? Have you made any kernel tweaks? What CPU governor are you using?
It sounds like something CB is trying to modify is conflicting with something else.
Click to expand...
Click to collapse
As tweaks, I've removed HEBF and LSpeed apps because I've had the same idea as you. As Magisk Modules, I've installed some camera and audio mods (Some very common mods for 5X: eis, 60fps libs, surround audio mod), Universal Deep Buffer remover, Selinux permissive script and Viper. The only one which modifies build.prop is EIS module. Does Crossbreeder modify build.prop too? Should I remove EIS in order to make this work?
As CPU governor, I'm using interactive (governor profile:Glasscannon)
Rorsch_X1 said:
Maybe you have too many file in the /system or installed too many modules
It will take a lot of time on the mount stage
Send me your magisk log
Click to expand...
Click to collapse
That's strange because usually it's very very fast, it takes something like 3-4 seconds after the vibration. Eith this module installed, I've tried to wait even 10 minutes without any success.
Now I'll retry and send you Magisk log.
Sent from my Nexus 5X using XDA Labs
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
edoardotavecchio said:
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I don't know about conflicts, but I saw you're using the audmodlib module by @ahrion with the V4A module by @metaspook. That Viper module isn't made to utilise the audmodlib... You probably wanted this one: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Didgeridoohan said:
I don't know about conflicts, but I saw you're using the audmodlib module by @ahrion with the V4A module by @metaspook. That Viper module isn't made to utilise the audmodlib... You probably wanted this one: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Click to expand...
Click to collapse
I know that and I've tried it but it didn't work.
Edit: Now it is working. what
Thanks for your suggestion.
Sent from my Nexus 5X using XDA Labs
crayola555 said:
Yea it breaks safetynet for me when I enabled it on magisk. Though for the mod itself that seems to be working great, don't know if it's placebo but I am noticing a little less "lag" on some apps.
Click to expand...
Click to collapse
I am a big fan of crossbreeder... However...
Iirc without frandom... You are not actually generating "random"
And according to what I have read (stop me if I'm wrong)... The less "lag" you are seeing is from that random number generation keeping your processor a little more ramped up... Equivalent to turning touchboost up a notch... Or raising your cpu min frequency...
Sent from my Nexus 6 using Tapatalk
This work on rooted s7 w/ Exynos CPU?
pan.droid said:
This work on rooted s7 w/ Exynos CPU?
Click to expand...
Click to collapse
Yes, it works on all ARM devices.
edoardotavecchio said:
That's my magisk log without having crossbreed installed. Can you take a look and see if there's something in conflict with your module? @Rorsch_X1
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
I have tried am3d & v4a & Audio-Modification-Library & deep buffer remover with my CrossBreeder , but they all works fine.
Where were you stuck at? Boot Animation or Boot logo?
By the way, are you using Android O? I see libfmas.so & android.hardware.audio.low_latency.xml & android.hardware.audio.pro.xml in the log you sent to me.
Rorsch_X1 said:
I have tried am3d & v4a & Audio-Modification-Library & deep buffer remover with my CrossBreeder , but they all works fine.
Where were you stuck at? Boot Animation or Boot logo?
By the way, are you using Android O? I see libfmas.so & android.hardware.audio.low_latency.xml & android.hardware.audio.pro.xml in the log you sent to me.
Click to expand...
Click to collapse
I get stuck at bootanimation after the "boot completed" vibration (that little vibration which runs a few seconds before the phone booting, usually reporting that boot process has been nearly completed). I've never experienced a situation like this in 6 years of modding so I don't know what could have gone wrong: the vibration usually doesn't trigger (when phone can't boot and gets stuck in a bootloop) or after a few minutes, a few seconds before booting (when the OS takes a lot to mount partitions or compiling caches, per example when you clean flash a new OS and caches have to be rebuilt). It's so strange that vibration fires and the phone doesn't boot anyway. I've tried to let the phone work for something like 20 minutes (which I consider is even too much for a simple boot) but nothing happens anyway.
Anyway no, I haven't updated to O yet because some mods aren't compatible with it yet so I've stopped on 7.1.2 which is stable and fully supported.
edoardotavecchio said:
I get stuck at bootanimation after the "boot completed" vibration (that little vibration which runs a few seconds before the phone booting, usually reporting that boot process has been nearly completed). I've never experienced a situation like this in 6 years of modding so I don't know what could have gone wrong: the vibration usually doesn't trigger (when phone can't boot and gets stuck in a bootloop) or after a few minutes, a few seconds before booting (when the OS takes a lot to mount partitions or compiling caches, per example when you clean flash a new OS and caches have to be rebuilt). It's so strange that vibration fires and the phone doesn't boot anyway. I've tried to let the phone work for something like 20 minutes (which I consider is even too much for a simple boot) but nothing happens anyway.
Anyway no, I haven't updated to O yet because some mods aren't compatible with it yet so I've stopped on 7.1.2 which is stable and fully supported.
Click to expand...
Click to collapse
Maybe the some script conflict with your system, try this version, you can enable/disable the tweak by yourself.
https://drive.google.com/open?id=0B1nFPsNMRIiiM2xocl9RTGt3OEk
After install this version, you need to go to /data/CrossBreeder, open the file with text editor then change the 0 to 1 to enable the tweak, I disable all in these config files.
P.S. Don't edit the CONF
Related
NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk
Damn this looks complicated as hell haha. Good job OP
Very nice job
Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me
I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?
Did you disable APK signature checking?
elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?
Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works
Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?
For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.
My rom is stock 4.4.4
I will try again with disabled optimization.
kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference
Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.
I tried again but this time booted upto lock screen and rebooted.
I tried with new build.
after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english
Deprecated - Use the New ViPER4Android v2.7:
GO TO THE THREAD LINKED ABOVE. You don't need to flash any zips. Just install it as a regular apk, allow it to install the drivers, and you're good to go.
For magisk users: I made a zip on the repo that includes the original vdc's and my profile converter (will convert your old profiles to the new and better format).
For rootless users: I made a zip to install drivers and such
Zips can be found here
ALL SUPPORT QUESTIONS FOR 2.7 SHOULD BE AT THE THREAD ABOVE.
This is ViPER4Android FX and Xhifi Unity installers
These installers utilize my Unified installer that can install on Magisk OR System if Magisk is not detected (with Pixel support).
Credits of Originality:
- @zhuhang (Official Thread)
- @Osm0sis
- Viper's Audio (Official blog)
- @ViPER520
- @Team_DeWitt
Special Instructions:
If you already know which original v4a you want to use, just add 'old' for 2.3.4.0, 'mid' for 2.4.0.1, 'new' for 2.5.0.5, or 'mat' for material to the zipname prior to flashing.
If you already know if you want it installed as a user or system app, add "uapp" for user app or "sapp" to system app to zipname.
If you already know if you want to apply the libstdc++.so lib workaround, add "lib" or "nlib" to zipname (note that there are some devices that are already known to require it and so they'll apply workaround regardless of choice)
If you already know if your device/rom requires the v4a open/close/fc audioserver workaround, add "ocw" to zipname. Otherwise, add "nocw" to zipname
To skip volkeys (if your device isn't compatible with them), add "novk" to the zipname. Note that if you don't specify the above, defaults will be applied which are: sapp, new
Make sure there are no spaces in the zipname
Audio Mod Troubleshooting Guide
Downloads
XDA:DevDB Information
ViPER4Android FX Legacy/XHiFI [Unity], App for the XDA Community Apps
Contributors
ahrion, Zackptg5
Version Information
Status: Stable
Current Stable Version: v4.4
Stable Release Date: 2019-08-11
Created 2019-01-18
Last Updated 2020-01-01
great!
Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.
kartikb said:
Hi, tried your two modules you've posted on my Nexus 6P stock ROM. March update. Both causing bootloop and using the uninstaller provided doesn't help. Have to use mount Magisk then go to file explorer in TWRP recovery and delete the modules from Magisk folder.
Click to expand...
Click to collapse
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.
Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.
ahrion said:
Hmm. This is probably a kernel or magisk limitation with your rom. Are you running 11.6? Try to run it without the deep_buffer Remover because this is probably what bootloops your phone. It's only necessary when you've NEED it, otherwise it may cause adverse effects. Just install V4A and see if it works.
Currently magisk still has limited boot.img compatibility which causes so.e mods to not work properly or bootloops when it's not the mod itself.
Click to expand...
Click to collapse
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
Magisk limitation. @topjohnwu is always improving magisk. I do recommend may e trying another kernel for your device which may help compatibility.
Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.
After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).
Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...
Didgeridoohan said:
Gave this module a go, and: it's a no go... Will not boot on my Nexus 6 running Vanilla ROM 7.1.1_r26, Franco Kernel r65 and Magisk v.11.6 - MagiskSU.
After flashing uninstaller the device still doesn't boot. Had to manually remove audmodlib from /magisk in TWRP to make it boot again. And it's in audmodlib the problem is. I did a quick test where I removed audmodlib after installation (kept v4afx in place) and it booted right up (with a non-functioning module, obviously).
Attaching installation and uninstallation recovery logs. Unfortunately I'm not at a computer with ADB, otherwise I would have captured a logcat of boot for you. Maybe later...
Click to expand...
Click to collapse
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.
If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.
ahrion said:
The only real thing in audmodlib is could be is service.sh or system.prop otherwise it would be the vendor file, which would mean that for some reason 11.6 is bugged for vendor file mounting. Try installing and remove those ONLY and and see if it fixes it.
If that fixes it then it's one of those two. And if you're cool can you see which one it is exactly.
Click to expand...
Click to collapse
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Seyaru said:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Click to expand...
Click to collapse
You are literally advertising your mods in everyone's threads. Stop this and make your own thread.
This is a magisk forum, not a system mod forum.
Didgeridoohan said:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
Click to expand...
Click to collapse
I will remove it with next release. Thank you man. This **** only started happening with 11.6. this was the reason Atmos was boot looping as well so I removed system.prop in Atmos.
Can you do me a favor and remove a few lines to see if it's just the specific lines? I think that certain lines don't play nice with your phone.
Remove the first part, low power audio tweaks, reboot and see if it works. If it doesn't then that's the culprit. If not then remove the first two on the other audio tweaks.
Seyaru said:
If you wanna try this is my module for Nexus phones. I use this in my Nexus 5X Stock and PureNexus
https://www.androidfilehost.com/?fid=529152257862713260
Sry ahrion for use your thread
Click to expand...
Click to collapse
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.
kartikb said:
Hi there, thanks for the suggestion. I've tried it already and it didn't work. Asked for drivers to be installed when I opened the app after installing the module and restarting the phone.
Click to expand...
Click to collapse
Enable permissive.
Turn off audiofx
ahrion said:
Enable permissive.
Turn off audiofx
Click to expand...
Click to collapse
I'll try again when I get a chance to. Thanks for the suggestion.
[UPDATED] ViPER4Android FX <2.5.0.5>
v1.1:
- Updated to Audio Modification Library (Magisk) v1.1
This should fix the boot loop issues seen in only Magisk v11.6
Download: Link - Mirror
Previous Changelogs (Unified installer):
HTML:
V1.0:
- Initial release
- Smali edits to automatically enable storage permissions
- Audio Modification Library v1.0 is included
- Unified installer that will install mod for both Magisk and System
- Pixel support included
- Magisk Template v3 support
kartikb said:
Hi, I'm on 11.6. I've tried both modules on their own and they both have caused boot loops unfortunately.
Thanks anyway..
Click to expand...
Click to collapse
Didgeridoohan said:
There has been an issue with vendor mounting in Magisk, but I believe that was for devices with separate vendor partitions (Nexus 6P, Nexus 5X, etc). I haven't seen any commits on GitHub about it though (although I haven't been keeping that close attention), so I don't know if it's been fixed.
I did find the culprit though: it's system.prop. With that file removed from /magisk/audmodlib my device booted up just fine.
Click to expand...
Click to collapse
Try 1.1.
ahrion said:
Try 1.1.
Click to expand...
Click to collapse
Thanks, I'll give it another go and report back.
Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.
kartikb said:
Thanks, I'll give it another go and report back.
Update: my phone reboots into Android fine now however it doesn't process audio on phone speaker.
Click to expand...
Click to collapse
Flash my deep buffer remover. Look in the magisk forum.
ahrion said:
Flash my deep buffer remover. Look in the magisk forum.
Click to expand...
Click to collapse
Thanks, it all finally works on my Nexus 6P. Now to try on my OnePlus 3..
Android Runtime Optimization
DISCONTINUED lol
Android Lollipop includes a new virtual machine called ART (Android Runtime.) ART uses AOT (ahead-of-time) compilation into native code, which performs better than JIT (just-in-time) compilation into bytecode. You can configure ART to perform this optimization in different ways. Android Lollipop includes the dex2oat tool for optimizing applications on deployment.
Click to expand...
Click to collapse
Compiler Filters
Since Lollipop, dex2oat takes a variety of --compiler-filter options to control how it compiles. Passing in a compiler filter flag for a particular app specifies how it’s pre-optimized. Here’s a description of each available option:
everything - compiles almost everything, excluding class initializers and some rare methods that are too large to be represented by the compiler’s internal representation.
speed - compiles most methods and maximizes runtime performance, which is the default option. ** default value on this module
balanced - attempts to get the best performance return on compilation investment.
space - compiles a limited number of methods, prioritizing storage space.
interpret-only - skips all compilation and relies on the interpreter to run code.
verify-none - special option that skips verification and compilation, should be used only for trusted system code.
This module sets a few dalvik.vm and pm.dexopt properties:
Code:
dalvik.vm.dex2oat-filter [B]**editable with the given compiler filters[/B]
dalvik.vm.image-dex2oat-filter
pm.dexopt.bg-dexopt
dalvik.vm.check-dex-sum
dalvik.vm.checkjni
dalvik.vm.usejit
dalvik.vm.heaptargetutilization
dalvik.vm.dex2oat-threads
Magisk Module (UI in Terminal Emulator)
How to use:
Open Terminal Emulator
Type su and then
Code:
art_magisk
Then choose your filter
Non-Magisk (command line)
How to use:
Code:
ART Optimization by veez21
setfilter [--compiler-filter] [file]
compiler filters:
everything
speed
balanced
space
interpret-only
verify-none
Ex:
Code:
setfilter everything
** this will find the file on common/default directories
Code:
setfilter everything /system/su.d/name.sh
** this will use the directory you entered, instead of the defaults
MORE INFORMATION ON THIS TOPIC HERE and here
UNIFIED INSTALLER IS PRESENT SINCE v1. IT INSTALLS IN A SPECIFIED ORDER (look below) . SO IF YOU DON'T HAVE MAGISK, YOU CAN STILL FLASH THE ZIP IN THE DOWNLOADS!
Order of Detection during Installation:
Code:
> Magisk > Systemless SuperSU > System SuperSU > Init.d
AFTER FLASHING, FOR THE FIRST TIME, WIPE DALVIK/ART CACHE. THIS IS NEEDED FOR IT TO TAKE EFFECT. YOU DON'T HAVE TO WHEN UPDATING THOUGH
THAT'S WHY YOU HAVE TO CHANGE THE --compiler-filter IF YOU WANT MORE APP PERFORMANCE. speed BEING THE DEFAULT IN ROMS (IF THE DEV HAVEN'T CHANGED IT), YOU CAN CHANGE IT TO everything IF YOU WANT MORE PERFORMANCE (BUT COSTS MORE SPACE). IDEAL VALUE WOULD BE balanced IF YOU ASK ME.
** This module can have problems with heavily modified OEM Roms (e.g. TouchWiz, MIUI). YOU HAVE BEEN WARNED. But this problem is inconsistent and just might work for you.
Read this Samsung ROM users: https://forum.xda-developers.com/showpost.php?p=72401085&postcount=594 ** possibly fixed on v1.3+
MOD Edit Links Removed Download here[/URL] or at Magisk Manager ** install in recovery
README and Changelogs
Uninstaller
Crash Fix
Source
Source (Magisk Repo)
MOD Edit Links Removed
DONATE? If you want to (ﾉ･ω･)ﾉﾞ
F.A.Q.
How to see if the changes are applied?
See Magisk log. ART Optimizations should be able to log there
Do this command and search for the properties given at the first post and if it there, it's working
Code:
su
getprop | grep dalvik
Bootloop! Help me!
Uninstall the module! Uninstaller
When in Magisk, RIL doesn't work, some apps crash, HELP!
Try flashing the crash fix. It might/might not work
Xposed not responding properly! Help me!
Can't do anything about it. Try wiping dalvik-cache, if that doesn't work uninstall the module
I don't use Magisk. How to can I use this?
Flash the zip at the OP. It installs to System if Magisk is not detected
I had some kind of trouble when using everything filter. Solution?
Try changing to speed. Several users have some trouble with everything too.
SuperSU + Magisk + This module is causing bootloop/some kind of problem. What do I do?
Uninstall the Magisk Module and install Non-Magisk instead
So by default this module should increase the speed of apps?
Enviado desde mi Aquaris X5 Plus mediante Tapatalk
Gonfebo said:
So by default this module should increase the speed of apps?
Enviado desde mi Aquaris X5 Plus mediante Tapatalk
Click to expand...
Click to collapse
Theoratically, yes, at first boot. After flashing wipe Dalvik/ART cache and see. :good:
Any Uninstaller to uninstall it ?
Does it work with Magisk ?
Sent from my YU5010 using Tapatalk
amihir said:
Any Uninstaller to uninstall it ?
Does it work with Magisk ?
Click to expand...
Click to collapse
Works with magisk since it's a magisk module ?. You can uninstall it in Magisk Manager
UPDATE TO v0.2!
Changelog:
- post-fs-data.sh and service.sh is additionally used to set properties
- fixed setting dalvik.vm.image-dex2oat-filter
Download
This module isn't needed on Nougat am I correct?
An XDA User said:
This module isn't needed on Nougat am I correct?
Click to expand...
Click to collapse
It can be used in nougat. I don't know the result of using it in it but try testing it and tell me the results if there's any problem
veez21 said:
It can be used in nougat. I don't know the result of using it in it but try testing it and tell me the results if there's any problem
Click to expand...
Click to collapse
Working fine on Nougat here.
I have a feeling that Plex (my media player) is MUCH snappier. And no, it hans't been updated lately.
Everything working... but I can't point a finger at anything else besides Plex.
Cheers!
If just edit system.prop with
dalvik.vm.dex2oat-filter=interpret-only
dalvik.vm.image-dex2oat-filter=speed
it should be work?
Hello m8 o/
Can you provide more download links?
"SYSTEM NOTICE: We apologize for any issues loading the site. We are working on a solution right now. Thanks for the understanding."
"Invalid response from the server: 502"
So when i can download this file i 1. Flash it in Magisk? 2. Flash it in TWRP?
Tesla said:
Hello m8 o/
Can you provide more download links?
"SYSTEM NOTICE: We apologize for any issues loading the site. We are working on a solution right now. Thanks for the understanding."
"Invalid response from the server: 502"
So when i can download this file i 1. Flash it in Magisk? 2. Flash it in TWRP?
Click to expand...
Click to collapse
2.Flash in TWRP
According to the OP, the mod requires wiping delvik/cashe after flashing the mod to work.
JERW28 said:
2.Flash in TWRP
According to the OP, the mod requires wiping delvik/cashe after flashing the mod to work.
Click to expand...
Click to collapse
:good:
Download works at the moment.
Edit: My phone (Note 4) is really fast as it is, but initial testing shows a bit faster launch of camera app.
Sure, it might be placebo. Hard to know just yet
Umm...
No... You've got this backwards...
Apps would launch slower... Not quicker... As your first boot is quicker... At least with the flags mentioned at the top of the post...
If you're looking for what would be faster app launch... You'd want to use the 'everything' flag as it builds a much larger cache file...
Sent from my Nexus 6 using Tapatalk
Tesla said:
Hello m8 o/
So when i can download this file i 1. Flash it in Magisk? 2. Flash it in TWRP?
Click to expand...
Click to collapse
I just installed it normally as a Magisk module. And wiped cache and dalvik on first reboot.
alroger said:
I just installed it normally as a Magisk module. And wiped cache and dalvik on first reboot.
Click to expand...
Click to collapse
That was my thought also, but it so simple to ge straight to TWRP so.
Thanks for the development and module for Magisk.
The effect is contrary with a Note 7 (MM) ported for SM N9005.
Installation according to indications, the smartphone is slower when starting up another 20 seconds.
There is no problem or fc but identically android lag enormously.
Perhaps a problem with the management of the kernel, ram ... etc
I tried to modify the filters without success for me.
A little feedback.
Thank you
This module sounds very interesting, but i have one question that isnt so clear to me... Does it speed up the start of apps in general or is it just the first start of the system after wiping dalvik/cache?
Just the first start thus it's pretty useless IMO. Mind you, it'll make apps perform worse.
I have no proof of this, but this has been happening on my Note 4 (SM-N910T) ever since v13.3, and now on v14.0. I also bought a Huawei Honor 6X about a week ago, it's now happening there too. I didn't feel that this was worth posting about, figuring it might be device-specific or ROM-specific. But now that it's happening on 2 devices I've changed my mind.
Note 4:
Android 7.1.2 (CMRemix)
Xposed unofficial by PurifyOS (system mode)
Kernel sets SELinux to permissive on boot
Magisk v14.0
No Magisk modules installed
Honor 6X:
Android 7.1.2 (Resurrection Remix)
Xposed (systemless Magisk version)
Kernel sets SELinux to permissive on boot
Magisk v14.0
No Magisk modules installed
Description of the issue:
After powering on/rebooting, I can't open system Settings app for up to a minute or so. It just hangs on a white screen. It then either gives a message stating that Settings isn't responding, or, if I manually close Settings with the Recent button then try to reopen it, it repeats the same behavior but will eventually open. Sometimes I need to access Settings immediately after boot to make changes. Device is otherwise responsive, Magisk appears to work fine.
I have tried clean ROM installs on both devices, with full wipes beforehand, and latest stable Magisk. I've also tried with and without Xposed, results are the same. This didn't happen before v13.3, v11.x and v12.x didn't exhibit this behavior. But back this I was using systemless SuperSU in conjunction with Magisk. I suspect that MagiskSU may be the culprit.
MagiskSU is also noticeably slower (when compared to SuperSU or non-Magisk Phh's Superuser) at responding to SU requests, even with a setting of auto-grant and the lowest possible timeout (10 seconds), and global mount namespace. This may be due to the fact that does more than just rooting, it is logical to assume that it has more background processes running since it is also a systemless framework, whereas the other 2 solutions only manage root access.
Last, my file managers oftentimes won't let me delete/modify certain files/folders in the system partition, with a message like "device or resource busy", or flat-out denying access. System is remounted as RW. This only happens with Magisk, but never with SuperSU or Phh. I do use Magisk for systemless mods, but sometimes I want to make direct midifications to /system. Magisk, as a root solution, shouldn't be denying my ability to do this, since I own my devices, not Magisk.
Right now I'm primarily concerned with the Settings issue, but I figured the other issues are worth mentioning. I'm still on the fence, I may return to SuperSU, or Phh, trying Magisk again after a few more stable releases. But if this can be resolved then I'll give it another chance.
I'm posting the logs for my Honor 6X, one is the Magisk log from /cache, the other is /data/anr/traces.txt. Attempts to get a logcat during boot were unsuccessful.
Thanks for any help!
Magisk saves a log during boot that you might find useful. It's /data/magisk_debug.log. A logcat from when the device has booted up and you're trying to open up the Settings might also be interesting.
Have you tried on a stock ROM? Both those ROMs you're using are related and may have similar ROM specific issues...
dont open setting immediately after reboot. open it after a minute. not really a problem
It is not Magisk problem that cause this problem but it is the rom...i'm also using RR 7.1.2 on bacon and Magisk v14 and have no problem at all but we bacon user does encountered this problem in RR build in July and the devs fixed this on August build....
Sent from my A0001 using Tapatalk
@all: I've been super busy lately, not much time to post anywhere. But getting back to this.....I doubt this is a ROM issue. My reasoning is that it would occur with or without Magisk if that were the case. I don't get this issue when using SuperSU or non-Magisk Phh Superuser (regular). This only occurs when Magisk is installed, since v13.3, but not before that version. It has also occurred on Huawei stock EMUI firmware.
@24imelqui: Just because you don't consider something to be a problem doesn't mean it isn't a problem for others. I have a need to be able to access my Settings app immediately after booting. Your comment isn't useful in the least, if you can't post something helpful then don't post at all. /Ignored.....
@iPusak Gaoq™: isn't Bacon a Nexus device (not sure, never owned one)? Can you reference something where this has been reported? And fixed? Like something on XDA or GitHub or whatever? If this can be proven to be ROM issue then I'll post something to my devices' devs to see if it can be fixed in later releases.
I'm attaching several logs, this time a logcat as well. No such debug log exists in /data, and Magisk v14.0 has no options in the Manager app for debug logging.
AnonVendetta said:
@all: I've been super busy lately, not much time to post anywhere. But getting back to this.....I doubt this is a ROM issue. My reasoning is that it would occur with or without Magisk if that were the case. I don't get this issue when using SuperSU or non-Magisk Phh Superuser (regular). This only occurs when Magisk is installed, since v13.3, but not before that version. It has also occurred on Huawei stock EMUI firmware.
@24imelqui: Just because you don't consider something to be a problem doesn't mean it isn't a problem for others. I have a need to be able to access my Settings app immediately after booting. Your comment isn't useful in the least, if you can't post something helpful then don't post at all. /Ignored.....
@iPusak Gaoq™: isn't Bacon a Nexus device (not sure, never owned one)? Can you reference something where this has been reported? And fixed? Like something on XDA or GitHub or whatever? If this can be proven to be ROM issue then I'll post something to my devices' devs to see if it can be fixed in later releases.
I'm attaching several logs, this time a logcat as well. No such debug log exists in /data, and Magisk v14.0 has no options in the Manager app for debug logging.
Click to expand...
Click to collapse
There have been issues previously, where it seems like it's a Magisk thing but it's really a ROM issue. Some things Magisk does (and it does a few more things than just root your device) can sometimes bring problems out into the light...
I believe bacon refers to the OnePlus One (Nexus devices are all named after aquatic creatures). Looking in the RR thread over in those forums I'd guess you'll find your information somewhere around here: https://forum.xda-developers.com/on...tion-remix-t3507102/post73283623#post73283623
About your logs: I'm not too good at reading logcats, so no help from me there. But, I see something there in your Magisk log... Have you tried disabling Xposed?
There are things going on when a device with Magisk starts, so depending on your setup it might take a short while (30-ish seconds for me on my daily driver) before root requests start being accepted. If the ROM settings require root, that might be the reason why it won't open straight away when booting up your device.
OK, back again, Xposed disabled this time in the app (but still installed), so not active.
Here is the full changelog on the build where the devs fixed the issues on settings freeze/fc on startup....
https://forum.xda-developers.com/showthread.php?p=73304715
Sent from my A0001 using Tapatalk
Only for Realme GT 2 (Snapdragon 888)
~15% performance increase
Pre Requisites: Rooted device
Original version: 530
Updated version: 615.65
Unstable Update: 682
How to Install: flash both the Magisk overlayfs module and Adreno GPU driver module given below and reboot
How to Uninstall: after flashing and rebooting come to Magisk modules section and remove both modules and reboot
Optional: Install bootloop protector Magisk module given below
Source: https://t.me/adreno_konabess/879129
Edit: Updated to 615.65 (1-2% performance increase from 615.50) and added Unstable 682 for people who wanna experiment (additional 3% performance increase over 615.65)
If some app doesn't work with it then add it to magisk hide and it will use stock drivers
I found in the group "updated" version of this drivers, with the old one I have problems with few applications, with this one for now I didn't have problems, some user report the about issue with firefox only.
Flash with Magisk.
b0nb0n3v said:
I found on the group "updated" version of this drivers, with the old one I have problems with few applications, with this one for now I didn't have problems, some user report the about issue with firefox only.
Flash with Magisk.
Click to expand...
Click to collapse
Nice, use the one that's more stable for you, for me genshin Impact had several artifacts/crashes with 615.50 so i resorted to 615
UNFORTUNATELY - After updating by DRIVERS through this method - my Whatsapp stopped working - the media stopped playing on my phone - don't know what went wrong - after removing the module - everything went back to normal!
I'm using RMX3312 on POS!
Prajwal_Beast said:
UNFORTUNATELY - After updating by DRIVERS through this method - my Whatsapp stopped working - the media stopped playing on my phone - don't know what went wrong - after removing the module - everything went back to normal!
I'm using RMX3312 on POS!
Click to expand...
Click to collapse
Hi, that didn't happen for me but I haven't tried pixel OS so can't confirm however you can try using the driver and adding WhatsApp to magisk hide apparently it uses stock drivers if u add app to magisk hide
Updated, actually works now and u can use 615.50 now
Latest driver from you are much better. I see one glitch on every version, as example I use Brave browser and have some tab, when I switch from active tab to inactive tab, some visual bugs/glitch are appeared. But this is not an issue. I will report after some day of tests.
Link to video of the glitch.
b0nb0n3v said:
Latest driver from you are much better. I see one glitch on every version, as example I use Brave browser and have some tab, when I switch from active tab to inactive tab, some visual bugs/glitch are appeared. But this is not an issue. I will report after some day of tests.
Link to video of the glitch.
Click to expand...
Click to collapse
Go to magisk manager and add the app that has these glitches to magisk hide, this will use stock drivers