Database Develop

Tasker setting may uncover a Filesystem bug -testers needed

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
Code:
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"

I guess everyone must think that i indeed did find a bug in the filesystem because not one person has come forward to try this out. If I am wrong at least you have yourself a very nice way to track you battery usage.

I read over your task and don't think I missed anything unusual (ie. weird infinite loop condition that would make it constantly write to the file).
I'm not about to try it, of course, given what you have experienced. You might try the limit repeats or cooldown period settings for the profile in case that really is the issue.
I can tell you I've been using the file writing actions for a clipboard history task I wrote and have not had your issue, even when I screwed up a condition and it was infinitely writing my clipboard contents to a file for a couple of minutes straight.
I'm running an i896 captivate with a js3 rom fwiw. Hope you get it figured out.
Sent from my SAMSUNG-SGH-I897 using XDA App

tiuk said:
I read over your task and don't think I missed anything unusual (ie. weird infinite loop condition that would make it constantly write to the file).
I'm not about to try it, of course, given what you have experienced. You might try the limit repeats or cooldown period settings for the profile in case that really is the issue.
I can tell you I've been using the file writing actions for a clipboard history task I wrote and have not had your issue, even when I screwed up a condition and it was infinitely writing my clipboard contents to a file for a couple of minutes straight.
I'm running an i896 captivate with a js3 rom fwiw. Hope you get it figured out.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I am not attempting to recreate at this time. I will be when I have a replacement phone. If this is indeed a fs bug i can imagine anyone who does not want their phone aymore could use this setting and go into infinite loop and get a replacement. The does not require root and can be used on any firmware. Samsung would have to react.

so after running the new phone for a week i got the boot loops again today at 11:08am
i am trying to see if it is battery related as I DID NOT have the tasker setting in place.
here is the log if anyone wants to try and help solve this. i have other batteries i will be trying this week. (everyday until i fix it) the problem is though that if the filesystem is damaged than testing on this phone is useless.
http://dl.dropbox.com/u/17699865/android_report1298308267139.zip

I solved the bug bug cant fix it.
follow the link to my report.
anyone able to reproduce?
i have been able to send the message to myself but it always arrives in 2 part.
goo.gl/wCrlp

[Problem] My phone has "remembering" problems

I suspect my issue is a problem of the phone not remembering some settings. I am using the latest CM7 nightly as of this morning (155), but this has been an issue for quite a while.
If I am having only one problem, it manifests itself in a several ways...
1) My facebook contacts won't STAY in sync. Every time i turn my phone on, I have to re-sync my facebook contacts if I want to see them.
2) The first time I send a text from outside the SMS program (sending a text via Vlingo for example) after a reboot, the system asks me which SMS program I want to use. It remembers that choice until the next reboot - when I have to chose again.
3) The first time I tap an internet shortcut, the system asks me which browser I want to use. It remembers that choice until the next reboot - when I have to chose again.
4) I have to re-sign into Twitter the first time I open it after every reboot.
There are other similar issues - none major, but annoying nonetheless.
What am I missing? I've gone through all my settings and can't find one for "Remember all my $hit" . I've run the phone with sync on, and I've run it with sync off - still the same results.
Any help would be appreciated.

I had something similar happen at one point about 6 months ago. I ended up (after much trial & error) just reflashing the whole danged thing....my sd card, recovery, and rom. No issues since.
Not sure what happened, although that was the time I was really flashing lots of different ROMs.

cmason1015 said:
I had something similar happen at one point about 6 months ago. I ended up (after much trial & error) just reflashing the whole danged thing....my sd card, recovery, and rom. No issues since.
Not sure what happened, although that was the time I was really flashing lots of different ROMs.
Click to expand...
Click to collapse
I tried this yesteday morning. As you suggested, I formatted everything including the memory card. Twenty-four plus hours later, everything is working fine.
Thanks for the tip.

[Q] Sprint Marquee reset during call, errlog attached

My sprint Marquee started to develop an annoying problem: reset during call. I cannot post link yet, but there are several other Marquee users reported same problem in androidcentral forum.
It's not a complete reset, but the screen will turn blank and not responsive, only the four button will flash the led. After 1 minute it will come back.
I knew I can try to restore to factory default, but after a little search, I saw many android phone user met this problem, and many of them were using factory default settings. So I decided to uninstall apps and install an error log app for next reset.
Yesterday there was another reset, and I saved the error log immediately after the reset. But I'm not sure if the error caused the reset can be recorded.
Hear are the error log, anybody can have a look at it and get some ideas about the problem?
For the apps I installed in my Sprint marquee:
It was rooted. No task killer. Used to freeze sprint bloatware with Ti backup but I uninstalled Ti backup earlier.
Was using Go launcher, then zeam launcher.
Was using dialer one, then back to stock dialer. the call log was limited to 7 days. -- I was guessing it could be the call log too long.
For the error log files:
alogcat.2012-01-26-18-06-31-error.txt
this one was generated right after the reset, but I didn't know how to turn on time display at that time.
The reset occurred on about 18:06.
alogcat.2012-01-27-00-00-52-warning.txt
this one was generated later at night with time displayed. It's a log on warning level.
alogcat.2012-01-27-00-03-07-info.txt
this one was generated later at night with time displayed. It's a log on info level.

Issues with s advance, internal storage and more

