On Thu, Aug 25, 2011 at 11:11 AM, String <[email protected]> wrote: > The funny thing is, that doesn't actually help. The FAILED BINDER > TRANSACTION seems to occur whenever you send too much data through IPC > (where "too much" is on the order of 1MB), but it doesn't seem to matter if > that 1MB is in a single transaction or split into several. As it is, if I > have multiple appwidget instances, I need to wait a second between updates > to avoid this problem - even though each instance uses a different > RemoteViews object.
Now, that's interesting. They must batch those up or something. > I've been seeing this issue since at least Donut, and I could've sworn that > it was already in the bugtracker, but looking now I can't seem to find it. > Anybody think of a reason why I shouldn't create an issue for it? I doubt you're going to get tons o' love for a "allow more than 1MB in a binder transaction", though you can try. Have you tried creating a ContentProvider that returns your images via openFile() and then using setImageViewUri() in the RemoteViews to point to that ContentProvider? Clearly the Uri/ContentProvider system is designed to handle larger-than-1MB data sets, since it's used for MP3 and MP4 files. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _Android Programming Tutorials_ Version 3.9 Available! -- 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
