Active Topics
-
maemo.org (1)
to Community by sixwheeledbeast - 15 mins ago -
Old stuff for Nokia 770 (0)
to Nokia 770 by teroyk - 4 hrs, 12 mins ago - more...
|
2011-04-03
, 14:37
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#472
|
advanced-systemui (0.5.3)
Two icons are installed to map ASUI and open the settings apps. The icons don't seem to work with Telescope but show up fine in the menu and control panel organizer. Anyone know why?
The settings app service section can now control services at boot and start, stop and restart them. When re-enabling a boot service it will start in the correct order instead of starting everything at 20 like maemo-control-services does. It also doesn't remove the kill links so if you disable a service at boot but then start it manually it will properly stop when changing runlevels.
Any service not known to the app will have OPTIONAL appended to its name and in a future release the order will be saved when disabling the service but for now you can't disable unknown services.
- fix: short power button press no longer does anything while in minimal UI
- fix: booting from charging runlevel now only displays keypad once
- 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 support
- removed popup clock vertical offset in portrait mode
- display names of python scripts in process viewer
- settings:services can now toggle ASUI and SystemUI to run at boot
- settings:services can now start, stop or restart ASUI and SystemUI
- settings:services can now toggle rc5 networking
- settings:services can now start, stop, restart all services
- settings:services can now toggle services started during boot
- removed /etc/asui-svc
- icons to open ASUI and ASUI Settings
- asui convenience script doesn't require root when using the show, hide, left, right, reload or settings commands
Two icons are installed to map ASUI and open the settings apps. The icons don't seem to work with Telescope but show up fine in the menu and control panel organizer. Anyone know why?
The settings app service section can now control services at boot and start, stop and restart them. When re-enabling a boot service it will start in the correct order instead of starting everything at 20 like maemo-control-services does. It also doesn't remove the kill links so if you disable a service at boot but then start it manually it will properly stop when changing runlevels.
Any service not known to the app will have OPTIONAL appended to its name and in a future release the order will be saved when disabling the service but for now you can't disable unknown services.
 |
|
2011-04-04
, 01:02
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#473
|
finally, service management that works!
__________________
Be warned, posts are often line of thoughts at highway speeds...
Be warned, posts are often line of thoughts at highway speeds...
|
|
2011-04-04
, 17:14
|
|
Posts: 86 |
Thanked: 8 times |
Joined on May 2010
|
#474
|
Not sure why, but both ASUI icons in the new install ended up in my Games folder in the menu. My menu is customized, of course; are these being placed by submenu position instead of name? Anyway, I don't care.
I wish an update would maintain the setting of which status-bar icons are displayed.
Found a problem this morning with ASUI 0.5.1 which persists in 0.5.3
Start with N800 powered off, with DoNotDim = Charger, and with ASUI set not to open on powerup
Plug in charger
eventually gets to ASUI charging screen, which dims but does not go black -- OK
Press and hold power button
blue LED comes on, one of the sliders (volume?) is displayed (minor glitch), then the normal boot screens
When booted:
ASUI is open: wrong
screen dims, then blanks: wrong (charger is plugged in)
Close ASUI window:
screen dims, then blanks: wrong
Control Panel's and ASUI's DoNotDim setting is shown correctly
Unplug charger, then plug it back in
Now it does not dim
I wish an update would maintain the setting of which status-bar icons are displayed.
Found a problem this morning with ASUI 0.5.1 which persists in 0.5.3
Start with N800 powered off, with DoNotDim = Charger, and with ASUI set not to open on powerup
Plug in charger
eventually gets to ASUI charging screen, which dims but does not go black -- OK
Press and hold power button
blue LED comes on, one of the sliders (volume?) is displayed (minor glitch), then the normal boot screens
When booted:
ASUI is open: wrong
screen dims, then blanks: wrong (charger is plugged in)
Close ASUI window:
screen dims, then blanks: wrong
Control Panel's and ASUI's DoNotDim setting is shown correctly
Unplug charger, then plug it back in
Now it does not dim
|
|
2011-04-05
, 00:15
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#475
|
Originally Posted by mcow
I just install the desktop files and HAM detected this and put them in my Extras folder. Is Games your last folder? Anyone know how to properly install the desktop files?
Not sure why, but both ASUI icons in the new install ended up in my Games folder in the menu.
Originally Posted by mcow
0.5.3 no longer modifies the original battery desktop file so it should no longer reappear after an update and the next release will merge the power button applet into the battery applet and fix that problem.
I wish an update would maintain the setting of which status-bar icons are displayed.
Originally Posted by mcow
Ugh, I have devlock enabled and missed that nasty corrupted ASUI screen after boot. Swiping from top down, escape key or power button will of course unmap ASUI and it will display correctly when remapped.
Found a problem this morning with ASUI 0.5.1 which persists in 0.5.3
When booted:
ASUI is open: wrong
screen dims, then blanks: wrong (charger is plugged in)
Close ASUI window:
screen dims, then blanks: wrong
Unplug charger, then plug it back in
Now it does not dim
There is a bug in Maemo (MCE? DSME?) that prevents it from not blanking when booted on charger. You can verify this by switching from ASUI to SystemUI and rebooting on charger. Read below before using asui-settings to do this.
--
I forgot to sudo asui-settings when run from the icon so it is unable to control the services unless launched from within ASUI or when asui settings is run as root.
I'll get another release out soon to fix both of these issues.
| The Following User Says Thank You to auouymous For This Useful Post: | ||
 |
