Originally Posted by ajalkane

You're not missing anything. With 1.7.0 it should just basically work. Inception could of course interfere, but I don't think that's it.

There's ways to debug it. First of all you can try manually from command line to use the separate exe:

Code:

invoker --type=m /opt/profilematic/bin/platformutil flightMode
On

It's important to use the invoker command.

If that doesn't work, check the file at

Code:

/var/lib/aegis/restok/restok.conf

Find profilematic's entries. The important bit is this:

Code:

Object: applauncherd-launcher::/usr/bin/applauncherd.bin
Request:
        AID::.profilematic.
        mce::DeviceModeControl

Let me know.

Originally Posted by P@t

Yes indeed I should check that PSM is improving the situation. I actually put my phone on PSM after 5mn iddle (thanks to your app) and even not sure now, I do not think it helps enough.

If wifi off is not possible (that was possible for the N900 i think but a less restrictive phone for such features), do you think that the fact that a 'known' wifi network can be either automatically connected or manually connected is helping and could be implemented in your app?

Originally Posted by N9uwu

Originally Posted by ajalkane

I've thought about implementing something like that. But I can't promise when and even if it will come.

any options or possibilities you found out so far? Is it possible to check for the "prestart" state of the main applications?
perhaps the process state itself (R <-> S) can be checked somehow? (using output of ps)? unfortunately /proc/<procID>/state yields permission denied.

PS: thank you for this app! have been using idle & 2G/dual switch for a long time now .

Originally Posted by ajalkane

Does it help at all? How often it stutters with and without PSM? I'd like to understand this a bit better to know if anything can be done about it. If I've understood it correctly the stuttering happens because of scanning of WLAN access points?

Originally Posted by ajalkane

I'm not sure. If it's the automatic scanning of WLANs that's causing it, that won't help.

But there is a value in gconf that you might try to change:

/system/osso/connectivity/network_type/search_interval

By default it is 300, which I guess is in seconds (5 minutes). Does this match the interval with stuttering bluetooth? You could try changing it if so. If that helps, it's easy to make Custom Action to ProfileMatic to change that upon some conditions.

Originally Posted by Diggler

Ajalkane, what a great work you have done! You have been around for almost a year improving, listening and answered almost every question. I'm impressed.

I installed your app yesterday and tried the PSM mode during 23:00 - 07:00 together with lowering ring profile to 40%. Morning after the phone was dead and phone had about 30% of battery when I got to bed. But I haven't seen such reports in the thread so it might been something else.

I have one question just to see if I have misunderstood how the rules works. I tried
15:00 - 15:05:
availability on (previously off) Restore profile
bluetooth on (previously off) Restore profile
Ring profile 100% (previously 40%) Restore profile
No default rule configured
No other rules active

Outcome is that it turns on FB at 15 and off at 15:05, same with BT. But ring profile remains at 100%. I have tried several times but it doesn't restore previous ring profile.

Originally Posted by Diggler

Outcome is that it turns on FB at 15 and off at 15:05, same with BT. But ring profile remains at 100%. I have tried several times but it doesn't restore previous ring profile.

Originally Posted by ajalkane

I haven't yet looked at it in detail. It'd have to be something event based to get notifications that applications are launched to minimize battery usage. I wouldn't want to poll for the state.

I doubt I have time to look how it could be achieved any time soon. But if anyone has code samples or links to APIs that would be useful, that could speed up things.



Thanks!

Originally Posted by knobtviker

You can hook on DBUS signal NameOwnerChanged and set to 3G if not previously already on 3G.
However, in my tests it was found that this approach works, but not really nice with incoming calls.
Lockscreen deactivates and Profilematic (does it's job) switched to 3G in upcoming conversation.
Connection dropped. :P