Jump to content

Recommended Posts

Guest peetu20
Posted

Will the project butter never work fully on our blade.

And what the vsync which is missing, does?

So would jellybean be faster than now?

Guest tilal6991
Posted

No vsync is unlikely to work on the Blade unless someone manages to port a 3.0 kernel. Any takers?

Guest Sulthekk
Posted (edited)

Squadzone will even port 5.8.6 for you if you ask him. :D

Even before release.

Edited by Sulthekk
Guest reedo_17
Posted

Squadzone will even port 5.8.6 for you if you ask him. :D

Even before release.

why dont you ask him?

Guest Snap.IT
Posted

No vsync is unlikely to work on the Blade unless someone manages to port a 3.0 kernel. Any takers?

I can port it with the available drivers but i don't see the point, there is nothing in it that would fix anything since we still don't have the proper drivers to work with.

Vsync will not matter ONE BIT on this hardware though, it would slow everything down and make it more choppy if anything, as it is vsync actually does work because it doesn't chop at vsync levels but i'll tell you what, you get the interface up to min 60fps and i'll vsync it for you.

Guest Snap.IT
Posted

well, so whats the problem? ^^

The problem is that he doesn't port anything, he uses old versions and changes the version numbers, in his latest CyanMobileX he says he's using 2.3.8 sources which don't exist and his kernel number is 3.33.33.33 but in reality he is using CM7.2 which is based on 2.3.7 with a 2.6.35 kernel.

He's just making s*** up and hoping that people will fall for it, there is a reason why he left XDA and then MadTEAM and now he's annoying other forums with his crap.

Guest Ganster
Posted

I can port it with the available drivers but i don't see the point, there is nothing in it that would fix anything since we still don't have the proper drivers to work with.

Vsync will not matter ONE BIT on this hardware though, it would slow everything down and make it more choppy if anything, as it is vsync actually does work because it doesn't chop at vsync levels but i'll tell you what, you get the interface up to min 60fps and i'll vsync it for you.

Vsynk not only slowdown screen updates, it synchronize its. Without it we can't use right hardware composer, and can't take really fast interface.

Guest Loren82
Posted

The only thing that seems to be the key is Burstlam in your rom, Vsync seems to be active, and the speed is amazing. But I'm not sure. :wacko:

Guest jventura
Posted

I can port it with the available drivers but i don't see the point, there is nothing in it that would fix anything since we still don't have the proper drivers to work with.

Vsync will not matter ONE BIT on this hardware though, it would slow everything down and make it more choppy if anything, as it is vsync actually does work because it doesn't chop at vsync levels but i'll tell you what, you get the interface up to min 60fps and i'll vsync it for you.

Snap.it,

I've surfed a bit in the zte-kernel although haven't ever touched anything in the kernel, except adding printfs once or twice in the g-sensor driver. You seem to know more about kernels! Could you just explain fast or point to some resource for how could someone port a 3.x kernel for the zte blade? Would we have to get a linux generic kernel and start from there? Or a 3.x kernel from a nexus 4 or something like that and start from there? What would the main problems, drivers?

If the thing is doable, i would probably take to chance to dive in so I could learn a little bit more about the kernel, since I've never messed with it.. It would be a pet project, lets put it that way.. :)

Thanks,

João Ventura

Posted

if its related to MDP version number as konstat said in his thread..we have 2 devices htc desire and nexus one with same gpu running the vsync..its software vsync though..

Guest habbo45
Posted

if its related to MDP version number as konstat said in his thread..we have 2 devices htc desire and nexus one with same gpu running the vsync..its software vsync though..

same CPU. not same processor.

Guest Sulthekk
Posted

same CPU. not same processor.

Whoah now this is a paradoxon! :D

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.