[BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes - Page 42

**arrrghhh** · #**411** (**permalink**) 03-13-2011, 02:57 AM

Quote:

Originally Posted by oisact

The problem is the FAT32 filesystem is corrupted every time Android runs, even if it is a clean shutdown. And since it always happens with the exact same two files it is something that is happening explicitly, not randomly.

A few days ago I had a reset, and afterward FRX05 was totally unstable and would reset every 20-30 minutes. After 6 or 7 resets I popped the card into my laptop, had it fix the errors, and then stability was back to normal - went all day and the next with no resets. So whatever this filesystem corruption is it does have an impact on the resets.

For it to be corrupting the filesystem every single run there is a fundamental IO problem.

There is no such thing as a clean shutdown, as I've said before. We never properly unmount the partitions off the card.

Bad SD cards can cause issues with Android, and I have had kernel panics and reboots to WinMo from SD card issues. I just swapped the card, they disappeared.

Honestly, if this is a problem/worry for you stick to WinMo until the project is complete. Thanks.

oisact · #**412** (**permalink**) 03-13-2011, 03:23 AM

I didn't realize the volume isn't unmounted. I'm not complaining, I'm pointing out a pattern that I've noticed that is beyond random corruption in the hope that it might be helpful for those working on kernels and drivers. I guess I'm bringing this up in the wrong place. I also specifically stated that I've not only used entirely different SD cards, but entirely different TP2s as well, so it's not a bad SD card.

I've not seen any FSCK### files on my SD card, so it appears the corruption I'm seeing is not being repaired when linux boots. This is further evidenced by the instability I saw until I repaired the card using Windows. People that are having major stability problems should try scanning their card in Windows just to see if that helps.

manekineko · #**413** (**permalink**) 03-13-2011, 03:40 AM

Quote:

Originally Posted by oisact

I didn't realize the volume isn't unmounted. I'm not complaining, I'm pointing out a pattern that I've noticed that is beyond random corruption in the hope that it might be helpful for those working on kernels and drivers. I guess I'm bringing this up in the wrong place. I also specifically stated that I've not only used entirely different SD cards, but entirely different TP2s as well, so it's not a bad SD card.

I've not seen any FSCK### files on my SD card, so it appears the corruption I'm seeing is not being repaired when linux boots. This is further evidenced by the instability I saw until I repaired the card using Windows. People that are having major stability problems should try scanning their card in Windows just to see if that helps.

Pretty interesting that the corruption always occurs in the same places. I wonder if there's anything that can be done with that information.

However, take a look here, maybe add your information:
Bug 89 – File system errors build up over time

**arrrghhh** · #**414** (**permalink**) 03-13-2011, 05:12 AM

Quote:

Originally Posted by oisact

I didn't realize the volume isn't unmounted. I'm not complaining, I'm pointing out a pattern that I've noticed that is beyond random corruption in the hope that it might be helpful for those working on kernels and drivers. I guess I'm bringing this up in the wrong place. I also specifically stated that I've not only used entirely different SD cards, but entirely different TP2s as well, so it's not a bad SD card.

I've not seen any FSCK### files on my SD card, so it appears the corruption I'm seeing is not being repaired when linux boots. This is further evidenced by the instability I saw until I repaired the card using Windows. People that are having major stability problems should try scanning their card in Windows just to see if that helps.

Heh, I think my user.conf's remove them so you don't have to deal with them

.

I'm sure they're there.

I'm not upset or anything, just there really is no fix for this issue AFAIK, as I understand it the issue will be present until we're full NAND.

oisact · #**415** (**permalink**) 03-13-2011, 11:20 AM

Thanks for the info guys!

murtaza · #**416** (**permalink**) 03-14-2011, 12:19 AM

Sprint Touch Pro2 uses RHOD400 startup? I tried it out, booted up fine but I get 'no service' everything else seems to run snappy. Tried RHOD500, 300 and 100 and get nothing. Checked 'force_cdma=' and ensured they were all set to '1' in the startups I tried. Also the led is always orange.. good or bad? Help?

**proxhack** · #**417** (**permalink**) 03-14-2011, 12:22 AM

Quote:

Originally Posted by murtaza

Sprint Touch Pro2 uses RHOD400 startup? I tried it out, booted up fine but I get 'no service' everything else seems to run snappy. Tried RHOD500, 300 and 100 and get nothing. Checked 'force_cdma=' and ensured they were all set to '1' in the startups I tried. Also the led is always orange.. good or bad? Help?

did you removed your sim card?

murtaza · #**418** (**permalink**) 03-14-2011, 12:30 AM

Was I supposed to remove the sim at some point? oops? Is RHOD400 correct for the startup txt?

**proxhack** · #**419** (**permalink**) 03-14-2011, 12:47 AM

Quote:

Originally Posted by murtaza

Was I supposed to remove the sim at some point? oops? Is RHOD400 correct for the startup txt?

yes it is.

murtaza · #**420** (**permalink**) 03-14-2011, 01:08 AM

thanks prox. i removed the sim and ran it off RHOD400 and it booted and showed '3g service' in the top panel but ran for about a minute before freezing and restarting the phone.. i tried it about 4 times now and the same thing happens. runs for a few minutes or seconds then reboots the whole phone