yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] eras2r:
Something interesting on this topic from my ROM thread. It looks as though users of my ROM are getting the SOD when the are traveling. I have not gotten this as of yet, but I dont really venture too far from home. But several users have stated that they never got the SOD until they drove ~45mins from home.

If the culprit module does have something to do with location, I wonder what it could be. Google Location service does not have any modules in the package. Manila has several. I also set the clock off of the cell tower. No clue where to start on this one... just wondering if any other chefs have seen something similar.
[Windows Mobile] B4PJS:
I havent seen that one and I commute between Reading and London every day
[Windows Mobile] mnet:
there are 2 kinds of SOD people are having:

the first is SYS SOD. this is related to build and/or source. the device completely fails to wake up after sleep (screen remains off)

the second is SOD due to manila 2.5 on some devices. the device does wake up, but the screen remains blank and the backlight is turned on. see this thread for more details about this, inc. a solution

personally, regarding SYS SOD, i have been having it very often on some builds like 21897, even when dumping from dio. BUT i have been using 21898 (from rollup) for several weeks now and never had SOD. i think this is related to the build not just the module addresses.
[Windows Mobile] pkoper:
I get SOD on com2 builds when SRS WOW is cooked in.
[Windows Mobile] the_scotsman:
I've had sleep of death with my 21901 ROM (SYS downloaded from main builds thread, not this one)....have you tested this 21901 for sod?
[Windows Mobile] Reza WM:
http://www.techparaiso.com/windows-...-up-from-sleep-on-windows-mobile-phone-device
[Windows Mobile] + Que PPC:
i already read this article from MAKK... but it works for you as a USER?
[Windows Mobile] ai6908:
Couple of my users said they had SOD cuz of s2u2 and htc messaging! I think i have SOD cuz of lock app! Same build...23563! I had the same issue with 23562 and 23559 as well!
[Windows Mobile] + Que PPC:
I dont have SOD in COM3 COM5 or COM8, just in some COM2,

A friend (Faria) said that making a clean upgrade using MTTY to erase the memory should fix the SOD but who knows... :p
[Windows Mobile] williyung:
My SoD experiences:

- In fact, I never got SoD issue with all my roms (COM2,COM3,COM5, etc (dio/roll up)) without Sense.

- With Sense ROMs:

1. If I cook in these 3 packages: aGPS Confirmation, GeoLocationService, and HTC Geo Service, I always got Startup SoD (From booting dont touch anything to the device, and let it sleep, will go to SoD).

2. If I dont cook those packages, never got StartUp SoD.

Ps.: I did MTTY a couple times, same results
[Windows Mobile] AndrewSh:
Guys.... :) Long ago I wrote about so called SOD. It happens only because of the wrong dump you use! If the source is dumped properly - no SOD! In wrong dump all the modules in Common have the same e32_vbase: usually 10000000. I don't want to start long and dull talks about that, but if your device has problems with rollup builds - use flash.dio and dump it. At least you will avoid reloc problems.

When you cook your roms - SOD issue happens when several modules are trying to occupy the same address.

So when you delete several packages - you can get working rom because you occasionally deleted the stuff trying to get to one address. But it's random! Next time other modules will try to occupy the same address.....

Some advices:

1. try to use different dumper when dumping dio

2. reloc your modules not according to e32_vbase but to order list in packages.cif (you should take care of your own Metadata for that)

3. recmod some stuff like monstrous BROWSINGCORE and other
[Windows Mobile] williyung:
Thanks for the explanations Andrew :)

But it's weird why I never had SoD in all my roms (dio or roll up) without sense?

My roms without sense also have many modules (more than my sense roms), I think it has the same posibility that several modules are trying to occupy the same address as you mentioned.
[Windows Mobile] AndrewSh:
The point is that it's a model dependent issue. Guys from our forum (who have several different PDAs) - got SOD on Asus, but not on HTC for example (same build same way of cooking).

So it depends upon the memory distribution things in device
[Windows Mobile] rgb-rgb:
Thanks for the info, but can you shed some light on how to find out the address of the modules or how to change it? Will recmodding it and converting it back to a module fix that?

I have had the SOD from both rollups and dumping from Flash.dio using xidump.

So far, the only thing that has helped me is that I changed back to the original OEM folder for my Tilt 2 instead of using the Rhodium 2.07 OEM folder. It's been 4 days now and I have not had the SOD and I have tried to get it.

