[Galaxy Ace II Android Development] ace2nutzer:
First of all: Thx u guys for testing !! - so if i understand it right, 02/11 is 100% but 08/11 not 100% ok because of freezes ??

But to be honest i don't think that it's buggy... because i don't have any problems at all with the latest version ... it's also for me the best kernel ever. It works fast and smooth like overclocked Phone. btw: i'm using the Phone all the time with Stock Freq's (kernel default) ... it's almost not needed to overclock .... also because with stock Freq the Battery lifetime is much better...

To be honest it's even underclocked a bit ... default GPU Clock on Stock JB is

static 400Mhz

... but on this Kernel here it runs with the Gov.

Mali AutoBoost @ 300 - 400Mhz.

But still fast and smoother than Stock JB :D

I'll release next Kernel with some more small Binary Code Optimizations ... then this kernel is fully optimized... but i don't say that u'll not see updates anymore .... of course if there is something to update.. like GCC Version or so.. then i'll update the Toolchain too and build the kernel with some new optimizations flags included in that new GCC Version.

For Now, the work is to make also great CM11 like this Kernel :D

Then For sure nobody want to sell his lovely Ace2 :o

I'm saying sorry again and again about that long waiting about CM11 ... but it's not really simply downloading sources and build it ----> no changes but just updated CM Sources. As i will update all Build tools for the ROM and flags for the ROM.

If everything goes well, u can expect approx. 50%+ more speed just on ROM Side ....

Also i had to upgrade my very weak Laptop ...

What i already did:

CPU: Intel Celeron M540 (540Mhz FSB) 1,87Ghz single core 1MB L2 Cache @ Intel Core 2 Duo Dual-core T7300 2x 2Ghz 800Mhz FSB 2x 4MB L2 Cache

RAM: 1GB 540Mhz FSB @ 4GB 800Mhz FSB .. (but runs @ 667Mhz because of faulty BIOS :D )

HDD: 80GB (old internal) + @ 1 TB USB 3.0 HDD (but runs @ USB 2.0 ... and still very fast)

Downloaded CM Sources...

Now optimizing ...

Next Step: compiling + testing on my Phone.

btw: u'll probably not see much ROM's or Builds from me... but only if there is important reason like Stagefright ... simply because, i've only 90kb/s upload speed and also because of low free time.

Hmm any reason why i should disable or even remove full zram Support from kernel ?? What expect u from that ??

It'll work with an simply line on 99_user script.... same result. or just because u guys are too lazy to make an script ?

I suggest to rename the script later in "98_zram" so that it can't overwrite with an empty script by kernel Update.

script to disable zRam as follow: (use predefined 99_user script)

swapoff /dev/block/zram0

save and set proper permissions like this:

root - shell (0:2000)

-rwxr-xr-x (755)

and to make some tests about to "see" the difference with zRam and without it:

type in terminal:

su

enter (press enter :D)

cd /dev/block
swapoff zram0

wait a bit... it can take some seconds..... until u see normal cmd line again... and let the terminal open in background

then test the Phone... (test also high ram usage...)

now turn it on again:

swapon zram0

and test again ... :)

okay... thx for great testing ! Can u pls install again latest Build and then post if it's almost same ? I hope with no freezes ...

btw: if u don't use zRam or swap at all, then u don't need to configure VM at all ..... only minfree Values are active then .....

If u want u can send me over pm your vm/minfree values... one set without swap, and one set with swap enabled ... i'll test them (i promise)

if they are really better than mine, i'll make them for kernel defaults, also i'll write your Nickname in Changelog .. so that your username will walk a bit around the world .. of course only if u're agree with that terms. ;) So i hope later that beef with "ridiculous" minfree Values are Gone :cool:

in this case it's virtual mem... but vm is also virt. machine.. u're right ... a bit confusing thing :)

thanks ! at least one user that understand this correctly !

Same here.... with normal usage zRam is only used from 60 to 120MB ... but sometimes, very rare it's even 150 - 200MB....

btw: that configured zRam Size is just a LIMIT .. so it doesn't mean that it should try to fill the full RAM with zRam ... nope .... :)

I ask once again:

is latest build really different as 02/11 ??? I mean freezes ....

I'm a bit confused now if it's buggy or not the latest kernel ....

but as i said, for me it works with no issues :)