[HTC One X] show-p1984:
To the discussion at hand:

You behaved wrong. You practically told ppl that this is **** and they should move on to other stuff + you provided links for the other stuff.

I am generally not mad if you choose another kernel, I won't hate you and won't send you hate emails. I don't even care if you don't like it, just don't bash my hard work. I have put ~8000 hours in android kernel development (that's a realistic number + only my free time), some of that stuff is in this kernel now too. That was time I could have spend working a 2nd job, being with my gf or family, or juggling my junk. So the bare minimum of what I expect from postings in this (!my!) thread is respect. You can reason/argue with me logically and I will have no problem with that.

You don't enter someones backyard and then scream that this looks like **** and xyz's backyard is that much better and all the guests should rather go over there. You additionally provided the address and means to get there on a sign in that backyard. Perhaps you can now see how wrong that was.

Your post was, in contrary to what you believe, not helpful. I have no idea why these issues occurred on your phone, but from the rather insufficient information nobody will be able to tell you what happened. Issue reports should generally contain a log from the incident + as much information as humanly possible. (but then again there was not enough room in your post for that due to advertising for other projects :cool:)

Furthermore: Why do you call this kernel not stable?

I was the one who fixed the random reboot problems on the HTC source. I fixed the lower-frequencies-are-not-used issue from the HTC source, I fixed a lot of compiler bugs from HTC, I fixed the section mismatches (the right way) that HTC left us which most likely would have resulted in additional reboots.

All remaining issues are not stability issues. I have never had my phone reboot, lockup, shutdown when I didn't want it to. It has been rock stable. Sometimes I have to press the powerbutton 5-10 times fast to get it to wake up properly, ok granted, but that is still not a stability issue and it is most certainly not my fault. HTC did leave us a lot of surprises with this source.

######

To the deep sleep s2w issue:

This issue is known, and I already wrote it like 3 times in here. There is a problem with the touchscreen driver (dumbed down: 'sleeps too deep'), and there is another problem which seems to be connected to the ninja core which does not react quick enough on incoming interrupts. Don't ask me why yet, this is my first tegra device. Furthermore this does elude my logic, since interrupts should not be dependent on the core that receives them. This also causes the power-button-has-to-be-pressed-5-10-times-fast-so-the-phone-wakes-up problem. It may be connected to the tegra keyboard handler, which has a, lets say 'unique' configuration I have never seen before.

I have collected tons of logs on this issue and the only fact I got from them: The phone does behave as if the power button is not pressed, sweep2wake is not triggered because there is no interrupt received (for both wakeup methods) to wake up the phone in order to get touchscreen positioning data and that's why the power button + s2w (which essentially only emulates a power button press) is failing.

######

2 guys have this. Both wrote about it the second time. Both have the means to reproduce it 100%, yet both have not reported the issue to the kernel issue tracker with a kernel log and as much information as humanly possible?

You wonder why it doesn't get fixed? - That's why. (can't read your mind, doh!)

I was never able to reproduce this and haven't seen one helpful kernel log yet. :/