This object is in archive!
SELlinux needs to be set to permissive
Closed
Some weeks ago I reported here that Locus couldn't work in CM13 or in other android 6 roms that I tried.
By chance I found out that if SELlinux is set to permissive, locus works perfectly, but if it is set to enforcing, it doesn't open.
It may help you sort the problem out, as locus is the only app that didn't work.
Regards
The same problem 
Ofcourse I made a typo. It is SELinux.
Ofcourse I made a typo. It is SELinux.
Good day,
well, I spend a while on this. I have SGS2 device with CM13, but I'm unable to make root works to be able to change this SELinux mode. Without change, I'm unable to simulate any problem.
I have no idea why this change has effect on Locus, but currently I don't have a half a day to investigate it more, sorry.
Good day,
well, I spend a while on this. I have SGS2 device with CM13, but I'm unable to make root works to be able to change this SELinux mode. Without change, I'm unable to simulate any problem.
I have no idea why this change has effect on Locus, but currently I don't have a half a day to investigate it more, sorry.
Thank you.
I'll change it back to enforcing and I'll upload some logs for you to check out.
What kind of logs should I create?
Regards
Thank you.
I'll change it back to enforcing and I'll upload some logs for you to check out.
What kind of logs should I create?
Regards
If you may take a log with app called CatLog a while after crash of Locus (do not forget allow CatLog root access to be able to read also Locus logs), it will be best.
If you may take a log with app called CatLog a while after crash of Locus (do not forget allow CatLog root access to be able to read also Locus logs), it will be best.
Thanks for a log. I firstly have to say that I'm quite a newbie if we talk about Linux and mainly this mysterious SELinux stuff.
In log are these two important lines
W/droid.locus.pro(27064): type=1400 audit(0.0:261): avc: denied { open } for name="_libraries.conf" dev="mmcblk0p29" ino=34008 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0 tclass=file permissive=0
E/aiz (27064): java.io.FileNotFoundException: /data/user/0/menion.android.locus.pro/files/_libraries.conf: open failed: EACCES (Permission denied)
which are probably key to this problem. First say that Locus is some "untrusted app" (it is an error from Android itself) and second is error from Locus that it's not able to create certain file on mentioned path. Interesting is, that this file should be by default created in /data/data/menion.android... directory and not this /user/0 ... any idea why this happen?
I've tried to Google little bit about it ( https://www.google.cz/search?q=android+avc:+denied+{+open+}+scontext%3Du:r:untrusted_app ), but there is so much information, that I should firstly spend few hours on study what is going on here :).
Thanks for a log. I firstly have to say that I'm quite a newbie if we talk about Linux and mainly this mysterious SELinux stuff.
In log are these two important lines
W/droid.locus.pro(27064): type=1400 audit(0.0:261): avc: denied { open } for name="_libraries.conf" dev="mmcblk0p29" ino=34008 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0 tclass=file permissive=0
E/aiz (27064): java.io.FileNotFoundException: /data/user/0/menion.android.locus.pro/files/_libraries.conf: open failed: EACCES (Permission denied)
which are probably key to this problem. First say that Locus is some "untrusted app" (it is an error from Android itself) and second is error from Locus that it's not able to create certain file on mentioned path. Interesting is, that this file should be by default created in /data/data/menion.android... directory and not this /user/0 ... any idea why this happen?
I've tried to Google little bit about it ( https://www.google.cz/search?q=android+avc:+denied+{+open+}+scontext%3Du:r:untrusted_app ), but there is so much information, that I should firstly spend few hours on study what is going on here :).
Good day kwizatz,
quite old unfinished problem. Since this, more then year, I received no more similar bug reports that Locus does not run correctly on any CM13+ powered device. Because as I wrote, I'm no expert in this field, I'm closing this topic with hope, you have already correctly working Locus Map app ( if you still use it ).
Thanks for understanding.
Good day kwizatz,
quite old unfinished problem. Since this, more then year, I received no more similar bug reports that Locus does not run correctly on any CM13+ powered device. Because as I wrote, I'm no expert in this field, I'm closing this topic with hope, you have already correctly working Locus Map app ( if you still use it ).
Thanks for understanding.
Replies have been locked on this page!