Note that there are some explanatory texts on larger screens.

plurals
  1. POAdMob Banner Sizes on Android
    primarykey
    data
    text
    <p>I am currently integrating AdMob into my Android game. </p> <p>I have difficulties integrating smart banners into my framelayout-based layout, because they take up different amounts of screen real estate on different devices.</p> <p>For example, if I display a smart banner on my Acer A500 (MDPI 1280x800), I receive one of the size 1280x90px, whereas on my Nexus 7, I receive one with 1279x66px (TVDPI 1280x800) and on my Galaxy Nexus (HDPI 1280x720) with 1196x64px. </p> <p>According to the AdMob documentation, that might be understandable behaviour, considering that the values given in the documentation are dp: <a href="https://developers.google.com/mobile-ads-sdk/docs/admob/smart-banners" rel="noreferrer">https://developers.google.com/mobile-ads-sdk/docs/admob/smart-banners</a></p> <p>However, this behaviour is a great problem for me, since a smartbanner with a height of 90px on a 1200x800px MDPI screen takes up a lot more screen real estate than a smart banner with a height of 64px on an HDPI screen (See screenshots below). </p> <p>So, here are my questions: - How much space should i reserve at least for a smart banner? - Has anyone tried something similar, and how did you deal with that?</p> <p>Note: Unfortunately, using a layout different to framelayout is not an option at the moment. Additionally, XML layouts can not be used to integrate the ads.</p> <p>Best Regards,</p> <p>Lorenz</p> <p>Screenshots:</p> <p><a href="https://imgur.com/qGAk77Y" rel="noreferrer">http://imgur.com/qGAk77Y</a> (A500)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload