Hi Vu:
You are right, it's a locker app. We have two kind of process, one is application name to configure some thing, another is ***:locker name.
We have two plan for make a locker. 1. We have overlay permission, we make a view add to Window Manager from service as a locker. 2. No permission, we make Activity as a locker.
In manifest, AdActivity is android:process=":locker".So there no process problem.
And, we found the issue is not belong to chrome. The reason is AdActivity not start chrome. You can see the log at attachment.
I use the command "adb logcat | grep "ActivityManager" to filter log. The first time click ad is work, you can see the process: -------->AdActivity----->com.google.android.apps.chrome.Main. But the second time: ----->AdActivity, it's end up with start AdActivity.
I think maybe it's because of overlay. But i found the issue still happen when i use activity as a locker.
So, do you know why AdActivity not start Chrome.
So thanks for your help and patience O(∩_∩)O~. I know my English grammar is very bed....