Archive for May, 2010

A demo Image using the Enlightenment WM

Wednesday, May 12th, 2010

Hello all.

I’ve been wanting to make angstrom more user friendly for some time, so I decided to start working on an e17 Illume build.  There were a bunch things I didn’t like about the current gpe build — the xkbd being too small, midori web browser being too chunky, the lack of overall user friendliness of the UI, amongst other small issues mostly revolving around functionality of Angstrom.

This image that I’ve compiled addresses these issues as well as others such as:

  • A more user friendly interface (Illume)
  • Increased size of buttons and fonts (Scaling)
  • Removal of misc. programs (broken programs and programs incompatible with e17)
  • An increased file system of 1Gb
  • Selection of 3 web browsers – Fennec, Woosh and Dillo (warning: fennec is still a WIP and will crash when loading larger pages due to RAM restrictions on Gen6 devices)
  • OptimSMS2 keyboard layout
  • Quasar Media Player (Mplayer frontend)
  • ePDFviewer
  • Abiword Word Processor
  • Numpty Physics (Neat little physics game)

This image is base on Kevin’s build of the revision 199 of openAOS Ångström overlay. All additional packages have been installed from the regular Ångström package feeds with the exception of Dillo, Woosh, NumptyPhysics and Quasar (which I modified together with some help from Thomas, dm8tbr [thanks m8!!]) and for which sources and bitbake recipe are available here.

Some screenshots (desktop will look different on the downloaded image due to additional software installation):

Main Desktop

Archos gen6 running e17 - main view

Archos gen6 running e17 - main view

Illumes “Top-Shelf” (note: Vkeyboard button is located in the top-right corner “qwerty“)

OptimSMS2 Keyboard (Switch between kbd layouts by hitting “ABC” [above letter"P"])

Archos gen6 running e17 - screen keyboard

Archos gen6 running e17 - OptimSMS2 on-screen keyboard

Quasar UI

Archos gen6 running e17 - running Quasar
Archos gen6 running e17 – running Quasar

OptimSMS keyboard still needs a bit more work, it’s a bit too large right now, but still very usable.  I may get around to finding a way to reduce the size of the container.  Look for that update.  I also kept the “transparent keyboard” active for use, and I have my custom xkbd layout defaulted (mimics OptimSMS2 layout).

There is also a known issue with the Battery Meter being broken.  Hopefully we can fix that soon.  If anyone wants to try, go right ahead.  :)

This image should need minimal adjusting, as we have worked to import all my custom e17′s settings into your home.img, so you should not have to go through the initialization process.  However, if you with to do so, goto “Settings->Settings->Profiles” and select the “Default” profile to run through the initialization process.  I would also suggest increasing the Terminal font size (click the “Look and Feel” icon, goto the “Terminal” tab and increase to the desired font size).  You will have to restart in order for those changes to take effect.

Grab your copy of the E17 Image HERE.**

**updated to beta2 build as described HERE

[ If you wish to run this along side your current build, rename image to "illume.img" and make the appropriate entry in "menu.lst" Otherwise just overwrite your "rootfs.img" and your good to go.]

~Cheers

Spz0.

openAOS brings you: ArchDruid – Android 2.0 for gen7!

Tuesday, May 11th, 2010

We are proud to be the first ones to have a public preview of Android 2.0 (eclair) on 7th generation Archos devices (Archos5IT).

Mind you, this is not an Archos build and none of the multimedia functionality would work right now. It just shows that even with the current 2.6.27.10 Linux kernel the device is able to boot an Android 2.0 user-space and bring up the UI. I’ll repeat this. If Archos releases an Android 2.0 firmware it will be very much different!

empty home screen

home screen

Given the ease with which I was able to modify an existing build of Android 2.0 to run on my device and get rid of most of the error messages – I have to say I have no idea why nobody else has done this yet. But this is kind of symptomatic for the Archos “community”. The loudest to cry out and demand but no one is even able to get their behind up and try it themselves. It took me less than an hour to have the GUI up and running.

locked screen

locked screen

One major downside at the moment is that the touchscreen driver is not cooperating. If someone wants to help and try to make it work – please contact me.

I/InputDevice.ReadPointercalFile: (  956): t.x1=796.0 t.y1=0.0 t.z1=-95501.0t.x2=0.0 t.y2=508.0 t.z2=-116804.0t.s=3830.0  
I/KeyInputQueue(  956): Device added: id=0x10002, name=ADS784x Touchscreen, classes=14                                    
I/KeyInputQueue(  956):   X: unknown values                                                                               
I/KeyInputQueue(  956):   Y: unknown values                                                                               
I/KeyInputQueue(  956):   Pressure: unknown values                                                                        
I/KeyInputQueue(  956):   Size: unknown values                                                                            

