On 12/23/09 07:27, William Kenworthy wrote: > 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.
The new lock screen works fine for me (once the old shr-today was really gone and I rebootet), I tested that on my FR for quite a while before pushing. Sorry to hear that it broke things for you. > 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! Yes, this is just the way it behaves now. No amount of testing would ever have changed that. Actually it always used to behave that way, it was just that odeviced was so slow in starting up that you had time to enter your PIN before it suspended, I think. I have no idea how suspend can be prevented now. Proabably phonefsod should be trying to request the CPU resource until GSM registration suceeds. Care to file a trac ticket to have that implemented? > I think these changes should have been tested more before being moved > from unstable to testing. See above, I did test the first and there is little I can do about the 2nd as long as this is not solved "upstream".... spaetz _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
