I'm trying 1MB kernel. Doesn't look bad. I'll try 500k this afternoon.

For the petition, I'm obviously going to sign these, too.

Sent from my Legend using XDA

Here's anther logcat of a Google navigation related crash. To be honest, this reminds me of the CM7.1 crashes. The GPS stuff was fixed quite recently in CM7.2 nightlies, perhaps the changes were not ported over to CM9.

This is CM9.0.0-beta2, with the default GPU mem size kernel from a few posts back flashed as well.

Trebuchet (the home screen and app drawer) sometimes drops out of memory still, forcing a recalculation of home screen widgets and the contents of the app drawer. I don't know if you can do anything about this, the only option I could see is locking it into memory, but that feature'll have to come from CM devs (it is present in CM7.x)

Really GPS works fine, so it is not necessary more work around of this. I merged the 2 line patch about agps and it locks relatively fast. I think it is not necessary more post about this. As told one and another time, check the gps properties and conditions: radio, gps.conf, openfield, number of sats, signal sats, etc.

Trebuchet is the official CM9 and it is thinked but an 2011 device, so it is assumed you are doing a responsible memory management supervision.


Anyway, I have not got these issues.

Originally Posted by rubenvb

Here's anther logcat of a Google navigation related crash. To be honest, this reminds me of the CM7.1 crashes. The GPS stuff was fixed quite recently in CM7.2 nightlies, perhaps the changes were not ported over to CM9.

This is CM9.0.0-beta2, with the default GPU mem size kernel from a few posts back flashed as well.

Trebuchet (the home screen and app drawer) sometimes drops out of memory still, forcing a recalculation of home screen widgets and the contents of the app drawer. I don't know if you can do anything about this, the only option I could see is locking it into memory, but that feature'll have to come from CM devs (it is present in CM7.x)

Originally Posted by zeubea

Really GPS works fine, so it is not necessary more work around of this. I merged the 2 line patch about agps and it locks relatively fast. I think it is not necessary more post about this. As told one and another time, check the gps properties and conditions: radio, gps.conf, openfield, number of sats, signal sats, etc.

Trebuchet is the official CM9 and it is thinked but an 2011 device, so it is assumed you are doing a responsible memory management supervision.


Anyway, I have not got these issues.

Just for info, at boot time my home screen always has to refresh and takes about 1min or more most times but once its up its fine, only rarely has to refresh launcher, (almost 180 apps on board) however I'm back on adw launcher so I can use those themes.

sent from my legend using zeubeas cm9 beta2

Originally Posted by zeubea

Really GPS works fine, so it is not necessary more work around of this. I merged the 2 line patch about agps and it locks relatively fast. I think it is not necessary more post about this. As told one and another time, check the gps properties and conditions: radio, gps.conf, openfield, number of sats, signal sats, etc.

GPS does work rather fine. It's the phone reboot as shown in the attached logcat I'm more worried about.

Originally Posted by zeubea

Trebuchet is the official CM9 and it is thinked but an 2011 device, so it is assumed you are doing a responsible memory management supervision.

All I did was open browser, or Angry birds or whatever. All I have running in the background is Friendcaster, Gmail&associates and Email.

Originally Posted by ranger4740

Just for info, at boot time my home screen always has to refresh and takes about 1min or more most times but once its up its fine, only rarely has to refresh launcher, (almost 180 apps on board) however I'm back on adw launcher so I can use those themes.

It's this refresh thing I'm talking about indeed.

It does seem the checkmark "do not save activities - delete activities as soon as user quits" (loose translation) helps though. I'll keep a closer eye on this.

Thanks ranger4340; if any interested, it would be useful to determinate the impact of GPU size in performance, measured with antutu, quadrant or so.

Originally Posted by ranger4740

I've just been trying the 4 kernels my report back is this,
Default kernel (300) unstable, after reboot, toast for superuser notifications never stop showing for apps that load at boot.
Kernel (500) no issues, nice n stable, in fact, maybe slightly better than (600)
Kernel (600) no issue.
Kernel (1M) similar issues as default (300)
So going to try the 500 kernel for a while...

sent from my legend using zeubeas cm9 beta2

Originally Posted by zeubea

Thanks ranger4340; if any interested, it would be useful to determinate the impact of GPU size in performance, measured with antutu, quadrant or so.

Yep OK, I'll do an antutu with the 500 kernel and post back here, stay tuned :thumbup:

sent from my legend using zeubeas cm9 beta2

Damn, I just flashed 500k kernel.

Anyway, 1M is quite unstable. It was starting to die twice but at the last moment it revived and returned normal. Still, I had 3 reboots today (+2 revived).

Hi guys, here are my results from extensive benchmark testing with all the kernels.

I used Antutu benchmark using only the 2D and 3D graphics test

Setup, I tested each kernel with 2 cpu frequency's, 806Mhz and 787Mhz, both using performance Governor. I took the average of 5 tests per kernel and here are my results.

Default kernel (300Kb)
frequency 787Mhz score = 920
frequency 806Mhz score = 927

500kb kernel
frequency 787Mhz score = 923
frequency 806Mhz score = 933

600Kb kernel
frequency 787Mhz score = 921
frequency 806Mhz score = 914 (yes this is correct)

1M kernel
frequency 787Mhz score = 914
frequency 806Mhz score = 925

So in conclusion the best results were
500k kernel running @ 806 Mhz with a score of 933.

Next results are the average of the 2 scores from each kernel
300 = 923
500 = 928
600 = 917
1000= 919

Ironicly the worst results were the 600K kernel

Edit:- I would also like to test a kernel with 400kb and 800kb GPU memory, having never messed with kernel code I'm not sure if I can change that localy myself or it needs to be compiled from source which I don't currently have the tools to do unless its plain text of course.

Edit again:- Holey Crap I just did a full antut benchmark using 500K kernel @ 806Mhz antut score 1936!!!!!!!

Thanks

@ranger

did you do anything particular to be able to set cpu clock to 806,or it's just the stock oc menu...because in my case setting it in performance menu freezes the device and reboots it