The failed binder transaction issue basically happens whenever you send data "too fast" to an AppWidget, where "too fast" is loosely defined. You can definitely cause it by sending >1MB at once, but you can also get it by sending much smaller quantities at too fast a rate. Which is what it sounds like you're doing.
Your best solution is probably to create a content provider and have your widget access that directly for the images, which will avoid the RemoteViews (and thus the binder which is causing the problem). A Google search for *image content provider* should get you started. Having said all that, updating an AppWidget with an image every 15 seconds sounds like a recipe for battery drain. You might want to test that hypothesis, see how bad the power drain is before you go to the trouble of re-implementing the image delivery mechanism. You may need to rethink your concept at a deeper level instead. String -- 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
