Originally Posted by wicki30

@Vurrut
Flashed vurrutKer for CM7 v2. All bins working upto 1300 with no probs. Since OC is stable, would it be possible to add 1 more bin for UC 200mhz? Thanks.

GT-i9003 on CM7 - 14.12
+GPS and DSP Fix on
Vurrut kernel #2

Work on it! the problem is whit 200 jump to next 300, and no use.

vurrut, I found another minor bug which is easily recreatable, at least on my phone.


right now I'm testing vurrut/joode 4.6, both with the included kernel and uc9t2.

as far as I've discovered, this bug only happens in a very specific action occurs, namely trying to activate the lockscreen while playing a game with high cpu demand. it happens when I set the max cpu to 1.25, 1.2 and also when I set it to 1.0 (depending on the kernel). it happens on all governors available in the kernel loaded at that time. it does not happen when using stock kpq, deodexed, and either uc5t6 or uc9t2. therefore, I would also assume that if I tried your kernel by itself in stock kpq, it would work fine, which means it should be somewhere in the rom itself.

my settings:

Any governor, any kernel

300 min and 1.0/1.2/1.25 max for all apps listed

my test:

1) play the game and press the power button to activate the lockscreen

2) play the game, then press the home button and wait for the desktop to appear before activating the lockscreen

games that always work (both 1 and 2 without random restart):

bubble blast
cut the rope
abduction2
sliding blocks
bubble birds

games that fail test 1 and pass test 2:

ace's jewel hunt
all angry birds games
zombie defense


as mentioned, the first group is less demanding on the cpu, and the second group all push my cpu demand close to 100%, regardless of max cpu setting.

I have not had any game or app fail both tests.


can you test this yourself on v4.6 and confirm it happens? and can anyone else running v 4.6 also confirm? thanks in advance, and great work!


======================

P.S. can you add "sd cards swapped" to your list of mods that you've done? I wasn't aware you swapped the cards in vold.fstab until after I selected to unmount the sd twice and twice got the warning that I hadn't ejected my microSD first when I pulled it out...

Thanks Bro..

so far your kernel work fine for me on stok rom..

for V5 and V5 experimental is so smooth and fast but maybe better if you add other Gov like Lionheart (i like it.. ) like at UC kernel.. I hope too for MIUI kernel..

Antutu Benchmark score : 3112 - 3301

for V5 UV its still lagy

Thanks for your Great Job.. :twothumbs:

question

---

is the ROM deodexed already? Cant seem to find it on the OP. Thanks

yep, it is.

Originally Posted by supergaijin

yep, it is.

really? thank for the information.
How would you know if the ROM is deodexed?

Originally Posted by Jazone...

really? thank for the information.
How would you know if the ROM is deodexed?

Using a file explorer go to system/apps
If there are are only .apk files the rom is deodexed
If there are are .odex files as well the rom is not deodexed
Hence the term Deodexed (De-odex-ed) meaning no odex files

Awesome! Thank you so much for that info...

Originally Posted by devilhell007

Using a file explorer go to system/apps
If there are are only .apk files the rom is deodexed
If there are are .odex files as well the rom is not deodexed
Hence the term Deodexed (De-odex-ed) meaning no odex files

Sent from my GT-I9003 using XDA App

Hi vurrut. Thanks for your work.

Can you create a kernel (version 2) for CM7 that will boot with frequencies 300-1000Mhz (like the lates kernels of the Doomlord). Because when I flash your kernel v2 for CM7/MIUI it frizes on the logo (as I understand my CPU can't boot with 1300MHz) and I had to flash your kernel v1.

Thanks again.

Originally Posted by falex007

Hi vurrut. Thanks for your work.

Can you create a kernel (version 2) for CM7 that will boot with frequencies 300-1000Mhz (like the lates kernels of the Doomlord). Because when I flash your kernel v2 for CM7/MIUI it frizes on the logo (as I understand my CPU can't boot with 1300MHz) and I had to flash your kernel v1.

Thanks again.

Ok, I forgot to include.