Screen Shot Of Applications Running On Opie/angstrom

zroadmap 1.1.0 (with 2006 US street map)

Angstrom Status On Tosa

Get it here: Get Angstrom Unstable Release for tosa The latest tested release is r8 (kernel 2.6.23).

Working out-of-box

altboot with loopback image or direct fs
Kernel 2.6.23 (testing 2.6.24 for >= r9) Tosa kernel status from Dmitry
Images: Opie 1.2.3 (core opie application feed, other opie or qt applications not in the feed yet) and GPE 2.8 (x11-image) with match-box as default WM
Keyboard (keymap changed in 2.6.24)
Internal Wifi (wlan-ng-modules-usb 2.8) 802.11b WEP only, no WPA
SD: non-sdhc or sdhc (tested with 4GB card of both)
CF and 2nd CF on sled

OE Tosa Meta-Bug

Outstanding critical bugs:

1. suspend/resume OE bug 2134
[Closed] 2. sound system OE bug 3518 Speaker/Headphone tested working. Mic/phone untested

Major bugs:

[Hacked kdrive in x11-image to overcome the problem, still an issue in opie-image] 1. frame buffer (a.k.a, screen corruption or the famous yellow vertical lines) : occurs "occasionally" with 2.6.23 kernel, much better than "often" with 2.6.17 kernel OE bug 490

Opie bugs: file Opie bug tracker

GPE bugs: file GPE bug tracker

Kernel, roofs or packaging bugs: file OE bug tracker


Not tested yet:
?USB host
?Speaker/Headphone/Headset/Mic (need to fix the alsa state in r9)
USB client
USB network
Mic (the one on the back of the device) / PhoneMic (2.5mm jack used with a headset)
etc.

Oesf Wiki Needs Love And Care

everybody knows the situation, without further adieu, I volunteer to take care of the following sections: SL-6000, VoIP, "Secret" Key Combinations, GPS, and will likely spill over as time permits. I will encourage people to contribute and glean information from the forum and digest them into the wiki.

Somebody will argue the wiki server (ibilio) is shaky due to the recent outages. However it is still very useful for lots of users.

How Many Kernel Branches For A Single Device

Please help me to understand the current kernel status for Tosa (or other Z breed):

pdaXrom: 2.4.18 and 2.6.xx

OZ: 2.4.18 (old) and 2.6.18

along the line of sharp compatible rom

Cacko: 2.4.18
Tetsu special kernel: 2.4.18
guyhelm: 2.4.18 (a.k.a. common kernel)

for the various 2.4.18 kernels, are most of patches same or equivalent? Are they all stemming from a common well patched version? Is it worth to dig into each one to find the best patch available or am I wasting my time?

Tosa Development Plan

As most of your know the 6000L is an odd breed compared to other Zauri, esp the clamshells, where availability and dev activities are high. Hence Tosa ROM version is behind others except for OZ/Angstrom where the key dev. Hrw has the device.

Current Tosa ROM status in the other popular rom is pretty disappointing

PdaXrom: beta1
Cacko: None

I've been whining for a long time without contributing. Part of the reason is that I don't know where should my effort go. I have to admit that I'm not even close to software engineer in trade and pretty inexperienced in the whole thing. But I'm pretty confident in my learning ability to get some Tosa dev going.

For a starter, I'm interested to advance PdaXrom to a stable/usable 2.4 kernel, similar to what Meanie did for pdaXii. (weed out bugs, etc. ) Who else is interested and have time to contribute? We probably need some sort of infrastructure (svn, emaillist, bugtracker, etc.) Could we borrow what's available in the PdaXrom site? Should we get together and form a team?

Btw, anybody interested in a Cacko ROM for Tosa?

I can probably commit half an hour per day for the project after my thesis defense.