<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for WorkingFromHere</title>
	<atom:link href="http://www.workingfromhere.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.workingfromhere.com/blog</link>
	<description>working from here, there, and everywhere.</description>
	<lastBuildDate>Fri, 16 Dec 2011 11:10:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>Comment on Orientation Sensor Tips in Android by G.</title>
		<link>http://www.workingfromhere.com/blog/2009/03/30/orientation-sensor-tips-in-android/comment-page-1/#comment-71</link>
		<dc:creator>G.</dc:creator>
		<pubDate>Fri, 16 Dec 2011 11:10:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=21#comment-71</guid>
		<description>Hi, I have a little problem with it.
I use accelerometer and magnetic field like you showed, but when my phone lie on the table the values are changing very fast like crazy. When it&#039;s should show 10, it&#039;s shows values between 6 and 11. 
So this is my questions: Why is that? How I can fix it? I need that to be very accurate.

And I also want use calibrate - sometimes you can see on other apps a warning that your device have to be calibrate and you have to wave your phone in a figure 8 pattern to reset magnetometr in your device.

i checked it in onAccuracyChanged, i checke the accuracy variable, but I don&#039;t sure that it&#039;s enought. Is it?

I hope you can help me, 
Sorry for mistakes if any there, probably there are. ;)

Greetings from Poland for all of you:)</description>
		<content:encoded><![CDATA[<p>Hi, I have a little problem with it.<br />
I use accelerometer and magnetic field like you showed, but when my phone lie on the table the values are changing very fast like crazy. When it&#8217;s should show 10, it&#8217;s shows values between 6 and 11.<br />
So this is my questions: Why is that? How I can fix it? I need that to be very accurate.</p>
<p>And I also want use calibrate &#8211; sometimes you can see on other apps a warning that your device have to be calibrate and you have to wave your phone in a figure 8 pattern to reset magnetometr in your device.</p>
<p>i checked it in onAccuracyChanged, i checke the accuracy variable, but I don&#8217;t sure that it&#8217;s enought. Is it?</p>
<p>I hope you can help me,<br />
Sorry for mistakes if any there, probably there are. <img src='http://www.workingfromhere.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Greetings from Poland for all of you:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Close / Hide the Android soft keyboard by Dvorak Keyboard Android</title>
		<link>http://www.workingfromhere.com/blog/2011/04/27/close-hide-the-android-soft-keyboard/comment-page-1/#comment-70</link>
		<dc:creator>Dvorak Keyboard Android</dc:creator>
		<pubDate>Mon, 24 Oct 2011 15:31:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=129#comment-70</guid>
		<description>[...] to use the tip (take what you like), so sensitive android better keyboard skins or insensitive. But close hide the android soft keyboard  once you have been to the desired page, the bottom line of it fine.The this case, if you are [...]</description>
		<content:encoded><![CDATA[<p>[...] to use the tip (take what you like), so sensitive android better keyboard skins or insensitive. But close hide the android soft keyboard  once you have been to the desired page, the bottom line of it fine.The this case, if you are [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Orientation Sensor Tips in Android by Lawrence D’Oliveiro</title>
		<link>http://www.workingfromhere.com/blog/2009/03/30/orientation-sensor-tips-in-android/comment-page-1/#comment-69</link>
		<dc:creator>Lawrence D’Oliveiro</dc:creator>
		<pubDate>Sat, 20 Aug 2011 11:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=21#comment-69</guid>
		<description>I have done another sample app that uses OpenGL to display a compass arrow that takes into account all three angle readings. The code is here:

https://github.com/ldo/3D-Compass</description>
		<content:encoded><![CDATA[<p>I have done another sample app that uses OpenGL to display a compass arrow that takes into account all three angle readings. The code is here:</p>
<p><a href="https://github.com/ldo/3D-Compass" rel="nofollow">https://github.com/ldo/3D-Compass</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Orientation Sensor Tips in Android by Pranav</title>
		<link>http://www.workingfromhere.com/blog/2009/03/30/orientation-sensor-tips-in-android/comment-page-1/#comment-68</link>
		<dc:creator>Pranav</dc:creator>
		<pubDate>Tue, 19 Jul 2011 11:58:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=21#comment-68</guid>
		<description>Bow to thee!! thanks a lot... I have ruined enough grey cells on this... you saved some from getting wasted!</description>
		<content:encoded><![CDATA[<p>Bow to thee!! thanks a lot&#8230; I have ruined enough grey cells on this&#8230; you saved some from getting wasted!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Orientation Sensor Tips in Android by iamZoltanVaradi</title>
		<link>http://www.workingfromhere.com/blog/2009/03/30/orientation-sensor-tips-in-android/comment-page-1/#comment-67</link>
		<dc:creator>iamZoltanVaradi</dc:creator>
		<pubDate>Fri, 24 Jun 2011 19:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=21#comment-67</guid>
		<description>Thanks for the code it helped me very much!

However if you only use value[2] to determine the orientation, you will never know if the phone is straight or straight,but upside down. for that, you&#039;ll ned value[1] too. if it&#039;s positive, then it&#039;s upside down, if it&#039;s negative, then it&#039;s held straight. hope it helps.

Zoli</description>
		<content:encoded><![CDATA[<p>Thanks for the code it helped me very much!</p>
<p>However if you only use value[2] to determine the orientation, you will never know if the phone is straight or straight,but upside down. for that, you&#8217;ll ned value[1] too. if it&#8217;s positive, then it&#8217;s upside down, if it&#8217;s negative, then it&#8217;s held straight. hope it helps.</p>
<p>Zoli</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JaLaGa by Jacq</title>
		<link>http://www.workingfromhere.com/blog/2010/07/15/jalaga/comment-page-1/#comment-59</link>
		<dc:creator>Jacq</dc:creator>
		<pubDate>Fri, 20 May 2011 11:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=81#comment-59</guid>
		<description>I really liked game and its helped tons but wish there was another format for answering instead of just multiple choice to make it more challenging for more advanced studiers. Great app the same.</description>
		<content:encoded><![CDATA[<p>I really liked game and its helped tons but wish there was another format for answering instead of just multiple choice to make it more challenging for more advanced studiers. Great app the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Orientation Sensor Tips in Android by Shell</title>
		<link>http://www.workingfromhere.com/blog/2009/03/30/orientation-sensor-tips-in-android/comment-page-1/#comment-41</link>
		<dc:creator>Shell</dc:creator>
		<pubDate>Sun, 20 Mar 2011 03:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=21#comment-41</guid>
		<description>the m in mGravity and mGeo... implies that they&#039;re module (global) level variables declared at the top of the class. 

they&#039;re likely just float arrays...

private float[] mGravity;
private float[] mGeomagnetic;</description>
		<content:encoded><![CDATA[<p>the m in mGravity and mGeo&#8230; implies that they&#8217;re module (global) level variables declared at the top of the class. </p>
<p>they&#8217;re likely just float arrays&#8230;</p>
<p>private float[] mGravity;<br />
private float[] mGeomagnetic;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Orientation Sensor Tips in Android by em</title>
		<link>http://www.workingfromhere.com/blog/2009/03/30/orientation-sensor-tips-in-android/comment-page-1/#comment-39</link>
		<dc:creator>em</dc:creator>
		<pubDate>Tue, 08 Feb 2011 18:36:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=21#comment-39</guid>
		<description>I have a question about the mGravity and mGeomagnetic variables. I realized that they&#039;re of type float[]. But i can&#039;t see where you declared them. I&#039;m just curious of what the size should be when you initialize them.</description>
		<content:encoded><![CDATA[<p>I have a question about the mGravity and mGeomagnetic variables. I realized that they&#8217;re of type float[]. But i can&#8217;t see where you declared them. I&#8217;m just curious of what the size should be when you initialize them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Orientation Sensor Tips in Android by tenaicous</title>
		<link>http://www.workingfromhere.com/blog/2009/03/30/orientation-sensor-tips-in-android/comment-page-1/#comment-38</link>
		<dc:creator>tenaicous</dc:creator>
		<pubDate>Wed, 01 Dec 2010 08:49:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=21#comment-38</guid>
		<description>What versions of Android does this apply to?</description>
		<content:encoded><![CDATA[<p>What versions of Android does this apply to?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on JaLaGa by Steven</title>
		<link>http://www.workingfromhere.com/blog/2010/07/15/jalaga/comment-page-1/#comment-37</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Thu, 21 Oct 2010 23:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.workingfromhere.com/blog/?p=81#comment-37</guid>
		<description>Joshua,

great app, it was definitely helpful for me as a new person to japanese. One thing I like to see in an update is some sort of library that gives you example on how to pronounce the kana. Like other people I felt some levels moved to quickly then others. Maybe some sort of test as you finish a level. But overall great app!</description>
		<content:encoded><![CDATA[<p>Joshua,</p>
<p>great app, it was definitely helpful for me as a new person to japanese. One thing I like to see in an update is some sort of library that gives you example on how to pronounce the kana. Like other people I felt some levels moved to quickly then others. Maybe some sort of test as you finish a level. But overall great app!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