I understand what you are saying about the address being random, but could it be random conflicts with my OEM folder and the SYS folder being dumped?
[Windows Mobile] + Que PPC:
Thanks a lot for the INFO Andrew... do you have a link to read more about this?
[Windows Mobile] AndrewSh:
+ Que PPC, link - nice question :). It was a private talk between me and Da_G in skype. Also Alexx, SergeyLAR and Barin were participating in the conversation. I told him that his dumper is not good - we checked the addresses of the Common stuff after the first SOD appearance.... OK, he refused to send me his dumper for checkup and fixing - it was kinda private soft. But he already fixed his program. You can see that - his rollups are good now. But I have a strange feeling that his old dumper is now in the hands of our Chinese friends - so COM2 started to cause SOD issues.
[Windows Mobile] + Que PPC:
Oh, yeah that kind of talks dont have links to know more :p

So we will be alert from Chinese sites rollups or dumps

thanks a lot bud. hope nobody has that dumper anymore, but if you chef has a copy of this dumper please try another or the fixed one. ;)
[Windows Mobile] dotcompt:
Hi AndrewSh,

I still have my doubts about SOD being related with leaked builds not dumped properly. I build my own Roms and I never have SOD like many XDA members that flash my Roms too, however there are some members that are constantly reporting SOD issues with my Roms.

The odd thing is that SOD is happening always with the same members (mostly AT&T and T-mobile users) and other guys do not even know what SOD stands for, because they have no issues. So the same Rom and different behaviours.

This makes me wonder that SOD may be related to Carrier\Network\band services, poor 3G coverage or even automatic updates while device is in standby.

Well it is just a thought and I may be wrong.
[Windows Mobile] Laurentius26:
Hi Dotcompt,

Just to inform you, I had SOD only once with a build I think it was 21893.

Up till now I never faced it anymore.

And I'm having a HTC device, no carrier. ;)

Btw my Operator is neither AT&T or T-Mob.
[Windows Mobile] + Que PPC:
SOD isnt related to any signal or anything, Telcel (my carrier) sends me so much **** (advice) via STK, i always have signal strenght at full 3G but i dont use data conections (so ridiculous expensive) my device HTC 8525 Cingular. and i used to have SOD in a build cant remember wich one then a friend of me in Taiwan gives me all the Common folder shared of the same build from another dump directly from dio using xidump, and the sod dissappears... ;)
[Windows Mobile] miky6682:
If this could be useful I hadn't SOD with 23563 until I added bubbleblreaker into my kitchen. I had recmodded this files.

Also some user of my htc elf reported frequent restarting, others hadn't this iussues.
[Windows Mobile] Nibbley15:
Howdy all,

I am experiencing the SoD with certain folks and myself to say the least with my builds. I'm using 21903 from RSTOYGUY's kitchen. I have been doing research on the net only to find this that may or not apply.

http://forum.ageye.de/viewtopic.php?f=4&t=1854

I did find that when I looked in my registry that these defaults were set to 5 not to 1 like it calls for. I have been looking all over my kitchen to find a way to change these defaults but to no avail. I'm not using G-Alarm in my builds so there is probably some default location from a .DLL file that I'm missing.

Anyhow this is what is causing my SoD that I have been able to duplicate many times. I make a phone call, and to end my call I press the bottom right red end button on my HD2, this causes almost an immediate SoD.

If I press the "end call" button on the sense screen and then press the "X" in the top right corner then it will usually not go into a SoD until I plug in to charge for the night.

I searched my phone REG and did find that these 2 settings were set at "5"; I just found this info today, so I'll try some testing myself and see what happens.

Thanks all and hopfully we can find a solution that works.

EDIT: This REGEDIT didn't work, I heard a small beep after about 10 minutes and it went into the SoD.

After this I did the following:

1. Task 29

2. Installed the original ROM 2.10.0

3. Task 29

4. Installed my cooked ROM; so far no more SoD

The only thing I did differently this time is I didn't install a radio after my cooked ROM. Could this be it? Installing radio's after the fact? I am running the stock radio from the 2.10.0 install right now. I'm going to install the radio again and see if it starts to duplicate again.

EDIT: I turned off the "automatic light adjustment" and installed the 2.9 radio. So far after 24hrs of testing working great! No SoD, I'm going to turn back on automatic light again and see if it crops back up.

EDIT: I also used the stock bootloader this round instead of the one from PPCit anyone else had this issue with a different loader?
[Windows Mobile] Nibbley15:
bump, just a bit to see if I could please get some feedback
[Windows Mobile] Laurentius26:
Hi Andrew,

