Notices

sixwheeledbeast, I have AIS installed and 97-88% of time in C4. It is not "direct" AIS flaw, as it seems to not affect most users. I have no idea what triggers such behavior. What do You use? Bluetooth, GSM, wifi, any combination of those?

/Estel

Wifi only
No SIM in device.
Installed it twice and rebooted after each, Same results.

so I did a deep and successful research, but I need more feedback.
the scenario is as follows:
- install AIS
- turn off all signal strength getters, set one of the interfaces to show dialog on click, other one not
- reboot
- make device settle down
- powertop
- toggle interface w/o dialog on->off->on (or opposite)
- powertop
- if powertop changed, reboot
- let device settle down
- get interface dialog
- powertop
- if powertop didn't change open Settings, don't save, powertop
- open Settings, save settings powertop
On my device wakeups' arise seems to happen after getting interface dialog.
If yours powertop shows the same, get last svn revision from garage and replace files in /opt/maemo/usr/lib/hildon-desktop/advifsw, then reboot, let device calm down and repeat the powertop procedure.

--edit
You were too fast 412b. My answer relates to sixwheeledbeasts post
--edit

I am afraid I have to report similar.
Not as bad as sixwheeledbeast ones (not hitting c4 at all), but it definitely wakes up CPU (hindering to deep sleep).
But my (standard) batt still keeps me a day with middle usage.
I attach my outputs as zip.
first one is asis
second deinstalled (rebooted) aifs and apm
third only aifs
fourth only apm
fifth aifs and apm
six aifs and apm (rebooted)

@sixwheeledbeast (and Estel)
my experience with powertop output is that I do use it three times in a row and do see differences. First output is not reliable, but average of three gives a tendency.

Hopefully 412b got an idea, but even if not I am keepin this piece of wonderful soft (from devel)!

I do agree sometimes you can catch the device doing something, althought the results posted where the best out of a number of tries.

sixwheeledbeast, as You're the one that have high possibility of being affected by bug (I'm not at all), could You do as 412b requested? I tried, but I'm not affected by increased wakeups even after the 1st part of test.

/Estel

OK gonna little busy this weekend but will find time to test your suggestions and report back.

So it's taken most of this morning but I have complied three powertop's per stage. See attached.

In each section I have calculated the mean amount of wake ups

If it is certain setting causing this issue I think it would be best to provide a warning within the application somewhere.
Also I think the application should come default as the least energy consuming settings.

I currently have AIS set to all settings disabled (except WLAN and GSM on startup) I am currently getting 900-1100 Total wakeup's (double pre-installation).

Released a fresh build (13).
powertop shows me 0 or 1 for hildon-status-menu and wakeups are good.

what's new:
- enabling/disabling interface at all (needs reboot in this built, almost made it to change in runtime)
- default values for signal strength and network name set to false
- minor review

Thanks 412b,

seen it this morning and installed and at first glance it looks better. Will check it over weekend ...

Okay, did some checks and I have to say thanks again.
Attached a few powertop outputs. I still have over 1000 HW wakeups, but my percentual Cx state ratio and also average duration shows better values!
Thumbs up!