I wrote an app that loads an image of an A4 sized document into a bitmap.
Another bitmap then has its InitializeMutable method run with the height and width of the first bitmap.
On a Huawei phone (model CUN-L01) which has android 5 there is no problem.
So it surprised me when on a Samsung Galaxy tab A (Model SM-T550) running Android 7, it caused an outOfMemory error.
When I got the error I saw that it was because my bitmap's dimensions are large and switched to using
the LoadBitmapResize method instead as was recommended.
This works fine except the bitmap is a little bit blurry when it's resized back to its original size afterwards.
I was wondering if this is happening just because my phone has more memory available or is it a difference between how android 5 and android 7 work?
The code I used I took more or less verbatim from Erel's signature capture project
Thanks for any comments
Another bitmap then has its InitializeMutable method run with the height and width of the first bitmap.
On a Huawei phone (model CUN-L01) which has android 5 there is no problem.
So it surprised me when on a Samsung Galaxy tab A (Model SM-T550) running Android 7, it caused an outOfMemory error.
When I got the error I saw that it was because my bitmap's dimensions are large and switched to using
the LoadBitmapResize method instead as was recommended.
This works fine except the bitmap is a little bit blurry when it's resized back to its original size afterwards.
I was wondering if this is happening just because my phone has more memory available or is it a difference between how android 5 and android 7 work?
B4X:
Dim Bm As Bitmap
Bm = LoadBitmap(Main.sProgFolderPath & "/unsigned",document_show.selectedImage)
Dim Bmz As Bitmap
Bmz.InitializeMutable(Bm.Width,Bm.Height)The code I used I took more or less verbatim from Erel's signature capture project
Thanks for any comments