My SD card access has gotten EXTREMELY slow. I'm running CM7 nightlies, with DT A2SD 2.7.5.2. For some reason lately, writing files to my SD has slowed to a crawl, and it seems to be getting slower and slower. Copying an ~80MB ROM to my SD can take 5-10 minutes.
Is there anything I can do short of re-formatting the card? That would be a big PITA.
There is an issue with .37 kernels that cause this.
Sure enough, I'm running redstar's kernal which is a .37 version.
I get around by just mounting from recovery.
That's fine for flashing, but it doesn't help with moving large media on and off the SD card.
Sure it does. You get full SD access in recovery, no different from mounting via the notification bar.
And recovery uses a different kernel i believe. (.35.7 ?)
Sent from my Nexus One using XDA App
Yeah, that's why it works.
Hi.
I've got the 37.2 kernel for cyanogenmod 7 RC2 and got the same problem. Is there any other kernel that is supported and will increase the speeds?
Got that same issue in recovery :S
Regards
Kevin.
Related
is it because i have a class 2 memory card?
it lags and i get the htc screen alot after i exit from an app.
if i get a class 6, will the phone run as smooth as it did with the stock rom on there?
Which ROM are you using? Could be something else.
If you are rocking a class 2 card, you might want to not use the Apps2SD feature of rooted roms, you have plenty of space on the phone.
When I first rooted my MT3G I wasnt using the SD card for apps and it ran so much faster on the Cyanogen ROM than on the stock ROM.
im using the one click method. im fairly new to the whole rooting stuff, so im not to savvy just yet.
i believe it runs off the memory card if im not mistaken
Be mindful.
mahfuzurkhan said:
im using the one click method. im fairly new to the whole rooting stuff, so im not to savvy just yet.
i believe it runs off the memory card if im not mistaken
Click to expand...
Click to collapse
If you utilized the One-Click Root Method (correctly) you shouldn't have immediately run into any issues. In fact, if you played it safe and flashed a Cyanogen ROM - hopefully stable at first...then you should be in great shape. Obviously, since that doesn't appear to be the case. Consider this:
- Upgrading your card to a Class 6, the rewrite speeds exceed that of the standard Class 2 and 4 cards.
- Wipe, re-flash, and install your applications to a reformatted SD card.
- If your card isn't partitioned to some extent, might I suggest that you search a tutorial on HOW-TO (one you can fully understand) partition the card properly.
- Always, always, always...NANDROID backup a fully functional ROM - just in case you should ever encounter a problem.
mahfuzurkhan said:
is it because i have a class 2 memory card?
it lags and i get the htc screen alot after i exit from an app.
if i get a class 6, will the phone run as smooth as it did with the stock rom on there?
Click to expand...
Click to collapse
if you are running hero, it will be slow... if you want a fast rom for the mytouch, try cyanogen or jacxrom
How do I disable the apps2sd feature? I'm running cyanogen 4.0.4 if that makes a difference
if you dont have linux ext partitions in the sd card, it wont do it.
Anyone out there having the same experience as me?
After unlocking and rooting my N1 I now get frequent, if not regular, soft reboots. It seems that it only when reading or writing a lot of data to or from the SD card (e.g. search the SD card for applications, a full data or app backup to the SD card, reading a large playlist off the SD card etc). It seems to be easy to reproduce and certainly didn't happen before unlocking/rooting.
Part way though an operation the screen will go dark and the phone will reboot from the static Nexus logo.
Am using himem. Allocation problems?
Any thoughts?
Wipe , format sd card. Start over with latest stable ROM.
Thanks, I'll try that.
Is this advice offered because it's a known problem or because it's just the default advice for random problems?
Ive never had any random reboots on mine (running cyan latest right now) I did with some roms on my G1, what rom are you using?
Stock...
10
Th weirdest thing happening on my Vibrant with Eugene R2 rom.
When I put a microSD in the slot, it can not use it past 2.19 gb (like if it was a corrupted card), but when I use the same card in my TP2 or in the SD card reader of my laptop, everything is fine. I first noticed this when I was copying over all my files and I kept getting the same errors I have had with fake cards in the past, so I tried my old faithful 8gb and sure enough, when I plug my vibrant as a USB drive, I can not navigate most folders and runing the checkdisk gives me hundreds of corruption errors. When I try to format, it tells me the max is 2.19 gb. When I take the same card (which had always been fine) and put it in the sd card reader, everything is back to normal, including attempting to format (it gives the proper size). My vibrant is doing this with all cards I have tried up till now.
Any clues?
Thanks
Did you ever run an older ULF kernel at some point? Are you running one now?
I had similar issues with both my SD card *and* the internal SD, which was causing all sorts of random system glitchiness. In my case, I suspected that this was due to the problems in early ULF kernels that caused filesystem corruption. I ended up using Heimdall (you'd use Odin if you're on Windows) to restore an official Samsung firmware, then I reformatted both SD cards, and from then on everything was fine.
There's probably a less drastic approach to be taken, but restoring to stock from Odin/Heimdall is a pretty surefire way to get rid of all the gremlins.
Incidentally, it was at that point that I decided to stop flashing anything except official or leaked Samsung ROMs until CM gets released. The price for being an early adopter is just too high
I am not sure what ULF kernels are, but all I have had is stock, then Eugene, then I did a restore to my stock backup (that screwed thigns up) so I reflashed eugene. I don't know how to use odin\can't figure out what files i should use.
julienrl said:
Th weirdest thing happening on my Vibrant with Eugene R2 rom.
When I put a microSD in the slot, it can not use it past 2.19 gb (like if it was a corrupted card), but when I use the same card in my TP2 or in the SD card reader of my laptop, everything is fine. I first noticed this when I was copying over all my files and I kept getting the same errors I have had with fake cards in the past, so I tried my old faithful 8gb and sure enough, when I plug my vibrant as a USB drive, I can not navigate most folders and runing the checkdisk gives me hundreds of corruption errors. When I try to format, it tells me the max is 2.19 gb. When I take the same card (which had always been fine) and put it in the sd card reader, everything is back to normal, including attempting to format (it gives the proper size). My vibrant is doing this with all cards I have tried up till now.
Any clues?
Thanks
Click to expand...
Click to collapse
Julie, I had this same problem with both this ROM, and my proceeding one, ASOPish; as have many, many others!
I too have been wanting a fix, but have not come across one. Because I am able install data onto my micro sd card via the adapter this is what I have resigned to doing. There was a mounting fix posted last month some time, but it didn't work for me, though others state that it did for them.
Sorry I couldn't give you a more workable solution, but at least, for me, this way does work.
FYI I had this problem until nero V3
Eat at Joe's
Having micro sd issues also. I tried moving some music and pics from the internal sd. It put the names but 0 data. I erase them and they come back. I reformatted the 8gb card it said 8gb free. I go back to the gallery or music player and they are all back. Check the sd with a file manager and thete they are.
t1n0m3n said:
FYI I had this problem until nero V3
Eat at Joe's
Click to expand...
Click to collapse
hum... anyone else with this problem fix it by using nero v3?
This is happening on all 2.2 roms.
One issue was fixed, where the internal and external cards were being read opposite to what there were ..., but the issue of reading external sd above 2gigs is still there ...
If I remember correctly, this was the issue when 2.2 was released for the N1 .... they forgot to re-add support for sdhc cards... that's why they pushed 2.2.1.......
Short story: Was running the latest (as of Dec. 4-5) ICS ROM(s) - the ones with the SD card bug - and my SD card appears to be shot.
Long story:
-----
I had been using the various betas of the ICS ROMs since I noticed Tytung's first Alpha was out and the ROMs had been improving rapidly. I guess when the headphones issue was fixed it caused problems with reading the SD Card which was documented and seems to be well known.
The constant SD messages didn't bother me much, but eventually I noticed launch icons missing and went to the Market to re-download one of the apps I use (I've been flashing so much, I wasn't sure which apps I didn't bother restoring). The Market app tells me I need a SD Card to install apps, so I just figured it's just the instability of the sd card mount for this latest batch of ROMs and I'll flash an older ROM off my SD card when I get the chance. I also noticed the messages started saying I inserted a blank SD Card but I brushed it off (couldn't look into it at the time).
I get home and find out Clockwork refuses to mount my card which means I can't easily wipe and install something else, so I switch to USB storage mode in CWM to simply transfer a ROM from my PC and my PC only sees ~30mb of my 16GB SD! I initially thought it was just some corruption but I tried all sorts of format and partitioning programs and nothing recognizes more than 30mb of space and none have even been able to format that little space that's showing.
I've been Googling for a while and came up with nothing I haven't already tried so I finally decided to post here. Is there any hope for my SD card? Being the holiday season and for once I've got most of my Christmas shopping done early, I'd rather not waste the little money I have left to run out and buy another SD card right away if it's not necessary.
-----
Does anyone have any ideas how I could fix this? I'd greatly appreciate it because I now stuck with WM6.5 and realize how much I didn't miss it for the past year
This is also a heads up for testers to be sure to upgrade their ROM ASAP (or at least to the kernel that fixes this) if they're on a ICS ROM with an SD card bug. I'm not complaining - I know this is a part of testing early builds (please ignore my sorry post count; I've been flashing for quite a while) - but there's no reason for others to go through this issue if it can be helped.
Have you tried EaseUS?
Sent from my LG-VM670 using Tapatalk
Yes,
Try Easus Partition Manager and/or MiniTool Partition Manager.
They can help but you will have to format your SD card I think.
Good luck!
I had the same problem. I plugged my card into a USB reader after it working error free, it then said it needed to be formatted and was only showing 30mb. After formatting repeatedly it still doesn't read. I haven't retired any positioning software but i think the card may just be done with.
Sent from my HD2 using XDA App
probably you'll need a replacement.
have you tried the SD formatter? there's like a 0.000001% chance it will work in your case, but why not try it?
Hello,
I'm wondering if others have the same issue.
Issue: Whenever I unlock the phone (via fingerprint or PIN), I notice the response time is 2-3 seconds slower after mounting my microSD Card (Samsung 256GB EVO+ microSDXC). The SD Card is filled with 199GB of files. My little workaround for now is to unmount the microSD card when I'm not using it. Anyone have a similar issue? I am running on the latest stock ROM (rooted) for H918.
- Will
I'm on the same phone, same SD card. Deff different kernel. My finger unlock is actually TOO fast (phone turns back on if I turn off using my print finger). So look for optimizations elsewhere is my advice.
533y4 said:
I'm on the same phone, same SD card. Deff different kernel. My finger unlock is actually TOO fast (phone turns back on if I turn off using my print finger). So look for optimizations elsewhere is my advice.
Click to expand...
Click to collapse
May I ask what ROM + Kernel you are using. I may look into it. Thanks.
aznxwill said:
Hello,
I'm wondering if others have the same issue.
Issue: Whenever I unlock the phone (via fingerprint or PIN), I notice the response time is 2-3 seconds slower after mounting my microSD Card (Samsung 256GB EVO+ microSDXC). The SD Card is filled with 199GB of files. My little workaround for now is to unmount the microSD card when I'm not using it. Anyone have a similar issue? I am running on the latest stock ROM (rooted) for H918.
- Will
Click to expand...
Click to collapse
aznxwill said:
May I ask what ROM + Kernel you are using. I may look into it. Thanks.
Click to expand...
Click to collapse
NATF with NotSoStock 6.5 kernel. I also flashed the FluenceUHD optimization patch. Big difference with the FluenceUHD patch in general. Better battery and less lag overall. I do get the occasional stutter when typing but that has more to do with my governors and such than the optimizations. Also, I am using T-UI as a launcher, dunno if that plays into it at all. I know that launcher is godly for battery. :highfive:
I came to a similar conclusion a few weeks ago. Removing the SDCard speeds up unlocking, and also seems to clean up some of the settings not saving.
Depends on what you have the sdcard FS as. if its fat32 it will probably be slower
me2151 said:
Depends on what you have the sdcard FS as. if its fat32 it will probably be slower
Click to expand...
Click to collapse
According to DiskInfo, the sdcard FS is texfat (which I assume is exFAT) while the system is ext4. It makes me wonder if it's better to format the sdcard as ext4 since that FS is native to linux.
For those who have fast unlock responses for your sdcard filesystem?
Thanks.
TexFAT is NOT exFAT. TexFAT is actually one of the slowest filesystems you can use. Even slower than Fat32 by almost 2-4 times. That right there is your issue. your computer will possibly have issues if you format to ext4 though so i recommend just formatting to exFAT using twrp.