Notices

could you try this? and see whether it results on expected ringtone

dbus-send --session --dest=com.nokia.profiled --type=method_call --print-reply /com/nokia/profiled com.nokia.profiled.get_value string:"general" string:"ringing.alert.tone"

happened to me once, and apparently caused by profilex not saving my assigned tone properly

or you can manually assign it using

dbus-send --session --dest=com.nokia.profiled --type=method_call --print-reply /com/nokia/profiled com.nokia.profiled.set_value string:"general" string:"ringing.alert.tone" string:"/home/user/MyDocs/.sounds/myringtone.mp3"

App seems to work very well for me. One request however. Would you be able to add the ability to turn on bluetooth and perhaps turn off/on wifi.

When I jump in my car I like to have BT switch on when I change my profile in order to sync up with the handsfree etc but there is no need for wifi.

Thanks nicolai for such a great program! I modified some icons I found online for use with different profile settings. There are two icons for a "Vibration" profile and two for an "Outdoor" profile (trees and a picnic table). I thought I'd share them here if anyone wanted to use them.

id made 3 custom profiles. just tested them and one worked.
deleted the 2 that didnt work, re-created them, now they seem to work.

any news about this request?

No, and the power menu is a totally different thing.
The profile buttons are controlled by the /etc/systemui/systemui.xml
file and it works as follows.
This entry controls the "silent" profile button:

<menuitem priority="300" name="powerup_memainmenu_silent" visible="general">
<keyfile>/home/user/.profiled/current</keyfile> <icon>statusarea_silent</icon> <return>8</return>
<po>osso-powerup-shutdown</po>
<callback service="com.nokia.profiled" path="/com/nokia/profiled" interface="com.nokia.profiled" method="set_profile" bus="session" autostart="true">
<argument type="string">silent</argument>
</callback>
</menuitem>

This button is visible, when the "visible" condition holds.
The value for this visible condition is read from the keyfile
/home/user/.profiled/current. When you change your profile,
the name of the new profile is written in this file.
The action for this button is the dbus call which changes to
silent profile.
So, that means, the "silent" profile button is visible when the
contents of your /home/user/.profiled/current is:
general
And the dbus-command is send when you press this button.
A similiar entry exists for the general profile button.

You can add extra entries for your own profiles,
but this is impractical if you use many profiles.

For example, you have a third profile "home" and you want to
have this in your power menu when the current profile is "silent",
then you need to add this entry:

<menuitem priority="200" name="home" visible="silent">
<keyfile>/home/user/.profiled/current</keyfile>
<icon>general_profile</icon>
<return>9</return>
<po>osso-powerup-shutdown</po>
<callback service="com.nokia.profiled" path="/com/nokia/profiled" interface="com.nokia.profiled" method="set_profile" bus="session" autostart="true">
<argument type="string">home</argument>
</callback>
</menuitem>

And if you want to have a button for your home profile when
the current profile is "general", you need to add another one:

<menuitem priority="200" name="home" visible="general">
<keyfile>/home/user/.profiled/current</keyfile>
<icon>general_profile</icon>
<return>9</return>
<po>osso-powerup-shutdown</po>
<callback service="com.nokia.profiled" path="/com/nokia/profiled" interface="com.nokia.profiled" method="set_profile" bus="session" autostart="true">
<argument type="string">home</argument>
</callback>
</menuitem>

And if you want to have the "silent" profile button when the
current one is "home":
<menuitem priority="200" name="powerup_memainmenu_silent" visible="home">
<keyfile>/home/user/.profiled/current</keyfile>
<icon>statusarea_silent</icon>
<return>9</return>
<po>osso-powerup-shutdown</po>
<callback service="com.nokia.profiled" path="/com/nokia/profiled" interface="com.nokia.profiled" method="set_profile" bus="session" autostart="true">
<argument type="string">silent</argument>
</callback>
</menuitem>

And for the "general" profile button.
<menuitem priority="200" name="powerup_memainmenu_general" visible="home">
<keyfile>/home/user/.profiled/current</keyfile>
<icon>general_profile</icon>
<return>9</return>
<po>osso-powerup-shutdown</po>
<callback service="com.nokia.profiled" path="/com/nokia/profiled" interface="com.nokia.profiled" method="set_profile" bus="session" autostart="true">
<argument type="string">general</argument>
</callback>
</menuitem>

And of course for every additional profile you have to
even more entries, this grows quadratic.
n*(n-1) entries, where n is the number of profiles :-)

Nicolai

Oh one more request and. Would it be possible perhaps to make a profiles widget which would show say 4 selected profiles. My dropdown is very crowded and its sometimes a pain to try find the profiles entry. Having something I could put on my desktop and quick change between profiles would be awesome.

Maybe there are already "queen beecon" or "desktop execution command"
scripts.

I would be happy to write up some quickwidget qml for it. Does the app respond to dbus signals?

How did you get your desktop to look like that...icons all orderly aligned vertically... oh is the bottom bar a battery life indicator? and what calendar are you using?