Compiling CM9 (and maybe CM10) for Blade

[Guest sej7278]

I don't think I explained what I meant very well.

The thing I'm saying is that that CM9 uses a prebuilt libGLES_android.so from koush's propeitary repo. Wheras CFX uses a source built one from the repos.

The prebuilt comes from the QCOM zip files which had the drivers but we don't need it. If that can be got rid of then I hope/expect that CM9 will be as smooth as CFX.

ah that would explain this then:

Binary files cm9_syslib/libEGL.so and cfx_syslib/libEGL.so differ

Binary files cm9_syslib/libGLESv1_CM.so and cfx_syslib/libGLESv1_CM.so differ

Binary files cm9_syslib/libGLESv2_dbg.so and cfx_syslib/libGLESv2_dbg.so differ

Binary files cm9_syslib/libGLESv2.so and cfx_syslib/libGLESv2.so differ

Binary files cm9_syslib/egl/libGLES_android.so and cfx_syslib/egl/libGLES_android.so differ

so where is the source for these libs then?

[Guest jventura]

For the record, here are some more differences I could find of ColdFusion libs vs CM9 libs, only by looking at filesizes..

lib/modules/ - all files different

coldfusion has lib/invoke_mock_media_player.so and CM9 does not

coldfusion has different lib/libbcc.so

coldfusion has different lib/libcamera.so	  (More recent in latest CM9 (17/05) than CFx (15/05)

coldfusion has different lib/libOmxVidEnv.so	  (More recent in latest CM9 (17/05) than CFx (15/05)

coldfusion has different lib/liboverlay.so

coldfusion has different lib/libQcomUI.so

coldfusion has different lib/libsurfaceflinger.so

Edited May 18, 2012 by jventura

[Guest C3C0]

My experience.

I did the fresh build for Skate without any changes compared it to my previous build from 11/05.

Just did a repo sync - that's the only change I did.

UI is really noticably more choppy than it was in my previous build.

So my suspicion is that there must've been some commit to CM9 that did this.

EDIT:

I am pretty confident that this is the side-effect of one of these commits

from 13th of May.

https://github.com/C...mits/ics?page=2

Edited May 18, 2012 by C3C0

[Guest sej7278]

I did the fresh build for Skate without any changes compared it to my previous build from 11/05.

Just did a repo sync - that's the only change I did.

UI is really noticably more choppy than it was in my previous build.

So my suspicion is that there must've been some commit to CM9 that did this.

interesting that the skate is effected too when it didn't have the alpha/blur change (which backs up my findings that true/true makes no speed difference to what we have now).

maybe its the kernel changes here: http://review.cyanogenmod.com/#/c/14992/ ?

[Guest C3C0]

No... I am using my own kernel. And used the same sources and config compared to my earlier build.

I have a feeling that changes to surfaceflinger are the cause.

I'll maybe try to revert those commit one by one to see if it makes any difference...

Although this will probably take some time. Because one change in fw base requires

all framework jars to be rebuilt.

Edited May 18, 2012 by C3C0

[Guest shezar]

My experience.

I did the fresh build for Skate without any changes compared it to my previous build from 11/05.

Just did a repo sync - that's the only change I did.

UI is really noticably more choppy than it was in my previous build.

So my suspicion is that there must've been some commit to CM9 that did this.

EDIT:

I am pretty confident that this is the side-effect of one of these commits

from 13th of May.

https://github.com/C...mits/ics?page=2

Are you sure? I have a build that was made after these got merged and is quite smooth. (May 14 23:59:28 CEST) Or do we have different definitions of smoothness?

[Guest C3C0]

This is clearly just my personal judgement when I am comparing two of my builds where the only difference is that the repo was synced to the latest one.

The difference in smoothness is really visible. In settings menu, launcher screen transittions which worked really smooth are now lagging as hell.

Edited May 18, 2012 by C3C0

[Guest shezar]

Well since I was always suspicious about this one, I'll make a build where I only revert this patch: http://review.cyanogenmod.com/#/c/16056/ and include the blackscreen fix. Will report in 1-2 hours.

For the skate maybe the commit which enabled dithering is responsible? (https://github.com/CyanogenMod/android_frameworks_base/commit/a50c5ecfd2c049a4218922f5b3e8296b82f6a618)

[Guest C3C0]

Seems like it's not that one. I reverted, rebuilt but no difference... Must be something else.

[Guest shezar]

Well my theory got busted. It may be a bit better than with alpha on false, but it's definitely not smooth at all.

[Guest targetbsp]

Well my theory got busted. It may be a bit better than with alpha on false, but it's definitely not smooth at all.

Phew! Cause I really need that patch lol. The window animation lag on my phone is horrible without.

[Guest shezar]

Phew!

That made me laugh, lol (the sound of relief) :) Somehow my windows start quite normally on my 15th build but it started only when I reinstalled it over the later one. Maybe the install process left the framework intact so that it uses alpha=false on my phone? I haven't got a clue about it since I'm not sure how the CMW install process works.

Hmm I found this: http://review.cyanogenmod.com/#/c/16028/

"Causing a regression in 3D performance. It's very noticeable in ui transitions, for example when zooming in and out of the app drawer. The ui feels more laggy in general."

Edited May 18, 2012 by shezar

[Guest tilal6991]

That made me laugh, lol (the sound of relief) :) Somehow my windows start quite normally on my 15th build but it started only when I reinstalled it over the later one. Maybe the install process left the framework intact so that it uses alpha=false on my phone? I haven't got a clue about it since I'm not sure how the CMW install process works.

Hmm I found this: http://review.cyanog....com/#/c/16028/

"Causing a regression in 3D performance. It's very noticeable in ui transitions, for example when zooming in and out of the app drawer. The ui feels more laggy in general."

I think that commit could be the reason.

[Guest shmizan]

wait a minute. now what lag are we all talking about?

first it was just the app drawer that opens slowly, the clock that twitches and the menu transitions that happen quicker in CFX.

now are we talking about something beyond that? because I have a build from the 13th that everything works like it should and only the above slowdowns occur.

but since the 15th every build I made lags seriously. the launcher, the status bar pulled down. EVERYTHING.

is this what we're talking about now? or am I the only one? this caused me to completely wipe my cm9 build folder! recreating it took ages and still every build I make is laggy..

[Guest sej7278]

Phew! Cause I really need that patch lol. The window animation lag on my phone is horrible without.

eh, what lag is that now then?

with everything as stock (true/false alpha/blur from gerrit) i'm seeing slow animation in the notification power widgets but the clock is fixed (better anyway).

with true/true as it used to be in cm9, the clock "explodes" again, but the power widgets are still crazy slow, which could be due to this

but in neither build am i seeing slow window fades - like between screens in settings, when you press the back button you mean?

[Guest C3C0]

Yes. We are talking about this commit that's causing it, probably:

https://github.com/C...7a7d1f7f75b2eb2

I am just rebuilting with this commit being reverted. I will report in a while.

Ooops. Build is broken now after reverting

Edited May 18, 2012 by C3C0

[Guest shezar]

wait a minute. now what lag are we all talking about?

first it was just the app drawer that opens slowly, the clock that twitches and the menu transitions that happen quicker in CFX.

now are we talking about something beyond that? because I have a build from the 13th that everything works like it should and only the above slowdowns occur.

but since the 15th every build I made lags seriously. the launcher, the status bar pulled down. EVERYTHING.

is this what we're talking about now? or am I the only one? this caused me to completely wipe my cm9 build folder! recreating it took ages and still every build I make is laggy..

That is what we are talking about. Since something got merged, the UI runs at ~10 fps or so making it unpleasant to use. It seems to be a common problem not just ZTE-related.

[Guest jventura]

wait a minute. now what lag are we all talking about?

first it was just the app drawer that opens slowly, the clock that twitches and the menu transitions that happen quicker in CFX.

now are we talking about something beyond that? because I have a build from the 13th that everything works like it should and only the above slowdowns occur.

but since the 15th every build I made lags seriously. the launcher, the status bar pulled down. EVERYTHING.

is this what we're talking about now? or am I the only one? this caused me to completely wipe my cm9 build folder! recreating it took ages and still every build I make is laggy..

Well, I'm new at the CM9 party, so I don't know what happened before 14/May (my first compilation). But, CM9 is slower than CFX in many things, most noticeable on launcher transition, app drawer, menu transitions, top bar pulldown.. Like I've said, by only copying the /system/lib from CFX to my CM9 /system/lib, the slowdown disappeared big time.. It is almost as fast as CFX.. The only bit that is not as fast must be what the people around here is talking about.

So, repeating myself: I'm using koush's proprietary files as mentioned in the first post. Then, I've compile CM9. Then I've copied CFX /system/lib to my CM9 /system/lib and the UI is (almost almost almost) as fast as CFX. Maybe the other guys don't have that CM9/Koush sluggishness and are talking about other things!

I'm still trying to find which CFX proprietary libs do the speedup. The files on /system/lib/egl are not, for sure, because using diff, only libGLES_android.so is different, and changing only this file (in relation to Koush's proprietary files) does not speed up the UI..

