I am facing a strange issue with running apk on galaxy tab 3.
The apk did run on older devices such as Galaxy s3 note 2,
I see the splash screen for longer seconds than a black screen and splash again … but app doesn’t run.
I did debug (cmd > adb logcat -c)
and I found an error “java.lang.IllegalArgumentException: Requested window android.os.BinderProxy”
I did search and couldn’t do anything about it.
changed Android min API Level from 2.3 to 4.2 , still same.
Aslo device has ARMv7 processor (since ARMv6) is not supported.
Its not also memory issues, and what might it be???
Has anyone faced such as issue??
Just found an interesting thread ((Android) After resume causing window death #1126) which throws same error but it was for MonoGame. But since MonoGame uses the Mono backend itself this looks like a very similar issue to what Unity might be facing. The solution states that:
This was an infinite loop on the
texture reloading that I was doing
when the android activity resumed from
the lock screen or prior-apps screen.
Even though this is not directly related to Unity but check out: App Crashes on Android 4.0, but not 2.3 — Strange Exception
Also based on all these and my other research on this issue I can narrow down this problem to something related to rendering. Some people have even reported they being benefited from disabling dynamic batching.
I’ll keep you posted if I come across any more information regarding this issue. In the meantime you can use GDB to find out what is actually happening inside the app at the moment of it crashing. This will provide a clearer insight of the issue. You can also post that GDB log here for review.