698 replies to this topic

[elrond_bs]

Great, I was just about to ask if someone will continue KonstaT's work. Thank you, daemond!

Is there a specific reason you call your build experimental (will there be a stable?) or you just wait for more feedback?

@peetu20: you don't need to format system, because there is a "format system" command in the .zip and it is formatted automatically when you install. But to be on the safe side - fromat it.

About the 3.x kernel, AFAIK there is an experimental version, but it breaks more things, than it fixes. And it's not worthed to replace a hacked kernel with our stable kernel, if I understand correctly.

[Simono]

Great work. I was on CM10 some time ago. Now I'm on CM7 but WiFi thether don't work fir me, so I will try this build on weekend.

[ziofaggio]

andr0idbeliev3r, on 21 January 2013 - 12:49 AM, said:

I would suggest to make a post of how to compile CM10 since KonstaT's thread will be far away into the "lost forums"

i would suggest also to make a post of how to install CM10 with s2e and a FAQ so people don't do the same questions every 2-3 page,

[96frozen]

Daemond, please post this on xda. If you don't can I have permission to post it there with the given credits to you?

Edited by 96frozen, 22 January 2013 - 08:00 PM.

[daemond]

DellXCD35, on 21 January 2013 - 07:33 PM, said:

1. The camera takes ages to boot up and gives a message Gallery loading force close.
2. The gallery itself takes ages to show up folders and pictures in it.

I can't reproduce this here either.

KRoman47, on 22 January 2013 - 06:35 AM, said:

@daemond: Hi, I much appreciate your work! But I'm missing center clock which I'm using for about half year. Can you include it in next builds?

Center clock? The setting for the lock screen clock is part of CM10, and so it's included here as well. Or do you mean something different?

peetu20, on 22 January 2013 - 10:39 AM, said:

Why i need to format system? In konstas original rom i just needed to flash zip..

You don't need to, as someone pointed out it's a "just to be sure" thing.

96frozen, on 22 January 2013 - 07:59 PM, said:

Daemond, please post this on xda. If you don't can I have permission to post it there with the given credits to you?

I'm not in the right mood for XDA. Sure, post it there. Please link back to this thread and the github repositories.

[96frozen]

daemond, on 22 January 2013 - 08:15 PM, said:

I can't reproduce this here either.



Center clock? The setting for the lock screen clock is part of CM10, and so it's included here as well. Or do you mean something different?



You don't need to, as someone pointed out it's a "just to be sure" thing.



I'm not in the right mood for XDA. Sure, post it there. Please link back to this thread and the github repositories.

yeah no problem, the work's yours and KonstaT's why would I take credit for both of you.

[KRoman47]

@daemond: I mean clock in the middle of the status bar. This should be it: 1, 2 (it's from KonstaKANG CM10 changelog).

[archish]

Nav bar resize seems missing as well.

[daemond]

I have successfully made vsync events (i.e. Project Butter) work. This was never really implemented correctly for MDP 3.00 in the MSM7x27, but the hardware can do it, and after a bit of reading code and hacking around, it seems to work just fine! It feels a little bit smoother with vsync event timing enabled, especially touch latency appears to be reduced. But I have no good way to measure this.

The most important bits can be found in my kernel tree, but the device tree requires some additional updates, too.

Please test this, if you can.

[C3C0]

Impressive!
I suppose that the "fake vsync" patch needs to be reverted, too.

[96frozen]

daemond, on 24 January 2013 - 03:00 AM, said:

I have successfully made vsync events (i.e. Project Butter) work. This was never really implemented correctly for MDP 3.00 in the MSM7x27, but the hardware can do it, and after a bit of reading code and hacking around, it seems to work just fine! It feels a little bit smoother with vsync event timing enabled, especially touch latency appears to be reduced. But I have no good way to measure this.

The most important bits can be found in my kernel tree, but the device tree requires some additional updates, too.

Please test this, if you can.

You just keep on surprising us don't you?

[96frozen]

After being in this community I feel like a spoiled kid lol

[99x]

Is any one else able to compile this ROM? I'm tempted to try compiling myself (have only ever compiled a raspi from source) but I'm a little under qualified lol

[anantk]

96frozen, on 24 January 2013 - 08:10 AM, said:

After being in this community I feel like a spoiled kid lol

You should add Daemond's name in your signature along with all the Blade ROM stalwarts you have named

Edited by anantk, 24 January 2013 - 10:50 AM.

[DellXCD35]

Hey Daemond The gallery force closing and Camera not booting up problem got solved on its own. I have no conclusion how it happened but i am more than happy. Battery life is also respectable and GPS signal is also good.
Million thanks to you.

The rom just takes a bit toll on the RAM, depletes the poor 512mb ram quickly on many instances. For example after a while typing in Whatts App messenger gets laggy.

[KonstaT]

daemond, on 24 January 2013 - 03:00 AM, said:

I have successfully made vsync events (i.e. Project Butter) work. This was never really implemented correctly for MDP 3.00 in the MSM7x27, but the hardware can do it, and after a bit of reading code and hacking around, it seems to work just fine! It feels a little bit smoother with vsync event timing enabled, especially touch latency appears to be reduced. But I have no good way to measure this.

The most important bits can be found in my kernel tree, but the device tree requires some additional updates, too.

Please test this, if you can.

Nice job, I'll test this when I have time. I knew something like this was possible, but I never thought it was worth the trouble. We've already previously had fake vsync event on two different levels and IMO it really hasn't made much of a difference. This now takes the final step to the kernel side of things but as far I can tell it shouldn't again make much difference from how it's currently implemented. But hey, now we can at least say that we have full butter.

I'm just happy if we can get this Project Butter case now finally closed. Things get easily blown to mythical proportions when most of the people have no clue what it is or what it is supposed to do. All they think it's something super-amazing that makes things super-fast (when it fact it's just to give consistency). Google certainly didn't fail in marketing that thing...

C3C0, on 24 January 2013 - 05:04 AM, said:

Impressive!
I suppose that the "fake vsync" patch needs to be reverted, too.

You can, but you don't have to. It's all been ifdef'ed, removing the TARGET_NO_HW_VSYNC flag from BoardConfig is enough.

[Squizzy911]

can anybody make a benchmark please? want to see how much faster it is like gingerbread

any camera glitches? maybe i want to upgrade my girlfriend's phone with this rom useful as daily driver?

[De@n]

archish, on 23 January 2013 - 05:04 AM, said:

Nav bar resize seems missing as well.

daemon, can you add navbar height/width setting?

[twat4u]

Squizzy911, on 25 January 2013 - 03:52 PM, said:

can anybody make a benchmark please? want to see how much faster it is like gingerbread

any camera glitches? maybe i want to upgrade my girlfriend's phone with this rom useful as daily driver?

Just test. Antutu give 2656 points.   
Good to use your girlfriend daily, go ahead.

[99x]

twat4u, on 25 January 2013 - 04:36 PM, said:

Just test. Antutu give 2656 points.   
Good to use your girlfriend daily, go ahead.

Nice, better than me, what performance settings you using?

Attached Files

•  uploadfromtaptalk1359134259680.jpg   43.46K   41 downloads