[Galaxy S II Original Android Development] D.O.C:
That one has happened to me before, randomly, not on this kernel, not on this base, but it has happened to me on HD2, and SGS2.

Of course kernel can overheat your phone, but honestly, I dont think this is the case here.

We have been running the same kernel for about 10 days now, and it has not happened.

When we tested other kernels (I am not mentioning which ones cause it is not my style to talk trash), three of three people experience overheating, so we drop it.

Testing yet other kernels, 3/3 experience either lagging, battery drain, etc, etc, etc. So we were on the same channel, and testing properly.

Then, when we finally manage to build the kernel, the three of us tested, no problems found. Then out for beta testers, and no problems reported there either. That is the reason I am sure is not kernel releated.

Anyhow, every device is different, and have different behaviours.

BUT, It is far more likely that the overheating is caused by:

1. Misbehaving app on your system, some that may be constantly downloading data, or has been corrupted at its database so it cannot read the information thus entering a nonstoping cycle.

2. maybe you entered a poor signal phone quality area, on which, data was interrupted abruptly, thus making apps misbehave. (this one right here is my case, no matter what device, rom, kernel, apps, etc, certain areas (physical areas and its reproducible) cause either rebootin of phone entering bootloops or overheating. I know its the signaling because, if I turn off automatic network search on my phone or turn on airplanemode, this phenomena dissappears.

3. Bad download.

4. Your device doesnt like the default powersaving features of the kernel (notice its last, cause we have yet to find an incompatible one, because this features are not aggressive enough to cause overheating)

So, redownload base rom and whatever surgeon/theme u are using and place them again on sd card, replacing the olde ones, clear data, format/dalvik, flash androidmeda, reboot recovery, flash surgeon or theme, reboot phone, reinstall your apks or restore them without data, and try again.

That same procedure I have been doing long enough and it has never failed me. If bug is there, after clean wipe and redownload/reflashing bug will appear (dont install apks if you want to reproduce a bug that u know its rom related). If bug is not there anymore, be happy, cause, as long it is ur fault, you can solve it :).

Now, be assured that our releases has been tested and retested and released only when considered safe, solid, and ready for daily use.

We are not samsung, HTC or professional providers.

We are just guys that have a hobbie and want to share their fun with you.

We are not looking for donations, greatness, fame, or intend to commercialize this.

We are not competing with anyone, as a matter of fact, adopting some of what great minds on XDA have done we believe is a very productive way of start. The latter s why, all of our work we do, intend to do as opensource as possible, creating gits, and sharing the "secrets" with anyone who wants, because we are inside a community, a great one called XDA.

We are just having fun with our devices, same like you are. Please keep that in mind. We dont have any psicology department to keep the spirit up when developing.

Imagine building a new rom and coming with new ideas, and people telling you at thread your work does not function when, you are certain (cause you built it and tested it yourself) that the bug is being caused because you flashed ANOTHER framework-res.apk or systemui.apk....lol.

We obviously dont have some of the factors that arise when releasing public, frankenising the build if I may call it that, doing such moves like trying to alterate an apk by yourself, then having the FC and blaming the build itself. Main reason I believe for HTC to lock bootloaders, or samsung to warn you with a BIG yellow ugly triangle that u are on your own now and you dont have support.

So please, have fun with this, if it doesnt meet your requirements, good, if it does, we are very glad.

:D

cheers.