![]() |
Re: [Announce] advanced-systemui
Quote:
Quote:
Quote:
Lock&blank and blank will not override the blanking pause either and result in the same notification. Quote:
What is your timeout from dim to blank? Power button will dim the screen if another key is required to unlock, but if your dim->blank timeout was near zero it might cause problems. If the screen is off and locked then power button requires another key to unlock or none if you prefer the old way, you can change it in the settings. If the screen is locked and has dimmed then power button will blank the screen. It is important that is has dimmed because MCE will dim it after power button has blanked the screen causing it to turn back on. |
Re: [Announce] advanced-systemui
Quote:
As for the power button long press, i held it down for a couple of seconds, then on release the screen would light up and give me a "press fullscreen to unlock" message. big case of :o on my part right now. Sorry for the thread noise. |
Re: [Announce] advanced-systemui
Quote:
After posting the previous question I took a careful look at the installed software in both App managers, and then I spotted the difference : 810 has CSSU, 800 did not... My mistake ! After adding the CSSU to the 800 and rebooting, ASUI is back to its normal behaviour... sorry for the corner case :-) I did spot another niggling detail though (probably nothing to do with ASUI) : on the 800, in Cpanel/Navigation, I can uncheck the standard Maemo battery icon, and check the ASUI one in its place. On the 810 I can't because the Maemo icon is greyed out (and checked), so I'd end up with two. Strange. |
Re: [Announce] advanced-systemui
Quote:
Just need to figure out what bug is causing your screen to re-blank after short pressing power button, since your dim->blank timeout isn't causing it. Quote:
Quote:
Code:
sed -i "s:^Mandatory=true$:#Mandatory=true:g" /usr/share/applications/hildon-status-bar/hildon-status-bar-battery.desktop |
Re: [Announce] advanced-systemui
Quote:
Quote:
Quote:
|
Re: [Announce] advanced-systemui
While adding alarm support I managed to get devlock working properly and have it showing the keypad at boot up. :)
I then discovered that the maemo-control-services plugin puts all services at S/K20 causing several of them to die hundreds of times during boot and never start. The alarm service is one of them but moving it to a higher value got it to start. Could one of you who hasn't used that plugin or tampered with the rc links run ls /etc/rc?.d/ and send me the output? |
Re: [Announce] advanced-systemui
That's why I run from mmc :D
This is from a qemu vm running unmodified diablo. Code:
Nokia-N800-:/etc/rc1.d# ls |
Re: [Announce] advanced-systemui
The libxpm4 dependancy is in the Maemo sdk/tools repository so I replaced the install file on the download page to keep the number of installed repos down for anyone who already had that one.
Pressing the power key will dim the screen if a secondary key is required to unlock. Problem is that if dim timeout is equal to blank timeout then the screen skips the dim stage and goes straight to blank. You will need to set the secondary key to none until I release a fix. |
Re: [Announce] advanced-systemui
So I hadn't realized that Canola2 had its own "Remain Lit While Charging" setting. I've now turned that off, but have the system "remains-lit" still set to "while charging." Things seem to be behaving as expected now.
With Canola's setting turned on, I was frequently seeing that the Lock&Blank and Blank would not blank, and also that Lock&Blank would not consistently lock. It seemed that, for instance, after seeing the "an app may have paused blanking" notification and then "screen is locked, will blank in 60 seconds" notification, that screen taps would be recognized. Then, on pressing the power button, a notification "screen and keys active." |
Re: [Announce] advanced-systemui
advanced-systemui (0.5.2)
|
| All times are GMT. The time now is 20:19. |
vBulletin® Version 3.8.8