Hello...
I have a rooted EVO running 2.3 via the recent flashable update. Swype (version 2.5-ish I think) came pre-installed on that ROM.
In the past couple days, Swype came out with a beta version (3.5.xxx) that I wanted to try so I did some research and got some suggestions that all I needed to do was to freeze or remove the Swype apk via Titanium, run the beta install, download the beta and I'd be all set.
I went the "uninstall" route for the Swype apk and that went fine even though Titanium "warned" me that I was now messing with a "system app." I even reinstalled the Swype 2.5 version to see if I could get back to where I was and I had no problems.
So, I did the uninstall, signed into my beta login, downloaded Swype 3.5, installed and everything was great, UNTIL...
I reboot...then force close, fc, fc, fc, one after another, rapid succession with the following message:
Now, although I was confident that all I had to do was uninstall the apk with Titanium, I did also read the suggestion to remove the following file in /system/lib as well:
/system/lib/libSwypeCore.so
The SPECIFIC file name that I found with Root Explorer was "/system/lib/libSwypeCore.2.50.72.20895.so"
AHA!!! I found the SwypeCore file and thought that since it referenced the ROM-installed 2.50.xxx number and the beta was 3.5.xxx that all I had to do was remove the file and I would be good to go!! I moved the file and renamed it to a non-root section of my card, rebooted and hoped for the best and...
NOPE...DID NOT WORK!! Same force close messages again!!
Now, NOTE: prior to accepting the download via the Swype beta install, I received the following WARNING:
I do read warnings and DID read the above. Even the Sprint site warns of this problem (Support - Article ) but honestly thought that, hey, I'm rooted, and if I (1) removed the apk file and (2) after experiencing the force closes, removed the SwypeCore file in /system/lib that I would AVOID the problems and the force closes....
Well, as you can see now, I'm still having the problems.
I was wondering if anyone (has cared enough to ) SUCCESSFULLY remove the pre-installed Swype apk and get back onto the beta version?? Or does anyone know what I need to do to avoid these force closes?? Is there something else that needs to be done or file removed?? I can pick and choose which Swype apk version to run (2.5.xxx or beta 3.5.xxx) but the beta 3.5 does not work.
An INTERESTING THING is that the beta 3.5 works JUST FINE WITHOUT PROBLEM after uninstalling version 2.5, running the beta installer and downloading/installing the beta version. But AFTER THE PHONE IS REBOOTED, then allllllll the force closes come back. SOMETHING during the reboot process...with the beta apk itself, or a system file or SOMETHING...and/or after startup is causing these force-closes!! Any ideas??
THANKS!!
I have a rooted EVO running 2.3 via the recent flashable update. Swype (version 2.5-ish I think) came pre-installed on that ROM.
In the past couple days, Swype came out with a beta version (3.5.xxx) that I wanted to try so I did some research and got some suggestions that all I needed to do was to freeze or remove the Swype apk via Titanium, run the beta install, download the beta and I'd be all set.
I went the "uninstall" route for the Swype apk and that went fine even though Titanium "warned" me that I was now messing with a "system app." I even reinstalled the Swype 2.5 version to see if I could get back to where I was and I had no problems.
So, I did the uninstall, signed into my beta login, downloaded Swype 3.5, installed and everything was great, UNTIL...
I reboot...then force close, fc, fc, fc, one after another, rapid succession with the following message:
Now, although I was confident that all I had to do was uninstall the apk with Titanium, I did also read the suggestion to remove the following file in /system/lib as well:
/system/lib/libSwypeCore.so
The SPECIFIC file name that I found with Root Explorer was "/system/lib/libSwypeCore.2.50.72.20895.so"
AHA!!! I found the SwypeCore file and thought that since it referenced the ROM-installed 2.50.xxx number and the beta was 3.5.xxx that all I had to do was remove the file and I would be good to go!! I moved the file and renamed it to a non-root section of my card, rebooted and hoped for the best and...
NOPE...DID NOT WORK!! Same force close messages again!!
Now, NOTE: prior to accepting the download via the Swype beta install, I received the following WARNING:
I do read warnings and DID read the above. Even the Sprint site warns of this problem (Support - Article ) but honestly thought that, hey, I'm rooted, and if I (1) removed the apk file and (2) after experiencing the force closes, removed the SwypeCore file in /system/lib that I would AVOID the problems and the force closes....
Well, as you can see now, I'm still having the problems.
I was wondering if anyone (has cared enough to ) SUCCESSFULLY remove the pre-installed Swype apk and get back onto the beta version?? Or does anyone know what I need to do to avoid these force closes?? Is there something else that needs to be done or file removed?? I can pick and choose which Swype apk version to run (2.5.xxx or beta 3.5.xxx) but the beta 3.5 does not work.
An INTERESTING THING is that the beta 3.5 works JUST FINE WITHOUT PROBLEM after uninstalling version 2.5, running the beta installer and downloading/installing the beta version. But AFTER THE PHONE IS REBOOTED, then allllllll the force closes come back. SOMETHING during the reboot process...with the beta apk itself, or a system file or SOMETHING...and/or after startup is causing these force-closes!! Any ideas??
THANKS!!