Notices

Sometimes I accidentally reject an incoming call, in cases when:
the interface jumped from portrait to landscape and back,
my fingers were typing on the virtual keyboard before the call came,
the display-screen was blank while touch-screen already accepted interaction,
or something similar.
Theoretically, I would suggest disabling the reject button for at least the first three seconds of the call. The interface might be still slightly annoying - but, at least, I wouldn't have to call back, or wait for the call to be repeated.
Do you know any simple and efficient way to do this? Which wouldn't decrease battery life?
Disabling the whole screen for the first three seconds of the call is acceptable, too. Though less comfortable, especially for the person on the other side of the call who will have to wait. At least, it will be better than seeing the call rejected for no reason.
Best wishes. Thanks in advance.

I'm experiencing this too. But it happened only recently, since a few weeks.
Couldn't make out when excatly this happens.
Very annoying...

You could argue there is an underlying reason for the lag.
You could find the cause of this instead of trying to modify closed rtcomm.
I would guess this happens after a period of uptime? A freshly booted device would have no issues in this case.

It's also a noticable issue with "recaller", if you use that.

The only "hack" I can think of, is to make rtcomm think the proximity switch is closed. This would keep the screen locked for "x" amount of time.

Quick reply...
My uptime is less than a day, and this problem happened during this stretch of time, yes. So, "long uptime" isn't causing the problem.
Yes, I use recaller. It would be interesting to investigate how it could possibly cause this lag. I will read its files, just in case.
The files created by the recaller are stored in a "hidden" directory (starting with a dot), so the tracker doesn't index them. Thus, the problem with device slow due to large number of files being indexed is eliminated, too.
Thank you.
Best wishes.

I'm facing this though I don't have recaller installed.

Edit: forgot to update earlier... ahem... I switched carrier at that time and a 3-time ring was the standard setting, which I didn't realize at first. So for me, it turned out to be that my usual behaviour of taking a call after ~2 rings sometimes was just a tad bit late.
Changed settings on carrier side and things are fine now.

happened this to me also today. was replying my friends message as suddenly he called me and i rejected the call as i was typing message and my finger touched reject button. can't CSSU developers replace reject/answers buttons with slide to answer thing ?

Here's some of the recaller issues threads
http://talk.maemo.org/showthread.php?t=43979
http://talk.maemo.org/showthread.php?t=59191
http://talk.maemo.org/showthread.php?t=80711

While the application is a good idea, there have been so many "issues" reported I have always avoided it.
Widgets generally do cause system lag.

It's not a tracker issue it's the running of the python script while the system is under a lot of load.

rtcomm-ui is a closed package.

The interaction might become inconsistent, if you are implementing gestures for each app separately.
Though, as an option, or an additional app, it could be done.
The problem is, to replace reject-answer buttons with something, you would have to reverse-engineer rtcom-call-ui. Or, you could overlay it somehow, like lfocus overlays camera-ui.
I would rather use camera key for answer-reject, but then, the incoming call will happen when I am photographing something...
[Edit]Recaller is a very useful widget. And it's the only widget I use.[/Edit]
Best wishes. Thank you.

i hate Nokia