<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:itunes="http://www.itunes.com/DTDs/Podcast-1.0.dtd">
  <channel>
    <title>Android Zaurus</title>
    <link>https://androidzaurus.seesaa.net/</link>
    <description>ザウルスをAndroidにしちゃうよ。androidzaurus@yahoo.co.jp&amp;nbsp;|&amp;nbsp;日本語な別館＠はてな</description>
    <language>ja</language>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <itunes:subtitle></itunes:subtitle>
    <itunes:summary>ザウルスをAndroidにしちゃうよ。 androidzaurus@yahoo.co.jp&amp;nbsp;|&amp;nbsp;日本語な別館＠はてな</itunes:summary>
    <itunes:keywords>Google, Android, Zaurus, Linux, リナザウ, リナックスザウルス, グーグル, アンドロイド</itunes:keywords>
    
    <itunes:author>安藤恐竜</itunes:author>
    <itunes:owner>    
       <itunes:name></itunes:name>
       <itunes:email></itunes:email>
    </itunes:owner>
        <itunes:explicit>no</itunes:explicit>
        <item>
      <link>https://androidzaurus.seesaa.net/article/135889863.html</link>
      <title>NetWalker x Eclair - Bootable Image</title>
      <pubDate>Thu, 17 Dec 2009 17:19:50 +0900</pubDate>
            <description>Though few will be interested in, here is a binary set of Android 2.0 (Eclair) system for NetWalker (Sharp PC-Z1) o http://drop.io/eclairwalker091217/and followed by How-To. A patch set is available on my github but they are for donut. I&#39;ll..</description>
            <itunes:summary><![CDATA[
Though few will be interested in, here is a binary set of Android 2.0 (Eclair) system for NetWalker (Sharp PC-Z1)
 o <a href="http://drop.io/eclairwalker091217/" target="_blank">http://drop.io/eclairwalker091217/</a>
and followed by How-To. A patch set is available on <a href="http://github.com/androidzaurus/droidwalker" target="_blank">my github</a> but they are for donut. I'll make Eclair version available some time later.

1) Recovery SD
In a terminal on NetWalker, run following commands to create a bootable SD card using recovery system image.$ wget http://mit.sharp.co.jp/os.tar.bz2
$ sudo umount /media/disk
$ sudo fdisk /dev/mmcblk0
 -&gt; claim at least 2GB for Linux
$ sudo mkfs.ext3 /dev/mmcblk0p1
$ sudo mount -t ext3 /dev/mmcblk0p1 /mnt
$ sudo tar jxvpf os.tar.bz2 -C /mnt && sync
$ sudo mv /mnt/etc/rc2.d/S01upfirm /mnt/etc/rc2.d/~S01upfirm
2) Copy Eclair system files and kernel
Continue to install Eclair and kernel. First download eclairwalker.tar.gz from <a href="http://drop.io/eclairwalker091217/" target="_blank">http://drop.io/eclairwalker091217/</a> with Firefox on NetWalker.
 o size 32,115,123
 o md5sum df72d1f48e3d15c4ac93df9a20fb5adf$ mkdir -p /mnt/android/eclair
$ cd /mnt/android
$ tar zxvpf ~/Desktop/eclairwalker.tar.gz
$ sudo mv /mnt/boot/boot.conf /mnt/boot/recovery.boot.conf
$ sudo cp zImage boot.conf /mnt/boot
$ tar zxvpf eclair.tar.gz -C eclair
$ sudo mkdir -p /mnt/lib/modules/2.6.28.10-android/kernel
$ sudo tar zxvpf ko.tar.gz -C /mnt/lib/modules/2.6.28.10-android/kernel
$ sync
$ sudo poweroff
3) Boot Android
Booting from SD is a bit tricky.1) Press and hold both mouse buttons next to the power switch.
2) Press the power switch and hold for a few seconds.
3) Keep pressing both mouse buttons until Tux the Penguin shows up.
4) Login as root without password.
You can play with a console. First thing to do is depmod.
# depmod -a
Now is the time to boot Android by a familliar chroot commnad.
# chroot /android/eclair /init & 
4) Tips
Key assignment.FunctionKey AssignOKF5, Mouse LeftMenuF1, Home IconBackESC, Back Space, Mouse RightEndF4, Star Icon
Don't forget to change screen off timeout in Settings otherwise you end up loosing control in a few seconds. I'll recommend also set end key behavior to "Go Home" with Spare Parts.

To shutdown, press and hold F4 until a shutdown dialog comes up, then hit F5 twice.

5) Known issues
A lot of kown issues like,No WiFi.
No Sound.
No SD storage.
Just a proof of concept, as usual. Any contributions are always welcome.

