How about jack Daniels for jack ? Will that make him happy ?All work and no play makes Jack a dull boy.
Have some fun, kernel can wait a couple of days.
Have a good time geecko
Sent from my GT-N7000 using xda premium
How about jack Daniels for jack ? Will that make him happy ?All work and no play makes Jack a dull boy.
Have some fun, kernel can wait a couple of days.
+1 :good: :good:We are waiting also for a 4.3.1 updated kernal![]()
Rest assured I won't give up now :highfive:Want to hear something fun? hwcomposer update doesn't even work on the i9300cc @xplodwild
There was a compilation error that disabled hwcomposer, so the test build was running without it.
When trying to fix on my n7000 I didn't understood how it even worked on the i9300, but it turns out it never did
I'm working on updating the s3cfb driver again, so it matches insignal's hwcomposer requirements.
It's funny how people reported better performance. It may be true as the current source is horribly broken, but placebo is strong here.
Some (bad) news
Rest assured I won't give up now :highfive:
So that being said, if you get through it successfully the real improvement will be noticeable, won't it?
Thanks for your efforts!:good::laugh:
You got it right. The new mail driver only present in r3p2. The performance in r3p2 are better than s3cfb. But the s3cfb seems more battery friendly.I've read the posts announcing r3p2 and s3cfb but i can't quite understand which of these offers better performance. Since, if i understand correctly, s3cfb doesnt include new mali gpu drivers present in r3p2.
if you want s3cfb+r3p2 use slimsaber romI've read the posts announcing r3p2 and s3cfb but i can't quite understand which of these offers better performance. Since, if i understand correctly, s3cfb doesnt include new mali gpu drivers present in r3p2.
Reflash the kernel will do the trick. Cheersif i install s3cfb and i want to revert back to r4 do i need to reflash the rom again or just the kernel?
New hwcomposer depends on Insignal's s3cfb framebuffer driver. This driver depends on new ION driver from Android 3.4 kernel, because the Insignal kernel is 3.4. I'm trying to backport it right now, it's hard, and it will take time.Hi Geekodev, just wanted to ask how you're getting on. Or will hwcomposer remain a dream for n7000?
Near future? How about never and a couple of days after that? :laugh:which will happen in a not near future.
That's pretty much what I thinkNear future? How about never and a couple of days after that? :laugh:
Take your time, no hurry here, been w/o hwcomposer for a year now...New hwcomposer depends on Insignal's s3cfb framebuffer driver. This driver depends on new ION driver from Android 3.4 kernel, because the Insignal kernel is 3.4. I'm trying to backport it right now, it's hard, and it will take time.
On another news, ARM released Mali r4p0 kernel drivers source, but it is 100% useless until we have userspace blobs from samsung, which will happen in a not near future.
We could. I talked with @XpLoDWilD and Espenfjo about this. They said it is doable, even though it would take a lot of efforts. However, I am pretty confident that this ION driver can be backported, so it won't be needed.Take your time, no hurry here, been w/o hwcomposer for a year now...
Not a real noob, been using Linux since kernel 1.0.16..., anyway a noob question: what exactly
nails us to kernel Version 3.0.64? No option to forward port the n7000 bits to 3.4?