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

With OC I was getting 7-8 random reboots a day

With it turned off I am getting 3-4

That is the ONLY thing I do not like about my DX, it is very frustrating.
 
wow 3-4? My very first X did that. I called in and got a replacement. Since then(around the first of august) I haven't have any. Atleast none that I didn't cause myself! :D
 
how is it unacceptable? i only get it if i'm doing too much stuff. like opening and closing several apps within a very short amount of time. it reboots in well under a minute so i doesn't bother me too much. certainly not enough to go back to stock.
 
I'm not sure, I just turned OC off a couple days ago. I had been trying to tweak it to get it stable for a while before I just gave up. I am going to probably try Rubix or a different blurless ROM in the next couple of days, if that doesn't work I'll be trying to get a replacement. Any reboots are unacceptable to me too, which is why I gave up on OC'ing hoping that would eliminate them.
 
how is it unacceptable? i only get it if i'm doing too much stuff. like opening and closing several apps within a very short amount of time. it reboots in well under a minute so i doesn't bother me too much. certainly not enough to go back to stock.

But sometimes mine reboots when I am not running anything or even touching it. I just look at it and see the boot animation. Sometimes it restarts when I am doing things, but not always.

Any reboots are unacceptable to me. The only time my phone should power off or reboot at all is if I reboot it into recovery to install something.
 
But sometimes mine reboots when I am not running anything or even touching it. I just look at it and see the boot animation. Sometimes it restarts when I am doing things, but not always.

Any reboots are unacceptable to me. The only time my phone should power off or reboot at all is if I reboot it into recovery to install something.

+1

All I was doing was trying to send an email from the gmail app. It seems truly random.
 
I don't know what it is about ApeX. Really stunning ROM but the reboots are much more frequent than any other. I had it reboot twice whilst using nav. I had to pull over and restore fission.
 
He's not the only one, and mine does it completely stock so its not just caused by a bad app unless its one of the bloatware apps that everyone has/had. At 50 mb and under I can barely use my phone because it lags so bad, don't need to measure anything when its so noticeable. My phone slows down at 90 mb, then it gets even slower at 70 mb, and once it gets to 50 its basically useless

Well its not the lack of memory causing it. Other wise EVERYONE would have this issue as 50 seems to be the default for the OS. It's probably that F'ing CityId we can't uninstall :D Anyways think about it if it was truely a lack of memory problem these boards would be full of complaints about it and it would do it on all phones.

The way the OS works is it would free the memory from old apps if it needed it and since it doesn't do that it has to be something else. Have you ever checked you CPU usage when this happens? Have you gone through your system monitor looking for apps that are using large amounts of CPU? I have an app called SeeCPU that lets you monitor cpu on the notification bar. Usually when my phone starts acting up and going slow the CPU is pegged

I ran with Autokiller for three days and the only difference was I got to see a message telling about all the free RAM I had. there was absolutly no difference between 150 megs free and 50 free on my phone. But I'm not runnig stock or any bloatware either.

In stead of letting AutoKiller kill app next time why don't you kill them one at a time yourself and see when it improves? And then the next time start with the one where it improved.
 
Well its not the lack of memory causing it. Other wise EVERYONE would have this issue as 50 seems to be the default for the OS. It's probably that F'ing CityId we can't uninstall :D Anyways think about it if it was truely a lack of memory problem these boards would be full of complaints about it and it would do it on all phones.

The way the OS works is it would free the memory from old apps if it needed it and since it doesn't do that it has to be something else. Have you ever checked you CPU usage when this happens? Have you gone through your system monitor looking for apps that are using large amounts of CPU? I have an app called SeeCPU that lets you monitor cpu on the notification bar. Usually when my phone starts acting up and going slow the CPU is pegged

I ran with Autokiller for three days and the only difference was I got to see a message telling about all the free RAM I had. there was absolutly no difference between 150 megs free and 50 free on my phone. But I'm not runnig stock or any bloatware either.

In stead of letting AutoKiller kill app next time why don't you kill them one at a time yourself and see when it improves? And then the next time start with the one where it improved.
Tried that, no matter what I close its still sow until I reach 90 mbs free. All that was using CPU would be the stock OS and the last app I was using (not the same app every time) if its bloatware everyone would have the problem also. I think its just certain phones, some had the camera pixel problem that was OS related, some have phones that reboot often, there's the 3g problem some have. I have none of those problems at all, or any other problems besides the lag, that's just another one of the problems that may be caused by the OS that only some people experience. A lot of people here tend to say that certain problems don't exist simply because their phone doesn't have that particular problem, but every phone is different
 
