Re: clarification re easy OpenMoko updating for average consumer
Ron K. Jeffries wrote: As an Ubuntu *user* every now and then I get an alert that upgrades are available. Likewise with other major distros like Fedora -- you get an alert that upgrades are available when you login, or come back from an idle state overnight (nightly cron job I imagine). In the case of the Freerunner though, if updates are available, we should give the user the option of upgrading everything automagically, without ever prompting them, or letting them manually update. Not saying this is necessarily the way to go because some other mobile OS does this, but my Blackjack 2 running Windows Mobile 6 gives me the option of manually looking for updates and manually applying them, or just letting the phone do things on its own. Of course, *because* it's Windows I don't let it do anything automatically... But from an end user perspective, if we want to reach non-techies (or as Ron put it, people with IQ's less than 175), should we even prompt for a password when the root user doesn't even *have* a password? Unless we prompt the user upon first boot-up of the phone to enter a security passphrase for things like updates, locking the phone from any use, locking the phone for international calls, etc. Just my $0.02. -id ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: clarification re easy OpenMoko updating for average consumer
On Thu, 15 May 2008 13:58:40 -0700 ian douglas [EMAIL PROTECTED] wrote: In the case of the Freerunner though, if updates are available, we should give the user the option of upgrading everything automagically, without ever prompting them, or letting them manually update. We should disable this on GRPS/GSM unless the user specifically asks for it as it would cost quite a lot to download all updates over the mobile network. Also maybe doing major updates while on battery should be disabled (certainly while battery is low) just to avoid any problems (bricked phone) solar.george ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: clarification re easy OpenMoko updating for average consumer
On 15 May 2008, at 19:37, Ron K. Jeffries wrote: ... As an Ubuntu *user* every now and then I get an alert that upgrades are available. If I say yes it automagically fires up a package manager. I enter the my root password, and a few minutes later it's a done deal. Smooth, easy... for a major Ubuntu upgrade, e,g from Gutsy 7.10 to Hardy 8.04, I select an upgrade button, and sit back while magic happened. ... I did NOT lose my address book, either. g I don't see why you would expect it to be much different on Openmoko. I would expect most users to update their phones this way, and 3rd- party repositories CVS/SVN archives to be available for those who want bleeding edge. Stroller. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: clarification re easy OpenMoko updating for average consumer
Seems that there is already a Moko-Manager project http://projects.openmoko.org/projects/openmokomanager/ I was unable to run it yet but it got screen shoots ian douglas [EMAIL PROTECTED] escribió: Ron K. Jeffries wrote: As an Ubuntu *user* every now and then I get an alert that upgrades are available. Likewise with other major distros like Fedora -- you get an alert that upgrades are available when you login, or come back from an idle state overnight (nightly cron job I imagine). In the case of the Freerunner though, if updates are available, we should give the user the option of upgrading everything automagically, without ever prompting them, or letting them manually update. Not saying this is necessarily the way to go because some other mobile OS does this, but my Blackjack 2 running Windows Mobile 6 gives me the option of manually looking for updates and manually applying them, or just letting the phone do things on its own. Of course, *because* it's Windows I don't let it do anything automatically... But from an end user perspective, if we want to reach non-techies (or as Ron put it, people with IQ's less than 175), should we even prompt for a password when the root user doesn't even *have* a password? Unless we prompt the user upon first boot-up of the phone to enter a security passphrase for things like updates, locking the phone from any use, locking the phone for international calls, etc. Just my $0.02. -id ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community - Enviado desde Correo Yahoo! La bandeja de entrada más inteligente. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: clarification re easy OpenMoko updating for average consumer
On Thu, 2008-05-15 at 23:48 +0100, George Brooke wrote: Also maybe doing major updates while on battery should be disabled (certainly while battery is low) just to avoid any problems (bricked phone) How about it downloads the updates whenever wifi is available (battery or not), and then (if set to update automatically) updates once plugged in to charge, and if set to manual requires battery power to be above a certain percentage. Mo. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: clarification re easy OpenMoko updating for average consumer
Mo Abrahams wrote: How about it downloads the updates whenever wifi is available (battery or not), and then (if set to update automatically) updates once plugged in to charge, and if set to manual requires battery power to be above a certain percentage. I'd say that if GSM downloads are going to be slow, then downloads should also occur if the phone is plugged into a PC and network bridging is set up -- not everyone will have a wifi router. Since the updates will require a certain amount of time and battery power, the update should only happen once the battery power is above a certain level whether plugged in for charging or not. For example, if the battery was completely drained, and the user plugs it into a PC, if the charger can't keep up with the drain of installing updates, then updates shouldn't happen just because it's plugged into a charger. Thoughts? -id ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: clarification re easy OpenMoko updating for average consumer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think the user should decide, wheter the update should be done at once or later. Of cource an advise of batterystate should be done. Greetings Bastian ian douglas schrieb: | Mo Abrahams wrote: | How about it downloads the updates whenever wifi is available (battery | or not), and then (if set to update automatically) updates once plugged | in to charge, and if set to manual requires battery power to be above a | certain percentage. | | I'd say that if GSM downloads are going to be slow, then downloads should also occur if the phone is plugged into a PC and network bridging is set up -- not everyone will have a wifi router. | | Since the updates will require a certain amount of time and battery power, the update should only happen once the battery power is above a certain level whether plugged in for charging or not. | | For example, if the battery was completely drained, and the user plugs it into a PC, if the charger can't keep up with the drain of installing updates, then updates shouldn't happen just because it's plugged into a charger. | | Thoughts? | | -id | | ___ | Openmoko community mailing list | community@lists.openmoko.org | http://lists.openmoko.org/mailman/listinfo/community | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFILNBzlYiDScJJ+7QRAkoZAJ9UE9CPLsd1Ew1yr1A4yRZvlTHfPACeLA7q Nc6IhZQqMFiGrXtg8nq7pzU= =f3P1 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: clarification re easy OpenMoko updating for average consumer
That's something I thought some time ago, but it was not possible 'couse there are too many possible hardware combinations. But we don't have that on the Freerunner. It would be nice to add to the description of every package, app or update the time it take to install it. I mean, we can calculate the time it takes to download from the spped of the connection, and we ask the developers to add the times it takes to install to the description of the software, or even devel an app wich times it. Perhaps also could show and/or share that data. Just a thought. Happy waiting. Kosa - Un mundo mejor es posible . Bu we don't have that on te Freerunner ian douglas escribió: Mo Abrahams wrote: How about it downloads the updates whenever wifi is available (battery or not), and then (if set to update automatically) updates once plugged in to charge, and if set to manual requires battery power to be above a certain percentage. I'd say that if GSM downloads are going to be slow, then downloads should also occur if the phone is plugged into a PC and network bridging is set up -- not everyone will have a wifi router. Since the updates will require a certain amount of time and battery power, the update should only happen once the battery power is above a certain level whether plugged in for charging or not. For example, if the battery was completely drained, and the user plugs it into a PC, if the charger can't keep up with the drain of installing updates, then updates shouldn't happen just because it's plugged into a charger. Thoughts? -id ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
