What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[ROM] ApeX for Droid X - An AOSP Experience

You need to manually enable overclocking :

su
insmod /system/lib/modules/overclock.ko
setscaling.sh

I am trying to test the overclock shell script.

I first did:

su
overclock -off
reboot

This, I understand, will disable overclocking at boot time.

I then went back to terminal emulation and typed:

su
cpuinfo


maximum frequency applied: 1000000
maximum frequency available: 1000000
minimum frequency applied: 300000
minimum frequency available: 300000


I then typed:

overclock -oc * in the same terminal

I got back the:

"Blazing at 400/700/900/1300"

but when i typed:

cpuinfo

It gives me the same results as before i typed "overclock -oc"

What am I doing wrong?



Sent from my DROIDX using Tapatalk
 
anyone having issues after install with lockups and then reboots ? I have exchange configured for my work. Im temporarily trying to restore the backup and may try again in a couple of days.
 
I still expierence some lockups and/or reboots. I have overclocking disabled on boot. Fab suggested it could possibly be app related. Trying to figure out which app is causing this issue seems to be a very daunting task.

UPDATE: I bought the Droid X/2 Overclock app and been running for 2 days with ULV 1.35Ghz and no reboots.
 
Last edited:
I was having reboot issues and massive slowdown on Apex all of a sudden. Went to Rubix with all the same apps and the slowdown is gone. Too soon to give a verdict on the reboots...
 
Does anyone know if there is a Galaxy theme for the X that I can use. I saw one called the Gala X theme, but it was running over TranQ. Not sure if it would play nice with ApeX.
 
Wow...did something or downloaded wrong. I got a bootloop. Tried to restore nandroid, and it also bootlooped. I had to go back to a pre-ApeX backup, and that restored.

For now, I am saying forget it and SBFing and will re root, and then install ApeX again. Or else I may run stock for a day just to appreciate customs. LOL.

Edit: It's been 15 minutes and I see how pitifully slow stock is...but I am too tired to flash a ROM tonight.
 
Last edited:
Fab,

In the next release of ApeX can you not package in spare parts, terminal emulator and others? For some reason when updates are available for the prepackaged apps, they are not listed for updates. There seems to be a new update for terminal emulator which supports the delete key when using the swype keyboard. For me this is huge. So I download the update but now have 2 terminal emulator apps installed.
Am I perhaps doing something wrong?

Sent from my DROIDX using DroidForums App
 
I've noticed the same thing and agree they should be separate from the ROM itself, although I wonder if they can be removed via command line?

Fab,

In the next release of ApeX can you not package in spare parts, terminal emulator and others? For some reason when updates are available for the prepackaged apps, they are not listed for updates. There seems to be a new update for terminal emulator which supports the delete key when using the swype keyboard. For me this is huge. So I download the update but now have 2 terminal emulator apps installed.
Am I perhaps doing something wrong?

Sent from my DROIDX using DroidForums App
 
Tired of 2.1

Ok I was one of those unfortunate people who went from 2.1 > 2.2 then realized how EXTREMELY buggy it was, and tried to sbf with a 2.1 sbf ---> FAIL. Ended up with a bricked "MEM MAP BLANK" error phone. Verizon couldnt fix so they sent another. Just told them the 2.2 update broke it >:P.

Now it came stock with 2.1 and I like the speed of it because to me, 2.1 is so much faster than 2.2 was. 2.2 is just laggy, and slow to me.

Now I'm tired of 2.1 --> and want some of the features that 2.2 has. I guess I just want to know if I should do an OTA update, or is there some hacked 2.2 update I can do that will allow me to go BACK to 2.1 if I want to?
 
When moving from 2.1 to 2.2 it changes the bootloader. This is why when you tried to go back to 2.1 sbf it bricked the phone. You could have used the 2.2 sbf and you would be back to 2.2. I am not sure if there is a way to downgrade your bootloader (not sure that you would want to).
There are many roms you can use to get better performance then with the stock vzw rom.


Ok I was one of those unfortunate people who went from 2.1 > 2.2 then realized how EXTREMELY buggy it was, and tried to sbf with a 2.1 sbf ---> FAIL. Ended up with a bricked "MEM MAP BLANK" error phone. Verizon couldnt fix so they sent another. Just told them the 2.2 update broke it >:P.

Now it came stock with 2.1 and I like the speed of it because to me, 2.1 is so much faster than 2.2 was. 2.2 is just laggy, and slow to me.

Now I'm tired of 2.1 --> and want some of the features that 2.2 has. I guess I just want to know if I should do an OTA update, or is there some hacked 2.2 update I can do that will allow me to go BACK to 2.1 if I want to?
 
So either way I am going to need to do the OTA update to 2.2 before modding right? Probably need to un-root first I guess as well aye?
 
Back
Top