You mean the one you were working on (and PM me about) after I wrote this post? Sorry, I'm not precognisant. I can't check a version you released after my comments were made.
break!!
another incorrect
kernel-power-settings doesn't modify /etc/pmconfig
Technically we are both correct and both wrong. kernel-power-settings overrides /etc/pmconfig by loading it's own preferred default if it's installed. So, the proper operational order appears to be:
Kernel starts with Nokia base-line defaults at boot.
Kernel loads /etc/pmconfig shortly after fs is mounted.
If kernel-power-settings is installed, it's scripts load /etc/default/kernel-power if it exists, so long as this isn't the second reboot in under 5 minutes.
So to be sure to capture existing settings for later restore during uninstall, batery-patch should backup /etc/pmconfig AND /etc/default/kernel-power. The later is a link, so capturing/restoring it isn't quite as simple. (It complicates the restore, as an existing link needs to be removed first...)
Technically, if you never call kernel-config default <filename> in any of your scripts, then you don't need to backup either file. If you scripts are changed to only call kernel-config load, then all changes made will be temporary, and it will never change the default, removing the need to restore it in postrm. That currently is not the case, as you do call kernel-config default in at least one of your scripts.
You mean the one you were working on (and PM me about) after I wrote this post? Sorry, I'm not precognisant. I can't check a version you released after my comments were made.
Technically we are both correct and both wrong. kernel-power-settings overrides /etc/pmconfig by loading it's own preferred default if it's installed. So, the proper operational order appears to be:
Kernel starts with Nokia base-line defaults at boot.
Kernel loads /etc/pmconfig shortly after fs is mounted.
If kernel-power-settings is installed, it's scripts load /etc/default/kernel-power if it exists, so long as this isn't the second reboot in under 5 minutes.
nothing new here
//edit
but nokia base-line is pmconfig i guess
Technically, if you never call kernel-config default <filename> in any of your scripts, then you don't need to backup either file. If you scripts are changed to only call kernel-config load, then all changes made will be temporary, and it will never change the default, removing the need to restore it in postrm. That currently is not the case, as you do call kernel-config default in at least one of your scripts.
well this is something didn't came on my mind
will deal with it later, after the new speedpatch
wow...with all testing its give you 30 days WTF man
What are you talking about? There was a good 5+ month period between when Titan left and Pali picked up working on the kernel. And I never claimed to run ALL kernels, or that I was getting 30 days from day 1. In PR1.0 I was lucky to get 7 days before I needed to reboot, mainly because of memory leaks in Nokia/Hildon code.
Understand, I was one of the first people to have an N900. I pre-ordered, twice (read the threads here for why twice), and owned one within the first week if it hitting the open market. I've had my N900 for over 2 years now, and have had a several periods where it's gone >30 days without a reboot. Most of those have been in PR1.2/Titan-KP or PR1.3 with Pali-KP.
Also understand that I don't test every kernel or every package known to man. I update things when I need to, and reboot when I have to (which is quite rare). And with a few exceptions, most updates don't require a reboot. Updating ModRana or Boggle doesn't necessitate one to reboot their phone, unlike WP7.
and woody ?? (again)! i have never stated that i have adapted cgroup to syspart before
didn't like this from u
??? What are you talking about? I never claimed that you adapted cgroup to syspart before this. Where do you see me saying that? I didn't. I'm simply stated that it may not be reasonable to expect the next version to behave like the previous version because you have dramatically changed how you're doing something. Period.
You stated in your own thread that this was a major change for speed-patch. What's so hard to understand about that?
Regardless, changes to /etc/pmconfig will be short lived if you are using battery-patch, since it loads it's own configs within the first minute of the system starting up. Since that's a fact, and you can't debate it, you make things up and claim I say things when I don't.
I'm kind of tired of the childish games and lies. It's bad enough that you say/claim things when you don't know what you're doing. Or when you're doing damaging things to other people's devices because you can't be bothered to do proper testing or read documentation about dbus results. But when you actively lie about what someone is saying, and back hand them, when in PM you're asking for help on scripts and how things work? I've known 5 year olds with more common sense and respect for others.
Btw: ONE person does not prove much about any program. Especially when the same person later notes this was "normal use", which could mean just about anything. (eg That normal use could mean he made a 10 minute call with BP and a 20 minute call without... both "normal use", but both take vastly different tolls on the battery!) I also note you didn't mention at all about several people having issue with ring-stuttering or video playback being a problem after installing a version.
Funny that you only present a single positive review, vs dealing with the factual discussion at hand. Frankly, when someone asks "if I change pmconfig will it work if I have battery-patch installed", the factual answer is NO, which is what I answered. We both know that to be true, but rather than accept the truth, you play a childish game, claim I say things I've never said, and act hurt.
battery patch (except the last version that was stuttering my videos) is a great program....I remember the days where I had to charge my phone every night.Now, it lasts for two days so I`m not anxious to rush to the power cord every single night.....keep up the good work!
Hi Woody! I hope that when you talk to karam you'd also consider the fact that English is not his native language. I wouldn't really want to join in this conversation but I, as a non-native English speaker, feel that sometimes you feel that he is being rude when he isn't. Your tone or wording is actually pretty harsh.
I do understand why you are making so much effort in posting here and correcting/guiding karam but I think you can be more civil, which I have seen you are capable of when karam is following your advice.
I'd also share my experience as a non-coder and previous user of karam's patches. I did notice improvements in my battery life and apparent performance of my N900 when I still had the patches installed. I used the script versions and had KP47 then. I never tried the repo versions and I didn't use his profile that came with the patches as I don't want to overclock my device. I'm now running my N900 without the patches and I do remember my browser being more responsive when I had them. Thanks for your efforts, I'm looking forward to more constructive/productive exchanges between you guys!
@ed_boner
yes totally safe install and uninstall
and no need to purge
i added a line to *rule* file that does purging from FAM or HAM
@woody14619
as vetsin said : do feel that i'm rude ?
if you do .. well i don't mean to be so
but check what sophocha posted
and those links you provided . they had a problem with a previous version
but currently batterypatch is bug free (at last)
as well as the new speedpatch (but need replies about it)
@vetsin
if you are using the script version , i highly recommend to switch to repo version ,because finally i was able to make cgroup uses syspart configs and it does improve the device response, and it installs/uninstalls safely
@sophocha
is the current version causing any troubles ?
