I love the way my apps look on iPhone/iPad. I tried to avoid Android altogether but one of my apps is quite popular and people kept asking for an android version so I did it last year. People liked it but said it was "quite buggy" and crashed often. This past month I converted the app from v 1.5 to 2.0. To be on the safe side I did not use any new plugins and not even a splash screen. The first two days I received emails about how much more stable it was and I thought the problem was solved. The same people have since emailed me back stating that unfortunately it does crash just as often as before. The reviews are awful because of it. The two main errors in the Developer Console are: 1. NullPointerException in BT_viewUtilities.updateBackgroundColorsForScreen() 2. OutOfMemoryError in BitmapFactory.nativeDecodeAsset() I have seen these mentioned in the discussion forum before and no one seems to have figured out a way to fix it. I'm just curious if this is happening to all BT android apps? I'm getting ready to just screw Android altogether and just stick with iOS. Josh

Did you try shrinking your image sizes? Are they localized or remote?

@Mutzy, Try following this thread: https://www.buzztouch.com/forum/thread.php?tid=8C8489F8D597BD93CC80EE1&fid=79A3D47D59E2A7B06AB0970&sortColumn=FT.id&sortUpDown=DESC&currentPage=1 Some progress is being made and David@Buzztouch is involved in it. Massively frustrating issue. Does it only happen to a few of us? Or are other devs just unaware of it, or don't care?

Thanks raveyd, subscribed.

@raveyd it happened to me on one app that had huge images, I shrank those and it has no erros since then. Maybe it was a coincidence, but that fixed my problem. Ah well.

Hi @coderx. I had a similar problem with buttons in a grid view being too large. Made them smaller and that fixed my issues. Other people are reporting slightly different problems but the same (or very similar) logcat reports. It's like there's an underlying issue related to various similar scenarios. Or something..

Hi @coderx, I have a similar story to @raveyd. I also had an Android stability problem and it was all down to image sizes in a button menu. The the ios version of my app had no problems, the Android app did. It turned out that one of my button images (yes, just one) was very very big and whilst the ios app could cope with dynamically shrinking it, the android version could not - it would launch, but subsequently crash when I was navigating. Bringing that one image down to a reasonable size seemed to do the trick, but now, to be sure, I now fix the final size of all my images to the dimensions I wanted them displayed and my android apps are stable.

Seems to be some common issues and solutions here, but as David says in the thread above, they shouldn't cause nullpointerexception errors, yet they seem to, which I suppose would point to some other underlying issue. Dunno, way over my head. *edit* @AlanMac, with regard to button sizes, have you checked on different devices? I was building buttons optimised for a large screen phone and they were perfect, but on a small screen phone - waaaaaayyyy too big, causing the errors. I've reached a middle ground but the buttons look faintly ridiculous on a small screen and just too small for a big screen. The issue is that both phones are classed as 'small devices' in the advanced settings. Almost need a range of options for various screen sizes as well as large and small devices.

Hi @raveyd, I use a zte blade phone, a google nexus tablet and I have about 10 AVD's in Eclipse of different sizes. On real hardware, the way a device reports its screen type, who knows what is what. It is a nightmare! Finding decent size compromises for Android button layouts takes longer than creating the app itself. I find vertical button layouts not bad. Horizontal layout would work better if it could be 'centralised' and I gave up on grid button layout as the number in the grid varied all over the place on different devices. The multi AVD route helps.