you run updatetb from terminal
dont sure on your other question
all i noticed i lost on 141 flash was launcher pro i had to reinstall it
and all i did was wipe cache
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 V1.4.1 for Droid X & Droid 2 - Refinement and Ease of Use (2/22/2011)
- Thread starter Fabolous
- Start date
dont sure on your other question
all i noticed i lost on 141 flash was launcher pro i had to reinstall it
and all i did was wipe cache
I had this also with other installs. I got into a habit of running fix permissions after an install and then reboot. Seemed to work for me.
deftdrummer
Member
Fab, don't mean to bother with petty stuff but can you please post the original mountain wallpaper that came with the ROM? Another user was also asking about it a little further up. Thanks dude.
miketoasty
Member
Go to wallpaper gallery and its the only wallpaper there.
Sent from my DROID2 using DroidForums App
miketoasty
Member
Well its sad but I'm going to have to stop using this ROM. Got a System Force close while the phone was just idly sitting there. I need a ROM thats going to be 100% stable. Great work anyways Fab as it is still my favorite ROM!
I'm having a variation on this problem after updating to 1.4.1. I did a wipe of cache, factory reset and dalvik cache before flashing 1.4.1. Everything booted fine. After restoring apps using Titanium Backup, I get the FC or Wait option on boot. If I select either option, I get no display. Pressing the power button does give me the reboot/shutdown options, so something's running. There's just nothing on my screen. Can I run fix permissions from there somehow?
Realizing the stuff I restored from TB is likely the culprit, I reset to factory defaults using the power+X->search function, but the phone would still not boot. I got the same FC or Wait screen. I recovered by doing an SBF to restore to stock.
I then (foolishly) repeated the entire process with the same results, just to make sure. I realize it's probably something I've restored with TB that's the root cause of the problem, but the fact that a factory reset doesn't allow me to boot the new ROM after this happens is alarming. I'm on my 2nd SBF now. I'm installing 1.4 until I have more time or get some advice.
1.4 was rock steady, even after restoring the same boatload of stuff using TB, so I'm not sure what the new factor is, but I wanted to make you aware of this in case it bites anybody else.
- Bob
Last edited:
This happens to me once a day. It'll just sit there and go into the boot animation then system force close. Rebooting works though. Just sucks.
brettofamerica
Member
Its great but...
Fab. I love your rom and have been using it since 1.3.1 (although it has only been about 3 months), but I'm quite disappointed. Like stated above, I would get a system force close every time I started my phone if I even changed one setting in the terminal which is quite unfortunate because thats one of the main reasons I use your rom.
But I proceeded to downgrade to 1.4.0 which is AMAZING! dancedroid Its basically the same as 1.4.1 from what I can tell. I would very much appreciate it if you could fix 1.4.1 for the Droid 2!
One last thing, is there anything you could do for the notification bubbles? It is a quirk that rubs me the wrong way because I like to be able to see the icon AND the number of notifications from that icon. I attached a picture of what I'm talking about...
Thanks again Fab, your great!
Fab. I love your rom and have been using it since 1.3.1 (although it has only been about 3 months), but I'm quite disappointed. Like stated above, I would get a system force close every time I started my phone if I even changed one setting in the terminal which is quite unfortunate because thats one of the main reasons I use your rom.
But I proceeded to downgrade to 1.4.0 which is AMAZING! dancedroid Its basically the same as 1.4.1 from what I can tell. I would very much appreciate it if you could fix 1.4.1 for the Droid 2!
One last thing, is there anything you could do for the notification bubbles? It is a quirk that rubs me the wrong way because I like to be able to see the icon AND the number of notifications from that icon. I attached a picture of what I'm talking about...
Thanks again Fab, your great!
brettofamerica
Member
Yeah, its weird because the rom is completely stable but from what I have experienced, if you change the framework or do anything through the terminal, you get a system force close on your next boot. Well at least for the Droid 2. Unfortunately from testing to try and find the cause, the only way to fix the force close is to reflash the rom ontop of the other one so everything is the same but the settings go back to default.
brettofamerica
Member
That's wierd because I know from searching around other people are having this problem and so idk what is different between us that have problems and you guys who don't have problems.
I can tell you that I did an install from 1.3.1 straight to 1.4.1 and when I ran a command in the terminal I got a FC on reboot and then I had to do a fresh install of stock cuz I couldn't get into clockwork recovery. After that fresh install before doing anything else I tested the terminal and upon reboot I got a FC... I hope we can figure this out because its killing me not being on the latest rom even if its basically the same... haha
Sent from my DROID2 using DroidForums App
I can tell you that I did an install from 1.3.1 straight to 1.4.1 and when I ran a command in the terminal I got a FC on reboot and then I had to do a fresh install of stock cuz I couldn't get into clockwork recovery. After that fresh install before doing anything else I tested the terminal and upon reboot I got a FC... I hope we can figure this out because its killing me not being on the latest rom even if its basically the same... haha
Sent from my DROID2 using DroidForums App
so did you do a full wipe and install 1.4.1?
if not then try it
it runs faster than any rom i have ever tried and overclocks faster than any rom i have ever tried
and the only time i have had the problem is after flashing a theme...
when i did get the system force close i just hold power and reboot and it runs fine
if not then try it
it runs faster than any rom i have ever tried and overclocks faster than any rom i have ever tried
and the only time i have had the problem is after flashing a theme...
when i did get the system force close i just hold power and reboot and it runs fine