[ROM] ApeX V1.4.1 for Droid X & Droid 2 - Refinement and Ease of Use (2/22/2011)

[brettofamerica]

Yes I did wipe before the install after having to flash back to stock...

Sent from my DROID2 using DroidForums App

 

[bobstro]

so did you do a full wipe and install 1.4.1?
if not then try it [...]

In my case, I installed 1.4.1 as follows:

1. Boot into Clockwork recovery
2. Wipe Dalvik Cache
3. Wipe battery stats
4. Wipe system cache
5. Factory reset
6. Install 1.4.1 ROM
7. Reboot. Didn't do much with system at this point, but it was working with no problems.
8. Restored some apps from Titanium Backup

At this point, I'd reboot and get the "FC or Wait" message. No matter which option I selected, I'd only get the black screen. The only function was the power menu. To recover, I did an SBF back to stock.

I'm happy to chalk this up to something being restored causing problems and call it my bad, except:

1. I did a factory reset (power+X->search), and still couldn't get 1.4.1 to boot after this happened. Whatever "bad" thing the restore from TB did, it was clearly something another app could do at some point. I find this a real threat to stability.

2. Doing the exact same procedure on 1.4 causes no problems whatsoever. It has been remarkably stable. I suspect there's a difference between 1.4 and 1.4.1 that is causing unexpected issues for some of us, so I'm hoping this explanation will help in troubleshooting.

I love 1.4. My only problems on 1.4 are very minor (notification bubble, no charge LED, persistent sync icon on right). If there's anything I can do to provide more diagnostic info, please let me know.

when i did get the system force close i just hold power and reboot and it runs fine

I always wound up with a black screen. I was hoping to get into Clockwork recovery and try the Fix Permissions option, but I needed to get a running system to run recovery. Is there a way to force Clockwork to come up when I first power on?

- Bob

 

[brettofamerica]

so did you do a full wipe and install 1.4.1?
if not then try it [...]

In my case, I installed 1.4.1 as follows:

1. Boot into Clockwork recovery
2. Wipe Dalvik Cache
3. Wipe battery stats
4. Wipe system cache
5. Factory reset
6. Install 1.4.1 ROM
7. Reboot. Didn't do much with system at this point, but it was working with no problems.
8. Restored some apps from Titanium Backup

At this point, I'd reboot and get the "FC or Wait" message. No matter which option I selected, I'd only get the black screen. The only function was the power menu. To recover, I did an SBF back to stock.

I'm happy to chalk this up to something being restored causing problems and call it my bad, except:

1. I did a factory reset (power+X->search), and still couldn't get 1.4.1 to boot after this happened. Whatever "bad" thing the restore from TB did, it was clearly something another app could do at some point. I find this a real threat to stability.

2. Doing the exact same procedure on 1.4 causes no problems whatsoever. It has been remarkably stable. I suspect there's a difference between 1.4 and 1.4.1 that is causing unexpected issues for some of us, so I'm hoping this explanation will help in troubleshooting.

I love 1.4. My only problems on 1.4 are very minor (notification bubble, no charge LED, persistent sync icon on right). If there's anything I can do to provide more diagnostic info, please let me know.

when i did get the system force close i just hold power and reboot and it runs fine

I always wound up with a black screen. I was hoping to get into Clockwork recovery and try the Fix Permissions option, but I needed to get a running system to run recovery. Is there a way to force Clockwork to come up when I first power on?

- Bob

Yeah were on the same boat because everything except for restoring with titanium backup is what I did. I even have the constant sync icon in the notification bar on 1.4.1

Sent from my DROID2 using DroidForums App

 

[Fabolous]

Hey guys, what I did was change the way my startup script runs in 1.4.1, from just being applied using the /system/etc/install-recovery.sh file to being a series of scripts found in /system/etc/init.d/

Now, from my testing on the Droid X, this prevented the system FC after installing themes/restoring nandroids, which was caused by the original install-recovery.sh script.

But unless I'm reading it wrong, it still does this on the Droid 2? On 1.4.1? If so, I'm puzzled since it doesn't seem to do this for the Droid X, and I don't have a Droid 2 to troubleshoot with.

The workaround is just to hold down the power button to get the reboot menu. It will work on the 2nd boot (no need to reflash the ROM or go into Clockwork).

Please let me know! Thanks.

 

[RevNumbers]

