Originally Posted by MartyHulskemper

WelL, all this refreshing meant a lot of wear of that paint on the F5 key. Now I just have to guess which key to hit. Luckily I remembered it's located somewhere between F4 and F6.

(Slightly) off-topic: @sbdags: I do not seem to have my keyboard issue on v2.7 (yes, I know it's a prehistoric version). I'm going to nandroid this setup and try 3.3, but I am afraid of it popping up again. I even have many more apps installed (with their concurrent data) than on my testing setup of 3.2.2 that did have the error. I admit I'm stumped, but it might be that my dock doesn't like the more recent versions of CROMI --- I would not give a **** if I were you since I seem to be the only one with the issue, but this is just a little FYI.

I'm really anticipating v3.3, for several reasons, as you may notice.
Now I'm on v2.7, it still strikes me how fast that version really is.

what keyboard issue are you talking about?
i'm waiting for my keyboard dock to come, so I'm a bit worried about it...

Originally Posted by william tanaya

what keyboard issue are you talking about?
i'm waiting for my keyboard dock to come, so I'm a bit worried about it...

Marty has a peculiar issue with one row of keys stopping working. Currently we don't know why and it doesn't seem to affect anyone else. But interesting that CROMI 2.7 appears to have fixed it. That was an old 10.4.4.20 version and was very quick!

Originally Posted by sbdags

Marty has a peculiar issue with one row of keys stopping working. Currently we don't know why and it doesn't seem to affect anyone else. But interesting that CROMI 2.7 appears to have fixed it. That was an old 10.4.4.20 version and was very quick!

oh. okay. so the problem might not from the rom...

I'm not sure if it's CROMI-related, but I am the only one suffering from it, or rather, my device is having the issue and I'm suffering as a result.

Funny thing is that v2.7 ran really nicely,and I haven't had a single lockup in about24 hours. That sounds pretty good. After pulling a Nandroid I installed v3.3 over v2.7, and within the hour... BLAM! Keyboard gone. The top row of shortcuts keeps functional except for the back key, and the rest of the keys stops working. I'm now debating what to do in the morning: rolling back to the Nandroid and stay on there for a few days, or format the hell out of everything and start over (after doing FTP backups of more or less mission-critical data, obviously).

I'm going to backup anyway, now I think of it, since my TF700 might be dying (the dock, at least).

TL;DR: CROMI is fine with everybody else. I'm just the sad little green frog in the rain .(A Kermit the Frog reference should carry weight in pretty much any given situation. )

widgets

---

Is anyone having problems loading asus widgets after flashing 3.3 odex? Weather widget?

Re: [ROM][13 Feb]★★CleanROM Inheritance 3.3 | JB 10.4.4.25 | ODEX/DEODEX | New Kernel

---

Originally Posted by Gene588

Is anyone having problems loading asus widgets after flashing 3.3 odex? Weather widget?

Weather widget is faulty since Asus JB update.

Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Sorry my stupid question !!

Which version is better for performance ODEX or DEODEX ?

thanks

Did I screw up?

---

I got a little confused and flashed the TF700T 10.4.4.25 bootloader to my TF300T, will this screw anything up?

---------

Re: [ROM][13 Feb]★★CleanROM Inheritance 3.3 | JB 10.4.4.25 | ODEX/DEODEX | New Kernel

---

Originally Posted by focusbra

Sorry my stupid question !!

Which version is better for performance ODEX or DEODEX ?

thanks

Been covered over n over again... Speed = Deodex / Smoothness = Odex

Sent from my ASUS Transformer Pad TF700T using Tapatalk HD