Hi.
I've done some experiments and think there are three problems:
1) Image file size versus image quality - a JPG with lots of detail will be a large image file and may fail to load.
2) Image dimensions may cause errors - very large images may fail to load.
3) The WebView seems to re-render images that are large in dimensions and/or large in filesize - this you have already discovered.
So even if you load a high quality JPG it will not be displayed in it's original quality.
Your image
big.jpg is 4975 x 600 pixels and ~152KBs in size.
My image editor tells me that the JPG image quality is 78%.
The majority of that image is plain white so even though the image dimensions are large it compresses well.
Take a look at this panorama i've been using for tests:
http://code.martinpearman.co.uk/deleteme/webview_canvas/cley_windmill.png
It's 4096 x 392 pixels and, in PNG format, is ~2.5MBs in size.
If i convert it to a JPG with 78% image quality i get a filesize of ~250KBs.
This JPG loads with no problems in a WebView buts looks awful in the emulator - the JPG compression has removed far too much detail (
or so it seems).
The same image on my Advent Vega (10" tablet) looks much better - acceptable quality.
Increasing the JPG image quality seems to have no effect using the emulator - even with 90% image quality (the image is ~398KBs) the image looks awful.
The same seems to apply to my Vega - the 90% image quality looks the same as the 78% image quality(acceptable).
So it looks to me as though a WebView will re-render an image based on the device's available resources.
BUT
no matter how much you increase image quality and no matter how much memory the device has available, the WebView will likely re-render the image.
Try running the attached code on both an emulator and a real device and compare the image quality.
The image in the code is saved with 78% image quality btw.
This is my emulator:
And this is my Vega:
Martin.