What about the wifi and bluetooth hardware? I could use double tap for services (and hardware?) and single taps for everything else. And if hardware is to use double should the flight mode button use double tap to enter flight mode and single to enter normal mode or single for both modes?

To toggle the d-pad between UI navigation and whatever you actions you have bound to the d-pad (volume, brightness or rotation).

--

The test binary fixes problems when transitioning from off but charging to full on and prevents the wakeup screen tap from activating anything in ASUI. If you like the test binary just rename it to /usr/bin/advanced-systemui and restart service.

Are there any other problems that aren't documented in red on the todo page?

Uploaded another test binary that requires a double tap (two taps within half a second of each other) to start or stop all services. If the service is yellow then it only takes a single tap on either side to start or stop it.

It also ignores any taps on a button that is highlighted blue so if you tap a button and nothing happens you can tap it again to wake up X. If you did this before it would process both taps causing the button to flip to the state you wanted and then flip back from the second tap. Each button tracks its own taps so you can still tap another button while one is blue and the second button will activate when the first is finished. The buttons that open dialogs or rotate the screen ignore all taps that happen while the dialog is opening or the screen is rotating.

seems to work ok.

I don't know if the new test binary has an option for double tap, but I certainly don't want it as the right half of my screen requires a pretty hard press. I don't have a stylus.

New test binary with a setting to disable double taps. Also has new brightness and volume sliders with single step buttons.

Here is the last test binary before next release.

Main loop timer code has been redone making it easier to add more timers in the future and X is polled every 250ms when a button is down. This doesn't fix the problem with X not waking the main loop immediately for some button up events but the continuous polling should significantly reduce time from tap to action. Let me know if this new code screwed something up.

- Swiping from button bar to widgets will work better now
- Fullscreen clock now requires a downward swipe to close
- Long press is required to open governor dialog
- Volume and brightness sliders can now be dragged
- Process viewer is now updated while being scrolled with finger

The code to set brightness is cpu intensive and can't track like the volume slider does.

seriously grateful for the effort your putting into this.

one thought on the brightness slider, perhaps rather then changing the brightness every time it moves, have it change after the screen is released or the slider have been motionless for a second or so.

A second is a time too large for feedback. 0.1 second is much better, while keeping the cpu load low. I'd suggest that for X polling too.

The brightness slider in test binary was accidentally set to process motion every 10µs but I've since changed it to 100ms. Not much of a difference though.

Changing the X polling from 250ms to 100ms would probably just waste cpu cycles since the button release event can take longer than 250ms to become available.

advanced-systemui (0.3.0)

• fix: power button no longer maps/unmaps when in minimal mode
• fix: detect transition from runlevel 5 to 2 and switch to full interface
• fix: battery is polled in minimal interface since it doesn't appear to send signals in the charged state
• fix: the tap used to unblank display will not be processed
• fix: when stopping wifi/bluetooth services, sleep to allow icd/bluez time to turn off hardware
• fix: swipe from buttons to widgets to unmap window is now easier to do
• fix: X is polled for button release events to reduce tap lag
• better handling of timers in the main loop
• power button to startup message in minimal interface
• moved desktop start/stop ticks above the indicator
• gray ticks when starting wifi and bluetooth services
• all services require a double tap to start/stop, but only single tap if yellow
• setting to disable double taps
• tap throttling for action duration plus 500ms
• brightness and volume icons instead of text
• brightness and volume single step buttons
• draggable brightness and volume sliders
• fullscreen clock now requires a downward swipe to close
• governor dialog now requires a long press to open
• smooth scrolling in process viewer
• brightness timer updates current brightness every 100ms until it matches set value
• brightness value changes position when 'dimmed' or current value isn't displayed below it
• /etc/asui-svc file to control systemui and charging runlevel

This release adds the two changes to the brightness value and the /etc/asui-svc file in addition to the changes released in test binaries. You need to restart the service whenever you change the ASUI_CHARGING variable in that file.