Cheers,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Though few will be interested in, here is a binary set of Android 2.0 (Eclair) system for NetWalker (Sharp PC-Z1)<br /> o <a href="http://drop.io/eclairwalker091217/" target="_blank">http://drop.io/eclairwalker091217/</a><br />and followed by How-To. A patch set is available on <a href="http://github.com/androidzaurus/droidwalker" target="_blank">my github</a> but they are for donut. I'll make Eclair version available some time later.<br /><br /><strong>1) Recovery SD</strong><br />In a terminal on NetWalker, run following commands to create a bootable SD card using recovery system image.<blockquote>$ wget http://mit.sharp.co.jp/os.tar.bz2<br />$ sudo umount /media/disk<br />$ sudo fdisk /dev/mmcblk0<br /> -> claim at least 2GB for Linux<br />$ sudo mkfs.ext3 /dev/mmcblk0p1<br />$ sudo mount -t ext3 /dev/mmcblk0p1 /mnt<br />$ sudo tar jxvpf os.tar.bz2 -C /mnt && sync<br />$ sudo mv /mnt/etc/rc2.d/S01upfirm /mnt/etc/rc2.d/~S01upfirm</blockquote><br /><strong>2) Copy Eclair system files and kernel</strong><br />Continue to install Eclair and kernel. First download eclairwalker.tar.gz from <a href="http://drop.io/eclairwalker091217/" target="_blank">http://drop.io/eclairwalker091217/</a> with Firefox on NetWalker.<br /> o size 32,115,123<br /> o md5sum df72d1f48e3d15c4ac93df9a20fb5adf<blockquote>$ mkdir -p /mnt/android/eclair<br />$ cd /mnt/android<br />$ tar zxvpf ~/Desktop/eclairwalker.tar.gz<br />$ sudo mv /mnt/boot/boot.conf /mnt/boot/recovery.boot.conf<br />$ sudo cp zImage boot.conf /mnt/boot<br />$ tar zxvpf eclair.tar.gz -C eclair<br />$ sudo mkdir -p /mnt/lib/modules/2.6.28.10-android/kernel<br />$ sudo tar zxvpf ko.tar.gz -C /mnt/lib/modules/2.6.28.10-android/kernel<br />$ sync<br />$ sudo poweroff</blockquote><br /><strong>3) Boot Android</strong><br />Booting from SD is a bit tricky.<blockquote>1) Press and hold both mouse buttons next to the power switch.<br />2) Press the power switch and hold for a few seconds.<br />3) Keep pressing both mouse buttons until Tux the Penguin shows up.<br />4) Login as root without password.</blockquote><br />You can play with a console. First thing to do is depmod.<br /><blockquote># depmod -a</blockquote><br />Now is the time to boot Android by a familliar chroot commnad.<br /><blockquote># chroot /android/eclair /init & </blockquote><br /><strong>4) Tips</strong><br />Key assignment.<table border="1"><tr><td>Function</td><td>Key Assign</td></tr><tr><td>OK</td><td>F5, Mouse Left</td></tr><tr><td>Menu</td><td>F1, Home Icon</td></tr><tr><td>Back</td><td>ESC, Back Space, Mouse Right</td></tr><tr><td>End</td><td>F4, Star Icon</td></tr></table><br />Don't forget to change screen off timeout in Settings otherwise you end up loosing control in a few seconds. I'll recommend also set end key behavior to "Go Home" with Spare Parts.<br /><br />To shutdown, press and hold F4 until a shutdown dialog comes up, then hit F5 twice.<br /><br /><strong>5) Known issues</strong><br />A lot of kown issues like,<blockquote>No WiFi.<br />No Sound.<br />No SD storage.</blockquote><br />Just a proof of concept, as usual. Any contributions are always welcome.<br /><br />Cheers,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/135889863</guid>
                </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/130268081.html</link>
      <title>Android on NetWalker</title>
      <pubDate>Wed, 14 Oct 2009 20:09:07 +0900</pubDate>
            <description>I&#39;ve ported Android on to NetWalker, sort of. Required patch files can be downloaded from my github.This port is still very preliminary and unstable. Current status is just a proof of concept.NetWalker has a good boot loader that allows us ..</description>
            <itunes:summary><![CDATA[
<a href="http://androidzaurus.up.seesaa.net/image/fidandroidzaurus20091013194335jimage.jpg" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/fidandroidzaurus20091013194335jimage-thumbnail2.jpg" width="150" height="145" border="0" alt="fidandroidzaurus20091013194335jimage.jpg" /></a>

I've ported Android on to NetWalker, sort of. Required patch files can be downloaded from <a href="http://github.com/androidzaurus/droidwalker" target="_blank">my github</a>.

This port is still very preliminary and unstable. Current status is just a proof of concept.

NetWalker has a good boot loader that allows us boot from SD card. You can create your own roof file system by following steps.

1) Download os.tar.bz2 and zImage from http://mit.sharp.co.jp/
2) Unzip os.tar.bz2 to SD card formatted as ext2
3) Copy zImage to boot/ directory on SD card
4) Edit boot.conf in boot/ directory
&nbsp;&nbsp;&nbsp; - add console=tty1
&nbsp;&nbsp;&nbsp; - remove quiet
5) Power off
6) While pressing [Left] and [Right], press [Power]
7) Keep pressing [Left] and [Right] until kernel boot message printed.

Now you have a root console. Kernel can be replaced by just changing /boot/zImage. Kernel command options are configurable by /boot/boot.conf. What a heaven.

To boot Android on NetWalker, follow the instructions in README and build kernel and Android system. Then copy zImage to boot/ and Android system to SD card. Now the time to do a familiar chroot to Android system directory.

