View Single Post
Posts: 1,313 | Thanked: 2,978 times | Joined on Jun 2011 @ Finland
#458
Originally Posted by naytsyrhc View Post
I think this was mentioned already, but somehow after a reboot profilematic always complains about credential files removed and that flight mode will not be affected by rules. Is there a workaround for it? (Reinstalling profilematic does not help). Would it help to install Profilematic with inception?
Installing with Inception should work, in theory. I haven't tried it myself yet, so I can't offer any assistance. Please provide some instructions if you get it working.

I have an app installed called "toggle flight mode" which works, so I thought Profilematic should be able to do so as well even without tricks like inception or am I wrong?
The difference is that ProfileMatic is a background task. In technical jargon, ProfileMatic requires credentials to run the background task as "user" and with the credentials needed to change flight mode. The Flight Mode toggle only needs the credentials to change flight mode. When I was fighting with the Aegis credentials I found it was hard to keep both of them reliably.

One workaround, besides Inception, may be to use ProfileMatic's "Custom action" to run the Flight Mode toggle application.

I could, perhaps, create a separate application with only the Flight Mode changing capabilities that ProfileMatic would call when flight mode was changed. That might, or not, retain the credentials better. But I have really low motivation to spend any time on fighting
the credential bug, as it will probably be fixed in PR1.3, thus wasting the time I'd use on it. Inception and open mode kernel are the only long term solutions, but we'll see when PR1.3 comes around.
__________________
My N9/N950 projects:
 

The Following User Says Thank You to ajalkane For This Useful Post: