Archive for August, 2010

Archos releases updated GPL sources for gen7 devices

Thursday, August 5th, 2010

The sources released today contain kernel source for the 2.0.x line of Archos firmware. Especially the SGX/EGL kernel module sources are included which will be important for our FroYo and MeeGo endeavors.

We will soon start to sync the openAOS kernel to those sources.

Thanks Archos!

50£ for the first person to deliver working WiFi on Froyo!

Wednesday, August 4th, 2010

This gained momentum way faster than I expected. After some very interesting discussion I was surprised by this:

15:03:44< AlSutton> I'm going to put up 50 GBP (~ 60 EUR) for the first person to deliver working WiFi on Froyo that gets Gr8Ks approval.
15:04:50< AlSutton> When Gr8K gets back he can check the code, confirm it works, and then the payment will be made.
15:05:37< AlSutton> Payment will be via PayPal, and documentation on how to get the WiFi working needs to be included
15:08:10< AlSutton> Unless Gr8K has any objections I'm happy to let the fun begin... :)
15:08:44<@dm8tbr> AlSutton: in this case it wouldn't be that easy to keep the 'completely FOSS' rule though. the ti driver is not GPL. neither is the wpa_supplicant with the load of TI patches.
15:09:52< AlSutton> In the case it needs non-GPLed code it can do what the Nexus One Froyo build does; include a script to pull it from a known location (e.g. existing firmware / device)
15:11:00<+Gr8K> dm8tbr: no pb with the bounty
15:12:32< AlSutton> The N1 script to pull files from the device & put them in the build tree is at
http://android.git.kernel.org/?p=device/htc/passion.git;a=blob;f=extract-files.sh;h=afc97d5b5bd777843873c72f39946e018ce07015;hb=froyo-release in case anyone wants an example

(Parts not relevant to the bounty have been omitted)

The bounty is being offered by AndAppStore.

Hack the planet!

Should we start a feature-bounty programme?

Wednesday, August 4th, 2010

A thought that partly springs from necessity. I was thinking it might be nice to start a feature-bounty programme.

How would that work? Users that want a special feature implemented within the openAOS ecosystem would pledge to pay some amount of money or would put some amount of money into a deposit/escrow. Then if someone implements this feature the person would receive this amount. People could also pool their money to make it more attractive to implement a feature.

Why the idea? Hackers are often selfish people. Most of the time they implement things they need for themselves or that give them personal pleasure for tackling them. This may not be what non-programmer users would like to have as new features. Also a feature might be nice but only useful for very few people or not useful for the people potentially implementing it.

So what would be the benefits?

  • Features with popular demand would be implemented faster
  • People who want features that might not be popular could raise the chance of those being implemented
  • Features that may be harder to implement but more desirable than  others would get implemented faster
  • Faster development due to the monetary incentive
  • Developers may feel more rewarded for their work

I guess I should expand on the last one: the openAOS project has been around for more than half a year now, the openPMA project for much longer. We have done pretty nice things on many generations of Archos products. Many people have downloaded our alternative firmwares and our Linux builds. We spent weeks or months developing hacks, programs or just analyzing Archos hardware and software. But what did we get in return? A few people said ‘thanks’ or ‘great job’, but the majority of voices and feeback was “this doesn’t work!” or “But I want this [totally uncommon] feature, why didn’t you think of implementing it!” or other not very encouraging things.

We’d like to feel more appreciated!

And I mean it, if you can’t donate, but like what we did, just say ‘thanks’ it makes a day so much nicer! People of the ArchosFans forum, I’m looking at you! People with an genuine FOSS background already do. But back to the topic. I think – although not the ultimate solution – it would help both sides if there would be some transfer of monetary units involved. The users would get a feeling that TANSTAFL and the people working to make openAOS better could buy themselves a beer after a hard weekend of coding.

How is this different from commercial software you may ask or you might say that I’m trying to commercialize openAOS. Far from this, very very very far. Why? If a bounty is claimed a new feature is made available not only to the person who paid for it but to everyone who would like to use it, also the source code will be open – there is a reason this is called openAOS!

Thoughts? Critique? Rants? Praise? Flaming?- The comment section is open!

Thomas, your friendly neighbourhood Archdruid

Froyo Archos5IT update – touchscreen working

Monday, August 2nd, 2010

Gr8K put a lot of effort in and got the touchscreen working! Congratulations on this result of his hard work!

We won’t be keeping you in suspense, here’s the video:

I haven’t tried the image yet myself, but I’ve been told there are still many problems to solve.

Gr8k is also working on getting things into a nice GIT repository so it will be easier to join in. Expect updates on that as soon as things pan out.

That’s all for tonight folks!

Thomas, your friendly ArchDruid

PS: Image not available for general public due to pre-alpha status, but feel free to pop by on IRC if you want to help fixing bugs. Requests for ‘gimmeh gimmeh image’ will be ignored!