Tried that, no matter what I close its still sow until I reach 90 mbs free. All that was using CPU would be the stock OS and the last app I was using (not the same app every time) if its bloatware everyone would have the problem also. I think its just certain phones, some had the camera pixel problem that was OS related, some have phones that reboot often, there's the 3g problem some have. I have none of those problems at all, or any other problems besides the lag, that's just another one of the problems that may be caused by the OS that only some people experience. A lot of people here tend to say that certain problems don't exist simply because their phone doesn't have that particular problem, but every phone is different

I'm not saying it doesn' happen to you I'm just saying its not due to a lack of free memory. But I don't really see any harm in using AutoKiller either (unlike a takskiller) so if it helps you cool but recommending it just because you think freeing memory helps your phone is wrong (I know you aren't doing that I'm just saying others do)

If my phone was doing hat your is and I couldn't figure out why I'd return it for a replacement, but that's just me. :D
 
Has anyone used the Navigation and had repeated reboots? I installed 1.0 aboout 2 days ago and then installed google maps and used the navigation and it would reboot every 2 minutes or so. I wasnt running a theme or have a ton of apps installed or restore anything. Can anyone else try this and report back? Thanks

Well I was running this ROM just fine at the default OC speed....then I decided to play Angry Birds. My phone now reboots every time I play the game. Anyone else with this problem?

Side note: If I turn off OC then I get zero reboots. :(

I glanced through the posts to see if someone has already posted confirmation on this, so i apologize if i missed previous posts that may already address this. I didn't find a lot of detailed info, but I did see a couple short posts suggesting to turn off overcloking, but that's no fun is it? :D

When i first flashed Apex, I was having issues with lots of freezing and random reboots as well. Specifically, Angry Birds would run for about 3 minutes or so and then freeze. I'd have to do a battery pull in order to reboot. Also, google maps/nav would run for about 3-5 minutes and then reboot. Both of these issues (and a couple others) were very consistant, yeilding the same result every time.

Turning off overclock does, indeed, fix the problem but i couldn't live without the snappy speeds. It's a pretty easy fix...for me at least. Every phone varies a bit, but i am now getting fantastic results by using jRummy's overclock app. If you haven't already, perhaps you may want to try:


- As has been posted, turn off overclocking using the Terminal Emulator:
su
overclock -off

- Download and install "Quadrant" from the market. It's a great benchmark utility that will help you compare the results from different overclock settings.

- Download and install Droid X/2 Overclock, by jRummy16, from the market (more info Droid X/2 Overclock App - Easy & Noob friendly ;) - Droid Forum - Verizon Droid & the Motorola Droid Forum)

- Using Droid X/2 Overclock, experiment with various settings to see what works for you. The tweaks take affect immediately so you don't have to reboot to see the changes. In fact, when you reboot it will restore the default frequency settings. Do NOT use the option, "set frequencies at boot" until you have tested it. Basically, you can change the settings in the app, then just go about your business (open some games, check email, etc.).

Interestingly, Angry Birds has become the perfect test app for me. I change the settings in Droid X/2 Overclock, then i launch Angry Birds. If Angry Birds does not freeze after about 10 minutes, i know that the overclock setting will work (including navigation, maps, etc.). After testing, the best settings for me are:

- Set Scaling Frequencies>Low Voltage> 1.3GHz, 1.0GHz, 900MHz, 400MHz.
- CPU Frequency Scaling> Max: 1300MHz, Min: 900MHz.
- Governor> onDemand (default)

For me, the result is deliciously smooth and snappy. :rolleyes:

*NOTE*: Be sure to test out your settings for a while before doing a "set frequencies at boot." After rebooting, the "CPU Frequency Scaling" min setting is set to 400MHz by default. i usually bump it to 1000MHz.

Shablam! No freezes and no random reboots and a great rom! It works like a charm for me. Hope this helps. :o
 
This is my very first ROM and i have a few questions. First off i installed the ROM from ROM Manager. Everything went smooth with the install i was just wondering how current/up to date ROM Manager is and if i should continue to use ROM Manager to do my installs with themes/roms? Second i lost all my FB contacts and my photos wont show up next to the names and if a quick fix could solve this?

Ive had this running an hour so far and like it a lot. I still have a lot of exploring, customizing etc. to do. Thanks in advance for the help!
 
I use rom manager not just for installs of themes and roms, but also to do nandroid backups and manage those backups. its kept pretty up to date, but there are devs that don't post their stuff there, TBH(tranquility) and Team DeFuse(fission) don't post their stuff in rom manager.
 
This is my very first ROM and i have a few questions. First off i installed the ROM from ROM Manager. Everything went smooth with the install i was just wondering how current/up to date ROM Manager is and if i should continue to use ROM Manager to do my installs with themes/roms? Second i lost all my FB contacts and my photos wont show up next to the names and if a quick fix could solve this?

Ive had this running an hour so far and like it a lot. I still have a lot of exploring, customizing etc. to do. Thanks in advance for the help!

