We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2014-02-07 18:41:37 +0200 |
I experienced for the first time today a calendar hang that I tried to reproduce (just succeeded in reproducing it twice). Let me describe the steps performed under 1.0.3.8: 1) calendar alerts me of an event while the phone is locked and shows me two pulley menus 2) first pull the bottom pulley menu and highlight the only menu entry (dismiss), then I don't confirm to dismiss closing the pulley menu 3) I pull the top pulley menu and select show event 4) subsequently unlock the phone and enter the calendar from the launcher area 5) now, whatever I try to do in the calendar, it is frozen and the system asks me to wait or close the app Since I don't succeed in reproducing the hang every time (but 3 times seems to be significant), I don't know whether the app occasionally conflicts with the system of apps (just have the alarm clock programmed, not even open) or it's a real bug of the app. Anyway, it is my experience and it seems to me I didn't find other messages here reporting that. Hope I checked well this time ;)
2 | No.2 Revision |
I experienced for the first time today a calendar hang that I tried to reproduce (just succeeded in reproducing it twice). reproduce: always successful even after rebooting the phone. Let me describe the steps performed under 1.0.3.8:
1) calendar alerts me of an event while the phone is locked and shows me two pulley menus
2) first pull the bottom pulley menu and highlight the only menu entry (dismiss), then I don't confirm to dismiss closing the pulley menu
3) I pull the top pulley menu and select show event
4) subsequently unlock the phone and enter the calendar from the launcher area
5) now, whatever I try to do in the calendar, it is frozen and the system asks me to wait or close the app
Since I don't succeed in reproducing the hang every time (but 3 times seems to be significant), I don't know whether the app occasionally conflicts with the system of apps (just have the alarm clock programmed, not even open) or it's a real bug of the app. Anyway, it is my experience and it seems to me I didn't find other messages here reporting that. Hope I checked well this time ;)