Android Agenda Widget bug...

[Syphon Filter]

Hi,

I wasn't sure where to post this but the issue I am experiencing is on the Nexus S and I couldn't find mention of the problem elsewhere, so this seemed like a logical place to start.

I have Agenda Widget and it seems to work for the most except for the following bug:

If you click an event/date the event/calendar opens. If you now press "Back" the event/calendar view closes.

If you repeat the above process but instead of pressing Back you press Home, the next time you press an event/date the calendar takes a long time to open. The effect is cumulative the more times you use the Home button to close the calendar (after opening it via Agenda Widget).

Has anyone else experienced this? Is there a fix?

TIA,

Syphon.

 

[roflharrison]

This sounds like a problem with the calendar application rather than Agenda Widget (I'm the dev of Agenda Widget, Hi ). When you press the home button in any application it pauses the current activity, when you press the back button it stops the current activity.

This problem sounds like the actual calendar application isn't managing the pause/restore process properly and is trying to re-load the entire activity rather than restoring it.

The fact that it is a Google application suggests that the above scenario is unlikely and maybe Google have changed their code in Android 2.3 which I may have to account for in AAW. If you can email me a log of the problem you outlined I will analyse it and look for the cause, roflharrison at gmail.

 

[Syphon Filter]

wow!

Thanks for taking the time to reply. I suspect you are correct in your analysis of the situation.

Clearly, pressing a date/event from the widget simply invokes the built-in calendar app and the subsequent back/home button presses (and the reaction to these inputs) are simply OS level interactions.

I don't know if this will help further but I noticed that pressing an event followed by the home key essentially stacks up events/calendar states (that's not the right word but best way I can think to describe it).

For example:

Press: Event 1 -> Event 1 is shown
Press: Home -> Returned to home.
Press: Event 2 -> Lag -> Event 2 is shown
Press: Home -> Returned to home.
Press: Event 3 -> Lag -> Event 3 is shown.
Press: Home -> Returned to home.
.
.
.
Press: Even n -> Lag -> Event n is shown
Press: Home -> Returned to home.

If you now press event n+1, event n+1 will be shown. If you now start pressing the "back" button, the calendar will page through every event that was previously selected...the calendar has remembered every previous state that it was invoked into (as long as the back button was not pressed at any stage). If the back button is used the calendar is returned to a null/default state and the next time it is invoked there is no issue.

Regarding the log, where would I find that? Also, if (as we suspect) this is an OS level issue, would any record of the problem even be in the log?

 

[roflharrison]

You can make a log by downloading alogcat from the market and opening it after you have performed the actions which are causing the problem. You can then email from alogcat and it will send the recent activity on the phone.

This behavior is strange (and as far as I know specific to Gingerbread), I am going to get my friend who has a G-bread ROM to test and see if he gets similar results...

 

[Syphon Filter]

Ok cool.

I've just emailed a log over to you.