[Meego-handset] Clarification on bug 7494
Shane Bryan
shane.bryan at linux.intel.com
Mon Oct 4 09:56:34 PDT 2010
CC'ing the meego-handset ML as this is of general interest to handset
dialer reference app...
On Mon, 4 Oct 2010 13:17:01 +0000
<ext-arun.1.ravindran at nokia.com> wrote:
> Hi Shane,
>
> While trying to reproduce this issue, i can see the following
> behavior.
>
> 1) No indication comes when Dialer is not running, but at the called
> end the call is ringing.
This is known behavior due to the same cause of BMC #7074 [1]
> 2) if dialer is running, there is a notification, once the call is
> disconnected, but this goes off immediately, i donno is this a
> correct functionality.
Not sure I understand what you mean by "goes off immediately"? Can you
please explain in more detail, with exact steps to reproduce?
> 3) If i have a number of calls made, and go to the call list, it is
> not possible to call the last number (number at the end if the list)
> because there is no way i can scroll to it. When the list is panned,
> it goes back to the original position. Is this a bug?
I don't see this in dialer. Are you referring to the list of missed
calls in the system-ui status menu pop-up or in the dialer's recent
call log?
I just tested dialing 8 #'s, then going to the recent call log in
dialer, and I can still touch the last entry to initiate a call.
Shane...
[1] http://bugs.meego.com/show_bug.cgi?id=7074
More information about the Meego-handset
mailing list