Sauce Labs Customer Idea Portal

Submit an idea and make Sauce Labs even better!

Higher resolution emulators for Android 5.0, 5.1, 6.0, 7.0

For 5.0 and above SauceLabs only offers the Android Emulator.


It would be nice if SauceLabs also offers 5.0 on other devices, like Nexus 5 or 6 or Moto X or similar.


Basically the size of the Android Emulator is small compared to current devices like Nexus 5 or the other current ones. That means the at least our App does not look like our real clients see, and our App is designed with those type of devices in mind.



  • Guest
  • Jun 12 2015
  • Shipped
  • Attach files
  • Chandra Yalangi commented
    9 Mar, 2018 01:19am

    Dear Sauce users,

    We are very excited to announce that the following high resolution emulators are available for beta testing. Please email me at if you would like to try out the new emulators.

    • Samsung Galaxy Tab S3, 9.7"
    • Samsung Galaxy Tab A 10, 10.1"
    • Samsung Galaxy S8+
    • Samsung Galaxy S8
    • Samsung Galaxy S7 Edge
    • Samsung Galaxy S7
    • Samsung Galaxy S6
    • Google Pixel
    • Google Pixel C

    Beta test program will end on March 30, 2018. 

    Thank you,

    Chandra Yalangi


  • Srinivas R commented
    2 Oct, 2017 05:42pm

    Hi Team,

    Do we have any time line on this.. We still don't have 10' tablet emulators available in sauce labs


  • Miquel OC commented
    1 Dec, 2016 04:07am

    It doesn't look they plan to fix this in the short term. I solved my screen size issues trying another simulator described in their wiki. It's kind of old, but it does the work:


    DesiredCapabilities caps =;
    caps.setCapability("platform", "Linux");
    caps.setCapability("version", "4.4");
    caps.setCapability("deviceName","Samsung Galaxy S3 Emulator");
    caps.setCapability("deviceOrientation", "portrait");
  • Bharadwaj commented
    21 Sep, 2016 12:34pm

    Hi Team,
    In platform configurator only two emulators for android version 5.0 and one emulator for android version 5.1 is available.Please add more emulators .

  • Brian Watson commented
    4 Sep, 2016 04:13pm

    PLEASE, get to this one soon!  This request is over a year old now and I too need to be added to this list.  What we really need for an Android image is either increase the resolution of the (Android GoogleAPI Emulator Android 5.0) image, or add another virtual device image that has both the GoogleAPI and Android 5.x on it for both a phone AND a tablet.

  • shailesh kadam commented
    26 Jul, 2016 10:47am

    ETA for Android 6 ?

  • Chiarng Lin commented
    7 Apr, 2016 06:28pm

    Hi Everyone, 

    We're keenly aware that our emulators do not reflect the Android device specs in the wild today, and we're working hard to resolve the infrastructural blockers that are stopping us from rolling out emulators at higher resolution and RAM. For now, Android 5.0/5.1 are available via the default Android Emulator device. It recently underwent a heap size upgrade to 64MB and a RAM upgrade to 1.8GB. They exist in both Google API versions as well as non-Google API versions. 



  • Satyajit Malugu commented
    7 Apr, 2016 04:15pm

    The emulator support on sauce labs need has to improve. Other than Samsung s4 and Nexus 5 emulators none of the others seems to even boot

  • G D commented
    6 Apr, 2016 12:27am

    We definitely need better Android Emulator options with regards to screen size and resolution. The current offering by Sauce Labs does not represent the current real-world view of our customers' devices. 

  • Jeff Benton commented
    25 Mar, 2016 03:15pm

    This page lists the currently available devices for android 5.0 and 5.1

    The default android device according to this page and the comments below is a 480 x 800 device with 500M of memory.

    This is not representative our actual customers. A significant number of our customers are running on Samsung devices.

    Android 5.0 has been out for almost 18 months. How or when can we get better android emulator device options?


    P.S. We tried the real device beta program and it did not work for us.  Too many network connectivity issues resulting in false failures.

  • Fernando Martin commented
    29 Jan, 2016 07:52pm

    Any update on this? This is starting to be a blocker issue for us

  • Bryan Lester commented
    21 Jan, 2016 09:06pm

    Is there any update on the timeline for this, or fixing the head / memory sizes on the Android emulator?  We now have nearly 50% of our users on 5.0+, compared to only 25% of our users that are on 4.4.  If this isn't addressed soon we're going to need to look at other options for mobile testing than Sauce Labs, since it can only cover a minority of our users.

  • Jack Whitney commented
    6 Jan, 2016 08:24pm

    We are also blocked by the low RAM / heap size of the 'Android Emulator' configuration. Much of the world has moved past 4.4 and yet we can't run tests at Sauce Labs on 5.0. Bumping heap size / ram to useful levels on the Android Emulator, which does have 5.0 support, would work for us.

  • Bryan Lester commented
    18 Dec, 2015 12:34am

    Something that could satisfy this in the near term is bumping heap size / ram to useful levels on the Android Emulator, which does have 5.0 support.  Is there a reason that is set so small?

  • Chiarng Lin commented
    17 Dec, 2015 10:48pm

    Hi everyone. I'm the new product manager for mobile at Sauce. I want to reassure everyone that we do intend to add the latest versions of Android on the other devices, and it is on our roadmap. I do not yet have a timeline for you at the moment. Thank you for your patience!

  • Bryan Lester commented
    26 Oct, 2015 06:25pm

    Any update on this?  We're seeing a lot of crashes in our app that are android 5.0 related, and want to get them covered in sauce.  The low RAM / heap size of the 'Android Emulator' configuration is blocking us.  Just like others mentioned, we're not too picky about the actual device as long as it has realistic RAM / head allocations.

  • Arjan Blok commented
    1 Oct, 2015 09:23pm

    Testing on android is useless if there isn't at least a phone AND a tablet available with the latest android major versions.

    But would it not be possible to create a service that would let you configure AVD's on the fly? Basically the same as you guys do with the VM's that run the desktop browsers?

  • Jack Moxon commented
    1 Oct, 2015 09:12pm

    Thanks, Jack and Fernando. We are evaluating and hope to have something working this quarter. 

  • Jack Whitney commented
    1 Oct, 2015 08:02pm

    We would be satisfied with Galaxy S5, as long as it is configured with enough memory. We currently run with Galaxy S4, which is configured with 1900 MB, so I would expect the S5 to have that much memory or more.

  • Guest commented
    1 Oct, 2015 06:29pm

    It would be a good first step, still if the emulator RAM is not 2Gb (or whatever that phone usually has) it will still make our app (and as I can see many apps of the people that replied here) very slugish. Right now the tests locally take 4 or 5 minutes, but in SLabs they can take up to 20 minutes since the JVM is always doing GC.

  • Load older comments
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • +3