Develop Bugs

[Q] Will no data connection for days wreak havoc for the Epic?

I went to Mexico for a week recently and turned off the data connection on my phone to avoid data fees. I planned to use my phone for GPS and maps since I didn't have Mexico map data for my Garmin. Everything worked fine for about 5 days and then suddenly I started getting FCs on everything and the phone became unusable and eventually required a complete rebuild. I rebuilt using the new EC05 and then loaded Syndicate ROM 1.1.0 and have had no problems since. When I had this issue I was using EB13 with Syndicate ROM 1.0.1 flashed on top of it.
I have no idea what caused this but it was a major pain not having a phone until I returned. Some idea I had were that some application that like to check for piracy couldn't connect to the market and after a few days went haywire. I also think it may have been the ROM but I was using it fine for a couple weeks prior to the trip.
Any ideas on what went wrong for me?

How were you using the navigation system without data? Unless you have a program that already includes all the maps stored on the phone you were probably still using data.
And, no, I don't believe shutting off the data caused your force close issues.

You stated you were using SRF 1.0.1, and as that rom has journaling disabled, it is very likely that an improper shutdown/reboot or a problem with an app may have caused data corruption, which will cause all those FC's.

socos25 said:
How were you using the navigation system without data? Unless you have a program that already includes all the maps stored on the phone you were probably still using data.
And, no, I don't believe shutting off the data caused your force close issues.
Click to expand...
Click to collapse
I was using Gaia GPS which allows you to store maps on the phone and I downloaded maps for the entire area before leaving. That part actually worked very well while it was working.

Dude like the mexican water never let your phone drink mexican data.... you'll only get force closes and will need to do a ##786# and enter msl code and reformat your phone to like new condition.
Also you use ext4 which only lasts for a few days. You need to reset your phone. Only use ext4r with jourling on or stop using custom roms as they all have issues like ext4 bug. I using stock and not one issue. Can't say that with custom roms.
Sent from my SPH-D700 using XDA Premium App

Koadic said:
You stated you were using SRF 1.0.1, and as that rom has journaling disabled, it is very likely that an improper shutdown/reboot or a problem with an app may have caused data corruption, which will cause all those FC's.
Click to expand...
Click to collapse
Interesting insight. I'm supposing journaling was disabled to increase performance/disk space usage? Before this happened I turned my phone off and on to conserve battery life, then finally when turning it back on it went berserk and after that it was toast until I could Odin it. I didn't notice a bad shutdown and I never had to remove the battery or anything unusual to restart the phone. If this happens again is there a way to get the logs off the phone for some analysis? I use CatLog to find issues now but that assumes the phone is mostly operational. If I have a bad application that is causing this I'd like to contact the author or remove it. I've since discovered CWM backup/restore and I hope that will help me if it happens again. FYI, I'm a little new to Android and I'm sure that shows in my reply but I've been using Linux for 13 years now and am a software developer. This is my first Android phone.

epicblows said:
Dude like the mexican water never let your phone drink mexican data.... you'll only get force closes and will need to do a ##786# and enter msl code and reformat your phone to like new condition.
Also you use ext4 which only lasts for a few days. You need to reset your phone. Only use ext4r with jourling on or stop using custom roms as they all have issues like ext4 bug. I using stock and not one issue. Can't say that with custom roms.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
"Also you use ext4 which only lasts for a few days."
Is that for real? I could see a catastrophic shutdown corrupting the filesystem but your response makes it sound like it could fail at any time with no cause. That is very consistent with what I experienced though.
I like the Syndicate ROM and would like to continue using it so I'll look at turning the journaling on like you mentioned. But in the end I came from Windows Mobile to Android for stability in my phone. Using custom ROMs and tweaking my phone might seem dumb considering stability is my highest priority but it's in my nature to take things apart and tinker with them. In the end I will revert to stock ROM if that is the only long term stability I can find.

I really don't know what epicblows is talking about. Journaling, like the name implies, creates a journal of the changes you make before actually executing the action. Say for example, you are playing a game straight through and get to level 6, then suddenly you drop your phone and the battery pops out. With journaling on, you can likely restart your phone and get back to level 6. No journaling, you will likely be right back to level 1. Journaling slightly slows the system because it has to write information to the journal before it executes the command. I have not heard anything about a bug inherent to ext4. There are plenty of stable roms here such as Bonsai, Shinigami and UrbanLegend. I have used those myself and had great stability. They are really stripped down roms with most of the mods done under the hood to improve stability and performance. I have used other roms but prefer these for their barebone approach.

