I have had blackouts at night, either with "kp v48" as with "kp v49". Only ocuure me when I leave loading at night. In the mornings I find online, yes fully charged.
What if I have seen is an improvement in battery life with "kp V49" and batterypatch version 1.9-7
Battery life was a big improvement in v48 for me. Gonna see how long I get with v49.
I did notice though, the handset didn't get quite so warm while I was watching videos over Wi-Fi with the charger plugged in after the update to v49.
Running at 1.1GHz I did notice video was slightly laggy under v48, whereas v49 was faultless.
So... Is Kernel-power v48 considered stable (in a kernel-power way) now? Are there any regressions or bugs?
Well, yes for a lot fo people.
But in my personal case, KP48 screwed up all the video system on my device: unable to watch videos saved, unable to record any video, unable to take any photos...
In adition, my battery life was worse than on KP47, where I'm for now.
But I have followed the KP48 threads and I'm the only one with this kind of troubles.
But in my personal case, KP48 screwed up all the video system on my device: unable to watch videos saved, unable to record any video, unable to take any photos...
In adition, my battery life was worse than on KP47, where I'm for now.
But I have followed the KP48 threads and I'm the only one with this kind of troubles.
Regards.
N900 strange device. From one to anoother its own glitches. They are unique))
- which version of compcache was included into kp?
Btw: i cannot retrieve anything relevant from the syslog other than (standard logging configuration after install of sysklogd):
- exiting on signal 15 (==SIGTERM, but only happened once)
- DSME: BOOTSTATE: "USER"
You should read my posts instead of going in a noob bashing rampage http://talk.maemo.org/showpost.php?p...postcount=1700
And as any other module, initialization is performed at insertion. Just read the module source code, it is quite easy to follow.
You should read my posts instead of going in a noob bashing rampage http://talk.maemo.org/showpost.php?p...postcount=1700
And as any other module, initialization is performed at insertion. Just read the module source code, it is quite easy to follow.
But in my personal case, KP48 screwed up all the video system on my device: unable to watch videos saved, unable to record any video, unable to take any photos...
I had this issue, when I loaded ulv. The low voltages didn't reboot my device, but made video playback corrput.
You should read my posts instead of going in a noob bashing rampage http://talk.maemo.org/showpost.php?p...postcount=1700
And as any other module, initialization is performed at insertion. Just read the module source code, it is quite easy to follow.
It was me who insist compcache statistics to be disabled because of performance reasons (there are several spinlocks involved as you may see in source code which COULD result in performance loss). Instead of enabling stats for general public, I think it is better to just rebuild module from compcache thread with stats enabled and test with it. And if you find which exactly kernel parameter causes swap trashing when RAM/compcache is full I think all of us will say BIG thank you . For changing compress threshold - maybe it will have slight difference in memory consumption, but I think our major problem is swap trashing, not few megs of RAM more.
EDIT:
And maybe it is better to continue compcache conversation on its dedicated thread.
EDIT2:
For those of you who are unable to play videos with KP48-49 - I am sure it is because of your overclocking profile, DSP subsystem is totally new and voltages which were OK with KP47, are slightly lower than needed in KP48-49. Try to increase your voltages by 1 and try again video playing(after reboot).
