tag:blogger.com,1999:blog-51505936721906312002024-03-19T02:23:50.733-07:00Android OSfor Controlling1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-5150593672190631200.post-26450080417344510382012-05-20T18:45:00.002-07:002012-05-20T18:45:58.548-07:00Live Android on Laptop or PC via LiveCD or USB<div dir="ltr" style="text-align: left;" trbidi="on">
<span class="" id="result_box" lang="en"><span class="hps">Try</span> <span class="hps">operating system</span> <span class="hps">Android</span> <span class="hps">is the desire of</span> <span class="hps">many</span> <span class="hps">technology enthusiasts</span><span>.</span> <span class="hps">It's great</span> <span class="hps">if</span> <span class="hps">the</span> <span class="hps">test run</span> <span class="hps">it on</span> <span class="hps">your</span> <span class="hps">laptop</span> <span class="hps">or</span> <span class="hps">desktop PC</span> <span class="hps">without</span> <span class="hps">using</span> <span class="hps">any application</span> <span class="hps">that</span> <span class="hps">put</span> <span class="hps">what</span><span>.</span> <span class="hps">The following</span> <span class="hps">method</span> <span class="hps">lets you run</span> <span class="hps">Android</span> <span class="hps">from</span> <span class="hps">external memory card</span> <span class="hps">or</span> <span class="hps">USB</span> <span class="hps">or CD</span> <span class="hps">on the</span> <span class="hps">real</span> <span class="hps">hardware</span> <span class="hps">of the computer.</span></span><br />
<div style="text-align: center;">
<span class="" id="result_box" lang="en"><span class="hps"> </span></span><span class="" id="result_box" lang="en"><span class="hps"> </span></span><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXCEVNkVi0R2S98UKP8zPAe4uyyV2WHSTvojUjc7aPU9tP5Q34HUGNwlmnkjRKBpxnP-Jc7Q0aUUD9czNbAnBN91fR5t86PzI96Aop8g8MDa2x7j-bZqEn3pczr7r6nTnzwdD6aHofF_s/s1600/android-on-laptop-pc.jpg" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="257" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXCEVNkVi0R2S98UKP8zPAe4uyyV2WHSTvojUjc7aPU9tP5Q34HUGNwlmnkjRKBpxnP-Jc7Q0aUUD9czNbAnBN91fR5t86PzI96Aop8g8MDa2x7j-bZqEn3pczr7r6nTnzwdD6aHofF_s/s400/android-on-laptop-pc.jpg" width="400" /></a></div>
<span class="" id="result_box" lang="en"><span class="hps">Only need to</span> <span class="hps">download</span> <span class="hps">two</span> <span class="hps">files</span> <span class="hps">android</span><span>-x86</span><span>-1.6</span><span class="atn">-</span><span>r2.iso</span> <span class="hps">and</span> <span class="hps">UNetbootin</span><span>.</span><br /> <span class="hps">Then</span> <span class="hps">install</span> <span class="hps">the following steps</span><span>:</span><br /> <span class="hps">1</span><span>.</span> <span class="hps">First</span> <span class="hps">prepare</span> <span class="hps">a</span> <span class="hps">USB</span> <span class="hps">storage space</span> <span class="hps">is</span> <span class="hps">at least</span> <span class="hps">256Mb</span><span>.</span><br /> <span class="hps">2</span><span class="">.</span> <span class="hps">UNetbootin</span> <span class="hps">download</span> <span class="hps">by</span> <span class="hps">link: </span><a href="http://sourceforge.net/projects/unetbootin/"><span class="hps">http://sourceforge.net/projects/unetbootin/</span></a><br /> <span class="hps">3.</span> <span class="hps">Download</span> <span class="hps">android</span><span>-x86</span><span>-1.6</span><span class="atn">-</span><span>r2.iso</span> <span class="hps">the</span> <span class="hps">link: </span><a href="http://www.android-x86.org/download"><span class="hps">http://www.android-x86.org/download</span></a></span><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg0qaX_uxE-F1AoGhRuBFlyAKoNA7G0M1n5UW8ITe4-raaXrVUP9lShu62c77Rjc0PbaeiT-n4w_hxwMAIUh-pGL-k4PDptyXcXai6Jo73-PG-0MI_8lwJTNTXU6QrfrADyURx6sMS8kvE/s1600/UNetbootin.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="300" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg0qaX_uxE-F1AoGhRuBFlyAKoNA7G0M1n5UW8ITe4-raaXrVUP9lShu62c77Rjc0PbaeiT-n4w_hxwMAIUh-pGL-k4PDptyXcXai6Jo73-PG-0MI_8lwJTNTXU6QrfrADyURx6sMS8kvE/s400/UNetbootin.png" width="400" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXCEVNkVi0R2S98UKP8zPAe4uyyV2WHSTvojUjc7aPU9tP5Q34HUGNwlmnkjRKBpxnP-Jc7Q0aUUD9czNbAnBN91fR5t86PzI96Aop8g8MDa2x7j-bZqEn3pczr7r6nTnzwdD6aHofF_s/s1600/android-on-laptop-pc.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><br /></a></div>
<span class="" id="result_box" lang="en"><span class="hps">After completed</span> download<span class="hps"> two</span> <span class="hps"></span><span class="hps">files</span>, let <span class="hps">run</span> <span class="hps">file:</span> <span class="hps">UNetbootin</span><span class="atn">-</span><span class="atn">windows-</span><span>377.exe</span><br /> <span class="hps">then</span> <span class="hps">select</span> <span class="hps">option</span><span> </span></span><span class="" id="result_box" lang="en"><span class="hps">Diskimage</span><span class="hps"></span></span><span class="" id="result_box" lang="en"><span>, click the</span> <span class="hps atn">sign (</span><span>...</span><span>)</span> <span class="hps">select the path</span> <span class="hps">to the</span> <span class="hps">file</span> <span class="hps">android</span><span class="">-x86</span><span>-1.6</span><span class="atn">-</span><span>r2.iso</span><span>.</span><br /> <span class="hps">Select</span> <span class="hps">Type</span> <span class="hps">as</span> <span class="hps">USB</span> <span class="hps">driver</span><span>,</span> <span class="hps">choose</span> <span class="hps">USB</span> <span class="hps">Driver</span> <span class="hps">you want to install</span> <span class="hps">Android</span> <span class="hps">OS</span><span>.</span><br /> <span class="hps">Click</span> <span class="hps">Ok</span> <span class="hps">and everything</span> <span class="hps">has been installed</span> <span class="hps">for you.</span><br /> <span class="hps">- After</span> <span class="hps">installation is completed</span> <span class="hps">you need to adjust</span> <span class="hps">a</span> <span class="hps">bit in the</span> <span class="hps">BIOS</span> <span class="hps">of</span> <span class="hps">your</span> <span class="hps">PC</span> <span class="hps">at the</span> <span class="hps">Boot</span> <span class="hps">menu,</span> <span class="hps">you</span> <span class="hps">select the</span> <span class="hps">preferred</span> <span class="hps">boot</span> <span class="hps">from</span> <span class="hps">USB</span><span>.</span><br /> <span class="hps">When</span> <span class="hps">your</span> <span class="hps">computer boots</span> <span class="hps">boot</span> <span class="hps">selection</span> <span class="hps">menu</span> <span class="hps">will appear</span><span>:</span> <span class="hps">Live</span> <span class="hps">CD -</span> <span class="hps">Run</span> <span class="hps">Android</span><span class="atn">-</span><span>x86</span> <span class="hps">without installation</span><span>.</span></span><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjf8lGXr8Guui7BPEFNtRz7nvCwkaIePm063zTe7eAzCnuYPqdigW4hSYoR8r3LvbDz0YXljPOXq0wn2UnmYW9y36OI0s8n-5aCD515n5lort2pNp0VV9ctErJ2CJ9tt1db3h9c2n0wkzQ/s1600/android-boot-menu.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="231" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjf8lGXr8Guui7BPEFNtRz7nvCwkaIePm063zTe7eAzCnuYPqdigW4hSYoR8r3LvbDz0YXljPOXq0wn2UnmYW9y36OI0s8n-5aCD515n5lort2pNp0VV9ctErJ2CJ9tt1db3h9c2n0wkzQ/s400/android-boot-menu.png" width="400" /></a></div>
</div>1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.com1tag:blogger.com,1999:blog-5150593672190631200.post-35359923187741142932012-05-19T01:05:00.001-07:002012-05-19T01:05:33.411-07:00Cortex-A15 Processor<div dir="ltr" style="text-align: left;" trbidi="on">
<div style="text-align: justify;">
The ARM Cortex™-A15 MPCore™ processor is the highest-performance
licensable processor the industry has ever seen. It delivers
unprecedented processing capability, combined with low power consumption
to enable compelling products in markets ranging from smartphones,
tablets, mobile computing, high-end digital home, servers and wireless
infrastructure. The unique combination of performance, functionality,
and power-efficiency provided by the Cortex-A15 MPCore processor
reinforces ARM’s clear leadership position in these high-value and
high-volume application segments.</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXQR4i368Z-yuUGXI-PhohgFWaGXHHG3VOOlELlu_pN9zlZgkAFhD7pGTNawus4G1gv2klpCG-QLy_F2ExjO7eB6KfhqXoej1knfDS7_41e8MUOGVqcWzJt0jwjYfdYyQs7iSTsvaJN28/s1600/cortex-a5.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="256" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXQR4i368Z-yuUGXI-PhohgFWaGXHHG3VOOlELlu_pN9zlZgkAFhD7pGTNawus4G1gv2klpCG-QLy_F2ExjO7eB6KfhqXoej1knfDS7_41e8MUOGVqcWzJt0jwjYfdYyQs7iSTsvaJN28/s400/cortex-a5.jpg" width="400" /></a></div>
<div class="mainbodycontent">
<h3>
Overview</h3>
<div style="text-align: justify;">
The ARM Cortex™-A15
MPCore™ processor delivers unprecedented processing capability, combined
with low power consumption to enable compelling products in a wide
range of new and existing ARM markets ranging from mobile computing, high-end digital home, servers and wireless infrastructure.</div>
<div style="text-align: justify;">
The Cortex-A15 MPCore processor is the latest member of the Cortex-A series of
processors, ensuring full application compatibility with all of the
other highly acclaimed Cortex-A processors. This enables immediate
access to an established developer and software ecosystem including
Android™, Adobe® Flash® Player, Java Platform Standard Edition (Java
SE), JavaFX, Linux, Microsoft Windows Embedded, Symbian and Ubuntu,
along with more than 700 ARM Connected Community™ members providing applications software, hardware and software development tools, middleware and SoC design services. </div>
<div style="text-align: justify;">
The
Cortex-A15 MPCore processor has an out-of-order superscalar pipeline
with a tightly-coupled low-latency level-2 cache which can be up to 4MB
in size. Additional improvements in floating point and NEON™
media performance result in devices that deliver the next-generation
user experience for consumers as well as high-performance computation
for web infrastructure applications. </div>
<div style="text-align: justify;">
It is expected that mobile
configurations of the Cortex-A15 MPCore processor will deliver over five
times the performance of today’s advanced smartphones. In advanced
infrastructure applications, the Cortex-A15 running at up to 2.5GHz will
enable highly scalable solutions within constantly shrinking energy,
thermal and cost budgets</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjCtNjSPK25OKOhE9A5Mw2zilmExjd1nkgIf9pXsFkmWhJFCHlLEilwCxKWi3Fwht5gLl29ArnCPaRjA49CiXtZcUSxB5ZXS9m_ul3w5bM59RoVP6wXZkBpyZALAWDGuK1eNS3LDRVQPQ/s1600/cortex-a5-mpcore.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjCtNjSPK25OKOhE9A5Mw2zilmExjd1nkgIf9pXsFkmWhJFCHlLEilwCxKWi3Fwht5gLl29ArnCPaRjA49CiXtZcUSxB5ZXS9m_ul3w5bM59RoVP6wXZkBpyZALAWDGuK1eNS3LDRVQPQ/s400/cortex-a5-mpcore.jpg" width="346" /></a></div>
<div style="text-align: justify;">
<br /></div>
<h4>
Applications:</h4>
<ul style="text-align: justify;">
<li>Advanced Smartphones</li>
<li>Mobile Computing</li>
<li>High-end Digital Home Entertainment</li>
<li>Wireless Infrastructure</li>
<li>Low-power Servers</li>
</ul>
<div style="text-align: justify;">
The
growing complexity of the Web2.0 centric devices is creating the
requirement for devices to support multiple software personalities and
combine disparate functionality. For this reason the Cortex-A15 MPCore
processor introduces new technology from ARM that enables efficient
handling of the complex software environments including full hardware
virtualization, Large Physical Address Extensions (LPAE) addressing up
to 1TB of memory as well as error correction capability for
fault-tolerance and soft-fault recovery.</div>
<div style="text-align: justify;">
The Cortex-A15 MPCore
processor is the first ARM processor to incorporate highly efficient
hardware support for data management and arbitration, enabling multiple
software environments and their applications to simultaneously access
the system capabilities. This enables the realization of devices that
are robust, with virtual environments that are isolated from each other.</div>
<div style="text-align: justify;">
<br /></div>
<div style="text-align: right;">
<b>By ARM</b> </div>
</div>
</div>1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.com0tag:blogger.com,1999:blog-5150593672190631200.post-89813140578898910112012-05-09T23:13:00.000-07:002012-05-09T23:13:26.758-07:00FPGA tool on Android platform<div dir="ltr" style="text-align: left;" trbidi="on">
Robei is the world smallest EDA tool for FPGA design and simulation.
With this tool, you can design your hardware visually at anywhere, and
view the simulation result through waveform. It is a tiny, fast software
for hardware prototyping and verification.<br />
Imagine that when you are waiting for a bus, on a business travel or
laying on the bed, suddenly a genius idea for a piece of hardware
showing to your mind, how can you implement it with just mobile phones
or tablets? Robei runs on any Android platform, you can implement your
design and test it immediately in such situation.<br />
<strong>Currently, Robei released 2.1 version on Windows and Android
platform. You can share the same model on android platform and windows
platform.</strong><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJxarPiENyAWl3VSEYdsBGXhbmy_q3hTO_EEwiJJdVT01eks8-xe2d82ntjxe6lqPmauTG00xliIhSlrQE70KezwWJCR9pStNXVzexN3EBdDg6xqlwPp08OFIakgQ_Q1dDumHwMTOwjCk/s1600/Robei.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="370" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJxarPiENyAWl3VSEYdsBGXhbmy_q3hTO_EEwiJJdVT01eks8-xe2d82ntjxe6lqPmauTG00xliIhSlrQE70KezwWJCR9pStNXVzexN3EBdDg6xqlwPp08OFIakgQ_Q1dDumHwMTOwjCk/s400/Robei.jpg" width="400" /></a></div>
<br />
Robei 3.0 already released<strong><a href="https://play.google.com/store/apps/details?id=org.kde.necessitas.example.Robei2" target="_blank"> Robei 3.0</a></strong></div>1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.com0tag:blogger.com,1999:blog-5150593672190631200.post-89119776868409858112012-05-09T18:48:00.002-07:002012-05-09T23:04:24.011-07:00Android to Microcontroller via Bluetooth<div dir="ltr" style="text-align: left;" trbidi="on">
<span style="color: #333333;"><b>1. Choose a bluetooth device for your microcontroller.</b></span><br />
<span style="color: #333333;">The first thing you need to do is
decide which bluetooth device you want to use for your microcontroller.
You will want a device that you can communicate with via the serial
protocol. I used the BlueSmirf Gold modem from <a href="http://www.sparkfun.com/products/582"><span style="color: blue;">Sparkfun</span></a>.</span><br />
<a href="http://www.ryandebenham.com/wp-content/uploads/2011/05/bluesmirf1.jpg"><span style="color: #333333;"><br /></span></a><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhIvon2h3iRxGsXmSs65tcyhNYOK-SN6NVZ1ROfA2ay9cn7kzyDUJiBQZNrOTQuqyyaaZxWueQemRW2kyPj81bsYbd9TyjbmokIqnapAAlSu2mC1M7yffgITkAP1UnvnltHBe4SmUX9M68/s1600/atmega8.jpeg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhIvon2h3iRxGsXmSs65tcyhNYOK-SN6NVZ1ROfA2ay9cn7kzyDUJiBQZNrOTQuqyyaaZxWueQemRW2kyPj81bsYbd9TyjbmokIqnapAAlSu2mC1M7yffgITkAP1UnvnltHBe4SmUX9M68/s1600/atmega8.jpeg" /></a></div>
<span style="color: #333333;">You will probably have to solder some headers to the chip, I used male headers to make it simple to plug into my breadboard.</span><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1NMMXg1VVW9dfVcmFkDW5x2wMIyXAKz35jc6ERzhVj-LICUv8C10dzr7SWbRUbTTOEJ16dsQjmQkfhHqOfAKsEQiYD0cIWnSkESWk60FaLwN95WQNbvzU2GO-hGzNxI8t_5ns59Ydx8w/s1600/bluesmirf.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1NMMXg1VVW9dfVcmFkDW5x2wMIyXAKz35jc6ERzhVj-LICUv8C10dzr7SWbRUbTTOEJ16dsQjmQkfhHqOfAKsEQiYD0cIWnSkESWk60FaLwN95WQNbvzU2GO-hGzNxI8t_5ns59Ydx8w/s1600/bluesmirf.jpg" /></a></div>
<span style="color: #333333;"><b>2. Connect the bluetooth device to the microcontroller</b></span><br />
<span style="color: #333333;">To connect the bluetooth device, you
will need to find the Rx and Tx pins on your microcontroller. Make sure
that you cross the wires by connecting the Rx pin from your bluetooth
device to the Tx pin on the microcontroller, and the Tx pin from your
bluetooth device to the Rx pin on the microcontroller. You will want to
look in your datasheet to make sure you are using the right pins. If
you are using an Arduino, the diagram below may be helpful.</span><br />
<div style="text-align: center;">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-gFO4lZ4FbWlKGXBpTNxBr7zWDB10fWKoXHXssBNPOBcmAFtqAxOsMRM8qE2wByGQPq1wWz8gBh6v916J0nsQEdgTgJxOf5yPFCsJLHB-nXF_1EOO4iqifOvK8ui2pVwADPrW_6A7PkU/s1600/arduino_pinmap.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="260" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-gFO4lZ4FbWlKGXBpTNxBr7zWDB10fWKoXHXssBNPOBcmAFtqAxOsMRM8qE2wByGQPq1wWz8gBh6v916J0nsQEdgTgJxOf5yPFCsJLHB-nXF_1EOO4iqifOvK8ui2pVwADPrW_6A7PkU/s400/arduino_pinmap.png" width="400" /></a></div>
</div>
<span style="color: #333333;"><b>3. Configuring the Bluetooth Device</b></span><br />
<span style="color: #333333;">To configure the bluetooth device from a
computer, it is helpful to have a USB to serial breakout board. I use
the following from </span><a href="http://www.sparkfun.com/products/718"><span style="color: blue;">Sparkfun</span></a><span style="color: #333333;">:</span><br />
<div style="text-align: center;">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1rzBunDgc3fINQJCsxeW3xQp84gS8DV9IM0goq6D1MFdkXIGBlnECkqeurOh5Gpuznp14gEEG699Fr6i2a1eFVdWaaC-OcuBMgEq8gI-0JZygHcE0KfsYM-TeztSsaIhtqrg7kjzO-OE/s1600/usbtoserial.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh1rzBunDgc3fINQJCsxeW3xQp84gS8DV9IM0goq6D1MFdkXIGBlnECkqeurOh5Gpuznp14gEEG699Fr6i2a1eFVdWaaC-OcuBMgEq8gI-0JZygHcE0KfsYM-TeztSsaIhtqrg7kjzO-OE/s1600/usbtoserial.jpg" /></a></div>
</div>
<span style="color: #333333;">The
simplest way to hook this up to the bluetooth modem is by using the 4
pins located along the front. Make sure you cross the Tx and Rx wires.
The board above has a 3.3v pin that is powered via the USB when plugged
into the computer. The BlueSmirf above can also operate on 3.3v, so
powering the BlueSmirf is as easy as running a wire from the 3.3v output
of the USB device to the BlueSmirf. Also, make sure you run a wire
from the ground pin of the USB device to the BlueSmirf to give them a
common ground.</span><br />
<span style="color: #333333;">Now that everything is connected you can use a program such as Hyperterminal or <a href="http://www.ayera.com/teraterm/"><span style="color: blue;">Tera Term</span></a>
to communicate with the bluetooth modem. HyperTerminal may already be
installed on your computer if you are using Win XP. Whichever
application you are using, create a new connection. Make sure to select
Serial Port and the desired COM port. If you do not know which COM
port to use, you should be able to find it by looking in the device
manager. Mine says USB to Serial Port (COM3). You also need to
configure the serial port connection to use the corect baud rate.
Remember, the default baud rate of the BlueSmirf is 115200. If you are
using a different bluetooth device you will want to check your data
sheet to determine what the default baud rate is.</span><br />
<span style="color: #333333;"><b><i>The following instructions
are specific to the BlueSmirf. If you have a different bluetooth device
you will want to refer to your datasheet.</i></b></span><br />
<span style="color: #333333;"><i></i>Now that everything is
configured, type $$$ in the prompt. If everything is wired up
correctly, you will received a response of CMD. If you are using the
BlueSmirf, the status LED will start blinking rapidly. Now type D and
press enter. This will display the current configuration settings.</span><br />
<div style="text-align: center;">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEig-8Tp-p-DnZN45EJOVvPWxuyKfgSDJ0bc-ML4nCNFQbx0lMrBZpo5yMT1HEZSyg-dGYPsE6XKf-Xq-CTCUVCJViWWEVyo5XHmS1x_6s2tBgXDLLL0svJWbwKpiLhCbrbcG1GY10pmZWE/s1600/tera-term-default.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="301" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEig-8Tp-p-DnZN45EJOVvPWxuyKfgSDJ0bc-ML4nCNFQbx0lMrBZpo5yMT1HEZSyg-dGYPsE6XKf-Xq-CTCUVCJViWWEVyo5XHmS1x_6s2tBgXDLLL0svJWbwKpiLhCbrbcG1GY10pmZWE/s400/tera-term-default.png" width="400" /></a></div>
</div>
<span style="color: #333333;">If
you want to change the baud rate (to 9600 for example) type SN,96 and
press enter. You should receive a response of AOK which signifies that
the change was successful. Again, type D to see the settings and verify
that the baud rate is now 9600.</span><br />
<div style="text-align: center;">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3BFKrMUZO2RU6Dy9PgI4CsnbN7vBHrGjs0cl1bQXK7fCIm9I9cSmuA-Hsaerw8jYmnaz9kdoBokdsg8QL-CPGPt1-0DNFqlT0I60vbDZ_tgFOc5ujgZCFn2LV7U1kQcmM491CbM8PMPg/s1600/tera-term-baud-change.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3BFKrMUZO2RU6Dy9PgI4CsnbN7vBHrGjs0cl1bQXK7fCIm9I9cSmuA-Hsaerw8jYmnaz9kdoBokdsg8QL-CPGPt1-0DNFqlT0I60vbDZ_tgFOc5ujgZCFn2LV7U1kQcmM491CbM8PMPg/s400/tera-term-baud-change.png" width="343" /></a></div>
</div>
<span style="color: #333333;">Once
you have completed the change, type — to exit command mode and
terminate the connection. If you desire to make additional changes to
the configuration that I have not covered here, you should be able to
find detailed commands for the bluetooth device that you are using in
the documentation. For the BlueSmirf you can look </span><a href="http://www.sparkfun.com/datasheets/Wireless/Bluetooth/rn-bluetooth-um.pdf"><span style="color: blue;">here</span></a><span style="color: #333333;">.</span><br />
<span style="color: #333333;"><b>4. Writing code for the microcontroller</b></span><br />
<span style="color: #333333;">Depending on the microcontoller you are
using, this may or may not be a daunting task. You will want to refer
to your data sheet for specifics on how to set this up for your
microcontoller. One thing to remember is that you must use the baud
rate that your device is configured to use.</span><br />
<span style="color: #333333;">Use the settings you have configured
above to initialize the serial driver on your microcontroller. If you
are using an Arduino, this is as simple as writing <i>Serial.begin(baudRate);</i> in your setup function.</span><br />
<span style="color: #333333;">That’s it for Part 1. At this point
you should have a bluetooth device connected to your microcontroller and
be able to read/write to it using a USB to serial breakout board such
as the one I discussed above. In Part 2 I will discuss how to interface
this bluetooth device with an Android phone. Hopefully the information
above has been helpful, let me know if you have any questions.</span><br />
<br />
<div style="text-align: right;">
<span style="color: #333333;"><b>By ryandebenham.com</b> </span></div>
</div>1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.com0tag:blogger.com,1999:blog-5150593672190631200.post-24293085447306341622012-05-08T18:07:00.000-07:002012-05-08T18:07:29.193-07:00Open source Linux tablet showcases KDE Plasma Active technology<div dir="ltr" style="text-align: left;" trbidi="on">
<span class="txt"><strong>Members of the KDE Plasma Active community
announced an open source tablet platform that runs the mobile-oriented
version of KDE's Plasma UI layer on a MeeGo Linux-based "Mer" operating
system. The seven-inch "Spark" tablet features a 1GHz AMLogic ARM
Cortex-A9 processor with a Mali-400 GPU, offers 512MB of RAM, 4GB of
internal storage, an SD slot, and a projected price of about 200 Euros
($262).</strong><br /><br />The Spark was announced with fairly minimal
detail by KDE Plasma Active team member Aaron Seigo -- who has been on
loan from the newly open source <a href="http://www.linuxfordevices.com/c/a/News/Qt-goes-open-source/" rel="nofollow"><u>Qt Development Framework</u></a> project to work on <a href="http://plasma-active.org/" rel="nofollow" target="new"><u>KDE Plasma Active</u></a>.
The latter is the KDE community's touch-friendly, mobile device version
of the KDE desktop environment. (Long the leading competitor to GNOME
on Linux desktops, KDE was upgraded last week <a href="http://www.linuxfordevices.com/c/a/News/KDE-48-ships/" rel="nofollow"><u>version 4.8</u></a>.)</span><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlt1ssrMVqn8VsSP5ySvbNIvoTtrlEq6hYJKe1QLVCS9zbKnC1Hoj8cjxeGpl1Q_KDsW7Z9eikn-gZFWzecpXRo089qZpl8fchVQaJ5HhHfYrfi1NgE_N0oPZKb9qV8_ZY0TRFo2Jp7z0/s1600/kde_plasmactive.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="257" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhlt1ssrMVqn8VsSP5ySvbNIvoTtrlEq6hYJKe1QLVCS9zbKnC1Hoj8cjxeGpl1Q_KDsW7Z9eikn-gZFWzecpXRo089qZpl8fchVQaJ5HhHfYrfi1NgE_N0oPZKb9qV8_ZY0TRFo2Jp7z0/s400/kde_plasmactive.jpg" width="400" /></a></div>
<div style="text-align: center;">
<span class="txt"> </span><span class="txt"><strong>KDE Plasma Active 2</strong></span></div>
<div style="text-align: left;">
<span class="txt">Like Michael Arrington's ill-fated <a href="http://www.linuxfordevices.com/c/a/News/Linux-tablet-emerges-from-blogosphere/" rel="nofollow"><u>CrunchPad</u></a>, -- eventually reborn as Fusion Garage's commercial JooJoo tablet, the forerunner of the <a href="http://www.linuxfordevices.com/c/a/News/Fusion-Garage-Grid-OS-plus-Grid10-and-Grid4/" rel="nofollow"><u>Grid-10</u></a>
-- the Spark is billed as an entirely independent, open source Linux
tablet platform. In his blog announcement, Seigo notes that "There's no
walled garden to get locked into or which can be taken away."
</span></div>
This is an apparent reference to Amazon.com, which has been earning
the ire of the open source community over its locked-down version of
Android within the Kindle Fire tablet. <a href="http://www.eweek.com/c/a/Desktops-and-Notebooks/Amazon-Kindle-Fire-Hijacks-Android-Tablet-Market-722454/" rel="nofollow" target="new"><u>(Flurry just released a report claiming</u></a> the Fire has already eclipsed the entire installed base of the Samsung Galaxy Tab.) <br />
Like the Kindle Fire, the Spark is a seven-inch capacitive tablet
running on a Cortex-A9 processor. However, instead of a dual-core
processor, the Spark offers Amlogic's single-core <a href="http://www.linuxfordevices.com/c/a/News/Amlogic-AML8726M/" rel="nofollow"><u>AML8726-M</u></a>.
The 1GHz system on chip (SoC) includes a Mali-400 graphics processing
unit (GPU) and full 1080p video decoding, as detailed on this <a href="http://www.amlogic.com/product02.htm" rel="nofollow" target="new"><u>Amlogic AML8726-M product page</u></a>. <br />
Additional Spark features include 512MB of RAM, 4GB of internal
storage, and microSD expansion, according to Seigo. In addition, the
image shown above appears to indicate an HDMI port and dual mini-USB
host ports. No manufacturer for the device was listed. <br />
<strong>KDE Plasma Active 2</strong>
The hardware is secondary, however, to Spark's main focus:
showcasing KDE Plasma Active. Intended as a fast embedded UX (user
experience)
platform with minimal memory requirements, KDE Plasma Active is designed
for tablets, smartphones, and other touch-enabled devices
such as set-top boxes, smart TVs, home automation equipment, or
in-vehicle infotainment (IVI), says the project. <br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgqcRrRJfPi4lTovuehQqcTpkh_eFdDJdmF6kMbXxHjIA6vIQBYbkUacrNsT0IVnJvJxFsTd5I2F1H8u8IGMiVhq6wqBWsZKlrC426WSzoSbKmyfsu_rdWnXYoAp79bVrZ22SJAbYOG2vA/s1600/spark_tablet.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="212" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgqcRrRJfPi4lTovuehQqcTpkh_eFdDJdmF6kMbXxHjIA6vIQBYbkUacrNsT0IVnJvJxFsTd5I2F1H8u8IGMiVhq6wqBWsZKlrC426WSzoSbKmyfsu_rdWnXYoAp79bVrZ22SJAbYOG2vA/s400/spark_tablet.jpg" width="400" /></a></div>
<span class="txt"> <span class="txt"><strong>Spark tablet</strong></span></span><span class="txt"></span><span class="txt"><span class="txt"></span><br />
The stack is notable for featuring an interface
that adapts as users change KDE Activities, says the project. Additional
features are said to include: a Peek&Launch bar to select
applications or switch between them; touch-enabled apps and widgets; and
a "Share-Like-Connect" function that "molds your computer to your
preferences."
<br />
The KDE Plasma Active project is a collaboration between the KDE community, as well as development firm <a href="http://basyskom.com/" rel="nofollow" target="new"><u>Basyskom</u></a> and <a href="http://download.open-slx.com/balsam/professional/distribution/plasma-active/12.1/" rel="nofollow" target="new"><u>Open-slx GmbH</u></a>. As noted, Qt, whose development framework underlies the Spark platform, is also a contributor to the Spark tablet effort.<br />
<strong>MeeGo spin-off Mer involved in Spark project</strong><br />
Also collaborating on the Spark project is <a href="http://www.merproject.org/" rel="nofollow" target="new"><u>the Mer project</u></a> -- a fork of the fading MeeGo project that was announced in October as an alternative to the MeeGo-based, Samsung-backed <a href="http://www.linuxfordevices.com/c/a/News/Samsung-tips-Tizen-and-Bada-merger-plans/" rel="nofollow"><u>Tizen project</u></a>. KDE Plasma Active runs on a foundation of either Mer, MeeGo, or Open-slx' Balsam Linux Professional 12.1.<br />
Compared to Tizen, which Samsung says it plans to eventually merge
with its Bada operating system, Mer appears to be a more independent,
community-driven effort. Like Tizen, Mer adds a strong HTML5 component,
but unlike Tizen, also retains the Qt framework. The Mer project says it
plans to collaborate and share code with the Tizen project.<br />
Seigo also notes that the Spark project is establishing partnerships
with the KDE-backed OwnCloud hosting services, as well as two other
KDE-related groupware efforts that will assist in "deployment support": <a href="http://www.kolab.org/" rel="nofollow" target="new"><u>Kolab</u></a> and <a href="http://userbase.kde.org/Kontact_Touch" rel="nofollow" target="new"><u>Kontact Touch</u></a>.
Seigo goes on to note there will be "exciting Qt/QML add-on apps for
download," referring to the Javascript-based QML (Qt
Meta-Object-Language), which is also incorporated in Mer. <br />
In addition, the Spark tablet will offer "Free Culture artifacts,"
including digital books from Project Gutenberg, as well as contents and
apps for purchase, writes Seigo.<br />
<strong>Availability</strong><br />
The Spark tablet will ship soon for about 200 Euros (as of this
moment, about $262), says Seigo, but more is expected to be revealed
Jan. 31 on the same <a href="http://aseigo.blogspot.com/2012/01/reveal.html" rel="nofollow" target="new"><u><em>Aseigo</em> blog</u></a> where the Spark was announced. </span><span class="txt"><strong></strong></span><br />
<span class="txt"><br />
<span class="txt"><strong><i> Source by linuxfordevices.com</i></strong></span></span><br /><span class="txt"><span class="txt"><strong></strong></span></span><span class="txt"><strong><br /></strong></span></div>1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.com0tag:blogger.com,1999:blog-5150593672190631200.post-47817619804159590742012-05-08T08:29:00.001-07:002012-05-08T08:29:29.388-07:00Using Android for Embedded Systems<div dir="ltr" style="text-align: left;" trbidi="on">
Android has gained an enviable market share in the mobile space and is gaining momentum in the tablet market space as well.<br />
From the time Android was bought by Google in 2005, the Open Handset
Alliance was announced in 2007, the first Android Smart Phone (T-Mobile
G1) in 2008 followed by the Android Market the same year, Android has
been making steady progress in the mobile space and has captured the
imagination of the mobile user.<br />
In 2011 Google Android made its first major/official deviation from
the mobile only approach by coming out with Honeycomb (Android 3.0) that
was custom made for the tablet devices. It was an image makeover of
sorts. The buzz that Android could potentially come out of its
mobile-only approach move on to dominate other verticals in the embedded
domain gained more noise and credibility with Google’s foray into the
tablet.<br />
As system integrators and product development partners of various product development companies, we at e-con Systems (<a href="http://www.e-consystems.com/">www.e-consystems.com</a>)
face questions from OEMs/Product Companiesabout the possibility of
using Android on their next embedded product. There is a consistent
effort inside e-con Systems to follow, study, experiment new
technologies like Android and consolidate the knowledge gathered to
answer such questions from our customers. We would be sharing this
knowledge and our views on the various questions regarding usage of
Android for non-mobile embedded systems through this Android Blog.<br />
In the first blog of this series we are discussing, “What are the
possible areas Android could move into and why we should track it”<br />
<h2>
Understanding Android and “Google
Android”</h2>
“Google Android” – Yes, Google Android is different from “Android”.
Though Android is open source and is under GPL2 and Apache license,
without the backing of Google it would have never become what it is
today. We are free to use the Android source code in our products (of
course abiding by the respective licenses it requires us to follow) but
the most attractive features of Android like the Android Market,
YouTube, Mail App, Maps and search integration come with the “<strong><em>blessing</em></strong>” of Google.<br />
So if you are a product OEM then you have to get in touch with Google
and discuss the licensing of the Google services and pass the
Compatibility Test Suite to gain access to the Google goodies in your
device. Well this is not as straight forward as it sounds and all of you
who had made products would appreciate the “effort” involved in
speaking with big companies like Google and the volume that is required
to have them take their time and work on our case.<br />
So you can use the Google Trademark and other goodies only with the
permission from Google. You can use the Android source code and build
your own device and sell it, but cannot use the Google services,
trademark, etc. Google does not guarantee anything on the source code
and they are all available as is under GPL2 (partly) and Apache (partly)<br />
That’s the difference between “Android” and “Google Android”<br />
<h2>
Google’s Android Strategy and why we should closely monitor it</h2>
Having known about the Google Android complexities, there are two
different strategies that you can follow as a product developer,
considering to use Android for your next product (Note: We are
discussing only non-mobile/tablet devices).<br />
<ol>
<li>Get Google’s “<strong><em>blessing</em></strong>” for the
development of your next product (Of course you should have a good
product and good volume to start with) and get the support along with
Google services, trademark, etc.</li>
<li>Develop the product from the Android open source and “invest” in
developing any missing chunk that is necessary to make your product.</li>
</ol>
Either of these 2 strategies (though opposite in nature) requires us
to follow Google’s Android direction closely. We are in need to know how
Google is planning to extend Android to non-mobile devices.<br />
In the first strategy, if we need to get Google’s nod for our
product, the product vertical should be in the roadmap of Google at some
point. If we are not, there is a high possibility that Google may not
be ready to support our product idea with Android. You can find examples
of this later in the blog..<br />
In the second strategy, if you are going to invest your money to
create something new with Android for your next device, you should be
aware of Google’s plan as you don’t want them to come your way with
their guns blazing and make a void of your investment. For e.g., imagine
that you had spent a year or so developing a Tablet friendly version
with Android 2.2 and you were planning a release on May 2011. BOOM !!
Google comes out with Honeycomb which would be widely accepted because
of obvious reasons and kills your tablet optimized Android.<br />
So it pays to understand what Google is planning with Android and
guess its direction. That’s just what we did and we are presenting that
here. Our approach would be to take a market segment or a particular
type of product and analyze Google’s plan for that market. Also we would
suggest what approach can be taken if you are considering to build a
device for that market and want to use Android.<br />
<h2>
Embedded Systems – Verticals and Markets</h2>
Before we go into Google’s Android Strategy in detail, let’s take up
some time to identify the various embedded systems verticals. Each
vertical would have a market, requirements, sales strategy and revenue
on its own. The pictorial representation below shows the various
embedded verticals and the categories them into broad areas like
Communication, Consumer, Industrial & Mission Critical.<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2RCvwhc7XnN4ZYmj3pn0QgFLlSiM6kvQdI7puXIv189coO-BLfA4OzR7coLWsT33fkgAX5TbMl_hV2L8fPNunOE7kWalIXxL9b4_KUJ8r6OnTnOWehb8I-nhyphenhyphen7CmvMQbAhREq1DgYzIo/s1600/Google-Android.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="371" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh2RCvwhc7XnN4ZYmj3pn0QgFLlSiM6kvQdI7puXIv189coO-BLfA4OzR7coLWsT33fkgAX5TbMl_hV2L8fPNunOE7kWalIXxL9b4_KUJ8r6OnTnOWehb8I-nhyphenhyphen7CmvMQbAhREq1DgYzIo/s400/Google-Android.jpg" width="400" /></a></div>
<div style="text-align: center;">
Figure 1: Embedded Systems Verticals</div>
<div style="text-align: left;">
There is a thin line of difference between
some of these differentiations. So there is a scope for debate as to
what would fall under what (and that’s how the embedded space has grown
in the last 10 years). Mobile Internet Devices (MIDs) and Personal Media
Players (PMP) are slowly merging into the tablet and the smart phone.
We may see no more PMPs and MIDS coming out in some time. The embedded
space is pacing so fast that product verticals get created and killed in
no time.</div>
<div style="text-align: left;">
I would use the verticals indicated above to discuss Android’s emergence into each one of them.</div>
First let’s discount the areas where Android is not going to be used either by Google or by any other 3<sup>rd</sup>
Party. Most of the devices in the Communications side like the routers,
firewalls, switches are going to be off limits for Android. Together
with these devices, any HEADLESS device may not require Android in the
first place. Most headless devices run Linux, Windows CE or VxWorks. So
we would not discuss about these devices any more in this series.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGI_vqJqOwbOsVSjLmKf8kifojBwdeqUOr_y6PJWwjJtKq8d7XFxw4oxSEL7xSCVbmEZnUk2mKTOCLY1V7a1W0LLonxWrUEUJuCPvbrJvfJrGwcWabC91WZJps2xt1n_zZtAbPliezGoE/s1600/Google-Android-1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="283" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGI_vqJqOwbOsVSjLmKf8kifojBwdeqUOr_y6PJWwjJtKq8d7XFxw4oxSEL7xSCVbmEZnUk2mKTOCLY1V7a1W0LLonxWrUEUJuCPvbrJvfJrGwcWabC91WZJps2xt1n_zZtAbPliezGoE/s400/Google-Android-1.jpg" width="400" /></a></div>
<div style="text-align: center;">
Figure 2:No Android for these devices</div>
<div style="text-align: left;">
Secondly let us consider the area where
Android is already prevalent with some devices and may spread with
minimum changes and fuss to other devices in the market<strong>. Consumer Electronics/Devices</strong>is
the next vertical/segment where we are going to analyze Android’s
influence. My next blog in the series would start addressing that
segment.</div>
<div style="text-align: left;">
<br /></div>
<div style="text-align: right;">
<b>Source by <a href="http://www.e-consystems.com/">www.e-consystems.com</a></b></div>
</div>1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.com0tag:blogger.com,1999:blog-5150593672190631200.post-67733269929744606792012-03-30T00:17:00.000-07:002012-03-30T00:17:40.046-07:00Use a PS3 Controller With Android Phones and Tablets<div dir="ltr" style="text-align: left;" trbidi="on">
When it comes to gaming on your Android smartphone, nothing can beat a physical controller.<br />
The slide out PlayStation controller that is built-in to the Sony Xperia Play was the highlight of the phone, delivering a much more enjoyable, and visible, gaming experience.<br />
If you don’t have the Xperia Play, but you want to be able to use a
controller on your Android smartphone, you need to check out this app
that lets you use your PlayStation 3 controller on your Android
smartphone or tablet.<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8_HoF6lR-xgZ9T2wpZNdkRqPGzyRkE6fmFeaOYBF1ErvVWgsfT3LO5w9UfNiptrlUHzhoajtC69ePn65oyx1_0Ghzgfnj6_oLVoAGX079FDIVLHB8MU0jBajQiK2RNvc5o8FL-_USe3s/s1600/Sony+Sixaxis+Wireless+Controller+for+PS3.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="210" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg8_HoF6lR-xgZ9T2wpZNdkRqPGzyRkE6fmFeaOYBF1ErvVWgsfT3LO5w9UfNiptrlUHzhoajtC69ePn65oyx1_0Ghzgfnj6_oLVoAGX079FDIVLHB8MU0jBajQiK2RNvc5o8FL-_USe3s/s320/Sony+Sixaxis+Wireless+Controller+for+PS3.jpg" width="320" /></a></div>
<br />
The app Sixaxis Controller
allows you to hook your PS3 controller up to your Android smartphone
wirelessly, so that you can game without covering up the screen. The App
is available in the Android Market for $1.65, which is a steal for what
it delivers.<br />
<br />
<strong>IMPORTANT:</strong> You must have root access to use this app.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGWABq_a-oqWkRs03KOt6vGj3aRxnRPtPh_nBLDDKg07wgqQibYYIW484DdHmmi7kOC_CMK4UFNMGIyGtaiq_HMc4k6VQR7jSn981DdYGpstZkKIs0lMCUb3Brvta93drMRdHfPNADikk/s1600/Sixaxis-Controller-app.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGWABq_a-oqWkRs03KOt6vGj3aRxnRPtPh_nBLDDKg07wgqQibYYIW484DdHmmi7kOC_CMK4UFNMGIyGtaiq_HMc4k6VQR7jSn981DdYGpstZkKIs0lMCUb3Brvta93drMRdHfPNADikk/s1600/Sixaxis-Controller-app.jpg" /></a></div>
The Sixaxis Controller app needs your computer and mini USB cable to
pair the controller to your phone, but after that you can use up to four
controllers at once, without any wires.
<br />
Features include;<br />
<ul>
<li>Up to four Sixaxis and DualShock 3 controllers supported at once</li>
<li>All 17 buttons on the controller can be mapped to any key press in Android</li>
<li>Analog sticks emulated as digital key presses</li>
</ul>
Before you buy the app, we suggest that you run the free Sixaxis comaptibility checker
app to make sure your phone is supported. Device support seems hit or
miss, but there are reports of it working with the Xoom, Galaxy Tab and
the ThunderBolt.<br />
The controller will work with many apps and games, including popular emulators that can be found for Android devices.<br />
<br />
Hopefully we’ll see built in support for some type of gamepad in the
near future. I know it would make me much more likely to play games on
the Android platform. <br />
<br />
</div>1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.com0tag:blogger.com,1999:blog-5150593672190631200.post-33927349346099264332012-03-29T09:22:00.000-07:002012-03-29T09:22:12.714-07:00Kernel of Android<div dir="ltr" style="text-align: left;" trbidi="on">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBfKtG6A7nzrxi74axcvOfq_M_4C6F-G0Fh4os-sdlLOvLoV-d8elq0lo2pVsrLL_3uzSTX1XhScy_Wd-2u7MPUgmoOrn0U23ZTCt5DI4E814JLlRyvPkbS3iqSvQnV0qXgpyo5C2VZTA/s1600/linux.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="190" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBfKtG6A7nzrxi74axcvOfq_M_4C6F-G0Fh4os-sdlLOvLoV-d8elq0lo2pVsrLL_3uzSTX1XhScy_Wd-2u7MPUgmoOrn0U23ZTCt5DI4E814JLlRyvPkbS3iqSvQnV0qXgpyo5C2VZTA/s320/linux.jpg" width="320" /></a></div>
<br />
<br />
<div class="rteleft">
Android devices use the Linux kernel, but it's not
the exact same kernel other Linux-based operating systems use. There's a
lot of Android specific code built in, and Google's Android kernel
maintainers have their work cut out for them. OEMs have to contribute
as well, because they need to develop hardware drivers for the parts
they're using for the kernel version they're using. This is why it
takes a while for independent Android developers and hackers to port new
versions to older devices and get everything working. Drivers written
to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich
kernel. And that's important, because one of the kernel's main
functions is to control the hardware. It's a whole lot of source code,
with more options while building it than you can imagine, but in the end
it's just the intermediary between the hardware and the software.</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZOUnXM5FWjOil8NIhtd1IaKb51rcyErx-AaHYnwUJD0JBIcUnVN0rBteQRGtfh9dPgc_MirkN3nCAYH86wNCe4x7JLFoT59rzD82PagTkby2K9_CBS__e3_6Ppz33gbT8DOqzj_ywP0w/s1600/kernel.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZOUnXM5FWjOil8NIhtd1IaKb51rcyErx-AaHYnwUJD0JBIcUnVN0rBteQRGtfh9dPgc_MirkN3nCAYH86wNCe4x7JLFoT59rzD82PagTkby2K9_CBS__e3_6Ppz33gbT8DOqzj_ywP0w/s320/kernel.jpg" width="320" /></a></div>
<div class="rteleft">
<br /></div>
<div class="rteleft">
When software needs the hardware to do anything, it sends a request to the kernel. And when we say <em>anything</em>, we mean <em>anything</em>.
From the brightness of the screen, to the volume level, to initiating a
call through the radio, even what's drawn on the display is ultimately
controlled by the kernel. For example -- when you tap the search button
on your phone, you tell the software to open the search application.
What happens is that you touched a certain point on the digitizer,
which tells the software that you've touched the screen at those
coordinates. The software knows that when that particular spot is
touched, the search dialog is supposed to open. The kernel is what
tells the digitizer to look (or listen, events are "listened" for) for
touches, helps figure out where you touched, and tells the system you
touched it. In turn, when the system receives a touch event at a
specific point from the kernel (through the driver) it knows what to
draw on your screen. Both the hardware and the software communicate
both ways with the kernel, and that's how your phone knows when to do
something. Input from one side is sent as output to the other, whether
it's you playing Angry Birds, or connecting to your car's Bluetooth. </div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRQnPlTMeHoPODYVwOeP9ZaSa01iTY720usG27QPRc8cMFvFi3rGwbD8Y5kETQImGNPh8PAaeuN4hYZrjGuoiqfEHz1cLjtw2a_uRdeQG3FDVt2RmtP8HCun0M3x7xUvuDwzaV55MaHko/s1600/android.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhRQnPlTMeHoPODYVwOeP9ZaSa01iTY720usG27QPRc8cMFvFi3rGwbD8Y5kETQImGNPh8PAaeuN4hYZrjGuoiqfEHz1cLjtw2a_uRdeQG3FDVt2RmtP8HCun0M3x7xUvuDwzaV55MaHko/s1600/android.jpg" /></a></div>
<div class="rteleft">
<br /></div>
<div class="rteleft">
It sounds complicated, and it is. But it's also
pretty standard computer logic -- there's an action of some sort
generated for every event. Without the kernel to accept and send
information, developers would have to write code for every single event
for every single piece of hardware in your device. With the kernel, all
they have to do is communicate with it through the Android system
API's, and hardware developers only have to make the device hardware
communicate with the kernel. The good thing is that you don't need to
know exactly how or why the kernel does what it does, just understanding
that it's the go-between from software to hardware gives you a pretty
good grasp of what's happening under the glass. Sort of gives a whole
new outlook towards those fellows who stay up all night to work on
kernels for your phone, doesn't it?</div>
</div>1982http://www.blogger.com/profile/00187370909316551287noreply@blogger.com0