SD card is possibly linked to sleep of death (SOD) on TP2

[willysp]

I'm going to speculate that some TP2's just have the SOD problem due to manufacturing / component tolerance out of specs.

I remember my old Mogul just would never work with BT (and others had the same problem), but most would work. I always believed there was something in it that was out of design tolerance.

Since new users have the problem with the stock ROM, it's not software.

[dalastone]

i had a trancend 8gb class 6 with no problems, an A-data 16gb class 6 with no probs. for me the SOD started a week after upgrading to sprint 6.5. however it's been working fine so far for 6 weeks. i did 2 hard resets, then reflashed the stock 6.5, hard reset again. the only thing different this time is i left the auto akjust backlght "checked" so far so good.

[THE-COPS]

Wesley, posting in one of the old threads isn't very practical. The OP thought he found a possible fix, so in order to highlight his findings, he made a new thread. The thread title notes that the SD card "may" be linked to the SOD. It's not (just another SOD thread). If this were posted as a reply in one of the old threads, it probably wouldn't get as much views because some people would think it was just another user with an SOD or that it's someone jabbering on and on about the same problem and not really providing anything useful. It would get buried so fast , you know it. And it just isn't very practical to go through 30 pages of stuff, especialy if there still isn't a solution in the mix. It's very tedious to read about the same thing over 100 times. When threads get that long, new info should be relayed in to a new thread, so to get better responses. New threads with catchy titles are the key here. I could see if the OP labeled it "Another SOD issue" or something monotonous as usual, but that's not the case here.

Now to get back to the topic here.

Never had an SOD on my TP2, yet. But I did have a odd issue on another phone. I don't know if this is relevant but, I had a problem with SOD on my Moto Q9M. If the screen was off when I inserted the MiniSD card (any card) , the phone would never wake up. As long as the screen was on when I inserted it, no problem. It could very well be a problem with WinCE and the SD bus. A com or driver issue. Perhaps the phone tries accessing the card, or something on it, or vice versa, but gets hung up trying to do so in sleep mode. Idk, but it's just a guess. I asked a ton of others with q9M's and they never had the issue I did. So, a bug in the ROM or on the phone, which would not be present on every unit. A manufacturing flaw the inadvertently pops up. Just some guesses here.

[Wesley762]

Originally Posted by THE-COPS

Wesley, posting in one of the old threads isn't very practical. The OP thought he found a possible fix, so in order to highlight his findings, he made a new thread. The thread title notes that the SD card "may" be linked to the SOD. It's not (just another SOD thread). If this were posted as a reply in one of the old threads, it probably wouldn't get as much views because some people would think it was just another user with an SOD or that it's someone jabbering on and on about the same problem and not really providing anything useful. It would get buried so fast , you know it. And it just isn't very practical to go through 30 pages of stuff, especialy if there still isn't a solution in the mix. It's very tedious to read about the same thing over 100 times. When threads get that long, new info should be relayed in to a new thread, so to get better responses. New threads with catchy titles are the key here. I could see if the OP labeled it "Another SOD issue" or something monotonous as usual, but that's not the case here.

Now to get back to the topic here.

Never had an SOD on my TP2, yet. But I did have a odd issue on another phone. I don't know if this is relevant but, I had a problem with SOD on my Moto Q9M. If the screen was off when I inserted the MiniSD card (any card) , the phone would never wake up. As long as the screen was on when I inserted it, no problem. It could very well be a problem with WinCE and the SD bus. A com or driver issue. Perhaps the phone tries accessing the card, or something on it, or vice versa, but gets hung up trying to do so in sleep mode. Idk, but it's just a guess. I asked a ton of others with q9M's and they never had the issue I did. So, a bug in the ROM or on the phone, which would not be present on every unit. A manufacturing flaw the inadvertently pops up. Just some guesses here.

There have been a few threads that have claimed to fix it but if it was really fixed there would not still be people having issues with it. there is no REAL fix for it, for everyone it has been the cause of many different things and there has been nothing solid on it, but having it all consolidated makes the information about it more accessible. it would make it easer to search with it being in one thread, even Sticking the thread would make it more visible and accessible. I am not trying to be mean or distasteful I just would like to not see a new thread every other day created on it. Most of the threads that are created all is the same info over and over.

[nrfitchett4]

Originally Posted by willysp

I'm going to speculate that some TP2's just have the SOD problem due to manufacturing / component tolerance out of specs.

I remember my old Mogul just would never work with BT (and others had the same problem), but most would work. I always believed there was something in it that was out of design tolerance.

Since new users have the problem with the stock ROM, it's not software.

care to explain how it's not a software explosion when the reports of the SOD went through the roof after people installed 6.5, whick by the way, comes standard now on sprint tp2's?

[IIVisionII]

Hey everyone,

Just checking in. I still havent had an sod and the phone is running smoothly. I would recommend that everyone whose having it at least try scandisk and defrag on their card as i believe that it could be due to a corrupt card rather than card brand.

On another note, i started this thread here because i know i did not want to sift through hundreds of pages of an old thread to find new info and know others probably feel the same. It seems like there are many reasons for the sod as there are different options that work for some people and the same won't work for others. I just hope tis works for some of you too.

[boodaka]

Originally Posted by IIVisionII

Hey everyone,

Just checking in. I still havent had an sod and the phone is running smoothly. I would recommend that everyone whose having it at least try scandisk and defrag on their card as i believe that it could be due to a corrupt card rather than card brand.

On another note, i started this thread here because i know i did not want to sift through hundreds of pages of an old thread to find new info and know others probably feel the same. It seems like there are many reasons for the sod as there are different options that work for some people and the same won't work for others. I just hope tis works for some of you too.

I think im finding that was my issue, after removing the card i still had to reflash in order to get the screen working (flashed without the card inserted) im trying to clean the card now to see if i put it back in, if it goes retarded again. I believe something with winmo was getting lost via the card because i could run Android fine and the screen would come on and off, so i dont believe its hardware, or else both os's would have the issue. When flashing with the card in would result in the same problem of the screen not responding instantly after flash.

Edit: As soon as i plugged in the headphone jack it went wonky again, flashed back and normal again, so no jack and sd card use, and works fine { bangs head on wall }

[willysp]

Originally Posted by nrfitchett4

care to explain how it's not a software explosion when the reports of the SOD went through the roof after people installed 6.5, whick by the way, comes standard now on sprint tp2's?

Please re-read my post - I said I was speculating; I did not say I could prove. But, by way of explanation, it's really very simple - some people have stock & SOD, some have stock & no SOD. That implies it's not software. sounds exactly like Mogul BT issues - some devices had problems regardless of stock version, some never did have issues. If people are using the same software and some have issues, and some don't - what's the variable? Hardware.

And if it's shown up more with the 6.5 stock, a very feasible explanation could be that a modified driver has different timing conditions that stress a HW tolerance more than in 6.1. I'm speaking as a former ebedded HW/SW engineer - timing issues, race conditions, and mfg tolerances DO exist and are B--ch to find and fix!!!

BTW, I've never had a SOD with either 6.1 or 6.5 stock, or a zillion customs, and several different cards.

BTW, others feel the same way:

http://forum.ppcgeeks.com/showpost.p...50&postcount=1

[clueless25]

I disagree with it being the SD card itself. You probably had something on sd card. I have had to reformat my sd card once.

[Wesley762]

Originally Posted by clueless25

I disagree with it being the SD card itself. You probably had something on sd card. I have had to reformat my sd card once.

I have seen bad SD cards cause all kinds of weird issues with PPC over the years, I would not rule it out completely.