[HD2 Android SD Development] shamez23:
You don't have to look it up. I read every post of this thread.

However, many users don't. A little heads up from time to time would greatly be appreciated and limit reposts. Remember, some users can't even read back one post above their own. How do you expect people will remember a post 10 or 20 pages back?

You don't have time right now to look into it? Sure, no problem, we'll wait till you find the time. But you have to tell us. You have to ackowledge a problem if one comes up, you have to tell us you'll look into it, you have to tell us if it can't be solved and you have to tell us when you don't have the time to work on it.

Sounds pretty demanding, I know.

But if you don't people will assume they weren't heard or weren't believed. Naturally they'll repeat their posts till they get an answer.

You don't have to write books about what's up, just a line on what's going on will do.

Of course not everyone will read that line, but many of the senior members will and they will tell the others. All in all, reposts and complaints will greatly be limited.

I'm sure that's worth the time.

You are the devs of this build, the moderators of this thread. You are the guys everyone turns to when the **** hits the fan. Interact don't only react.

As I said, this is something new. We are not talking about the BT issues. I'm not even using BT.

Some of the users that like to do tests and try to find the problem, have narrowed those new spikes down to phone calls. Maybe it's the proximity sensor, maybe something else that kicks in when you make a call. There have been several users that wrote about this, some repeatedly. There were no answers to that.

Some of those same users experimented with other kernels. That is not meant as an attack against you. Don't take things personal that are not meant to be personal.

The issue seems to be gone with other kernels. So I can't see anything wrong in assuming that something in ACAs kernel doesn't work so well with the rest of the build. Some kind of incompatibility or a bug, whatever. I'm not a dev, I have no insight in such things, like many other users.

If someone absolutely can't live with those spikes and repeatedly, annoyingly asks for a solution and can't wait for you to solve it, hell, I don't mind if someone like that gets told to use another kernel in the meantime.

You are way to negative. The world is not against you. We love the work you do for us. We appreciate the time you spend on, the effort you put into it. We don't want another kernel.

Another kernel may be a solution in the short term, for this one issue. But we know that in the long run we are way better off with a team of devs that works hand in hand. Don't think we are stupid.

A little impatient at times, maybe some of us a little ungrateful but the majority knows very well how much both of you devs do for us.

Something in Tytungs kernel is different. Again, I'm not talking about BT. The phone call spikes are gone with that kernel. There are too many reports about this working to not believe it. (And there is nothing wrong in reporting it. It's meant to help not to insult.)

I know you know that. I'm pretty sure you work on finding out why. But we can't see the hours you put into doing that.

We'll eventually see you worked on it, when the problems gone.

Why wait for that moment to receive some gratitude and in the meantime put up with annoying complaints, when you can get thanks and maybe even some unsuspected help from your users all the time, by letting us take part in your work? Just some interaction with the users will do.

I'm not trying to tell you what to do. I'm trying to help you. I can see how much this situation is annyoing you.