epicblows said:
Also you use ext4 which only lasts for a few days.
Click to expand...
Click to collapse
I call BS.
I ran EXT2 for MONTHS with no issues on both my Moments, and have run EXT4 on my Epic since it was first released.
I have done battery pulls several times, and for the most part, have not run into any issues I could trace back to EXT4.
If your EXT4 build is not lasting more than a couple days, YOU must be doing something wrong to cause the issues, IMO, not EXT4 itself.

I also like the stripped down nature of the ROMs found here. I don't particularly care for NASCAR, I have my own channels for accessing football information, and so on. After using Syndicate ROM I would only reluctantly go back to stock as a last resort. Based on my problem do you think the CWM backup/restore would fix that problem that I described? If I can fix my phone on the road that would be good enough disaster recovery for me.

DCRocks said:
I call BS.
I ran EXT2 for MONTHS with no issues on both my Moments, and have run EXT4 on my Epic since it was first released.
I have done battery pulls several times, and for the most part, have not run into any issues I could trace back to EXT4.
If your EXT4 build is not lasting more than a couple days, YOU must be doing something wrong to cause the issues, IMO, not EXT4 itself.
Click to expand...
Click to collapse
I agree about the nature of software errors. As a junior developer 15 years ago I would always find problems with the compiler I was using, or the OS, etc. After some time I came to realize that my problems were always related to some oversight/misunderstanding on my part. Since Gingerbread is set to use ext4 I was having a hard time accepting that it is fundamentally flawed, but then again I'm new to the Android world, and ext4 is new for Android. It is good to know there are people using ext4 for months with no problems.

If it ever happens again I would recomend just applying your clockwork /data backup. This will usually fix your force closes and other problems from data corruption due to improper shutdown. That's the bad part of running with journaling disabled. It is quick to restore a nandroid backup though and will save you the hassel of a full reformat.
Sent from my SPH-D700 using XDA App

DCRocks said:
I call BS.
I ran EXT2 for MONTHS with no issues on both my Moments, and have run EXT4 on my Epic since it was first released.
I have done battery pulls several times, and for the most part, have not run into any issues I could trace back to EXT4.
If your EXT4 build is not lasting more than a couple days, YOU must be doing something wrong to cause the issues, IMO, not EXT4 itself.
Click to expand...
Click to collapse
Well bs it is not. Ext4 is flawed with out journling on. I would say it is worth any performance hit to not lose your mind about force close. I use stock and not a single issue
Sent from my SPH-D700 using XDA Premium App

In approximately 30 seconds, a spammer will post "fifth post" below me.

k0nane said:
In approximately 30 seconds, a spammer will post "fifth post" below me.
Click to expand...
Click to collapse
Mandro1d said:
fifth post
Click to expand...
Click to collapse
I'll be here all week, folks.

brian0wens said:
...Since Gingerbread is set to use ext4 I was having a hard time accepting that it is fundamentally flawed, but then again I'm new to the Android world, and ext4 is new for Android. It is good to know there are people using ext4 for months with no problems.
Click to expand...
Click to collapse
Ext4 itself isn't really the problem, it is the fact that journaling was disabled added to the fact that there was obviously some event that caused the data corruption (whatever that may have been). While ACS is looking into getting their newest version with journaling enabled working, you can always effectively reenable journaling on their non-journaling rom by doing a full backup in clockwork, and then do a full restore, which should provide an additional safeguard to help keep something like that from happening again.

[Q] SFR 1.2 - All apps start freakin out

So this morning for no apparent reason my phone started freaking out and was flashing FC's on the screen, it appeared to be every app installed, Google, Touch Pro, etc... I pulled the battery, then re-booted and it just started over. I finally went back into CWM and reloaded SFR, then Genocide, then re-enabled Journaling (ran the zip) and everything seems to be okay now (except the battery has been sucking juice worst than being on stock). Just wonderin if anyone else has experienced this? I honestly didn't do anything to the phone, it was in my holster, I pulled it to check email. I love this rom, and I'd rather not go back to stock... thanks for any help.

Sounds like a bad flash. Flash it again only wipe before you do. Do a nand restore>advanced restore data from a known good nand.
Sent from my SPH-D700 using XDA App

and dont forget to calibrate your battery after a fresh rom flash.

