maybe there was a bug in bq27x00-battery module earlier, and it just now popped up? perhaps it caused trouble before not only due to BME itself? i'm not an expert in drivers, but i hope that it may be long not discovered bug that when recovered from, it can help with something recently meant as impossible due to conflict.
(maybe it's one of reasons battery related crashes or unwanted scheduled shutdowns?)

PS: i don't touched bq module since i updated to v49, but general tasks of the phone works, hostmode works usb-networking too, compache works, so if you want me to test something another that those troubled battery module, maybe point me a feature to test?

@pali: Did you disable compcache notifications in your 20111006 build? I wonder because:
- /dev/ramzswap0 creation and initialization works every time now, repeatable, which it never did on my device
- 'rzscontrol /dev/ramzswap0 -s' shows a value of '0' for every statistic given

I'm asking that caused by the empty statistics, also that freemangordon mentioned issues with notifications enabled quite some time ago (that could have been the root cause of my shutdowns observed with all previous v48 and v49 builds)

Also, if I have compcache enabled (96MB) I am able to open microB, Opera, Wordpress client, Evince, moNav, and several other applications.

But, if nothing besides conky is running, and I start Frogatto, it loads, then during the main menu some slight pulseaudio stuttering can be observed. If I load a level and start playing, it gets worse and the control input lags, up to the point of overall heavy frame drops and complete loss of audio.

When at this point I try to switch to the task manager using CTRL+BCKSP, the device almost freezes, inputs take at least 20 seconds up to several minutes to be registered, and from the minimized conky I can barely see that CPU usage is almost(?) 100%, on 805MHz in my case. General load is equally high. Only if I manage to close the game, after some while it gets back to normal behavior.

IIRC freemangordon wrote something about swap trashing; it looks like it...

hey i experienced semi-random crashes during usb-networking
it happens if much of data is transferred at once, but not everytime.

i experienced it with kp48 too, but in kp49 it seems to trigger more frequent (or at least i wasn't so crazy to transfer nnn MB data at once, but i have done now)

to trigger that you have to transfer more than 100mb data in one data stream, like massive app install or huge up/download, it happens when one multifile transfer too.

i haven't checked but it may affect general networking not only usb ones (i have no wifi in home, so i have to use usb networking or to hunt for some not secured wifi in another place)

if it seems unconnected with kernel power, then sorry, but i feel i may have found a bug in KP, but if its really not it please point to where i have to search help.

notice that it doesn't happen when transferring huge amount of data while normal operation (ie. much of small chunks of data with many multi-milisecond time-breaks)

EDIT: this time i tried to transfer 500MB at once and 250MB at once, both failed once, and one recovered from filepart succesfully and one not

Sorry for quoting me... but anyone?

So which files do I download to install 49?

[ ] kernel-power-bootimg_2.6.28-10power49_armel.deb
[ ] kernel-power-debug_2.6.28-10power49_armel.deb
[ ] kernel-power-flasher_2.6.28-10power49_armel.deb
[ ] kernel-power-headers_2.6.28-10power49_armel.deb
[ ] kernel-power-modules-debug_2.6.28-10power49_armel.deb
[ ] kernel-power-modules_2.6.28-10power49_armel.deb
[ ] kernel-power-source_2.6.28-10power49_all.deb
[ ] kernel-power_2.6.28-10power49_armel.deb 06-Oct-2011
[ ] linux-kernel-power-headers_2.6.28-10power49_armel.deb

dpkg -i *.deb?

kernel-power_2.6.28-10power49_armel.deb
kernel-power-modules_2.6.28-10power49_armel.deb
kernel-power-flasher_2.6.28-10power49_armel.deb
kernel-power-bootimg_2.6.28-10power49_armel.deb (for multiboot)

Thanks, done.

Is order important?

yes, of course and also you must install each package separatly.

So it's kernel, then modules, then flasher?
Thanks