How to switch SELinux to Permissive?
I really don't want to screw up.
In terminal getenforce is command to check status
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shooter7889 said:
In terminal getenforce is command to check status
View attachment 5324827
Click to expand...
Click to collapse
Thank you so much. So basically all I need to do is switch getenforce to 0, right?
netgar said:
Thank you so much. So basically all I need to do is switch getenforce to 0, right?
Click to expand...
Click to collapse
Yeh u type "setenforce" and 0 to change to permissive and 1 to go back to enforcing
Getenforce us just to checkout which state it's in
Shooter7889 said:
Yeh u type "setenforce" and 0 to change to permissive and 1 to go back to enforcing
Getenforce us just to checkout which state it's in
Click to expand...
Click to collapse
Thank you
Edit: ones I reboot cellphone it's coming back to enforcing.
netgar said:
Thank you
Edit: ones I reboot cellphone it's coming back to enforcing.
Click to expand...
Click to collapse
Yeh I was going to say it wld prob go back to enforcing after reboots anyway. But that u cld switch it back manually if not wanting to reboot
You should only set to permissive to install run want you want then set back to enforcing. Protect yourself not a good idea to leave on permissive
Related
Hey, I am trying to add a face unlock function to my A5 2017 and apparently there is no such option in the Google Smart Lock. I know there is a method to make it work that requires root, but I am unrooted.
I'm running Oreo if that makes a difference
Maybe someone knows how to make the Trusted Face option appear ? Currently I'm only getting this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Afdabrikman said:
Hey, I am trying to add a face unlock function to my A5 2017 and apparently there is no such option in the Google Smart Lock. I know there is a method to make it work that requires root, but I am unrooted.
I'm running Oreo if that makes a difference
Maybe someone knows how to make the Trusted Face option appear ? Currently I'm only getting this:
Click to expand...
Click to collapse
It.s not really supported on ARM now. Only arm64 oreos
MaDaLiNoSt said:
It.s not really supported on ARM now. Only arm64 oreos
Click to expand...
Click to collapse
Oh okay thank you
Magisk module google face unlock makes it appear.
satnavpt said:
Magisk module google face unlock makes it appear.
Click to expand...
Click to collapse
do you understand the meaning of 'unrooted' ?
....................I know there is a method to make it work that requires root, but I am unrooted.
I'm running Oreo if that makes a difference..............
Click to expand...
Click to collapse
Just noticed that when trying to install the 021 Beta, it keeps prompting for an update to a newer version. You click later but the second prompt basically forces you to either update or disable (close app).
Last evening it worked fine. How can we bypass this or what version should we use with the chinese ID to upload faces to a GT2/GT2e? Thx.
Run i use
View attachment 5056117
gagi75 said:
Run i use
View attachment 5056117
Click to expand...
Click to collapse
what are you trying to say and what attachment is that? It's not valid.
Beta ver
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gagi75 said:
Beta verView attachment 5056167
Click to expand...
Click to collapse
and if you delete it and reinstall? Do you get the update prompt that doesn't let you use the app?
zerozoneice said:
and if you delete it and reinstall? Do you get the update prompt that doesn't let you use the app?
Click to expand...
Click to collapse
Yes but... Start app whit out net after swich on when wish to insatll wf thats all
Put it into flight mode before you run it
weird, it was always in airplane mode, but it worked eventually.
i actually now have both beta and newest from playstore installed at the same time, different accounts, watch connected to both (and keeps connection).
Block update.hicloud.com on your dns/firewalle. Problem solved. (for now...)
The full OTA is also available in Oxygen Updater
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, i was waiting for this version!
Same here was looking for it... glad to see!
Just got it this morning.
And holy crap this website now has more ads on mobile than the Sunday newspaper.
Hmm, my device is now failing safetynet, didn't have any of this before with previous updates.
Anyone seeing the same?
plz delete
No issue with safetynet if this what you mean @emontes
Fre$h said:
No issue with safetynet if this what you mean @emontes
Click to expand...
Click to collapse
It is, yes. I have no idea why , though,it was fine on the previous version.
emontes said:
It is, yes. I have no idea why , though,it was fine on the previous version.
Click to expand...
Click to collapse
Did you try to simply disable any Magisk module then reboot just to the if the culprit isn't there ? Is Magisk Hide engaged ?
You can also try to fasboot boot the correct boot.img that is already patched too and see how the assertion react
Anyone notice any sound issues since the update when watching videos or listening to music? I have to crank the volume way up and there doesn't appear to be any bass.
Did you try to simply disable any Magisk module then reboot just to the if the culprit isn't there ? Is Magisk Hide engaged ?
You can also try to fasboot boot the correct boot.img that is already patched too and see how the assertion react
Click to expand...
Click to collapse
Didn't even think of that,been using edxposed for a while and didn't have any issues until now. Found some other people complaining and saying lsposed did the trick and that was it. Thanks!
Anyone else have issues with AdAway not auto updating lists since January update?
Nekromantik said:
Anyone else have issues with AdAway not auto updating lists since January update?
Click to expand...
Click to collapse
You talking about the sources? If so, mine is working fine.
wgrant said:
You talking about the sources? If so, mine is working fine.
Click to expand...
Click to collapse
yup sources
its meant to update every day but I go days without.
I will try re install
Please double check that you have systemless hosts module in Magisk. Because I also am not having any issues. And this will cause adaway to not update
My sources auto-updating fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
danw_oz said:
Please double check that you have systemless hosts module in Magisk. Because I also am not having any issues. And this will cause adaway to not update
Click to expand...
Click to collapse
yup its enabled
Lughnasadh said:
My sources auto-updating fine.
View attachment 5523987
Click to expand...
Click to collapse
Off topic but what are your signal/WiFi icons?
bowlandspoon said:
Off topic but what are your signal/WiFi icons?
Click to expand...
Click to collapse
They are from the substratum theme "Iris".
Lughnasadh said:
They are from the substratum theme "Iris".
Click to expand...
Click to collapse
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Incomming calls cannot be recognized. Most of incomming calls (it not depends on he/shi is or not in my phone contacts) are recognised as "Unknown"
How can I solve this problem?
I had the same problem with another ROM.
For this I had to deactivate VolLTE.
VOLTE/VOWIFI profile was set propably incorrect by phone.
to set it right I must change profile with code:
*#*#663368378#*#*
Then - MBN config loading and activating tool
Then : search for your country operator and select
Choose - All_SUB
Then click on - Act
Wait few sec
Your operator settings will be activated and stored
Incomming calls will be recognised again
This trick works on my phone with Xiaomi.Eu roms
Not working on my phone. I get the attached screen.
dreamdrake said:
Not working on my phone. I get the attached screen.
Click to expand...
Click to collapse
I have same screen
Vega56 said:
I had the same problem with another ROM.
For this I had to deactivate VolLTE.
Click to expand...
Click to collapse
I will rty it. But without VolLTE will calls work normally again?
sab404 said:
I have same screen
Click to expand...
Click to collapse
So propably this working only on Xiaomi.eu roms
Vega56 said:
I had the same problem with another ROM.
For this I had to deactivate VolLTE.
Click to expand...
Click to collapse
I do not see any setting about VoLTE in any menu.
Can you please explain where did you deactivate it?
dreamdrake said:
I do not see any setting about VoLTE in any menu.
Can you please explain where did you deactivate it?
Click to expand...
Click to collapse
You can find it in Sim card settings, or just use settings search
I do not have it..