yashsingh1/xdaforums huggingface dataset:
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] Bruce Inman:
This did not work for me. I tried the network settings but it affected my data.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] nlel:
How? if you find that WCDMA + UMTS (3G) means that you get too poor coverage in some places then set it to GSM + AUTO if that means your data is too slow then change the band manually as and when you need to leaving it set to GSM + AUTO for best all round coverage only switching to 3G when you really need it.

If changing the network settings does work for you but you would rather not use it then I suggest changing the phone for a HTC Hero Android or equiv as that is likely the only way you are going to find a solution suitable for you. I could not afford/did not want to change phones when I first got it if there was any way I could get the phone to be 100% stable without changing it, I was therefore prepared to compromise on the band settings.

The Standby of Death can affect the majority of HTC Windows Mobile phones and if you are one of the unlucky ones to suffer from it because of the band settings then short of changing the phone to Android you are pretty much out of luck, you could still try changing sim (network provider) as a last resort.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] Menjic:
It is not solution believe me !

You have to ask your self a few simple questions:

Why just your device have a problem, not your brothers, friends .... ?

How come you have problem now not before, when device was new ?

Is it real that you did not notice it before ?

If SOD happened just recent time, is it caused by something you did ?

Did you drop it, flash it, changed something ?

HTC can not produce 100% same or 100% working devices, some must be broken, if all devices are same, flashing problematic ROM on another device should cause same symptoms ?

So, long story short it is sometimes, software, you can solve it with "flash dance" or this procedure:

1.Task29,

2.Hard reset,

3.Factory shipped ROM,

4.Hard reset.

But if that does not help it is 100% hardware problem.

I am maybe competent to tell this, but my opinion is that SOD is caused by faulty - corrupted memory and it is 110% hardware. This can be caused by dropping device, or spill something on it or even extreme heat or cold or both or over clocking or just factory flaw but it is hardware.

But always the real solution is the simplest one.

Me and lots of people solved the problem with new device, or motherboard, so it is for now only 100% solution.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] nlel:
How come I had the same problem with both my Tytn II and my Touch Diamond 2 from new and I never dropped them or spilt anything on them, seems to much of a coincedence to get two faulty devices and besides setting the phone band options as I did solved the problem, if they were faulty that would never have happened.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] Menjic:
I dont know how to explain but for my 2 devices only solution was to buy new one.

You can get SOD with factory shipped rom, you can change network band settings and solve sod like that, but again I think it is hardware related.

Why SOD is not present on all devices if it is software problem, isn't a big chance that people mistake in cooking roms for another device not just for HD, TP and Tytn maybe one or two more but not all devices have SOD ?

If you ask me, there is more chance for hardware malfunction, then software problem on just small group of devices.

If it is software it would be present on all devices, and it would be more people with problem and someone would made fix for it already.

Sorry on bad english I hope you understand what I am trying to tel you.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] nlel:
To me it seems like this, my Sim or Network or Location or whatever causes the SOD in every HTC Windows Mobile phone I buy as I had it in two brand new phones used in the same Location with the same SIM on the same Network.

Setting the phone band option as I did solved the problem on both phones, I now have an Android phone using the same SIM, Network and Location and I do not have SOD with auto band switching enabled (as default).

My reasoning for saying the phone is not faulty is that I had two with the same fault that could be solved in the same way and that people who do not have the problem are not on the same SIM, Network or Location that is why they do not get it.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] Menjic:
OK I respect that, but are those 2 devices Touch HD, diamond and Tytn ?

How come only on these few devices SOD, and if you for example take touch pro 2 and put same sim on same network you wil never have a SOD ?

That is from my experience.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] nlel:
The two devices were the Tytn II bought Sept 2007 and had SOD straightaway from new and the other was the Touch Diamond 2 bought June 2009 and had SOD straightaway from new.

