Maemo turns on the screen for headphones, charger, usb, mmc, etc. It would be quite easy for ASUI to do the same though. I just need to figure out how to control music apps via dbus and how to best handle it. Laziest solution would only control master volume and maybe mute the volume with fullscreen button. Problem with that is some apps use a separate volume (canola) and if its set low you won't be able to hear the music even with master volume at max. And canola likes to randomly change its volume per song.

Another easy option would be to place a blank window over the music app and catch certain keys (home and escape) while letting others pass through to the music app. This approach would require you to set the master volume to max or whatever you want before entering media mode. Problem with this is that ASUI can't turn on the screen for the keys it passes through since it doesn't actually see them. Another problem is that I'd have to catch not only home and escape but any other keys that could change the app in bad ways. Not a big deal for the n800 but I'd rather not have to grab all keys on the n810's keyboard.

The best method would be to have dbus calls for various music apps and ASUI could handle all keys and turn on the screen briefly with a blank window (catches keys) so you can see the music app. The home and escape keys could also be used and keys can be bound to pause the music or skip songs, all user-defined of course. We'd also have to solve the problem of which volume control to change or maybe adjust one of them until it reaches max and then switch to the other. It might also be better to dedicate one of the keys to temporarily turning on the screen instead of doing it on key presses as the battery would last much longer if you were just controlling the volume and current song from your pocket without the screening turning on in there.

I'm busy with some other stuff right now but if someone dug up the dbus calls for the popular music apps then I could quickly add support.

I would say that if the N810 keyboard is extended, the user better well be looking at the screen.

On the issue of master volume: For a few weeks, I'd been setting it to 100% and then adjusting volume in Canola, either low if using headphones or 100% when connected to the little stereo. I notice that the master volume keeps resetting to 85%. I haven't been able to determine what event might make that happen; I thought maybe insertion/removal of the audio plug might do it, but that doesn't seem to be the case. I've just decided to let it remain at 85%.

In my usage of Canola, the volume always remains where I have it set. I don't think my MP3s have Replay Gain volumes set; that might be related.

Regarding the audio-passthru mode: to me, it sounds like this is getting far afield of ASUI's original plan. I'd hate to see this great utility succumb to feature creep.

Maemo reduces master volume when headphones are plugged in.


Could be the problem.


ASUI is responsible for locking and unlocking the screen and audio-lock mode would do exactly that. And if you were to add this feature to the OS it would need to be in systemui or ASUI. When audio-lock is active ASUI can keep the devlock keypad from opening so you can still interact with your music app but as soon as you unlock the screen it will open the keypad.

it appears that turning off flight mode no longer turns on bluetooth if it was on when turning on flight mode.

The new flight mode code turns off wifi and bluetooth before entering flight mode. It was done to fix a problem where icd would scan while in flight mode and I figured I'd turn off bluetooth as well. Would you prefer to have bluetooth turn back on?

if bluetooth was on before flight mode gets activated, it would prefer that bluetooth was turned back on when fight mode was deactivated.

I've noticed that if my device shuts down due to low battery, that the system reverts locking screen & keys automatically (have to uncheck the box in "control panel > display")
wondering if anyone else has come across this behavior?

Not that i have noticed. Tho i have noticed that if the device had screen and keys lock on when getting a low battery shutdown it will keep that state when powered back on.

ASUI overrides the control panel setting so it can perform all four locking modes no matter what your settings are. When the screen comes back on the settings are restored but if ASUI is killed, restarted or the system shuts down then ASUI doesn't restore the values.

I'll work on getting the shutdown and battery_empty signals to restore state and maybe also save the original values in state settings and ASUI can restore them on next start if it is killed. In the mean time, there are two buttons on ASUI's secondary widget page that toggle those settings without requiring a trip to the control panel.