Has anyone had any luck using Flurry with a home screen widget? What I want to do is tap into the "onEnabled" and "onDisabled" life- cycle methods, so I know how long at least one of the widgets has been installed on the home screen. The problem here is that the widget does not maintain the same context between these two calls, and (if well designed) shouldn't spend much time being in memory at all.
My widget is triggered repeatedly by the AlarmManager and does the UI within the permitted time span of the BroadcastReceiver. This is extremely efficient from a saving battery perspective(AlarmManager can be configured not to wake up the device), but may not be giving Flurry enough scope to report back usage data over the network. I have no idea how Flurry have implemented this functionality? Hence I am seeing incorrect session length values in my Flurry reports, i.e. Flurry is reporting 3-10 seconds (probably the time it takes to initialise my widget) and not the time the widget spends being shown on the home screen (in this example several days). Unfortunately Flurry have locked down their own forums, and are not returning my support emails. :-( As Flurry reports are delayed, this is very difficult to debug. Does anyone know if this kind of tracking is this possible? Would it help if I spun up a service or cached the context (i.e. leak some memory)? Could anyone suggest another usage tracking tool that supports Android Home screen widgets? Regards Mark I'm blogging this: http://blog.zedray.com/2010/04/24/using-flurry-with-a-android-home-screen-widget/ -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
