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

Root [ROM] ApeX V1.0 for Droid X - An AOSP Experience (10/20/10)

Steven, sounds like your phone is not agreeing with my overclock profile. You may want to disable it with:

su
overclock -off

in terminal emulator.

If you have your own setscaling.sh that you know is stable, you can load it up on your sdcard and then apply it with:

su
overclock -sd

and if you want to make it auto apply those overclock settings at boot, you can additionally add:

overclock -on

Seems like the there are a few phones that cannot run 1.1 stable @ 56vsel. Maybe I'll just have auto-oc turned off by default for the next release?

Thanks for the super support Fab!

Any chance you could post a few alternate setscaling.sh set ups for us to try with instructions on how to load from sd?
 
Steven, sounds like your phone is not agreeing with my overclock profile. You may want to disable it with:

su
overclock -off

in terminal emulator.

If you have your own setscaling.sh that you know is stable, you can load it up on your sdcard and then apply it with:

su
overclock -sd

and if you want to make it auto apply those overclock settings at boot, you can additionally add:

overclock -on

Seems like the there are a few phones that cannot run 1.1 stable @ 56vsel. Maybe I'll just have auto-oc turned off by default for the next release?

Thanks Fab. One question. One thing I don't understand is why one phone would be fine with the overclocking and another wouldn't. Isn't this the age of mass-production and all things are the same? Understand, I'm not challenging your diagnosis, I just want to learn what makes some phones different than others that come off the same assembly line.

TIA.
 
Thanks Fab. One question. One thing I don't understand is why one phone would be fine with the overclocking and another wouldn't. Isn't this the age of mass-production and all things are the same? Understand, I'm not challenging your diagnosis, I just want to learn what makes some phones different than others that come off the same assembly line.

TIA.

Not so much the case, actually. There are many variables in the fabrication process. Each wafer will turn out different, and each chip on the wafer will have different performance. As long as they all pass a test (i.e. stable at 1GHz), they're shipped out.

That doesn't mean there aren't standouts that can get to 2GHz, and most likely, the majority can probably do like 1.3-1.5. But that also means there are the lemons (like mine) that are stuck at 1.15 or lower.

This happens a lot with computer processors too. They make a big batch, and then they're "binned" according to performance. The ones that clock higher get the faster moniker, while the lower clockers get the cheaper branding, when in fact, they were all produced together.
 
That doesn't mean there aren't standouts that can get to 2GHz, and most likely, the majority can probably do like 1.3-1.5. But that also means there are the lemons (like mine) that are stuck at 1.15 or lower.

Mine can't even handle 1.05. even at elevated voltages it hangs after a few minutes.
default 1.0 also hangs if I use low voltages.
Oh well.

But even at stock 1ghz, this thing flies with Apex!
 
Mine can't even handle 1.05. even at elevated voltages it hangs after a few minutes.
default 1.0 also hangs if I use low voltages.
Oh well.

But even at stock 1ghz, this thing flies with Apex!

-oc is running better than -def for me. Anyone else compare these?
 
Quadrant = 1575
FPS = 59

NICE!

My scores above were running stock OC at 1.1...

Here they are at 1.3

Quadrant = 1762
FPS = 59

WOW

snap20101022115238.png
 
Not so much the case, actually. There are many variables in the fabrication process. Each wafer will turn out different, and each chip on the wafer will have different performance. As long as they all pass a test (i.e. stable at 1GHz), they're shipped out.

That doesn't mean there aren't standouts that can get to 2GHz, and most likely, the majority can probably do like 1.3-1.5. But that also means there are the lemons (like mine) that are stuck at 1.15 or lower.

This happens a lot with computer processors too. They make a big batch, and then they're "binned" according to performance. The ones that clock higher get the faster moniker, while the lower clockers get the cheaper branding, when in fact, they were all produced together.

Thank you for your explanation.
Steven rants and raves complaining about his crappy processor. He's also thinking about returning it hoping to get a better one, but realizes he can't. Dammit!! (he says)

EDIT: I want to overclock so badly that I'm going to try it again without syncing with google programs. I know. Mental illness is repeating the same thing expecting different results.
 
So far, 2 random lock ups (which led to reboots) after installing the new OC edition... I'm now thinking I have an
 
I'm carefully restoring apps from TiBu Pro, rather than syncing from market right off.

I got a quadrant score of 1584, not bad.

I got one forced reboot, in the last hour. No more than that.

