Sunday, November 02, 2008

Back to basics: Update

We are now 2 weeks (and a few days) after Openmoko announced the 'back to basics' plan. Let's look at the changes.

After one week they had all of us fooled. Most of us thought Openmoko hadn't done a thing. But a day later they gave us a rather long list of things they had done. Also this week, they have worked on the plan and they even got a real name, the 'Optimization' team.

What are the main things they did?

  • The main problem with the touchscreen is when you try to scroll through a list. It's hard to keep your finger on the screen the whole time. Sometimes you lift your finger of the touchscreen and the FreeRunner things you clicked somewhere. That's now solved in 'testing' image, because those finger presses are filtered if they happen withing 0.3 sec of each other.
  • Secondly they fixed the testing images. It wouldn't start because of some Wifi trouble. After that, they still have some trouble with the newest release of illume. (Some applications will not launch.)
  • The echo when someone is calling to the FreeRunner should be solved, but a part of the people are still complaining of the echo. So Openmoko is looking into making a new firmware of the calypso gsm modem. They got green light of TI for letting the users upgrade their calypso modem themselves. (Thank you TI) Plus they have hired someone new for diving into that chip in particularly. Also they are still experimenting with alsa state file for better audio quality, but it's hard to find an alsa state file that works for everyone.
  • Also there's made an image with the speedup's from previous week.
  • The Optimization team is also looking into the suspend/resume issues. Nothing earthshaking is happened on these issues, except they are analyzing the issues.
Official status report

2 reacties:

TreviƱo said...

Nice to read...

Btw about the modem firmware upgrading, joerg posted a wiki with the instruction and the packages needed to perform this task! ;)

We're just waiting for an improved fw image ;)

lindner_marek said...

Little correction from my side:
The testing image never had boot problems because of the wifi. If you read the mentioned bug (2071) carefully you will notice that the initial guess pointed to the wifi driver. After starting to debug this issue it became apparent that changes within EFL caused all the trouble which was fixed by later updates.