Native interface not work after AlarmManager/onReceive in Android 6.0

[ahs...@gmail.com]

Dear Sir,

On Android 6.0 when I wanna do AlarmManager and onReceive, it is quickly found out that of the Doze mode issue, the "setRepeating" is not work but using "setExactAndAllowWhileIdle"  instead ( or may use "setInexactRepeating") so that the receiving is successful. Afterwards when i call the native code function, the native code function is not work  anymore and the application will be suspended.

e.g.

After calling

public void setScheduler(Context context) {
//.................

        am.setExactAndAllowWhileIdle(AlarmManager.RTC_WAKEUP, cal.getTimeInMillis(), pi);

//.................

}

Then

public void onReceive(Context context, Intent intent) {
//...............        

                        Intent mainUIIntent = new Intent(context, MainUIStub.class);
                        mainUIIntent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
                        mainUIIntent.putExtra(LAUNCH_BY_SCHEDULER, true);
                        context.startActivity(mainUIIntent);
//.................

}

Then in MainUI

public void start() {
       //.................
            MobileNative mobileNative = (MobileNative) NativeLookup.create(MobileNative.class);
            if (mobileNative.isLaunchByScheduler()) {
                Form gui = stateMachine.showForm("FormMain", null);
                gui.getMenuBar().removeAll();
            }
      //.....................
}

When i call the native function "mobileNative.isLaunchByScheduler()" which is used to just return true, i can see it can go into the native function but cannot return and the application is suspend here.

Would you have any suggestion and what is the codename one response for the android 6.0 change for Doze mode issue?

Thanks and Regards,
Ronald

[ahs...@gmail.com]

any ideas? Many thanks!

[Shai Almog]

You shouldn't use your own activity or implement/extend additional classes in the native interface itself. We already have a portable way for background notifications so it's unclear to me what you are trying to achieve with native interfaces here?

[ahs...@gmail.com]

As the code presented, we would like to set a schedule at which time to start the application. Once the application start, it checks something from native function e.g. permission, get intent value. However, after the alarm manager trigger app start, all the native function call is no return success and app suspend. I have tried the app which was running smooth if i commented out all the native function call.

[ahs...@gmail.com]

Any updates? Thanks!

[Shai Almog]

Did you set the API level to a newer API level to work with this?
Maybe Chen has an idea here.

[ahs...@gmail.com]

Already using android api 23. Please help to check up the problem, many thanks!

[zeus...@yahoo.com.hk]

Any news? Thanks!

[Shai Almog]

I assigned this to Chen but he's under a bit of a heavy load with a few enterprise customers and hasn't been as responsive lately. I pinged him again.

[mispro...@gmail.com]

I see. Would you have another assignment if he is quite busy? Thanks and Regards!

[Chen Fishbein]

Are you seeing an exception in the android ddms log? can you open an issue with a test case? and I'll have a look

[mispro...@gmail.com]

 Hi, thank you for your response. I can't see any error log , it just stop once the native interface call after schedule kick start. What test case exactly do you want? Thanks and Regards!

[Shai Almog]

Create a hello world application and add to it code that reproduces the problem so we can reproduce it on our builds. Submit it based on the guidelines here: https://www.codenameone.com/blog/issue-submission-guideline.html

[jsa4...@gmail.com]

Is there a way to make native code consume less battery?

WhileIdle runs even while in low-power standby mode.

[Shai Almog]

I suggest opening a separate question for this as it is unrelated.