I did the equivalent up grade with shr-u. Stop the xserver, frameworkd etc before starting and suspend wont happen. Upgrade from a screen session via ssh.
That being said, I had to resort to a one by one to upgrade even though I have 256M swap. And at the end it segfaulted. The result was sort of usable, but so bad that I am going to shr-testing and see if thats any better, or keep my old build for the time being. I was able to disable the dimming (an idiot feature that one :(, but shr-todays new implementation sucks badly, locking the screen and refusing to unlock, fighting with apps like ffalarms so you cant turn the alarm off (seems they both want to be "top", with the result you cant send shr-today a keystroke. It also dies regularly and doesnt appear after suspend. There also seems to be changes to the way suspend works - now it suspends before GSM lock is obtained when booting, with the resultant refusal to register until you reboot and keep tapping the screen to stop suspension - actually hard to do! I think these changes should have been tested more before being moved from unstable to testing. BillK On Tue, 2009-12-22 at 13:01 -0500, Warren Baird wrote: > Thanks! sounds like a great update! I'll try upgrading to it again > from shr-u - and if that fails, I'll try to find time to install it on > a new partition. > > One thing, though - I thought I saw discussions on the irc a while > back that opkg already is grabbing the CPU resource, so prefixing it > with fsoraw doesn't help --- the issue is that on large upgrades, > fsodeviced gets restarted, and then the hold on the CPU resource is > lost... > > Unfortunately I'm not sure that there are options other than tapping > the screen periodically - or cranking the timeout way up... > > Warren > > > On Tue, Dec 22, 2009 at 11:55 AM, Sebastian Spaeth > <[email protected]> wrote: > I just pushed an update to the shr-testing repository. How to > upgrade > and what has changed? > > -------------------------------------------------------------- > Make big upgrades work > -------------------------------------------------------------- > This upgrade will unfortunately require manual attention. Why? > opkg > downloads all upgrades to /tmp (which is in RAM), so for big > upgrades > your RAM will be full even before it starts upgrading. > > There are 2 solutions for this: > > 1. Only install one package at a time, calling opkg > multiple time. > This is quite easy and described here: > http://trac.shr-project.org/trac/wiki/opkg#Installonepackageatatime > 2. Create a swap file that allows to swap out the downloads > on the > SD card. I recommend this anyway: > http://trac.shr-project.org/trac/wiki/swap#Createaswapfile. If > you are > afraid that your SD card will die soon because of this, I > don't think so > and they are cheap anyway, so if you need to buy a new one > every 2 > years, what the heck. > > -------------------------------------------------------------- > Remove SHR-TODAY > -------------------------------------------------------------- > Before starting the upgrade do "opkg remove -force-depends > shr-today". > Opkg *should* be removing this automatically, however > according to some > reports opkg failed to do so (due to opkg stupidness), and > keeping > shr-today seems to cause weird lockups. So get rid of it in > advance. > > -------------------------------------------------------------- > Safety tipp: screen session > -------------------------------------------------------------- > - Do run this upgrade (as in every upgrade) in a screen > session. My FR > display froze during the upgrade (access through ssh still > worked) > - It's a big upgrade unfortunately which takes some time. All > kernel > modules and all the efl stuff seems to have been bumped. > > -------------------------------------------------------------- > What is new: > -------------------------------------------------------------- > - Plenty of changes to the shr phone apps... > - Dimming is now done with a dim phase rather than the simple > on/off. > Timeouts can be set for the Idle and Idle_dim timeouts. To > make these > changes persistent, modify the values in /etc/frameworkd.conf > - python-based shr-today is no more. It is now rewritten in C > and > integrated into the shr UI. It's reportedly faster than the > old lock screen. > > Bugs that I have seen: > - The new idle screen does not show the signal strength for me > - During the opkg upgrade process my phone suspended and this > aborted > the upgrading.... Annoying, I know. I now tap on the screen > while > updating which is pretty silly but.... Of course, what you > should be > doing is to automatically request the CPU resource while > running updates > using this technique: > > http://trac.shr-project.org/trac/wiki/opkg#Preventsuspendwhileupgrading > > To sum it up: if you see mysterious screen hangs, you have > still > shr-today installed and/or running. > _______________________________________________ > Shr-User mailing list > [email protected] > http://lists.shr-project.org/mailman/listinfo/shr-user > > > > -- > Warren Baird - Photographer and Digital Artist > http://www.synergisticimages.ca > _______________________________________________ > Shr-User mailing list > [email protected] > http://lists.shr-project.org/mailman/listinfo/shr-user -- William Kenworthy <[email protected]> Home in Perth! _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