Forgive me I only want to report but I just faced SOD on 23569 packages plus XIP provided by you.

I'm coming from 23568 (flash.dio dumped) which works fine never faced SOD.

Also I followed your instruction about DPI and Lang so I only used the common packages and used DPI and Lang from 23568.

XIP:

http://xdaforums.com/showpost.php?p=6449581&postcount=15813

SYS:

http://xdaforums.com/showpost.php?p=6429333&postcount=15765

23568 DIO:

http://xdaforums.com/showpost.php?p=6385390&postcount=15615
[Windows Mobile] AndrewSh:
Laurentius26, as I told - SOD issue is also device-dependant. Once I got SOD on P525 and I was not able to fix it, but the same SYS on Topaz worked perfectly w/o issues. It depends upon the memory mapping of the device. It can happen that your SYS modules are in address conflict with some OEM ones and so on....

As you see from my sig - I have 23569 rom in public in two different configs and both work well. That means - normally I published working sources.

You should try to recmod something in SYS or OEM or delete some unimportant packages - but it's random - no-one can definitely clarify: "that bloody Solitaire or Office or something else is causing SOD".....

So if your 23568 DIO dump works well for you - make 23569 from it. For that case it's easy - grab from 23569 only:

caldll.dll, tcputil.dll, welcome.exe, ril.dll and cplmain.cpl. Replace them in your 23568. That's it. No other changes. Also try again to use my xip.
[Windows Mobile] Laurentius26:
Allright friend thanks for the reply and for all the good stuff you share. :)

Sorry if I offended you that's not my intention, only trying to help finding the bugger. ;)

Edit; btw I never faced SOD if I dump flash.dio or ruu_signed.nbh but I will keep you updated if it happens.

This is the second time I'm experiencing SOD.
[Windows Mobile] ai6908:
I had SOD when I was using that smartlock program. But once I quit using it, I dont experience it anymore.

Just my 2 cents.
[Windows Mobile] ElCondor:
Some people are saying that GTX could be causing SOD too. Maybe it's got something to do with manila?
[Windows Mobile] dotcompt:
I wish it was but there are people not using Manila, only Titanium and still have SOD.
[Windows Mobile] ElCondor:
Too bad... I will help investigating the cause of this, and let you know if I have some information.
[Windows Mobile] spikegotti:
could be a conflict with manila and something in the sys too... my non manila roms are SOD-free and i experienced SOD in builds i tested like 21903 and 21901 with manila... without manila there is no SOD
[Windows Mobile] Laurentius26:
Well I returned back to 23568 the flash.dio source I use with same oem and EXT and SOD is gone.
[Windows Mobile] Nibbley15:
I found out my issue, it was just the bootloader program, and it was random. The self extrating bootloader from PPCit was the one that caused my troubles.
[Windows Mobile] miky6682:
I haven't SOD with your 23569.
[Windows Mobile] magawa:
it sometimes caused by

edited Oem drivers

bad xip porting ( both sys and device xip )

some app like srs wow hd ( should be a cab install or in config.txt)

I've faced SOD when do things above ...
[Windows Mobile] Ronin666au:
Sleep Of Death

Hi,

Some additional info for those trying to solve the Sleep of Death problem. I have found that having the lock (Start ==> Settings ==> Lock) activated has some bearing on this issue.

Having the lock set to 1 hour, I get the Sleep of Death issue.

Having the lock set to 5 minutes, I do not get the problem.

I can swap between the two settings and the SOD comes back very quickly with the 1 hour setting, and does not appear after a week plus with it set to 5 minutes.

Don't know the relevance, but this may help.

Cheers and good luck!
[Windows Mobile] spikegotti:
Quote:

Originally Posted by spikegotti

not sure if task29 or constant flashing does any harm to the device, but what i can say is, i had a rock solid system up to when i reflashed the same rom again...

before i had no SOD, no freezes, no hangups nothing, everything was perfect... i tried new manila files and they were fast, but not stable... so i flashed my phone back to the rom i had before which i was using, now im trying hard as heck to get the rom to work properly... this is my 4th flashing after experiencing one SOD and many freezes...

its not the roms here that are problems people... if so i would have had issues from yesterday... i only experienced this after trying those unstable manila files and reflashing...

again, i had a rock solid device but went testing stuff and now i flashed back the said rom which was solid and now im struggling...

