Error on Galaxy S5 (klte) devices after splash screen updates

My latest update got some bad reviews, because people with a Galaxy S5 (klte) device have issues now. They report crashes since the update.
Every other device seems to be ok with the splash screens (app is only available on the Play Store)

to create the splash screens i used the new ionic cli tool. Worked wonderfully on my end. Is anyone else experiencing same issues?

It seems this occurs only on Android 5.0. Here is a backtrace:

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

Build fingerprint: 'samsung/kltexx/klte:5.0/LRX21T/G900FXXU1BNL9:user/release-keys’
Revision: '14’
ABI: 'arm’
pid: 9675, tid: 9690, name: GCDaemon >>> com.ionicframework.plankchallenge245184 <<<
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x86e40000
r0 76eb0000 r1 00000080 r2 00000001 r3 86e40000
r4 00010000 r5 00000010 r6 00000000 r7 00000001
r8 b3daf454 r9 afb437ac sl 76eb0080 fp 76eb0100
ip b258f674 sp b3daf388 lr b4c27d17 pc b4c27496 cpsr 800f0030

backtrace:
#00 pc 00125496 /system/lib/libart.so (void art::gc::accounting::SpaceBitmap<8u>::VisitMarkedRangeart::gc::collector::ScanObjectVisitor(unsigned int, unsigned int, art::gc::collector::ScanObjectVisitor const&) const+41)
\ #01 pc 00125d13 /system/lib/libart.so (art::gc::collector::MarkSweep::ScanGrayObjects(bool, unsigned char)+1026)
\ #02 pc 00125da3 /system/lib/libart.so (art::gc::collector::MarkSweep::RecursiveMarkDirtyObjects(bool, unsigned char)+6)
\ #03 pc 00126121 /system/lib/libart.so (art::gc::collector::MarkSweep::MarkingPhase()+112)
#04 pc 0012624f /system/lib/libart.so (art::gc::collector::MarkSweep::RunPhases()+254)
#05 pc 0011d717 /system/lib/libart.so (art::gc::collector::GarbageCollector::Run(art::gc::GcCause, bool)+234)
#06 pc 0013c0c1 /system/lib/libart.so (art::gc::Heap::CollectGarbageInternal(art::gc::collector::GcType, art::gc::GcCause, bool)+1380)
#07 pc 0013d4b5 /system/lib/libart.so (art::gc::Heap::ConcurrentGC(art::Thread*)+48)
#08 pc 000003db /system/framework/arm/boot.oat

Hmm, surprisingly, I got the app to crash on an old android 4.1 device.

Are you using admob is your app?

yes I do!
Using this cordova plugin.
It’s just one banner ad at the bottom of the page!
Are crashes common with admob (and ionic)?
After reverting the simple splash screen update, the galaxy s5 users reported that their app didn’t crash on start anymore.

Is it a problem to have the banner ad always at the bottom (generated in the run method of angular) and splash screens?

Hmm, so it may be a edge case where the two aren’t playing well with each other.
Have you had it crash for you?

Have you tried with crosswalk?

Hi All,

I am also facing the same issue . could you please share your workaround with me.

Advance Thanks
-Bikash