Guys I have some issues with my s advance. They all started when I flashed cm10.2, but I also encountered them in cm11, and now in stock jb (now my phone is not even rooted).
The main issue is the internal storage space (ROM memory) which after a period of time gets full although I don't a lot of apps. The first time when I had the problem it appeared after about a month of using cm10.2, then even sooner in cm11, then after a couple of days in stock jb, and today after a couple of hours (about 4). The only solution I managed to find till now is flashing a new rom or doing a factory reset, but I don't want to do this every couple of days. Today it happened even though I had only one app instaled besides the ones that come with the stock jb. First time I thought that it had to do with cyanogenmod os, then with the fact that my phone was rooted and I had a lot of apps instaled, some of them not from google play, but since I reflashed jb I didn't even root the phone. So if you have any suggestions about this problem please let me know because I don't know what to do.
The second issue has the same story behind it, meaning that it appeared in cm10.2 and I don't know what it causes it and how to solve it. So the phone restarts itself usually when is not used for a period of time. For example in the morning after I wake up, but during may night shifts at work (where I dont't sleep) it nevere restarted. Also during the day if I don't use the phone for a period of time I found the phone restarted. The frequencyof this problem is variable, sometimes a couple of time in a day, sometime one time in a couple of days.
I mention that at home my phone is always connected to the internet via my wireless connection. I don't know if this has something to do with it, but when I searched the web for my problems some users where suggesting that the phone stores some data over the wifi connection. Also some where suggesting to install es file explore and find the folder or folders that occupies the space but es file explorer does not show how the internal storage is occupied by files and folders. There weren't a lot of result when I searched for my issue but there were complains of similar problems with different models of phones, most of all galaxy s2 and some htc.

slider2 said:
Guys I have some issues with my s advance. They all started when I flashed cm10.2, but I also encountered them in cm11, and now in stock jb (now my phone is not even rooted).
The main issue is the internal storage space (ROM memory) which after a period of time gets full although I don't a lot of apps. The first time when I had the problem it appeared after about a month of using cm10.2, then even sooner in cm11, then after a couple of days in stock jb, and today after a couple of hours (about 4). The only solution I managed to find till now is flashing a new rom or doing a factory reset, but I don't want to do this every couple of days. Today it happened even though I had only one app instaled besides the ones that come with the stock jb. First time I thought that it had to do with cyanogenmod os, then with the fact that my phone was rooted and I had a lot of apps instaled, some of them not from google play, but since I reflashed jb I didn't even root the phone. So if you have any suggestions about this problem please let me know because I don't know what to do.
The second issue has the same story behind it, meaning that it appeared in cm10.2 and I don't know what it causes it and how to solve it. So the phone restarts itself usually when is not used for a period of time. For example in the morning after I wake up, but during may night shifts at work (where I dont't sleep) it nevere restarted. Also during the day if I don't use the phone for a period of time I found the phone restarted. The frequencyof this problem is variable, sometimes a couple of time in a day, sometime one time in a couple of days.
I mention that at home my phone is always connected to the internet via my wireless connection. I don't know if this has something to do with it, but when I searched the web for my problems some users where suggesting that the phone stores some data over the wifi connection. Also some where suggesting to install es file explore and find the folder or folders that occupies the space but es file explorer does not show how the internal storage is occupied by files and folders. There weren't a lot of result when I searched for my issue but there were complains of similar problems with different models of phones, most of all galaxy s2 and some htc.
Click to expand...
Click to collapse
You should do factory reset when you change ROM. On CM10.2 there might be still some problems - yes reboots happen some times. So I suggest you to use CM10.1 or CM11.
You can use this to see what uses most of the space on internal memory. With space you get how much space is occupied in folder.
http://forum.xda-developers.com/showthread.php?t=2105707

hmmm
So you are saying that I should flash a new rom for example cm11 than I should do a factory reset from recovery? It may be possible that I had already done this but I will try i again because I got nothing to lose.

slider2 said:
So you are saying that I should flash a new rom for example cm11 than I should do a factory reset from recovery? It may be possible that I had already done this but I will try i again because I got nothing to lose.
Click to expand...
Click to collapse
And to see what do you have on internal memory manualy.

Text messages take a really long time to send

Hi. I have a dual SIM P9 on the latest software (EVA-L19C432B386).
I just got the phone around 2 weeks ago, and I did a full update and full wipe/hard reset when I got it. I finished setting up all my apps and settings and everything has been really great and I really like the phone.
Until two nights ago, I noticed that when I send texts, it would just say "Sending..." under the message bubble for 15 minutes or more (sometimes upto an hour). It's the same with both SIMs on two different networks. Calls would come in just fine, and I could still receive texts, so it couldn't be a signal issue (Signal was 4-5 bars on both networks)
I tried swapping out the SIMs, putting my sim on another phone, and on the same location, texts send really quick. I also tried putting other SIMs on my P9 and the same thing happens, the text messages take forever to send. Sometimes it works well, I could easily send texts on both networks. But after a few minutes it starts acting up again and it just says sending for the longest time.
I've tried clearing the data of messages app (it didnt delete the text messages), I also manually deleted all texts, I tried using another SMS app, and I also tried clearing cache and dalvik data, to no avail.
Any thoughts?

UPDATE:
Hard reset fixed the problem. I was almost sure it would fix the problem but i was hesitant since I didn't want to have to set up all my stuff over again.
I did a nandroid backup before doing a hard reset. Restoring the backup also restores the problem.
So hard reset fixed it, but I probably would never know what caused it. I didn't install anything new on the day it happened, and I havent installed any apps I havent tried before. To think it's only been 2 weeks since my last reset. I hope I wouldnt have to do another hard reset 2 weeks from now.
ANOTHER UPDATE 7/14/17
It's back again. Texts take a really long time to send. After I've set up all my stuff, apps, accounts, etc, it was all well. Less than a week later its back at it again. Didn't install anything new. It just started acting up on its own. Not sure how to solve this, or where to look first.