i think our devices fail when flashing over and over just like when we install different OS over and over on a harddrive... the disk then show errors and fail at some point...

this is why i had to buy a new HD for my comp too, because i was constantly installing OSX when i was developing graphics drivers for normal computers... then months after, my disk failed
[Windows Mobile] jakdillard:
In the CDMA touch pro 2 I believe it was caused by the newer 2.04 kernal from SPCS it was calling on commands from the CIQ services which the drivers for this service broke other apps within the ROM itself, changing the kernal "nk.exe" resolved "SOD" issues
[Windows Mobile] + Que PPC:
I guess all members has this kind of "SOD" cause we all stay so much time in XDA :p

Im the one with that unlucky mtty procedure.... once i changed all the common pkgs inthe sys that has teh SOD and it works even without mtty.
[Windows Mobile] Menjic:
I have posted my experience with SOD in this treads:

[REF] "LOCKUP" issue on HD

and

HTC Touch Diamond 2 and Standby of Death SOD

Maybe more which I did not subscribe and I can not find it now :)

BUT I am really freaking out with this SOD so I decided to collect all I can about it and find solution :) big words but I am really stubborn person, when I begin something I can not stop until I find solution or cause of problem and realize that it cant be fixed :)

I am curious how come nobody from HTC did not find cause or solution for this, or how come that every SOD device have similar symptoms and no one can find exact cause of it.

Can anybody confirm is it hardware of software problem ?

My opinion is that it is hardware related but software problem, but I can not test this.

I think that HTC built some devices which are not compatible with software used on all other HTC's or that SOD device have something hardware similar, not that they are broken, just something different than non-SOD devices.

Maybe some one could try to compare hardware versions or actual components in sod devices against non-sod.

Maybe we could run some benchmarks and post results and some who knows what he is doing can compare some parameters.

Maybe it is network + sim related, but it is not solution in some country's or for people who travel, there must be another solution.

Maybe easiest solution is to buy another device but I don't like easy solutions :)

I can bet that it is such stupid thing that nobody would not belive it when we find what it is.

Things that I did not try but will are:

Removing NEO drivers package, and changing sim card.

I did try factory shipped rom, but same thing hapen to me, SOD (what ugly word it is)

also every kind of procedures found on XDA and google and .... like Task29, hard reset, hard reset .....ROM or reset after charging, or flash shipped rom or disassemble clean reassemble device..... nothing works for me in first it looks like solved but eventually SOD comes back.

I am not any kind of guru or chef or mad scientist, I just admire them and they time and money and knowledge invested in making our device nicer and better and solving our problems :)

Thanks to all of you.

Sorry on big post and bad english.

===============================================================================================

And one more thing, it is not just HD, I saw and try to solve SOD on TP, XDA NEO, HD, DIAAMOND 2 and HD 2 but read about it on tytn and others. You know this but just to remind you :)
[Windows Mobile] Menjic:
One more interesting thing!!!

I did not read anywhere this, when I expirience SOD and constantly pressing power then home than power again, repeat that three steps few times, screen comes on and I have up side down picture of everything but not touch just lcd.

If anybody understand me. Touch reacts as normal orientation but lcd displays up side down picture - manila tabs are up but when I swipe finger down they react in reverse if I swipe to right tabs going left :)

Then I again press power button to go to standby and again to wake device and then it is normal everything works.

I repeated this 4 times.

This would mean that SOD is caused by graphics driver ???

Is anybody reading this ???

=========================================================

Device is Touch HD T8282 from Orange, bought in London if it means something.

Kwbr_Topix_3.6_Sense2.5_WM6.5_no_htcMsg

OS Version : 5.2.21901 (21901.5.0.92)

Manila version : 2.5.20121225.0

ROM version : kwbr topix 3.6 WWE

ROM date : 04/08/10

Radio version : 1.17.25.09

Protocol version : 52.69.25.37U
[Windows Mobile] AndrewSh:
Dude, no-one reads here - everyone is only writing!

I wrote long ago - so called SOD caused by mistakes and overlapping during readdressing SYS modules while building IMGFS.

The mistakes and malfunctioning are RANDOM!!!

But - nevermind :) Continue looking for guilty hardware or software....
[Windows Mobile] Menjic:
Thanks, so this is now solution:

1. Task29

2. Factory shipped rom

3. Task29

4. Cooked rom of choice.

If it does not work repeat 1,2 and 3 and flash another cooked rom

