Active Topics

 


Reply
Thread Tools
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#441
Originally Posted by jstokes View Post
Request: It would be nice if asui had an entry in sudoers so that "sudo asui" works.
ASUI was originally launched through sudo so I know how to do it. The advanced-systemui binary can't be run from sudo because some of the services won't start. I think there was some other problems as well. Can't you just type root to become root and then run asui, same number of keystrokes and the 'oo' makes it easier to type?

Originally Posted by fpp View Post
the power button doesn't do anything. The status bar icon dims briefly, then back again, nothing more.
However, just before I also installed Diablo-Turbo, so I don't know if ASUI would have worked on stock Diablo.
It will work on stock Diablo without rotation support or on Community SSU or Diablo Turbo. Is ASUI running ps aux|grep advan? If so, run asui dd ; asui k ; asui rd as root, press the hardware power button, press the statusbar applet, ctrl-C to kill it in the console and send me the /root/asui-XXXXXXX log file. If it is not running then use the same commands and the log file should show why it isn't starting.

Originally Posted by tso View Post
dimmed closer to 120 seconds then 60

i guess if we want to be sure it dims perfectly each time we lock the screen we can switch the locking action to lock&blank.
Is your dim timeout 2 minutes? The dim timeout begins when you press the lock button but won't dim until at least 60 seconds after the last blanking pause signal. I could probably read the dim timeout and adjust the message if greater than 60 seconds.

Lock&blank and blank will not override the blanking pause either and result in the same notification.

Originally Posted by tso View Post
seems there is some other issue now. When i press the power button to unlock there is a short flash of the ui and then the screen blanks again. Oh wait, a long press on the power button got me a view with a "press fullscreen to unlock" popup. Following that got me access to the ui again. Ah, it was part of the feature added earlier by request, right?
Wouldn't a long press on the power button shutdown your device?

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.
 

The Following 2 Users Say Thank You to auouymous For This Useful Post:
tso's Avatar
Posts: 4,783 | Thanked: 1,253 times | Joined on Aug 2007 @ norway
#442
Originally Posted by auouymous View Post
Is your dim timeout 2 minutes? The dim timeout begins when you press the lock button but won't dim until at least 60 seconds after the last blanking pause signal. I could probably read the dim timeout and adjust the message if greater than 60 seconds.

Lock&blank and blank will not override the blanking pause either and result in the same notification.

Wouldn't a long press on the power button shutdown your device?

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.
Bah, why did i assume it was a ASUI issue. I should have thought of how i have the brightness settings set (max duration brightness, 2 min, to help with reading long websites and such, and a minimum blank time, 2 min as well as i can not set it below the brightness time to have it save as much battery as possible when left idle).

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 on my part right now. Sorry for the thread noise.
__________________
Be warned, posts are often line of thoughts at highway speeds...
 
fpp's Avatar
Posts: 2,853 | Thanked: 968 times | Joined on Nov 2005
#443
Originally Posted by auouymous View Post
It will work on stock Diablo without rotation support or on Community SSU or Diablo Turbo.
... but not (quite), it seems, on stock Diablo without rotation with Diablo Turbo but without Community SSU :-)

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.
__________________
maemo blog
 
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#444
Originally Posted by tso View Post
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.
You can edit the dim->blank timeout (/system/osso/dsm/display/display_blank_timeout) with gconf-editor so it would be less than the 2 minute dim timeout, it might work.

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.

Originally Posted by fpp View Post
After adding the CSSU to the 800 and rebooting, ASUI is back to its normal behaviour... sorry for the corner case
Had you rebooted the device after installing ASUI? Maybe it didn't properly start and the reboot fixed it, and not the CSSU. But the CSSU is probably good to have installed since it patches various userland apps.

Originally Posted by fpp View Post
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.
Did you have advanced-power installed on the n800? It seems the battery applet is mandatory and advanced-power probably disabled that. I will have ASUI do the same in next release, in the mean time you can run
Code:
sed -i "s:^Mandatory=true$:#Mandatory=true:g" /usr/share/applications/hildon-status-bar/hildon-status-bar-battery.desktop
as root so you can remove the default battery applet.
 
fpp's Avatar
Posts: 2,853 | Thanked: 968 times | Joined on Nov 2005
#445
Originally Posted by auouymous View Post
Had you rebooted the device after installing ASUI? Maybe it didn't properly start and the reboot fixed it, and not the CSSU. But the CSSU is probably good to have installed since it patches various userland apps.
It was definitely CSSU that fixed it, as I'd turned the N800 on and off a number of times in between.

Did you have advanced-power installed on the n800?
Spot on ! And I uninstalled it just before adding ASUI...

It seems the battery applet is mandatory and advanced-power probably disabled that. I will have ASUI do the same in next release, in the mean time you can run
(code) as root so you can remove the default battery applet.
Great, thanks ! And now that I've learnt to fish, maybe I can also remove that useless Presence icon that's been bugging me all these years... :-)
__________________
maemo blog
 
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#446
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?
 
