[Meego-handset] Clarification on bug 7494
Shane Bryan
shane.bryan at linux.intel.com
Tue Oct 5 09:31:24 PDT 2010
On Tue, 5 Oct 2010 05:41:27 +0000
<ext-arun.1.ravindran at nokia.com> wrote:
>
> Hi Shane,
>
> > 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?
>
> 1) Dial to meego phone.
> 2) Incoming call is shown in the dialer with options to accept and
> reject. 3) After few rings (heard at the MO side), disconnect the
> call from MO side. 4) There is a notification shown in meego (seems
> to be with some contact icon), and it goes off immediately, before
> even getting time to read it.
>
> Please see the attached video. (05102010 (1).mp4)
Ok, this appears to be two problems, neither of which I can control.
1) The timeout for the display of the MNotification event is controlled
by the MNotificationManager or MNotificationView, not by the sender
(dialer). I'm not aware of any way for me to control that
unfortunately.
You can test if this is the default behavior by using the
mnotificationtool utility (installed with the libmeegotouch-devel
package). Here is an example invocation to test with:
mnotificationtool -a add -i x-nokia.call -c 1 "Test Event" \
"Summary text" "Body text" icon-m-telephony-call-missed
2) The blank screen after the notification is most likely a compositor
issue, or, some loss of frames in the notification removal animation.
I've seen this lots on the i945 Gfx systems (netbooks) and it's a
compositor issue there. Not sure if it can be blammed on that on the
N900 though, since it's different Gfx device. I *do* see lots of
animation frame loss on the N900's and Aava's, but I'm not an expert on
performance so I won't even pretend to guess as to the cause.
>
> > 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.
>
> This is in the dialer's recent call list. Please have a look at the
> attached video. 05102010.mp4
Ok, I understand what you are describing now. I don't see this on my
dev system, but it's on a different sized system.
Can you open a bug on this one, specifying it is an N900 device, what
build (please be sure it is reproducible on one of the official builds
that can be found on http://repo.meego.com/MeeGo/builds/ ...).
Please attach the video, the file /etc/meegotouch/devices.conf, and the
output of the following command:
$ gconftool-2 -R /meegotouch/theme
Thanks for the reports,
Shane...
PS: you can usually find me (sabotage) on irc at #meego-handset on
freenode.
PPS: For the sake of those also subscribed to this list, please try to
avoid sending large (multi MB) files like these videos through email.
Find a place online to host them (wiki.meego.com might work, unless
they have a file size limit and type restrictions for uploads), or just
send them to me directly, just not to the list. If they result in a
bug being filed or updated, then we can attach them to the bug for all
to see.
More information about the Meego-handset
mailing list