I also got the app drawer locked up. The rest of the apps worked fine. If I hit the home key I could access open apps. Eventually the home screen unlocked. I don't know what that was all about. I'll keep you posted.

Hmm... what shall I restore next?
 
You guys that are having issues with the default setscaling.sh can create your own (probably with higher voltages), place it on your sdcard, and apply it with:

overclock -sd

It'll probably help stabilize your overclock (though at the expense of battery life)
 
Yes no .odex I installed BackupAssistanceClient.apk from 2.3.15. I remembered reading somewhere that android-syncservice-app.apk was needed for backup assistant to work. I noticed that my system/app did not have that file, so I copied it from 2.3.15 and installed, now my backup assistant is working. Thanks the ROM is working great!!

Any chance I could get someone to email me or link me to these files. Mine's doing the same as Ted's with just the BackupAssistanceClient.apk...force closes immediately, so I'm thinking I need android-syncservice-app.apk

My google backup didn't work for my phone contacts (I think I turned something off or deleted them at some point), I'm at work, and downloading the entire SBF can't happen here.

Here's some beer.:D

german-beer.jpg
 
I've been having lockup/reboot issues with my current setup (2.3.15 leak, ApeX RC1, then V1 on top without wiping. Looks like I'm going to have to wipe tonight and start over. Would I be better off flashing the SBF or just going back to my fresh 2.3.15 leak? Is the new bootloader/kernal better? (Has no correlation been found between limited overclock-ability and the OTA? I tried the 1.38Ghz .zip that was posted yesterday and my phone went all turtle-y on me.)
 
I completely realize this is not the point of having an AOSP ROM, but has anyone attempted/succeeded in getting the stock Blur "Text Messaging" app to work on ApeX? I suppose I can live with Handcent, but I really miss the stock app. I've tried damn near everything to get it to work. There's something, besides Conversations.apk and Messaging.apk, that it depends on... and I can't for the life of me figure out what that something is.
 
I must have got a top notch X because I am scooting along at 1.3 no issues whatsoever and it feels like it can take even more....

Wonder if I should try it at 1.5?
 
Any chance I could get someone to email me or link me to these files. Mine's doing the same as Ted's with just the BackupAssistanceClient.apk...force closes immediately, so I'm thinking I need android-syncservice-app.apk

My google backup didn't work for my phone contacts (I think I turned something off or deleted them at some point), I'm at work, and downloading the entire SBF can't happen here.

Here's some beer.:D

german-beer.jpg

Ha, thanks for that!

I've updated the 2nd post with Blur restoring instructions, as well as a file that has all the Blur apps I removed in them. You'll find what you're looking for there.

I've been having lockup/reboot issues with my current setup (2.3.15 leak, ApeX RC1, then V1 on top without wiping. Looks like I'm going to have to wipe tonight and start over. Would I be better off flashing the SBF or just going back to my fresh 2.3.15 leak? Is the new bootloader/kernal better? (Has no correlation been found between limited overclock-ability and the OTA? I tried the 1.38Ghz .zip that was posted yesterday and my phone went all turtle-y on me.)

I'm not sure if there is a correlation, but if you're going to start with a clean slate, doesn't hurt to get the newest kernel/radio. You may want to just turn off overclocking or use a modified setscaling.sh file though first, before you try wiping (you may be disappointed if your phone doesn't clock any higher!)

I completely realize this is not the point of having an AOSP ROM, but has anyone attempted/succeeded in getting the stock Blur "Text Messaging" app to work on ApeX? I suppose I can live with Handcent, but I really miss the stock app. I've tried damn near everything to get it to work. There's something, besides Conversations.apk and Messaging.apk, that it depends on... and I can't for the life of me figure out what that something is.

I'm not exactly sure either...have you tried restoring BlurSNMessaging.apk?

I must have got a top notch X because I am scooting along at 1.3 no issues whatsoever and it feels like it can take even more....

Wonder if I should try it at 1.5?

Just be sure to turn off auto overclocking before you try it!
 
ok so i did overclock -oc and it gave me what you said in the second post, the various levels , but what i want to know is how these guys are getting this crazy benchmark level, i got 1500 but i see some people are at like 1700 and such, also what do the numbers mean, sorry if i seam dumb i trying to learn is all
 
Ok.... Using the .zip in post #2 I am able to install and use NewsWidget.apk (it would not even install from the 2.2 .rar files)...

Now it's there as an app and I can open the app and view news but it won't let me add the widget... Any ideas???
 
Back
Top Bottom