[Captivate Themes and Apps] PAulyhoffman:
This turns out to be a crash bug in Android see last post

While i was researching ways to maximize the battery life on my captivate I came across a setting in the tasker wiki that would help me log the life of my battery.

I had already set up juice defender and other ways to let tasker turn on and off battery draining settings like GPS and WIFI and thought that this would be a good way to track on a day to day basis how much life i was getting out of each battery.

Here is what i found. The day after i set up the tasker profile i began watching results. Around 11 am the next day my phone began to loop in reboot. it just went right to my bootanimation and then home screen, boot animation, home screen....

I thought nothing of this as i flash roms often and was beta testing some stuff at the time. I proceeded to flash stock ---> flash custom rom. what i i had to repeat this process a few times because it continued to reboot. After a few flashes i became stable. the following day at around 11 am my phone began to boot loop again. this time i flashed stock and left it there only to begin looping again. i turned the phone off for a while and then flashed stock--> custom rom. It looped again.

this time i brought the phone to a device support center and had it replaced.

with the new phone i use no settings or backups from TiBu except for a few apps like handcent, takser, angry birds and a couple other games. at this point i thought that my old phone was just worn out from the many flashes. Two days after getting the new phone and installing all apps (except the few apps like tasker) my phone began to boot loop at 11AM. this time i flashed to stock and it began to boot loop again. I repartition and flashed again and it became stable. Until the next day at 11am when it began to boot loop again.

i returned to the device support center with a stock phone in boot loop.

this time I have not used a setting from tibu backup but have returned all aps to almost the same as before (the best i can by memory)

day one i Ran stockfor a day.

day two i ran the same custom rom/kernel combo.

day 3 i ran everything with the apps set up and used the same battery that was in from the last time it looped.

The only Thing that was the same from both phone that looped what isn't in my newest phone is that tasker setting.

I am almost 99% sure that this setting did something to the file system at low levels which is unrepairable by flashing.

Is this a bug? i do not know, I reproduced it twice but do not think that a device support center will replace a third device for me.

If anyone is/has ran this profile with no problems than I can let this go as unsolvable.

If anyone is willing to test this setting and can reproduce the bug then i think we will have something to take to Samsung regarding a system bug that is unrepairable at user level.

here is the link for the profile

i followed this setup exactly as stated except here Write File: File "Batterlog.txt" i used "BattLog.txt" im not sure if it makes a difference but if you are going to set this up please try it using BattLog.txt

here are the steps

1. Make up a new profile, context: Power: Battery changed, priority normal -> done.
3. Add task Alert: Flash: Text "%BATT % %MEMF", If checked "%BATT !~ %BATTPREV" -> done
4. Add task File: Write File: File "BattLog.txt", Text "%DATE %TIME %BATT", Append checked, If checked "%BATT !~ %BATTPREV" -> done
5. Add task Variable: Variable Set: Name "%BATTPREV", To: "%BATT"