Confirmed Expert Mode

[unclefab]

I'm still using Xprivacy 2.0.25, cuz from version 2.0.30 something the so called dangerous functions have to be ticked manually.
Which means that when I upgrade to a new Xprivacy version it messes all my restrictions by unticking all the dangerous functions, and leaves me alone to clean the mess and retick all those restrictions.
I tried to import from a backup but no dice, the "dangerous" functions still have to be ticked manually.
Not very convenient, to say the least, moreover that I don't remember all what is restricted on all apps and would need to test again (specially with the system apps).
Another problem is that when I install a new app those functions are not disabled (eventhough they are ticked in my template), which means that my phone is unprotected until I do the job manually. In my template everything is disabled cuz that's the best way to prevent privacy leaks, but what's the point if it's not applied...
Could you implement a kind of expert or confirmed expert or whatever mode, for people that know what they are doing, where those perms don't need to be set manually and where Xprivacy doesn't mess with the existing restrictions?
I have been on Xprivacy since the days of version 0.30 and I allways restricted most of those perms, my phone never exploded:-)
At the worst I get a bootloop, so what? I enter recovery and fix it in two minutes from my file manager, that's not rocket science...
Thanks in advance!

[M66B]

Try again with the latest stable, but wait until the update service has completed before drawing conclusions.

Even if this doesn't work (it should), then you can use the new template merge option, perhaps using one of the alternate templates, to restrict all dangerous functions.

[unclefab]

I allways wait for the update to complete...
Anyway, I have tried with all possible template/import combinations without any results, it still erases my restrictions on the dangerous functions and then refuses to import them back.
Using a template, be it default or alternate, merging or not merging, is of not much help since obviously all apps don't have the same restrictions.
The conclusion is that if I want to use the latest Xprivacy versions I have to tick/untick manually and test extensively (cuz I don't remember what can and what can't be restricted for all my apps), a long, boring and tedious process.
I don't understand why you've implemented this, really, but for now I have no other choice but to be back again to 2.0.25:-(

[M66B]

Do you have the setting 'restrict dangerous' enabled?

[unclefab]

Of course:-)

[M66B]

I really don't understand why the update for you isn't working.
I will think about it.

[unclefab]

Thanks mate, I appreciate!
But no rush, take your time:-)

[M66B]

Can you please try if this version fixes your problem:
https://crowd.xprivacy.eu/XPrivacy_2.1.5-3.apk

[M66B]

Can you please try this version instead:
https://crowd.xprivacy.eu/XPrivacy_2.1.5-4.apk

[unclefab]

Version 2.1.5-4 works well, thank you Marcel, you're The Guy!!!
Respect...