On Sun, 2009-12-20 at 13:34 +0100, Klaus 'mrmoku' Kurzmann wrote: > On Sun, 20 Dec 2009, William Kenworthy wrote: > > > I updated shr-u yesterday and ran into some critical problems. > > > The start at 80% brightness sounds good in theory, but in summer > > sunshine, that isnt an option as you cant even see if the phone is on > > unless you can find some shade. Coupled to this is the dim in 5 seconds > > and you lose another random amount of brightness (doesnt seem to be a > > constant amount?) so even indoors its not good. > > > There are also problems with trying to save power settings which dont > > work as already mentioned on the list, so you cant work around the dim > > problem. I tried to edit the settings in frameworkd.conf but that didnt > > have the desired result either. I dont have a problem with the dim > > option as some people might like it, but I would like a way to disable > > it where its use is impractical, and be able to specify 100% startup > > brightness :( > you can do that :) It is configurable in /etc/phonefsod.conf in the > [idle] section: > default_brightness = 100 > > you can completely switch off dimming too... comment out the three dim_* > config values and it won't dim. > > > The dim also seems to get confused if you use fsoraw to hold the display > > or ffalarms which dims the display itself. The end result is the screen > > keeps dimming in steps until its invisible, and requires manual > > intervention to get it back. Another reason to want to disable it :( > > > The changes in shr-today havent been too good either - no battery or > > phone icons on the today screen and several times it disappeared and > > required a full reboot before it would work again. The old-shr-today has > > been removed. > One problem I see is on startup... phoneuid tries to get the values for > signal and stuff on start... and FSO is not ready yet at that point in > the boot sequence :| Needs to be fixed. After doing a 'killall phoneuid' > once the values are all correct for me though... > > > Maybe I had a bad update (had a segfault towards the end), but others > > seem to have problems too. > > > BillK > tkx, I'll try upgrading again and fix these annoyances :)
BillK _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
