Active Topics
-
Old stuff for Nokia 770 (0)
to Nokia 770 by teroyk - 17 mins ago - more...
|
2011-04-26
, 02:54
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#582
|
Another ASUI test binary.
For me, screenshot-tool takes twice as long as the delay value before it snaps. Let me know if this happens for you so I can have ASUI halve the time it passes to screenshot-tool.
- screenshot button doesn't block ASUI while waiting for delay
- play sound after screenshot has been taken
- time_in_state percentages for each cpu clock on governor/dsp dialog
- changed to short tap instead of long to open governor/dsp dialog
For me, screenshot-tool takes twice as long as the delay value before it snaps. Let me know if this happens for you so I can have ASUI halve the time it passes to screenshot-tool.
| The Following User Says Thank You to auouymous For This Useful Post: | ||
|
|
2011-04-26
, 23:58
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#583
|
New test binary.
Screenshot code was moved out of the ASUI binary and into a script (not included with this test) that is launched by ASUI. So if you want to test the button editor and don't care about screenshots for a day or two...
Rotation buttons can be moved but not to the secondary page. Landscape and portrait also share the same layout.
- fix: widget editor page number was in the wrong location for portrait mode
- button positioning can be changed by the user
Screenshot code was moved out of the ASUI binary and into a script (not included with this test) that is launched by ASUI. So if you want to test the button editor and don't care about screenshots for a day or two...
Rotation buttons can be moved but not to the secondary page. Landscape and portrait also share the same layout.
| The Following User Says Thank You to auouymous For This Useful Post: | ||
|
|
2011-05-01
, 00:03
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#584
|
advanced-systemui (0.5.7)
- fix: short events should no longer disappear from the battery graph
- fix: don't clip last X usage hours to 24
- fix: restore control panel screen settings on shutdown and battery_empty signals
- fix: widget editor page number was in the wrong location for portrait mode
- no longer prompts for application category when upgrading
- hour and 24 hour tick marks on battery graph
- charger events on battery graph
- horizontal lines every 10% on battery graph
- used same alignment for all labels in bottom area of battery graph
- setting to lock&blank screen with power button instead of opening/closing ASUI
- merged the n800_lock_mode and the new softpoweroff_mode into a power_action setting
- changed 28% battery icon from gray shell to yellow
- screenshot button that provides an interface for the screenshot-tool package
- governor/dsp now opens with short tap instead of a long
- time_in_state percentages for each cpu clock on governor/dsp dialog
- button positioning can be changed by the user
| The Following 7 Users Say Thank You to auouymous For This Useful Post: | ||
|
|
2011-05-10
, 17:45
|
|
Posts: 1,101 |
Thanked: 1,184 times |
Joined on Aug 2008
@ Spain
|
#586
|
@auouymous
A couple of suggestions...
The battery icon shell colour could be used to provide information about the discharge rate (could be defined as battery_left/remaining_time): white=low (6-7 hours with 100% battery), yellow=medium (5-4 hours), orange=high (4-3 hours), red=very high (3-2 hours)
The battery graph just grows and compresses more and more data into the screen, then resets and starts again. Wouldn't be better if it were a moving window of a given (may be configurable) number of hours?
Could it be possible to make power button long press shutdown work with ASUI? Or would it be too complicated?
A couple of suggestions...
The battery icon shell colour could be used to provide information about the discharge rate (could be defined as battery_left/remaining_time): white=low (6-7 hours with 100% battery), yellow=medium (5-4 hours), orange=high (4-3 hours), red=very high (3-2 hours)
The battery graph just grows and compresses more and more data into the screen, then resets and starts again. Wouldn't be better if it were a moving window of a given (may be configurable) number of hours?
Could it be possible to make power button long press shutdown work with ASUI? Or would it be too complicated?
|
|
2011-05-10
, 22:04
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#587
|
Originally Posted by maacruz
Changing the shell color makes it harder to see the interior color but I could render one of those discharge colors above/below the battery icon. Will look into it.
The battery icon shell colour could be used to provide information about the discharge rate (could be defined as battery_left/remaining_time): white=low (6-7 hours with 100% battery), yellow=medium (5-4 hours), orange=high (4-3 hours), red=very high (3-2 hours)
Originally Posted by maacruz
It is a moving window and is configurable by number of days 0-7. Events older than the configured time are removed. If ASUI crashes or is restarted it will lose all event data since it isn't saved.
The battery graph just grows and compresses more and more data into the screen, then resets and starts again. Wouldn't be better if it were a moving window of a given (may be configurable) number of hours?
Originally Posted by maacruz
There is only a signal that is sent whenever the power button is touched, short or long. MCE calls a systemui powerkyemenu_open method when the button is short pressed and the TODO page documents the problems I had when trying to convert from the signal to this method call. As far as I know there is no signal or method call when the button is long pressed, MCE handles the shutdown internally. But if you know of a way to read the raw power button events...
Could it be possible to make power button long press shutdown work with ASUI? Or would it be too complicated?
BTW, why do you want ASUI to handle shutdown? ASUI does listen for the shutdown signal and switches to its charging UI.
|
|
2011-05-11
, 11:51
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#588
|
Don't use asui it for this!
Could someone with an n800 download and run the newest test binary (asui dt ; asui k ; asui rt), press and release the power button and tell me the two lines printed in console. Then press ctrl-c in console to kill ASUI and restart it with (asui s).
Could someone with an n800 download and run the newest test binary (asui dt ; asui k ; asui rt), press and release the power button and tell me the two lines printed in console. Then press ctrl-c in console to kill ASUI and restart it with (asui s).
|
|
2011-05-11
, 16:37
|
|
Posts: 86 |
Thanked: 8 times |
Joined on May 2010
|
#589
|
Originally Posted by auouymous
I had no lines printed in the console when I tried the above.
Could someone with an n800 download and run the newest test binary (asui dt ; asui k ; asui rt), press and release the power button and tell me the two lines printed in console. Then press ctrl-c in console to kill ASUI and restart it with (asui s).
(test binary size = 179460)
|
|
2011-05-11
, 16:55
|
|
Posts: 1,101 |
Thanked: 1,184 times |
Joined on Aug 2008
@ Spain
|
#590
|
Originally Posted by auouymous
Ok, nice
It is a moving window and is configurable by number of days 0-7. Events older than the configured time are removed. If ASUI crashes or is restarted it will lose all event data since it isn't saved.
Originally Posted by auouymous
I'll look into it.
There is only a signal that is sent whenever the power button is touched, short or long. MCE calls a systemui powerkyemenu_open method when the button is short pressed and the TODO page documents the problems I had when trying to convert from the signal to this method call. As far as I know there is no signal or method call when the button is long pressed, MCE handles the shutdown internally. But if you know of a way to read the raw power button events...
Originally Posted by auouymous
I've had a couple of kernel crashes in the events/0 kernel thread. Buttons and keyboard position sensor stopped working except for the power button, which brings ASUI, but I was unable to shutdown because the touchscreen was locked and I couldn't unlock it. So it occurred to me that there may be other circumstances where a power key shutdown could be desirable.
BTW, why do you want ASUI to handle shutdown? ASUI does listen for the shutdown signal and switches to its charging UI.
 |
| Tags |
| bada blows, bada rox |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 16:00.
asui dt;asui it;asui ds;asui is to download and install both.
Two settings were merged into a new one so if you had changed either you'll need to go to the bottom of settings:button modes and update it.
screenshot button
- a long press anywhere in the button uses screenshot-tool to take a delayed screenshot
- the plus and minus buttons increment and decrement the delay
- run apt-get install screenshot-tool as root to use this feature
- images are stored in /home/user/MyDocs/.images/ or N8x0/Images
Long press takes screenshot when used anywhere inside the button, which means the delay buttons can't auto-repeat when they are long pressed.