Android Question Old Content chooser problem

[hookshy]

Hi,
I have read about all problems related to content chooser and did not found an answer for my device
Huawei Jelly Bean

- declared content chooser as process globals
- initialised in activity create
- created a service and started foreground before call cc.show

Problem is that even the service was started with start foreground the activity is killed and content chooser does not fire the results...
My activity starts always as first true when it should have resumed after pick image from gallery ...
CC returns results only if I hury up and choose an image in the first 5 seconds ) ...(my cc works speaking of code)


If the device is low on resource does the OS kills the activity even if the process itself have services that runs foreground ?
The service itself runs but the activity is killed ...
Thank you for advice.
Will test on other devices too...


Thank you

 

[Erel]

Are you sure that you are not calling ExitApplication somewhere in your code?

 

[hookshy]

cation somewhere in your code?

no ... and I do test content chooser
what coud it be ... service start forground is forceing the service to stay alive not the activity ...it that right?
the process itself it should live as I have put a service in foreground ...

 

[Erel]

There is a setting in the developers options that could cause it. Make sure that there is no limit to the number of background processes.

Can you post the app logs while you use content chooser?

 

[hookshy]

new tests today
- No need to post logs ...by using the service trick it seems to be working fine now ... I have tried to load the phone memory and it does the work
I do not understand why the notification is not cancelling when calling service.stopforeground(1) ? the id is corect
I had to use noti.cancel(1) as well .

Thanks