• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

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

I would really recommend updating to the newer kernel at MDW. Most of my issues with apps have been fixed with the new kernel.
 
Fabolous said:
If you open up the 1.3.0 update file, there's a folder called sdcard, and in it is 'ApeX'

Put that on your sdcard and my script'll work again.



Also, check this out :D

DROID DOES

"Unofficial Gingerbread update", rotflmao.
Click to expand...

Thanks Fab you are the man! Worked like a charm!

I would've stayed with the GB keyboard as I love the black and orange color and predictive text, it was just the small keys that were really bothering me. Hopefully someone maybe at XDA will fix that up at some point and it can be used in the next version of ApeX! :)

Im using the black MT now and its much better for me. I will say though that the vibrations are much stronger in the GB keyboard vs. the MT. Any idea why that is? I prefer the stonger vibrations, but eh, I can live with it.

Thanks again my friend. :D

Haha on the update!
 
Fabolous said:
Hey guys with the Handcent MMS issue, can you try switching from the AOSP messaging to the Blur app? Since the AOSP one has modified code (for the black backgrounds and custom notifications), Handcent may be having some issues communicating with it.

Handcent requires a native SMS app for MMS functionality. So what I'd like you guys to try to do is change that native app:

su
messaging -mot

And then try to send a MMS with Handcent. Be sure to go to 'Text Messaging' to turn off notifications, or you'll get double.
Click to expand...

This works for me...but now the popups won't show on the lockscreen.
 
anyone else getting sporadic market Force Close's?

I've never had the market FC on me until now. and since i've upgraded to 340, and apex 1.3, it has happened 4-5 times. It works normally other times. usually it FCs when downloadding multiple items.

Don't know if it is 340 or Apex, or something else.

Anyone else?
 
Trooper said:
Thanks Fab you are the man! Worked like a charm!

I would've stayed with the GB keyboard as I love the black and orange color and predictive text, it was just the small keys that were really bothering me. Hopefully someone maybe at XDA will fix that up at some point and it can be used in the next version of ApeX! :)

Im using the black MT now and its much better for me. I will say though that the vibrations are much stronger in the GB keyboard vs. the MT. Any idea why that is? I prefer the stonger vibrations, but eh, I can live with it.

Thanks again my friend. :D

Haha on the update!
Click to expand...
I've gotten used to it but if anyone hears about it getting a size increase let me know.
 
incrediblenotinstock said:
Hey excellent rom but my phone won't vibrate is there a fix
Click to expand...

Vibration in general? Or just using the keyboard? If its the keyboard, make sure you have vibration enabled.

Menu>Settings>Language and Keyboard>Mulitouch keyboard settings. Then check Vibrate on keypress.

If its the entire phone, download Sound Manager from the market. Go to menu, and vibration. Set both settings to vibrate all the time.

novemberwhiskey said:
anyone else getting sporadic market Force Close's?

I've never had the market FC on me until now. and since i've upgraded to 340, and apex 1.3, it has happened 4-5 times. It works normally other times. usually it FCs when downloadding multiple items.

Don't know if it is 340 or Apex, or something else.

Anyone else?
Click to expand...

Not really. I was getting a fair amount on the leak, but so far so good. Did you try clearing data and cache for the market?

Rockaholic said:
I've gotten used to it but if anyone hears about it getting a size increase let me know.
Click to expand...

Ditto. I like the keyboard a lot. Unfortunately my big hands do not. I hope it gets fixed at some point. If so, I will be going back to the GB keyboard.
 
Fabolous said:
Hey guys with the Handcent MMS issue, can you try switching from the AOSP messaging to the Blur app? Since the AOSP one has modified code (for the black backgrounds and custom notifications), Handcent may be having some issues communicating with it.

Handcent requires a native SMS app for MMS functionality. So what I'd like you guys to try to do is change that native app:

su
messaging -mot

And then try to send a MMS with Handcent. Be sure to go to 'Text Messaging' to turn off notifications, or you'll get double.
Click to expand...

This fixed the Handcent problem... I had figured out if you put the phone in airplane mode while sending before and then take it out of airplane it would work too... but that was annoying... this fixed it up right...
 
Fab - sweet job once again. Will be sending you some more NOS funds soon.

Minor problem, or more a source of can't figure out what is going on: I was on 2.3.15 and using Apex 1.0.2.2 with no problems. Wanted 1.3, so I cleared data, cleared cash, and restored to my non-Apex image. Booted up, set the phone up, and then went to check updates and received the OTA update to .340. That installed "successfully". However, EVERY time I did a shut down/restart, it would boot into Recovery?? I just select first option "reboot phone" and she would boot just fine. Everything worked great in the .340 OTA. But, do a restart and it would only boot into Recovery mode... I did multiple Clear Data/Cache's, but no different. I repeated all over (2.3.15 -> OTA .340 and clearing of everything), same issue. Did another restore to 2.3.15, and absolutely no issues rebooting. Did one more OTA to .340, and had the reboot to Recovery, so I said screw it and installed 1.3, and it's working great!? No restarts to Recover anymore.....

So, what did I miss? Could it be a bootloader version issue? Z4Root or Bootstrap issue?? This is bugging me..

Thanks - daggerNC
 
Trooper said:
Thanks Fab you are the man! Worked like a charm!

I would've stayed with the GB keyboard as I love the black and orange color and predictive text, it was just the small keys that were really bothering me. Hopefully someone maybe at XDA will fix that up at some point and it can be used in the next version of ApeX! :)

Im using the black MT now and its much better for me. I will say though that the vibrations are much stronger in the GB keyboard vs. the MT. Any idea why that is? I prefer the stonger vibrations, but eh, I can live with it.

Thanks again my friend. :D

Haha on the update!
Click to expand...