and so on, and on, and ...... until one rom works without SOD ?

Am I right ?
[Windows Mobile] nauman:
That looks like a solution :D
[Windows Mobile] Menjic:
It is, for some devices, I tested on few but on mine HD it is not working.

On my HD what ever I do after few days I get SOD.

Longest time without SOD I have with FACTORY SPL and FACTORY ROM !

If it helps someone, if you ask me most devices it is nod hardware but there is some small percent where is hardware proble. It could be connectors between mothrboard and other things, because if my device is working and I disassemble it in to pices take all out and then assemble it I get SOD immediately, then I repeat flashing or hard reset or disassemble again and then it works ????

And I have BIIIG question mark above my head. It seems that is hardvare, but if it is hardware why flashing helps ?

If I leave loose or dirty connectors I get that inproc or whatever called error it is ??? (said that it is connector issue) ???

It is so confusing that I gave up, I sold device as is and saving for HD2 or next generation of capacitative windows mobile device.

Maybe I am wrong but it seems that devices from networks are somehow different compared to WWE unlocked bought in store not network.

But that is my opinion.

Every trouble HTC I had was from network provider.

Every trouble free device was factory unlocked double expensive device bought in legal store.
[Windows Mobile] toadlife:
I checked my common sys dir and found that e32_vbase value in my modules in common and a few of them have 10000000 but not all of them. Is having more than one with the same e32_vbase value enough to cause the issue??

If so, can recmoding all of the affected modules solve the issue?
[Windows Mobile] Farmer Ted:
I don't think the addresses matter in the sys/common folder. What matters is what the addresses are in your \dump folder, after the addresses have been re-assigned by g'reloc. The problem is that using EVK, you can't see what the addresses are, because the .txt files are deleted in the modules.
[Windows Mobile] toadlife:
I switched from evk to OSKitchen awhile back. OS Kitchen has the option to stop before running platformbuilder, so the next time I build I'll have a look at the dump dir.

If there is no .txt file, there is still a way to find out the relevant info using this excellent tool.
[Windows Mobile] Farmer Ted:
Wow, that's pretty cool. From the dump, I get this for rilphone.dll:

--------- Module name : rilphone.dll
e32_imageflags : 0000212E
e32_entryrva : 00005A38
e32_vbase : [COLOR="Red"]7966F000[/COLOR]
e32_vsize : 000[COLOR="green"]80000[/COLOR]
o32[0].o32_vsize : 000754D3
o32[0].o32_realaddr : 79670000

From Devhealth.exe, I get this from the rom:

=== physicsengine.dll page summary: code=0[rom(C):0 ram(c):0] data r/o(R)=0 r/w=0[ro(r)=0 rw(W)=0 exe(E)=0 dll(D)=0 heap(H)=0] page(p)=0 stack(S)=0 dup(d)=0 unknown(?)=5 obj(O)=0 reserved(-)=11
=== rilphone.dll ([COLOR="red"]7966f000[/COLOR] - 796eefff) (not pageable)
79670000(0): DDDDDDDDDDDDDDDD <-- DLL: rilphone.dll + + + + + + + + + + + + + + +
79680000(0): DDDDDDDDDDDDDDDD <-- DLL: rilphone.dll + + + + + + + + + + + + + + +
79690000(0): DDDDDDDDDDDDDDDD <-- DLL: rilphone.dll + + + + + + + + + + + + + + +
796a0000(0): DDDDDDDDDDDDDDDD <-- DLL: rilphone.dll + + + + + + + + + + + + + + +
796b0000(0): DDDDDDDDDDDDDDDD <-- DLL: rilphone.dll + + + + + + + + + + + + + + +
796c0000(0): DDDDDDDDDDDDDDDD <-- DLL: rilphone.dll + + + + + + + + + + + + + + +
796d0000(0): DDDDDDDDDDDDDDDD <-- DLL: rilphone.dll + + + + + + + + + + + + + + +
796e0000(0): DDDDDD------DDD- <-- DLL: rilphone.dll + + + + + + + +
=== rilphone.dll page summary: code=0[rom(C):0 ram(c):0] data r/o(R)=0 r/w=121[ro(r)=0 rw(W)=0 exe(E)=0 dll(D)=121 heap(H)=0] page(p)=0 stack(S)=0 dup(d)=0 unknown(?)=0 obj(O)=0 reserved(-)=7

I guess it works, lol.

(7966F000 + 80000 = 796EF000)