When android application (JNI+Java) goes to background, then based on Elixir monitor it takes 40-80% CPU without any visible reason. Logcat has no indication of any real activity, DDMS method profiler does not find any method calls.
In fact, after some minutes OS (ISC) at least sometimes seems to fix it automatically: restarts application process, and then it is as expected – taking 0% of CPU and some memory. When I start app again, and press home to take it to background, same CPU hogging happens.
Any ideas what could be investigated?
So my conclusion is: 1. if the method calls are not shown in Profiler, then very probably it means that CPU is wasted in NDK side, 2. GDB-based profiling should be used there, probably something like that