How to pass bitmap from one activity to another

Question

i have bitmap in ActivityA i want to pass the bitmap from here to ActivityB, i googled for this. when i use this

Intent intent = new Intent(this, NewActivity.class);
intent.putExtra("BitmapImage", bitmap);

for getting

Bitmap bitmap = (Bitmap) intent.getParcelableExtra("BitmapImage");

i am getting this error !!! FAILED BINDER TRANSACTION !!! . how can i solve this problem.

what do you mean with "sometime works, but not all the times"? which effects do you see on screen (or in logcat if you get errors)? — STT LCU, Nov 24 '11 at 09:58
check my answer edited answer you can also use Application class. — Lalit Poptani, Nov 24 '11 at 10:17
This will help http://stackoverflow.com/questions/13577664/pass-a-bitmap-image-from-one-activity-to-another — Manish, Apr 26 '14 at 19:08

score 13 · Answer 1 · answered Nov 24 '11 at 10:47

Your code is correct for putting bitmaps into the extras and works fine for me with small images. But it seems that there is a limit for the size of the Parcelable extra. See http://groups.google.com/group/android-developers/browse_thread/thread/7322a84adcfee567?pli=1.

You might want to store the image first and only hand over the URI to the store location.

Edit: Using a public static field for the bitmap as suggested by udaykiran violates so many OO principles I don't even know where to start.

THANK YOU FOR THAT EDIT. I've downvoted the two answers that suggested it and left harsh comments, which I never do, because it's simply **terribad**. I wish I could upvote this a few more times. — salezica, Jul 07 '12 at 01:45

Lalit Poptani · Answer 2 · 2012-07-07T04:39:35.757

3

I tried and its working as below using intent.putExtra("name", bitmap)

While passing with intent,

Intent intent = new Intent(Current.this, Next.class);
intent.putExtra("bmp", bitmap);
startActivity(intent);

While fetching,

Bitmap bitmap = getIntent().getParcelableExtra("bmp");

OR

Other option is to use Application class,

You can also use a class that extends Application and have a setter getter for Bitmap and call it from every Acitivity.

((myApplication_class_name)getApplication()).setBitmap(bmp);

and fetch the Bitmap using,

((myApplication_class_name)getApplication()).getBitmap();

edited Jul 07 '12 at 04:39

answered Nov 24 '11 at 09:59

Lalit Poptani

i created like as u said but not getting in ActivityB – NagarjunaReddy Nov 24 '11 at 10:17
i decleared in ActivityA private static Bitmap b; try to get in this class Bitmap a = ImageAfterCrop.b; – NagarjunaReddy Nov 24 '11 at 10:22
you have to declare as public static not private static. – Lalit Poptani Nov 24 '11 at 10:23
can i decler this in my ActivityB public static Bitmap b – NagarjunaReddy Nov 24 '11 at 10:26
Sorry but storing Bitmaps in memory statically is just poor coding. There is a good chance you may be causing memory leaks. Store the image in some temp cache and pass the URI instead. – Reno Nov 24 '11 at 13:42
2

This is **awful** design, not a solution but a workaround, and the OP obviously did not have the knowledge to tell. I rarely downvote, but come on... – salezica Jul 07 '12 at 01:45

score 1 · Answer 3 · edited May 23 '17 at 12:00

1

I dont think that is the right method... you can use this link for the feature to be implemented. i too have used something like this itself.

edited May 23 '17 at 12:00

Community

answered Nov 24 '11 at 10:06

medampudi

score -5 · Answer 4 · answered Nov 24 '11 at 10:03

-5

You can simply name you Bitmap as static first.

then create a method like

public static Bitmap getBitmap(){
return bitmap;
}

then you can simply call from other activities,

bitmapwantedclass.getBitmap();

Hope it helps

answered Nov 24 '11 at 10:03

Uday

i done as u said but getting error in the wanted class The method getBitmapCrop() is undefined for the type ImageAfterCrop – NagarjunaReddy Nov 24 '11 at 10:14
You have to call like this, suppose your bitmap is in class A and getBitmap is in A , you want that bitmap in class B, so you have to call A.getBitmap() in class B. – Uday Nov 24 '11 at 10:27
17

This is **awful** design, not a solution but a workaround, and the OP obviously did not have the knowledge to tell. I rarely downvote, but come on... – salezica Jul 07 '12 at 01:43
Why is he getting down voted? Sure it's not good design. But the standard way to write to disk then extract is extremely slow for high resolution photos even testing on new phones like the Nexus II. – Math is Hard Oct 26 '14 at 00:53

4 Answers4