as far as ROM Manager it can be used for some ROMS and not for others ...reason i say this is because for one i have tried to install a rom through rom manager and have it not apply then go through bootstrap into recovery and manually install and the rom would apply ....second some roms require you to go through bootstrap into recovery simply due to the fact that they have much more intensive instructions to install them and third ...personally i just prefer manual installation but thats just me .....about your pics not syncing with your contacts the only solution i can offer is an app called syncmypix ....it will at least sync your pics that are also contacts from facebook and what not ....then i believe you would have to manually install pics for each other contact that this does not work for
 
Wow I feel like this is a dumb question, but if you turn off the overclock through terminal emulator, you can still use SetCPU or Droid X/2 Overclock apps to change your clock and voltages? Which is the better one? I already have SetCPU and don't want to spend the $1 if that is fine, or is the Droid X/2 OC better?

Also piiman, what is the seeCPU app you are talking about...I looked in the market and couldn't find it.
 
Wow I feel like this is a dumb question, but if you turn off the overclock through terminal emulator, you can still use SetCPU or Droid X/2 Overclock apps to change your clock and voltages? Which is the better one? I already have SetCPU and don't want to spend the $1 if that is fine, or is the Droid X/2 OC better?

Also piiman, what is the seeCPU app you are talking about...I looked in the market and couldn't find it.

set cpu just shows you your numbers on overclocking/underclocking etc. and you can set profiles for them through set cpu. The only ways to change your frequencies and voltages is through root explorer/term emulator or one of the apps like Droid X/2 app, trust me it is well worth the dollar it has many add-ons and nice features and allows you to set overclocking easily
 
Here is a weird thing...SetCPU and Droid X/2 Overclock show I am at 1.4ghz, but system panel only shows 1ghz...I did the following before using Droid X/2 overclock:

Turned off overclock through terminal emulator, installed DX/2 OC, played with low voltage scaling freq. and am at 1.4Ghz. Both DX/2 OC and SetCPU say I'm at 1.4 and running Angry Birds without issues...but System panel only shows 1Ghz.

Am I OC'd?
 
Here is a weird thing...SetCPU and Droid X/2 Overclock show I am at 1.4ghz, but system panel only shows 1ghz...I did the following before using Droid X/2 overclock:

Turned off overclock through terminal emulator, installed DX/2 OC, played with low voltage scaling freq. and am at 1.4Ghz. Both DX/2 OC and SetCPU say I'm at 1.4 and running Angry Birds without issues...but System panel only shows 1Ghz.

Am I OC'd?

You know, i have never checked system panel until you mentioned it. When i checked, my System Panel also says 1000MHz, but i am OC'd at 1300MHz (min 900MHz). I would also be curious to know why system panel gives a different read out. I am going to try asking the System Panel dev and see if the issue might be on their end. One thing is for sure...i can definately see and feel the difference when i adjust the OC settings (it's not just psychological). When i go back to stock settings it's a night and day difference. If i were to guess, i would say that we ARE OC'd and system panel just isn't recognizing it?

I was a big Windows Mobile guy until getting my DX. Though i'm a tech guy, i am still learning the ring as to how to truly, manhandle Android. Perhaps some of the pros out there can shed some light on it?
 
You know, i have never checked system panel until you mentioned it. When i checked, my System Panel also says 1000MHz, but i am OC'd at 1300MHz (min 900MHz). I would also be curious to know why system panel gives a different read out. I am going to try asking the System Panel dev and see if the issue might be on their end. One thing is for sure...i can definately see and feel the difference when i adjust the OC settings (it's not just psychological). When i go back to stock settings it's a night and day difference. If i were to guess, i would say that we ARE OC'd and system panel just isn't recognizing it?

I was a big Windows Mobile guy until getting my DX. Though i'm a tech guy, i am still learning the ring as to how to truly, manhandle Android. Perhaps some of the pros out there can shed some light on it?

With system panel mine shows a CPU speed of 1.35 GHz. Press the menu button > Dev Info, then scroll down to CPU Information.
 
With system panel mine shows a CPU speed of 1.35 GHz. Press the menu button > Dev Info, then scroll down to CPU Information.

Thanks! When i look at the dev info it is correct, like you said. The "System Clock" (with the progress bar graphic) is what's saying 1000MHz. My dev info shows the accurate max and min settings though.

Thanks for the help!
 
Ive had it installed for 24hrs and enjoying it! The only changes i made was the black bar mod which im addicted to. What Themes are you guys running with this?
 
Am I the only one dying for an update to this ROM? Don't know how to make it much better, but....would be nice. Thanks Fabulous for the ROM. I am also anxiously waiting for the LPP overhaul as well. :)
 
Back
Top Bottom