[Guest C3C0]

Something's telling me it's not that commit that's causing it. ( https://github.com/CyanogenMod/android_frameworks_base/commit/417d89259effb373c0c3a411b7a7d1f7f75b2eb2 )

Simply because it was comitted 24 days ago... It's too far in the past and we definitelly had smooth UI in builds after that time.

[Guest shmizan]

my build from the 13th is good. the next one I made is from the 15th and the BIG lag is there.

I want to know first if we all talk about the same. it seems sej and targetbsp both don't get what shezar, jventura and I get, which is COMPLETE lag in launcher, status bar, windows transition, everything.

it's the changes merged between 13th and 15th that cause this

[Guest C3C0]

Yes. I am talking about the same issues. Completely laggy UI. Everything.

[Guest WildeRNS]

4. Apply patch from gerrit to fix blackscreen issue

thanks for nice guaide, but have a quastion, in what folder i must apply patch?

[Guest jventura]

...don't get what shezar, jventura and I get, which is COMPLETE lag in launcher, status bar, windows transition, everything.

it's the changes merged between 13th and 15th that cause this

So you are saying that before 13th of May, CM9 was as fast/smooth as ColdfusionX?

[Guest shezar]

my build from the 13th is good. the next one I made is from the 15th and the BIG lag is there.

I want to know first if we all talk about the same. it seems sej and targetbsp both don't get what shezar, jventura and I get, which is COMPLETE lag in launcher, status bar, windows transition, everything.

it's the changes merged between 13th and 15th that cause this

I started my "good-build" on the 14th at about 6PM GMT+1 So that narrows it a bit down.

[Guest shezar]

thanks for nice guaide, but have a quastion, in what folder i must apply patch?

kernel/zte/zte-kernel-msm7x27