Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 15 hrs, 25 mins ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 16 hrs, 39 mins ago -
Maemo repository (3)
to Community by torsen - 1 day, 8 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 5 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 12 hrs ago - more...
| The Following User Says Thank You to auouymous For This Useful Post: | ||
 |
|
2010-12-15
, 23:25
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#222
|
Just tried with -test, no crashes.
__________________
Be warned, posts are often line of thoughts at highway speeds...
Be warned, posts are often line of thoughts at highway speeds...
|
|
2010-12-15
, 23:55
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#223
|
advanced-systemui (0.4.4)
Please run the debug binary as root if you have any problems with this release and send me the output from /root/asui-debug-2 (desktop and shutdown charging runlevel) or /root/asui-debug-5 (if the problem happens when booting into the charging runlevel).
- fix: ASUI no longer grabs pointer, prevents focus in/out loop
- fix: ASUI would segfault if bluetooth was visible at startup
- wifi widget now starts and stops the optional openntpd service
- wifi widget now starts and stops the osso-connectivity-ui-conndlgs service
- audio widget now starts and stops the osso-media-server service
- dialogs now change theme when a light sensor change occurs while open (some take longer to respond)
- a blue asterisk is displayed if bluetooth is visible (discoverable)
- swiping from bluetooth service indicator to bluetooth hardware indicator will toggle visibility
- flight mode long press won't try to stop services that aren't started, except ssh
Please run the debug binary as root if you have any problems with this release and send me the output from /root/asui-debug-2 (desktop and shutdown charging runlevel) or /root/asui-debug-5 (if the problem happens when booting into the charging runlevel).
|
|
2010-12-16
, 19:48
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#224
|
bah, still having problems with the "unlocked" window.
|
|
2010-12-16
, 21:54
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#225
|
New test and debug binaries on the download page.
The removal of the dbus_free calls should reduce the number of random crashes and also means 0.4.5 should FINALLY restart when upgraded with the application manager!
(I've tested it)
The debug binary now produces a new timestamped log file each time it starts to make it easier to find bugs. If you think ASUI is crashing, just run the service for a couple days using the debug binary and see if it produces multiple log files with a seg fault at the end of them.
Also disabled that "unlocked" window until I can get it fixed.
Edit:
For anyone who gets a GUID in the wifi widget: if you start wifi, kill ASUI so it restarts, do you still have a GUID? The initial value is acquired from a different signal and I'm wondering it if it might produce a different result than what you get after starting wifi.
Last edited by auouymous; 2010-12-16 at 21:59.
- fix: removed all dbus_free calls so ASUI should no longer crash when upgraded with appman
- removed the startup sleep when system is loaded
- SIGINT, SIGTERM and SIGSEGV signal handlers to clean up and log termination reason
- debug binary produces a new timestamped log file each time ASUI starts
- continuously poll all initial dbus values until each one has responded (mce, bme, bluez, icd2)
- disabled the "unlocked" blank window until properly fixed
The removal of the dbus_free calls should reduce the number of random crashes and also means 0.4.5 should FINALLY restart when upgraded with the application manager!
(I've tested it)The debug binary now produces a new timestamped log file each time it starts to make it easier to find bugs. If you think ASUI is crashing, just run the service for a couple days using the debug binary and see if it produces multiple log files with a seg fault at the end of them.
Also disabled that "unlocked" window until I can get it fixed.
Edit:
For anyone who gets a GUID in the wifi widget: if you start wifi, kill ASUI so it restarts, do you still have a GUID? The initial value is acquired from a different signal and I'm wondering it if it might produce a different result than what you get after starting wifi.
Last edited by auouymous; 2010-12-16 at 21:59.
|
|
2010-12-17
, 01:12
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#226
|
didnt try with -debug, but i noticed no change on the wifi name when killing asui after connecting to wifi.
|
|
2010-12-17
, 02:12
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#227
|
didnt try with -debug, but i noticed no change on the wifi name when killing asui after connecting to wifi.
--
New binaries up.
- process viewer now highlights other known services in light blue
- brightness level moved to /apps/asui_state/, will cause brightness to reset on first run
- theme button in brightness widget (ALS, black, white)
Send me the full line from the ps command if see any system services that aren't highlighted. Helps to distinguish between applications and services.
N800 users:
Tap theme button in brightness widget to toggle between black and white, no more hacking the white_threshold.
N810 users:
Defaults to ALS auto-theming. Long press the light sensor button to toggle between ALS and manual. Once in manual mode (sensor value is underlined), you can tap to toggle between black and white.
|
|
2010-12-17
, 15:12
|
|
Posts: 235 |
Thanked: 339 times |
Joined on Nov 2010
|
#228
|
Originally Posted by auouymous
Yes, I do still have a GUID there. That said, ConIc has stuff for getting the name from a GUID: http://maemo.org/api_refs/4.1/libcon...d739702429e449 (the ConIcIap created by using http://maemo.org/api_refs/4.1/libcon...e70735621159c6). ConIc is opensource, so I guess stealing its code is perhaps an option?
For anyone who gets a GUID in the wifi widget: if you start wifi, kill ASUI so it restarts, do you still have a GUID? The initial value is acquired from a different signal and I'm wondering it if it might produce a different result than what you get after starting wifi.
Oh, a feature request: If you perform a tap-and-hold on the time widget, could it switch to 12-hour time?
EDIT: Sorry, but I have to ask: Why is rotation using the volume keys slightly slower than the rotation widgets? Thanks
Last edited by jstokes; 2010-12-17 at 15:18.
|
|
2010-12-17
, 17:36
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#229
|
ConIc has stuff for getting the name from a GUID. ConIc is opensource, so I guess stealing its code is perhaps an option?
Oh, a feature request: If you perform a tap-and-hold on the time widget, could it switch to 12-hour time?
Would you actually switch back and forth between a 12 and 24 hour clock on a regular basis? The gconf settings in /apps/asui/ are set-once-and-forget and shouldn't have extra code in ASUI unless it something that needs to be changed frequently. I do plan to write a GTK config app that will be launched from ASUI and make it easier than using gconf-editor. The widget editor is also a set-once feature but is easier and more intuitive to do in ASUI than a GTK app. That said, if it is something you would actually change often then I can easily add it and it only takes a few lines of code.
Why is rotation using the volume keys slightly slower than the rotation widgets?
| The Following User Says Thank You to auouymous For This Useful Post: | ||
|
|
2010-12-17
, 18:03
|
|
Posts: 235 |
Thanked: 339 times |
Joined on Nov 2010
|
#230
|
Originally Posted by auouymous
No, I didn't! (Sorry, I should've actually read the brilliant documentation you have on your website)
I assume you already know about the /apps/asui/clock_* settings accessible with the gconf-editor app, if not then ignore the following, go install gconf-editor and change them.
Would you actually switch back and forth between a 12 and 24 hour clock on a regular basis?
They look the same speed on my device. There is also no difference in the code, the key press handler calls the same rotate_screen() function as the on-screen button handler. The on-screen buttons do support rotate-and-close and if enabled, it would make them faster since the "rotating..." window isn't opened and ASUI isn't resized and redrawn.
 |
| Tags |
| bada blows, bada rox |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 01:53.
New test and debug binaries won't segfault and also display a blue asterisk if bluetooth is visible. Will probably make a swipe from left to right inside the bluetooth widget toggle visibility.
Do you still have any crash problems?