Android AdMob causes background cpu usage after adding share

I am working on an C++ app which I had banner ads working using sdkbox AdMob. After adding the share plugin to use twitter my app started using cpu in the background. Usage in the background is usually between 2% and 5% on a Samsung Tab3. If I comment out sdkbox::PluginAdMob::init(); in applicationDidFinishLaunching() of AppDelegate background usage goes back to zero. I used the sdkbox installer to import both plugins. I had to manually change Cocos2dxActivity.java after importing pluings.

Which version of the twitter plugin are you using? we’ll double check it

2.2 Here is the output of sdkbox info:
installed packages:
v2.2.0.15 admob
v2.2.0.15 share
v2.2.0.15 googleplayservices

I was using cocos2d-x v3 from github. I brought it up to v3.11 yesterday with the same result on both versions.

Thanks we’ll try to reproduce that

I made a new Hello World project and added the AdMob and share plugins with the same result. I added the Facebook plugin to see what impact that would have and it seems to have cured it. Tomorrow I’ll add Facebook to my actual project and see if it fixes it there also.

I installed the facebook plugin on a copy of my real project which didn’t fix it like it did on my hello world project. Note that the plugins were updated to v2.2.1.6

i run empty cocos 3.11 cpp andriod project and check cup usage
packagename is com.htl.test

then, i clone admob sample(https://github.com/sdkbox/sdkbox-sample-admob),
and go to cpp directory, run sdkobx import share to import twitter into cpp project
packagename is com.sdkbox.sample.admob.cpp

you can see addition therad WebViewCoreThre
so, the thread is created by admob or share?

i clone admob repo(https://github.com/googleads/googleads-mobile-android-examples) and run banner example project

admob official example show thread WebViewCoreThre

Seems having android-AdMob-test set to true in sdkbox_config.json is the cause. I must have switched test to false the first time I added facebok as it doesn’t seem to make a difference now.
Does test under AdMob do anything locally or does it just include an addTestDevice with the current device id when it calls the ad builder behind the scenes?

It just include an addTestDeviceI, nothing more.