I've confirmed it happens in 3.2 as well.
Any advice for finding out if a bitmap is corrupt instead of silently
failing and wasting a user's time?
Nathan
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Nathan,
Is it possible to you to get a checksum of the image before the file
transfer?
So you can calc the checksum again after the file transfer and compare to
see if the file is corrupted.
Regards,
Guilherme
On 31 May 2012 13:22, Nathan nathan.d.mel...@gmail.com wrote:
I've confirmed it
On some 2.3.x version it was worse: a corrupted image could make native
decoding functiond block forever
--
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
On May 31, 11:37 am, Guilherme Utrabo utr...@gmail.com wrote:
Nathan,
Is it possible to you to get a checksum of the image before the file
transfer?
No, I don't control the server(s). So unless they already send this in
the http headers. . .
But I did make more progress on the prevention
On May 31, 4:19 pm, b0b pujos.mich...@gmail.com wrote:
On some 2.3.x version it was worse: a corrupted image could make native
decoding functiond block forever
Well, that could definitely be happening to some of my customers, and
could explain some freezes that I have never explained.
Nathan
5 matches
Mail list logo
