Posts Tagged ‘multiroot’

Updated Gingerbread image for gen8

Friday, July 8th, 2011

BuBU has built an image based on the latest openAOS and CM code:

  • improved bluetooth (BT HID confirmed working)
  • workaround for web browser crash
  • default homepage is openaos.org
  • Archos community bookmarks
  • other

The latest image is openaos-gingerbread-gen8-20110708_183154.img.gz (md5sum).
Confirmed working with boot menu version featured here.

If you are new please be warned that this is still experimental and bugs are expected, for installation instructions continue reading here.

Gen7 code compiles but is not ready for public images. If you want to build it yourself for gen7 or gen8 here are some instructions.

New week, new boot menu version

Tuesday, July 5th, 2011

BuBU made significant improvements to the gen8 boot menu, so we’ve decided to make a blog post.

Note that this is still work in progress so you should actually follow (and link to) the boot menu guide on the developer wiki.

http://dev.openaos.org/wiki/SettingUpMultiRootGen8

Most notable recent improvements:

  • new advanced menu which appear in OS selection (which lead to a new menu with debugging (serial stuff), recovery, reboot, disable rooted device, disable comcache)
  • other important feature is check validity for /file.img if does not exists it shows a list of available *.img under storage and it magically fix the menu.lst with the selected entry
  • fixed the touchscreen issue (under debian/other OSes)
  • difference between standard and debug is that the menu for serial appears early in initramfs
  • for both debug/standard you can switch serial… if you selected NONE initially.. u can go back in advanced menu > DEBUGGING to change to Ether or if u selected Ether you can got to same place to change to Both (or None or whatever)
  • Booting off partitions including µSD card partitions
  • IPv6 support in kernel

We plan to bring as many features as possible to the gen7 boot menu too in the near future so stay tuned.

Please report all problems on IRC and or to our issue tracker!

Here are the files for the impatient who know what they are doing:

https://openaos.org/wp-upload/gen8/2011-07-05/

An interim fix for booting Android and Ångström

Wednesday, September 15th, 2010

Bubu worked out how to tweak the kernel with fbset to do what we want.

A known working snapshot is here:

https://openaos.org/wp-upload/gen7/2010-09-15/

You’ll most likely only need the zImage and initramfs.

He added an temporary extension to the menu.lst structure. If you add ‘|1′ then fbset will set the framebuffer like in the original SDE kernel (e.g. for Ångström). If you add ‘|0′ then it will be set like for the Archos firmware and FroYo. In addition it tries to guess the right defaults: Everything gets the old 24 bit framebuffer unless it is: Archos firmware or the menu entry name contains ‘android’ or ‘froyo’, then it is set to the new mode.

Example for an android froyo override:
MyDroid|/dev/sda1|/rootfs.img|/init|0

Example for an linux image using SDE framebuffer override:
MyLinux|/dev/sda1|/rootfs.img|/sbin/init|1

This is a temporary hack though. We will rework the menu.lst structure to be more flexible in terms of options.

Froyo Alpha1 a quick summary

Wednesday, September 8th, 2010

It looks like we’ll be trying to get an alpha2 out sooner than we thought.
There are various issues we’ve found.
The most annoying is the random shutdown which was caused by a typo. There are also some other problems with the initramfs not working 100% as we’d like (serial debugging doesn’t activet or if it activates the kernel log is missing, the menu.lst is not generated/extended automatically, etc.)

We’ll keep you posted.

For more info on what’s been discovered, fixed or still open please check this report on our developer pages.

openAOS brings you: FroYo alpha1 for Archos 5 IT!

Sunday, September 5th, 2010

We had some early development snapshots already, but for an real alpha version we said we want to fix at least WiFi and SGX. For WiFi we even had an bounty and I guess this image is best proof that the bounty has been earned. Furies did the work on it. Thanks to AndAppStore for sponsoring the bounty!

Well we don’t want to make the tension unbearable here is the image:

FroYo Alpha1 for Archos5IT

This also needs this boot-menu update: zImage and initramfs.¹

Enjoy your FroYo! Here are the much easier new instructions for setting up the boot-menu if you haven’t yet.

This image needs the following line added to menu.lst (do NOT use notepad! use an editor capable of proper unix line endings!):

openAOS Froyo alpha|/dev/sda1|/rootfsfroyo.img|/init

This all comes with a bootnote, a rather extensive one:

  • This is alpha grade software intended for developers and tech-savy testers.
  • There are still many unresolved issues and problems.
  • If you ‘just want FroYo’ – this is not for you! Wait until it’s stable and usable.
  • If you don’t plan to give us feedback – this is not for you! Wait until it’s stable and usable.
  • If you expect everything to work – this is not for you! Wait until it’s stable and usable.
  • After this has been said, thank you very much you seriously want to help us with this. We appreciate this very much as we really need every help we can get!
  • If you notice anything that doesn’t feel right, please file an ticket and
    use Android 2.2 Alpha2 as the target milestone
    and Android 2.2 – alpha1 as the version
  • Please do the same if you want some feature included or something improved
  • First boot will take very long! Keep your USB cable connected.
    • First the rootfs gets unzipped (You can unzip it on your PC that’s much faster!)
    • The Android cache is compiled – this can also take a while, just watch the boot logo while this happens.
  • Please join the mailing-list to discuss this image!
  • Want to see if someone is online right now to ask a question or discuss? Join us on IRC!
  • Yes sound does not work, sorry. Next Alpha maybe.
  • Don’t want to install the alpha but still want to help? Consider donating to the openAOS project!

¹ please note that the default Ångström image needs to be modified to work with this kernel! adding the command ‘fbset -nonstd 0′ could fix at least part of the issue during boot process. Expect updates on this soon.