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

Been using Apex for over 2 weeks, on my DX its been the best ROM that I have used to date. Today I wanted some color. I added what I think is the best theme Droid928's theme. I have no Issues at all, I first used his build.prop and then Apex build.prop. Apex had 2 changes in his build.prop. Now I have a great phone. Congrats to both, keep up the great work, I am in heaven.

Thanks
 
@fab not sure if your still trolling this thread

but i've been using dx/d2 over clocking app from the market
and that app rocks big time. the question I have is their a way to
get your rom to go past 1.3ghz. and second has anyone figured out a way
to get the OG 2.2 Dialer to work on any DX rom. I dislike the blur dialer
and I have Dialer one from the market running over it but it would be nice to have that blur dialer gone. I know it has something to do with the DX radio and it not working if you remove the dialer. any suggestions
 
Where are the settings for the OC profiles stored? I'd like to use the -lv option, however the settings ApeX uses locks up my phone. The DX/D2 overclock app in the market I use does not lock up my phone with its lv presets so I'd like to mimic those at boot.
 
@fab not sure if your still trolling this thread

but i've been using dx/d2 over clocking app from the market
and that app rocks big time. the question I have is their a way to
get your rom to go past 1.3ghz. and second has anyone figured out a way
to get the OG 2.2 Dialer to work on any DX rom. I dislike the blur dialer
and I have Dialer one from the market running over it but it would be nice to have that blur dialer gone. I know it has something to do with the DX radio and it not working if you remove the dialer. any suggestions

I've got Apex to go to 1.35ghz which is as far as it would go on stock Froyo as well on my phone. You can try different kernels but the more reading I do the more I find out that the DX varies wildly as far as the overclocking abilities. Some ppl have issues with the minor bump to 1.1ghz when you load Apex so I would be thankful you can hit 1.3ghz and leave it at that. I got a Quadrant score of 1761 running Apex at 1.35ghz. Anything over 1.35 causes the phone to lock up bigtime.
 
Ok so to over clock this with jrummys app....should we turn off the built in overclock or should we just go about it like it never existed?
 
Just go about it like it never existed. To the user who couldn't get facebook installed, no idea what is going on there. Everything on my X works just like stock Froyo, just faster.
 
I've used all RC1, RC2, and V1 and I must say Fab did a tremendous job on V1. I'm absolutely loving this ROM, the only issues i had was the rebooting (which i turned overclock off so no more of that) and the camera panoramic assist (which i applied the fix for)..other than that...LOOOOOVEE..thanks so much for your hard work!!


Do you have more info for the panoramic fix?
 
Overclocking questions

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?
 
I've been having reboot issues too. About once a day which is not acceptable to me after the thing rebooted right in the middle of me using it as a GPS and I had to pull over and backtrack. I'm guessing its the overclock but I've brought it back down to med voltage and 1.1ghz and it still does it.

I'm going to give rubix another shot and see if the reboot issues still happen.

Not sure what the "panoramic fix" is, the blur camera is just fine on mine unless you mean you don't want it to be full panoramic every time and want something like the AOSP camera's widescreen which is more standard to what actual cameras do.
 
I've been having reboot issues too. About once a day which is not acceptable to me after the thing rebooted right in the middle of me using it as a GPS and I had to pull over and backtrack. I'm guessing its the overclock but I've brought it back down to med voltage and 1.1ghz and it still does it.

I'm going to give rubix another shot and see if the reboot issues still happen.

Not sure what the "panoramic fix" is, the blur camera is just fine on mine unless you mean you don't want it to be full panoramic every time and want something like the AOSP camera's widescreen which is more standard to what actual cameras do.


When you try to use panoramic mode with the camera included in ApeX v1, you will be prompted in what direction to capture the pictures. Once you choose a direction, the app quits.
 
Ah, never had that issue. I just turn sideways and shoot, that is plenty wide enough for me haha. You could always just download Vignette premium and go with that. That is what I use when I run a non-blur rom because it goes full wide.

Just tried rubix again and I went back to Apex till I get home and have some time to mess with it not having any interruptions. All my contacts got erased for some reason so thank god for nandroid lol.
 
is there a way to get the music controls back on the lockscreen?


Yes, revert back to the stock music player with th following in terminal emulator:

su
music -mot

Also, I believe the panoramic assist issue is caused by installing NexTheme. The fix would be to get the original .apk from ApeX and install it over the themed one.

Sent from my DROIDX using Tapatalk
 
Back
Top