<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Emulator &#8211; Wiebe Elsinga</title>
	<atom:link href="http://wiebe-elsinga.com/blog/tag/emulator/feed/" rel="self" type="application/rss+xml" />
	<link>http://wiebe-elsinga.com/blog</link>
	<description>Blog</description>
	<lastBuildDate>Thu, 17 Jan 2013 16:29:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.8</generator>
	<item>
		<title>Google TV emulator device definition</title>
		<link>http://wiebe-elsinga.com/blog/google-tv-emulator-device-definition/</link>
					<comments>http://wiebe-elsinga.com/blog/google-tv-emulator-device-definition/#respond</comments>
		
		<dc:creator><![CDATA[W.Elsinga]]></dc:creator>
		<pubDate>Thu, 17 Jan 2013 09:29:49 +0000</pubDate>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[How-To]]></category>
		<category><![CDATA[Emulator]]></category>
		<category><![CDATA[Google TV]]></category>
		<guid isPermaLink="false">http://wiebe-elsinga.com/blog/?p=1405</guid>

					<description><![CDATA[So you want to use a Google TV emulator to develop Android applications. Many people having problems using the Google TV emulator because it hangs during booting (only showing the Google TV logo). The problem is that it only works with specific device configurations and resolutions. So lets have a look at the device definition: This setup is for a 720p resolution, for a 1080p you must change the resolution to 1920×1080 and the density from tvdpito xhdpi. Once the device definition is created, the next step is to create a new Android Virtual Device using it:]]></description>
										<content:encoded><![CDATA[<p>So you want to use a Google TV emulator to develop Android applications. Many people having problems using the Google TV emulator because it hangs during booting (only showing the Google TV logo).<br />
The problem is that it only works with specific device configurations and resolutions.</p>
<p>So lets have a look at the device definition:<br />
<a href="http://wiebe-elsinga.com/blog/?attachment_id=1407" rel="attachment wp-att-1407"><img loading="lazy" class="size-full wp-image-1407 aligncenter" alt="Device definition" src="http://wiebe-elsinga.com/blog/wp-content/uploads/2013/01/Screen-Shot-2013-01-17-at-17.21.58.png" width="667" height="389" srcset="http://wiebe-elsinga.com/blog/wp-content/uploads/2013/01/Screen-Shot-2013-01-17-at-17.21.58.png 667w, http://wiebe-elsinga.com/blog/wp-content/uploads/2013/01/Screen-Shot-2013-01-17-at-17.21.58-300x175.png 300w" sizes="(max-width: 667px) 100vw, 667px" /></a></p>
<p>This setup is for a <strong>720p</strong> resolution, for a <strong>1080p</strong> you must change the resolution to <strong>1920×1080</strong> and the density from <strong>tvdpi</strong>to <strong>xhdpi</strong>. Once the device definition is created, the next step is to create a new <strong>Android Virtual Device</strong> using it:</p>
<p><a href="http://wiebe-elsinga.com/blog/?attachment_id=1408" rel="attachment wp-att-1408"><img loading="lazy" class="aligncenter size-full wp-image-1408" alt="Avd" src="http://wiebe-elsinga.com/blog/wp-content/uploads/2013/01/Screen-Shot-2013-01-17-at-17.25.27.png" width="529" height="525" srcset="http://wiebe-elsinga.com/blog/wp-content/uploads/2013/01/Screen-Shot-2013-01-17-at-17.25.27.png 529w, http://wiebe-elsinga.com/blog/wp-content/uploads/2013/01/Screen-Shot-2013-01-17-at-17.25.27-150x150.png 150w, http://wiebe-elsinga.com/blog/wp-content/uploads/2013/01/Screen-Shot-2013-01-17-at-17.25.27-300x298.png 300w" sizes="(max-width: 529px) 100vw, 529px" /></a></p>
]]></content:encoded>
					
					<wfw:commentRss>http://wiebe-elsinga.com/blog/google-tv-emulator-device-definition/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How-To: Android emulator performance tuning tips</title>
		<link>http://wiebe-elsinga.com/blog/android-emulator-performance-tuning-tips/</link>
					<comments>http://wiebe-elsinga.com/blog/android-emulator-performance-tuning-tips/#comments</comments>
		
		<dc:creator><![CDATA[W.Elsinga]]></dc:creator>
		<pubDate>Sun, 10 Jul 2011 23:30:10 +0000</pubDate>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[How-To]]></category>
		<category><![CDATA[Android]]></category>
		<category><![CDATA[Emulator]]></category>
		<category><![CDATA[Honeycomb]]></category>
		<category><![CDATA[Tips]]></category>
		<guid isPermaLink="false">http://wiebe-elsinga.com/blog/?p=674</guid>

					<description><![CDATA[As some of you may already noticed, running Android Honeycomb application on the Android emulator, isn&#8217;t the most fun thing to do, because it&#8217;s painfully slow. Besides the start-up time (can be avoided, which I explain later), just using it is a pain. Google is planning to improve the performance, but if you can&#8217;t wait that long I’ve put together a few tips which may help improve your experience. &#8211; Emulated memory size. By default the Honeycomb AVD is created to emulate 256MB of RAM, my advice is to increase this significant, I’m using 1GB (1024MB). If you’re creating the AVD for Honeycomb in Eclipse you’ll find the RAM setting in the Hardware section under “Device ram size”. If you already have an AVD you can increase the setting by finding the directory you’re AVD is in (e.g. .android/avd/honeycomb.avd), editing the emulator-user.ini file, and changing hw.ramSize to whatever you want the ram size to be in MB. &#8211; Enable Snapshots. Enabling snapshots on an AVD allows the emulator to start-up an AVD in the state it was in when you closed it. This means that it doesn’t have to go through the boot-up procedure each time, which will save you a reasonable chunk of time. First on the initial launch make sure you select “Save to snapshot”. Get the emulator up and running and put it into the state you want. I like to have it start at the desktop (home screen) view. Now close the emulator. I found that it wasn’t very responsive when closing, so wait a bit, watch the mouse icon go to “busy” and let it write everything to disk. Now, launch the emulator again and this time uncheck “Save to snapshot” but make sure Launch from snapshot is chosen. Voila! The emulator launches quickly. And when you save it it shuts down quickly because it’s not saving anymore.]]></description>
										<content:encoded><![CDATA[<p>As some of you may already noticed, running Android Honeycomb application on the Android emulator, isn&#8217;t the most fun thing to do, because it&#8217;s painfully slow. Besides the start-up time (can be avoided, which I explain later), just using it is a pain. Google is planning to improve the performance, but if you can&#8217;t wait that long I’ve put together a few tips which may help improve your experience.<br />
<span id="more-674"></span><br />
&#8211; <em><strong>Emulated memory size</strong></em>.<br />
By default the Honeycomb <em>AVD</em> is created to emulate 256MB of RAM, my advice is to increase this significant, I’m using 1GB (1024MB).<br />
If you’re creating the <em>AVD</em> for Honeycomb in Eclipse you’ll find the RAM setting in the Hardware section under “<em>Device ram size</em>”. If you already have an <em>AVD</em> you can increase the setting by finding the directory you’re <em>AVD</em> is in (e.g. .android/avd/honeycomb.avd), editing the <em>emulator-user.ini</em> file, and changing <em>hw.ramSize</em> to whatever you want the ram size to be in MB.</p>
<p>&#8211; <em><strong>Enable Snapshots</strong></em>.<br />
Enabling snapshots on an <em>AVD</em> allows the emulator to start-up an <em>AVD</em> in the state it was in when you closed it. This means that it doesn’t have to go through the boot-up procedure each time, which will save you a reasonable chunk of time.<br />
First on the initial launch make sure you select “<em>Save to snapshot</em>”. Get the emulator up and running and put it into the state you want. I like to have it start at the desktop (home screen) view. Now close the emulator. I found that it wasn’t very responsive when closing, so wait a bit, watch the mouse icon go to “busy” and let it write everything to disk.<br />
Now, launch the emulator again and this time uncheck “<em>Save to snapshot</em>” but make sure Launch from snapshot is chosen. Voila! The emulator launches quickly. And when you save it it shuts down quickly because it’s not saving anymore.</p>
<p><a href="http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_1.png" rel="lightbox[674]" title="snapshot_1"><img loading="lazy" class="size-medium wp-image-676 alignnone" title="snapshot_1" src="http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_1-212x300.png" alt="" width="212" height="300" srcset="http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_1-212x300.png 212w, http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_1.png 259w" sizes="(max-width: 212px) 100vw, 212px" /></a> <a href="http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_2.png" rel="lightbox[674]" title="snapshot_2"><img loading="lazy" class="size-medium wp-image-677 alignright" title="snapshot_2" src="http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_2-212x300.png" alt="" width="212" height="300" srcset="http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_2-212x300.png 212w, http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_2-213x300.png 213w, http://wiebe-elsinga.com/blog/wp-content/uploads/2011/07/snapshot_2.png 259w" sizes="(max-width: 212px) 100vw, 212px" /></a></p>
]]></content:encoded>
					
					<wfw:commentRss>http://wiebe-elsinga.com/blog/android-emulator-performance-tuning-tips/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
