[ROM] ApeX 1.3.1 for Droid X - Running, running, as fast as it can (12/16/10)

[Fabolous]

The FCs from Gmail are because of the update that came out, so a lot of you have the newest version on your /data partition, and the ROM installs it on /system, which causes a little panic

I've updated the instructions for 1.2.1 upgraders in the OP to just uninstall updates to Gapps (Gmail, Voice Search, Search Bar, Market) prior to updating to 1.3.0, since it automatically installs those updates to /system.

 

[buenos]

FYI:
I installed the theme too...i was getting the FC on gmail too....didnt want to reload the rom.
just for fun i went in and cleared the data through application - gmail and it resynced and all is good.....

 

[kman79]

Thanks for the replies guys.

After getting gmail to work on ApeX 1.3 with the Revo theme, the black menus of ApeX 1.3 has reverted back to the silver/grey color. Really liked the black menus on 1.3. It's still functional, just sorta an FYI to Fab if he didn't know

 

[hyperlite]

Everything is running great. I haven't bothered installing a theme...I liked the added color and thoroughness of nextheme but the gingerbread theme is so sexy. Props again fab.

Sent from my DROIDX using Tapatalk

 

[Porterhouse0]

The FCs from Gmail are because of the update that came out, so a lot of you have the newest version on your /data partition, and the ROM installs it on /system, which causes a little panic

I've updated the instructions for 1.2.1 upgraders in the OP to just uninstall updates to Gapps (Gmail, Voice Search, Search Bar, Market) prior to updating to 1.3.0, since it automatically installs those updates to /system.

what if there are no options to uninstall updates in those apps in manage apps...but im still getting FCing in gmail...not all the time by any means....but enough to say "whats going on?" lol

Edit: and am i able to go back to 1.2.1...

 

[Fabolous]

The FCs from Gmail are because of the update that came out, so a lot of you have the newest version on your /data partition, and the ROM installs it on /system, which causes a little panic

I've updated the instructions for 1.2.1 upgraders in the OP to just uninstall updates to Gapps (Gmail, Voice Search, Search Bar, Market) prior to updating to 1.3.0, since it automatically installs those updates to /system.

what if there are no options to uninstall updates in those apps in manage apps...but im still getting FCing in gmail...not all the time by any means....but enough to say "whats going on?" lol

Edit: and am i able to go back to 1.2.1...

Did you try going into manage applications and clear the data/cache.

It'll take like a couple of mins to sync again, and you'll have to redo notifications, but I've gotten reports this fixes the FC issues.

 

[Porterhouse0]

The FCs from Gmail are because of the update that came out, so a lot of you have the newest version on your /data partition, and the ROM installs it on /system, which causes a little panic

I've updated the instructions for 1.2.1 upgraders in the OP to just uninstall updates to Gapps (Gmail, Voice Search, Search Bar, Market) prior to updating to 1.3.0, since it automatically installs those updates to /system.

what if there are no options to uninstall updates in those apps in manage apps...but im still getting FCing in gmail...not all the time by any means....but enough to say "whats going on?" lol

Edit: and am i able to go back to 1.2.1...

Did you try going into manage applications and clear the data/cache.

It'll take like a couple of mins to sync again, and you'll have to redo notifications, but I've gotten reports this fixes the FC issues.

Yeah I cleared data and cache. I even fixed permissions in rom manager. The droid forums app force closed on me twice while writing this reply. Can I go back to 1.2.1?

Sent from my DROIDX using DroidForums App

 

[droidxchat]

if you're getting FC you should try installing alogcat (free from market) and changing the level to error only, then next time you get a FC post what alogcat says here

 

[Porterhouse0]

if you're getting FC you should try installing alogcat (free from market) and changing the level to error only, then next time you get a FC post what alogcat says here

I will try that thank you...if that does not work I'm hoping I can revert back

Sent from my DROIDX using DroidForums App

 

[gamemaster333]

I'm pretty sure it may just be me , but is anybody else having trouble swapping out the keyboard through terminal emulator? I type in "su", then "keyboard". I wanted the black multitouch one so I input "bmt" and it says "bmt: not found". It says this same thing for any option that I use. Can anybody help?

 

[hyperlite]

I'm pretty sure it may just be me , but is anybody else having trouble swapping out the keyboard through terminal emulator? I type in "su", then "keyboard". I wanted the black multitouch one so I input "bmt" and it says "bmt: not found". It says this same thing for any option that I use. Can anybody help?

Su
Keyboard -bmt

Sent from my DROIDX using Tapatalk

 

[bamfsig45]

I'm pretty sure it may just be me , but is anybody else having trouble swapping out the keyboard through terminal emulator? I type in "su", then "keyboard". I wanted the black multitouch one so I input "bmt" and it says "bmt: not found". It says this same thing for any option that I use. Can anybody help?

su
keyboard -bmt


you're typing just like that?

 

[Porterhouse0]

I'm pretty sure it may just be me , but is anybody else having trouble swapping out the keyboard through terminal emulator? I type in "su", then "keyboard". I wanted the black multitouch one so I input "bmt" and it says "bmt: not found". It says this same thing for any option that I use. Can anybody help?

Su
Keyboard
Keyboard - bmt

I think lol
Sent from my DROIDX using DroidForums App

 

[gamemaster333]

That worked. Many thanks everyone!

 

[Fabolous]

And I've updated the instructions on the keyboard script to be a little more clear:

after switching keyboards, it automatically switches to Swype because the GB/MT keyboard was deleted for a split second before being replaced by the one chosen in the script.

So, after the reboot, you'll need to manually switch back to the correct keyboard.