This module enables the native multiwindow mode of Marshmallow without having to set the build time to Userdebug.
The feature is native to 6.0+, but on 6.0 it was disable due to being not ready to release and having some bugs.
This module enables it by adding the build prop line:
persist.sys.debug.multi_window=true
To disable it, simply disable or delete my module on Magisk Manager.
Download link.
https://drive.google.com/file/d/0B5MjHsFKl11beFdacVNQZVl0WFU/view?usp=drivesdk
Cannot run on redmi note 4 mtk.
I install via twrp and check list magisk but still running
x_boogies said:
Cannot run on redmi note 4 mtk.
I install via twrp and check list magisk but still running
Click to expand...
Click to collapse
Hi, can you see if the mentioned line has been added to the build prop?
What magisk version are you using?
Sent from my ASUS_Z00L using XDA Labs
Yeah i see on system/build.prop as txt file adding persys....
I use magisk v16
x_boogies said:
Yeah i see on system/build.prop as txt file adding persys....
I use magisk v16
Click to expand...
Click to collapse
Can you try this module then? This will change your build to userdebug.
The solution is a little dirtier, you have to flash the module, reboot then enable the multiwindow function in the developer options, then reboot again, then if all goes well you can disable my module to return to the user build.
The multiwindow function will continue to work, even in the normal build.
https://drive.google.com/file/d/1lYmf7EtaYl79LoNmdg3Htyu9OAsx237B/view?usp=drivesdk
Sent from my ASUS_Z00L using XDA Labs
I flashing but still not showing multiple on developer
@FHC1998 Neither of the files you've provided work...
First of all because you haven't set PROPFILE to true in config.sh. That's necessary if you have props set in the system.prop file. And secondly, it'll not install on a current release of Magisk unless you update the module template.
Also worth noting is that there won't be anything added to build.prop with this method, the value will just be loaded. Check by using the getprop command.
Didgeridoohan said:
@FHC1998 Neither of the files you've provided work...
First of all because you haven't set PROPFILE to true in config.sh. That's necessary if you have props set in the system.prop file. And secondly, it'll not install on a current release of Magisk unless you update the module template.
Also worth noting is that there won't be anything added to build.prop with this method, the value will just be loaded. Check by using the getprop command.
Click to expand...
Click to collapse
Thanks, yeah the module is a little outdated, I didn't update it since magisk 12. Wierdly it worked for me (Z00l Stock Marshmallow with magisk 11-13) even though those settings were off. But I will update the module and change those settings. Thanks for the tip.
Sent from my ASUS_Z00L using XDA Labs
Related
Hello everyone,
I have just created an app to enable or disable Xposed in a click. Hope you like it, here's the package name: com.dotweb.xposedswitch (search for it on the Play Store)
How does it work?
Well, it uses an interesting feature of Xposed: the disabled file. However, to apply changes, you need to reboot.
The what?!
The disabled file is located here: /data/data/de.robv.android.xposed.installer/conf/disabled -- the Xposed Installer app's data directory.
Whenever this file is detected, whatever it contains, the Xposed framework will be disabled, and no modules will work. I guess you see where this is going.
But it's not in the SD card?
Well spotted! This is why the app also needs root access. Since it cannot disable Xposed by other means, you need to grant it root access. No worries, I tested whatever the app does.
Why would we want to disable Xposed then?
Not specifically disable it, the app can also re-enable it if it was disabled because of a problem. Also, disabling Xposed can be a good thing to do troubleshooting if your device has problems, etc.
I guess you know everything now, and I hope this app will be useful!
Until next time,
TheSola10
New update: Horizontal layout, SDK25 build and multi window manifest
Material Xposed Installer already has this. I had to install your app to find out it requires reboot. You might want to add that to the OP. Thanks.
buffal0b1ll said:
Material Xposed Installer already has this. I had to install your app to find out it requires reboot. You might want to add that to the OP. Thanks.
Click to expand...
Click to collapse
Well okay, but it's a warmup or sth, and I have never seen that feature with Material Xposed Installer. Also as it's an app that only does that, I can add a widget and stuff. Thanks for feedback!
Ward
Enviado desde mi XT1563 mediante Tapatalk
As many of you know Nintendo's first mobile app Miitomo crashes on most custom kernels and ROMs. Since version 1.2.0 Miitomo does no longer check for root, but it checks the value of 'ro.debuggable'. If 'ro.debuggable' is set to '1' by the kernel (in /default.prop), Miitomo will crash.
So what this Module does, is to set 'ro.debuggable' to '0', using the shiny new resetprop introduced in Magisk v9. This Magisk Module is meant for people who can't use Xposed or don't want to.
For Xposed users, check my SecurityBypasser Xposed Module.
Tested on Lux (Moto X Play).
Download and Code over at github.
Can you make another module that sets ro.build.type=user in build.props?
Link_of_Hyrule said:
Can you make another module that sets ro.build.type=user in build.props?
Click to expand...
Click to collapse
Should not be a problem. Any particular reason?
Setialpha said:
Should not be a problem. Any particular reason?
Click to expand...
Click to collapse
Because Android Wear won't work if it's userdebug.
EDIT: I was able to make a script based on an existing script for something else thanks for your reply. This is the script I made if anyone needs it.
@Setialpha This still works great and you should get it put on the Magisk module repo.
Link_of_Hyrule said:
@Setialpha This still works great and you should get it put on the Magisk module repo.
Click to expand...
Click to collapse
+1
I can't install this on magisk with the install module feature. Does it work through twrp?
Brentboy said:
I can't install this on magisk with the install module feature. Does it work through twrp?
Click to expand...
Click to collapse
That's likely an issue with MagiskManager, flashing through TWRP will work.
Setialpha said:
That's likely an issue with MagiskManager, flashing through TWRP will work.
Click to expand...
Click to collapse
Thanks, and is there away to make this work for puzzle and dragons jp? I'm in nougat so can't use your xposed module :/
Just FYI it also helps with Super Mario Run.
This actually allows me to play Mario on my Oneplus One with resurrection remix ROM.
Thank you very much
So I do need to run that script of I don't want to have Android Wear issues?
well it helped in playing Mario Run but it made Yugioh duel links stop working so i uninstalled it
going to give this a try for mario. thanks very much!
WORKS!
Guys... Since v11.5 Magisk changes this prop value by default. If you're keeping up to date, there's really no need to flash the module, just enable Hide...
That is not working in resurrection remix (redmi note 3)
---------- Post added at 03:40 PM ---------- Previous post was at 03:36 PM ----------
Didgeridoohan said:
Guys... Since v11.5 Magisk changes this prop value by default. If you're keeping up to date, there's really no need to flash the module, just enable Hide...
Click to expand...
Click to collapse
That is not working in resurrection remix (redmi note 3)
I still think it would be great if this was added to the magisk module repo I know a lot of people probably use it.
Sent from my Nexus 7 using Tapatalk
Link_of_Hyrule said:
I still think it would be great if this was added to the magisk module repo I know a lot of people probably use it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It won't be added...
1 - Magisk Hide changes this prop by default. If someone has issues with Hide, there's always modules like this and you could also very easily make a boot script utilising resetprop.
2 - @topjohnwu have clearly stated he won't add modules that only changes a prop value to the repo. This is an upcoming feature in the Manager.
Didgeridoohan said:
It won't be added...
1 - Magisk Hide changes this prop by default. If someone has issues with Hide, there's always modules like this and you could also very easily make a boot script utilising resetprop.
2 - @topjohnwu have clearly stated he won't add modules that only changes a prop value to the repo. This is an upcoming feature in the Manager.
Click to expand...
Click to collapse
Oh ok so basically I don't even need this module any more?
Sent from my A0001 using Tapatalk
Link_of_Hyrule said:
Oh ok so basically I don't even need this module any more?
Click to expand...
Click to collapse
U don't need it, because magisk already does what this module does since months.
I'm trying to install the Viper4Android 2.5.0.5 module in Magisk. I installed the module and the app and then rebooted, but the driver status in Viper4Android under enabled indicates a "no".
I've tried some of the settings, but it does not seem to work. The sound is all the same. Any idea how to get this to work? There were no additional instructions for getting V4A to work.
Nexus 6 running Pure Nexus 7.1.2 with Magisk version 12.0
I've had great success on several different devices with this module: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Didgeridoohan said:
I've had great success on several different devices with this module: https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
Click to expand...
Click to collapse
I can confirm that the above link works great..
I was hoping I didn't have to use that workaround, but I guess I have no choice. I don't know if anyone will agree with me, but I find it annoying to have to decipher and read through all these guides and forum posts to figure out how to get something to work. I wish things just "worked".
MiuKing said:
I was hoping I didn't have to use that workaround, but I guess I have no choice. I don't know if anyone will agree with me, but I find it annoying to have to decipher and read through all these guides and forum posts to figure out how to get something to work. I wish things just "worked".
Click to expand...
Click to collapse
Everyone has different devices, different setups, etc. It's never going to "just work" easily for everyone. That said, the link above works great and doesn't really have much reading to do....
Only issue I had was it not working initially, but I set the mode to "compatible" instead of "normal" it instantly started working. In case you have issues with it not starting like I did.
Hello, I have a OnePlus 3T (Oreo - 8.0.0 - OxygenOS Open 20 ) I was in the big sh*t installing this app but now it's working so what I do ?
I simply install 4/5 things :
- Viper4Android APK here ( http://www.mediafire.com/file/xonl4jha2e4vez1/ViPER4Android_FX_v2505.zip )
- BusyBox you can get it on the Play Store
- This Magisk module for OP3T but if you have an other phone search an other compatible module ( https://androidfilehost.com/?fid=673368273298977808 )
- The SELinux Switch [IMPORTANT] ( https://forum.xda-developers.com/devdb/project/?id=22073#downloads )
UNINSTALL ALL PREVIOUS VERSIONS OF V4A ON YOUR DEVICE.
Now I'm gona show you how to get this sh*t working
Simply install unzip the Viper4Android folder and install this apk :
ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk
(Maybe a newer version can be delivered in the future I think you can install it).
Then install BusyBox.
Open V4A and install the Drivers.
When it's done go to Magisk -> Modules -> + and install the zip module for your device.
/!\REBOOT /!\
Finally you just have to install The SELinux Switch.apk and switch your SELinux to Permissive (maybe you have to reboot but for me when I reboot my SELinux go back to Enforcing SELinux so I switch it back when I reboot).
[Note : I don't know if it's important but I was flashing a zip of V4A that's install me V4A as a system app and it wasn't working (error I/O) this is not important but it maybe install me other files so maybe you have to do this if it's not working at the end].
V4A is working now (don't forget to switch off your stock equalizer in Settings -> Sound -> Balance)
If you have any problem or questions contact me.
Franck7519 said:
Hello, I have a OnePlus 3T (Oreo - 8.0.0 - OxygenOS Open 20 ) I was in the big sh*t installing this app but now it's working so what I do ?
I simply install 4/5 things :
Click to expand...
Click to collapse
My dude, you are doing way more then you have to. Just install Ahrions magisk viper module. It has all the patches for OOS Oreo to work (it seems OnePlus made it impossible for viper to work on Enforcing with their Oreo release -.-)
Sent from my LG Nexus 5X using XDA Labs
Skittles9823 said:
My dude, you are doing way more then you have to. Just install Ahrions magisk viper module. It has all the patches for OOS Oreo to work (it seems OnePlus made it impossible for viper to work on Enforcing with their Oreo release -.-)
Click to expand...
Click to collapse
No because V4A is not working when SELinux is on enforcing bru this is why I install the switcher and it's working but if a problem comes I will test with your module.
Franck7519 said:
No because V4A is not working when SELinux is on enforcing bru this is why I install the switcher and it's working but if a problem comes I will test with your module.
Click to expand...
Click to collapse
The module I suggested automatically sets permissive on boot for OOS devices.
Sent from my LG Nexus 5X using XDA Labs
Skittles9823 said:
The module I suggested automatically sets permissive on boot for OOS devices.
Click to expand...
Click to collapse
It's better than my method yet I'm agree but I don't find your module can you send me a link ?
Franck7519 said:
It's better than my method yet I'm agree but I don't find your module can you send me a link ?
Click to expand...
Click to collapse
Look at the previous link in this thread. That's the one (it requires Magisk 15+ to work).
Sent from my LG Nexus 5X using XDA Labs
Skittles9823 said:
Look at the previous link in this thread. That's the one (it requires Magisk 15+ to work).
Click to expand...
Click to collapse
Ok thanks bru
Since Google Camera with HDR+ was ported already, it requires that camera2api to be enabled.
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1".
Note:
This mod only adds camera2api support in the build.prop systemlessly. This does not guarantee modded google camera hdr+ will work on your device.
Axon 7 Users:
Here's a working GCAM that works on my device. However, I don't see any difference with my stock cam hdr. I just use this for slowmo, panorama, photosphere and lens blur effects.
MGCB_7.0H_C2API_Mid_v.3.6_AllinOne_Full_Manual.apk
Requirements:
Android 5.0 & up
Magisk v15
~2014+ Snapdragon SoCs
Instruction:
Add the zip in Magisk Manager -> Modules and reboot.
Or you could also flash it in your custom recovery, TWRP etc.
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled=1". Check attached screenshot for example.
Or
2. Install Camera2 Probe from playstore to check your device's camera capabilities.
UPDATES:
9-15-17:
-added v1400 template
-added camera2api with slowmo fix for Axon 7 users. (I can't guarantee slowmo on other models will work since I used my device's media_profiles.xml file.)
01-25-18
-updated to v1500 template for C2API - Download this file if you only want the HAL3 enabled.
-updated to v1500 template for C2API+slowmo+ (credits to @j1505243)
Credits:
- BSG (4pda)
- @j1505243
Noob question: how do I check in terminal if it's already enabled because in rom included?
vergilbt said:
Noob question: how do I check in terminal if it's already enabled because in rom included?
Click to expand...
Click to collapse
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"
Like this?
vergilbt said:
Like this?
Click to expand...
Click to collapse
Yes.
Unfortunately it did not activate manuals comtrole on my p8lite with Los 13
youwi said:
Unfortunately it did not activate manuals comtrole on my p8lite with Los 13
Click to expand...
Click to collapse
I think this is for snapdragon devices only.
otaconremo said:
I think this is for snapdragon devices only.
Click to expand...
Click to collapse
Yes, and from SD 820+ right?
otaconremo said:
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"
Click to expand...
Click to collapse
I have a G5 which supports it and if I try the command above it does not show the "persist.camera.HAL3.enabled" property. So can we assume that property is specifically to indicate the magisk module is working?
I used this app to check if it was supported already Camea 2 Probe on the play store.
ok how to disable this and revert back to stock ?
causing problem ...
Sent from my ONEPLUS A3003 using XDA Labs
Not working on lenovo zuk z2..... Snapdragon 820
I think the OP should mention that this module is for SD820+ .
Thanks for the effort but still nothing for XZ
josephnero said:
Thanks for the effort but still nothing for XZ
Click to expand...
Click to collapse
Works on my XZ
What is the benefit of getting this mod?
otaconremo said:
Since Google Camera with HDR+ was ported already, it requires that camera2api to be enabled.
This is done by editing build.prop to add or enable "persist.camera.HAL3.enabled=1".
Requirements:
Magisk v13
Instruction:
Add the zip in Magisk Manager -> Modules and reboot.
Or you could also flash it in your custom recovery, TWRP etc.
How to check if it is running:
1. Open terminal and issue command "getprop | grep camera".
If it's running, you should be able to find a line "persist.camera.HAL3.enabled 1"
Click to expand...
Click to collapse
Flashed it on my Lenovo Zuk Z2
Snapdragon 820.
Unfortunately didn't work.
Got really excited for it.
Am i missing anything?
Very noob question is this work on mtk devices
sifatrhmn said:
ok how to disable this and revert back to stock ?
causing problem ...
Sent from my ONEPLUS A3003 using XDA Labs
Click to expand...
Click to collapse
Remove the module in the Magisk Manager app and reboot.
Ariac Konrel said:
Remove the module in the Magisk Manager app and reboot.
Click to expand...
Click to collapse
it doesn't work with my rom like that..
i have to dirty flash the rom again to solve it ..
Sent from my ONEPLUS A3003 using XDA Labs
CStadler said:
What is the benefit of getting this mod?
Click to expand...
Click to collapse
same question, I see no difference on photos.
Modules work one time after reboot stop working
Rom RR 7.1.0
Nexus 6p
Everything looks fine in your log. Unless you really need it though, I'd recommend removing the Universal SafetyNet Fix module. It replaces Magisk internal busybox with one that might cause issues... Better to use the resetprop tool to change the device fingerprint to the stock 6P one of you can't pass SafetyNet on that ROM.
What is it that doesn't work? Details, please...
Didgeridoohan said:
Everything looks fine in your log. Unless you really need it though, I'd recommend removing the Universal SafetyNet Fix module. It replaces Magisk internal busybox with one that might cause issues... Better to use the resetprop tool to change the device fingerprint to the stock 6P one of you can't pass SafetyNet on that ROM.
What is it that doesn't work? Details, please...
Click to expand...
Click to collapse
injected youtube models
Fix mic
Didgeridoohan said:
Everything looks fine in your log. Unless you really need it though, I'd recommend removing the Universal SafetyNet Fix module. It replaces Magisk internal busybox with one that might cause issues... Better to use the resetprop tool to change the device fingerprint to the stock 6P one of you can't pass SafetyNet on that ROM.
What is it that doesn't work? Details, please...
Click to expand...
Click to collapse
Ans this msg show up after every reboot
hk48 said:
injected youtube models
Fix mic
Click to expand...
Click to collapse
That's not very detailed...
hk48 said:
Ans this msg show up after every reboot
Click to expand...
Click to collapse
That's not a Magisk issue. You have to match the vendor image with the system image. It even tells you what factory image to get the file from.
Modules not working 14.3/14.0
Modules work one time after reboot stop working
Rom RR 7.1.0
Nexus 6p
Click to expand...
Click to collapse
HI.. I have the same issues last days - then i tried to use an other Kernel that have Magisk integratet! Since that all fine (mostly) !!
Here the link to my thread about - in it you can found the link to the Kernel with Magisk...
https://forum.xda-developers.com/apps/magisk/problem-module-install-lost-root-galaxy-t3703398
I hope that fix your issues...
Greetz...
Didgeridoohan said:
That's not very detailed...
That's not a Magisk issue. You have to match the vendor image with the system image. It even tells you what factory image to get the file from.
Click to expand...
Click to collapse
That one I check it
Sent from my Nexus 6P using Tapatalk
n82freak said:
HI.. I have the same issues last days - then i tried to use an other Kernel that have Magisk integratet! Since that all fine (mostly) !!
Here the link to my thread about - in it you can found the link to the Kernel with Magisk...
https://forum.xda-developers.com/apps/magisk/problem-module-install-lost-root-galaxy-t3703398
I hope that fix your issues...
Greetz...
Click to expand...
Click to collapse
I will try it and hope work، thanks [emoji846]
Sent from my Nexus 6P using Tapatalk
hk48 said:
That one I check it
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You made it sound like no modules work...
If it's only specific modules are troublesome, ask for help in the specific module threads. With lots of details about what doesn't work and don't forget to include logs.
Didgeridoohan said:
You made it sound like no modules work...
If it's only specific modules are troublesome, ask for help in the specific module threads. With lots of details about what doesn't work and don't forget to include logs.
Click to expand...
Click to collapse
Yes، all modules not working but in magisk shows modules work but when i use every module nothing work like im use the original app، hope i got that clear [emoji20]
Sent from my Nexus 6P using Tapatalk
hk48 said:
Yes، all modules not working but in magisk shows modules work but when i use every module nothing work like im use the original app، hope i got that clear [emoji20]
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ok. We need to clear things up....
I see you have a whole bunch of modules installed and like I said, your log looks good. But when asked for details you only mentioned iYTBP and Android mic fix as not working. This is where I would like some details. How do you know that the modules don't work? What have you tested? What is the expected behaviour and what are you seeing?
Let's start with something that's easy to test: busybox. Open a terminal emulator and type busybox. If nothing happens, run the command as su. Does it show a list of all the applets available?
Didgeridoohan said:
Everything looks fine in your log. Unless you really need it though, I'd recommend removing the Universal SafetyNet Fix module. It replaces Magisk internal busybox with one that might cause issues... Better to use the resetprop tool to change the device fingerprint to the stock 6P one of you can't pass SafetyNet on that ROM.
What is it that doesn't work? Details, please...
Click to expand...
Click to collapse
If i remove universal safetynet fix module i got fules pass[emoji34] so resetprop tool fix that ??
I search for resetprop tool and got nothing can u pls give a like for that، i know im ask to much [emoji28]
Sent from my Nexus 6P using Tapatalk
Didgeridoohan said:
Ok. We need to clear things up....
I see you have a whole bunch of modules installed and like I said, your log looks good. But when asked for details you only mentioned iYTBP and Android mic fix as not working. This is where I would like some details. How do you know that the modules don't work? What have you tested? What is the expected behaviour and what are you seeing?
Let's start with something that's easy to test: busybox. Open a terminal emulator and type busybox. If nothing happens, run the command as su. Does it show a list of all the applets available?
Click to expand...
Click to collapse
Use all modules not work،
I install the module ok then i go test it nothing happen..
Like utube first i download the the module iytbp and first time work perfect also fix mic and jamesDSP module for better sound work all perfect but after second time reboot all modules show in magisk but when i test every modules not working like i dont have any modules there [emoji36]
Sent from my Nexus 6P using Tapatalk
hk48 said:
If i remove universal safetynet fix module i got fules pass[emoji34] so resetprop tool fix that ??
I search for resetprop tool and got nothing can u pls give a like for that، i know im ask to much [emoji28]
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The resetprop tool is a part of Magisk. I've written a bit about in the troubleshooting guide (start under "Matching official prop values to pass SafetyNet").
hk48 said:
Use all modules not work،
I install the module ok then i go test it nothing happen..
Like utube first i download the the module iytbp and first time work perfect also fix mic and jamesDSP module for better sound work all perfect but after second time reboot all modules show in magisk but when i test every modules not working like i dont have any modules there [emoji36]
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Those screenshots clearly show that the busybox module is working so things are Magic Mounting as they should. How do you test the modules?
Didgeridoohan said:
The resetprop tool is a part of Magisk. I've written a bit about in the troubleshooting guide (start under "Matching official prop values to pass SafetyNet").
Those screenshots clearly show that the busybox module is working so things are Magic Mounting as they should. How do you test the modules?
Click to expand...
Click to collapse
By use there effect app like module iytbp i check the utube work like normal utube، and jumesDSP module i use there app and not see any change when i switch things..
… ..
After besybox imgs i send is that should told u everything is running??? U dont see anything wrong [emoji47][emoji47][emoji47]
Sent from my Nexus 6P using Tapatalk
hk48 said:
By use there effect app like module iytbp i check the utube work like normal utube، and jumesDSP module i use there app and not see any change when i switch things..
… ..
After besybox imgs i send is that should told u everything is running??? U dont see anything wrong [emoji47][emoji47][emoji47]
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
The busybox screenshots do tell me that everything is working as it should.
The iYTBP Youtube app looks just like the normal Youtube (unless you use the black themed version). It removes ads and brings background playback to the app. If you're seeing ads it might be because you didn't uninstall updates for the stock Youtube app or you let it update through the Play store (you should disable updates for Youtube when using this module).
The audio module might simply be incompatible with your device or you may have another audio mod that is conflicting. Ask for advice in the module support thread.
Didgeridoohan said:
Everything looks fine in your log. Unless you really need it though, I'd recommend removing the Universal SafetyNet Fix module. It replaces Magisk internal busybox with one that might cause issues... Better to use the resetprop tool to change the device fingerprint to the stock 6P one of you can't pass SafetyNet on that ROM.
What is it that doesn't work? Details, please...
Click to expand...
Click to collapse
Didgeridoohan said:
The busybox screenshots do tell me that everything is working as it should.
The iYTBP Youtube app looks just like the normal Youtube (unless you use the black themed version). It removes ads and brings background playback to the app. If you're seeing ads it might be because you didn't uninstall updates for the stock Youtube app or you let it update through the Play store (you should disable updates for Youtube when using this module).
The audio module might simply be incompatible with your device or you may have another audio mod that is conflicting. Ask for advice in the module support thread.
Click to expand...
Click to collapse
What can i say، when u say disable update ? the only thing i dont check it is update im really sorry for wist ur time oh god i feel so ?? for not check that before post ???
For iytbp module now work fine
And another modules i will check one by one، dont worry i will not wist ur time like that ،،
Im really sorry.
Have a good day sir