Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Hi Karam, I'm using your Patches now for a long time and simple want to say Thank you! Happy new year!

I've upgraded to the latest Battery-Patch (Stable) and take a look into the dbus-skripts. Now there were two overclock-profiles used but it seems that the overclock-call-profile is missing.

Greetings

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

i do many reboots but same problem any other solution for this

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

try reinstall speedpatch

apt-get install --reinstall speedpatch

hope it fix it

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

thanks alot ravent-n900 i finally install speedpatch

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

hello again everyone, sorry for taking so long to respond
i was busy with freespace2 open !! (really impressive game).. tried to port it to N900 but wasn't able to (some needed sources are still closed)


anyway
@SirSocke
thank you for reporting
i was actually testing that function with batterypatch-testing
it's time to get it into batterypatch i think
expect an update soon ;)

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Hi Karam,
I update battery-patch to v4.0 and I can not play any videos again. I have changed vdd1 to 0 but nothing change.
And when I reboot the phone, the boot video play very fast. It's just flash up.
I uninstalled it and reboot and have the reboot loop again.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Ola also updated to version 4.0 and having no problems.

kp49 and playing 720p video's

works like a charme :)

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

@Kenny.Vo
you have a strange N900 behavior

i will release a new batterypatch for unstable devices like yours
with disabled vdd1 and no switching to overclock profile while brightness is on ...(only with unlock and lock)
BUT IT CANNOT INCLUDE THE TWEAK call response

that's how it should be ;)

//EDIT
batterypatch-for-unstable is on it's way to devel
Kenny.Vo try and report

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

@Karam
After reflashed my phone, I installed battery-patch v4 and lastest CSSU. And then I turn off the phone and switch on the boot videos also play very fast.
I uninstalled v4 and installed your batterypatch-for-unstable. My N900 work well and don't have any problem.
I don't know what's wrong with my N900. Am I chose the wrong image flash firmware? (I'm using latest Maemo 5 Global release)

---Edit
@Karam
After tried again I found that I forgot to edit overlock-call and change vdd1 to 0 :). And now my N900 having no problems with battery patch v4.
Thank Karam for your supports and batterypatch-for-unstable package. :)

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Hello :)
I updatet speedpatch from version 3.5 to 4. I noticed that my cpufreq sets to 720 (minfreq) - 805 (maxfreq). So I rebootet my device and the frequencies seems to be normal (250-900) again but it sets the frequencies back to 720-805 some time later.
I also changed my overclock profile to 250 to 900 (I tested with 950- with 3,5 a while ago- but it was unstable :) )

So whats wrong?! :)

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

willi6868 this happens if you continued using N900 directly after receiving a call
this is totally normal
after some time it will auto set min to 250 or 125 according to the status

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

So now I have a problem.

I installed both speedpatch and batterypatch on the power49 kernel.

Then I decided that since it was at 805 MHz that I wanted to overclock it. So I did, and I cannot boot at all on power49. I can boot just fine from stock kernel but I really use PK a lot. I uninstalled speedpatch, but that didn't fix anything.

I can't reflash it as my USB port broke, so is there anything else I can do?

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

forget to change vdd1 to 0 ?

the only solution (if you were able to access N900) with stock kernel (multiboot) is to check the overclock profile


PS: it's batterypatch btw not speedpatch

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Okay, I'll give that a try.

Could you tell me how I would go about doing so? And if I can edit the power49 overclocking settings, where would that be?

EDIT: nevermind, I figured out where kernel-power was located (in /etc/default/)

Thank you!

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

http://s1113.photobucket.com/albums/...108-052200.png

any idea to get rid of this ?

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

why don't you check faqs from page 1

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

well you need to install speedpatch and then uninstall it again
after uninstalling reboot your phone twice

hope it will help

thank you karam

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

how to revert back to battery patch 3.5 ? checked repository but ver 3.5 is not there anymore.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Here you go buddy
http://repository.maemo.org/extras-d..._3.5_armel.deb

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

@panjgoori
it would be helpfull if you told me why did you reverted to the older version

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

I wanna remove Speedpatch by typing apt-get purge speedpatch.
But after rebooting I'm getting

BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

-sh: /home/user/.bashrc: line 5: cannot create /dev/cgroup/cpu/user/2686/tasks: nonexistent directory
-sh: /home/user/.bashrc: line 5: cannot create /dev/cgroup/cpu/user/2686/notify_on_release: nonexistent directory
~ $

