Quick dial on the "Last Caller" mini widget is now live on the Market, enjoy, Mark
On Jul 12, 10:43 pm, whitemice <[email protected]> wrote: > Hi Operand Zombie > Thanks for ruling out the CMDA API on your EVO. > Issue is with the original Droid AFAIK (I'm guessing specific > firmware), but I'll accept a LogCat trace from anyone who can > reproduce the update issue on their device. > > Auto-populate/quick dial feature will be coming, as soon as I figure > out how to make it work in the new 2:1 layout. > Thanks for the feedback. > Mark > > On Jul 11, 8:30 pm, Operand Zombie <[email protected]> wrote: > > > > > I'd also highly doubt that the network type is impacting your app. > > Just to confirm, I downloaded your app on my EVO - a phone on the > > Sprint (CDMA) network, and it seems to work just fine (it'd be nice if > > when I tap the small 2x1 widget the persons number would auto-populate > > like when I tap the phone on the larger widget). > > > So it would seem that the problem stems more from something the Droid > > is doing (the complaints are from Droid, and not Droid Incredible > > users, yes?), or perhaps some other app on the users phone.. > > > On Jul 11, 11:18 am, whitemice <[email protected]> wrote: > > > > I am based in Germany and publish the "Last Call Widget" on the > > > Android Market. I have been steady improving it over time, but one > > > group of users still complain about it not working on their devices. > > > > My widget listens for the "android.intent.action.PHONE_STATE" intent, > > > and then sets an alarm to update the last call UI in 20 seconds, then > > > 60 seconds, then 5 minutes, 1 hour, etc. This works reliably on all > > > my test devices, even with aggressive task killers (try it yourself). > > > Unfortunately I have a cluster of users with Motorola Droids on the > > > Verizon network who complain that the UI does not automatically > > > update. > > > > I believe Verizon is a CDMA network (we have GSM here in Europe), > > > though the Android API docs don't specify any implementation > > > differences. This could also be a driver issue on the Motorola Droid > > > (we have GSM Motorola Milestones in Europe). > > > > I am wondering if anyone reading is in a position to offer any ideas, > > > or test the widget on a Droid and/or CDMA network to see if they can > > > reproduce an issue (with logs)? > > > > Regards > > > Mark -- 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
