Who has NOT had memory card issues with the Touch? - Page 8

kg4peq · #71 (**permalink**) 12-01-2007, 07:44 PM

I may have come across something of value in remedying this situation. I'll test it out and report back after a couple of days.

I decided to fire up a Mogul here at the store and compare a couple of possibly-related registry entries to those in the Touch, and I noticed something interesting.

In "\HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\ Class\" there are a few folders and sub-folders, "MMC_Class", "SDMemory_Class", and "SDMemory_Class\High_Capacity".

On the Touch, there is an additional registry key present that is NOT present on the Mogul:

DisablePowerManagement="1"

Oddly, this key appears in all but the "SDMemory_Class\High_Capacity" path, but for all I know the value could be inherited from "SDMemory_Class".

Because "1" represents "true" or "enabled" (for the benefit for those who may not have known otherwise), this flag would seem to disable power management on memory cards.

Since one of the recurring themes in the data corruption issue is the device going into standby mode, I can't help but wonder if this might be our culprit.

So, I'm going to remove those DisablePowerManagement keys (to mirror the Mogul, rather than simply setting them to "0") and we'll see how things go. You're welcome to try it, I'd like to see if it fixes the issue for anyone.

I'll keep both threads updated with my findings.

hippity.hoppity · #72 (**permalink**) 12-02-2007, 12:03 AM

Good find. I'm going to set mine to "0" and see what happens. My previous workaround was to set S2U2 to just blank the screen instead of putting the phone to sleep.

kg4peq · #73 (**permalink**) 12-02-2007, 12:09 AM

Quote:

Originally Posted by hippity.hoppity

Good find. I'm going to set mine to "0" and see what happens. My previous workaround was to set S2U2 to just blank the screen instead of putting the phone to sleep.

Pardon my ignorance, but what's S2U2?

EDIT: Nevermind. Found it. Not using it personally.

I regret to report that my previous suggestion did not fix this problem. Everything worked fine until I ran a few manual updates on Spb Insight and then the card showed up corrupted. I have popped the hood again and am tinkering with some other stuff. Stay tuned.

jhale83 · #74 (**permalink**) 12-02-2007, 12:22 AM

I have had my files become corrupted twice today and both times I had a playlist open within WMP (I had paused the music and the phone went to sleep with WMP still open). I do think it has something to do with files on the storage card being accessed when the device goes to sleep. It's going to suck if we have to go until the 1Q 2008 update for a fix...

kg4peq · #75 (**permalink**) 12-02-2007, 12:24 AM

I'm tinkering with some filesystem-related registry keys now...

EtherealRemnant · #76 (**permalink**) 12-02-2007, 03:30 AM

All of this stuff reminds me of the DSOD issue on the 6700...

If it truly is a standby-related problem, I imagine we won't see a fix for at least 4 or 5 months. =/

By the way, I let my phone go to standby mode while syncing with Insight... no issues. Tried pausing WMP and letting the device fall asleep... no issues.

I'm trying to reproduce this issue but I'm not having any luck.

kg4peq · #77 (**permalink**) 12-02-2007, 05:50 PM

It seems the only way I can *force* the unit to do this--- that is, in an effort to deliberately reproduce the issue--- is to open several applications that work with the memory card, including in my cases Spb Insight (while running an update), Sprint Music Store, the camera album viewer, etc., have them running for a few seconds, push the power button to put the device in standby for 10-20 seconds, turn the unit back on, and use the Quick Menu's "close all" button to exit the applications. Then when I check the memory card, I have the corruption. Reset and everything's fine.

So far I have removed the power management keys in the registry as described previously, disabled the FATFS cache (which was already set to 0 KB anyway), and applied a previous HTC patch for this issue from another model (P3300 rings a bell). After removing the power management keys, Tom Tom stopped auto-launching, but that problem reappeared after installing the HTC patch. However, since installing the patch, I have not been able to force the memory card into a corrupt state, but that's only been a couple hours ago so it's too soon to say if the combination of this stuff will fix the issue.

Ph33zy · #78 (**permalink**) 12-03-2007, 01:11 AM

I tried just the HTC patch from the P3300 and im still getting the corruption. In fact, usually i could just soft reset and have my files come back but, this time the files were still corrupted.... not sure if it had to do with the patch or not but I uninstalled it anyways...

kg4peq · #79 (**permalink**) 12-03-2007, 02:15 AM

Since installing the P3300 patch I've still had filesystem issues, but instead of the filenames getting garbled and the outrageous file sizes and dates, here's what's happening: The directory structure remains intact, but the files vanish. Reset, and they're back.

I decided the best way to fix this is to go Blackberry. I like Windows Mobile, except for the fact I haven't yet come across a WM PDA or phone that works as intended. Combined with the fact HTC has had this issue before and still can't get it right (and my Touch is a replacement for several Mogul's that also didn't work right) I think it's time to call it quits and go back to what works.

maxqc · #80 (**permalink**) 12-03-2007, 11:58 AM

Using a Bell HTC Touch with the provided 512mo card (bought it last week). I began having problem today ... The file names are something like "DF/&/HE" and all weird names...

The only thing I installed today is Pocket Mecanics but I dont know if it has something to do with it...

I currently use my SD card to copy .CAB I want to install and I also have SPB Insight to save it's data on it... also, the camera saves images on the card.

I Also use S2U2.

It sucks...