OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Android => Topic started by: cortez on March 03, 2008, 04:39:10 pm
-
Sorry for the delay, but I had some trouble uploading the files to my site.
The image files and installation instructions can be obtained from my website (http://www.omegamoon.com/blog/index.php?entry=entry080303-221250)
Have fun!
-
Thank you!! Testing now!
**EDIT: I'd like a bit of help. I didn't want to format my whole microdrive so I just used gnu-tar to untar the image to the first partition of my microdrive (ext3). I then flashed the provided kernel renaming it zImage and with the standard updater.sh from Sharp. So far, everything is good, android boots!
BUT, when running /start, I get stuck at the red thingy moving
Is there something to do, or is my way of installing wrong in the first place? Is there something to do with alboot at the beginning?
-
Press Fn+Left cursor to see if there are any errors shown on the console, or else change the last line in /home/root/android-root/start from /init to
strace -ff -F -tt -s 200 -o /data/logs/log-init /initThen run /start, be patient, press Fn+Left to see the console, then press Ctrl+Alt, and while keeping these pressed press Menu (release), Home (release), Menu(release)... until you see a line with all sorts off options. This is while keeping Ctrl+Alt pressed all the time. When you see this line, keep Ctrl+Alt pressed and then press I to exit Android gracefully. Now look at the logfiles in /home/root/android-root/data/logs to see what the problem is.
-
just red line but don't start window
error:
sh: can't access tty: job control turned off
-
just red line but don't start window
error:
sh: can't access tty: job control turned off
I see the same message on my working system, so that's "normal"
-
ok it's normal but don't start , I'm waiting for a long time...I'm can see just the red line
-
ok it's normal but don't start , I'm waiting for a long time...I'm can see just the red line
Same thing here.
I'm getting this errors on the console:
PANIC: handle_group_exit: xxxx leader xxxx
repeated, where xxxx are different everytime.
attached is the log-init file with the lowest number. there are many after a while.
-
Yea, it scrolls errors faster than I can read. It does install nicely though.
-
I'll re-check the complete installation to see what's going on, and come back to you asap with the results.
-
I see that Google released a new version of the SDK yesterday, which resolves the issue of the incorrect handling of BMP images (wasn't even aware of that being an issue). I'll try to incorporate that as well.
-
I have an updated image ready, but I'm currently unable to upload it. It will have to wait until tonight I'm afraid.
I have yet to find out what the problem was with the previous image. Really strange
-
Thanks cortez, I'm waiting
-
New image is uploaded here (android-root.tar.gz) (http://www.omegamoon.com/blog/index.php?entry=entry080303-221250). Please give it another try. Strange thing for me was after startup the screen stays black. When pressing any key the boot process continues. I don't know why this is. When time permits I'll try to fix this.
-
woohoo, thanks cortez, I'll try it on my c3100 within the next day and report back.
-
just installed on my c3000 ! it works !!!
-i had the black screen bug, solved by pressing the return key
-new interface, which seems much much faster than first version !!!
-no touchscreen working (perhaps it needs some conf file tweaking)
-screen is rotated (is androidzaurus' rotage apk working? i'm trying !)
so far i'm very impressed by the speed, once it boots
-
Got it to work as well!! Very very nice!!! THANKS!
#things that didn't go well: didn't manage to connect to the network, neither with lan nor wireless cf. But I guess I'm just an idiot.
#Android on zaurus is sexy!! I can't wait for it to be my main rom.
-
the first time it ran, my c3100 took a very long time to start up and I thought I'd be looking at the "nightrider eye" (or is a cylon) forever!
eventually it did start, so I was pretty wowed.
I've managed to get WEP wifi up at home, didn't seem to want to connect to work's WPA access point. I had to hack /etc/resolv.conf and /etc/network/interfaces though, set a manual IP + mask + route as it reports bad protocol when udhcpc runs, it's still very finicky. Locked up Z, hard reset (nice there's a button in the battery compartment)
Not actually managed to use the android web browser yet, but hopefully very very soon!
--edit-- rebooted, this time the manual settings in /etc/network/interfaces worked and I could ping www.google.com straight off.
fired up android and the browser, it reports "Page Load Suspended
No network coverage. Load will resume when network connection recovers"
--edit2-- my wireless access point is a linux box with intel 2915abg minipci card, so I can sniff the lan and do interesting stuff; when android browser fires up, I see no traffic, so it's not even trying to talk to the network. bummer. Went back to console, Z got upset, reboot time.
--edit3-- do I need to do the net.eth0.dns trick? hmm, I can use FN-left to switch back to the console, but weirdly android is still getting every key press too! Tried killing android process off, Z locks up, reset
--edit4-- aha, when the Z brings up wlan0 (ifup wlan0=home), I have to ping it from the gateway and then wlan0 works, otherwise Z can't ping the linux server. ok, I left a ping running, so know the Z is definitely online, but android cannot see the network. still no traffic on gateway. maps work, but when I scroll off the edge, I get a blank space and it pops up the no network alert.
no sound, no touchscreen either.
-
fired up android and the browser, it reports "Page Load Suspended
No network coverage. Lod will resume when network connection recovers"
I think that 3G is stuff. We can ignore it for now.
Did you set net.eth0.dns1 in etc/default.prop?
-
fired up android and the browser, it reports "Page Load Suspended
No network coverage. Lod will resume when network connection recovers"
I think that 3G is stuff. We can ignore it for now.
Did you set net.eth0.dns1 in etc/default.prop?
d'oh, Z locked up. don't know why I bother to put battery cover back on. BTW, you do know you can get to the flash menu by pressing the reset button in the battery compartment, ensuring cover lock is slid towards battery, hold OK and turn on? no need to remove battery and disconnect power at all. You also need to ensure you don't leave a card in the slot - my 4GB non-sdhc card breaks it.
anyway, where was I.. oh yes!
er, I used net.eth0.dns, so I will addnet.eth0.dns1 too.
woohoo! yes, it works. I still got the page load suspended but it still did the google search! Woohoo! (my wife, at this point, is reaching for the phone to call a psychiatrist and telling me not to wake our child (it's nearly 23:00)!)
browser seems to stall for no reason. trcpdump indicates lack of activity, can still ping.
wahay, I googled for "android zaurus" and got androidzaurus.seesaa blog site.
the home screen is now getting pretty full of icons... not sure how I close down all those apps. the FN button always seems to bring up the dialler, alphanumeric keys kick off a contact search.
damn, this is impressive stuff!!!
-
I demonstrated android at work, one of the guys worked on some 3G phone stuff and was quite impressed that it was even possible! I showed off the browser, hitting a few sites, and apart from having to hit enter a few times on some links, it worked very well. If barfed when I went to www.taptu.mobi, searched for some music and tried to play a sample, crashing android (but not the Z), the red dot reappeared, then android screen came back and it worked again.
I had to put my laptop into ad-hoc mode and use it as a gateway to the corporate lan, as I didn't get wpa wifi to work.
-
I totally forgot about updating my RotateView to m5-rc14/rc15. Just uploaded to my blog.
o Android Zaurus: RotateView for Android SDK m5-rc14/rc15 (http://androidzaurus.seesaa.net/article/89043507.html)
Eventhough I made some improvement in double buffer handling of frame buffer driver, still rotating display eats a lot of CPU power. A lot slower than portrait view.
Have fun.
-
I totally forgot about updating my RotateView to m5-rc14/rc15. Just uploaded to my blog.
o Android Zaurus: RotateView for Android SDK m5-rc14/rc15 (http://androidzaurus.seesaa.net/article/89043507.html)
Eventhough I made some improvement in double buffer handling of frame buffer driver, still rotating display eats a lot of CPU power. A lot slower than portrait view.
thanks for that. it's odd that android doesn't have the intelligence to handle rotated frame buffers, surely by now people have realised that hard-wired display resolutions is just stupid (I'm looking at you, PalmOS and Microsoft PocketPC!)
-
Sorry for the delay, but I had some trouble uploading the files to my site.
The image files and installation instructions can be obtained from my website (http://www.omegamoon.com/blog/index.php?entry=entry080303-221250)
Have fun!
Does any one have this working on a sl-6000 yet? I have been trying using the sd instructions w/ Angstrom but with no success.
-
A hacker in Japan successfully runs m5-rc14 on C700! His blog is written in Japanese, so I translated roughly.
o Android Zaurus: Android m5-rc14 on Zaurus C700 (http://androidzaurus.seesaa.net/article/93200205.html)
Very interesting news here is, frame buffer driver of C700 (w100fb.c) doesn't have double buffer support. Double buffer may not be mandatory for some cases. I'll update if there's any progress.
Cheers,
-
Finally, touchscreen driver has been fixed. Now touchscreen works correctly.
Android Zaurus: Touchscreen works!
http://androidzaurus.seesaa.net/article/96581331.html (http://androidzaurus.seesaa.net/article/96581331.html)
A reader of my blog has done a great job! Big thanks to Rebecca.
Cheers,
-
If anyone feels in a generous mood, could we have a new android image?
Thanks
matthis