The memory used by the application is from 110 to 190 Mb.
Unless you set LargeHeap to true in your manifest, that's too much for most devices. And even LargeHeap is not the ultimate solution because this setting is ignored before Honeycomb and some devices (I have one in this case) won't allocate more than 128 MB to the large heap (especially if their total RAM is 256 Mb or less). So you should try to reduce your memory consumption under 128 MB if your application is not designed for a specific device.
I use
1 image for the splash screen : 1000x625 for tablets 10" and 800x500 for the tablets 7"
7 icons file png : 5 in 64x64, 1 in 40x40 and 1 in 32x32
1 image png : 256 x 256
There is a slideshow in the application : the default files are 1 file 1280x800 and 1 file 512x597. They are loaded one by one.
I think the main culprit is your slideshow. You probably do not remove the images from memory once they are seen, so the memory usage grows with each new image. I cannot give more details without knowing how you display and handle your images.
The biggest file is a background image 1760x2414 which is resized. I will try to resample it.
Resampling is not enough, you have to rescale it. You can use the LoadScaledBitmap function of my BetterImageView lib.
FYI, this image alone consumes 16 MB of RAM.
I don't know how to get the Java heap size.
You just have to know what the device is. The max VM heap size is publicly available in the specs. Otherwise, you can use my Cache lib or my StrictMode lib to know the max. available memory when you start your app.