Posts: 1,101 | Thanked: 1,184 times | Joined on Aug 2008 @ Spain
#447
That's why I run from mmc
This is from a qemu vm running unmodified diablo.
Code:
Nokia-N800-:/etc/rc1.d# ls
K00zzinitdone                  K20wlancond
K01alarmd                      K21af-startup
K01mediaplayer-daemon          K22af-services
K01metalayer-crawler0          K23x-server
K15icd2                        K24dsp-init
K15tablet-browser-daemon       K26esd
K16hal                         K30ke-recv
K20af-base-apps                K40wide-dhcpv6-client
K20btcond                      K45maemo-launcher
K20dbus                        K45osso-systemui
K20gpsdriver                   K74bluez-utils
K20hildon-application-manager  K74osso-systemui-early
K20hildon-desktop              K75multimediad
K20hulda                       K79mce
K20libgpsbt                    K85dnsmasq
K20obexsrv                     K85product-code
K20osso-ipv6

Nokia-N800-:/etc/rc2.d# ls
K00zzinitdone                  S54gpsdriver
S12fb-progress.sh              S54libgpsbt
S20dbus                        S54osso-ipv6
S20hal                         S56bluez-utils
S20osso-applet-display         S57btcond
S21mce                         S58wide-dhcpv6-client
S21x-server                    S58wlancond
S22af-services                 S59icd2
S24dsp-init                    S60af-base-apps
S25multimediad                 S61osso-systemui
S26esd                         S70obexsrv
S26osso-systemui-early         S99alarmd
S30ke-recv                     S99hulda
S41product-code                S99mediaplayer-daemon
S45maemo-launcher              S99metalayer-crawler0
S50af-startup                  S99tablet-browser-daemon
S51hildon-desktop              S99ttyusb0
S52hildon-application-manager  S99zzinitdone
S53dnsmasq

Nokia-N800-:/etc/rc3.d# ls
K00zzinitdone                  S53dnsmasq
S20dbus                        S56bluez-utils
S20hal                         S57btcond
S21mce                         S58wide-dhcpv6-client
S21x-server                    S58wlancond
S22af-services                 S59icd2
S24dsp-init                    S60af-base-apps
S25multimediad                 S61osso-systemui
S26esd                         S70obexsrv
S26osso-systemui-early         S99alarmd
S30ke-recv                     S99hulda
S41product-code                S99mediaplayer-daemon
S45maemo-launcher              S99metalayer-crawler0
S50af-startup                  S99tablet-browser-daemon
S51hildon-desktop              S99zzinitdone
S52hildon-application-manager

Nokia-N800-:/etc/rc4.d# ls
K00zzinitdone                  S53dnsmasq
S20dbus                        S56bluez-utils
S20hal                         S57btcond
S21mce                         S58wide-dhcpv6-client
S21x-server                    S58wlancond
S22af-services                 S59icd2
S24dsp-init                    S60af-base-apps
S25multimediad                 S61osso-systemui
S26esd                         S70obexsrv
S26osso-systemui-early         S99alarmd
S30ke-recv                     S99hulda
S41product-code                S99mediaplayer-daemon
S45maemo-launcher              S99metalayer-crawler0
S50af-startup                  S99tablet-browser-daemon
S51hildon-desktop              S99zzinitdone
S52hildon-application-manager

Nokia-N800-:/etc/rc5.d# ls
K00zzinitdone                  S20dbus
K01mediaplayer-daemon          S20hal
K15btcond                      S20osso-applet-display
K15icd2                        S21mce
K15tablet-browser-daemon       S21x-server
K20af-base-apps                S22af-services
K20fb-progress.sh              S24dsp-init
K20gpsdriver                   S25multimediad
K20hildon-application-manager  S26esd
K20hildon-desktop              S26osso-systemui-early
K20hulda                       S41product-code
K20libgpsbt                    S53dnsmasq
K20obexsrv                     S58wide-dhcpv6-client
K20osso-ipv6                   S61osso-systemui
K20wlancond                    S99alarmd
K30ke-recv                     S99metalayer-crawler0
K45maemo-launcher              S99zzinitdone
K74bluez-utils
 

The Following User Says Thank You to maacruz For This Useful Post:
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#448
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.
 
Posts: 86 | Thanked: 8 times | Joined on May 2010
#449
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."
 
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#450
advanced-systemui (0.5.2)
  • fix: allow default battery applet to be disabled
  • fix: ASUI properly locks the device with MCE
  • fix: if blank timeout isn't at least 10 seconds greater than dim timeout then power button will not dim the display if a secondary key is required to unlock
  • fix: tapping the battery applet will no longer change it to the solid red battery icon before values from ASUI have been received
  • more changes to the flight mode images
  • removed cpu percentage from popup clock
  • refreshed memory, frequency and temperature before drawing popup clock
  • added alarmd, metalayer-crawler and browserd to system services for process viewer
  • display names of shell scripts in process viewer
  • added gpsdriver_guard to process viewer and GPS service widget
  • init.d script and convenience script must now stop SystemUI whenever ASUI is started
  • changed runlevel order from SK99 to S61/K45
  • added advanced-systemui-early script at S26/K74
  • setting to not show clock popup when ASUI is mapped, except for on secure keypad
  • setting for minimum time between clock popups
 

The Following 2 Users Say Thank You to auouymous For This Useful Post:
Reply

Tags
bada blows, bada rox


 
Forum Jump


All times are GMT. The time now is 23:03.