[Android Apps and Games] krzych:
Never said I trust LBE - rather the opposite. But I have really big problems now with PDroid itself, so I suppose I have not much choice around.

Since above is connected to the below answer, it's not really necessary, open source can be rooted ig you publish both, patch and app. Waste of your time to be honest.

Latter has many disadvantages, repo has many more advantages than just publishing the source - git/svn/cvs/similar is a tool for a dev which is a must - problably you are using one right now, so setting up a repo would only be one-time job exposing any version control system to the public, which is rather quick to do, and publishing sources one by one on the forum is rather harder to maintain (what we see right now - the sources are few versions back).

To be honest, I would prefer the sources over solution to this. And below I'll answer why.

PDroid is definitely doing something on boot - the answer why is simple - you left the debug logging around and logcat says that PDroid is accessing it's privacy.db million times a second (which the logging itself is a nice overhead for the system and causes real lag - tested on my aplications - logcat can slow down an app even more than 50%).

So, while we know now that PDroid really is doing something on boot, the quiestion is only what. For me it seems that every "access" to the data done by other app is catched by PDroid, checked against the permission set and then answered positively or negatively. If I have a right, then at boot there is a _hell_of_a_requests_. And thats why PDroid makes my system muuuuuch more laggy than usual. You can ask then "but why reboots"? - It's simple - when PDroid causes let's say "i/o wait" for those apps which are trying to access something, other apps are starting - in some point, there is too much apps to maintain in the memory, but killing the apps does not solve the problem because they will be restarted quickly by for example Sense wich wants to show widgets maintained by those apps, so here, a condition race starts which causes at some point something which I do not clearly understand - system_server death. Mayibe it is caused by ss instability, maybe by permissions flying in the air, or maybe something kills it to free memory - I don't really know.

And answering your question about bootloops - we do not understand each other - I used PDroid on the same system a week or more. Nothing really bad happened. Nothing. Everything was fine and I was happy that I found a stable ROM. But then I decided to recover all my apps. And you know the story.

Now, if I had the sources and possibility to compile them (which I have, right now writing an app), I would compile PDroid without the debug logging every privacy.db open/access/close, check that it is better this way and report that this could be solution or not. I would help this way to your time spent on the app, and help myself to get rid of the problem if I have right about this is a speed causing problems.

Screenshots - It's kinda hard to make screenshots when you barely have time to run any CPU usage app because you have seconds to reboot... By the way, I dont even know how to make a screenshot, lol - ok, I'll try to do it by the USB debugging, but I cannot promise because I'm still wondering whether to patch back the system and try to remove some apps, leave this in the state unpatched like I have right now to test the rom itself is ok, or maybe go back to earlier roms to have a piece and quiet life...

I really don't know what to do. Especially I did not want to do anything, I wanted my phone only :).

Never seen it, I have to check this out.

Good to hear :). Next step would be best for patcher - describing how it works inside (smaling/baksmaling and other java crap), because with this, I could do some patches which I couldn't now. I lack the knowledge of what is goin on inside.

[EDIT]

I just caused restart again - without PDroid onboard - as I have to have working phone tommorow, I cannot do debugging right now - switching to older rom, and then I will take a look on PDroid load. Maybe I will see it there too, if not, I will get back to nandroid of this one for a short time just to take few screens and adb shelled top's.