I still can't get the GB keyboard to work, after I select it within terminal and it reboots, I just get FCs "(process com.android.inputmethod.latin) has stopped.."
 
Hey guys ive got two problems, that im pretty sure are actual functionality that i dont know how to use, but i keep hiding my notifications bar and main dock accidentally and i have no idea how to get them back other then restart my phone. And i couldnt figure if i could turn it off in ADW settings either. Any ideas?
 
andrewmiller said:
Hey guys ive got two problems, that im pretty sure are actual functionality that i dont know how to use, but i keep hiding my notifications bar and main dock accidentally and i have no idea how to get them back other then restart my phone. And i couldnt figure if i could turn it off in ADW settings either. Any ideas?
Click to expand...
For the main dock one just swipe up on the blank space. That space can actually be used as an additional dock.
 
daggerNC said:
Fab - sweet job once again. Will be sending you some more NOS funds soon.

Minor problem, or more a source of can't figure out what is going on: I was on 2.3.15 and using Apex 1.0.2.2 with no problems. Wanted 1.3, so I cleared data, cleared cash, and restored to my non-Apex image. Booted up, set the phone up, and then went to check updates and received the OTA update to .340. That installed "successfully". However, EVERY time I did a shut down/restart, it would boot into Recovery?? I just select first option "reboot phone" and she would boot just fine. Everything worked great in the .340 OTA. But, do a restart and it would only boot into Recovery mode... I did multiple Clear Data/Cache's, but no different. I repeated all over (2.3.15 -> OTA .340 and clearing of everything), same issue. Did another restore to 2.3.15, and absolutely no issues rebooting. Did one more OTA to .340, and had the reboot to Recovery, so I said screw it and installed 1.3, and it's working great!? No restarts to Recover anymore.....

So, what did I miss? Could it be a bootloader version issue? Z4Root or Bootstrap issue?? This is bugging me..

Thanks - daggerNC
Click to expand...

Did you reinstall Bootstrapper, give it root access, and rebootstrap it? I'm not going to get into the specifics why it keeps rebooting into recovery, but basically there's a file the bootstrapper uses to load recovery at boot each time, but once a full boot completes, the file is deleted by the bootstrapper app.

If you don't have the app, it doesn't delete the file.

andrewmiller said:
Hey guys ive got two problems, that im pretty sure are actual functionality that i dont know how to use, but i keep hiding my notifications bar and main dock accidentally and i have no idea how to get them back other then restart my phone. And i couldnt figure if i could turn it off in ADW settings either. Any ideas?
Click to expand...

Swipe up on the screen to get your notification bar back. Swipe down on where the main dock is to get it back.

You can load up my adw settings, which does away with both of these features (but keeps swipe down on screen for notification bar) by doing the following:

In terminal

su
fabadw

return home, hit menu, adw prefs, scroll down and restart adw

k0smo86 said:
I still can't get the GB keyboard to work, after I select it within terminal and it reboots, I just get FCs "(process com.android.inputmethod.latin) has stopped.."
Click to expand...

Ok, gimme a sec to look over my script. It may not be correctly changing back the library files.
 
Trooper said:
Vibration in general? Or just using the keyboard? If its the keyboard, make sure you have vibration enabled.

Menu>Settings>Language and Keyboard>Mulitouch keyboard settings. Then check Vibrate on keypress.

If its the entire phone, download Sound Manager from the market. Go to menu, and vibration. Set both settings to vibrate all the time.



Not really. I was getting a fair amount on the leak, but so far so good. Did you try clearing data and cache for the market

Ditto. I like the keyboard a lot. Unfortunately my big hands do not. I hope it gets fixed at some point. If so, I will be going back to the GB keyboard.
Click to expand...
I got it working thank you very much
 
novemberwhiskey said:
anyone else getting sporadic market Force Close's?

I've never had the market FC on me until now. and since i've upgraded to 340, and apex 1.3, it has happened 4-5 times. It works normally other times. usually it FCs when downloadding multiple items.

Don't know if it is 340 or Apex, or something else.

Anyone else?
Click to expand...

I had some issues with it as well and there are some posts about in a few hundred threads before, but it boils down I think to two versions of the market conflicting with each other.

What I did is SBF to .320 and then in the Apex 1.3 file, I deleted the vending.apk from it so it would not install and then applied the Apex 1.3 update and since then I have had no more FC. I even updated to the new market as well with no problems.

The same issue applies to the Gmail app as well.

YMMV.
 
I'm also having problems with the camera everytim I take it picture it doesn't show up in the gallery. Idk if it has to do with this rom. But any help would be appreciated
 
incrediblenotinstock said:
I'm also having problems with the camera everytim I take it picture it doesn't show up in the gallery. Idk if it has to do with this rom. But any help would be appreciated
Click to expand...

Does any of your media work (i.e music, video)?

If not, you need to update to .320 or .340 because your kernel is incorrect.
 
Fabolous said:
Hey guys with the Handcent MMS issue, can you try switching from the AOSP messaging to the Blur app? Since the AOSP one has modified code (for the black backgrounds and custom notifications), Handcent may be having some issues communicating with it.

Handcent requires a native SMS app for MMS functionality. So what I'd like you guys to try to do is change that native app:

su
messaging -mot

And then try to send a MMS with Handcent. Be sure to go to 'Text Messaging' to turn off notifications, or you'll get double.
Click to expand...


I did the script but now getting error NATIONAL COVERAGE NOT AVAILABLE AND WON'T SEND MY MMS =(
 
Will the market update still be pushed to me with this new rom applied? Also when this rom is updated how hard is it to install the update?


Edit- also isnt there a way to overclock from the terminal?
 
You must log in or register to reply here.
Back
Top Bottom