Crash in Android 4.0 While Re-Open App

[Rubin__Andy]

Hi,

The sample conference Android 4.0 application working fine but after disconnection from the conference and i minimise the application when i re-open  from recent tasks it will crashes. Can someone please explain why anyone would still use Android 4.0. Thank you. 

[He_Z_Intel]

Hi Rubin, sorry for your bad experience. 

Could you please provide more information, such as error log and reproduce procedure?

And please kindly keep in mind, our demo app might not be fully consider all situations and corner cases, more needs to implemented by app developers.

[Sharma__Mukesh]

P2P Android application is also crashing in on Reopening

because of the following lines

ContextInitialization.create()
                     .setApplicationContext(this)
                     .setCodecHardwareAccelerationEnabled(true)
                     .setVideoHardwareAccelerationOptions(
                             rootEglBase.getEglBaseContext(),
                             rootEglBase.getEglBaseContext())
                     .initialize();

how to get rid of this crashing error

[He_Z_Intel]

please don't initialize multiple times

[tony1]

How to prevent multiple initialization?

[tony1]

Hank Zhang (Intel) wrote:

please don't initialize multiple times

How to prevent multiple initialization?

I'm trying to initialize in Application, so you can't see the image when you go to video. Cannot render video stream, cannot display image.

How to solve this problem?

[He_Z_Intel]

Probably to add a flag to identify if the activity has been initialized.

[Paul_S_2]

Hi,

we're having the same issue. But in our case we're initializing the conferencing workflow in a second activity. When the conference is ended, the activity is destroyed. When trying to join a new conference the singleton ContextInitialization is already initialized and won't accept another context. This is quite an issue right now. Initializing in the Base-Activity is not an option.

Any ideas? 

[He_Z_Intel]

Sorry Paul, i am afraid that our current code structure does not allow actions such as change context after initialization.

Paul S. wrote:

Hi,

we're having the same issue. But in our case we're initializing the conferencing workflow in a second activity. When the conference is ended, the activity is destroyed. When trying to join a new conference the singleton ContextInitialization is already initialized and won't accept another context. This is quite an issue right now. Initializing in the Base-Activity is not an option.

Any ideas? 

[Paul_S_2]

Hello Hank,

do you have any Tipps of a workaround or are there plans to change the behavoir in future releases?

Thank you a lot in advance!