64

I would like to test my application with new Samsung Galaxy Tab tablet.

What parameter should I set in emulator to emulate this device?

  • What resolution and density should I set?
  • How can I indicate that this is large screen device?
  • What hardware does this tablet support?
  • What is max heap size?
  • Which Android version?
Dariusz Bacinski
  • 7,471
  • 7
  • 33
  • 43

7 Answers7

89

UPDATED:
Matt provided a great link on how to add emulators for all Samsung devices.

OLD:
To get the official Samsung Galaxy Tab emulator do the following:

  1. Open the Android SDK and AVD Manager
  2. Click on Available packages
  3. Expand the Third party Add-ons. There you will see Samsung Electronics add-ons.
  4. Once the add-on is installed create a new emulator. Under Target you will see the new Samsung Tab settings, select that.

That's it!

Jona
  • 12,642
  • 13
  • 82
  • 124
6

You can't.

"The Samsung Emulator has the same functionality as the Generic Android Emulator, but varies with the size and appearance of the device."

The problem with Samsung is that they don't use a generic android image, they have custom apps and they react in custom ways and do weird things you wouldn't expect and when you're trying to fix bugs that's what you want. You cannot get that. You need access to a physical device to get the right ecosystem to hunt down the bugs and map out which intents work and how they work on that device. And sometimes there are errors that only occur on Samsung devices because some of the core rendering code is different as well. I've had errors where all Android devices except Samsung would work flawlessly but the scheme itself could not work on Samsung and had to be scrapped. The only thing Samsung allows is skinning and that won't properly note the changes in the rendering pipeline or how the samsung ecosystem deals with intents.

You can make the device look similar, that's worthless. I don't care what it looks like, I care whether this bug still affects that particular model or whether the tweak to the intents I made rectified the issue and I can't learn that from a pretty picture as the border to the same device.

Tatarize
  • 8,825
  • 4
  • 53
  • 56
5

I found under website.

http://developer.samsung.com/android/tools-sdks/Samsung-GALAXY-Tab-Emulator

Extract zip file to add-ons under android sdk path. then launch Android SDK Manager. under "extras" folder check "Android + Google APIs for GALAXY Tab, API 8, revision 1" item and install package.

That's all.

Kim Ki Won
  • 1,581
  • 1
  • 21
  • 18
  • 4
    I followed the same steps but now in extras i am able to see "GALAXY TAB by Samsung.... so on" but it has red file broken icon on hover says Addon Failed to Load: Unable to find base platform with API Level '8'. Do you have any idea on how to fix this. – Hbksagar Jun 14 '13 at 09:20
  • @HBK I know this is old, but I have the same problem, did you find the solution? – The One Sep 16 '14 at 19:28
  • @216 No clue what I was working on then. Sorry, I couldn't help you out. – Hbksagar Sep 17 '14 at 07:17
  • 1
    Your link is broken – AXMIM Dec 18 '19 at 18:59
4

What resolution and density should I set?

  • 1024x600

How can I indicate that this is large screen device?

  • you can't really (not that i know of)

What hardware does this tablet support?

What is max heap size?

  • not sure

Which Android version?

  • 2.2

Hope that helps - check the spec page for all unanswered questions.

JohnLBevan
  • 18,988
  • 5
  • 75
  • 151
xil3
  • 16,020
  • 8
  • 56
  • 95
  • what about density? I heard that it has got not standard (high) density. – Dariusz Bacinski Sep 19 '10 at 13:55
  • 2
    "In this context, the Samsung has another little surprise: If you do the arithmetic, its screen has 170 DPI, which is far from the densest among Android devices. Still, it declares itself as “hdpi” (and as having a “large” screen size). The reason is simple: It looks better that way." --- I have found this at google blog, but I do not know how to understand that. Is it 170 dpi or just standard hdpi? – Dariusz Bacinski Sep 19 '10 at 18:17
  • If it has 170 DPI, that means it's closer to mdpi (160 DPI), not hdpi (240 DPI). – xil3 Sep 19 '10 at 21:16
  • 1
    @ xil3 I know that, but pls read message from google blog. Should I set 170 dpi or 240 dpi in the emulator? – Dariusz Bacinski Sep 20 '10 at 06:18
  • 3
    170 is certainly false. The is only 120, 160, 240 and 320 available. Everything else has to to be rounded up or down. – Martin Aug 09 '11 at 06:11
3

If you are developing on Netbeans, you will not get the Third-Party add-ons. You can download the Skins directly from Samsung here: http://developer.samsung.com/android/tools-sdks

After download, unzip to ...\Android\android-sdk\add-ons[name of device]

Restart the Android SDK Manager, and the new device should be there under Extras.

It would be better to add the download site directly to the SDK...if anyone knows it, please post it.

Scott

Scott Wardlaw
  • 536
  • 5
  • 12
  • That url goes to http://developer.samsung.com/technical-doc/list.do and is just a technical documentation list.. – rhand Jan 09 '15 at 05:42
  • Man...crazy web developers have changed things again! After a lot of searching, it looks like Samsung has removed all references to those emulator skins. They want you to use their real device lab. Makes sense for final testing, but would be nice to have a tuned emulator for early testing! – Scott Wardlaw Jan 10 '15 at 14:30
2

Go to this link ... https://github.com/bsodmike/android-avd-profiles-2016/blob/master/Samsung%20Galaxy%20Tab%20A%2010.1%20(2016).xml

Save as xml file in your computer. Go on Android Studio => Tools => AVD Manager => + Create Virtual Device => Import Hardware Profiles ... choose the saved file and the device will be available on the tablet's section.

Happy Android developments guys!!!

dokam_scotland
  • 205
  • 3
  • 9
-2

I don't know if it is help. Create an AVD for a tablet-type device: Set the target to "Android 3.0" and the skin to "WXGA" (the default skin). You can check this site. http://developer.android.com/guide/practices/optimizing-for-3.0.html

Naya
  • 7