Hey guys, what I did was change the way my startup script runs in 1.4.1, from just being applied using the /system/etc/install-recovery.sh file to being a series of scripts found in /system/etc/init.d/

Now, from my testing on the Droid X, this prevented the system FC after installing themes/restoring nandroids, which was caused by the original install-recovery.sh script.

But unless I'm reading it wrong, it still does this on the Droid 2? On 1.4.1? If so, I'm puzzled since it doesn't seem to do this for the Droid X, and I don't have a Droid 2 to troubleshoot with.

The workaround is just to hold down the power button to get the reboot menu. It will work on the 2nd boot (no need to reflash the ROM or go into Clockwork).

Please let me know! Thanks.

I've got a D2 and was having this issue, but for me just rebooting didn't work, I would up having to SBF to get things going, tried 1.4.1 again with the same results... so I've gone back to 1.4.0 and when i do get the system FC problem the reboot fixes it

 

[brettofamerica]

Hey guys, what I did was change the way my startup script runs in 1.4.1, from just being applied using the /system/etc/install-recovery.sh file to being a series of scripts found in /system/etc/init.d/

Now, from my testing on the Droid X, this prevented the system FC after installing themes/restoring nandroids, which was caused by the original install-recovery.sh script.

But unless I'm reading it wrong, it still does this on the Droid 2? On 1.4.1? If so, I'm puzzled since it doesn't seem to do this for the Droid X, and I don't have a Droid 2 to troubleshoot with.

The workaround is just to hold down the power button to get the reboot menu. It will work on the 2nd boot (no need to reflash the ROM or go into Clockwork).

Please let me know! Thanks.

I've got a D2 and was having this issue, but for me just rebooting didn't work, I would up having to SBF to get things going, tried 1.4.1 again with the same results... so I've gone back to 1.4.0 and when i do get the system FC problem the reboot fixes it

Same here. I tried rebooting several times and so I just went back to 1.4.0. Maybe if it isn't too much work when you make future roms, make the droid 2 with the classic install-recovery.sh instead of the new series of scripts.

Maybe the Droid 2 doesn't like playing nice with the series of scripts...

 

[ath2424]

This ROM works great on my D2, love how I can customize the framework

Sent from my DROID2 using DroidForums App

 

[jdog94]

yeah i thought going unthemed was going to work for me but i got the system force close today againso i have tried 141 a couple different way and flashed 3 different times and it always seems to happen at some point............
i never had any problems with 140 so maybe ill go back to 140

other than the system force close 141 is awesome

 

[brettofamerica]

Fab,
How hard would it be to whip up a test version of 1.4.1 with the install-recovery.sh start up script? If it wouldn't be any easier than just replacing the new scripts with the install-recovery.sh one, than forget it, I understand you have a life and don't want to spend all your time on this! But if you could, than we (the ones with the problem droids) could give it a go and let you know if that was the problem or if we still get FCs.

 

[Fabolous]

Perhaps I will just do this...remove the autorun aspect of the startup scripts, and you guys can just initiate them by running something like:

su
startup

?

That's very easy to implement, and I believe should fix all the issues, while allowing you to keep the benefits of the startup script. I will make an experimental version and upload it for you guys to try.

 

[brettofamerica]

Sounds good! Have you ever thought of doing beta versions of your roms so that you can fix all the little glitches left to iron out before release (even though this is the first time I have had really any problem with any of your roms)? I think it would help you out especially since you don't have a D2!

Sent from my DROID2 using DroidForums App

 

[Fabolous]

Yeah, I probably should have more people test the D2 version for me

Can you try this one? Apply some themes or whatever causes the FC and let me know if it's still doing it.

Remember to run the script after your phone is complete finished booting up:

su
startup

Thanks!

http://fabdroid.com/roms/droid2/Fabolous_ApeX_V1_4_2-D2.zip



EDIT: don't be alarmed if your terminal "freezes" for like 30 seconds. I forgot to take out the wait period (which was important when it was being autorun).

 

[jdog94]

ill have to wait till tomorrow eve to try it

 

[Johnly]

Ain't no ROM hold a changed file system like ApEx.........Thanks Fab....I likez runnin the best........effen A.......

 

[randizzard]

Ok I'm curious as to how I can get the no icon theme because that is just sick looking!!

Sent from my DROID2 using DroidForums App