Cheers,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
<a href="http://androidzaurus.up.seesaa.net/image/fidandroidzaurus20091013194335jimage.jpg" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/fidandroidzaurus20091013194335jimage-thumbnail2.jpg" width="150" height="145" border="0" align="" alt="fidandroidzaurus20091013194335jimage.jpg" onclick="location.href = 'https://androidzaurus.seesaa.net/upload/detail/image/fidandroidzaurus20091013194335jimage-thumbnail2.jpg.html'; return false;" style="cursor:pointer;" /></a><br /><br />I've ported Android on to NetWalker, sort of. Required patch files can be downloaded from <a href="http://github.com/androidzaurus/droidwalker" target="_blank">my github</a>.<br /><br />This port is still very preliminary and unstable. Current status is just a proof of concept.<br /><br />NetWalker has a good boot loader that allows us boot from SD card. You can create your own roof file system by following steps.<br /><br />1) Download os.tar.bz2 and zImage from http://mit.sharp.co.jp/<br />2) Unzip os.tar.bz2 to SD card formatted as ext2<br />3) Copy zImage to boot/ directory on SD card<br />4) Edit boot.conf in boot/ directory<br />&nbsp;&nbsp;&nbsp; - add console=tty1<br />&nbsp;&nbsp;&nbsp; - remove quiet<br />5) Power off<br />6) While pressing [Left] and [Right], press [Power]<br />7) Keep pressing [Left] and [Right] until kernel boot message printed.<br /><br />Now you have a root console. Kernel can be replaced by just changing /boot/zImage. Kernel command options are configurable by /boot/boot.conf. What a heaven.<br /><br />To boot Android on NetWalker, follow the instructions in README and build kernel and Android system. Then copy zImage to boot/ and Android system to SD card. Now the time to do a familiar chroot to Android system directory.<br /><br />Cheers,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/130268081</guid>
            <enclosure url="https://androidzaurus.up.seesaa.net/image/fidandroidzaurus20091013194335jimage.jpg" length="47858" type="image/jpeg" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/fidandroidzaurus20091013194335jimage.jpg" length="47858" type="image/jpeg" />
                      </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/126695479.html</link>
      <title>Sharp NetWalker PC-Z1</title>
      <pubDate>Fri, 28 Aug 2009 22:02:41 +0900</pubDate>
            <description>I&#39;m really impressed by the news that Sharp comes back to Linux PDA market.o Sharp NetWalker PC-Z1 MID lands in Japan next monthAs far as I know, PC-Z1 will be a very first product which uses ARM Ubuntu for consumer market. And I have no do..</description>
            <itunes:summary><![CDATA[
I'm really impressed by the news that Sharp comes back to Linux PDA market.

o <a href="http://www.slashgear.com/sharp-netwalker-pc-z1-mid-lands-in-japan-next-month-2753969/" target="_blank">Sharp NetWalker PC-Z1 MID lands in Japan next month</a>

As far as I know, PC-Z1 will be a very first product which uses ARM Ubuntu for consumer market. And I have no doubt that it will be a good gadget to host Android.

But PC-Z1 reminds me HP200LX a lot more. fbterm + (emacs -nw | screen) with w3m for 10 hours could be a can't-live-without-gadget.

Anyway, I'm lucky living in Japan to have a chance to enjoy NetWalker first place. And welcome back, Sharp!
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
I'm really impressed by the news that Sharp comes back to Linux PDA market.<br /><br />o <a href="http://www.slashgear.com/sharp-netwalker-pc-z1-mid-lands-in-japan-next-month-2753969/" target="_blank">Sharp NetWalker PC-Z1 MID lands in Japan next month</a><br /><br />As far as I know, PC-Z1 will be a very first product which uses ARM Ubuntu for consumer market. And I have no doubt that it will be a good gadget to host Android.<br /><br />But PC-Z1 reminds me HP200LX a lot more. fbterm + (emacs -nw | screen) with w3m for 10 hours could be a can't-live-without-gadget.<br /><br />Anyway, I'm lucky living in Japan to have a chance to enjoy NetWalker first place. And welcome back, Sharp!<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/126695479</guid>
                </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/121920729.html</link>
      <title>Android Screen Monitor</title>
      <pubDate>Sun, 21 Jun 2009 10:42:28 +0900</pubDate>
            <description>Android Screen Monitor is a must-have application for Android developers.o http://www.adakoda.com/adakoda/android/asm/ASM transfers continuously screen captures from an attached Android device to your PC. It is very useful when you make a p..</description>
            <itunes:summary><![CDATA[
Android Screen Monitor is a must-have application for Android developers.

o <a href="http://www.adakoda.com/adakoda/android/asm/" target="_blank">http://www.adakoda.com/adakoda/android/asm/</a>

ASM transfers continuously screen captures from an attached Android device to your PC. It is very useful when you make a presentation using PC, projector and of course your Android device.

Because ASM leverages adbd functions, you may experience "lost connection" issue once in a while. If it happens, give an "adb kill-server" - "adb start-server" cycle as usual.

A tip for installation. If you don't set PATH to Android SDK, copy the ASM to sdk/tools directory.

Anyway, a big thank you to adakoda san for sharing this amazing software!

Cheers,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Android Screen Monitor is a must-have application for Android developers.<br /><br />o <a href="http://www.adakoda.com/adakoda/android/asm/" target="_blank">http://www.adakoda.com/adakoda/android/asm/</a><br /><br />ASM transfers continuously screen captures from an attached Android device to your PC. It is very useful when you make a presentation using PC, projector and of course your Android device.<br /><br />Because ASM leverages adbd functions, you may experience "lost connection" issue once in a while. If it happens, give an "adb kill-server" - "adb start-server" cycle as usual.<br /><br />A tip for installation. If you don't set PATH to Android SDK, copy the ASM to sdk/tools directory.<br /><br />Anyway, a big thank you to adakoda san for sharing this amazing software!<br /><br />Cheers,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/121920729</guid>
                </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/116995835.html</link>
      <title>Android 1.5 on Zaurus</title>
      <pubDate>Tue, 07 Apr 2009 10:32:41 +0900</pubDate>
            <description>In Android source code repository, cupcake (Android 1.5) has been merged to master branch. Current implementation of SystemServer.java throws exceptions and Android doesn&#39;t boot up properly.Quick hack. Let the system thinks battery is healt..</description>
            <itunes:summary><![CDATA[
In <a href="http://android.git.kernel.org/" target="_blank">Android source code repository</a>, cupcake (Android 1.5) has been merged to master branch. Current implementation of SystemServer.java throws exceptions and Android doesn't boot up properly.

Quick hack. Let the system thinks battery is healthy. Here's my patch.


<a href="http://androidzaurus.up.seesaa.net/image/git.diff.gz">git.diff.gz</a>

Cheers,

<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
In <a href="http://android.git.kernel.org/" target="_blank">Android source code repository</a>, cupcake (Android 1.5) has been merged to master branch. Current implementation of SystemServer.java throws exceptions and Android doesn't boot up properly.<br /><br />Quick hack. Let the system thinks battery is healthy. Here's my patch.<br /><br /><ul><li><br /><a href="http://androidzaurus.up.seesaa.net/image/git.diff.gz">git.diff.gz</a></li></ul><br /><br />Cheers,<br /><br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/116995835</guid>
            <enclosure url="https://androidzaurus.up.seesaa.net/image/git.diff.gz" length="1655" type="application/x-gzip" />
                      </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/111434080.html</link>
      <title>Bootchart on Android</title>
      <pubDate>Fri, 19 Dec 2008 09:43:08 +0900</pubDate>
            <description>I tried bootchart to see how Android boots up and how long each process takes.First, rebuild /init with bootchart enabled.$ cd mydroid$ export INIT_BOOTCHART=true$ make clean$ makeCopy it to Zaurus and setup environment as written in README..</description>
            <itunes:summary><![CDATA[
I tried bootchart to see how Android boots up and how long each process takes.

First, rebuild /init with bootchart enabled.$ cd mydroid
$ export INIT_BOOTCHART=true
$ make clean
$ make
Copy it to Zaurus and setup environment as written in README.BOOTCHART in system/core/init.$ scp out/target/product/generic/root/init root@zaurus:~/android-root/
$ ssh root@zaurus
# echo 1 &gt; android-root/data/bootchart
# echo 5 &gt; android-root/data/bootchart-stop
Make android-root/tmp directory and boot Android up.# mkdir android-root/tmp
# chmod 777 android-root/tmp
# chroot android-root /init
After shutting Android down, copy grab-bootchart.sh to the same directory as the adb tool.$ cp mydroid/system/core/init/grab-bootchart.sh mydroid/out/host/linux-x86/bin
$ cd mydroid/out/host/linux-x86/bin
In grab-bootchart.sh, adb is executed without path and I don't set PATH to adb, so simply modify the scrpit from "adb pull" to "./adb pull".

Boot Android up on Zaurus again, then run the script on the host PC.$ export ADBHOST=zaurus
$ ./adb kill-server
$ ./adb start-server
$ sudo ./grab-bootchart.sh
On Ubuntu 8.04, the visualizer can be installed by apt-get.$ sudo apt-get install bootchart
$ java -jar /usr/share/bootchart/bootchart.jar ./bootchart.tgz
The result, bootchart.png, looks like this.
<a href="http://androidzaurus.up.seesaa.net/image/bootchart.png" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/bootchart-thumbnail2.png" width="150" height="51" border="0" alt="bootchart.png" /></a>
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
I tried bootchart to see how Android boots up and how long each process takes.<br /><br />First, rebuild /init with bootchart enabled.<pre>$ cd mydroid<br />$ export INIT_BOOTCHART=true<br />$ make clean<br />$ make</pre><br />Copy it to Zaurus and setup environment as written in README.BOOTCHART in system/core/init.<pre>$ scp out/target/product/generic/root/init root@zaurus:~/android-root/<br />$ ssh root@zaurus<br /># echo 1 > android-root/data/bootchart<br /># echo 5 > android-root/data/bootchart-stop</pre><br />Make android-root/tmp directory and boot Android up.<pre># mkdir android-root/tmp<br /># chmod 777 android-root/tmp<br /># chroot android-root /init</pre><br />After shutting Android down, copy grab-bootchart.sh to the same directory as the adb tool.<pre>$ cp mydroid/system/core/init/grab-bootchart.sh mydroid/out/host/linux-x86/bin<br />$ cd mydroid/out/host/linux-x86/bin</pre><br />In grab-bootchart.sh, adb is executed without path and I don't set PATH to adb, so simply modify the scrpit from "adb pull" to "./adb pull".<br /><br />Boot Android up on Zaurus again, then run the script on the host PC.<pre>$ export ADBHOST=zaurus<br />$ ./adb kill-server<br />$ ./adb start-server<br />$ sudo ./grab-bootchart.sh</pre><br />On Ubuntu 8.04, the visualizer can be installed by apt-get.<pre>$ sudo apt-get install bootchart<br />$ java -jar /usr/share/bootchart/bootchart.jar ./bootchart.tgz</pre><br />The result, bootchart.png, looks like this.<br /><a href="http://androidzaurus.up.seesaa.net/image/bootchart.png" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/bootchart-thumbnail2.png" width="150" height="51" border="0" align="" alt="bootchart.png" onclick="location.href = 'https://androidzaurus.seesaa.net/upload/detail/image/bootchart-thumbnail2.png.html'; return false;" style="cursor:pointer;" /></a><br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/111434080</guid>
            <enclosure url="https://androidzaurus.up.seesaa.net/image/bootchart.png" length="173473" type="image/png" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/bootchart.png" length="173473" type="image/png" />
                      </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/108547690.html</link>
      <title>Porting Open Source Android to Zaurus</title>
      <pubDate>Fri, 24 Oct 2008 17:14:21 +0900</pubDate>
            <description>Big congratulations to Android team and even bigger thanks to make things happen.o Android is now Open SourceThere is only one final touch left for my project.I built Android framework from scratch as described in source.android.com and bri..</description>
            <itunes:summary><![CDATA[
Big congratulations to Android team and even bigger thanks to make things happen.

o <a href="http://android-developers.blogspot.com/2008/10/android-is-now-open-source.html" target="_blank">Android is now Open Source</a>

There is only one final touch left for my project.

I built Android framework from scratch as described in source.android.com and bring the image to my Zaurus. It works as expected with one exception.

I received SEGV everytime I type something on the keyboard. It is resolved by copy keyboard configuration files and change permission.# cd android-root/system/usr/keylayout
# cp qwerty.kl Spitz_Keyboard.kl
# chmod 666 *
# cd ../keychars
# cp qwerty.kcm.bin Spitz_Keyboard.kcm.bin
# chmod 666 *

By the way, T-Mobile G1 is unleashed with debuggerd enabled. It means you can debug your application running on G1. It is really sweet.
o <a href="http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware" target="_blank">Developing on Device Hardware - code.google.com</a>

I assume debugging over WLAN also works. If you have G1, this is worth to try, I guess.

From your PC installed Android SDK 1.0, $ export ADBHOST="G1 IP address connected through WLAN"
$ ./adb kill-server
$ ./adb start-server
$ ./adb devices
$ ./adb shellIf it successfully gives you a console, now  Eclipse environment should be able to talk to your phone.

Cheers,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Big congratulations to Android team and even bigger thanks to make things happen.<br /><br />o <a href="http://android-developers.blogspot.com/2008/10/android-is-now-open-source.html" target="_blank">Android is now Open Source</a><br /><br />There is only one final touch left for my project.<br /><br />I built Android framework from scratch as described in source.android.com and bring the image to my Zaurus. It works as expected with one exception.<br /><br />I received SEGV everytime I type something on the keyboard. It is resolved by copy keyboard configuration files and change permission.<blockquote># cd android-root/system/usr/keylayout<br /># cp qwerty.kl Spitz_Keyboard.kl<br /># chmod 666 *<br /># cd ../keychars<br /># cp qwerty.kcm.bin Spitz_Keyboard.kcm.bin<br /># chmod 666 *</blockquote><br /><br />By the way, T-Mobile G1 is unleashed with debuggerd enabled. It means you can debug your application running on G1. It is really sweet.<br />o <a href="http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware" target="_blank">Developing on Device Hardware - code.google.com</a><br /><br />I assume debugging over WLAN also works. If you have G1, this is worth to try, I guess.<br /><br />From your PC installed Android SDK 1.0, <blockquote>$ export ADBHOST="G1 IP address connected through WLAN"<br />$ ./adb kill-server<br />$ ./adb start-server<br />$ ./adb devices<br />$ ./adb shell</blockquote>If it successfully gives you a console, now  Eclipse environment should be able to talk to your phone.<br /><br />Cheers,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/108547690</guid>
                </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/107106587.html</link>
      <title>KeycodeChecker.apk for Android 1.0</title>
      <pubDate>Thu, 25 Sep 2008 09:22:15 +0900</pubDate>
            <description>Finally, Android 1.0 SDK has been released. The kernel is exactly same as Android 0.9. Just poring system image into my Zaurus, Android 1.0 works fine.I rebuild KeycodeChecker on 1.0 SDK.o KeycodeChecker-1.0-r1.zipJust in case, if anyone is..</description>
            <itunes:summary><![CDATA[
Finally, Android 1.0 SDK has been released. The kernel is exactly same as Android 0.9. Just poring system image into my Zaurus, Android 1.0 works fine.

I rebuild KeycodeChecker on 1.0 SDK.
o <a href="http://androidzaurus.up.seesaa.net/image/KeycodeChecker-1.0-r1.zip" target="_blank">KeycodeChecker-1.0-r1.zip</a>

Just in case, if anyone is looking for keylayout file working on Zaurus, here is the one.
o <a href="http://androidzaurus.up.seesaa.net/image/qwerty.kl.zip" target="_blank">qwerty.kl.zip</a>

One issue currently I'm working on. Landscape view and portrait view issue. Until SDK m5, Zaurus booted up in portrait view which is hardware buffer aligned. But with Android 0.9 and 1.0, Zaurus boots in landscape view. It has huge impact to performance. I used to run my RotateView.apk to make adjustment, but the APIs RotateView uses have gone. I'm looking for alternative API but still can not find.

Cheers,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Finally, Android 1.0 SDK has been released. The kernel is exactly same as Android 0.9. Just poring system image into my Zaurus, Android 1.0 works fine.<br /><br />I rebuild KeycodeChecker on 1.0 SDK.<br />o <a href="http://androidzaurus.up.seesaa.net/image/KeycodeChecker-1.0-r1.zip" target="_blank">KeycodeChecker-1.0-r1.zip</a><br /><br />Just in case, if anyone is looking for keylayout file working on Zaurus, here is the one.<br />o <a href="http://androidzaurus.up.seesaa.net/image/qwerty.kl.zip" target="_blank">qwerty.kl.zip</a><br /><br />One issue currently I'm working on. Landscape view and portrait view issue. Until SDK m5, Zaurus booted up in portrait view which is hardware buffer aligned. But with Android 0.9 and 1.0, Zaurus boots in landscape view. It has huge impact to performance. I used to run my RotateView.apk to make adjustment, but the APIs RotateView uses have gone. I'm looking for alternative API but still can not find.<br /><br />Cheers,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/107106587</guid>
            <enclosure url="https://androidzaurus.up.seesaa.net/image/KeycodeChecker-1.0-r1.zip" length="39315" type="application/x-zip" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/qwerty.kl.zip" length="651" type="application/x-zip" />
                      </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/106292204.html</link>
      <title>V8 on Angstrom Zaurus</title>
      <pubDate>Tue, 09 Sep 2008 17:18:51 +0900</pubDate>
            <description>Chrome shines! V8 rocks!I&#39;ve been using Chrome since release and love more and more. Chrome is maximized on my desktop all the time and I&#39;m crusing the Net with shortcut keys.Chrome on Android is rumored. And amazingly V8 the Javascript eng..</description>
            <itunes:summary><![CDATA[
Chrome shines! V8 rocks!

I've been using Chrome since release and love more and more. Chrome is maximized on my desktop all the time and I'm crusing the Net with shortcut keys.

Chrome on Android is rumored. And amazingly V8 the Javascript engine is already ported to ARM. I couldn't wait for Android Chrome, so tried to build V8 for Zaurus.

First of all, grab the source code.svn checkout http://v8.googlecode.com/svn/trunk/ v8I tried to cross compile by modifing scons scripts, but no luck. Next I tried to port scons itself to Angstrom but so many problems, then forgot about it.

Quick dirty hack. Batch build, I tried.

First dry run scons on PC to generate script file.$ scons -nQ toolchain=gcc arch=arm library=static os=linux sample=shell &gt; build.sh  2&gt;&1Copy it and add #!/bin/sh at the fist line, add executable permission and fire it.# ./build.sh
src/macro-assembler-arm.cc:66:2: error: #error "for thumb inter-working we require architecture v5t or above"It looks V8 is really ported to ARM. It is promissing. I modified build.sh adding; -march=armv5te -mtune=xscale to tell compile generate Armv5t binary. There is a little patch required to compile platform-linux.ccdiff -ur --exclude .o v8/src/platform-linux.cc v8-work/src/platform-linux.cc
--- v8/src/platform-linux.cc	2008-09-03 11:42:30.000000000 +0900
+++ v8y-work/src/platform-linux.cc	2008-09-07 11:02:35.226762251 +0900
@@ -567,8 +567,10 @@
     ucontext_t* ucontext = reinterpret_cast(context);
     mcontext_t& mcontext = ucontext-&gt;uc_mcontext;
 #if defined (__arm__) || defined(__thumb__)
-    sample.pc = mcontext.gregs[R15];
-    sample.sp = mcontext.gregs[R13];
+	// sample.pc = mcontext.gregs[R15];
+    // sample.sp = mcontext.gregs[R13];
+    sample.pc = mcontext.arm_pc;
+    sample.sp = mcontext.arm_sp;
 #else
     sample.pc = mcontext.gregs[REG_EIP];
     sample.sp = mcontext.gregs[REG_ESP];Another and final touch to build.sh is required to avoid JS2C script. Commnet out JS2C line and copy libraries.cc from PC. I guess this libraries.cc is platform independent, so just scons on PC and pull obj/relrease/libraries.cc to Zaurus.

Finally I got libv8.a and shell program# file shell
shell: ELF 32-bit LSB executable, ARM, version 1 (SYSV), for GNU/Linux 2.6.14,
dynamically linked (uses shared libs), not stripped

# ./shell 
V8 version 0.3.0
&gt; for (var n in function() { return this } () ) print(n) 
n
escape
unescape
decodeURI
decodeURIComponent
encodeURI
encodeURIComponent
load
quit
print
version
&gt; quit()I tried to run benchmark script in source tree but the program dies in out of memory.~/work/v8/benchmarks# ../shell run.js 

#
# Fatal error in CALL_HEAP_FUNCTION
# Allocation failed - process out of memory
#

Aborted

Conclusion. V8 does run on ARM. V8 on Android will be possible once source code becomes available.

Cheers,

<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Chrome shines! V8 rocks!<br /><br />I've been using Chrome since release and love more and more. Chrome is maximized on my desktop all the time and I'm crusing the Net with shortcut keys.<br /><br />Chrome on Android is rumored. And amazingly V8 the Javascript engine is already ported to ARM. I couldn't wait for Android Chrome, so tried to build V8 for Zaurus.<br /><br />First of all, grab the source code.<pre>svn checkout http://v8.googlecode.com/svn/trunk/ v8</pre>I tried to cross compile by modifing scons scripts, but no luck. Next I tried to port scons itself to Angstrom but so many problems, then forgot about it.<br /><br />Quick dirty hack. Batch build, I tried.<br /><br />First dry run scons on PC to generate script file.<pre>$ scons -nQ toolchain=gcc arch=arm library=static os=linux sample=shell > build.sh  2>&1</pre>Copy it and add #!/bin/sh at the fist line, add executable permission and fire it.<pre># ./build.sh<br />src/macro-assembler-arm.cc:66:2: error: #error "for thumb inter-working we require architecture v5t or above"</pre>It looks V8 is really ported to ARM. It is promissing. I modified build.sh adding;<blockquote> -march=armv5te -mtune=xscale</blockquote> to tell compile generate Armv5t binary. There is a little patch required to compile platform-linux.cc<blockquote>diff -ur --exclude .o v8/src/platform-linux.cc v8-work/src/platform-linux.cc<br />--- v8/src/platform-linux.cc	2008-09-03 11:42:30.000000000 +0900<br />+++ v8y-work/src/platform-linux.cc	2008-09-07 11:02:35.226762251 +0900<br />@@ -567,8 +567,10 @@<br />     ucontext_t* ucontext = reinterpret_cast<ucontext_t*>(context);<br />     mcontext_t& mcontext = ucontext->uc_mcontext;<br /> #if defined (__arm__) || defined(__thumb__)<br />-    sample.pc = mcontext.gregs[R15];<br />-    sample.sp = mcontext.gregs[R13];<br />+	// sample.pc = mcontext.gregs[R15];<br />+    // sample.sp = mcontext.gregs[R13];<br />+    sample.pc = mcontext.arm_pc;<br />+    sample.sp = mcontext.arm_sp;<br /> #else<br />     sample.pc = mcontext.gregs[REG_EIP];<br />     sample.sp = mcontext.gregs[REG_ESP];</blockquote>Another and final touch to build.sh is required to avoid JS2C script. Commnet out JS2C line and copy libraries.cc from PC. I guess this libraries.cc is platform independent, so just scons on PC and pull obj/relrease/libraries.cc to Zaurus.<br /><br />Finally I got libv8.a and shell program<pre># file shell<br />shell: ELF 32-bit LSB executable, ARM, version 1 (SYSV), for GNU/Linux 2.6.14,<br />dynamically linked (uses shared libs), not stripped<br /><br /># ./shell <br />V8 version 0.3.0<br />> for (var n in function() { return this } () ) print(n) <br />n<br />escape<br />unescape<br />decodeURI<br />decodeURIComponent<br />encodeURI<br />encodeURIComponent<br />load<br />quit<br />print<br />version<br />> quit()</pre>I tried to run benchmark script in source tree but the program dies in out of memory.<pre>~/work/v8/benchmarks# ../shell run.js <br /><br />#<br /># Fatal error in CALL_HEAP_FUNCTION<br /># Allocation failed - process out of memory<br />#<br /><br />Aborted<br /></pre><br />Conclusion. V8 does run on ARM. V8 on Android will be possible once source code becomes available.<br /><br />Cheers,<br /><br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/106292204</guid>
                </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/105551643.html</link>
      <title>double buffer patch of pxafb for linux-2.6.26</title>
      <pubDate>Thu, 28 Aug 2008 09:41:07 +0900</pubDate>
            <description>The latest Angstrom development environment gives me a nice linux 2.6.26 kernel but there is a drawback. The frame buffer driver degrades a bit. Overlay function and higher color depth support is gone.The source code of frame buffer driver ..</description>
            <itunes:summary><![CDATA[
The latest Angstrom development environment gives me a nice linux 2.6.26 kernel but there is a drawback. The frame buffer driver degrades a bit. Overlay function and higher color depth support is gone.

The source code of frame buffer driver in 2.6.23 version can not be compiled against 2.6.26 environment.

Based on the same strategy as 2.6.23 version, I wrote a small patch to handle double buffering and pan function for 2.6.26 version. Following is the patch file which is working fine for me.

o <a href="http://androidzaurus.up.seesaa.net/image/pxafb_doublebuffer.patch.bz2" target="_blank">pxafb_doublebuffer.patch.bz2</a>

The touchscreen driver is not working satisfactorily. Once I manage to make it work, I'll upload a pactch on this blog.

Cheers,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
The latest Angstrom development environment gives me a nice linux 2.6.26 kernel but there is a drawback. The frame buffer driver degrades a bit. Overlay function and higher color depth support is gone.<br /><br />The source code of frame buffer driver in 2.6.23 version can not be compiled against 2.6.26 environment.<br /><br />Based on the same strategy as 2.6.23 version, I wrote a small patch to handle double buffering and pan function for 2.6.26 version. Following is the patch file which is working fine for me.<br /><br />o <a href="http://androidzaurus.up.seesaa.net/image/pxafb_doublebuffer.patch.bz2" target="_blank">pxafb_doublebuffer.patch.bz2</a><br /><br />The touchscreen driver is not working satisfactorily. Once I manage to make it work, I'll upload a pactch on this blog.<br /><br />Cheers,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/105551643</guid>
            <enclosure url="https://androidzaurus.up.seesaa.net/image/pxafb_doublebuffer.patch.bz2" length="1226" type="application/x-bzip2" />
                      </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/105315032.html</link>
      <title>Network is up - Android 0.9 SDK beta</title>
      <pubDate>Mon, 25 Aug 2008 11:46:23 +0900</pubDate>
            <description>I checked system propertis in the emulator.$ ./emulator &amp;$ ./adb shell# getpropThere is a new property [net.dns1] and [net.dns2].net.dns1 sounds very interesting, so I modified android-root/default.prop, adding;net.eth0.dns1=208.66.222.222n..</description>
            <itunes:summary><![CDATA[
I checked system propertis in the emulator.$ ./emulator &
$ ./adb shell
# getpropThere is a new property [net.dns1] and [net.dns2].

net.dns1 sounds very interesting, so I modified android-root/default.prop, adding;net.eth0.dns1=208.66.222.222
net.dns1=208.67.222.222OK. Network is up. Now I can browse the Internet and see Street View with Map application.

Chrees,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
I checked system propertis in the emulator.<pre>$ ./emulator &<br />$ ./adb shell<br /># getprop</pre>There is a new property [net.dns1] and [net.dns2].<br /><br />net.dns1 sounds very interesting, so I modified android-root/default.prop, adding;<pre>net.eth0.dns1=208.66.222.222<br />net.dns1=208.67.222.222</pre>OK. Network is up. Now I can browse the Internet and see Street View with Map application.<br /><br />Chrees,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/105315032</guid>
                </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/105223369.html</link>
      <title>Android 0.9 SDK beta  - Up on Zaurus</title>
      <pubDate>Sat, 23 Aug 2008 21:54:02 +0900</pubDate>
            <description>Android Rocks! Zaurus Rules!Android 0.9 SDK beta now runs on my Zaurus C-3000.Booting... Hello, Goodie.Home Screen. A nice big clock.Applications. I want more apps.Tips for porting.o Get kernel tar ball from http://code.google.com/p/android..</description>
            <itunes:summary><![CDATA[
Android Rocks! Zaurus Rules!

Android 0.9 SDK beta now runs on my Zaurus C-3000.

Booting... Hello, Goodie.
<a href="http://androidzaurus.up.seesaa.net/image/booting-sdk-0.9.jpg" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/booting-sdk-0-thumbnail2.9.jpg" width="150" height="133" border="0" alt="booting-sdk-0.9.jpg" /></a>

Home Screen. A nice big clock.
<a href="http://androidzaurus.up.seesaa.net/image/home-sdk-0.9.jpg" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/home-sdk-0-thumbnail2.9.jpg" width="150" height="127" border="0" alt="home-sdk-0.9.jpg" /></a>

Applications. I want more apps.
<a href="http://androidzaurus.up.seesaa.net/image/applications-sdk-0.9.jpg" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/applications-sdk-0-thumbnail2.9.jpg" width="150" height="137" border="0" alt="applications-sdk-0.9.jpg" /></a>

Tips for porting.
o Get kernel tar ball from <a href="http://code.google.com/p/android/downloads/list" target="_blank">http://code.google.com/p/android/downloads/list</a>
o Look into mm/ashmem.c and drivers/android.
o Port ashmem and drivers/android to your platform. My case, linux-2.6.26 which   the latest Angstrom uses.
o Double buffering and pan functions for frame buffer driver is now mandatory.

Things not working yet.
o Network. Where should I put net.eth0.dns1?
o Touchscreen. It works very poor.
o Keyboard configuration. Mostly same as good old qwerty.kl but not ported yet.
o Sound. Haven't check it.

Anyway. So far, so good.

Cheers,

<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Android Rocks! Zaurus Rules!<br /><br />Android 0.9 SDK beta now runs on my Zaurus C-3000.<br /><br />Booting... Hello, Goodie.<br /><a href="http://androidzaurus.up.seesaa.net/image/booting-sdk-0.9.jpg" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/booting-sdk-0-thumbnail2.9.jpg" width="150" height="133" border="0" align="" alt="booting-sdk-0.9.jpg" onclick="location.href = 'https://androidzaurus.seesaa.net/upload/detail/image/booting-sdk-0-thumbnail2.9.jpg.html'; return false;" style="cursor:pointer;" /></a><br /><br />Home Screen. A nice big clock.<br /><a href="http://androidzaurus.up.seesaa.net/image/home-sdk-0.9.jpg" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/home-sdk-0-thumbnail2.9.jpg" width="150" height="127" border="0" align="" alt="home-sdk-0.9.jpg" onclick="location.href = 'https://androidzaurus.seesaa.net/upload/detail/image/home-sdk-0-thumbnail2.9.jpg.html'; return false;" style="cursor:pointer;" /></a><br /><br />Applications. I want more apps.<br /><a href="http://androidzaurus.up.seesaa.net/image/applications-sdk-0.9.jpg" target="_blank"><img src="http://androidzaurus.up.seesaa.net/image/applications-sdk-0-thumbnail2.9.jpg" width="150" height="137" border="0" align="" alt="applications-sdk-0.9.jpg" onclick="location.href = 'https://androidzaurus.seesaa.net/upload/detail/image/applications-sdk-0-thumbnail2.9.jpg.html'; return false;" style="cursor:pointer;" /></a><br /><br />Tips for porting.<br />o Get kernel tar ball from <a href="http://code.google.com/p/android/downloads/list" target="_blank">http://code.google.com/p/android/downloads/list</a><br />o Look into mm/ashmem.c and drivers/android.<br />o Port ashmem and drivers/android to your platform. My case, linux-2.6.26 which   the latest Angstrom uses.<br />o Double buffering and pan functions for frame buffer driver is now mandatory.<br /><br />Things not working yet.<br />o Network. Where should I put net.eth0.dns1?<br />o Touchscreen. It works very poor.<br />o Keyboard configuration. Mostly same as good old qwerty.kl but not ported yet.<br />o Sound. Haven't check it.<br /><br />Anyway. So far, so good.<br /><br />Cheers,<br /><br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/105223369</guid>
            <enclosure url="https://androidzaurus.up.seesaa.net/image/booting-sdk-0.9.jpg" length="100513" type="image/jpeg" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/booting-sdk-0.9.jpg" length="100513" type="image/jpeg" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/home-sdk-0.9.jpg" length="89155" type="image/jpeg" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/home-sdk-0.9.jpg" length="89155" type="image/jpeg" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/applications-sdk-0.9.jpg" length="119158" type="image/jpeg" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/applications-sdk-0.9.jpg" length="119158" type="image/jpeg" />
                      </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/105091433.html</link>
      <title>Android 0.9 SDK beta</title>
      <pubDate>Thu, 21 Aug 2008 10:12:31 +0900</pubDate>
            <description>Long awaited Android SDK was finally released as 0.9 beta.o http://code.google.com/android/index.htmlI have tried to boot it up on my Zaurus. No luck yet. /init dies with a segmentation fault. Maybe I need to port some drivers from the late..</description>
            <itunes:summary><![CDATA[
Long awaited Android SDK was finally released as 0.9 beta.

o http://code.google.com/android/index.html

I have tried to boot it up on my Zaurus. No luck yet. /init dies with a segmentation fault. Maybe I need to port some drivers from the latest Android kernel.

o http://code.google.com/p/android/downloads/list

Here is my first impression of the emulator.Copy and Paste. Huge advantage to iPhone, for now.WebView works much better than m5.Street View rocks!Conference call function. Android becomes a cutting edge phone.Science Calculator.A little tip how to get boot log of the emulator.$ ./emulator &
$ ./adb shell
# mount -o remount,rw rootfs /
# mkdir /tmp
# /system/bin/dumpstate
# exit
$ ./adb pull /tmp/state state.log
$ more state.logSince rootfs is mounted as read only, you need to remount it after booted the emulator.

Cheers,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Long awaited Android SDK was finally released as 0.9 beta.<br /><br />o http://code.google.com/android/index.html<br /><br />I have tried to boot it up on my Zaurus. No luck yet. /init dies with a segmentation fault. Maybe I need to port some drivers from the latest Android kernel.<br /><br />o http://code.google.com/p/android/downloads/list<br /><br />Here is my first impression of the emulator.<ul><li>Copy and Paste. Huge advantage to iPhone, for now.</li><li>WebView works much better than m5.</li><li>Street View rocks!</li><li>Conference call function. Android becomes a cutting edge phone.</li><li>Science Calculator.</li></ul>A little tip how to get boot log of the emulator.<pre>$ ./emulator &<br />$ ./adb shell<br /># mount -o remount,rw rootfs /<br /># mkdir /tmp<br /># /system/bin/dumpstate<br /># exit<br />$ ./adb pull /tmp/state state.log<br />$ more state.log</pre>Since rootfs is mounted as read only, you need to remount it after booted the emulator.<br /><br />Cheers,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/105091433</guid>
                </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/103999015.html</link>
      <title>Current kernel image and cumulative patch</title>
      <pubDate>Fri, 01 Aug 2008 16:56:53 +0900</pubDate>
            <description>Following is an Angstrom image which is working on my Zaurus C3000.o Angstrom-console-image-glibc-ipk-2007.11RC1-spitz-installkit.tgzMy case, lowmemorykiller is built as a module.o lowmemorykiller.ko.bz2I will not answer any questions about..</description>
            <itunes:summary><![CDATA[
Following is an Angstrom image which is working on my Zaurus C3000.
o <a href="http://androidzaurus.up.seesaa.net/image/Angstrom-console-image-glibc-ipk-2007.11RC1-spitz-installkit.tgz" target="_blank">Angstrom-console-image-glibc-ipk-2007.11RC1-spitz-installkit.tgz</a>

My case, lowmemorykiller is built as a module.
o <a href="http://androidzaurus.up.seesaa.net/image/lowmemorykiller.ko.bz2" target="_blank">lowmemorykiller.ko.bz2</a>

I will not answer any questions about these binary files. AT YOUR OWN RISK, PLEASE.

Here is a patch file which can be applied to vanilla 2.6.23 kernel source tree. This is cumulative, including all Angstrom patches, Android patches as well as frame buffer, touch panel and so on.
o <a href="http://androidzaurus.up.seesaa.net/image/diff-linux-2.6.23-vanilla-androidzaurus.patch.bz2" target="_blank">diff-linux-2.6.23-vanilla-androidzaurus.patch.bz2</a>

Please note that redistributing Android SDK m5 is prohibited by the licence.
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Following is an Angstrom image which is working on my Zaurus C3000.<br />o <a href="http://androidzaurus.up.seesaa.net/image/Angstrom-console-image-glibc-ipk-2007.11RC1-spitz-installkit.tgz" target="_blank">Angstrom-console-image-glibc-ipk-2007.11RC1-spitz-installkit.tgz</a><br /><br />My case, lowmemorykiller is built as a module.<br />o <a href="http://androidzaurus.up.seesaa.net/image/lowmemorykiller.ko.bz2" target="_blank">lowmemorykiller.ko.bz2</a><br /><br />I will not answer any questions about these binary files. <strong>AT YOUR OWN RISK, PLEASE.</strong><br /><br />Here is a patch file which can be applied to vanilla 2.6.23 kernel source tree. This is cumulative, including all Angstrom patches, Android patches as well as frame buffer, touch panel and so on.<br />o <a href="http://androidzaurus.up.seesaa.net/image/diff-linux-2.6.23-vanilla-androidzaurus.patch.bz2" target="_blank">diff-linux-2.6.23-vanilla-androidzaurus.patch.bz2</a><br /><br />Please note that redistributing Android SDK m5 is prohibited by the licence.<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/103999015</guid>
            <enclosure url="https://androidzaurus.up.seesaa.net/image/Angstrom-console-image-glibc-ipk-2007.11RC1-spitz-installkit.tgz" length="8726843" type="application/x-gzip" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/lowmemorykiller.ko.bz2" length="2169" type="application/x-bzip2" />
                  <enclosure url="https://androidzaurus.up.seesaa.net/image/diff-linux-2.6.23-vanilla-androidzaurus.patch.bz2" length="399881" type="application/x-bzip2" />
                      </item>
        <item>
      <link>https://androidzaurus.seesaa.net/article/103876791.html</link>
      <title>A patch for sound driver</title>
      <pubDate>Wed, 30 Jul 2008 17:57:49 +0900</pubDate>
            <description>Brilliant Service, who ported Android to Armadillo-500, released a patch of sound driver.o Enabling audio on Android (Japanese)o android-sound-patch.tar.gzI have applied this patch to Angstrom kernel source. It works beautifully on Zaurus, ..</description>
            <itunes:summary><![CDATA[
Brilliant Service, who ported <a href="http://androidzaurus.seesaa.net/article/82618724.html">Android to Armadillo-500</a>, released a patch of sound driver.
o <a href="http://d.hatena.ne.jp/bs-android/20080728">Enabling audio on Android</a> (Japanese)
o <a href="http://brilliant.android.googlepages.com/android-sound-patch.tar.gz">android-sound-patch.tar.gz</a>

I have applied this patch to Angstrom kernel source. It works beautifully on Zaurus, too. Because Android uses /dev/eac as sound device, make a symbolic link; $ ln -s /dev/dsp /dev/eacIf your Android is booted up by chroot, remeber to make symlink in android-root/dev, too.

Brilliant Service mentioned that this patch was originally written by <a href="http://www.atmark-techno.com/en/">Atmark Techno</a> who is the developer of Armdallio. Big thanks to Atmark Techno.

Cheers,
<a></a>

]]></itunes:summary>
      <content:encoded><![CDATA[
Brilliant Service, who ported <a href="http://androidzaurus.seesaa.net/article/82618724.html">Android to Armadillo-500</a>, released a patch of sound driver.<br />o <a href="http://d.hatena.ne.jp/bs-android/20080728">Enabling audio on Android</a> (Japanese)<br />o <a href="http://brilliant.android.googlepages.com/android-sound-patch.tar.gz">android-sound-patch.tar.gz</a><br /><br />I have applied this patch to Angstrom kernel source. It works beautifully on Zaurus, too. Because Android uses /dev/eac as sound device, make a symbolic link; <blockquote>$ ln -s /dev/dsp /dev/eac</blockquote>If your Android is booted up by chroot, remeber to make symlink in android-root/dev, too.<br /><br />Brilliant Service mentioned that this patch was originally written by <a href="http://www.atmark-techno.com/en/">Atmark Techno</a> who is the developer of Armdallio. Big thanks to Atmark Techno.<br /><br />Cheers,<br /><a name="more"></a>

]]><![CDATA[
]]></content:encoded>
            <category>日記</category>
      <author>安藤恐竜</author>
      <guid isPermaLink="false">blog:https://blog.seesaa.jp,androidzaurus/103876791</guid>
                </item>
      </channel>
</rss>

