OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Android => Topic started by: cortez on December 29, 2007, 04:52:50 pm
-
Hi,
For the time being posted here in "General Discussion" since there is no dedicated Android subforum (yet). Tested on my SL-C3100, this is a small bootable Poky 2.6.23 kernel with a copy of the Android OS from the SDK (qemu) emulator.
Installation is done in the usual way:
1. Download zImage.bin (http://www.omegamoon.com/zImage.bin), updater.sh (http://www.omegamoon.com/updater.sh), gnu-tar (http://www.omegamoon.com/gnu-tar) and android-root.tar.gz (http://www.omegamoon.com/android-root.tar.gz) and copy the files to a SD card
2. Remove battery and power adapter cable
3. Wait for 5 seconds
4. Replace battery, close and lock battery cover
5. Attach power adapter cable
6. Keep OK button pressed while pressing on/off switch
7. From the Japanese menu, choose option 4 (Update), then 2 (SD) and finally Y
Flashing starts, and you are asked if you want to flash the kernel, if you want the microdrive to be formatted and if you want the root filesystem to be installed.
Accept all questions answering them with y
After flashing is complete, the machine is rebooted. Login with root and type /start to start Android.
This is the basic version, without any of the patches found across the Net.
Have fun, and share your results and findings here please!
Updated: There is a special version for the SL-C1000. Downloads and instructions can be found at www.omegamoon.com (http://www.omegamoon.com)
Updated: A test version for the SL-C7x0 and SL-C860 can be downloaded from www.omegamoon.com (http://www.omegamoon.com). Please test and give feedback
Greetz,
cortez
-
Good job, cortez!
I just bought a used C3000 eBay specifically for experiments with Android and now flashed your image.
Looks quite quick... the network and rotate-to-landscape hacks would be nice to have setup.
How does one kill the GUI and get back to the shell prompt, what are the navigation keys (as the touchscreen is not working)?
Can you describe in more detail your build setup, especially the differences to original japanese one (http://androidzaurus.seesaa.net/), if any?
I'll be spending time on this during the holidays, and even intend to install OpenEmbedded...
Thanks!
-
excellent! looking forward to testing
-
any hint about getting android on a 6k?
-
I m trying to chroot your rootfs under my debian. It fails to launch with this error :
fatal error opening "/sys/android_power/acquire_partial_wake_lock"
any help ?
-
I m trying to chroot your rootfs under my debian. It fails to launch with this error :
fatal error opening "/sys/android_power/acquire_partial_wake_lock"
any help ?
jpmatrix,
To get things working on any 2.6.23 distro, including Debian, Poky, Angstrom etc just extract the /home/root/android and the /start script from andoid-root.tar.gz. Make sure to extract android in /home/root/android, otherwise it doesn't work. If /lib/modules/2.6.23/kernel/drivers/binder doesn't exist on your distro extract this also from andoid-root.tar.gz. Finally extract /doit to force the /start script to setup the binder module correctly.
Last but not least, use the tar -xzpf options (the p is important) to make sure you keep all permissions correct.
I hope I didn't miss anything, but I think this should do the trick.
Greetz,
cortez
-
any hint about getting android on a 6k?
If you have a 2.6.23 kernel running on your 6k, then read my previous post to get Android working. Shouldn't be any problem I guess
-
Good job, cortez!
I just bought a used C3000 eBay specifically for experiments with Android and now flashed your image.
Looks quite quick... the network and rotate-to-landscape hacks would be nice to have setup.
How does one kill the GUI and get back to the shell prompt, what are the navigation keys (as the touchscreen is not working)?
Can you describe in more detail your build setup, especially the differences to original japanese one (http://androidzaurus.seesaa.net/), if any?
I'll be spending time on this during the holidays, and even intend to install OpenEmbedded...
Thanks!
sds,
I'll try to incorporate all hacks available shortly. I didn't find any info on the Net about ways to exit Android, but I've found out the following:
Press CTRL+ALT+1 simultaneously for approx. 1 second to display the console. Next, keeping CTRL+ALT pressed press HOME followed by MENU. Following message is displayed:
SysRq : HELP : loglevel0-8 reBoot Crashdump tErm Full kIll saK showMem Nice powerOff showPc show-all-timers(Q) unRaw Sync showTasks Unmount shoW-blocked-tasks
Keeping CTRL+ALT pressed, choose one of the (bold) uppercase characters to perform the corresponding action. I don't know the meaning of all actions, but pressing I results in a forced exit. Pressing CTRL+ALT+2 returns you to Android.
My build setup is a clean Poky environment not much different from the Japanese (Angstrom) version I guess. I just added a few extras like Midnight Commander (mc) to make life a bit easier when copying/editing etc on the Zaurus.
Cheers,
cortez
-
I m trying to chroot your rootfs under my debian. It fails to launch with this error :
fatal error opening "/sys/android_power/acquire_partial_wake_lock"
any help ?
jpmatrix,
To get things working on any 2.6.23 distro, including Debian, Poky, Angstrom etc just extract the /home/root/android and the /start script from andoid-root.tar.gz. Make sure to extract android in /home/root/android, otherwise it doesn't work. If /lib/modules/2.6.23/kernel/drivers/binder doesn't exist on your distro extract this also from andoid-root.tar.gz. Finally extract /doit to force the /start script to setup the binder module correctly.
Last but not least, use the tar -xzpf options (the p is important) to make sure you keep all permissions correct.
I hope I didn't miss anything, but I think this should do the trick.
Greetz,
cortez
gotcha! i at last managed to launch it ! thank you !
-
just one question:
how do you open the android console ?
i can switch to another tty but i cannot go back to android gui then...
-
Will it work on a C1000?
Any screenshots?
-
Will it work on a C1000?
Any screenshots?
(terrrrrible!) screenshots can be seen on this master blog:
http://androidzaurus.seesaa.net/article/75516785.html (http://androidzaurus.seesaa.net/article/75516785.html)
my main problem at now is that i cannot have network to work....any help? (under debian chroot)
-
That's definitely a good toy to play with in New Year!
I notice that image is for installation via the [OK] flash menu.
So anyone got it working under the debian-yonggun kernel using uboot (2or0)?
-
That's definitely a good toy to play with in New Year!
I notice that image is for installation via the [OK] flash menu.
So anyone got it working under the debian-yonggun kernel using uboot (2or0)?
or you can also just untar the android-root dir and run it as chroot under your existing debian
about network problem i've a dns setting trouble i think
perhaps this page would help:
http://nemustech.blogspot.com/ (http://nemustech.blogspot.com/)
http://www.anddev.org/advanced_networking_...linux-t155.html (http://www.anddev.org/advanced_networking_with_android-linux-t155.html)
-
That's definitely a good toy to play with in New Year!
I notice that image is for installation via the [OK] flash menu.
So anyone got it working under the debian-yonggun kernel using uboot (2or0)?
I already did it last week. I built the kernel and tested it on debian. If you are interested in it, I will upload the kernel and modules.
-
I already did it last week. I built the kernel and tested it on debian. If you are interested in it, I will upload the kernel and modules.
Sure, pleazzzzzzz.
-
I already did it last week. I built the kernel and tested it on debian. If you are interested in it, I will upload the kernel and modules.
Sure, pleazzzzzzz.
Ok, I upload them in my blog. Check it
-
Dear jpmatrix,
DNS issue might be resolved by running android-root/init instead of runtime in start script.
Network is up.
http://androidzaurus.seesaa.net/article/74649330.html (http://androidzaurus.seesaa.net/article/74649330.html)
A better way to bring network up.
http://androidzaurus.seesaa.net/article/74701717.html (http://androidzaurus.seesaa.net/article/74701717.html)
Android console could be bring up by /system/bin/sh in start script and/or changing the system console to tty2 because android-init always grabs /dev/tty1.
setconsole and tty1
http://androidzaurus.seesaa.net/article/75560174.html (http://androidzaurus.seesaa.net/article/75560174.html)
Cheers,
-
Look who's here, it's the author of all the androidzaurus.seesaa.net articles
It's great to see you around, and keep up the good work!
Dear jpmatrix,
DNS issue might be resolved by running android-root/init instead of runtime in start script.
Network is up.
http://androidzaurus.seesaa.net/article/74649330.html (http://androidzaurus.seesaa.net/article/74649330.html)
A better way to bring network up.
http://androidzaurus.seesaa.net/article/74701717.html (http://androidzaurus.seesaa.net/article/74701717.html)
Android console could be bring up by /system/bin/sh in start script and/or changing the system console to tty2 because android-init always grabs /dev/tty1.
setconsole and tty1
http://androidzaurus.seesaa.net/article/75560174.html (http://androidzaurus.seesaa.net/article/75560174.html)
Cheers,
-
DNS issue might be resolved by running android-root/init instead of runtime in start script.
gotcha! it works!!!!!
(sometimes i wonder why people simply doesn't write EXACTLY what is written in blogs/wiki...... )
i could launch the browser, and try some google searches with success!!!! terrrrrible
i also noticed that the hdd light was blinking a lot, i don't really know what is was looking/loading....
edited:i forgot to say that the touchscreeen was somewhat working : it seems rotated...but the screen respond!
-
DNS issue might be resolved by running android-root/init instead of runtime in start script.
gotcha! it works!!!!!
(sometimes i wonder why people simply doesn't write EXACTLY what is written in blogs/wiki...... )
i could launch the browser, and try some google searches with success!!!! terrrrrible
i also noticed that the hdd light was blinking a lot, i don't really know what is was looking/loading....
edited:i forgot to say that the touchscreeen was somewhat working : it seems rotated...but the screen respond!
Glad to know you've successfully done.
My case, the touch screen sometimes woks, sometimes doesn't. It's unstable.
The coordinate of touchscreen is in landscape view, even though frame buffer is in portlait view. It really confusing. I think touchscreen driver needs a little hack to incooperate with "service call window 18 i32 1" command.
Cheers,
-
Dear cortez,
Thank you very much for your welcoming message. There are two more guys successfully booted Android on Zaurus based on your install image.
Android on Zaurus
http://ceo.gclue.jp/2008/01/04/android-on-zaurus/ (http://ceo.gclue.jp/2008/01/04/android-on-zaurus/)
His comment is "it is encouraging to develop some Android applets."
Android Zaurus: the movie
http://blog.so-net.ne.jp/vhehas/2008-01-05 (http://blog.so-net.ne.jp/vhehas/2008-01-05)
He uploaded a movie Android is working on Zaurus.
-
Android Zaurus,
i love your RotateView applet Thank you !!!
and i've just tried this one:
http://www.androidapps.org/2007/12/android...odge-balls.html (http://www.androidapps.org/2007/12/androids-got-game-dodge-balls.html)
it works! .... in fact at least it runs, but i've troubles with the keyboard to play it
-
just another world to say that i've just tried google maps on Android ! wwwwhooooowwww!!!!
full screen rendering on the zaurus !
-launch Maps
-press Calendar to have the menu, then Search
then enter your address
-press "S" to have the famous Google satellite view ! enjoy !!!
-
You guys are my heroes!!!!! Android is the future!! Think about it.. the biggest tech company and most successful backing this project and the manpower that will be developing for it will be MIND BLOWING.. It's so sweet that you guys are letting us have a working preview of the future.
CHEERS!!
-
after playing a little with android, it happens that my hdd went full !!! apparently the tmp directory is growing fast as you use android... i notice it is erased on android launch but is it safe to erase it as android is running ???
-
after playing a little with android, it happens that my hdd went full !!! apparently the tmp directory is growing fast as you use android... i notice it is erased on android launch but is it safe to erase it as android is running ???
does it generate lots of new files, or one big one? If one big one, can you symlink it to /dev/null? Or, if not possible, delete /tmp and symlink to a directory on a flash card?
-
after playing a little with android, it happens that my hdd went full !!! apparently the tmp directory is growing fast as you use android... i notice it is erased on android launch but is it safe to erase it as android is running ???
Good point, jpmatrix.
I tried ls on android-root/tmp.
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']
-rw------- root root 11429 2008-01-07 23:37 eventlog
srwxrwxrwx root root 2008-01-07 23:36 system_bus_socket
-rw-r--r-- root root 5 2008-01-07 23:36 messagebus.pid
prw--w--w- root root 2008-01-07 23:43 android-SurfaceFlingerSynchro
-rw-r--r-- root root 4096 2008-01-07 23:37 android-shared_heap.1864.0x157f80
-rw-r--r-- app_0 app_0 23552 2008-01-07 23:37 media.db
-rw-rw-rw- root root 9838592 2008-01-07 23:37 android-shared_heap.1864.0x189b90
-rw-rw-rw- app_4 app_4 1048576 2008-01-07 23:37 android-shared_heap.1897.0x15df98
-rw-r--r-- app_0 app_0 12288 2008-01-07 23:37 im_transient.db
-rw-rw-rw- phone phone 1048576 2008-01-07 23:38 android-shared_heap.1899.0x18f678
-rw-r--r-- app_0 app_0 2048 2008-01-07 23:37 contacts_presence.db
-rw-rw-rw- root root 9838592 2008-01-07 23:37 android-shared_heap.1864.0x1b1c80
-rw-rw-rw- phone phone 1048576 2008-01-07 23:38 android-shared_heap.1899.0x186ba0
-rw-rw-rw- root root 9838592 2008-01-07 23:38 android-shared_heap.1864.0x1a4088
-rw-rw-rw- phone phone 1048576 2008-01-07 23:38 android-shared_heap.1899.0x1947b8
[/div]
Each Android applet eats 1M to 9M bytes shared memory and they are put in /tmp. I guess Dalvik VM does this trick. Obviously you can't delete them on runtime.
For a real target device, /tmp is usually assigned to ramfs. Our Android Zaurus case, it's on internal hdd/flash filesystem. I've been wondering why Android runs on poor 64M, but shared memory on /tmp explains a little.
On the other hand, if android-root/tmp goes to ramfs, Android Zaurus may run much faster. There's always bright side.
By the way, start-android script erases android-root/tmp each time at startup. The reason is binderdev.o reports warning if messagebus.pid[/] exists in android-root/tmp at boot up. So I decided clean them up all in start script. Well, it's supposed to be volatile anyway.
Cheers,
-
Can I use wireless cf card with android? my card is a planex that use hostap driver
-
Can I use wireless cf card with android? my card is a planex that use hostap driver
android is chrooted under your main distro (debian or angstrom). so if your card is supported, there's no problem at all
-
so I have to install debian and then android?
-
so I have to install debian and then android?
it depends on your hardware and actual distro.
if you want to start from fresh, just follow post #1 here from Cortez
-
Hi, I have followed the instructions in the first post and have Android running! Thanks!
So, poor noob would like some help
- How do I get my Wifi CF turned on? I am not in a chrooted environment; having followed the instructions straight from the 1rst post. Or is that chrooted too?
- What's the way back to sharp rom if needed?
Thanks!
-
if I install without chroot there are packages to isntall or android is a small distribution without package manager?Thanks
-
Hi, I have followed the instructions in the first post and have Android running! Thanks!
So, poor noob would like some help
- How do I get my Wifi CF turned on? I am not in a chrooted environment; having followed the instructions straight from the 1rst post. Or is that chrooted too?
- What's the way back to sharp rom if needed?
Thanks!
Edit wlan0 section in your /etc/network/interface. There are a couple of samples how to configure in the interfaces file. And don't forget to delete the gateway line in usb0 section.
By the way, I found this news very interrested this morning.
Penguinistas hack Android onto real hardware
http://linuxdevices.com/news/NS4262102607.html (http://linuxdevices.com/news/NS4262102607.html)
Cheers,
-
By the way, I found this news very interrested this morning.
Penguinistas hack Android onto real hardware
http://linuxdevices.com/news/NS4262102607.html (http://linuxdevices.com/news/NS4262102607.html)
Cheers,
it 's funny, i read the same article this morning! congratulations!
-
any idea on running android with the native sharp rom?
Is it possible?
Definitely, it's a good software stack to be tried.
-
I was happy to try!! And now I'm safely back to sharp rom.
I'm looking forward to Android progress, and will switch again when it's good for noobs;)
-
Sorry to hijack this thread... I'd like to try this on my old C760... is there a Howto somewhere to get me started ?
TIA,
fp
-
Penguinistas hack Android onto real hardware
http://linuxdevices.com/news/NS4262102607.html (http://linuxdevices.com/news/NS4262102607.html)
it 's funny, i read the same article this morning! congratulations!
I emailed them yesterday, when they posted about a rumoured HTC device ready for march, to say "why wait, buy a zaurus!", and they replied later/this morning/? to say they were writing it up.
-
great
i wonder if a zaurus with a gsm card like the Audiovox RTM could be used as a Google phone... or at least it should be possible to have skype on google on zaurus.........
-
Sorry to hijack this thread... I'd like to try this on my old C760... is there a Howto somewhere to get me started ?
TIA,
fp
heh, i'd like to know too. got a C760 here.
-
Sorry to hijack this thread... I'd like to try this on my old C760... is there a Howto somewhere to get me started ?
TIA,
fp
heh, i'd like to know too. got a C760 here.
With a kernel capable of running Android you should be up and running in no-time. Let me know if you need help doing that.
-
Sorry to hijack this thread... I'd like to try this on my old C760... is there a Howto somewhere to get me started ?
TIA,
fp
heh, i'd like to know too. got a C760 here.
With a kernel capable of running Android you should be up and running in no-time. Let me know if you need help doing that.
What kernel is capable runnig Android? Also 2.4.20?
-
With a kernel capable of running Android you should be up and running in no-time. Let me know if you need help doing that.
I definitely would. I am not Linux-shy obviously, but not a super hacker either. I have only ever flashed Cacko ROMs on my Z, so I wouldn't know where to start...
-
Sorry to hijack this thread... I'd like to try this on my old C760... is there a Howto somewhere to get me started ?
TIA,
fp
heh, i'd like to know too. got a C760 here.
With a kernel capable of running Android you should be up and running in no-time. Let me know if you need help doing that.
What kernel is capable runnig Android? Also 2.4.20?
You need a kernel with EABI support. That's version 2.6.16 or newer.
-
Noone's tried the C1000 yet?
I'll give it a shot this weekend. Would I be able to just use the same files that the C3000 guys are using? There's no internal HD though..
-
I'll try to build versions for C7x0 and C1000 shortly, so you can join us all in this great experiment
-
AWESOME!! Most exciting thing to happen to the Zaurus community in a looong time
-
i'm currently trying to make it run on a C1000 running angstrom console image. it does run, but i can't get past the bouncing red eye. it just keeps bouncing and nothing happens. the main problem with running android on a C1000 and on earlier models is the jffs2 filesystem. i heard android won't work on a jffs2 filesystem. i'm currently trying to run it from the sd card. any useful advice is most welcome. :-)
-
I've just build minimal systems for the C7x0 and C1000 and hope to be able to test it tomorrow night on my C1000
-
Great news ! Thanks for making this accessible to (almost) normal humans :-)
My Z has seen little use since I've had my Nokia tablet and it's a pity - I hope this brings it a new life !
-
I got it running on my C1000 last night. I used an Angstrom 2.6.23 kernel that I applied the patch at http://androidzaurus.seesaa.net/ (http://androidzaurus.seesaa.net/) to. Then I grabbed the android.tgz.part?.rar from http://yonggun.tistory.com/ (http://yonggun.tistory.com/) and followed the instructions for running it. The first time I started it I got nothing but the "Cylon eye" but after rebooting it started no problem the next time. The touchscreen seems to work inconsistently and when android is oriented "portrait" style the touchscreen still acts like landscape.
-
Sorry to hijack this thread... I'd like to try this on my old C760... is there a Howto somewhere to get me started ?
TIA,
fp
heh, i'd like to know too. got a C760 here.
With a kernel capable of running Android you should be up and running in no-time. Let me know if you need help doing that.
The original Eu.Edge guys have done on thier C-760.
eu.edge » Blog Archive » Google Android runs on Sharp Zaurus SL-C760 (http://euedge.com/blog/2007/12/06/google-android-runs-on-sharp-zaurus-sl-c760/)
And I found Android can be booted up on ready-made Angstrom kernel as long as we have binderdev.ko module.
Android Zaurus: Android Zaurus on a ready-made Angstrom image (http://androidzaurus.seesaa.net/article/75131152.html)
So, Angstrom or Poky for C7x0 could be a host of Android. Question is how to get the binderdev.ko binary.
Do you guys think the driver module built for C3x00 runs on C7x0? My guess is possible because the binder driver seems not to rely on hardware much. If so, cortez's image or my binary (http://androidzaurus.up.seesaa.net/image/binder-angstrom.tar.gz) can be used.
Cheers,
-
I got it running on my C1000 last night. I used an Angstrom 2.6.23 kernel that I applied the patch at http://androidzaurus.seesaa.net/ (http://androidzaurus.seesaa.net/) to. Then I grabbed the android.tgz.part?.rar from http://yonggun.tistory.com/ (http://yonggun.tistory.com/) and followed the instructions for running it. The first time I started it I got nothing but the "Cylon eye" but after rebooting it started no problem the next time. The touchscreen seems to work inconsistently and when android is oriented "portrait" style the touchscreen still acts like landscape.
Great work!
Touchscreen is a issue. The orientation problem might caused by MOUSE_X=640, MOUSE_Y=480 in .config file eventhough frame buffer is 480x640. Could be fixed by modifying .config but not tried yet.
Workaround could be my RotateView.apk (http://androidzaurus.seesaa.net/article/76612103.html).
Cheers,
-
Hi, I have followed the instructions in the first post and have Android running! Thanks!
So, poor noob would like some help
- How do I get my Wifi CF turned on? I am not in a chrooted environment; having followed the instructions straight from the 1rst post. Or is that chrooted too?
- What's the way back to sharp rom if needed?
Thanks!
Edit wlan0 section in your /etc/network/interface. There are a couple of samples how to configure in the interfaces file. And don't forget to delete the gateway line in usb0 section.
By the way, I found this news very interrested this morning.
Penguinistas hack Android onto real hardware
http://linuxdevices.com/news/NS4262102607.html (http://linuxdevices.com/news/NS4262102607.html)
Cheers,
We're being watched The news spreads itself further... see articles in techworld (http://techworld.com/networking/news/index.cfm?newsID=11096&pagtype=all) and pcadvisor (http://pcadvisor.co.uk/news/index.cfm?newsid=11804)
-
So how do people like android (I have an 860 so I cannot try it yet myself). Innovative? Just curious. Thx
-
We're being watched The news spreads itself further... see articles in techworld (http://techworld.com/networking/news/index.cfm?newsID=11096&pagtype=all) and pcadvisor (http://pcadvisor.co.uk/news/index.cfm?newsid=11804)
and aki news!
http://www.akihabaranews.com/en/news-15328...+Zaurus%21.html (http://www.akihabaranews.com/en/news-15328-Get+Android+working+on+your+Zaurus%21.html)
also someone pointed out downloadsquad
http://www.downloadsquad.com/2008/01/10/go...n-sharp-zaurus/ (http://www.downloadsquad.com/2008/01/10/google-android-hacked-to-run-on-sharp-zaurus/)
-
We're being watched The news spreads itself further... see articles in techworld (http://techworld.com/networking/news/index.cfm?newsID=11096&pagtype=all) and pcadvisor (http://pcadvisor.co.uk/news/index.cfm?newsid=11804)
and aki news!
http://www.akihabaranews.com/en/news-15328...+Zaurus%21.html (http://www.akihabaranews.com/en/news-15328-Get+Android+working+on+your+Zaurus%21.html)
and...
Engadget - Android hacked to run on real hardware (http://www.engadget.com/2008/01/09/android-hacked-to-run-on-real-hardware/)
Slashdot - Hackers Get Android Running on Real Hardware (http://hardware.slashdot.org/article.pl?sid=08/01/09/2113235)
Hope more guys interrested in Android on Zaurus. Let's mash it up!
Cheers,
-
Hi,
We are trying to get the Android framework (binary) working on our custom hardware that is based ARM11 core. We do have a 2.6.23 kernel with ABI support and the android-root.tar.gz suggested in your post is being used as the rootFS. However when we try launching the /start script from console, it is unable to load the binderdev.ko module that is shipped with android-root.tar.gz archive. Hence we have added the binder module support into our custom kernel (binder module source code has been taken from from the linux-2.6.23-android-m3-rc20.tar archive) as static driver. After having added this support, the re-built kernel has been tried with aforesaid rootFS, but after couple of initial messages it bails out with segmentation fault. When I tried the strace utility to trace through the execution, it has been found that the "binder module is failing with Descriptor2Node failed". The complete strace log is give below:
--admin's note - text snipped and put in an attachment to make thread more readable--
It would be really great if someone can give some input/suggsetions regarding this.
Can the pre-built Android binaries run on ARMv6 compatible machines? How do we move forward and get the framework properly working on our custom hardware?
Warm Regards,
Anil
-
It would be really great if someone can give some input/suggsetions regarding this.
Can the pre-built Android binaries run on ARMv6 compatible machines? How do we move forward and get the framework properly working on our custom hardware?
Warm Regards,
Anil
i don't know if it is really true but i read somewhere that android can only be run under ARMV5te devices...
EDITED: just found that while googling:
http://benno.id.au/blog/2007/11/21/android-neo1973 (http://benno.id.au/blog/2007/11/21/android-neo1973)
-
i don't know if it is really true but i read somewhere that android can only be run under ARMV5te devices...
EDITED: just found that while googling:
http://benno.id.au/blog/2007/11/21/android-neo1973 (http://benno.id.au/blog/2007/11/21/android-neo1973)
hmm, very interesting. I concur with the conclusion - google are unlikely to release sufficient source to android's OS to allow it to be recompiled for any processor.
Possibly slightly interesting point of history. When Arm first release their processors with the thumb instruction set, my employer won a contract to do some testing on it to take a bunch of example programs and verify they worked and compare execution speeds and code sizes etc.
-
hmm, very interesting. I concur with the conclusion - google are unlikely to release sufficient source to android's OS to allow it to be recompiled for any processor.
I'm looking forward to hte source codes of /init and qwerty.kcm.bin.
The /init source will explain where setprop/getprop saves runtime parameter. The qwerty.kcm may be only a filter module but without source code we don't know how to customise for Zaurus.
By the way, regarding Anil's ARM6 porting, I guess EABI support is required.
-
I'm trying to get this thing to work on my C1000, but this is giving me some headaches. I did some traces to find out what is happening, and I get following socket error during the start of runtime:
socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path=@property_service}, 19) = -1 ECONNREFUSED (Connection refused)
close(3) = 0
On the working SL-C3100 version this looks like:
socket(PF_FILE, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_FILE, path=@property_service}, 19) = 0
recvmsg(4, {msg_name(0)=NULL, msg_iov(1)=[{"\200\", 4}], msg_controllen=16, {cmsg_len=16, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, {5}}, msg_flags=0}, 0) = 4
mmap2(NULL, 32768, PROT_READ, MAP_SHARED, 5, 0) = 0x40000000
close(5) = 0
close(4) = 0
Any ideas what the reason could be?
-
Hi
I'm hoping to get this working on a C1000 but unfortunately my knowledge of Linux is limited. It would be great if you could share in steps how to do it once you manage to get it working.
-
I'm trying to get this thing to work on my C1000, but this is giving me some headaches. I did some traces to find out what is happening, and I get following socket error during the start of runtime:
socket(PF_FILE, SOCK_STREAM, 0) = 3
connect(3, {sa_family=AF_FILE, path=@property_service}, 19) = -1 ECONNREFUSED (Connection refused)
close(3) = 0
On the working SL-C3100 version this looks like:
socket(PF_FILE, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_FILE, path=@property_service}, 19) = 0
recvmsg(4, {msg_name(0)=NULL, msg_iov(1)=[{"\200\", 4}], msg_controllen=16, {cmsg_len=16, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, {5}}, msg_flags=0}, 0) = 4
mmap2(NULL, 32768, PROT_READ, MAP_SHARED, 5, 0) = 0x40000000
close(5) = 0
close(4) = 0
Any ideas what the reason could be?
I just installed Angstrom (x11-image-glibc-ipk-2007.12) and tried to see if it works. Same applies here, connection errors on property_service. According to the article here (http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html) the init executable needs to be patched.
* if you have jffs2 for / patch /init
* modify with hexedit : "/system_property" -> "/tmp/sy_property"
* NOTE: jffs2 does not support memory mapped file
I patched the init-exec but that didn't help. This isn't the way I expecting this to work. Any help is much appreciated.
-
I just installed Angstrom (x11-image-glibc-ipk-2007.12) and tried to see if it works. Same applies here, connection errors on property_service. According to the article here (http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html) the init executable needs to be patched.
* if you have jffs2 for / patch /init
* modify with hexedit : "/system_property" -> "/tmp/sy_property"
* NOTE: jffs2 does not support memory mapped file
I patched the init-exec but that didn't help. This isn't the way I expecting this to work. Any help is much appreciated.
Perhaps they got it to work because their /tmp is assigned to ramfs and not to the jffs2 part.
-
Alright, maybe I'm an idiot, but can someone give me a step-by-step of what I need to type to get the android stuff extracted the right way?
So far, I have a clean install of Angstrom on my C-860 and the android-root.tar.gz on my CF card. What do I do from here?
-
I just installed Angstrom (x11-image-glibc-ipk-2007.12) and tried to see if it works. Same applies here, connection errors on property_service. According to the article here (http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html) the init executable needs to be patched.
* if you have jffs2 for / patch /init
* modify with hexedit : "/system_property" -> "/tmp/sy_property"
* NOTE: jffs2 does not support memory mapped file
I patched the init-exec but that didn't help. This isn't the way I expecting this to work. Any help is much appreciated.
Perhaps they got it to work because their /tmp is assigned to ramfs and not to the jffs2 part.
We want the source code of init!
I was lucky to have C-3000, which is equipped with versatile ATA HDD. For the NAND model, yaffs2 might need to be ported.
Cortez, what happens if you go back to run Xzygote, dbus-daemon, runtime instead of init?
-
It would be really great if someone can give some input/suggsetions regarding this.
Can the pre-built Android binaries run on ARMv6 compatible machines? How do we move forward and get the framework properly working on our custom hardware?
Warm Regards,
Anil
i don't know if it is really true but i read somewhere that android can only be run under ARMV5te devices...
EDITED: just found that while googling:
http://benno.id.au/blog/2007/11/21/android-neo1973 (http://benno.id.au/blog/2007/11/21/android-neo1973)
Thanks a lot for this input Does that mean the ARMv6 machines are not backward compatible with ARMv5 instructions?
-
I just installed Angstrom (x11-image-glibc-ipk-2007.12) and tried to see if it works. Same applies here, connection errors on property_service. According to the article here (http://nemustech.blogspot.com/2007/12/android-porting-to-real-target-hw.html) the init executable needs to be patched.
* if you have jffs2 for / patch /init
* modify with hexedit : "/system_property" -> "/tmp/sy_property"
* NOTE: jffs2 does not support memory mapped file
I patched the init-exec but that didn't help. This isn't the way I expecting this to work. Any help is much appreciated.
Perhaps they got it to work because their /tmp is assigned to ramfs and not to the jffs2 part.
We want the source code of init!
I was lucky to have C-3000, which is equipped with versatile ATA HDD. For the NAND model, yaffs2 might need to be ported.
Cortez, what happens if you go back to run Xzygote, dbus-daemon, runtime instead of init?
Running init segfaults after reading the /etc/init.d file. Running zygote, dbus-daemon and runtime instead generates the timeouts. After a long time it displays ++post-zygote, but the timeouts prevent it from continuing I guess.
-
When I had it working on my C1000 zaurus I was running it off of an ext3 formatted USB stick.
-
Help Wanted!
I tried an applet called MusicDroid which can be downloaded from here.
http://www.helloandroid.com/node/166 (http://www.helloandroid.com/node/166)
It is an MP3 player which can play MP3 files on SD card.
http://www.helloandroid.com/node/134 (http://www.helloandroid.com/node/134)
It's an interresting applet to have, isn't it?
But it didn't work on my Android Zaurus.
If you have your Androided Zaurus ready, please let me know how it works on your Z.
Quick instruction for test.
1) Download MusicDroid.zip
2) Unzip it and copy bin/MusicDroid.apk to you android-root/data/app.
3) Load your favorite MP3 files on to an SD card.
4) Boot Android up and click MusicDroid in app folder.
5) See what happens.
o Are MP3 files enumelated correctly?
o Can you hear MP3 file played back?
My case, MP3 files are not listed. Neither I can listen to any sound. I posted an article to my blog on this issue.
Two more issues: sdcard and sound
http://androidzaurus.seesaa.net/article/78452267.html (http://androidzaurus.seesaa.net/article/78452267.html)
Thanks,
-
When I had it working on my C1000 zaurus I was running it off of an ext3 formatted USB stick.
What did you use to do that, Altboot?
-
Pfew, just to let you all know. I finally did it, Android is working on my SL-C1000. I'll post more info on my blog (http://www.omegamoon.com) shortly, including downloads and installation instructions. After this I think it will be a piece of cake to set things up on the C7x0 and C860 series. More on that later.
-
Great ! Our turn now... :-)
-
Noone's tried the C1000 yet?
I'll give it a shot this weekend. Would I be able to just use the same files that the C3000 guys are using? There's no internal HD though..
I'm in if you can get this going on the C1000. My C3200 is set just the way I like it in pdaXii13 5.4.9 and I'm loathe to lose it.
-
I've uploaded all files for the SL-C1000 version and included the installation instructions. I hope the instructions are clear enough, I checked everything twice, and it worked for me. You can check this out at www.omegamoon.com (http://www.omegamoon.com). Good luck and have fun!
-
HI Cortez,
That's awesome. I have been having a lot of issues trying to get Angstrom to build correctly (toolchain).
This is a nice alternative. Now, my question is what do I have to do to get this working on older Zaurus with no
"microdrive". The install script looks for a microdrive and exits. I have an SL-C750 with a 256 MB SD card and a
2GB CF card.
Any help will be appreciated.
Thanks
Regards
Zluver.
Hi,
For the time being posted here in "General Discussion" since there is no dedicated Android subforum (yet). Tested on my SL-C3100, this is a small bootable Poky 2.6.23 kernel with a copy of the Android OS from the SDK (qemu) emulator.
Installation is done in the usual way:
1. Download zImage.bin (http://www.omegamoon.com/zImage.bin), updater.sh (http://www.omegamoon.com/updater.sh), gnu-tar (http://www.omegamoon.com/gnu-tar) and android-root.tar.gz (http://www.omegamoon.com/android-root.tar.gz) and copy the files to a SD card
2. Remove battery and power adapter cable
3. Wait for 5 seconds
4. Replace battery, close and lock battery cover
5. Attach power adapter cable
6. Keep OK button pressed while pressing on/off switch
7. From the Japanese menu, choose option 4 (Update), then 2 (SD) and finally Y
Flashing starts, and you are asked if you want to flash the kernel, if you want the microdrive to be formatted and if you want the root filesystem to be installed.
Accept all questions answering them with y
After flashing is complete, the machine is rebooted. Login with root and type /start to start Android.
This is the basic version, without any of the patches found across the Net.
Have fun, and share your results and findings here please!
Updated: There is a special version for the SL-C1000. Downloads and instructions can be found at www.omegamoon.com (http://www.omegamoon.com)
Greetz,
cortez
-
Cortez, thanks man. Awesome job.
-
I'm in if you can get this going on the C1000. My C3200 is set just the way I like it in pdaXii13 5.4.9 and I'm loathe to lose it.
Thanks Cortez. I'm starting your C1000 image for the first time as I type. Looks really interesting.... More later. Gotta play.
-
HI Cortez,
That's awesome. I have been having a lot of issues trying to get Angstrom to build correctly (toolchain).
This is a nice alternative. Now, my question is what do I have to do to get this working on older Zaurus with no
"microdrive". The install script looks for a microdrive and exits. I have an SL-C750 with a 256 MB SD card and a
2GB CF card.
Any help will be appreciated.
Thanks
Regards
Zluver.
I assume you use the SL-C3x00 install script. Don't use it, use the SL-C1000 script instead. The C1000 doesn't have a microdrive either. What's needed for the SL-C7x0 and SL-C860 series is a kernel and Altboot. Altboot makes it possible to boot from SD instead of the internal flash memory and we need that to make Android work.
-
Alright, I'm just having no luck here. I flashed the console image of Angstrom on my 860 and extracted the /home/root/android-root directory from android-root.tar.gz to /home/root/android-root, copied the binder thing to /lib/mod.../drivers, and copied the doit and start files to /home/root. I ran doit and when running start I get:
=============
Starting Android
=============
'/home/root/android-root/dev/binder' exists
*Booting Android
mount: not found
mount: not found
After a few minutes, the screen went blank. I pressed enter and below the last mount it said "*** post-zygote"
Then it seems to freeze and I'm forced to hard reboot. Any pointers as to what I'm doing wrong? Am I just going to have to wait until there's a release for 7x0 devices?
-
Alright, I'm just having no luck here. I flashed the console image of Angstrom on my 860 and extracted the /home/root/android-root directory from android-root.tar.gz to /home/root/android-root, copied the binder thing to /lib/mod.../drivers, and copied the doit and start files to /home/root. I ran doit and when running start I get:
=============
Starting Android
=============
'/home/root/android-root/dev/binder' exists
*Booting Android
mount: not found
mount: not found
After a few minutes, the screen went blank. I pressed enter and below the last mount it said "*** post-zygote"
Then it seems to freeze and I'm forced to hard reboot. Any pointers as to what I'm doing wrong? Am I just going to have to wait until there's a release for 7x0 devices?
My guess is you're running this from internal flash memory. In that case you're having the same problems as described here (https://www.oesf.org/forum/index.php?s=&showtopic=25292&view=findpost&p=173589). You can try to run strace to see if this is the case. The Altboot solution is a workaround for this problem. I'll upload a kernel + console image for the SL-C7x0 and SL-C860 models shortly if you promise to test and give feedback
-
I've uploaded a kernel and minimal console image for the SL-C7x0 and SL-C860 models. Since I don't have one of these devices myself I need testers to see if it works. Please give me feedback on your results. Files and installation instructions can be found on www.omegamoon.com (http://www.omegamoon.com). Good luck!
-
I've uploaded a kernel and minimal console image for the SL-C7x0 and SL-C860 models. Since I don't have one of these devices myself I need testers to see if it works. Please give me feedback on your results. Files and installation instructions can be found on www.omegamoon.com (http://www.omegamoon.com). Good luck!
Great work you are doing, cortez!
I'll spread the word, well in Japanese again.
By the way, another report of C-860, which is the same hardware with C-760 and loaded with a lot of software.
http://yamashita.dyndns.org/blog/android-on-zaurus/ (http://yamashita.dyndns.org/blog/android-on-zaurus/)
He has done it by mouting android-root image on SD card as a loop device. It is a new technique to get around jffs2-mmap issue. I asked him for detail and I'll post once I get answered.
Cheers,
-
I've uploaded a kernel and minimal console image for the SL-C7x0 and SL-C860 models. Since I don't have one of these devices myself I need testers to see if it works. Please give me feedback on your results. Files and installation instructions can be found on www.omegamoon.com (http://www.omegamoon.com). Good luck!
Great work you are doing, cortez!
I'll spread the word, well in Japanese again.
By the way, another report of C-860, which is the same hardware with C-760 and loaded with a lot of software.
http://yamashita.dyndns.org/blog/android-on-zaurus/ (http://yamashita.dyndns.org/blog/android-on-zaurus/)
He has done it by mouting android-root image on SD card as a loop device. It is a new technique to get around jffs2-mmap issue. I asked him for detail and I'll post once I get answered.
Cheers,
Creating a loop-file is also possible with the aid of Altboot. Choosing Advanced from the bootmenu you have the option to create a loop file from a root.tar.gz archive file. Disadvantage is that a loop-file always has a fixed size which is determined during creation of that file (unless you resize the file of course). A nice Altboot FAQ can be found here (http://www.openzaurus.org/wordpress/howto/the-altboot-faq/).
-
For the time being posted here in "General Discussion" since there is no dedicated Android subforum (yet). Tested on my SL-C3100,
there is now
-
I've uploaded all files for the SL-C1000 version and included the installation instructions. I hope the instructions are clear enough, I checked everything twice, and it worked for me. You can check this out at www.omegamoon.com (http://www.omegamoon.com). Good luck and have fun!
Cortez
Thanks for your great work and steps for C1000!!! Im afraid i need to ask a question which is probably obvious to everyone but me as a Linux newbie. Why is this asking for a Cortex login and password and what is it?
Cheers
Studio
-
I've uploaded all files for the SL-C1000 version and included the installation instructions. I hope the instructions are clear enough, I checked everything twice, and it worked for me. You can check this out at www.omegamoon.com (http://www.omegamoon.com). Good luck and have fun!
Cortez
Thanks for your great work and steps for C1000!!! Im afraid i need to ask a question which is probably obvious to everyone but me as a Linux newbie. Why is this asking for a Cortex login and password and what is it?
Cheers
Studio
Glad you like it. Since this is a non-graphical console image, it asks you to enter a valid username and password on the command line. Cortez is just the machine-name I gave it (you can change it if you like), that's why it shows Cortez login:. Just enter root after the Cortez login: prompt. For this pre-defined (administrator) account no password is required (although it's saver to add a password of course).
-
I've uploaded all files for the SL-C1000 version and included the installation instructions. I hope the instructions are clear enough, I checked everything twice, and it worked for me. You can check this out at www.omegamoon.com (http://www.omegamoon.com). Good luck and have fun!
Cortez
Thanks for your great work and steps for C1000!!! Im afraid i need to ask a question which is probably obvious to everyone but me as a Linux newbie. Why is this asking for a Cortex login and password and what is it?
Cheers
Studio
Glad you like it. Since this is a non-graphical console image, it asks you to enter a valid username and password on the command line. Cortez is just the machine-name I gave it (you can change it if you like), that's why it shows Cortez login:. Just enter root after the Cortez login: prompt. For this pre-defined (administrator) account no password is required (although it's saver to add a password of course).
It works now!! Awesome. Thanks!.
Now i am trying to work out how to connect it to internet with a WiFi CF adapter...
-
I have installed it and I'm a believer!!! Installed no problem on my c3100 following cortez's instructions. I'll deal with the problems in different threads. Great work, very impressive!
-
Creating a loop-file is also possible with the aid of Altboot. Choosing Advanced from the bootmenu you have the option to create a loop file from a root.tar.gz archive file. Disadvantage is that a loop-file always has a fixed size which is determined during creation of that file (unless you resize the file of course). A nice Altboot FAQ can be found here (http://www.openzaurus.org/wordpress/howto/the-altboot-faq/).
The blog author gave me a detail instruction how he did.
http://yamashita.dyndns.org/blog/android-on-zaurus/ (http://yamashita.dyndns.org/blog/android-on-zaurus/)
[div class=\'codetop\']CODE[/div][div class=\'codemain\' style=\'height:200px;white-space:pre;overflow:auto\']$dd if=/dev/null of=/media/card/android.img bs=512 count=131072
$ mkfs.ext2 /media/card/android.img
$ mount -o loop /media/card/android.img /android[/div]
Then copy all the contents of ramdisk.img, system.tar.gz and data.tar.gz to /android and chroot to it.
He says Android runs very slow. Maybe half the speed than what C-3x00 gets. But it could be good enough for easy-goer.
Thanks for the tip about Altboot. Android as Altboot sounds interresting.
Cheers,
-
Thanks for the C1000 instructions Cortez. I think they worked, I am just wondering what I am supposed to be seeing once android is loaded. Touch screen doesn't work and I seem to be stuck in portrait mode. Just wondering if this is what I'm supposed to see. Looks promising, thanks again.
cycle_55
-
Thanks for the C1000 instructions Cortez. I think they worked, I am just wondering what I am supposed to be seeing once android is loaded. Touch screen doesn't work and I seem to be stuck in portrait mode. Just wondering if this is what I'm supposed to see. Looks promising, thanks again.
cycle_55
You're right. What you see is the version 0.01 and much is left to be done. I focused on getting the basic version "as is" on different Zaurus models so more people can give it a try and see what Android is currently and form an opinion on what it could be in potential if more application become available. Bear in mind that the source code of the OS itself is not available yet, so it may well be that a lot of functionality (touchscreen, sound etc) is very hard to hack.
-
I've uploaded a kernel and minimal console image for the SL-C7x0 and SL-C860 models. Since I don't have one of these devices myself I need testers to see if it works. Please give me feedback on your results. Files and installation instructions can be found on www.omegamoon.com (http://www.omegamoon.com). Good luck!
The SL-C7x0/860 version seems to hit an Altboot bug (http://projects.linuxtogo.org/pipermail/openembedded-issues/2007-December/006756.html). It seems there's no patch available (yet) so you might try this workaround (http://projects.linuxtogo.org/pipermail/openembedded-issues/2007-December/007162.html)
-
Thanks for the C1000 instructions Cortez. I think they worked, I am just wondering what I am supposed to be seeing once android is loaded. Touch screen doesn't work and I seem to be stuck in portrait mode. Just wondering if this is what I'm supposed to see. Looks promising, thanks again.
cycle_55
You're right. What you see is the version 0.01 and much is left to be done. I focused on getting the basic version "as is" on different Zaurus models so more people can give it a try and see what Android is currently and form an opinion on what it could be in potential if more application become available. Bear in mind that the source code of the OS itself is not available yet, so it may well be that a lot of functionality (touchscreen, sound etc) is very hard to hack.
Thanks for the great instructions and it is great to see this running on a Z.
-
I demoed android to a colleague at work who has an iPhone - she's a dedicated gadget freak and blogger - and she was very impressed, even though I didn't have working network!
-
Rotten luck, the altboot bugs pop up on my 860 and prevent proper installation. When rebooting from the SD after extracting android-root.tar.gz, it hangs on the copying /home to the loop-image.
The furthest I got so far was booting the standard image and typing reboot, which goes back to the boot selector thing. Selecting the SD option says something that the card is already mounted, but copying /home works and you get the command line eventually. Typing /start gets Android's gears turning, setting up the binder things, then complains that it can't mount stuff, and ultimately hangs up after saying ***post-zygote, the same error stuff as when I tried running Android under Angstrom from flash.
I really hope I get this working some time, it's just too cool to not be able to mess with!
---
Also, on many of my cards (formatted with gparted to ext3), trying to boot from the SD gives:
Checking file system on /dev/mmcblk0p1
/dev/mmcblk0p1 has gone 35814 days without being checked, check forced
then proceeds to freeze. Fooey
-
BTW, does the installer for the c3x00 repartition the disk, or does it rely on the disk being ready for use; if not, what partitioning is recommended?
-
Rotten luck, the altboot bugs pop up on my 860 and prevent proper installation. When rebooting from the SD after extracting android-root.tar.gz, it hangs on the copying /home to the loop-image.
The furthest I got so far was booting the standard image and typing reboot, which goes back to the boot selector thing. Selecting the SD option says something that the card is already mounted, but copying /home works and you get the command line eventually. Typing /start gets Android's gears turning, setting up the binder things, then complains that it can't mount stuff, and ultimately hangs up after saying ***post-zygote, the same error stuff as when I tried running Android under Angstrom from flash.
I really hope I get this working some time, it's just too cool to not be able to mess with!
---
Also, on many of my cards (formatted with gparted to ext3), trying to boot from the SD gives:
Checking file system on /dev/mmcblk0p1
/dev/mmcblk0p1 has gone 35814 days without being checked, check forced
then proceeds to freeze. Fooey
I may have found a way of preventing the system freeze - see https://www.oesf.org/forum/index.php?showtopic=25399 (https://www.oesf.org/forum/index.php?showtopic=25399).
Cheers,
Dan
-
My apology if this is off the track.
I'm working on booting android on a custom made phone equipped with ARM9v5 and following are the steps I've taken:
1. extract cortez's android-root distro to a host directory
2. update and merge my kernel to 2.6.23, including both binder and android drivers
3. nfs mount the rootfs after the device boot up with mounting point /mnt/nfs (unfortunately I don't have the mmc driver working on the device yet)
4. run shell command: $chroot /mnt/nfs/home/root/android-root/ /start
5. double checke that /dev/binder was in right mod after start:
crw-rw-rw- 1 root root 253, 0 2008-01-21 16:40 dev/binder
6. Guess what, I got this famous red cylon bouncing forever on screen
here's the list of start script:
######################
#!/system/bin/sh
echo "* Booting Android"
export PATH=/sbin:/system/sbin:/system/bin:$PATH
export LD_LIBRARY_PATH=/system/lib
export ANDROID_BOOTLOGO=1
export ANDROID_ROOT=/system
export ANDROID_ASSETS=/system/app
export ANDROID_DATA=/data
export EXTERNAL_STORAGE=/sdcard
export DRM_CONTENT=/data/drm/content
mount -t proc proc /proc
mount -t sysfs sysfs /sys
/system/bin/rm /tmp/*
/system/bin/ifconfig lo 127.0.0.1 up
umask 000
/system/bin/app_process -Xzygote /system/bin --zygote &
/system/bin/dbus-daemon --system &
runtime
######################
I also did strace for runtime, and the log file is attached.
Not sure what I did wrong, it would be greeeeeeat if someone can shed some light on this.
thanx
charli
-
5. double checke that /dev/binder was in right mod after start:
crw-rw-rw- 1 root root 253, 0 2008-01-21 16:40 dev/binder
Try chmod 666 /dev/binder in android-root/start again and again.
I'm still don't know why exactly but my case I put sleep 1 between init and chmod.
Android Zaurus: Boot Android up on Zaurus without chroot
http://androidzaurus.seesaa.net/article/79313160.html (http://androidzaurus.seesaa.net/article/79313160.html)
Good luck.
-
Hi Andriod,
Can the google andriod actually drive a cf GPRS card ? If it can
then we can just turn zaurus into a phone !
BR,
Felix.
-
Can the google andriod actually drive a cf GPRS card ? If it can
then we can just turn zaurus into a phone !
I would imagine it can, just need the serial_cs modules so that it can do the AT+ dialup and the ppp link. I will try this very soon.
-
where is the latest released files for c3000, and can we connect passworded networks with android?(if yes-how)
thanks
-
Has this thread totally died? I can't imagine there has been NO progress on Android for Zaurus in nine months!
I do find sites that tell Linux experts how to roll-your-own but no updates on the install files.
Can someone point me in the right direction?
Walt
-
Has this thread totally died? I can't imagine there has been NO progress on Android for Zaurus in nine months!
I do find sites that tell Linux experts how to roll-your-own but no updates on the install files.
Can someone point me in the right direction?
Walt
I have a working Android 0.9i Beta currently, using a patched 2.6.26 kernel. I'll post an image with instructions on my Blog (http://www.omegamoon.com) shortly.
Cheers,
cortez
-
I have a working Android 0.9i Beta currently, using a patched 2.6.26 kernel. I'll post an image with instructions on my Blog (http://www.omegamoon.com) shortly.
Cheers,
cortez
Great! Thank you. I'll be watching your blog.
I really appreciate you Linux Mavens who are willing to share your work with those less technically gifted!
Walt
-
my brother works for google and doesn't have android at all, so this would be a great way of putting one over him :-)
-
Has this thread totally died? I can't imagine there has been NO progress on Android for Zaurus in nine months!
I do find sites that tell Linux experts how to roll-your-own but no updates on the install files.
Can someone point me in the right direction?
Walt
I have a working Android 0.9i Beta currently, using a patched 2.6.26 kernel. I'll post an image with instructions on my Blog (http://www.omegamoon.com) shortly.
Cheers,
cortez
Wow, cortez, what a great job you have done! I really thank you for your great contribution. You work has revived my Zaurus C3200, which has slept for one year. After I have got my N800, it began to sleep. But now, it has a working environment.
But so far, the touch screen doesn't work, so is there any ongoing work? I have read that touch screen for N8x0 seems working, at least there is one patch: http://groups.google.com/group/android-int...c6ff76e0381e95a (http://groups.google.com/group/android-internals/msg/7c6ff76e0381e95a)
Meanwhile, if you can share your kernel source and config, it would be great!
-
Wow, cortez, what a great job you have done! I really thank you for your great contribution. You work has revived my Zaurus C3200, which has slept for one year. After I have got my N800, it began to sleep. But now, it has a working environment.
But so far, the touch screen doesn't work, so is there any ongoing work? I have read that touch screen for N8x0 seems working, at least there is one patch: http://groups.google.com/group/android-int...c6ff76e0381e95a (http://groups.google.com/group/android-internals/msg/7c6ff76e0381e95a)
Meanwhile, if you can share your kernel source and config, it would be great!
Thanks, glad you like it. I'm currently in the process of getting an Akita image ready. I've made adjustments to the touch screen driver, and hope to get that ready in time for the Akita image. Then there is the adjustment AndroidZaurus mentioned for a more graceful exit from Android, by using the Cancel-key on the back. And last but not least, a Tosa is coming my way, so that could mean one more device to support
Cheers,
cortez
-
Wow, cortez, what a great job you have done! I really thank you for your great contribution. You work has revived my Zaurus C3200, which has slept for one year. After I have got my N800, it began to sleep. But now, it has a working environment.
But so far, the touch screen doesn't work, so is there any ongoing work? I have read that touch screen for N8x0 seems working, at least there is one patch: http://groups.google.com/group/android-int...c6ff76e0381e95a (http://groups.google.com/group/android-internals/msg/7c6ff76e0381e95a)
Meanwhile, if you can share your kernel source and config, it would be great!
Thanks, glad you like it. I'm currently in the process of getting an Akita image ready. I've made adjustments to the touch screen driver, and hope to get that ready in time for the Akita image. Then there is the adjustment AndroidZaurus mentioned for a more graceful exit from Android, by using the Cancel-key on the back. And last but not least, a Tosa is coming my way, so that could mean one more device to support
Cheers,
cortez
Thanks.
would you like to tell me how to keep the time accurate from boot to boot?