This has happened to me on sfr 1.2, 3 times now. For no good reason. I ended up having to reinstall rom a few times when other fixes failed. Since I enabled journaling its been a good boy though.
Sent from my SPH-D700 using XDA Premium App

Thanks all, I did flash again (and yep, wiped x3 before doing it). I had journaling on to begin with (or at least I thought I did, I ran the zip to turn it on). We'll see how it plays out today. I love this rom.... Thanks for all the help.

libracolo said:
Thanks all, I did flash again (and yep, wiped x3 before doing it). I had journaling on to begin with (or at least I thought I did, I ran the zip to turn it on). We'll see how it plays out today. I love this rom.... Thanks for all the help.
Click to expand...
Click to collapse
I had a similar problem when I didn't have Journaling ON so double-check to make sure that you have the turned on after you reflash the ROM.

Goodroid said:
I had a similar problem when I didn't have Journaling ON so double-check to make sure that you have the turned on after you reflash the ROM.
Click to expand...
Click to collapse
Yeah I always turn Journaling on after I flash. It did it again today (for no apparent reason), all of a sudden I started getting FC's (from LauncherPro), so I couldn't get to the home screen or anything. I finally wiped everything again (x3 of course), reinstalled the Rom, then the Kernel, then turned Journaling On, then restored my last backup. It's getting just a little bit old, has anyone else had the problem of LauncherPro just FC for no apparent reason? Thanks!

libracolo said:
Yeah I always turn Journaling on after I flash. It did it again today (for no apparent reason), all of a sudden I started getting FC's (from LauncherPro), so I couldn't get to the home screen or anything. I finally wiped everything again (x3 of course), reinstalled the Rom, then the Kernel, then turned Journaling On, then restored my last backup. It's getting just a little bit old, has anyone else had the problem of LauncherPro just FC for no apparent reason? Thanks!
Click to expand...
Click to collapse
At this point, I would try downloading the ROM again. I would also check out different Kernel. I'm using Genocide 2.0 and it works perfectly.
Genocide 2.0 Kernel: http://forum.xda-developers.com/showthread.php?t=961614&highlight=genocide

libracolo said:
So this morning for no apparent reason my phone started freaking out and was flashing FC's on the screen, it appeared to be every app installed, Google, Touch Pro, etc... I pulled the battery, then re-booted and it just started over. I finally went back into CWM and reloaded SFR, then Genocide, then re-enabled Journaling (ran the zip) and everything seems to be okay now (except the battery has been sucking juice worst than being on stock). Just wonderin if anyone else has experienced this? I honestly didn't do anything to the phone, it was in my holster, I pulled it to check email. I love this rom, and I'd rather not go back to stock... thanks for any help.
Click to expand...
Click to collapse
We have the same thing with my Wife's phone. It started after her phone shut down from low battery. Then BOOM Force Closes, in Swype and Google Apps. I had to do a full wipe 3x and reload the ROM to get it to work again. MAJOR PITA!
Especially because she is much less forgiving of phone "flakyness" than I am.
Thoughts?

Snowdog1967 said:
We have the same thing with my Wife's phone. It started after her phone shut down from low battery. Then BOOM Force Closes, in Swype and Google Apps. I had to do a full wipe 3x and reload the ROM to get it to work again. MAJOR PITA!
Especially because she is much less forgiving of phone "flakyness" than I am.
Thoughts?
Click to expand...
Click to collapse
That's how I got it back to working. The 2nd time was from Launcher Pro FC'ing, but I wiped it again and re-imaged the Rom and Kernel. Then turned Journaling back on. I think it just gets in a "weird" state sometimes. It takes me about 3 minutes to re-run everything (including the backup once I re-image) and I guess I just don't see it as any worst than stuff I have to do to PC's all day long when testing....haha

Same happened to me. Just reinstalled rom and kernel
Sent from my SPH-D700 using XDA App

Calkulin's E4GT 2 v1.6 bug?

I would have made a reply post in the dev thread but my post count is to low, sorry about that.
Also i read through a lot of the recent pages that pertained to version 1.6 with no answer.
After a few days of using this ROM i have noticed an odd bug. Throughout the day, my phone would be on in my pocket with out me knowing. The screen would be on and also wife, Bluetooth, gps, 4g... Certain apps would also turn on. I wear thick work pants so i don't believe my skin would have triggered this. The battery would obviously be drained with only being off the charger for 4 hours...
yesterday night, i noticed my pocket was red hot. So i went to grab my phone out to see what was going on. I have never felt a phone that was this hot before. I immediately took the battery out and let the phone cool off for a good half hour.
Just curious if anyone has noticed this before and if there is a fix? To be safe i am going back to my old ROM.