Both devices responded to setting the band option to GSM + AUTO or WCDMA + UMTS 2100 I am not saying this is the solution that works for everyone as it doesn`t but its worth a try as it definetely works for some.

I have now switched to Android not because of the SOD but because I fancied a change and I can leave the band settings set to AUTO without issue.

I do not have enough money to have bought more then two Windows mobile phones in the space of 3 years but I am sure I would of had SOD on any and all of them because of my SIM, Network and Location.

I only got the Android because I sold my TD2.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] Ondrowicz:
Just a small update.

As I have written one page back I had problems with SOD. Then i switched the phone band option to GSM+AUTO and it definitely solved the problem, no SOD in several weeks. So I strongly recommend to try this option for everyone that has problems with SOD, maybe it is not an universal solution but it can help!
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] Devilish Angel:
Hello,

First of all, i'm sorry for my poor english... :(

I've read all previously post but I would like to be sure about the *solution*.

Yesterday, after install the last update found on HTC website (in french):

RUU_Topaz_S2_HTC_FRA_2.53.406.4_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe

After update, my Diamond 2 is a little bit slower (not so important) but freeze many times.

If the backlight is totally turn off (by the power switch or by the battery save after X seconds), SOD appears.

It never appear with attenuation only.

The only way that I've found to solve the problem is to soft reset it (I've never try the reset button, only remove the battery) or made a incoming call.

Charging the battery or not doesn't change anything.

Something *fun*, when freezing, start menu can appear normaly.

Solution: Buy a new one. :confused::(

Edit: After a last hard reset without restore my SMS, and never install Nodata, all seems like OK. I'll try today.

Do you know something similar as Nodata ?
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] shiva111:
me 2 having the same prob bro, 4 days back i upgraded my rom from 6.1 to photon 6.5 ux rom and now every day 2-3 times i am having this sod prob, i had also installed this radio ver. 4.49.25.17. i think its a radio problem. i dont know a lot abt. dev. but its my thinking. hoping to get a proper solution to this rather disabling 3g/auto mode.
[Touch Diamond2, Pure Q&A, Help & Troubleshooting] netrial:
Switching from the Asia WWE ROM to the Photon UX ROM actually helped some in my case. What helped most was dumping my previous phone carrier 3/Vodafone :p
[G1 Android Development] leoni1980:
I have been using the new Fatal1ty ROM on my G1 and was seemingly having no problems whatsoever HOWEVER it transpires that people have been sending me sms messages and they have not been coming through at all. this has happened twice with one person and once with at least FIVE people in the past 24 hours.

Scouring these forums it appears that people using the JACHero ROMs are not immune to this problem either. I PLEAD with the developers here to find the root of this problem and solve it before working on making Rosie more efficient. SMS messaging is a CRUCIAL aspect of of day-to-day life for most people, and many could be unaware that they are even suffering from missing texts. The problem for me is arbitrary with no predictability, I have received messages from those whose didn't come through yesterday subsequently, so there is no problem with my network; however the original messages are still AWOL.

In the meantime I'm not touching these Hero builds and I'm going back to cupcake.

Please don't flame me, I'm not trying to put a dampener on people's enjoyment of these ROMS but I think this problem is deserving of its own thread rather than the occasional mention in a huge ROM thread which could leave it overlooked.
[G1 Android Development] Nismo300zx:
This thread was really pointless this has been discussed plenty of times as well as slight fixes...check your apn settings...or open up messaging go into settings and uncheck auto retrieve then reboot and then go back and check it off....this has seem to work for some people and has also been a known tmobile issue...
[G1 Android Development] Klarato:
Hmm. Im on the latest jac build of hero. And the only issue im having is with mms's which is a known problem.

I tend to get 300 sms's a day and the person sending me these sms's would sure as hell let me know if i didn't reply to one for some reason lol.

I do use chomp sms rather then the default one though. Not sure if this might be fixing the problem people are having.
[G1 Android Development] Nismo300zx:
If you are on tmobile check your apn settings with the link in my Sig..hope that helps
[G1 Android Development] Klarato:
Hey mate,

Im on three in Australia. Thanks anyway.

Are the right APN settings meant to fix the MMS? As i am fairly sure i have the right settings for my provider.

-Klara
[G1 Android Development] bigballa:
i only missed one text today from 1 person

i guess it was more of my fault cuz i was in sams club and my 3g and edge were constantly switching so that couldve caused my problem

but other than that i havent been missing texts
[G1 Android Development] maxisma:
This problem occurs to me too.

Even when I use chompSMS. Android receives the message, but i doesn't "give" it to the messaging app(s).

I think this is a memory issue, android seems to terminate even system processes sometimes. (I think it is)

I'm going to test it.

EDIT:Yes, memory issue... it worked while on homescreen.

Opened brwoser, send another test sms, no message got.

)

D/dalvikvm( 597): GC freed 6958 objects / 760784 bytes in 177ms

I/ActivityManager( 102): Process com.android.settings (pid 468) has died. ?

I/ActivityManager( 102): Start proc com.android.mms for broadcast com.android.m

ms/.transaction.PrivilegedSmsReceiver: pid=619 uid=10017 gids={3003}

W/dalvikvm( 619): Refusing to reopen boot DEX '/system/framework/com.htc.androi

d.pimlib.jar'

I/ActivityManager( 102): Start proc com.p1.chompsms for broadcast com.p1.chomps

ms/.sms.SmsReceivedReceiver: pid=627 uid=10065 gids={3003}

D/dalvikvm( 33): GC freed 271 objects / 10232 bytes in 187ms

I/ActivityManager( 102): Process com.android.mms (pid 619) has died.

D/dalvikvm( 33): GC freed 47 objects / 2024 bytes in 400ms

I/ActivityThread( 627): Publishing provider com.p1.chompsms.provider.ChompProvi

der: com.p1.chompsms.provider.ChompProvider

D/dalvikvm( 33): GC freed 2 objects / 48 bytes in 289ms

I/ActivityManager( 102): Process com.google.android.gm (pid 488) has died.

I/ActivityManager( 102): Low Memory: No more background processes.

W/TabControl( 597): Free WebView cache

D/dalvikvm( 175): GC freed 1118 objects / 55248 bytes in 855ms
[G1 Android Development] sacredsoul:
I can confirm this. Pretty useless to me now. Gonna go back to CMOD till this get worked out.
[G1 Android Development] barakinflorida:
I noticed that you are runing at 528 MHz... I did not have any problems until I boosted speed, try going back to default speed range and rebooting.... Just an idea...I'm doing it now..
[G1 Android Development] maxisma:
528 MHz shouldn't be the problem..

i think it's like this:

1. Brwoser starts, eats much memory

2. Android detects an incoming SMS, starts giving it to an app

3. App is starting, want's memory which isn't avaible

4. App get's killed, SMS is lost

I'll look how it works with Swapper enabled..
[G1 Android Development] dipeshb:
On JAC Hero 2.3.3

I can confir that this issue has happened for me today also. I had to call the 2 people I was expecting a reply to to confirm that they had sent me a reply SMS. I am on the UK T-Mobile.. I may also have to revert to the Cyan fast rom until this is sorted out... I'm glad you guys have confirmed that this is a general issue rather than my Update issues.
[G1 Android Development] npace:
I did the same thing you did to confirm the issue. In some instances, the messaging app got killed.

Then, I saw on the JACHero thread that you need to disable "automatic retreival" from the messaging app, reboot, then enable it.

I ran the same test afterwards, and 10 messages in a row during high usage of browser with flash on the htc.com page, I have not had any missed messages.

Hopefully, that's the fix. I know it sounds strange.

EDIT: Never mind, it still happens.
[G1 Android Development] dipeshb:
I think this has worked, got a txt almost straight after I did this... Will have to confirm this over time though. Hero 2.3.3 and the Optimised Rosie are the closest to a fully usable Hero now and the more I use it the more I like it... Lack of SMS would have to be a deal breaker for me, already had an argument with the GF about that!
[G1 Android Development] npace:
I submitted it as a bug at http://code.google.com/p/jacheroplus
[G1 Android Development] abteer:
I'm glad I'm not the only one having this problem. I text more than I talk on my phone. It seems that when I ask some to text me it works but then a friend will text something and I won't get it. If this issue gets sorted out then JACHero is my rom of choice.
[G1 Android Development] blackgin:
The same for me!

This sms problem is the only that stops me from using stably JacHero rom
[G1 Android Development] h.nocturna:
Anyone know if they still get this problem with Swapper enabled? I haven't lost any text messages, but I might just not know it... hehe
[G1 Android Development] sxfx:
Guys I jsut got off the phone with T-Mobile, I live in USA Midwest, and they have confirmed they are having problems with their sms/mms servers.

It first started where their servers would report completely wrong times and your texts would show wrong times from people received, and I guess this is what is causing problems with certain people receiving their sms and certain not.
[G1 Android Development] maxisma:
It occurs on o2 Germany too.
[G1 Android Development] leoni1980:
Glad i'm not the only one then. Seems this problem isn't resolved after all.

I originally installed the Jachero ROM. I installed Handcent and received a couple of messages but when i selected them from the notification bar they had disappeared and i was unable to read them. The next day I tried out the fatal1ty ROM and it was only this morning, approximately 24 hours later that I started to find out that I'd been sent texts but had not received all of them, nor even received a notification.

I am on T-Mobile UK and am absolutely certain it is not a network issue.

With respect to enabling automatic retrieval in message settings, I fail to see how this is relevant as it is my understanding that SMS uses GSM and the APN settings are irrelevant. I could put 'Im a potato' as my APN address and i would still get texts ok in theory.

This really is a HORRIBLE problem, as we NEVER know for certain if we are receiving text messages. I really like the newest Hero releases BUT i simply CANNOT go back to them until someone finds the root cause of this problem and fixes it.
[G1 Android Development] obe1:
sms

like i said before in the jachero thread it seems like its only an isolated problem cause i have jachero 2.0r7 and i have not had any issues with sms and i have txt out side of las vegas to family members in verizon in oxnard california and also el paso texas and those people are in tel cel and i get all the txt back so its either 3 things people dont know or changed their apns 2nd an i-d-10-t error or i happen to have the only g1 with immunity to herorom sms problems.
[G1 Android Development] brummiesteven:
The biggest problem with this is not only do you not receive text messages, the phone actually DOES receive them but just doesn't present them to you.

That means that you can't just put your sim in another phone to see if you have missed any texts or anything like that. I went back to JF 1.51 as the hero builds were too unstable anyway for me (home screen REALLY laggy) :(
[G1 Android Development] djnutz:
Checked apn settings for T-Mobile USA - spot on.

Disabled auto-retreive - all the sudden received sms messages galore. Did not reboot, and I didn't recheck it. Right now auto-retrieve is off.

I didn't receive around 8 texts earlier today and now I'm receiving each one.

Whether this lasts or not...I'm not sure. But at least it seems to be working better for now.
[G1 Android Development] leoni1980:
Much as i would be happy to try disabling auto retrieve if it solved some other problem I'm still dubious about re-installing a Hero ROM on the off-chance that it solves the sms problem. Id rather a proper fix be found as i dont like the idea of risking losing any texts.

Its a shame as I found the Fatal1ty 1.2 build to be perfectly usable as a normal ROM once I'd disabled Touchflo. Im not that bothered about widgets but the better browser, multitouch, gallery, sms app and Facebook integration really make this ROM enjoyable. Maybe if I wait another month or so a new slimline build will surface. I really don't want to use App 2 SD or swapper as I don't install many apps and I like to keep things simple.
[G1 Android Development] blackgin:
See here! As said by maxisma it is a memory problem, so do not say anymore that could be a tmobile problem or a problem of the auto-retrieve checked/unchecked.

Continuing to suppose and suppose we wont resolve the problem, so let's focus on the memory problem, that is the real one.
[G1 Android Development] j2kquest:
Heres what i found out

I also have been having the dreaded sms problem whilst running jac hero 2.33

What i did was install jacheroski's optimised rosie rom, and lowed my cpu setting to 348

i have text myself 5 times now and all times the messages have come through instantly. before when i texted myself from another number 1 out 5 would come through

it seems overclocking at 528 is taking up alot of cpu memory hence the memory eating up alot of system resources.

no one flame me please im not a developer, just merely trying to contribute............can anyone else verify that this quick fix works consistantly across all platforms thanks

Ok just realised.....even though this solves the sms problem, it makes the rom slow (obviously) even with swapper enabled

soz
[G1 Android Development] Cammarratta:
A fix for SMS with the new jac 2.3.3 that I've found and seems to be working for me is to go into the apn menu. Where you select etc.t-mobile but don't select it. Instead hit menu and go to restore default apns. It'll reset your apn values and then reboot. Of course you're going to have to repeat it again at the menu "reset to default" one more time then reboot again. After that you should have no problems getting and sending sms' and mms'. I've tested it and it seems to hold up for the most part.
[G1 Android Development] jj972:
im runnin jac 2.3.3. Without rosie and everything seemed fine for a while......i tested sms and mms and i recieved all the ones that were sent to me but today i noticed im not getting some because i have the text widget from the market where it shows ur latest text and it showed one i recieved but in the msg app it didnt show the text.....kinda weird
[G1 Android Development] Cammarratta:
See this used to happen to me as well. Now whenever I send a picture message though there's a giant red exclamation mark on the thread but it still sends the picture.

Also is it just me or is it that when I receive pictures they're really blurry? I've been trying to figure out something but I get nothing. :( I miss getting clear pictures...
[G1 Android Development] leoni1980:
.....and that's the BIG problem I have with these builds: YOU JUST DON'T KNOW WHAT YOU'RE NOT GETTING THROUGH.

I installed Fatal1ty 1.3 a couple of hours ago, disabled 'auto retrieval', rebooted, sent myself 24 letters from a-z via SMS and received them all. I then got my friend to send me six separate texts.....received them all. Following that he sent me some texts which showed in the notification bar, but when i selected them there was only my previous message. On the two occasions where this happened I was engaging in loading/data downloading. In the first instance i was running setup for the new Bloo app, in the second I was loading a web page.

Could THIS be the answer? is there some glitch making the system 'throw away' text messages just after they've reached the notifications bar but BEFORE they've been properly saved?

Being as I know absolutely NOTHING about programming I could not possibly tell anyone whether or not this is the case, but I hope someone can.

It is worth noting that the missed messages occured when TouchFLO was disabled via clearing the defaults in the Application settings and using the default 'home'.

For the time being I have gone back to the Dude's Cupcake YET AGAIN and will await further developments with respect to this problem (it IS VERY DEFINITELY A PROBLEM)
[G1 Android Development] jj972:
Yea so i guess its like the dude said earlier about the memory thing killing the msg process so it throws out the txt.....hopefully theres a fix.....txt widget is kinda getting me by for now
[G1 Android Development] johncore:
Still a problem, have gone back to CM until this is sorted, have done lots of testing and getting nothing on JAC's builds. Even sitting at the home screen I don't recieve texts, definitely not network issue.

Doesn't seem like enough people are having this problem for it to ever get looked at though.
[G1 Android Development] leoni1980:
I think perhaps people are having problems but don't realise, or alternatively this only affects people on british/european bands rather than those used for example by US T-Mobile. There is no doubt that this is NOT a problem with my network, and the problem has occured on different ROMs with different messaging apps installed. I genuinely think this is happening to a lot more people but that they are oblivious to it, or are just sticking their fingers in their ears and going 'nerr nerr nerr'

I fail to see how we are just 'unlucky' since we have the same hardware with the same radio and spl.

I await further updates.....
[G1 Android Development] dipeshb:
I'm back to cyan 3.62. Run so well, but as said before, the browser in hero is the killer app for me, multi touch works great on this build too.

Jac has just released 2.34 but no mention of an sms fix in the change log.. I think this is certainly a UK and maybe euro issue, the US guys don't seem to be affected by this, hence the lack of fix available.

I may try the hero again but much later now until a change log mentions this issue as fixed.