If all you want to ask is “Can haz newist Image!?” – shove it, don’t even bother, if there will be updated images you’ll find the information about it on this blog.

Meanwhile you have something nice to look at:

boot animation

boot animation

and you can brag how you were among the “fr!st evar!” to boot Android 2.0 outside of Archos R&D on an Archos5IT.

Disclaimer: If this image makes your Archos bite your dog or eat your cat or otherwise damages the device or causes the Doomsday Machine to activate. – Tough luck, no cookies.
That said nothing bad has happened to my unit yet, but you never know.

That all said, if you still want to try or god forbid even want to help: here’s a bzip’ed image for you. Use something like this for the menu:

Android_2.0|/dev/sda1|/archdruid_0_0_1.img|/init

Ah and the original build is from here (qdroid).

That’d be all for today folks. Check back for a video soon.

Thomas, your friendly openAOS Archdruid

Just for fun: openAOS boots Maemo/Mer oh and Meego too, ’cause we can!

Friday, May 7th, 2010

This is more of an “oh-look-shiny” thing right now.

I’d like to EMPHASIZE this: Currently we do not support Mer on Archos hardware! This is just an proof of concept!

Gaap asked me on IRC today how to try Maemo/Mer on his A5IT. – Turns out it was very easy.

  1. You take: Mer build for SmartQ5 (Touchbook might work even better I guess)
  2. Throw that into an 500M+ ext3 image.
  3. For good measure throw in some parts of the original Archos SDE images.
  4. Modify menu.lst (the image needs /sbin/init)
  5. profit!

Here are two short videos by Ian58 and spz0:

To get this far you need to go through the first boot assistant. Notice that the screen calibration will be totally off and you need to aim a bit to the side. When you manage to hit an input field the virtual keyboard will show up.

Update: If you like watching paint dry you’ll also like this one: Meego code drop 20100331 repackaged for Archos

Please note, that this is just an proof of concept and nowhere near seriously usable. It just happens to work (a bit). But if someone wants to step up and properly port that or later Meego to Archos hardware. We’re very much open to it. Just contact us for hints and some help!

Mozilla Firefox Mobile – Fennec 1.1Beta1 now also in openAOS for gen7 (and gen6) Archos devices

Wednesday, May 5th, 2010

I’ve been working on this project on the side for a few weeks, but I’ve actually been eyeing it far longer. I’ve been affiliated to the Mozilla project for a few years and I’ve even been hoping to get something gecko based working on my PMA back then, but it just was not possible.

Now with openAOS running Ångström it was quite easy. I took an older BitBake recipe first devised by Koen and adapted it until it would build the source now known as Firefox Mobile 1.1 beta 1.

Mozilla Fennec 1.1b1c2 displaying the openAOS webpage

Mozilla Fennec 1.1b1c2 displaying the openAOS webpage

At first I was missing a patch and things were quite slow. But then I fixed a few things:

  • Reworked against current source a native-bpp patch
  • Installed the quick-fix tslib driver (as known from gen6) to calm down the touch screen
  • Fixed the keymap like on gen6 to have a lower repeat rate
Fennec start screen on an Archos5IT

Fennec start screen on an Archos5IT

Now Fennec (the code name for the Firefox Mobile project) is running a lot more smooth. Its still not a 100% match to the Android browser but quite close. But it sure beats it by giving me access to such cool AddOns like AdBlock Plus!

Side-notes: It does also run on gen6, but it comes currently with a huge caveat. It will run out of memory and crash easily. If you run an kernel that does not reserve RAM for AVOS then it runs quite fine as it then has 30M to fill.

I did – out of sheer curiosity – try to make the flash plugins shipped with the original Archos firmwares work, but failed. They are compiled against µclibc, we run glibc, some libraries have conflicting versions, unresolved symbols are the result.

Another nice thing is that Ångström is pretty simmilar to Maemo, so we get the regular 1.1 beta1 quality (plus the odd bugs that always creep in) and don’t have to run around with an “pre alpha” label like the Android version. ;-)   – Please note though even only very small bits of the source have been changed that this is not an official Mozilla build.

Fennec showing archoslounge on an Archos5IT

Fennec showing archoslounge and its tab sidebar on an Archos5IT

The updated recipes will surface soon in our svn. In addition I’m going to push this updated recipe to Koen for general inclusion in Ångström.

Oh and the installation packages can be had here:

http://www.openaos.org/tmp/fennec/

As this is only an temporary preview this link will die sooner or later as the package will either be pre-installed on our Images or will be available from an package feed.

NOTE for gen7: Please note that you won’t get network access if you don’t run it as root or add your user to the group 3003 (cf issue #59)