IssueTracker

Upgrade was never offered. I was offered directly Android 16. I can't
install Android 16 as I want to leave beta.

<buganizer-system@google.com> schrieb am Do., 27. Feb. 2025, 08:55:

Just want to add, same situation as yours, only it's been happening since December.
After upgrading to stable the issue persists.

It's not just the Gallery app. It's also the Browser. DisplayMate's article is pretty
silly in that it blames the OLED display for a lot of it (which isn't at fault), and
says the OS uses low bitdepth color (which, based on my testing, it does not).

I have the same issue viewing 10 megapixel pictures

i have the same problem

Same issue. Using a third party gallery app until this is fixed. Shame really as
everything else about the default app is good.

Same issue here, only have my N1 a week! Happening with high res images.

As I noted in the android-developers group:

http://groups.google.com/group/android-
developers/browse_thread/thread/c24466e69480dc30/

"It's an image handling "feature" (read: bug) of Android - images over
a certain size are compressed before being displayed by the browser.
So any zoom operations are done on the already highly compressed
image, resulting in unreadable text, artifacts, etc.
In my case I chopped up the image into smaller pieces and no
compression gets applied, so zooming works fine."

Presumably because apps are limited to 24 MB of memory. The piste map in the first
comment is around 8 MB uncompressed, so it wouldn't take many images of that size to
exhaust all the memory.

The solution is a smarter image library that allows decoding only part of the image
at full resolution when you zoom in.

I am facing the same issue with high resolution images. Is this going to be fix in
froyo? If not,then please resolve this issue in froyo if possible. Its really very
disappointing to see blurry images in gallery.

Running froyo on my nexus one and this is still
very much an issue,  has anyone found a good
work around for this?
I've also noticed that this disgusting image
compression only occurs on cellular data
connections,  connect over WiFi and this horrible
compression doesn't occur.
this makes reading web comics on my nexus
impossible and really needs a way to be turned
off....

hi, I've tested it on my htc desire and I
haven't noticed any change connecting
over wifi...have done many tests on
different browsers.

This may be a new change to the browser with
froyo.   Try clearing all caches before testing on
WiFi.
On WiFi
http://lh6.ggpht.com/_76WtIVC93XY/S_jOxVscgZI/
AAAAAAAAAHg/OXFbsdkXzh8/s400/
snap20100523_024143.png

On 3g
http://lh3.ggpht.com/_76WtIVC93XY/S_jO-uXE4EI/
AAAAAAAAAHo/5IXoUjoaX5Y/s400/
snap20100523_024219.png

If you get different results on cellular data compared to WiFi, your cellular carrier
is re-compressing images and possibly other content that travel through its network,
to reduce traffic and bandwidth usage. Most of the carriers I've used in the UK and
NZ do this.

That might be the issue for someone, however try looking at this page:
http://www.xtremesystems.org/forums/showpost.php?p=4357206&postcount=898
no matter which network you use it will always be blurry on the phone. Smaller
images (like 100KB) aren't affected

I can't see any difference between the display of that page in the Froyo browser and
the one in Firefox on my laptop when zoomed to the same size.  Both are slightly
blurry but perfectly readable.

It is true that Froyo did not fix the Gallery application to use the full resolution
of the photo.  Comparing the results in Gallery with B&B Gallery shows a clear difference

I have a HTC Desire on Telstra in Australia running firmware 2.1-update1.
I have this same issue - large images, when zoomed, are pixelated when displayed in
the browser or photo gallery.

This effectively stops me from visiting image websites; reddit, digg, deviantart,
LOLcats, unmotivational posters, infographics... what else is the internet good for?

Very verry annoying problem. It occurs for me on WiFi or 3g, it doesn't matter. Please fix.

It is probably related to the 24 MB memory limit for applications connected with lazy programming, however anybody with froyo can test and report if -using wifi- you get the same problem ? (using 3G, the compression could come from the network if your operator does it).

I've updated my nexus one to froyo and can confirm that the problem has been fixed.

If I check the same web sites that I listed in my original bug report, they are now displayed clearly.

I can report the original image (ski trail) renders fine now on Froyo.

But the images reported by diazivan still show the same issue. So there's still a limit being hit, but perhaps it has increased.

Nice, thank you. It's a bit weird though, as the first image is almost double the size in kb of the second. Perhaps it has to do more with canvas size allocation when rendering, and depends only on the geometrical size. I'm happy enough that they did something, I wouldn't have counted on it.

well, I could have sworn that even saving one of those images and viewing them afterwards would produce the same blurring, probably because of the same memory issue when rendering, however I've just tried with both images reported above and with this

Http://xtremesystems.org/forums/showpost.php?p=4357206&postcount=898

And the result is that it shows perfectly inside HTC gallery. Funny that I think I previously tried this and didn't work, perhaps I was using Android gallery or maybe a different eclair Rom...

Or perhaps I'm mistaken

Still having that issue on Nexus One 2.1update1 and also 2.2FRF50

Also see the discussion at:
http://groups.google.com/group/android-developers/browse_frm/thread/6578aa76a6bc4e8b

I experienced the same problem; in my case I don't load the the
image remotely. I load the image locally from the sd card. The
original image is very clear and uncompressed. I tried different
formats as well (png, jpg).
The only solution I found was to divide the large image into multiple
tiles and put them back together via html, then load the html file
locally. That's the only way the images don't get blurry when zooming
in.

I would probably stand the issue a bit better if I could know the reason for 24mb Limit.
Old winmo didn't have it if I remember correctly.

Also how do games manage to use big graphic bitmaps ?

andycted: See this thread: http://groups.google.com/group/android-ndk/browse_thread/thread/95c9f0cecceb112a

thanks a lot that makes it a lot more clear. .
I find the posts by developers on that thread to make a lot of sense and the response of the android support to be really bad and not helping. Besides if that limit isn't a problem and you can avoid it easily, how come the _browser_ they developed has this problem !?

Anyway, thanks for pointing me to that thread

I don't see why they don't simply let the user be able to change the max heap space per app in his phone by himself (i.e. under developer settings). So minimum would be 16/24mb but they could change it to a higher value if they want (similar to what was mentioned in above linked discussion as 'game mode'). Just the same as it's possible with the emulator.

I also consider about cases (like our app) where the developers actually bundles the app with an Android device (like in our case, we rent out pre-configured devices with our app that we rent out; only one app running on that device.).
In case we would want to change the 'max heap per app', we'd need to root the phone only in order to being able to set the 'dalvik.vm.heapsize' value to something higher in the build.prop.

Very interesting, changing that parameter would help applications stay in memory, where they crash for hitting that limit ?

Totally agree with your comment, sometimes android shows that it's not a fine tuned product, as sure it still is

Yes, See http://groups.google.com/group/android-developers/browse_thread/thread/8bc8e36753538d0c

And on the emulator, you can add "-prop dalvik.vm.heapsize=32m" for example as start parameter.

YouYou might have just made my day. I'm going to try it as soon as I get home and put this thing into recovery and see if it solves the all too frequent crashes of launcher pro

Thanks !

I can confirm that an increase on that parameter improves stability on memory intense applications. Thanks !

I doubt that it will change anything in regards to this issue of blurry pictures though. right  now I'm on 3g and can't test it in wifi, but pictures are still blurry

[Comment deleted]

I can't speak for other applications but large format images in the browser are deliberately down sampled.

The relevant code is in external/webkit/WebCore/platforms/android/ImageSource.cpp (or there abouts).

Yup, strange though that every browser does this, probably they use the same
code, but for image galleries, the HTC one and a couple of others manage to
render them full quality, no matter what

browser

abouts).

I'm having poor image quality in the browser w/ my HTC EVO, on 2.2

I have the same problem on the Nexus S. If you zoom on any picture it goes blurry. It is very disappointing and unacceptable. I hoped it would be fixed in 2.3 but it is not! My old iPhone 3G displays the same images much sharper than new Nexus S :((

Running gingerbread on an Evo and all large photos get compressed by the browser. This is unacceptable.

Compression for wallpapers = frown on face.  :(

This happens in every single phone, nothing new :( Hope this gets fixed! Google, I expect you to be the 1st one as usual. Don't dissapoint!

I kinda am having the same problem. if you look at the image I attached all the app names are kinda blurred out and aren't clear. Please help as this ruins the look of whole android. Its a Samsung Galaxy Discover and this problem just started yesterday.
Thanks so much!