That is definitely not normal. Try a clean wipe and reinstall. If still getting this then check a program like badass battery monitor to see what is doing it. Again this is not normal at all and you are one of the only ones potentially having the issue so i don't think it is the rom in this case. Good luck and hope it corrects.
Sent from my SPH-D710 using Tapatalk 2

Definitely not the ROM. I've been using it without issues since it came out and by the number of people that use the ROM, it would've come up if it were isolated to the ROM itself. As the previous poster indicated possibly something running in the background. Did you in do a clean install from GB or Calk 1.5 (whichever you were on)?
My phone did something similar running on of the leaked ICS (non-custom) ROM's a few weeks ago and I remember just going into recovery, then wiping cache and dalvik cache. No issues since then. When in doubt start with a "clean" install and if restoring from TB, then restore apps only and no system data. This seems to play nice for me.
Good Luck.

kperry1911 said:
Definitely not the ROM. I've been using it without issues since it came out and by the number of people that use the ROM, it would've come up if it were isolated to the ROM itself. As the previous poster indicated possibly something running in the background. Did you in do a clean install from GB or Calk 1.5 (whichever you were on)?
My phone did something similar running on of the leaked ICS (non-custom) ROM's a few weeks ago and I remember just going into recovery, then wiping cache and dalvik cache. No issues since then. When in doubt start with a "clean" install and if restoring from TB, then restore apps only and no system data. This seems to play nice for me.
Good Luck.
Click to expand...
Click to collapse
I used calk's format all coming from GB. All of his ROM's have run great for me.
The best ROM i have used to date was his el29 v3.0.
I figured this was very specific, i will check out that battery monitor. Thanks for the input!

Droid Incredible 2 Won't Record for Longer Than a Minute?

I couldn't find anything on Google or another thread on here... So I figured I'd start one of my own.
I've had my Droid Incredible 2 for about a month or two now and as soon as I got it, I flashed Cyanognen Mod 7. That is my all-time favorite ROM. Everything worked great, as usual, but recently, I've had some problems. For some reason, when I open the camcorder, it won't record for any longer than a minute, 2 at most. I tried wiping the camera data and cache. I also made sure my SD card had available memory, which it did, a little over 7GB... Finally, I tried flashing to CM Nightlies. I wiped all my data, all my cache, and remembered to make a backup of the previous ROM. After I went through basic setup, I used Titanium backup to restore all of my apps. But of course, when I tried to use the camcorder, it stopped recording after about 40 seconds...
I have lost so many good videos because of that. Sometimes they don't save and I have to delete them because they "cannot be played."
Is this definitely a software issue, or could it be a physical problem too? (an issue with the camera connecting with the motherboard or something...?)
Thanks in advance, I just wish I could take longer videos again...

I just recorded a 303 long video on cm9. It sounds like it could be a rom thing. If you did everything you said you did most of the time that fixes that stuff, at least for me. Does any other rom do the same thing?
Sent from my Incredible 2 using xda premium

ShadowTech13 said:
I couldn't find anything on Google or another thread on here... So I figured I'd start one of my own.
I've had my Droid Incredible 2 for about a month or two now and as soon as I got it, I flashed Cyanognen Mod 7. That is my all-time favorite ROM. Everything worked great, as usual, but recently, I've had some problems. For some reason, when I open the camcorder, it won't record for any longer than a minute, 2 at most. I tried wiping the camera data and cache. I also made sure my SD card had available memory, which it did, a little over 7GB... Finally, I tried flashing to CM Nightlies. I wiped all my data, all my cache, and remembered to make a backup of the previous ROM. After I went through basic setup, I used Titanium backup to restore all of my apps. But of course, when I tried to use the camcorder, it stopped recording after about 40 seconds...
I have lost so many good videos because of that. Sometimes they don't save and I have to delete them because they "cannot be played."
Is this definitely a software issue, or could it be a physical problem too? (an issue with the camera connecting with the motherboard or something...?)
Thanks in advance, I just wish I could take longer videos again...
Click to expand...
Click to collapse
I've had problems recording video zoomed in on various cm7 builds. It used to work fine then one day, no; when I stop the recording, it just hangs.
Vivow was designed with sense in mind. Thus, sense cameras are awesome: fast, reliable.
I love aosp, but go back to sense for the camera. Try ucam or another aftermarket app & see if you have any luck.
Also, be sure you're not restoring any system data with titanium. In fact, I would reflash & try everything before restoring anything.
Sent from my vivow using xda app-developers app

