I'd hate to suggest it but it could be a hardware failure, probably with that shoddy sd slot. Did you try formatting the card in Windows and then sticking it in your phone.Īs far as I know, the sd doesn't have sufficient permissions to invoke a shutdown request, as something like that has to be invoked using root permissions. I still stand by my theory of Samsung hardcoding something into the phone to kill non-samsung sds of specific sizes. Otherwise, you might try a Samsung sdcard, I know they run in the s3 with no problems. I would say to format your card to ext4, as it supports massive amounts of storage (like 2PB or something around there, don't know officail #), but from the sounds of things your running Windows on your PC, so thats a no go. Perhaps you could try formatting it to two 32 gig partitions, instead of one 64? I know that the S3 only officially supports up to 32GB sdcards, so perhaps that suggestion may work. I have never heard of that happening either. It just shut down again, with no files on it at all.Īnyone have any thoughts?Wow, that is weird. Thinking it might be a corrupt file, I reformatted the card in the phone. Within 15 minutes or so, the phone shut down. So after lunch today, I put the card back in. So I left the card out over night, and all morning. I didn't get around to putting the card back in the phone right away, and it occurred to me later that the phone hadn't shut down in a while.
Yesterday evening, I took the SD card out to put into my PC and make a backup (much faster than going through the USB cable). At first, I thought it was some configuration change or app I had installed, so I did a factory reset and restore from a known good nandroid backup. It seemed to work fine for a while, but a couple of days ago I noticed my phone was randomly shutting off (NOT rebooting, just turning off) multiple times during the day. I've got a Sandisk 64GB SD card, formatted as FAT32.
0 kommentar(er)
