Quote:
Originally Posted by oisact
Okay, I took a different SD card, formatted it FAT32, installed virgin FRX05, placed it in a totally different TP2 (so 100% different hardware, card and device), booted into Android. Once it was up I did a normal power off and let Android shut down and turn the device off. Pulled the SD card, popped it in my laptop, and it found two corrupt 32k files, the exact same files as my other device and SD card.
Something is going on that Android is corrupting the FAT32 file system in a consistent way. I can't imagine it is supposed to work this way?
Can someone else pop their SD into a windows machine and do an error check on the card and see if it finds errors? It will dump the files into FOUND.000 (FOUND.001, etc number increments each time you run error check and it finds corrupt files) on the SD card, and inside you should see two 32k files FILE0000.CHK and FILE0001.CHK.
|
Oh I see what you're saying... Yea I don't ever scan the card with Windows after running Android on it. Just seems like a bad idea
.
Seriously tho, what does it matter? We already know that Android doesn't get shutdown correctly, and Linux spits out FSCK records from not being shut down correctly. Not surprised Windows also spits out errors.
03-13-2011, 02:44 AM
Threaded Mode