Rushead said:
I've had problems recording video zoomed in on various cm7 builds. It used to work fine then one day, no; when I stop the recording, it just hangs.
Vivow was designed with sense in mind. Thus, sense cameras are awesome: fast, reliable.
I love aosp, but go back to sense for the camera. Try ucam or another aftermarket app & see if you have any luck.
Also, be sure you're not restoring any system data with titanium. In fact, I would reflash & try everything before restoring anything.
Sent from my vivow using xda app-developers app
Click to expand...
Click to collapse
Thanks. Ill give it a try.

How do I diagnose random reboots for my Note 2?

For the past 4 days my Note 2 has randomly rebooted at least once a day. I wasn't using the device for most of the reboots and just noticed that it rebooted because of battery drops. I don't really know what could be the cause since I don't remember changing anything recently. Is there any way I can diagnose this without root?

How about just flash stock rom? If you dont have lots of apps which you've used, then it should take care of problem without needing titanium backup which needs root. Just save ur data using kies and flash stock rom from sammy.

badbadtz.carlo said:
How about just flash stock rom? If you dont have lots of apps which you've used, then it should take care of problem without needing titanium backup which needs root. Just save ur data using kies and flash stock rom from sammy.
Click to expand...
Click to collapse
I'm actually currently on stock and unrooted. I was just wondering if there were ways to find out what caused the reboot such as logs and such? Or if there was an app I could install to keep track of what causes a forced reboot?

cesss said:
I'm actually currently on stock and unrooted. I was just wondering if there were ways to find out what caused the reboot such as logs and such? Or if there was an app I could install to keep track of what causes a forced reboot?
Click to expand...
Click to collapse
You could download alogcat from the marketplace, its free and will save a log of what's going on with your phone.
It might help find out why its happening

for me it happens cause the power button is so easy to press while phone is in pocket.
keep it pressed for some seconds by accident and phone reboots. even if screen is locked.

cesss said:
For the past 4 days my Note 2 has randomly rebooted at least once a day. I wasn't using the device for most of the reboots and just noticed that it rebooted because of battery drops. I don't really know what could be the cause since I don't remember changing anything recently. Is there any way I can diagnose this without root?
Click to expand...
Click to collapse
If your rooted run a logcat and that will tell you what happened right before the reboot, reboots are usually a Kernel Panic meaning something caused a big enough problem that it couldn't be recovered and crashed the core of Androids software "The Kernel".
As others have noted flashing a stock rom ideally via ODIN and then testing your phone may let you know if you had bad software or a hardware issue. Custom roms can have bugs that will cause kernel panic a stock rom should be 100% fine and reboot free

I find mine will sometimes reboot after copying something to the clipboard.
Sent from my GT-N7100 using xda premium

I had reboots on my previous unrooted HTC EVO. The problem was an app. I was able to diagnose the problem by looking at my install/update log. Basically, I uninstalled all apps back to the date I knew it was stable and waited to verify it was stable. Then added back one app only and waited. Repeat. About a week later, I added an app that caused a reboot within hours. I uninstalled it and the phone remained stable.
Here's where I found a chronological listing. If you have multiple devices, it will show all apps for all devices (tablets, vizio, phones,etc)
Google Play> My Android Apps> at the bottom My Orders & Settings.
This gives you a cronilogical listing of app installs and updates.
Mine turned out to be a call recorder app that I had put on the phone 4 weeks previous.

Seems like a Samsung issue:
http://androidforums.com/samsung-ga...-s3-crashing-when-copying-text-clipboard.html
I've got the same problem worth my note 2. At least I know I'm not alone.
Sent from my Galaxy Note 2 using Tapatalk 2

Bad SD cards are also a notorious source for spontaneous reboots. If you have one inserted, it should be easy enough to retract it for a while to test it. ..
Note'd too from my N7100...

I'm also experiencing this issue. I'm using 4.1.1 Brazilian stock ROM here.
Even before flashing CWM (yesterday) I as going through this problem. Most times it happens when the screen is off.
Maybe changing the stock Kernel to a custom one would solve this?