User:Graziano
From Openmoko
Line 38: | Line 38: | ||
=== NOT OK === | === NOT OK === | ||
* keyboard too small! | * keyboard too small! | ||
− | possible solutions: | + | possible solutions: |
− | * | + | functioning rotation (omnewrotate) included by default + illume keyboard |
+ | (i INSTALLED OMNEWROTATE BUT ILLUME KEYBOARD DISAPPEARS WHEN FREERUNNER IS IN LANDSCAPE MODE) | ||
+ | |||
+ | OR | ||
+ | |||
+ | different larger keyboard (literki?) | ||
+ | |||
+ | |||
+ | * scrolling pages in all apps | ||
it requires more pressure than usual, scrolling is not smooth | it requires more pressure than usual, scrolling is not smooth | ||
=== OK === | === OK === | ||
− | * slide | + | * slide |
− | * opening apps in home screen | + | * opening apps in home screen |
− | * making a call | + | * making a call |
+ | * phone log | ||
+ | * alarm setting | ||
+ | * calculator | ||
+ | * mokonnect scanning wifi networks | ||
+ | * SHR Settings | ||
+ | * browsing with Ventura | ||
+ | |||
+ | |||
Line 56: | Line 72: | ||
I don't think it's a good place. We should have them on the upper bar (as android) or in the lower buttons (as mac os mobile) | I don't think it's a good place. We should have them on the upper bar (as android) or in the lower buttons (as mac os mobile) | ||
* automatically detect wifi networks and login to a chosen default one (via mokonnect?) | * automatically detect wifi networks and login to a chosen default one (via mokonnect?) | ||
+ | * clock shows wrong time after reboot (you set it, save, reboot and it shows the wrong time) | ||
* tab menu to switch between dialer, contacts and call logs | * tab menu to switch between dialer, contacts and call logs |
Revision as of 12:20, 26 February 2010
Contents |
My name is Graziano Sorbaioli and I am a free software activist.
Device:
- Neo Freerunner A7+ bought from Golden delicious (highly recommended! Shipment to Italy in 3 working days)
- SHR LITE Testing
I want to hack on the Freerunner in the fields of usability and User Interface.
I own an HTC Dream with Android 1.6 and CyanogenMOD ROM.
Since the stability and maturity of the Dream and Android I am going to compare it to the Freerunner to see differences and
where we can improve.
Some random ideas:
Boot Time
How long do both phones take to be up and running? (aka cold start)
HTC Dream (Android 1.6 + cyanogenmod rom 4.5) about 2 minutes
Neo Freerunner A7+ (SHR LITE Testing - 2010 25th January) 1,40 minutes
Finger Friendly
All apps in android are finger friendly, what about SHR testing?
NOT OK
- keyboard too small!
possible solutions:
functioning rotation (omnewrotate) included by default + illume keyboard (i INSTALLED OMNEWROTATE BUT ILLUME KEYBOARD DISAPPEARS WHEN FREERUNNER IS IN LANDSCAPE MODE)
OR
different larger keyboard (literki?)
- scrolling pages in all apps
it requires more pressure than usual, scrolling is not smooth
OK
- slide
- opening apps in home screen
- making a call
- phone log
- alarm setting
- calculator
- mokonnect scanning wifi networks
- SHR Settings
- browsing with Ventura
Suggestions for SHR
- notifications: currently I see them only when I wake up the phone pressing the power button.
I don't think it's a good place. We should have them on the upper bar (as android) or in the lower buttons (as mac os mobile)
- automatically detect wifi networks and login to a chosen default one (via mokonnect?)
- clock shows wrong time after reboot (you set it, save, reboot and it shows the wrong time)
- tab menu to switch between dialer, contacts and call logs
- "copy to sim" button inside the contact details window
- SHR FULL should have ventura browser, calendar, email, music, vocal recorder apps preinstalled
- SHR LITE should have at least the calendar app preinstalled
- long press in home screen = background choice
Feedback
- small keyboard - it should fit the side borders of the screen, larger buttons
omnewrotate and literki
- opkg graphic application (om-showroom app?)
Wait for dos1 to fix shr-installer app.
- SIM application Toolkit aka SAT support
<DocScrutinizer> graziano: that SIM applications. Not supported by FSO <DocScrutinizer> it's complex, and most devels agree on we don't want to have to disable it, once FSO has implemented it <DocScrutinizer> as you don't have real control over that crap