you said here that you fail to install any .cab
Quote:
Originally Posted by rainabba
....
Any idea why any given cab (in this case, TouchPal 3.5) would fail to install (not cook in, but .cab install) ?
|
and then here, seem that you can install it now , what happens ?
Quote:
Originally Posted by rainabba
Even fully loaded with all my crap, I now have the fastest ROM I've ever experienced on the Vogue. Frankly, this phone feels like it got a CPU/RAM upgrade. The difference is that noticable.
For the last couple builds, i haven't been able to use TouchResponse. If I enabled it (after the Vogue registry fix of course), the phone would become virtually useless. It almost even seemed that a hard reset wasn't a reliable fix (yes, I know how that sounds). Same holds true for this SYS. I imagine it has to do with the fact that MS has integrated "TouchFlo" behavior and TouchResponse was essentially a hack so it's now broken. Still, AMAZING SYS!
EDIT: I previously had said "I cooked in TouchPal 3.5 and it's working flawlessly.". The today screen just locked up on me again and I believe TouchPal was found to be the cause of this yesterday so I'm testing further.
|