I guess Archos again licensed TI proprietary code for the WiLink6 driver. Haven't checked though.

The approach I took with gen7 (see openaos blog post on this) to get wifi working should also work with gen8.

go into recovery and 'upgrade firmware' or what it was called...

you could explore the Angstrom world, install a few applications etc.

I think we already solved this on IRC.
JFTR here the solution: go into ArchosHelper and modify the settings there. e.g. setting it to PM profile for Video will prevent it from sleeping.

Sure it's possible, be a hero and make it happen.

The file extension is irrelevant. It's what the file is what is really relevant.

In this case it is a raw ext3 filesystem image.

I'm no expert on the topic, but I imagine it would be similar to a BeagleBoard. Aaaaand he scores! Spot on! Gen6-8 are all quite similar to the BB (with slight variations of the SoC). This is why openAOS is in close contact with the BB community. Really helps. Actually I like to call them BB in a s...

that's a really cool vid, but doesn't really help us in dual-booting. i mean its a great step and all.... anyhow. i think, because we can't boot from usb, Please have a look over here: http://forum.archosfans.com/viewtopic.php?p=300429#p300429 there needs to be a way to edit the archos firmware fil...

The guide mentioned in the first post uses g_ether and ssh login to get access to the Angstrom installation and run a debootstrap directly on the device. I seem to remember there was an easier way to debootstrap on an x86 system and then just copy over the resulting image. In the end once you start ...

The menu.lst should be automatically generated and populated by the initramdisk script that runs on every boot. Note that Archos Android 1.6 will NOT show until you properly copy the firmware to NAND. The easiest way to do this is follow the howto and not leave out any steps. If you don't succeed th...

That is exactly what I expected. Thank you for clarifying that...I dont think everyone realizes that. With that said, How can we use Angstrom to put Ubuntu on? We must write it into the firmware. So where do we even start to begin? It's amusing how this repeats for every SDE so far. The first thing...

I just wondering, has ANYONE every installed a proper debian on their A5IT (gen 7)? Even booted to desktop or just commandline? Sure, I could serial debug, learn that too, post all the logs... But before I start, is it more that theoretically possible... HAVE YOU DEBIAN-ED? Yes there are people who...

I am a developer and my favorite plaform has been Qt on Linux. Currently Lighthouse is progressing to bring a wealth of apps to Android through Qt. It's also now part of Nokia so it's in MeeGo, which I'm very impressed with for tablets. Then you'll run into us sooner or later, in person or on IRC. ...

There is already a medical device project based on the gen7 unit. It uses both the USB host/slave functionality as well as the UART accessible from its docking port.

The driver part is quite straight forward. I guess you want to use X11 for your application GUI anyway?

All you need are the Android patches for the kernel and the necessary ABI changes etc.

2.6.32 is a recommendation if you go with vanilla and want to have an easy time applying the Android kernel patch.

Missing USB-ID in ini files for ADB. this is an FAQ.

FTR again: If you want to flash an AOS file through recovery it has to have 100% the exact filename like on the Archos server. Add a '1' or 'foo' to the filename and it will just silently fail and reboot.

The devil is in the details, in this case in the surrounding chips.
YMMV. Flashing an openAOS froyo rootfs on an other device is 99,9% likely to fail craptacularly if no proper steps are taken to adapt it.

There are a few quite unlikely corner-cases where you can really get into a state where no recovery is possible. The Archos page for the SDE says: don't install if you don't know what you're doing. At least if you run an openAOS kernel or compile from openAOS sources then overwriting the boot-loader...

It's a terrific idea! Just drop the 'open development' part in the name please! Like you did in the topic of this message. Then All the 'can haz r00tz' / Android hacking / whatever cracking /  people can congregate there. For open development my point stands: Gen6, Gen7 and Gen8 are fairly simmil...