• 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)

The way I put it on the first time was by flashing the entire 1.3.0 w battery icon over my original 1.3.0. So I don't think that will work.
 
Try going into /usr/bin/setup_bt.sh and deleting the line that does autokilling. You'll know which one it is when you see it.

See if that solves the problem. You may need to chmod it back to 755 when you replace the file.

Fab,

Was able to figure this out and it worked!!! Thanks!

Question tho. In that script there was a sleep 42s before the settings and sleep 2s after it. I deleted the adjustments for the script but left the 42 and 2s text in the script. Is that ok? Or should I delete that as well?
 
I'm not sure if it's my WiFi router or if it's the Apex 1.3.1, but for some odd reason my Wifi keeps dropping out. It says it's connected to my router, but oddly there's no sign of the Wifi in the notification bar and it says in my browser that I don't have internet. It didn't do this with 1.3.0 ROM.

Also, for some reason when I try to save custom battery settings, everything clicks and sets itself in place, (Instead of the 10:00 Pm, I want my data turning off after 15 minutes at midnight instead and go to 7:00 AM). But when ten PM comes around, my data's turning off like it's in the nighttime preferences. Any ideas?
 
im getting random reboots i think its bc of overclocking. i normally use LV @ 1.2 been using that forever and now since 1.3 ive been getting reboots. updates to 1.3.1 same thing. what should i do? im using jrummy's app

Try changing it to 1000 @ LV and see if the problem goes away.
 
Fab,

Was able to figure this out and it worked!!! Thanks!

Question tho. In that script there was a sleep 42s before the settings and sleep 2s after it. I deleted the adjustments for the script but left the 42 and 2s text in the script. Is that ok? Or should I delete that as well?

No don't delete those. They're in there for a reason. If you try to apply some of those changes too early, it messes up the bootup sequence and makes the system unresponsive at bootup.

Tried that and now it says it's not found.

Check your messaging app anyways. It'll throw out an error, but it'll still do its job.
 
Thanks for the feedback but I think you guys are missing what I'm saying. If someone sends me a text I get it in my Messaging App and the stock DX Text Messaging App. I'm trying to get rid of the stock one because I'm tired of checking the same text message in 2 different things.
 
Thanks for the feedback but I think you guys are missing what I'm saying. If someone sends me a text I get it in my Messaging App and the stock DX Text Messaging App. I'm trying to get rid of the stock one because I'm tired of checking the same text message in 2 different things.

I just turned off notifications for the "stock" messaging app, only get notified for my Handcent app and even though they're in the stock messaging app, i just don't go in there since I only use Handcent.

I'm not sure other than doing something like that why you would care if they are in the stock one, if you don't use it, it's out of sight out of mind?

When I delete the message in Handcent, it deletes out of the stock (just checked out of curiosity)

Sorry I can't help in that, I always thought the messaging.apk was needed for sms to work but you didn't have to actually use it.
 
I just turned off notifications for the "stock" messaging app, only get notified for my Handcent app and even though they're in the stock messaging app, i just don't go in there since I only use Handcent.

I'm not sure other than doing something like that why you would care if they are in the stock one, if you don't use it, it's out of sight out of mind?

When I delete the message in Handcent, it deletes out of the stock (just checked out of curiosity)

Sorry I can't help in that, I always thought the messaging.apk was needed for sms to work but you didn't have to actually use it.

Yeah that'll be fine if I can't delete it. Thanks.
 
Hi guys I just got my droid x about a week ago and ever since I haven't been shy about reading a lot of the threads on here about rooting and roms etc. After feeling comfortable from reading all the guides on here I made my nandroid backup and loaded apex onto my phone and I must say it was the easiest thing to ever do and its extremely smooth.

I am only having one minor quirk problem and I can not figure out whats causing it or what setting I have checked thats making it happen. Everytime I set my wallpaper and reboot my phone it comes on with some grassy type wallpaper and not the one i set. when I long press my home screen and set my wallpaper the grass wallpaper is its own option and its called Wallpaper Gallery and has a icon of a house with the android inside it. I have Beautiful widgets installed and checked to see if i did something in there but I can not see anything so I don't know whats the reason why my wallpaper that I set is reverting back to this grass wallpaper.


great forum here, lots of information to gather :D
 
Had something really weird just happen. Phone just out of nowhere rebooted, the Blue android text appeared for a few seconds, then the screen went black and a "Warning" pop up came up and said the system isn't respond, wait or close. So I pulled the battery and it booted up normally. Any idea what that was about? I'm not overclocked or anything.
 
Here is a GB Themed Dialer, that I put together for Apex 1.3.1.

Enter Recovery, install zip from SD Card. Choose the .zip, install, enjoy!