How can I solve this?!

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

use the script in the first post, for people who have messed up with the verions, it helped for me.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

hmm i can now see why people are still having this problem after removing speedpatch

@willi6868
you must have used the script version before right ?

if so :
1st post updated

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Since you said you wanted to have this discussion here, and aren't replying in the other thread, fine. I'll bring it here.

I find great irony that you're instructing people how to repair one of the permanent changes done in the post above this, while in other threads saying:

The current version does, in fact, do permanent changes. On install it replaces your .profile and .bashrc files, but fails to restore them when uninstalling. (See prerm and postinst for the deb if you don't believe me.) It also sets your kernel config to "default" which on most systems is (250-600), without mentioning it anywhere.

So, since I bothered to grab the latest versions to see what it actually does, lets take a look-see shall we?

All "speedpatch 2.0" seems to do is add a separate cgroup for CLI commands and adds shell-scripts to that cgroup as they run. Nowhere do I see it adding groups for desktop and applications, as stated in it's description. Which means it's not really doing anything but lumping shell scripts and xterms together into a shared cgroup. How does that help speed? Since most apps are not shell scripts, I don't see how that helps anything. Further, it depends on KP without specifying it as a pre-req. Everything I'm seeing would indicate that speedpatch has a better chance of slowing things down by setting the kernel back to default than it does speed things up.

As for Batterypatch 4.0: The current version also sets your config to default kernel config, on install and on uninstall. All it seems to do is set the nice levels on a few apps and loads a kernel config if your close the keyboard and it goes into sleep mode. Namely, it renices modest, browserd, image-viewer to a value of 1 and ignores nice loads. It loads a separate config for when you open it, and when a call is going on. I note that it tries to renice "background apps" via a call into /dev/cgroups, but unless you have speedpatch installed (not a pre-req!) it will find nothing there, as cgroups aren't mounted by default.

The "speed" from battery patch comes from the fact that you're heavily overclocking the system (705-850!) when the system is awake. For calls, you're using a (250-805) config that's closer to stock, but still overclocking. (Are you telling people that your scripts overclock their devices?) And for the sleeping system a (125-600) config that ignores nice loads.

This means when an app in the nice list (modest, browserd, etc) wake the system up to do something, when it's closed, it will run at 125Mhz until done. Weather this is even saving battery or not is questionable, since it's against the "race to finish" idea in multiple ways. Also, it's enabling 125Mhz, which just about everyone including Nokia, Titan, and Lehto believe is unstable.

So what does the combo of these two do? From what I'm seeing, next to nothing, except that it screws with your configuration, enables a kernel speed that Nokia and others avoid because it's unstable, and adds a user cgroup to lump scripts and shells together for sharing resources. Not something I'd care to inflict on anyone.

You've been asked, on several occasions (even on your dedicated thread) to explain what these patches are doing, and why it's helpful. You've declined to give much information at all, and what information you have given (the package description, for example) is patently false. So maybe that's where you should start in your "proof" of what either package does.

The fact that the entire install is nothing but scripts that tinker with kernel settings in a way you're incorrectly describing doesn't lend any confidence that anything you're saying about this is correct.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

As for speedpatch

first point is :

permanate changes :
first by default there are no .profile nor .bashrc at /home/user (reflash and see by your self)

so when uninstalling speedpatch
it leaves .profile.bak and .bashrc.bak (if there any created by user)


----

second point : what the hell has speedpatch to do with kernel-config ?
it doesn't touch it

----

thrid point : i'm not sure it depend on KP..

-------

As for batterypatch

first point :

it sets kernel-config default default in postinst
you know why ?

well so if any unexpected reboot happen
the user can uninstall batterypatch saftly
and btw default profile will be changed to overclock after the first lock of a boot up

and in prerm it sets to default
so if overclock profile is removed
there will be no reboot loop

---
second point :

actually you did discover a bug (it wasn't in previous versions)

just fixed it .. thank you
it should detect if speedpatch installed or not

and i saw at other threads you said overlcock 750-850 when a call is recieved
actually it's 720-805 (KP49) and 700-905 (KP49>)
and this will noticably improve the response on calls

and i set 805 as max because overclock uses conservative module which require such oc (leaving it 600 will cause lags with conservative module)


PS: i may not be able to write any replies till tomorrow

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

listen up woody boy
i have just reflashed my n900 and tested the speed without speedpatch

transmission lags to hell
nokia panorama lags to hell
multitask 8+ browser windows lags to hell

with installed speedpatch

transmission lags are reduced by half
nokia panorama doesn't lag at all while precess a pic
multitask is way improved

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

woody14619 got a point
also karam got a point
trying to be fair here

speedpatch 100% it improves multi tasking and the torrent application
batterypatch watching my old battery graphs ! it does increase batterylife compaired to dsp profile

IMO
IMO
IMO

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

so anyway..if i remove these files is like i never installed speedpatch and batterypatch right?

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Why not restore them if they exist? You go out of your way to back them up, and then don't restore them? If there were files, you're not restoring them on uninstall. That's a change.

No, batterypatch does. I was reviewing both at once, since you clearly have the assumption that both are installed together. (Batterypatch having an implicit reliance on speedpatch being around to mount cgroups as an example.)

Fair enough. Can you mount cgroups with base PR1.3? I don't know, because I never tried.

I also see you never addressed one key point of what I was saying. Your description (both here and in the deb) says you're creating cgroups for the desktop and for apps, when in fact you're doing neither. They only cgroup you're making is for bash and shell scripts using bash. The desktop and user apps are already in a cgroup, created by Nokia as part of the kernel compile.

Can you please address why you're lying about what you're doing?

The kernel already does that if there's a lockup, even if you default it to something else. If you load a profile as default, and the system reboots twice in the span of a couple minutes, the kernel automatically rejects loading the default config and uses the built-in Nokia-based values (250-600, high-voltage). That's been in there since Titan's kernels, well before KP. The fact that you don't know this, shows how little you know about this whole process.

Again, you show you have no idea what you're talking about. A missing default kernel profile will never cause a reboot loop. A missing module or kernel file may, but a profile never will. It will simply stick with the built-in Nokia defaults if the profile it's instructed to read is not present, or is corrupt in some way.

Nokia, as part of the phone app, triggers the phone app to get real-time priority, and locks the kernel at a set speed (600 as I recall). At that speed, the phone app takes about 60% of the CPU and allows enough background time for apps to continue to function if needed. I made plenty of calls using the stock 250-600 kernel and noticed no quality issues. If you're seeing issues, it's probably because you're either running something highly CPU intensive in the background, or because you've installed a speedpatch that's screwing around with cgroups and letting shell scripts take higher priority than they should!

Also, you again show ignorance on your own scripts. In the postinst for batterypatch, you check for version 42, 47, and 48 of KP, and copy the config settings from /opt/dbus-scripts/ to /usr/share/kernel-power-settings. The config files put in place for those kernels is:
call: 750-850 non-call:250-805 sleep:125-600 (all with SR2 set)

For all other kernels, the files used are
call: 720-850 non-call:250-805 sleep:125-600 (all with SR1 & 2 set!)

Also, for all but 42, 47, and 48, you're enabling SR1, another problem. You do know that with K49 (and 43, 44, 45, & 46) that SR1 is not always stable, right? The patch to handle that is slated for K50, and only those doing kernel testing have a version of K49 that might be recent enough to allow this in a stable way. Did you know SR1 is also never stable for 125Mhz, since Nokia never enabled it and never setup the e-fuse stuff for that? Yet you tinker with it.

It's no wonder people are having problems with their devices using these patches.

Conservative module? Do you mean the config setting for the governor? All that does is tweak how quickly the system jumps from one frequency to the next. The "ondemand" setting sets up the governor so it quickly ramps up to top speed (>50% cpu use for a short time ups the clock). Where "conservative" requires >80% use for a moderatly longer time to up the clock. Upping the max frequency has no effect, since the "lag" you're seeing is caused by the governor not moving the clock speed up quickly enough. The only thing you can do to make the system more responsive with the conservative governor is to up the minimum frequency, so you start out at a higher basis.

How is it you're tweaking values when you don't even understand the basic concepts of what they do?

Also, are you mentioning it anywhere that you're overclocking people's devices? Are you warning people that your script, notably the batterypatch, is not only silently installing kernel-power (HAM installs prereqs silently), but is overclocking their device? Don't you think that's worth mentioning on the top post, or in the description?

And you're not just overclocking them... you're severely overclocking peoples devices, placing the minimum clock speed well above the maximum limit deemed "safe" by TI and Nokia. It suddenly makes sense now why so many people with your patches were complaining about how hot their phone gets when they use it to call people. You're locking it into a severely over-clocked state. It's getting hotter, and using more energy for calls for the sake some perceived "clarity". That's the opposite of battery savings...

And you're turning SR1 on in several kernel versions where it's known to have issues. And enabling a frequency known to be unstable by Nokia and all overclock developers.

So, lets address the key items here in a nice little list:

• You're overclocking peoples devices without telling them. (BP)
• You're setting a minimum clock of >700 when Nokia max is 600. (BP)
• You're using a known-defective frequency (125Mhz) when asleep. (BP)
• You're not remembering/restoring actual kernel config settings at install/uninstall (BP)
• You're causing a few apps to not trigger cpu raise when active, removing any "race to idle" benefits.
• You're claiming to setup cgroups that you're not actually setting up. (SP)
• You're setting up a cgroup for shell scripts, for no real reason. (SP)
• You're removing any other user/app settings placed in .profile & .bashrc (SP)
• And not restoring those when uninstalling. (SP)
• You're calling on cgroups in BP, which is mounted only in SP. (Mix)

The real irony I see here is that speedpatch does frankly almost nothing. Most of the speed increases are coming from batterypatch, which are a mix of sever overclocking, and renice-ing a few apps with a config setup to ignore load caused by them for governing purposes. Battery savings is coming almost exclusively from the fact that you're forcing KP install, with a very small margin possibly coming from renice-ing a few processes in a couple situations. (And even that's debatable.)

Side effects include heat and quicker battery drain while making calls (from sever overclocking), instability (from overclocking, SR1, and using unstable frequencies), and perhaps slightly faster script execution.

I also read in this thread something about a "completely fare scheduler". Where exactly is that being installed and enabled? I see nothing affecting the scheduling algorithm of processes, outside of the minor tampering with cgroups done in speedpatch (which is a far throw from changing the scheduler).

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Sorry, but you're full of it. I can list for you the scripts installed by speedpatch. I downloaded the package, extracted it by hand, and looked at every script it runs, everything it installs, every action it takes.

The only thing speedpatch does is adds a cgroup for shell scripts, and puts a mechanism in place so shells scripts add themselves to the cgroup as they start up. Now it may be that some parts of what you're looking at are actually run (or lagged by the use of) shell scripts. That's fine. But it's not doing anything claimed by the install description of the package. It doesn't setup cgroups for the desktop or applications as stated. Nor does this speed-up apply to all applications, only ones that are or rely on shell scripts.

Now if you installed batterypatch too, that starts to make sense, since batterypatch also installs KP, which is where you'll see real speed and battery performance changes happening. But that has next to 0 to do with these patches. I can make a nearly empty deb that just depends on KP49 and adds a profile to load on as default and get the same results.

As for callings someone a boy... Shows what an ignorant person you are. But then I would expect that from you, given your past posts, ramblings, and pontifications on topics you are clearly not educated on.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Have you tested them independently, or only together. I'm willing to bet most of your speed is from batterypatch, not speed patch. Unless your torrent app is just a very large shell script, it's unaffected by speedpatch.

Your battery graphs can't be that "old" if you're comparing it to the dsp profile, since that was only put out about a couple weeks ago. As for batterylife being better, I see no reason why it would be the case, since for most of the time you're using the same profile as dsp. The only difference between the overclock profile in batterypatch and the dsp profile is that it's enabling SR1 by default, and using a slower governor.

Mind you, you could simple enable SR1 yourself, and I'm betting your battery life would be the same as it is with this patch. It's one line in one file, vs a bunch of scripts doing all this to your system.

Want proof? Try uninstalling battery patch, copying dsp to dsp2 in the kernel-config-scripts folder, then change the line in dsp2 so that the VDD1 value is set to 1. Then load that profile and see if it's not identical to the battery usage from this patch.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

maybe mohammad is karam evil twin..dont know and dont care...just want a solution to get rid of these patches efectively without reflash...:(

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

If you installed the most recent ones (BP 4.0 and SP 2.0) the commands Karma gave should in fact remove any residuals after uninstalling the apps. One thing it may not do on an uninstall is remove KP if it installed that as a pre-req for batterypatch. But then you probably don't want to do that anyway. And if you did, KP comes with an uninstaller app that re-flashes the Nokia kernel and removes itself properly.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

ok..finally we all agree on something..tks woody!
By the way..i deply believe that karam has the best intentions and has been doing a good job, and i am proud that he is such an active member of this community..but..i am uninstalling this.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

It certainly wasnt any faster for me, but I run my device at 450 min 1000 max, so its pretty quick anyway :D

edit: oh yeah and it definitely doesnt uninstall properly:rolleyes:

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

I agree. In fact, looking at what speedpatch does, it may in fact help with some issues where scripts are used. In particular, where scripts are called for taking actions based on real-time feedback (dbus-scripting for example). But it's not something that's going to help the common user for the most part.

My bigger issue right now is with batterypatch, since it's doing some pretty nasty things, like severe over-clocking and using configurations known to be unstable on most hardware. (SR1 enable for older kernels & over-clocked settings, using 125Mhz at all, etc.)

I don't have problems with people wanting to help out and code things. I take exception though when people make destabilizing, and in some cases potentially damaging mistakes, and then try to defend those mistakes when they don't understand what it is they've done. In this case both freemangordon, myself, and others, have on several occasions asked why he's doing things, and he's repeatedly replied with "it's all based on testing" to "I don't know why it works".

Sorry, but I wouldn't let someone who thinks they may know how to do heart surgery based on practicing on others (and causing issues for / killing several patients) anywhere near me. No difference here. Nor would I want them to freely be practicing medicine while clearly not knowing what they're actually doing. Thus why I'm here: Lots of people have had issues after installing these patches, and when anyone tries to help those people and tells them to not use speedpatch/batterypatch again, Karam get's all defensive and asks why everyone is attacking him.

It would be just like a doctor maiming people, then suing other doctors who advise patients not to go back to the doctor that maimed them. Does that sound sane? If you were a patient in that waiting room, wouldn't you want someone to come in and tell you he's maimed several other people, and you should run now, while you have the chance? Sure, some are always going to go back to the witchdoctor... that's their choice. But how can you tell which ones are good or bad without being able to talk about doctors in general? Without talking about the treatments, how they work, and what proof exists to show it's actually doing good?

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

There's quite a lot of heat round here! From a bystander's point of view, it seems like it was a useful experiment. Sympathy for the guinae pigs.

Thanks Woody (and Karam) for thrashing out what these scripts do. I got a bit lost in some bits where tempers appeared high or technical acronyms weren't obviously expanded. Is it about right to assume that
(a) Battery Patch is a no-no and conflicts with GPU operation, amongst other things?
(b) Speed patch is pretty 'safe' but fairly pointless unless the device is constantly performing high volumes of i/o through the cpu?
(c) Both need a wiki page for uninstall instructions?


ps Karam: you need to sort out your Karma. Single figures makes you look like a proper shady character!

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

Hmm.. since it's enabling SR1, maybe? But that link isn't totally clear yet. Let's say it's probably not a good factor to add to the "why my device might randomly reboot" pool.

Not I/O. It's pointless unless you have a lot of shell scripts running, monitoring dbus signals and changing settings based on that (like if you're running batterypatch...)

Actually, the install/uninstall scripts can easily be tweaked to properly do what's needed. It's just not doing it now....

The biggest issues are the crazy (7X0-850) overclocking, use of SR1, and use of unstable 125Mhz. If you took those issues out, it wouldn't be all that bad. But those alone, yet alone staked with other mods, make the whole deck of cards wobbly.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

TBH I have no idea why 125 is not used by Nokia (and Titan and others). I've never seen reports of 125 being unstable and I am using it on my device. The same for SR and 125 - actually efuse value for 125 is very high, almost enough voltage to run 250.

And for speedpatch doing nothing - well, it does, it ruins all the cgroups setup done by Nokia.

Re: [ANNOUNCE] Speed Patch + Battery Patch + Tweaks --> Everything Needed To Have A Perfect N900
 

If you want a quick N900, you have to uninstall some applets.

Applets use deamons, using more memory and CPU but are very usefull.

On computer, you cand add memory but on N900, you can't do it :(.