Kroll contacted me a while back about displaying IM notifications since Diablo5 removed the task switcher that was showing them. I finally got around to looking into it and discovered that if I open a dialog, any open menus will close. This is good news since ASUI will now be able to open and immediately close a dialog when it needs to map itself or its event eater window.

Anyway, asui-settings will be getting an option to enable the display of IM messages for those with Diablo5. Would it be better to show the messages as a temporary notification or in a dialog that must be closed? The dialog messages would stack so closing one will reveal the next message and so on. The notifications would only be seen if you are using your tablet when they arrive. I'm just worried about someone who may receive a lot of messages and have to close a lot of dialogs.

So if you'd use this feature, please let me know how best to handle the notifications. Other ideas are also welcome.

Cool! At the moment I'm making do with this, but wouldn't mind something a bit better integrated/looking :-)

If I understand you correctly, neither please. I'd like something similar to the stock offering, ie a permanent indicator (somewhere in the status bar I guess) showing that there are messages, that can be tapped to reveal them (and then those can be tapped to launch the appropriate app/whatever).

That's an issue, but you don't want to lose IMs (or missed calls, subscription requests and so on) if you don't see them either.

So we need an applet that replaces the presence applet, flashes when there are notifications and one of its menu options would open them in a scrollable dialog.

Yup, that should do it.

New test binary should fix any issues with open menus preventing ASUI from opening. The invisible event eater will now open when the screen blanks and catch the first screen tap or key pressed, and ASUI will properly open when the device locks or an alarm is triggered.

Run asui dit to download and install.

New test binary available. Run asui uu ; asui dit to download and install.

Not sure how well it will work but "asui restart_mce" will restart MCE and then restore display settings. If anyone knows an order to restart MCE and alarmd, that always works, please let me know and I'll add it to the script.

A "booting..." screen will appear briefly after you enter your code during boot, it then returns to the splash screen. This gets rid of the temporary solid white screen that was shown after the code had been entered.

And finally, swiping will now display a circle at the start point and a circle below your finger. Both circles change to green when you have swiped far enough to complete the action, and change back to gray if you change directions. This works on the main button bar (horizontal swipe), fullscreen clock (vertical swipe), battery graph (vertical swipe) and devlock bar (horizontal and vertical swipes).

just to give a bit of life to this thread..

my N800's battery is quite old, (dated 2007), but I noticed that ASUI's battery indicator does not follow the system battery indicator.

Usually the ASUI's battery status stops the "charging animation" when the battery is about 94%, at the same time the system battery indicator still displays that the battery is being charging.

Do I need to perform any battery calibration/ reset any setting ?

thx

odd............

After thinking long and hard...
No you don't have to recal the battery...
you have to just get a new battery!


I am not quite sure where the problem lies...
now you did a verbatim from beginning to end reflash ...up to turbo with asui ...
and did it with no issues along the way.. ...right?
If not...
if you just hacked and patched it all together from bits and pieces you found here and there...and tried to fix issues along the way...that may contribute to this behaviour and possibly others that have or may appear...

If you did the walkthrough proper...
Then this discrep. could most likely be just the battery...
I have a few old ones from 2007...and they perform between 98% and 80-some-odd percent...as their maximum charges...
and they do fine...
They have their own quirks a few of them..but not what you are expressing...

Possibly it could also be a flawed upgrading with issues...and battery issues combined...

The root culprit could be a variety of things...
including needing to reset the batt charge indicator to express the current charge...rather than an echo...or delayed reading..

I know in the last 3-4 years I saw a thread about doing it on the n8x0 ...somewhere in the subforums...
Just can't remember where...

Try some keywords in the search engine...
It should spit out where threads dealing with this type of recal ...are...

I understand, but the battery is not that bad, I can use it about 3-4hours continuous use of the N800, wifi/BT both on (BT connected to BT keyboard).
as new battery, not easy to find, (Chinese knock offs around or used being sold as "refurbished" (wtf), I only noticed (ebay) a couple sold in Germany, (3rd party) but are rated 1200mAh, less than Nokia's)

yes, last time I did a reflash->clone to SD -> DT/ASUI no issues


I found a thread about re-calibration, but was for N900, will tray again anyway, I still curious if there is way to reset the ASUI's batt indicator to be on a par with the system's one.