My device is having a deepsleep issue where it becomes unresponsive for an amount of time.
Its unmounting the SD card in the process... then remounting
Related
I am not sure what's wrong with it, but sometimes after I reboot my G1, the SD card simply won't mount automatically. Sometimes another reboot will solve the problem, but usually I need to eject the SD card manually and reinsert it to solve the problem.
Any one experience the same as mine? Any solution to that?
I've encountered the same issue from time to time and I fix it by doing the same thing either rebooting again or ejecting / inserting the card again.
Not sure the reason / if there is a fix for this atm.
After rebooting the NT this morning the sd card was apparently not mounted automatically. It was inserted in the NT and was working correctly before the reboot. My NT is rooted.
If I remove and re-insert the sd card it does mount and work normally until the next reboot.
I backed up all of the sd card data and then erased & formatted the sd card with the NT. That did not help.
Any ideas on how to get the sd card to mount automatically after reboot?
Thanks!
My bad...wrong forum.
You know this room is NC room, right?
When I moved from CM9 to CM10 my 64GB SD card started behaving very oddly. On reboot or occasionally just after the phone had been on for a while I'd get one of three results:
a. the card worked perfectly (rare)
b. the system would complain that the card was broken and needed reformatting
c. the system would spontaneously say it's safe to remove the SD card
It turns out that the problem I had was that the fsck on the card would (most of the time) fail to allocate memory and die, prompting to system to think the card was bad. By default Android will reformat your card with 4K clusters, which made the FAT about 15 million clusters long. When I try to run fsck manually via adb, that results in fsck trying to allocate a 60K block of RAM and usually failing. You can see if this is your problem by running the following:
Code:
/system/bin/fsck_msdos /dev/block/vold/179:1
If you get an error then you can fix it by reformatting your card (yes, this will mean losing all your data if you don't back up first!) to use 16K clusters (I tried 8K clusters and still got errors on the fsck). This will mean that your data storage will be a little less efficient (so if you store small files you won't be able to fit as many of them on the card) but for me that's better than having to move back to a 32GB card. To do the reformat, run (AFTER BACKING UP!):
Code:
/system/bin/newfs_msdos -F 32 -b 16384 /dev/block/vold/179:1
and enjoy your newly working SD card!
I thought I'd share my solution to fixing the sd card issues mainly with San disk cards that mount and unmount
I had a network branded phone (o2 uk) and it constantly mounted and unmounted especially will shuffling through my music
I really flashed my phone with a non brand firmware so it removes the ugly network logo on boot up
And so far I have not had a problem with the sd card mount and unmount issue.. I can shuffle through my music very fast without any issues..
Thought I'd share my solution maybe it might help you
My phone is unbranded but I have sd card issues.
I routinely (daily) get "sd card suddenly removed' or 'sd card ready to be unmounted'.
So i started using a 64GB sd card, transfered about 11GB of app data pver, and began filling more. All of a sudden android OS usage went skyrocketing, and the storage menu reports the internal memory as being 120% full (i.e. impossible). Backed up sd card and reformatted, no luck. Issue does not persist when sd card is unmounted.