[Greenify] kevin_1351:
I do not doubt that he's a good dev, I just said that he hasn't been replying messages. And it's really not me doing anything wrong or not knowing what i'm doing. My phone worked like our society did before justin biebs came to the power, in other words: really well. But something/ a bug has messed with greenify, and that's not my fault...

The thing with the firewall was only an example in order to make you understand what i meant. If it uses pm-disable though, and it starts after 3 minutes. It means that it may be some script file, getting launched right after boot. Android apps that don't really start at the boot process, start 2-5 minutes after boot right? SO as i've always said until now, maybe there is somewhere a file that sets those pm-disable commands.

Also, to all of you wondering why Bluetooth share etc gets woken up again, pm disable, if that really is what it's using, doesn't necessarily hinder the app from waking up again, or am i completely wrong? I've read it somewhere months ago

Of course I have catlog, but a log cat is just a system log. What meant was that ios handles this stuff a bit better. Everyone here says that android is much easier to mod and so on but i think it's not true at all. Well since xposed came to light a lot has been getting better but we are still lightyears back. What I mean is that if you want to mod something on ios, all you do is using the autoupdating cydia app store. And mods that behave on a system level like greenify for instance are kinda sandboxed. All of them rely on something called mobilesubstrate(cydiasubstrate), once you turn that off, a bit like xposed but still not the same, EVERY system mod based on MS stops working, there's no processes left. So you could basically trace a problematic module/mod/whatever pretty fast. That besides, what i mean with fragile is that let's say your permissions file is ****ed up in android. With ios you only have to attach it to the pc, and replace it or whatever. Et voila it works. Here I tried everything really, from restoring my permissions file, to using permissions fixing scripts and what not. But in the end there was a REAL CHANGE for every app in the system, none of them had the right permissions anymore. So a filemanager for instance didn't have the permission to even look at the filesystem.

Also, force closes are A LOT more common here than on ios, as i said, because of the way they are sandboxed etc.

I'm getting a bit of topic, and don't get me wrong, ios has a lot of problems too, but i think it's way better structured.

The main problem really hasn't anything at all to do with my apps. Before I greenified those system apps everything was working as butter.

The same goes for the months before samsung introduce that awesome bug that came with kitkat.

The problem is, the greenify app doesn't change greenifies settings anymore. It feels like a dummy ui app. After every reboot greenifies settings get back to 0. And the app list of hibernated apps return after every uninstall. That means that i can't follow your guide. And the system apps I could try with, are all forceclosing, because that stupid my magazine app is frozen. (even before those 3 minutes)

Well, I'm tired of this, i'll restore my phone now..... so be it...

Thanks for your help though, next time I won't ever touch system apps with greenify again.

Cheers