Hi, I will try to answer in one letter both to Tom and Al, and would add couple more items - see below:
I am using uImage-2.6.29-oe11+gitr119861+b90406de472c1aa5371ab593a2bb79136d5de658-r6-om-gta02.bin shr-full-eglibc-ipk--20091204-om-gta02.rootfs.jffs2 Not upgraded. BTW, I tried to ssh into the device with empty password but it would simple would not let me in. Only when I manually run "passwd" in terminal and put single letter as a password, it allowed me to login. As /etc/ssh/sshd_config assumes "PermitEmptyPasswords no", it is mandatory to set password for root. Not a big deal, but should be mentioned in the documentation: http://wiki.openmoko.org/wiki/SHR_User_Manual IMHO, the welcome screen for the phone should either include link to the manual on the internet or to have "README" in it. Power also brings up the menu to let you suspend or shut down. > Aux toggles the screen lock. I find this very useful when pocketing the > phone > while still powered, as when recording gps tracklogs. > On Android, pressing Power for a second suspends the phone as well. Pressing for 3 seconds opens a menu allowing to shutdown the phone. "Screen locking while phone is suspended" is such a rare operation that it looks unrational to use whole HW button just for that. The OS must allow scenario when application can request continue running even if the user "suspended" the phone. This is done nicely in android. I don't want to start POV fights, just want to note, that Google have poured a lot of money into designing android look and feel, so it should not be a shame to borrow from them an idea or two. Most apps don't have one to invoke, or have it present all the time. More > seriously we don't have any consistent application style rules. This is > partly because many of the apps are generic linux apps that happen to be > usable (just > about) on a 480x640 screen. > This is the point that one must admit that phone UI is different from desktop UI. The fact that SHR does not have any UI guidelines speaks for itself. * Default suspend time is very short - mere 15 seconds >> > You can change that in config, the default is *not* 15 seconds though. it's > more like 60 (which is too long in my pov) you probably consider screen > blanking as suspend. > Could well be. > * The AUX(Back) and Power(Menu) buttons are *very* intuitive on android. >> They are almost not used in SHR: >> > That's what you get when you use specifically designed software, we use > mostly regular linux apps, which means we don't have apps that respect > special keys for menus. > Exactly. See my list of recommendations for SHR at the end. > * numpty once locked up hard, so I could not kill it. Software power off >> did not work either... Had to remove the battery. >> > kill -9 ? > No, this answer is not acceptable. You can't ask users to do kill -9. SHR must be smart enough to kill the application no matter what. Android does it right by detecting unresponsive application automatically and offering to kill it - without user intervention whatsoever! You are free to ignore that if you want the SHR to remain OS for the ever-shrinking already-tiny market of FR phones. Before we continue with this thread, I would like to do a small poll: Please write here what you see as advantages of SHR distro against android system. -- Arie
_______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