Do NOT wipe date/cache.

I suggest making a backup before flashing, just as a precaution!

DOWNLOAD


Thanks, flashed jsut fine.

screenshot3ze.png
 
Hey Apex,

Awesome ROM you've got here. In terms of speed and smoothness, it's what the Droid X SHOULD have been out of the box...

Have a question for you - I'm trying to restore the the DroidX eye boot screen via the command in terminal. However, I'm getting an error stating it can't find the BAK file in /system...any idea why this is? Do I have to find and push the file to my phone via ADB?

Thanks for your help
 
If anyone else was having an issue here is how I fixed mine.

I had unwittingly caused the problem myself by altering the "bootanimation" file in System/Bin/ in the phone... I restored the original file which I was fortunate enough to have saved a backup of then placed the bootanimation.zip of my choice under data/local/ and rebooted and it works!

:)


I tried changing my bootanimation two different ways yesterday and I get the same result... Motorola Logo for bootup nothing else.

1st Method) found "bootanimation" file under System/Bin instead of Data/Local like "Stock" and replaced that file with the one I wanted... white moto logo on reboot.

2nd Method) free app from market called Boot Animation Changer... picked one as a test, it downloaded and said Boot Animation changed successfully... white moto logo on reboot.

Anyone know the correct file to replace to change the boot animation using this ROM (Apex 1.3)?
 
Had something really weird just happen. Phone just out of nowhere rebooted, the Blue android text appeared for a few seconds, then the screen went black and a "Warning" pop up came up and said the system isn't respond, wait or close. So I pulled the battery and it booted up normally. Any idea what that was about? I'm not overclocked or anything.

Just had the same thing happen to me less than an hour ago.
 
Here is a GB Themed Dialer, that I put together for Apex 1.3.1.

Enter Recovery, install zip from SD Card. Choose the .zip, install, enjoy!

Do NOT wipe date/cache.

I suggest making a backup before flashing, just as a precaution!

DOWNLOAD

Sweet! Thanks for this! Don't be surprised if this is in 1.3.2 Of course, all credit will be given to you! :)

Hey Apex,

Awesome ROM you've got here. In terms of speed and smoothness, it's what the Droid X SHOULD have been out of the box...

Have a question for you - I'm trying to restore the the DroidX eye boot screen via the command in terminal. However, I'm getting an error stating it can't find the BAK file in /system...any idea why this is? Do I have to find and push the file to my phone via ADB?

Thanks for your help

the dxeye removes/restores the Droid Eye live wallpaper, not the boot animation. It can't find the .bak file because you didn't ever remove it ;)

Just had the same thing happen to me less than an hour ago.

Hrm, this is caused by my startup script, if it runs too early in the boot up cycle. Was this right after installing a theme or something?

I have it set to a 42 second delay after the phone starts booting up, and that usually is enough, but I may increase it to like 60s if more people are having this issue.

The only way to fix it seems to be a battery pull, for now.
 
Sweet! Thanks for this! Don't be surprised if this is in 1.3.2 Of course, all credit will be given to you! :)



the dxeye removes/restores the Droid Eye live wallpaper, not the boot animation. It can't find the .bak file because you didn't ever remove it ;)



Hrm, this is caused by my startup script, if it runs too early in the boot up cycle. Was this right after installing a theme or something?

I have it set to a 42 second delay after the phone starts booting up, and that usually is enough, but I may increase it to like 60s if more people are having this issue.

The only way to fix it seems to be a battery pull, for now.

It was out of nowhere to me, but I guess as long as you are aware, and it's not a MAJOR issue, no biggie.
 
Thanks for the feedback but I think you guys are missing what I'm saying. If someone sends me a text I get it in my Messaging App and the stock DX Text Messaging App. I'm trying to get rid of the stock one because I'm tired of checking the same text message in 2 different things.

I had the exact same issue and I had a problem a few posts back (20-30).

I wanted the non-blur messaging app and so when I typed:

su
messaging -aosp

I kept getting errors.

So then I typed:
su
messaging -mot

All was good. I then typed:
su
messaging -aosp

And now I am using the non-blur version of messaging, and I only get one text instead of two.

Try that and if it doesnt work, then try it in reverse order. If it still doesn't work, then try to type just messaging without the switch and see if you get the help file. If still doesn't work, you may not have the scripts installed.

Hope it helps.
 
This is my first Droid X ROM and hands down.... I love this ROM.
The new Gingerbread keyboard is nice and the open/close window effects are very nice.

I backed up my old stock setup with launcher pro but I can't envision going back.

Good job, going to buy you a few beers for this.:D
 
Back
Top Bottom