[Asus  Eee Pad Transformer Prime] CekMTL:
DON'T DESPAIR!

Just a quick note, to let you know that there's hope, at least with all the hacks and mods that I have done and am running in my TF201 based on AndroWook 1.3x

I have also modded my kernel, based from _motley's and this thing flies, but I'm playing with fire (have backup of backup of backup :p)... so I'm my own sole guinea pig, and any moment my TF could explode in my face! :p

I can install an app and at the same time work with my tf, browse and everything, without ANY hiccup or lag.

I can have 4-6 torrents downloading in the background, to an external USB (dock) HD, at a rate of about 2 Mbytes/s, while browsing and working like a PC, without any lag... yes IT IS POSSIBLE!

I can have more than 50+ processes in memory without being killed by (STUPID!tm) OOM... and also have 6+ web pages (Desktop mode) open in Browser+ and flick between them (gesture), and they are instant, and it works on 1.8Ghz stable at 1300vcc.

BUT! ... that's no excuse for the HORRIBLE HORRIBLE HOOOOOOOOORRIBLE backend mmc speed (internal).

From code and debug KERNEL (printk() is my friend now), I know that I have Hynix 29.8Gb memory (if it's to be trusted), but from code, I also see that it's not optimized AT ALL... there are some strange thing going on, and a lot of waisted time... so do have hopes that it will get addressed, and then... WOW!

Am currently looking at all the code, and have integrated a couple of changes from nVidia, and now it's time to compile/copy/flash/boot/test, over and over again.

Also, from my modded sources I now know that there are some apps that ADORE to issue like 20 fsync() in burst batch, every time you do something (like gtalk), and that is VERY BAD for the SLOOOOOOW backend, so you notice lag and stutter for a moment, every time you do something (doesn't matter if you're clocked @ 4 GHZ, with 200 cores... everything halts till the MMC backend finishes that write).

If you are doing many things (even if you don't know, the OS is doing many things in the background), there's contention for the R/W access... OUCH!

OH WOW... sorry for my crazy ramblings... I start to write and there are so many things...

Don't despair, there are many very talented ppl working on a solution to make this TF fly (should have done it in the first time ASUS & nVIDIA!).

Mine is working as a missile fast, but it's not ready for prime time nor it's user friendly/stable.

EDIT1: Testing with AndroBench 0.1 - 1.8 Ghz interactive (normal background processes running).

Use Buffer : no.

SEQ RD : 20.02 MB/s (ufff!)

SEQ WR : 4.03 MB/s (ouch!)

RND RD : 1505.34 IOPS (4K)

RND WR : 55.84 IOPS (4K) (yihhhaaaaa.... now that is "speeeed" xD)

Insert : 564.97 TPS

Update : 482.31 TPS

Delete : 751.87 TPS.

EDIT2: Debuging & understanding flow of sdhci-tegra.c

I'm BAFFLED at HOW MANY TIMES IN A SECOND THIS SET CARD CLOCK FUNCTION GETS CALLED....

From 85.440374 to 85.648697 it gets called 44 times in less than 210 ms == called once every 23ms ... WHAAAAT???!?!?!

And it goes on and on and on... !?¿!?"!? :confused:

... so... every interaction with the mmc backend, read write (pray!), this function gets called at least 20 times in a short span... WHY?????

So everytime you set the mmc bus speed (this function does that for TEGRA3), there has to be a pause to stop the clock, wait, change the clock, wait, test, write one bit, see if it's ok and then continue with your life... there's also a 20ms wait timer...hummm...

Hummm more interesting debug stuff in my drill down

Enviado desde mi Transformer Prime TF201 usando Tapatalk 2