Thread: [Announce] advanced-systemui (ASUI)
View Single Post
auouymous is offline auouymous
2011-03-28 , 07:03
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#463
New test binary.
  • fix: screen should no longer turn back on when device becomes locked either from secure button or idle timeout
  • fix: blanking pause notification should no longer randomly appear when screen has been off longer than 6 seconds
  • fix: battery widget should no longer black out half the keypad clock in portrait mode
  • alarm volume gradually increases and then snoozes

I'll add settings later to configure alarm volume steps and duration.


Originally Posted by heavyt View Post
The following steps take place before the alarm alarms at the set time of 4pm as an example:

1.) Set the alarm for 4pm tomorrow with the clock app.

2.) long pressing of the power key will not power down the unit, instead the ASUI window is displayed showing the time and that the unit is being charge but the charger is not being used.

3.) If I had not long pressed the power key in step 2 but had short pressed the key to bring up the ASUI window, then touch the power off icon in that window the unit will power down.
I am not able to reproduce this with an alarm set by clock app or large statusbar clock. Is anyone else able to? What happens if you stop ASUI and long press? What happens if you start SystemUI and long press it?

It may appear to be ASUI related but isn't, I hope. Hal always sends a power button signal as soon as the button is touched and ASUI responds to this, it doesn't matter if you short or long press it. MCE is responsible for keeping track of how long the button is held down and then powering down the device. But now that ASUI listens on the system_ui interface I can have it map/unmap on the powerkeymenu_open method call from MCE so it won't respond to long presses.
 

The Following User Says Thank You to auouymous For This Useful Post: