Overclock

[Guest kallt_kaffe]

Here is how i did it on FLB1.5:

Copy Your own build.prop file from /system (with any explorer) to your SD Card and to Your computer

Download this zip: http://android.modaco.com/index.php?s=&amp...t&p=1297222

Edit Your own build.prop with adding dalvik.vm.execution-mode=int:jit to the latest line

copy the modified build.prop to the downloaded packet

boot into recovery

do nandroid

flash the modified zip

clear dalvik cache in recovery

reboot

If You loose root, then flash superuser again with recovery.

I wonder how stable JIT is with swap supported kernel (virtually no memory problems).

How long have you been running this JIT implementation? I added it to my U8100 ROM and it seems to work fine but I'm worried about stability. I've heard JIT is not stable on 2.1 but maybe that's something of the past that has been fixed now?

[Guest Daz555]

I think I noticed a first indication that 690Mhz is sometimes an issue. I played Tiki Towers (a game that was practically unplayable before, this may be due to an update though, can't be really sure) and after a few levels it started to get choppy. I turned it of (this was yesterday) and today I played the same level and it was smooth again, but the same happened on the next level and so on.

Only saying that still the most processor intensive stuff might not be that smooth even if they initially seem so. Or maybe it just got to a more detailed level and has nothing to do with overheating B) Can someone reproduce this with another game or app?

Just to note that nothing bad happened to the phone, maybe it detected that it got too hot and just reduced the CPU usage cause there where no reboots and no FC's so it appears to be completely safe under any circumstances :lol: Cheers!

Stuttering could also just be down to a lack of RAM.

[Guest il_cholo]

do you have jit enabled?

yes I forgot to mention, JIT is enabled

[Guest MikeRame]

I downloaded it, and copied the build.prop into the zip. Clockwork recovery aborts install "Can't open .../mcr_jit.zip (bad)". What did I do wrong?

Edited September 28, 2010 by MikeRame

[Guest ambrozija]

yes I forgot to mention, JIT is enabled

And how did you had it enabled: using a2sd jit or flashing it with mcr_jit.zip?

Edit: We're talking eclair, right?

Edited September 28, 2010 by ambrozija

[Guest hungi]

I downloaded it, and copied the build.prop into the zip. Clockwork recovery aborts install "Can't open .../mcr_jit.zip (bad)". What did I do wrong?

Hi, i updated my pulse with the mcr_jit.zip. Since it was already modified, you dont need to edit anything, just flash it with clockwork in recovery mode. Hope it helps.

My worst/best score btw is: 4.124 / 4.818 Miflops (FLB1.5, OC@691Mhz with 32Mb swap)

[Guest MikeRame]

Hi, i updated my pulse with the mcr_jit.zip. Since it was already modified, you dont need to edit anything, just flash it with clockwork in recovery mode. Hope it helps.

My worst/best score btw is: 4.124 / 4.818 Miflops (FLB1.5, OC@691Mhz with 32Mb swap)

It worked, I think 2.97 linpack score on FLB 1.6 64MB SWAP and no overclock.

EDIT: Root is lost, I'm going to restore it and run linpack again...3.67 @760MHz

Edited September 28, 2010 by MikeRame

[Guest LavX]

It worked, I think 2.97 linpack score on FLB 1.6 64MB SWAP and no overclock.

EDIT: Root is lost, I'm going to restore it and run linpack again...3.67 @760MHz

I used root explorer to copy the files and no problem with root. Just reboot when you already overwrote the files.

[Guest Krinyo]

How long have you been running this JIT implementation? I added it to my U8100 ROM and it seems to work fine but I'm worried about stability. I've heard JIT is not stable on 2.1 but maybe that's something of the past that has been fixed now?

Well, 24 hours now, I think. :lol: Not so much, but I have more than 24 installed apps and 60 MB active swap, it's maybe describe a little how much I'm using my phone. B) Typically my battery not last for 16 hours.

I don't have any reboot yet, and every installed apps working perfectly. Rock solid so far.

Krinyo

[Guest Krinyo]

Hi, i updated my pulse with the mcr_jit.zip. Since it was already modified, you dont need to edit anything, just flash it with clockwork in recovery mode.

Yes, but i don't want to overwrite my FLB1.5 build.prop file with an older mrc build.prop file. I suggested this method for safety reason: if You take your own config, you can't make bad things. :lol:

If You have root explorer (i don't), then copying the files and adding the line to build.prop in the phone itself working too...

BUT, before You change anything, do a nandroid, and don't forget the "menu+red key+switchon" combo for recovery. B)

Edited September 28, 2010 by Krinyo

[Guest InstantWater]

Well, 24 hours now, I think. :lol: Not so much, but I have more than 24 installed apps and 60 MB active swap, it's maybe describe a little how much I'm using my phone. B) Typically my battery not last for 16 hours.

I don't have any reboot yet, and every installed apps working perfectly. Rock solid so far.

Krinyo

16 hours????? B) Not too much. It means I have to charge it everywhere I can. Or not?

[Guest InstantWater]

