[Eee Pad Transformer Android Development] timduru:
Sure :)

For the main lag that we had here, it's there: https://review.teameos.org/1464

Don't use patchSet3 though, because it reverts part of my fix, and brings back about 7% cpu usage in a partial crazy loop again.

I'm not sure if you'd have that particular fixed issue on CM10 though as I think it was EOS specific code,

unless it was imported from CM10 or vice-versa.

We still have some fps drop in the default launcher when combined with the navbars though.

I think it might be a tad better in the latest preview I posted, but there's still some.

It's taking a long time to find out the exact culprit for that one unfortunately., and seems indeed to be general to all android builds I'd say.

I'll keep looking for that one, if/when I do I think all JB rom flavors might indeed benefit from it.

Sure I can have a look,

I'm kinda very busy with real EOS matters though as you may have noticed.

So if it takes me too long to get it to work, I'll have to postpone that.

There's holidays coming too, so not much time left before that.

But send me a PM with the necessary infos so that I can compile it and get it to boot:

- point me to where to get the latest 3.1 kernel sources + .config used to build it

- if it needs a special ramdisk

- explain exactly what is the issue you're having with the wm8903 code and what tests did you do and such.

It might be better to keep the kernel talk either in your own thread or by PM too I think.

This thread is already busy and complicated enough with all the EOS 4.2.1 related talk ;)

While it'll be definitely nice to have a working 3.1 kernel, it has been in work for months,

so I really don't understand what is the big hurry to switch completely your priorities just a few days after committing to be one of the supposedly official TF101 maintainer for EOS though...

As for the kernel, the current EOS kernel is stable and everything works fine. We definitely need to keep a stable and working kernel as the default.

As such I think it'd have been better 'for EOS' to work on the rom first.

As it has been said multiple times already, the order of priority in the EOS4 rom is:

- stability

- fixing

- bringing it up the same functionality wise compared to EOS3

That has already required a lot of work in the past few weeks to get to that point,

and in the latest B88 preview most of the major bugs are now fixed or have a workaround, and yes, it's now bloody fast :)

But toying around and adding other goodies, should comes later on imho.

In order to maintain stability, the 3.1 kernel should be distributed as a separate zip, at least in the first time.

Until it has been tested enough by other users.

On the EOS side: there are still a few things to fix *right now*

So as said already the last time you posted here about the kernel, it's fine if you prefer to concentrate on the kernel.

It just takes me more time to fix alone, but it's getting there.

If however you decide that you're bored between your night and days spent on the kernel,

feel free to pick something from the list of things that are left

and let me know first, so that we don't work on the same stuff:

4.2.1 Known issues & Workarounds

I'm working on 2 main things in the list atm:

the launcher lag if used with navbars & the autorotation eating cpu.

The launcher lag should be improved in the latest preview, but there's still something fundamentally wrong somewhere that I've not found yet.

The autorotation seems to be a combination of 2-3 bugs which makes it not easy.

It'll need more testing and even if I have a combined 2-3 fixes, 1 is impacting a bit the time it takes to detect auto-rotation.

So I need to find the best compromise between cpu eating and auto-rotation response, which will take more long testing ;)

Also had a look at the soft keyboard crash on autosuggestion, but didn't find a fix yet.

So deactivating the autosuggestions will have to do for the moment ;)

Hehe thanks ;)

Yeah I'm actually pleasantly surprised of how smooth and responsive it is in the latest B88 preview :)

when I started working on it, the goal was to make it at least as fast as the previous JB 4.1 while getting the 4.2.1 extra features.

But it's beyond that speed now I think, and much more responsive, which is really good,

as I think there can still be a few improvements made even ;)

What you call "navbar bug" is the fps drop in the default launcher if used in combination with the navbar, or something else ?

If so yeah, I've been working on that, it's not easy to determine the exact part of the code generating that yet.

I'd suggest just to use another launcher in the meantime.

Go Launcher EX is very fast and smooth here, Desktop scrolling is perfect even with the navbars on for example.

I think I prefer the notification bar on top too.

Makes it more natural to swipe down from there and such.

Better if you have a dock too I think, the dock always gets in the way with notifications at the bottom

With the option for the smaller navbar I definitely prefer it that way too,

makes it more consistent with the size of the top bar, and that way it's not really eating much more screen space than before :)