Posts Tagged ‘Froyo’

Here we come again, alpha3 of FroYo for A5IT

Saturday, October 30th, 2010

It’s been a while, we all were very busy and as nobody new stepped up to help with things this alpha3 took longer than it was expected. It would have taken even longer but we decided to make a cut and release what we have so far.

The following tickets were resolved on our way to alpha3:

Ticket Summary Resolution
#103 Continuous reboot worksforme
#104 most recent initramfs/zImage seems to break MSC under Archos Android fixed
#112 live wallpaper make device hot (also in standby) worksforme
#72 Audio not working fixed
#111 browser crashed occasionally duplicate
#115 lsusb showing wrong ID and ADB not working worksforme
#117 Native ABI mismatch from package file fixed
#94 strace from alpha1 broken fixed
#95 update busybox+busybox config fixed
#113 adobe flash 10.1 plugin not supported duplicate
#114 Full Screen Feature Needed: Same Feature Like in 1.6 (Full Screen For All Appz) duplicate
#89 dpi 195 is correct, but results in large ui elements and text fixed
#118 permissions on /mnt_data/download restricts market defect
The following tickets sadly didn’t get fixed/resolved yet. If you see one where you could help. PLEASE do so!
Ticket Summary Type
#107 Menu Line Missing: Even after duplicating lines defect
#126 need to provide encrypted storage for some apps enhancement
#93 sitting idle with power disconnected turns off defect
#92 brief press of power button does not put unit to sleep defect
#100 openvpn support enhancement
#109 Wifi unable to stop defect
#110 browser crashed occasionally defect
#116 GPS not working defect
#71 Accelerometer not working defect
#73 Bluetooth not working. defect
#84 Add IPv6 module enhancement
#122 Notification bar in Google Maps defect
#123 Sleep Error defect
#77 Touch Screen Calibration App enhancement
#101 external sd card does not get automounted on boot defect
#120 AppsLib does not recognize the device as an Archos device defect
#121 Change mount location of internal storage defect

and for the beta1 target:

Ticket Summary Type
#125 grep logic in boot menu doesn’t do exact match, tries to mount e.g. two rootfs’ defect
#105 Update Battery code with new algorithm for higher accuracy. defect
#108 DSP link enhancement

Again: Send patches! Discuss on the mailing list! Show some support by investing some time into this. Things don’t do themselves magically.

Keep in mind:
  • In general this is still alpha grade code so don’t expect wonders in stability and functionality.
  • If you find an issue that is not yet reported then file a new issue! If you do not report it we don’t know it and nobody can notice it and try to resolve it!
  • This is still not really intended for the average end user. If you are one, don’t come complaining that “stuff doesn’t work”. Just be happy that some ‘stuff’ works. ;)
  • Please note that we had to disable the Android root console on cdc-acm-serial1 due to stability problems. You should use ADB instead!
  • We require a working installation of the regular 1.6 Archos firmware as FroYo depends on a few files found in it!

Alpha3 is tested and works together with this zImage and this initramfs.
Please install those or preferably most recent before reporting bugs.

Oh yeah, if you just want the image: here it is and the md5sum.
Everyone else please follow the guide on the wiki which will help you install the most recent release.
Special thanks to Janis605 for creating the wonderful boot animation for us!

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.

Closer to Archdruid Froyo Alpha 1 – again a video

Monday, August 30th, 2010

Second video today.
We’ve supplied Furies with some updated binaries and the latest SGX enabled Froyo build from internal testing. Also checked things to make sure we will be able to distribute an image.

This video is what we got back:

Sure looks nice.

As soon as we get our hands on the necessary steps and scripts we’ll spin an Archdruid Froyo Alpha 1 image for all the impatient people out there.

bootnote: Alpha 1 should give you an idea what we think about general stability and buggyness. If you want something as stable as the Archos firmware come back in a few months at the earliest. Currently there are e.g. still power management issues that make the unit randomly freeze.