Yes, but i don't want to overwrite my FLB1.5 build.prop file with an older mrc build.prop file. I suggested this method for safety reason: if You take your own config, you can't make bad things. :lol:

If You have root explorer (i don't), then copying the files and adding the line to build.prop in the phone itself working too...

BUT, before You change anything, do a nandroid, and don't forget the "menu+red key+switchon" combo for recovery. B)

So, which build.prop file should I use? B)

[Guest Krinyo]

So, which build.prop file should I use? B)

Your own. B) Copy it from the /system to Your SD-card, and send it to yourself with GMail. :lol:;D

Edited September 28, 2010 by Krinyo

[Guest Krinyo]

16 hours????? B) Not too much. It means I have to charge it everywhere I can. Or not?

Yes, not so much, BUT, i'm using my phone for a lot navigation, taking notes all day, and using XE Currency many times in any day. And mail, web, etc... i'm a really HEAVY user. If my phone take only one day without reboot with JIT enabled, then it will working forever. B) And now I have more than 24 hours without any problem.

PS: sorry for my english. :lol:

Edited September 28, 2010 by Krinyo

[Guest InstantWater]

Your own. B) Copy it from the /system to Your SD-card, and send it to yourself with GMail. :lol:;D

Okay, I will B)

Thanks :lol:

[Guest il_cholo]

And how did you had it enabled: using a2sd jit or flashing it with mcr_jit.zip?

Edit: We're talking eclair, right?

yes eclair, I use FLB-1.5

I used root explorer to copy build.prop from /system to my SD partition

downloaded mcr_jit.zip

pulled build.prop from SD card to my laptop, edited adding the last line "dalvik.vm.execution-mode=int:jit" and replaced the one on the zip file, signed using "autosing" and flashed using amonra

if you lost your root you can flash it using su-2.3.2.1-ef-signed.zip

that´s all what I did, I hope it helps you.

Edited September 28, 2010 by il_cholo

[Guest ambrozija]

yes eclair, I use FLB-1.5

I used root explorer to copy build.prop from /system to my SD partition

downloaded mcr_jit.zip

pulled build.prop from SD card to my laptop, edited adding the last line "dalvik.vm.execution-mode=int:jit" and replaced the one on the zip file, signed using "autosing" and flashed using amonra

if you lost your root you can flash it using su-2.3.2.1-ef-signed.zip

that´s all what I did, I hope it helps you.

OK mate, thanks, although a bit late :lol:

For anyone interested: Backed up everything with TitaniumBackup; upgraded to flb 1.6b (yeah, I know, 1.7 is out...I was just an hour early. You can't really keep up with flib B) ) I did JIT as described here (btw, didn't signed the zip. I wasn't aware of it, but it worked just fine). I lost root and flashed the last Superuser version 2.3.6.1 and got it back. Flashed the flib's OC update. Restored everything with TB.

Now I have [email protected] and SetCPU LongBench@7800. Really loving this! B)

[Guest hungi]

The jit killed my phone (2.1 FLB based), its freezed increasingly so i went back to a swap-enabled, oc-disabled version. :lol:

[Guest Daz555]

The jit killed my phone (2.1 FLB based), its freezed increasingly so i went back to a swap-enabled, oc-disabled version. :lol:

JIT and OC are not related though so you can still have the OC back even if you don't like the stability of JIT.

[Guest hungi]

JIT and OC are not related though so you can still have the OC back even if you don't like the stability of JIT.

Thanks i am aware of that not related, but first of all i needed a stable phone so i disabled that also. B)

Update: its still stable with overclocked kernel. :lol:

Edited September 30, 2010 by hungi

[Guest hungi]

What is the lowest CPU frequency that is enough for a stable system? Im playing with profiles in SetCPU, that way we can use lower frequencies (for example if screen off) so we can actually save battery life. Am i right?

[Guest Simon O]

What is the lowest CPU frequency that is enough for a stable system? Im playing with profiles in SetCPU, that way we can use lower frequencies (for example if screen off) so we can actually save battery life. Am i right?

245Mhz is the lowest. I remember with the old custom 2.1 ROMs would crash the phone because the CPU was being clocked lower than 245Mhz, so I assume the CPU can't go any lower than this.

[Guest ambrozija]

245Mhz is the lowest. I remember with the old custom 2.1 ROMs would crash the phone because the CPU was being clocked lower than 245Mhz, so I assume the CPU can't go any lower than this.

I have set it to 122.88MHz using SetCPU, but when I check Frequency Stats in Android System I see that it spent 0% on this frequency (74% on 691 and around 14 on 245.76). So is it possible that it is not accepting this lowest freq.?

[Guest menno2]

4.4 Mflops with froyo 2.2 jit enabled SWAP 32 (swapper2) on a 2x 16gb cpu maxed at 655mhz

[Guest gusthy]

245Mhz is the lowest. I remember with the old custom 2.1 ROMs would crash the phone because the CPU was being clocked lower than 245Mhz, so I assume the CPU can't go any lower than this.

It could go down to 122800 for me seamlessly