No idea - it the problem has only started manifesting itself since DST - then it's likely to be the cause.
But it's something that's easy to test. Ensure the devices clocks are current & accurate. On 17 March 2010 19:01, Jason Proctor <jason.android.li...@gmail.com> wrote: > thanks for the response. what "times" would i ensure are in sync? i thought > that phones these days managed their own times. > > also, i'm really confused about why this would affect only DNS requests > made by broadcast receivers. wouldn't a timing issue affect all DNS > requests? unless... the UI libraries do some fixups [fx: barf] > > i wonder whether this has anything to do with the Android kernel being 18 > months out of date (IIRC) and the DST change coming in only *last* year. > > baffled of SF! > > > > Check that times are sync'd - I've seen some issues before where >> out-of-sync clocks caused DNS errors. >> >> On 17 March 2010 02:06, Jason Proctor <<mailto: >> jason.android.li...@gmail.com>jason.android.li...@gmail.com> wrote: >> >> hey all, >> >> something weird just started happening. my app has a broadcast receiver >> which may access the network when invoked. the code has been solid for ages, >> but in the last few days it has started getting DNS errors on perfectly fine >> hosts. these are hosts which can be reached without problems in the main app >> or from other apps. >> >> interestingly i've seen another app get DNS errors too -- another app with >> a broadcast receiver. >> >> seems to affect all OS versions -- we have 1.5, 1.6, and 2.01 here. i >> don't have a Nexus to test 2.1, though. >> >> are there caveats to doing network inside broadcast receivers? i didn't >> think so, as ours worked fine until.... the time change [fx: twilight zone >> theme] >> >> thanks for any guidance with this one! >> -- >> jason.vp.engineering.particle >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to <mailto: >> android-developers@googlegroups.com>android-developers@googlegroups.com >> >> To unsubscribe from this group, send email to >> <mailto:android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> >> >android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> >> >> For more options, visit this group at >> <http://groups.google.com/group/android-developers?hl=en> >> http://groups.google.com/group/android-developers?hl=en >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to android-developers@googlegroups.com >> To unsubscribe from this group, send email to >> android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> >> For more options, visit this group at >> <http://groups.google.com/group/android-developers?hl=en> >> http://groups.google.com/group/android-developers?hl=en >> > > > -- > jason.vp.engineering.particle > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
