Hi Jake Assuming you are talking about Android Home Screen Widgets, I had the same issue which I blogged here: http://blog.zedray.com/2010/05/01/tracking-a-android-home-screen-widget/
I still haven't gotten a response from Flurry, so I suggest you consider the Google Analytics API. While this offers fewer features relevant for application developers, it does provide a dispatch() method which allows you to manually workaround the widget life cycle issue. Let me know how this works for you. Regards Mark On Jul 7, 10:49 pm, Jake Colman <[email protected]> wrote: > I am familiar with using Flurry with Activities and calling > FlurryAgent.onStartSession() in the activity's onStart() method and > calling FlurryAgent.onEndSession in the activity's onStop() method. > What would be the best way to do the same thing if I want to use Flurry > with my appwidget? Should I use the onEnabled()/onDisabled() methods or > should I use onUpdate() since the user may never delete my appwidget and > I won't know he's still using it? Or maybe onUpdate() and onDisabled() > but then I won't be matching my start/end sessions. If my appwidget has > a configuration activity or some other displayed activity I can > obviously use flurry there. But how about in the appwidget itself? > > -- > Jake Colman -- Android Tinkerer -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
