I had the same problem when loading as ARGB_565. Use inDither to get rid of very obvious stair-stepping. I would say I could spot a 16-bit image, especially with a lot of reds, on a less red screen (Xoom and Acer Iconia Tab A500) while the Galaxy Tab 7" is a whole splotch of red. However with inDither on gets a bit hard to tell!
On Jun 9, 4:50 am, webmonkey <[email protected]> wrote: > That works but I don't consider 16-bit to be "full-resolution", color > fidelity is just as important. > > On Jun 8, 10:25 pm, Streets Of Boston <[email protected]> wrote: > > > > > > > > > I guess it's playing nice to other background apps. Even a foreground app > > can't gobble up all the memory and starve the background apps. > > > I figured out a way to edit 9MPixel images 16-bit (i.e. 18MByte of data). It > > makes you program quite carefully when using the left over 6Mbyte of memory, > > but it's possible. On tablets, i think that the limit has been raised to a > > 48MByte heap. > > > Since the 1st gen android phones never had cameras with more than 5MPixel > > and 2nd gen android phones never had cameras with more than 8MPixel, it > > worked out for my app. > > > But if images are side-loaded (e.g. from a sd-card or downloaded from the > > web), which could be larger than 5 or 9 MPixel, then my app would fail to > > handle these. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
