That said, you could probably get around this with a content provider.  But
please please please -- don't abuse widgets by consuming lots of resources
with them, this has a direct impact on the overall experience.

On Thu, Aug 25, 2011 at 10:40 AM, Dianne Hackborn <hack...@android.com>wrote:

> I am continually glad for this limitation.  Shoving over a MB of memory
> that the launcher needs to keep in its process for a widget is
> not desirable.  Sorry.
>
>
> On Thu, Aug 25, 2011 at 9:39 AM, Mark Murphy <mmur...@commonsware.com>wrote:
>
>> On Thu, Aug 25, 2011 at 11:11 AM, String <sterling.ud...@googlemail.com>
>> 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 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
>>
>
>
>
> --
> Dianne Hackborn
> Android framework engineer
> hack...@android.com
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.
>
>


-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
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

Reply via email to