Bug 6666 - (int-149744) Phone app kills itself after pressing message button while incoming call
(int-149744)
: Phone app kills itself after pressing message button while incoming call
Status: RESOLVED INVALID
Product: Chat & Call & SMS
Call Application UI
: 5.0/(1.2009.42-11)
: N900 Maemo
: Medium normal (vote)
: ---
Assigned To: rtcomm@maemo.org
: call-ui-bugs
:
:
:
:
  Show dependency tree
 
Reported: 2009-12-07 16:56 UTC by Esa
Modified: 2009-12-08 01:12 UTC (History)
4 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Esa (reporter) 2009-12-07 16:56:28 UTC
SOFTWARE VERSION:
(Settings > General > About product)
1.2009.42-11

EXACT STEPS LEADING TO PROBLEM: 

1. Phone app isn't running. 
2. Incoming call, phone app is opened automatically.
3. Press message-button in the phone app while incoming call.
4. SMS Message app is opened.
4. Close Conversation SMS Message app.

EXPECTED OUTCOME:
Conversation SMS Message app is closed and the phone app is running and
selectable.

ACTUAL OUTCOME:
Conversation SMS Message app is closed and the phone app doesn't exist. The
incoming call is still on and if you open the phone app manually the call can
be answered.

REPRODUCIBILITY:
always

OTHER COMMENTS:
The phone app's display orientation setting is Portrait and Launch by turning
is disabled.
Comment 1 Lassi Syrjälä nokia 2009-12-08 00:13:24 UTC
Thanks for the report.

The app does not kill itself - if you had it open, it remains open - but it
does hide the incoming call dialog to allow you to type in the message. To
attend the call, you need to open Phone again or switch back to it if already
open.

The reply with SMS feature is a soft way to reject, and the design is based on
the assumption that most of the time you do not want to return to the dialog.
Also, it's not possible to minimize a dialog unlike applications can be.

If you accidentally hit the wrong button, it can be a bit cumbersome to return
to the dialog. But it works as designed within the framework rules, so I am
marking this as invalid.
Comment 2 tom hensel 2009-12-08 01:12:33 UTC
evil bug ;)