It's a well-known issue that Android devices have very few similarities when it comes to their hardware. From the available memory and SD card storage to the resolution and ratio of their display, there are practically no assumptions we can make about the device our application runs on.
The standard approach taken by AndEngine developers is to simply set a resolution for their scene and then configure the engine with a so-called resolution policy. What this does is tell the engine how to scale and crop the rendered image. Here, we have the following options:
FixedResolutionPolicy
FillResolutionPolicy
RelativeResolutionPolicy
RatioResolutionPolicy
CropResolutionPolicy
Of these, FixedResolutionPolicy is the simplest one. It simply places the rendered image on the display with a 1:1 pixel-to-pixel ratio. See this illustration, including the gaps (white) it may leave around the rendered image on the screen:
FillResolutionPolicy, as the name suggests, fills the display...