Improving user experience
From Openmoko
(Difference between revisions)
Line 1: | Line 1: | ||
+ | '''Please check the discussion page''' | ||
+ | |||
=Overview= | =Overview= | ||
Line 44: | Line 46: | ||
** opkg: faster algorithm | ** opkg: faster algorithm | ||
− | |||
− | |||
− | |||
[[Category:Community]] | [[Category:Community]] |
Revision as of 19:56, 17 October 2008
Please check the discussion page
Overview
Like Wolfgang said in http://n2.nabble.com/Weekly-Engineering-News-41-2008-td1336450.html , Openmoko assembled a team to focus on improving the user experience. The focus and coverage of this group is:
- We improve the current stack instead of creating new features.
- Prefer stuffs which could be brought over to gta03 instead of gta02/om2008 specific.
- Won't work on om2007 stack. Won't do hardware.
- May cooperate with Paroli, FSO or system team but we're not them.
- Will work on Qtopia but with lower priority.
ToDO
Here is the current draft and it will be updated frequently.
- call quality
- echo (in testing #1267)
- volume (alsa-state?)
- Reduce boot time
- Optimize the touch screen driver on freerunner for finger usage.
- A generic python loader to enhance the start up time of python scripts.
- qtopia
- bugfix
- program startup speed
- response time
- network
- scripts: resolv.conf, etc.
Evaluating
- suspend/resume
- take a screenshot before suspend. display it on screen first thing on resume.
- do not suspend when usb connected, qtopia indexing, etc.
- qtopia
- change the button order of "end call" or "ans call"
- put speaker button on the dialer app
- peripherals
- LED & button behavior FreeRunner/Buttons and LEDs, FreeRunner LED signals
- illume: disable suspend by power button when screen blanked
- LED & button behavior FreeRunner/Buttons and LEDs, FreeRunner LED signals
- devices (command line improvement first)
- GPRS
- bluetooth
- wifi userspace
- misc
- opkg: faster algorithm