Related
Perhaps someone can clarify for me...
I use Magisk and I've noticed that it was recently updated and there are mentionings about SELinux/sepolicy and pseudo enforced, etc. in the changelog.
Whenever I run SambaDroid it will fail to start unless I open the SELinuxModeChanger app and change the mode to Permissive first, which of course ruins SafetyNet, so I can't just leave it in that mode all the time.
I have to go back and change it to Enforcing when I am done.
An extra step I'm hoping won't be required in the future. Perhaps on a per-app basis like MagiskHide.
Should the recent changes to Magisk allow me to run SambaDroid without having to manually change the SELinux Mode?
If so, it doesn't work yet, but maybe I am misunderstanding the changelog references.
andrewsfm said:
Perhaps someone can clarify for me...
I use Magisk and I've noticed that it was recently updated and there are mentionings about SELinux/sepolicy and pseudo enforced, etc. in the changelog.
Whenever I run SambaDroid it will fail to start unless I open the SELinuxModeChanger app and change the mode to Permissive first, which of course ruins SafetyNet, so I can't just leave it in that mode all the time.
I have to go back and change it to Enforcing when I am done.
An extra step I'm hoping won't be required in the future. Perhaps on a per-app basis like MagiskHide.
Should the recent changes to Magisk allow me to run SambaDroid without having to manually change the SELinux Mode?
If so, it doesn't work yet, but maybe I am misunderstanding the changelog references.
Click to expand...
Click to collapse
The update in v11 you're talking about should be able to hide permissive SELinux from SafetNet. In other words: you should be able to leave SELinux permissive and still pass SafetyNet with the help of Magisk Hide.
Didgeridoohan said:
The update in v11 you're talking about should be able to hide permissive SELinux from SafetNet. In other words: you should be able to leave SELinux permissive and still pass SafetyNet with the help of Magisk Hide.
Click to expand...
Click to collapse
Ahh okay, I get it. Just tested it now and it works exactly like you described. It wouldn't pass SafetyNet before on the previous version but apparently does now after the upgrade when left in permissive. Thanks!
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
Hmm... Interesting. I think I'll do some tests myself.
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
Ok. I've tested and it seems to work as expected.
What I did was add a file in /magisk/.core/post-fs-data.d named 08setperm (doesn't matter what the file is named). In that file I added:
#!/system/sh
setenforce 0
This way SELinux is set to permissive at boot.
Disabled Magisk Hide, rebooted and verified that SELinux now was set to permissive on boot (typed getenforce in Teminal Emulator).
Enabled Magisk Hide again and voila! Typing getenforce in Terminal emulator now reported Enforcing and SafetyNet passed.
No idea if this will make SambaDroid work though...
I found a way to somewhat replicate what I am experiencing.
You'll need SELinuxModeChanger (SELMC) to see if you get the same results.
Although I'm wondering if it may be the cause of the problem...
Open recent apps and clear everything out.
Open SELMC and change to permissive.
Hit the home button.
Launch Magisk Manager and check SN. Should pass.
Hit the home button.
Clear recent apps.
Open SELMC, and it's back to enforcing.
Change back to permissive.
Hit the home button.
Re-launch MM and check SN, and it comes back CTS fail.
If you stay in MM and wait for a while, occasionally clicking check SN, eventually, it'll pass without changing anything.
If you change tasks over to SELMC, you'll see it's still in permissive as well.
It appears the transition from enforcing to permissive causes SN to fail for a while, and SELMC reverts back to enforcing if cleared from recent tasks, and re-activating it causes SN to fail for a period of time?
andrewsfm said:
I found a way to somewhat replicate what I am experiencing.
You'll need SELinuxModeChanger (SELMC) to see if you get the same results.
Although I'm wondering if it may be the cause of the problem...
Open recent apps and clear everything out.
Open SELMC and change to permissive.
Hit the home button.
Launch Magisk Manager and check SN. Should pass.
Hit the home button.
Clear recent apps.
Open SELMC, and it's back to enforcing.
Change back to permissive.
Hit the home button.
Re-launch MM and check SN, and it comes back CTS fail.
If you stay in MM and wait for a while, occasionally clicking check SN, eventually, it'll pass without changing anything.
If you change tasks over to SELMC, you'll see it's still in permissive as well.
It appears the transition from enforcing to permissive causes SN to fail for a while, and SELMC reverts back to enforcing if cleared from recent tasks, and re-activating it causes SN to fail for a period of time?
Click to expand...
Click to collapse
Sounds like MagiskHide deamon takes a short wile to start up after the change, or something like that. Seems normal to me... If you wan't a more permanent solution than SELMC, try using the script I posted earlier.
Didgeridoohan said:
Sounds like MagiskHide deamon takes a short wile to start up after the change, or something like that. Seems normal to me... If you wan't a more permanent solution than SELMC, try using the script I posted earlier.
Click to expand...
Click to collapse
I gave your script a try, but it didn't work.
I created the file with the same contents/name by copy/paste, and put it in the folder you specified using Root Explorer.
Rebooted the phone, and checked selinux status using "sestatus" and it said enforcing.
Tried manually typing in the commands in your post into terminal emulator...
#!/system/sh (which didn't show a response.)
setenforce 0 (responded "Couldn't set enforcing to 0. Permission denied.")
So I tried...
su
setenforce 0
After that it shows permissive.
Ran SambaDroid, and it works fine, and SN passes.
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
andrewsfm said:
...
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/Shebang_(Unix)
MagiskHide sets pseudo-enforcing since Magisk 11 because enforcing is needed to pass SafetyNet
andrewsfm said:
I gave your script a try, but it didn't work.
I created the file with the same contents/name by copy/paste, and put it in the folder you specified using Root Explorer.
Rebooted the phone, and checked selinux status using "sestatus" and it said enforcing.
Tried manually typing in the commands in your post into terminal emulator...
#!/system/sh (which didn't show a response.)
setenforce 0 (responded "Couldn't set enforcing to 0. Permission denied.")
So I tried...
su
setenforce 0
After that it shows permissive.
Ran SambaDroid, and it works fine, and SN passes.
Suggestions as to what is stopping permissive from applying at boot using your method?
What does #!/system/sh do?
Sorry, I don't know much about Linux, but I'm open to learning.
Click to expand...
Click to collapse
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Didgeridoohan said:
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Click to expand...
Click to collapse
Yeah, I used notepad... Should have used UltraEdit I guess?
Just downloaded your script and installed it, and it works fine now.
SambaDroid worked right off the bat without needing to remember to open SELMC every time before and after.
Thanks!
Didgeridoohan said:
Could be that your file doesn't have the proper line endings. What text editor did you use (Notepad doesn't work)?
I'm attaching the file I used. Unzip it and place it in /magisk/.core/post-fs-data.d, reboot and see if that works.
By the way, I just realised I mistyped earlier. Not at all what i had named the file... Fingers going on auto I guess. Updated my earlier post.
Click to expand...
Click to collapse
Is this a bug in Magisk?
Meowdib said:
Is this a bug in Magisk?
Click to expand...
Click to collapse
No. Why do you think that?
andrewsfm said:
Nevermind my last post... Picked up the phone again, and opened SELinuxModeChanger and found that it had reverted back to enforcing on its own. Changed it to permissive, and then went back to Magisk Manager, and SafetyNet fails until I revert the setting back to enforcing. Seems like it works the first time, and then stops?
Click to expand...
Click to collapse
I have an S7 and a modified stock kernel with SELinux permissive. I enabled Magisk hide and only enabled SystemUI and SafetyNet passed.
Sent from my S7.
andrewsfm said:
Yeah, I used notepad... Should have used UltraEdit I guess?
Just downloaded your script and installed it, and it works fine now.
SambaDroid worked right off the bat without needing to remember to open SELMC every time before and after.
Thanks!
Click to expand...
Click to collapse
Sorry for reviving a somewhat old thread. I was just curious if with this script, do apps that need SELinux Permissive work, AND SafetyNet still passes? Thanks!
jbw716 said:
Sorry for reviving a somewhat old thread. I was just curious if with this script, do apps that need SELinux Permissive work, AND SafetyNet still passes? Thanks!
Click to expand...
Click to collapse
Magisk Hide have a pseudo-enforcing feature that will make SELinux seem enforcing to hidden apps, even though it's permissive. Including SafetyNet.
So the answer to your question is: yes.
I request a thread regarding this issue. The script is very helpfull and i currently dont know any other way making selinux stay permanently on permissive. Many people are having this issue with soundmods like arise which require permissive selinux. Thnaks!!
nadejo said:
I request a thread regarding this issue. The script is very helpfull and i currently dont know any other way making selinux stay permanently on permissive. Many people are having this issue with soundmods like arise which require permissive selinux. Thnaks!!
Click to expand...
Click to collapse
Are you asking for a module to install the necessary script? Like I've provided here https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549.
Hi Guys!
Recently I hope to use Tasker to do something automatically when the phone is turned on, but I found that Tasker can't start when my phone is turned on but locked.
So I wrote an Android app that uses the shell to enter the password at boot time, but even if I used DirectBoot mode(developer.android.com/training/articles/direct-boot) it still doesn't work.
So I tried to write a module using Magisk, and automatically entered the password when I booted. This time I raised succeeded.
I think there may be other people who have the same needs as me, so I do a function that can customize the password for others to use.
At first we need install AutoInputBootPinManager(github.com/ZeroingIn/AutoInputBootPinManager) to configure your PIN. The application needs to grant root privileges.
Next we download and install this module(github.com/ZeroingIn/AutoInputBootPin) and reboot phone to enjoy it.
If you have any questions, please submit an issue.
Thank you all.
Interesting idea.
There are several modules available that use a shell script UI, run through a terminal emulator, to change settings for the module. App systemizer, Unified Hosts Adblock, MagiskHide Props Config, Energized Protection, etc. Take a look at them for inspiration.
A couple of things:
An explanation of the command in post-fs-data.sh might be a good idea.
Code:
supolicy --live "allow untrusted_app default_android_service service_manager find"
And, why are you setting this prop? As far as I can tell that's for the app Brevent...
Code:
log.tag.BreventServer=DEBUG
Didgeridoohan said:
Interesting idea.
There are several modules available that use a shell script UI, run through a terminal emulator, to change settings for the module. App systemizer, Unified Hosts Adblock, MagiskHide Props Config, Energized Protection, etc. Take a look at them for inspiration.
A couple of things:
An explanation of the command in post-fs-data.sh might be a good idea.
Code:
supolicy --live "allow untrusted_app default_android_service service_manager find"
And, why are you setting this prop? As far as I can tell that's for the app Brevent(play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en)...
Code:
log.tag.BreventServer=DEBUG
Click to expand...
Click to collapse
Thank you very much for your advice, I will try it. Any progress, I will be posted in this post.
The setting of this prop is my mistake, and you have carefully discovered this bug that I have not noticed.
Because I was a beginner to make the Magisk module, I didn't see the Magisk Module Template(github.com/topjohnwu/magisk-module-template) at first, so I wrote it with reference to the Privileged Api Booter(github.com/Magisk-Modules-Repo/magisk-privileged-api-booter).I will fix this problem right away.
ZeroingIn said:
Thank you very much for your advice, I will try it. Any progress, I will be posted in this post.
The setting of this prop is my mistake, and you have carefully discovered this bug that I have not noticed.
Because I was a beginner to make the Magisk module, I didn't see the Magisk Module Template(github.com/topjohnwu/magisk-module-template) at first, so I wrote it with reference to the Privileged Api Booter(github.com/Magisk-Modules-Repo/magisk-privileged-api-booter).I will fix this problem right away.
Click to expand...
Click to collapse
In that case you have a couple of more things to rectify. The first part I mentioned, about the post-fs-data.sh script is also from that module. So, I'm going to assume you do not need it for your purpose. I'd suggest removing that as well... And after you've done that, you should also go in and edit config.sh and change PROPFILE and POSTFSDATA from true to false, because you're not using them anymore. From the looks of it you're only using service.sh, so only LATESTARTSERVICE needs to be active.
Didgeridoohan said:
In that case you have a couple of more things to rectify. The first part I mentioned, about the post-fs-data.sh script is also from that module. So, I'm going to assume you do not need it for your purpose. I'd suggest removing that as well... And after you've done that, you should also go in and edit config.sh and change PROPFILE and POSTFSDATA from true to false, because you're not using them anymore. From the looks of it you're only using service.sh, so only LATESTARTSERVICE needs to be active.
Click to expand...
Click to collapse
You are right, I modified it with reference to the template.Thanks a lot.
Are you going to.update this at all?
I have a bug if you are...
I only have 1 pin... But all 3 fire... Since there's no way to stop them without deleting it from the script
Hi Everyone,
I am aware these things happen and as of yet I have not found a work around.
=> It only works if I unflash Magisk 19.3 or downgrade to the previous version of the Keytrade app (5.0.9)
=> it appears not be triggered by Magisk manager nor by the presence of certain downloads related to rooting.
=> Magisk hide is not able to fix this.
Tested on a Sony Xperia Z1c with AICP ROM. If I can be to any use to the dev, please drop me a line.
Could be using the stat & uds detection method. @topjohnwu already has a fix for that, just needs some time to implement it.
Didgeridoohan said:
Could be using the stat & uds detection method. @topjohnwu already has a fix for that, just needs some time to implement it.
Click to expand...
Click to collapse
For a workaround see this thread https://forum.xda-developers.com/apps/magisk/app-detecting-root-saftynet-pass-t3940628
https://github.com/Ingan121/UDSBypass
So you were right on the money!:good:
Jeroen1000 said:
For a workaround see this thread https://forum.xda-developers.com/apps/magisk/app-detecting-root-saftynet-pass-t3940628
https://github.com/Ingan121/UDSBypass
So you were right on the money!:good:
Click to expand...
Click to collapse
Hello !
I have the same problem and no method works... And there are a new update for the app (5.1.1).
Pims13 said:
Hello !
I have the same problem and no method works... And there are a new update for the app (5.1.1).
Click to expand...
Click to collapse
Exit all 'su's running on terminal. If it still doesn't work, run 'su -c chmod 600 /sepolicy /sys/fs/selinux/policy' and 'su -c killall su'.
Ingan121 said:
Exit all 'su's running on terminal. If it still doesn't work, run 'su -c chmod 600 /sepolicy /sys/fs/selinux/policy' and 'su -c killall su'.
Click to expand...
Click to collapse
The chmod doesn't work... "Not a directory"... -_-
Pims13 said:
The chmod doesn't work... "Not a directory"... -_-
Click to expand...
Click to collapse
Try the app first. If it's not working, run 'su -c ls /sepolicy /sys/fs/selinux/policy' and show me the result.
Thanks linked solution of su -c chmod 000 /proc/net/unix fixed my o2 Banking App too ?
Ingan121 said:
Try the app first. If it's not working, run 'su -c ls /sepolicy /sys/fs/selinux/policy' and show me the result.
Click to expand...
Click to collapse
I'm not authorized to post external links...
I have the same error message : not a directory
Pims13 said:
I'm not authorized to post external links...
I have the same error message : not a directory
Click to expand...
Click to collapse
Does the app crash immediately? Or it crashes after about 10-15 seconds?
Ingan121 said:
Does the app crashes immediately? Or it crashes after about 10-15 seconds?
Click to expand...
Click to collapse
The app crashes immediately...
Pims13 said:
The app crashes immediately...
Click to expand...
Click to collapse
Run 'su -c killall su' and check if the app works. If it's not working, install RootbeerFresh on Google Play and check if everything passes.
Hello I have same problem with my oneplus 6 for banking app
So what I did? This may help you
1st restore magisk manager if you hide it
Uninstall magisk
Flash the rom again no need to wipe data
Install magisk latest version
Open magisk manager
Hide magisk and in setting enable magisk hide and magisk core mode only
And hide all app in magisk manager
Or
Simply before doing all bla bla stuff above try this first
Hide magisk and in setting enable magisk hide and magisk core mode only
And hide all app in magisk manager
If work use it for 1 or 2 hrs then try disable core mode only then check still app detecting root
Because some module cause root detection even safty net pass
Pims13 said:
The app crashes immediately...
Click to expand...
Click to collapse
immediately and the app opens a website with the warning from keytrade.
After a reboot of the device the keytrade apps always opens a website with the warning.
Rootbearfresh results los 16
Should we download an older version of the keytrade app of accept that we can't use the mobile app anymore?
Same issue for me, I'll try the solutions mentioned above.
Yes! I did it - I passed all the checks on Rootbeefresh except the UDS one.
Then I ran this script that's mentioned before and it worked for me:
https://github.com/Ingan121/UDSBypass
I deleted root apps and I reinstalled the Keytrade app.
flotheking said:
Same issue for me, I'll try the solutions mentioned above.
Yes! I did it - I passed all the checks on Rootbeefresh except the UDS one.
Then I ran this script that's mentioned before and it worked for me:
https://github.com/Ingan121/UDSBypass
I deleted root apps and I reinstalled the Keytrade app.
Click to expand...
Click to collapse
I have follow your solution and finally it's work for me also now / no needed to reinstall keytrade after script run keytrade run immediately
Thanks
It's finally working ! \o/
I did Rootbearfresh, I don't pass all the test, I created the script I copied in /data/adb/service.d, I executed the command and ta dam !
Thanks all !
Just as a FYI: the UDS detection method has been circumvented in the latest Canary release (19307) and will of course be included in the next beta/stable release. Yay.
Hello everyone, I try to create a module to replace my build.prop because I do not please change it (system play only).
I do not understand much to magisk modules, can someone make me the module or I can put my build,prop please?
Or if impossible to replace the buil.prop by magisk, can be add the line :
persist.debug.wfd.enable=1
Thank you I've been trying since yesterday and I really can't do it so it seems to be simple
You don't need a module to do that.
Edit: For future reference... I've been reminded that persist props are, well, persistent. No boot script is needed, just run the resetprop command and the value will remain set even across reboots. Until a new value is set, of course.
Simplest way is to just use a boot script and the resetprop tool:
Code:
resetprop persist.debug.wfd.enable 1
Or if you really want to use a module you'll just have to add the line to system.prop and nothing else:
Code:
persist.debug.wfd.enable=1
Or you could use MagiskHide Props Config and the custom prop feature.
And Magisk doesn't actually alter the build.prop file:
https://github.com/Magisk-Modules-R...etting-a-custom-prop-or-removing-a-prop-value
Thank you for this quick response. I'm going to try to figure out how to do this script because I really don't know all this
Hi, I solved the problem with the module activated and in termux
Code:
su
Props resetprop persist.debug.wfd.enable 1
Now he finds the TV but restarts the phone as soon as he connects on it
If you're having problems creating a boot script it might be easier to use the MagiskHide Props Config module. It'll do it for you.
Hi, I aI think I did it. Here's how to do it with the installed module magiskhide props
Code:
su
Props resetprop persist.debug.wfd.enable=1
He finds me the TV, but as soon as he connects to the phone restarts is there a way to solve this problem?
chuppito said:
Hi, I aI think I did it. Here's how to do it with the installed module magiskhide props
Code:
su
Props resetprop persist.debug.wfd.enable=1
He finds me the TV, but as soon as he connects to the phone restarts is there a way to solve this problem?
Click to expand...
Click to collapse
I'm not sure what you're doing there, but that's not right...
If you're gonna use MagiskHide Props Config, just run
Code:
su
props
And then pick the "Add/edit custom props" menu (#4). Follow the on-screen instructions to set your prop.
If you're going to use resetprop as a standalone tool you run:
Code:
su
resetprop persist.debug.wfd.enable 1
That will only survive until a reboot though, which is why you would have to put the line in a service.d boot script if you want it to be permanent.
Edit: For future reference... I've been reminded that persist props are, well, persistent. No boot script is needed, just run the resetprop command and the value will remain set even across reboots. Until a new value is set, of course.
If I use props, I have no options
If I use setprop it doesn't tell me anything
Edit :
With props where I have more options I managed to do.
It was already on 1 while it started again several times.
I watch as soon as I get home if it connects or restarts as soon as it tries
The TV is well detected but as soon as I try to connect, the phone makes a small reboot
chuppito said:
If I use props, I have no options
If I use setprop it doesn't tell me anything
Edit :
With props where I have more options I managed to do.
It was already on 1 while it started again several times.
I watch as soon as I get home if it connects or restarts as soon as it tries
Click to expand...
Click to collapse
Does your edit mean you figured it out? If you didn't, here goes:
From your first screenshot, showing the props module ui, it tells you to "Enter the prop to set". So if you enter persist.debug.wfd.enable you'll get to the next screen where you can enter your desired value (and also see what the current value, if any, is).
The second screenshot is exactly as it should be. You're not supposed to get any feedback if it works.
About your other issues, I have no idea...
Yes I was able to understand how it works. I found a post for other problems on xda, if I understand, google deleted files last July to make this trick obsolete and sell its chomecast
Hi guys,
I'm trying to make a script to enable the android 11 notification shade blur in my pixel 2 xl,, so far I have managed to successfully enable it with ADB with this command:
adb shell
taimen:/ $ su
taimen:/ # setprop ro.surface_flinger.supports_background_blur 1
taimen:/ # stop
taimen:/ # start
It does work fine but as soon as the phone reboots it is lost
I made a magisk module and also managed to make a setprop mod with magiskhide that does indeed successfully add ro.surface_flinger.supports_background_blur 1 in build.prop, but the mod does not work unless I adb and input the command
adb shell
taimen:/ $ su
taimen:/ # stop
taimen:/ # start
I believe this is to restart system UI.
Is there any way to do this in magisk automatically at boot?
When I input in termux
su
# stop
The phone seems to try to restart the UI but it gets stuck in google logo, unlike when I do it via adb the screen goes blank and comes back alive when I input via adb
# start
I'm a complete noob in this stuff, I would really like to make a magisk script or module that let me do this, it would be useful to try first via termux to avoid a magisk boot loop in case something goes wrong with this script. The notification blur is actually the only reason I unlocked the bootloader an rooted the phone...
Thanks in advance.
You should use Magisk's resetprop tool.
All you should need in your boot script is this:
Code:
resetprop ro.surface_flinger.supports_background_blur 1
Try using service.d first, but if that doesn't work move the script to post-fs-data.d.
Or, if you're using a module, use a system.prop file.
Does "magiskhide props config 5.3.6" uses resetprop?
I did try that in service.d and post-fs-data.d
As I said, the property does seem to be changed with the setprop, since after a restart of the phone all I need to do is
Adb shell
Su
Stop
Start
And I get the blurred notification shade...
Yes, MagiskHide Props Config uses resetprop (but there you generally don't need to change to late_start service or post-fs-data, the default should be fine most of the time).
With resetprop you shouldn't need to run stop/start. That's the difference.
I did not try the delay option. I really don't know what else I could try though...
Maybe there's a delayed script I could run with the stop/start command?
Edit: sorry if I understand what you're saying, should I delete the magiskhide props config key and instead do it manually? That way I should no need the stop/start command.
I thought you had been doing it manually all along... To quote your first post: "I'm trying to make a script", "I made a magisk module and also managed to make a setprop mod".
If the stop/start commands need to be included for this to work, making your own boot script with the resetprop command and stop/start commands is the way to go.
Yeah yeah sorry, I did manage to make the module, the setprop mod I was referring to was via magiskhide...
My problem is when I try to run this stop/start script in termux
#!/system/bin/sh
su
cd
cd data/adb
stop
start
The phone goes to google logo and is stuck there, I'm afraid if I do that with magisk I could get a non booting phone...
Does this script sounds good to you?
#!/system/bin/sh
resetprop to.surface_flinger.supports_background_blur 1
stop
start
BTW I really appreciate your help!
Edit: just ran this script from termux and stuck at google logo...
Edit 2: if anyone is wondering or maybe it helps someone I ended up making this simple script in service.d
resetprop to.surface_flinger.supports_background_blur 1
Then I discovered all I needed was the terminal command
# killall surfaceflinger
And Systemui does successfully restart with the blurred background, so I created a home screen shorcut with this terminal command and all I need to do is hit the shorcut shortly after booting and it works, it's not automatic but it gets the job done...
Thanks @Didgeridoohan for your help... XDA rocks!
Hello!
I don't know if you're still looking for this but decided to share anyway.
Attached to this post is a Magisk module that enables Background Blur that survives reboots....
It's weird that a simple Magisk module with a system.prop doesn't work but ok... had to create this version which uses a service.sh script to do the job.
You'll need Magisk, obviously.
Enjoy!
Cheers!
Thank you for making this. The double restart is kinda annoying tho
Typhus_ said:
Hello!
I don't know if you're still looking for this but decided to share anyway.
Attached to this post is a Magisk module that enables Background Blur that survives reboots....
It's weird that a simple Magisk module with a system.prop doesn't work but ok... had to create this version which uses a service.sh script to do the job.
You'll need Magisk, obviously.
Enjoy!
Cheers!
Click to expand...
Click to collapse
Is this module device specific or will it work on other devices running Android 11?
rodken said:
Is this module device specific or will it work on other devices running Android 11?
Click to expand...
Click to collapse
It should work on any device running Android 11.
Typhus_ said:
It should work on any device running Android 11.
Click to expand...
Click to collapse
Perfect - functions as expected on OnePlus 8 OOS 11.
How about android 13?