|
2011-04-05
, 12:55
|
|
Posts: 139 |
Thanked: 38 times |
Joined on Nov 2007
@ mid gulf coast florida
|
#476
|
Installed and then uninstalled for the last time.
really think that you should rename this CASUI (CA for completely assinine)
can not understan the logic of having to remember that the key combination that locks the screen and keys is not the same to unlock.
lock and blank has never worked. keep getting the message that "something" is not allowing the screen to blank. and while ASUI is attempting to do the described action nothing else is possible. is it a standard feature that requires one to remove the battery to get things working again?
just want to thank you for giving me a reason to hit the uninstall button
really think that you should rename this CASUI (CA for completely assinine)
can not understan the logic of having to remember that the key combination that locks the screen and keys is not the same to unlock.
lock and blank has never worked. keep getting the message that "something" is not allowing the screen to blank. and while ASUI is attempting to do the described action nothing else is possible. is it a standard feature that requires one to remove the battery to get things working again?
just want to thank you for giving me a reason to hit the uninstall button
|
|
2011-04-05
, 14:01
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#477
|
Originally Posted by n9ots
There is a setting at the bottom of button modes to change the secondary key which defaults to fullscreen but can be set to dpad center. Next release will default to fullscreen for n810 and dpad center for n800 but anyone who has already installed it would need to manually change that setting.
can not understan the logic of having to remember that the key combination that locks the screen and keys is not the same to unlock.
Originally Posted by n9ots
Power+fullscreen doesn't unlock it? You could try installing the debug binary asui dd;asui id as root, pressing lock&blank and then send me the /root/asui-debug-* file.
lock and blank has never worked. keep getting the message that "something" is not allowing the screen to blank. and while ASUI is attempting to do the described action nothing else is possible.
|
|
2011-04-05
, 14:20
|
|
Posts: 9 |
Thanked: 1 time |
Joined on Nov 2010
|
#478
|
Just chiming in to say that this application is great. I only wish that it looked a little bit nicer, but as long as it works (which it has so far) I'm happy.
|
|
2011-04-05
, 14:30
|
|
Posts: 1,101 |
Thanked: 1,184 times |
Joined on Aug 2008
@ Spain
|
#479
|
Originally Posted by n9ots
You are being rude, unjust and unpolite.
Installed and then uninstalled for the last time.
really think that you should rename this CASUI (CA for completely assinine)
can not understan the logic of having to remember that the key combination that locks the screen and keys is not the same to unlock.
lock and blank has never worked. keep getting the message that "something" is not allowing the screen to blank. and while ASUI is attempting to do the described action nothing else is possible. is it a standard feature that requires one to remove the battery to get things working again?
just want to thank you for giving me a reason to hit the uninstall button
First, ASUI is replacing a closed source component, on top of an undocumented protocol, on top of an ugly closed source stack. All of this could only be acomplished by countless hours of reverse engineering, guesses and testing.
Second, ASUI is a work in progress, and you are a fool if you expect any software to be free of bugs, specially if there is no specifications for the undelying system, which is also quite buggy.
Third, ASUI has shown an incredible level of progress over the time, and not only provides all the funtionality of the closed source component it replaces, but adds much more over it. It is a wonderful work.
Fourth, auouimous has been incredibly helpful and proactive, in fixing all bugs reported and implementing new features, all of this by the love of it, and gives us all the code under a floss license.
He doesn't owe you anything, on the contrary, if you want more software from this community you are expected to contribute to the best of your hability and resources.
'nuf said
| The Following 5 Users Say Thank You to maacruz For This Useful Post: | ||
|
|
2011-04-05
, 15:07
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#480
|
advanced-systemui (0.5.4)
Icons still don't render in Telescope but asui-settings can be launched from the icon and now actually controls the services.
You will need to uncheck the battery applet in asui-settings battery section if you were only using the power button statusbar applet.
- fix: ASUI unmaps when booting from charging runlevel and start visible unset
- fix: ASUI redraws when booting from charging runlevel and start visible is set
- fix: asui-settings icon now calls `asui settings` with sudo so it can control services
- fix: restart systemui when uninstalling advanced-systemui package
- fix: removed auto-devlock code and properly restore ASUI map state
- merged statusbar power button and battery applets and added setting in battery section
- statusbar applet listens for battery_low signal and displays notification
- power unlock key defaults to dpad center on n800 and fullscreen on n810
Icons still don't render in Telescope but asui-settings can be launched from the icon and now actually controls the services.
You will need to uncheck the battery applet in asui-settings battery section if you were only using the power button statusbar applet.
Originally Posted by Ordinary
User-defined colors are planned, if that is good enough I can try to get them ready soon. Otherwise I will need ideas on how to improve its looks.
I only wish that it looked a little bit nicer
 |
| Tags |
| bada blows, bada rox |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 19:56.
Be warned, posts are often line of thoughts at highway speeds...