Question: I noticed I get the following messages after the screen has been off:

```
I/Ads﹕ Ad is not visible. Not refreshing ad.
I/Ads﹕ Scheduling ad refresh 60000 milliseconds from now.

```

I have the following code inside `onResume`:

```
    if (adView != null) {
        adView.resume();
    }

```

I stepped the code and it does get called just fine. It also works just fine if I get out of the activity and back in, the only issue appears to be when coming back after the screen goes off.

Anyone else with this issue?

Thanks.

EDIT: The code I use to create the adview and request

```
    adView = new AdView(this);
    adView.setAdSize(AdSize.BANNER);
    adView.setAdUnitId(id);
    LinearLayout layout = (LinearLayout) findViewById(R.id.main_layout);
    layout.addView(adView);
    createAdRequest();

```

The code of `createAdRequest()`:

```
    AdRequest.Builder builder = new AdRequest.Builder();
    builder.addKeyword(somekeyword);
    AdRequest adRequest = builder.build();
    adView.loadAd(adRequest);

```

I have noticed something else that is odd, I sometimes call `createAdRequest` again if I notice the keyword has changed, after I make that call the ads seem to stop refreshing as well but this time I don't see any visibility messages, I just don't see anymore requests until I call `createAdRequest` again.

Answer: 
Did you add code to your onPause and onDestroy as well?

```
@Override
protected void onPause() {
    adView.pause();
    super.onPause();
}

@Override
protected void onResume() {
    super.onResume();
    adView.resume();
}

```
Admob will not refresh unless the ad is visible to user. Obviously when your phone turns off no one can see ads, thus there is no reason for Admob to request another ad.

I personally faced the same problem a couple of times. Once I was placing AdView bellow a ListView. The AdView was not visible until the list was scrolled to the bottom, therefore Admob was constantly logging **"Ad is not visible. Not refreshing ad."**

Another time, I had no internet connection and the same message was continuously being logged.