Romain,
What is the bug number for this? Was it fixed in the 1.0 r2 SDK?
- Cheryl
On Nov 12, 7:25 am, blindfold seeingwithso...@gmail.com wrote:
Interesting. In case this Android bug/feature not only applies to
input streams, this might also explain why I no longer had memory
related
It wasn't fixed in 1.0r2. We cannot put fixes in the SDK if they are
not available on the phones. Also, the bug is internal, it's not on
the external tracker.
On Mon, Dec 15, 2008 at 11:30 PM, Cheryl Sedota cherylsed...@gmail.com wrote:
Romain,
What is the bug number for this? Was it fixed
Romain,
Can you please give details on the exact problem with the current 1.0
SDK? Should we avoid Drawables completely in favor of setting resource
id's or bitmap objects? Or is the problem specific to a use case like
loading remote images (via URL)? Based on the comment above that
It has nothing to do with Drawables, it's just a buffering issue with
loading large bitmaps over slow connections. Local images are NOT
problematic at all, and BitmapFactory.decodeResource() is certainly
not better than getResources().getDrawable() since the latter pretty
much uses the former :)
Interesting. In case this Android bug/feature not only applies to
input streams, this might also explain why I no longer had memory
related crashes on the G1 after recently switching to using
BitmapFactory.decodeResource(getResources() instead of getResources
().getDrawable() to retrieve
This is a known bug. Here is a workaround:
in = new BufferedInputStream(new
URL(getUrl(size)).openStream(),
IO_BUFFER_SIZE);
final ByteArrayOutputStream dataStream = new
ByteArrayOutputStream();
out = new
It did help! Thanks a lot!
Of course, I now create a bunch of unnecessary objects, but hope it'll
be fixed soon...
On Nov 11, 10:30 pm, Romain Guy [EMAIL PROTECTED] wrote:
This is a known bug. Here is a workaround:
in = new BufferedInputStream(new
7 matches
Mail list logo
