One annoying problem fixed by Europe_1.37.401.3 ROM - Touch Diamond, MDA Compact IV ROM Development

The Europe_1.37.401.3 (and possibly all 1.37.x ROMs) fixed one annoying problem for me.
With 1.34.x when I was in the roaming area the phone would shut down and the only way to bring it up was to take out the battery and put it back again.
The 1.37 ROM fixed this problem.

Related

HTC Touch Pro 2 & Standby of Death SOD

I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
had this problem once: I switched on the camera, and then left the device on the table for a long time - so it went to standby.
I could not wake it up by the power button after 20 minutes, but as an incoming call came, it was ringing with a black display, and I could answer the call with my BT headset. screen was still pure black
finally I pushed the reset button and since then everything is fine - I still feel this was connected to the camera.
terta said:
had this problem once: I switched on the camera, and then left the device on the table for a long time - so it went to standby.
I could not wake it up by the power button after 20 minutes, but as an incoming call came, it was ringing with a black display, and I could answer the call with my BT headset. screen was still pure black
finally I pushed the reset button and since then everything is fine - I still feel this was connected to the camera.
Click to expand...
Click to collapse
Yeah if it only happened the once then that was probably the case, if you have the problem on a regular basis and you know its nothing to do with the camera (becuase you never loaded it) then you have the problem I am describing.
I have exactly the same problem has Terta.
I'm 100% sur that it's the camera that make this bug I have tried all my weekend to reproduce the bug a lot of time and it was always the camera...
Hope someone can fix this bug cause now I can't take any photo without soft-reseting my phone. Very, very, very annoying...
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Yes I guess there are many reasons for the Standby of Death, if you have ruled out all software causes such as the camera or installed apps then have a think about the SIM and/or the settings that impact the SIM.
Its the last thing most people will think about. It worked for me and got rid of a random SOD problem 2-3 times a week which coinceded with being in weak 3G areas (where the phone might switch bands automatically) although that never occured to me at the time.
You see I haven't installed other applications nor do I load up the camera and leave it running so I couldn't figure out what was causing it, it just happened randomly not connected with anything particular that I was doing.
i hope there is some kind of magical solution for this because i just got my Sprint TP2 today and I have this issue everytime my phone goes into standby. Pushing the power button wont bring it out but every once in a while opening the keyboard does. I have to continually reset my new phone just to use it
PS; beyond this annoyance, I love it!
coppertop24 said:
i hope there is some kind of magical solution for this because i just got my Sprint TP2 today and I have this issue everytime my phone goes into standby. Pushing the power button wont bring it out but every once in a while opening the keyboard does. I have to continually reset my new phone just to use it
PS; beyond this annoyance, I love it!
Click to expand...
Click to collapse
Try taking out the SIM card and see if it still happens everytime the phone goes into standby...
For the past few days I have been restarting my phone thru the soft reset. I think this is a windows issue...it has happened to me even without having the camera app running, and yes I checked the task manager. Hopefully this will be fixed when windows mobile 6.5 comes out, since Im getting frustrated with this phone...I have the phone for about a month now....grrr Stand by of Death!!!
coykiam said:
For the past few days I have been restarting my phone thru the soft reset. I think this is a windows issue...it has happened to me even without having the camera app running, and yes I checked the task manager. Hopefully this will be fixed when windows mobile 6.5 comes out, since Im getting frustrated with this phone...I have the phone for about a month now....grrr Stand by of Death!!!
Click to expand...
Click to collapse
so its not just mine then? this is ridiculous
Right, i had got seriously fed up with the standby of death happending, so i decided to contact HTC Europe directly.
They went over the usual 'factory reset' and 'update' solutions before coming to the conclusion that either there is a loose connection/faulty screen or there is some confiliction between drivers of the pre-installed software.
Because all HTC phones have 2 years warrenty as standard they have asked me to send if off so they can invistigate the problem and send me a replacement.
So if anybody is in the same boat as me a suggest you contact HTC and arrange a fix/replace.
Hope this helps.
nlel said:
Yeah if it only happened the once then that was probably the case, if you have the problem on a regular basis and you know its nothing to do with the camera (becuase you never loaded it) then you have the problem I am describing.
Click to expand...
Click to collapse
Add me to the list, seems to happen when I am charging my phone and it hits 100%
This phone reminds me of all my previous Sony Ericsson phones....very unstable OS' ... Makes me regret of getting this one and should've gotten an iPhone...but then again I'm pretty sure iPhone's have issues that apple fanboys aren't admitting. The reason that made me not get an iphone is because of ATT's ridiculous plan pricing...Its crazy!!!
if you are on sprints network, take out the sim card. This has fixed the issue for me. Used to get SOD a few times a day but opening the keyboard and then pressing the power button used to get me out of it. This was really annoying, and i read that it may be issues with the sim card. Took that out a week ago and havent had a SOD yet
jabberoo said:
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Click to expand...
Click to collapse
Jabberoo I can verify that this was caused by the SRS WOW HD program on my touch pro 2 as well. AS SOON as I uninstalled this application, restarted, everything was fine again.
I don't know if this will help anybody but if your phone suffers from SOD and you have TMO put it in airplane mode and see if it still does it.
I did that and it never went into SOD so that lead me to believe that the radio was the culprit. before that I tried everything listed. I don't have the 3G Plan so the 3.45.25.14 (T-Mobile) radio is the only one that worked for me.
I have the same problem.. just have installed spb mobile shell with mskip ultimate. I try to unistall all
I have a question: if I choose the 3G only option (WCDMA + UTMS 2100 in Europe) and the signal strength is low there will not be an automatic switch between 3G and 2G am I right? ...and i'm offline then
jabberoo said:
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Click to expand...
Click to collapse
sanjsrik said:
Jabberoo I can verify that this was caused by the SRS WOW HD program on my touch pro 2 as well. AS SOON as I uninstalled this application, restarted, everything was fine again.
Click to expand...
Click to collapse
Confirming this....
I had this issue for a while now...I tried hard resets, ROM flashes etc. It all works fine and was stable until I flash Sps Wow HD (I just realized this). Yesterday I flashed the latest HTC released sense ROM and right now after installing all the softwares I had the SOD again. Fortunately I saw the 2 posts and thought I will give it a try...and guess what?
I uninstalled the Srs Wow HD and phone is back to normal...no issues till now...will report later if I see any.
I am going to tmobile to get the SIM changed anyways hoping that it will fix another issue I am having. Every day I have to turn the airplane mode ON and OFF at least twice to get my data connection back. Mostly after a call and sometimes in random the phone is unable to reconnect to the data, it gives me an error that the epc.tmobile didnt respond or something like that. If any of you know how to fix this issue...plz help
I have been Experiencing this so called "SOD". HTC touch pro 2 sprint. On the 6.5.5 Build 23569 i had MAJOR sod issues. Energyrom , mighty , titanium , you name it. Ive Task 29 and reflashed them all multiple times. Still SOD was there... But i may have found a temp cure for me atleast. This is what i did....
First , i used task29 , next i reflashed the stock 6.1 rom, check for SOD... still had it... i task 29 again. Installed titanium edition , without sense. SOD was cured, phone worked fine, tryed to install sense 2.1, failed, SOD was back. Soo...
Then i task29 again, then repeated task29 a second time at the boot screen.... then i flashed Energyrom GTX themed 21907 build june 27th......Once it was flashed unplugged my USB plug and plugged it into the usb wall plug i have . Installed LUMOS, light sensor still was inactive and no response, could not brighten and still nothing... Installed G-light right after lumos without uninstalling lumos.... Still plugged into the AC wall USB plug....let it sit. Still nothing, couldnt adjust or brighten..... So i task 29 AGAIN... then flashed 21907 build GTX themed again... once flashed, unplugged it & back into wall charger... Installed lumos.... SUDDENLY!!! the sensor worked, and was accepting light AGAIN! ...
So i ran the LUMOS wizard, followed instructions and my phone was SOD FREE!! Let it sit over night, was fine....I wanted to see now if i could overwrite / flash over GTX themed with DiNiK glass cause i liked it better... so i DID NOT USE task29 this time, just reflashed over GTX themed one With DiNiK glass... same build 21907 and followed all my same steps, with wall plug, installed lumos, did the wizard,.... WALAaa.... works still like a charm. Have been using and testing it for 5 days, SOD is gone as far as i know.... ALSO in options, under setting / system / power / batt... i turned off the option to charge it when plugged into PC....Not sure if it helps or not. But Something i did is doing the trick. Seems between the backlight, and something to do with my 2.0 usb cord thats messing it up.
Seems to be cured... Still not sure exactly what fixed my phone. But between all that, IMO i believe installing lumos and glight triggered something also i think not letting it charge thru the PC, and only using a wall plug for charging has something to do with it....Either way . now its back to normal working just great... ONLY running LUMOS cab, and all the games i want. Energyrom Build 21907 DiNiK Glass Themed june 27th.... HOPE this helps!!! Have a wonderful DAY!

Calling problem

Hello,
I've started experiencing a weird problem with my Desire. Generally everything looks fine, but when I try calling somebody
instead of hearing "waiting tone" it goes back to dialer app.
And AFAIK I'm not available as well - I didn't check it thoroughly.
The thing is rebooting the phone (by rebooting device, switching airplaine mode on and off) fix the problem - for the moment - so I'm able to make a call - but my problem is that all the time I'm afraid that in a moment I won't be accessible by other people.
Other solution I've been using, is switching it to GSM only - and I think it solves the problem permanently - but since I'm using a lot of Internet I want to use 3G.
I'm not sure If it really is a 3g (maybe switching 3g/gsm) or other thing - I don't want to reset it default to just check if it will solve my problem.
I'm using original Froyo (from Polish Era) - I didn't do anything to my ROM, and I was thinking of trying maybe some custom (clear) rom - but since this was working fine - I didn't want to mess anything up.
If you have any suggestions how to fix it - please help. I've searched google and xda, but I didn't find a similar problem.
Generally I'm more than happy with my Desire, and I find it to be almost perfect, but this thing is affecting basic functionality, and I really need to do something with it.
P.S. I'm wondering if had something to do with Market, because it started the same day I was upgrading several apps at the same time - and probably because of the connections problem I restarted my device to finish everything. But I'm not really convinced that it was the cause of my bug.
Strange problem - haven't heard of that before.
I would suggest ensuring you have the latest Radio installed and/or also installing a clean rom but try the radio first.

[PROBLEM] Random freezes/crashes on Desire

Hey,
I know theres a lot of threads about htc/android phones freezing and crashing/rebooting but none of them really described my exact situation. And since it's getting worse and worse and driving me crazy, I wanted to ask for help.
As the title suggests my HTC Desire keeps freezing and crashing (sometimes rebooting, too).
It all probably started shortly before I first rooted my device, following the great sticky noob-tutorial. First problem was, that sometimes my phone wouldn't wake up from standby, especially after I a missed call (rooting didn't solve that problem).
Some time later, now rooted and with a custom ROM, I noticed, that sometimes when I wanted to use my phone, it showed the PIN-screen, which obviously means, that it rebooted quietly (don't remember if this also happened before rooting).
A few days ago it started to completely freeze, when connected to the charger. Orange LED showed it was charging but no reaction to pressing any buttons or disconnect the charger.
Since yesterday it also crashes randomly in standby mode (can't wake it up) or e.g. when watching a video (just freezes the device, no reaction to button-pressing, screen stays on etc.)
now I am running the stability test with the charger connected - no problem for 1h10min til now...
The ROM I am running is the latest cool sense (problems also existed before the latest update)
No modification of CPU (I used to use SetCPU but since I thought that would cause the problems I uninstalled it -> no improvement)
What could be the problem here? (And how can I solve it, of course?)
Anything else than a full wipe, which could help? (that would be my last option...)
Thanks for helping...
it just happened again -.-
I was just backing up some apps with titanium backup and in the middle of scrolling through the list - freeze!
dunno what to do...
is this hardware or software related?...
Hello.
It would be pretty easy if it is a soft problem. This kind of problems are usually dealt with by installing another ROM and see if the problems persist. So if you want to try and eliminate the last option, go and install another ROM, it can be a Stock ROOT-ed ROM, Sense or anything.
The fact that you mentioned your phone was crashing even before rooting got me thinking it is a motherboard fault. I've read some threads in which people had the same problems, and in the end they all got to the same conclusion: motherboard fault. The only resolve with this is to get it to guarantee.
So first of all try installing another ROM and if the problems persist, you will need to install a RUU and see if this one eliminates your problem. If not then I don't know if there is anything else you could do, besides getting it to the guarantee.
I wait for your progress.
Hi,
thanks for your reply.
The funny thing is, that I didnt have those problems with this ROM in the beginning. Everything was fine, that's why I was using it the whole time. But as I said before, it became worse by and by... thats why I thought it could be an app or so...
that would be a recent list of apps: appbrain.com/user/marioiram/
Cannot even sync my newest list, because after freezing while watching a video, it froze again shortly after reboot... still getting worse
Try reinstalling the ROM or installing another ROM.
hm.. just when I was thinking about following your advice, my desire stopped freezing xD
no crash, no freeze oder reboot since my last post.
I even tried to force it by watching videos, playing games, connect to the charger etc.
everything is fine... strange.
Will see for how long
Well this is good news. Just keep in mind what you can do if the rebooting comes back. Hope it doesn't
Well, it did xD
Now even shortly after reboot. I'll try ROM changes as soon as I get home but there's something I noticed: it often freezes when it's supposed to display a whatsapp notification and sometimes it seems there's a problem with the sdcard (just bought a new one because my old one went nuts). Sometimes the notification 'sdcard was removed unexpectedly' (translated from German) is appearing, but after waiting a few minutes everything is fine again...
Well I'll try some stuff when there's time...
Sent from my HTC Desire using XDA App
Hi:
I just wanto to let you know that I had the same issue, so I decided to send it to SAT, they changed the motherboard...
my problem now (with the new motherboard) is everytime I root my phone and use a cooked ROM, then freezes/crash again... ONLY works with the official ROM...
please let me know if you solved you problem pls... and how? of course...
I copy the link of my post (just in case helps to you)
http://forum.xda-developers.com/showthread.php?p=15103560#post15103560
best
SCeesarin
Hmm... I don't know what i did (nothing, actually) bit since my last post it runs stable... Absolutely nothing like freezing or crashing... Strange
Sent from my HTC Desire using XDA App

[Q] process com.android.phone not responding..

im currenty using liteROM 0.9.0 first 3 days work fine, but after i found this problem.. can anyone help me..
+1.
My phone.android repeatedly shut down in Gingerbread. Only fix i could find was upgrading to ICS.
when arldft
Hmmm.... that is weird, i´m also using LiteRom 0.9, never had that issue, first time i flashed the custom rom i did see that message a couple of times, but no big deal just reeboot and no probs. after that though i decided to install the rom from scratch, never had an issue with it since. only problem ive had is the toggle for gps sattelites and mobile connection giving me some issues, nothing a reeboot cant resolve.
my advice would be to backup all your info & apps and start from scratch. or boot to CWM and fox permissions.
hope i helped
I had similar issues with GB. I was using the latest Osimood rom. Upon receiving a call, my phone screen would go blank (the way it normally does when switching to a call) but then it would freeze. The ringtone would not ring and after a few seconds of this, the phone would go back to the last app and the network signals would be gone. After a few more seconds, the network signals would be back. The same thing would happen if I received another call. The only fix was to reboot the phone.
The annoying part was that there would be NO way for me to tell who was calling me since I would never see their name and no entry would be made in the phone log. I didn't have any success with treating that problem. While it didn't happen very often, the few times it did would be very annoying since I'd often find out several hours later that I had missed an important call.
I've just switched to Pacman rom today in the hopes that this was a rom issue and will be gone now. Let's see.

Question Graphical glitches on A52s (Culprit found)

Update: Found the culprit! When the phone is on a 2G network, it happens always when there is any (voice or data) communication and glitches are stronger when the signal is weaker. It's probably caused by an interference and bad shielding of components. Similarly how 2G network makes buzzing sound in radio speakers, on A52s it makes a mess on the screen.
At least one user (bellow) solved it by RMA - sending the phone to service and getting back new/fixed one.
Update 2: Problem fixed. I sent the phone to service center with description how to replicate the issue (phone must be on 2G network, ideally low signal, data or voice transfer is happening). Got it back after 2 weeks. Report says they replaced the display and also battery for "construction" reason (as they described it) and issue seems to be solved!
To conclude: It is indeed hardware issue and is fixed by replacing the display. If this happens to you too, don't wait for software update or anything else, send it to a service for a fix covered by the warranty!
Since few weeks ago, maybe since last update a month ago (security update from 1st October 2021), I'm randomly getting graphical glitches on my A52s.
It usually happens when I wake my phone after few hours of screen off but today I also saw few flashes even when playing a (graphically not demanding) game.
There is colour noise flashing over parts of the screen. It is usually just few random quick couple of 1/100 sec flashes, sometimes it stays a second and it disappears and everything is okay after that.
I also saw noise not covering the screen but flashing instead of wallpaper... Like there's a corruption in graphical memory, driver or whatever.
It doesn't make a difference whether the phone is freshly rebooted or running a week or two.
Does anybody else have this issue?
Is my phone (the memory, screen cable or something else) dying or is ist just a bug in current system update? I don't experience any other instabilities or problems.
(I'd send my phone to RMA but since I didn't find any consistent way to replicate this, it would make just as much of a difference as locking my phone in a drawer for a month.)
I'm appending mock-up screen shots how some of the flashing glitches look.
Clear system cache, hard reboot.
Huh, I didn't really ask for help, but yeah, that's a good idea with clearing the cache.
I rebooted to recovery and wiped the cache partition.
(I also accidentally hard rebooted when trying different button combos to enter the recovery LOL, so I did both things. In the end I had to enter the recovery using "adb reboot recovery" command because none of the button combos I found worked for me.)
I'll report back in few days whether it solved the issue or not.
Your screen is dying. This is hardware issue
Easy fixes are a good thing...
EugenStanis said:
Your screen is dying. This is hardware issue
Click to expand...
Click to collapse
A possibility as is a mobo failure but no harm in trying a few simple fixes first.
Samsung has been having a lot of issues with their displays this year...
It doesn't really feel like screen itself is dying when glitches can appear under the home screen icons in wallpaper or in the application area with status and nav bars being untouched. But I guess it can be; I have no idea how the image on screen is being redrawn.
But it happens especially after phone display is off for longer period of time. The phone then is quite sluggish, presumably because the system paused or killed some apps and is waking them up. And glitches mainly appear then.
That would suggest to me either a system memory being corrupted or something weird happening in the cache, depending on where these apps go when they're paused/killed.
jenda.69 said:
It doesn't really feel like screen itself is dying when glitches can appear under the home screen icons in wallpaper or in the application area with status and nav bars being untouched. But I guess it can be; I have no idea how the image on screen is being redrawn.
But it happens especially after phone display is off for longer period of time. The phone then is quite sluggish, presumably because the system paused or killed some apps and is waking them up. And glitches mainly appear then.
That would to me suggest either a system memory being corrupted or something weird happening in the cache, depending on where these apps go when they're paused/killed.
Click to expand...
Click to collapse
Factory reset. Before loading apps confirm if ok.
Then be careful what 3rd party apps you load.
If the reset doesn't work, reflash it to a known good version.
If all that fails it's likely hardware.
The most likely cause is a 3rd party app given right to overlap other apps and this 3rd party app has crashed. Uninstall apps in opposite order of installing until problem is solved. Or factory reset.
I have the same problem, sent phone for repair.
In my case, the issue is occurring when phone is on 2g network. You could try going to network and set it to 2g only, check if it's happening, and then set it to 3g and see.
Cheers!
Bvid said:
I have the same problem, sent phone for repair.
In my case, the issue is occurring when phone is on 2g network. You could try going to network and set it to 2g only, check if it's happening, and then set it to 3g and see.
Cheers!
Click to expand...
Click to collapse
So is it a hardware issue or software?
abood.mhd said:
So is it a hardware issue or software?
Click to expand...
Click to collapse
It was a hardware issue, got a new phone.
Bvid said:
It was a hardware issue, got a new phone.
Click to expand...
Click to collapse
I have the same problem, and I can't replace the phone, the question is here, will this problem increase and affect the screen more?
Same problem here...but mostly when I am on 2G network (anyone please try and post results)...Thinking of sending phone to service...will see how it goes
Huh, I didn't get notifications for my thread, so I didn't know about all the replies!
I tested different things in last few weeks and I came to the same conclusion - that it only and always happens when my phone is on 2G network. If 2G signal is strong, it's occasional small glitchy line here and there. When the signal is really bad, it just messes up the whole screen - I had my phone ringing with screen being all just noise and mess. So I guess it's probably because of interference similarly how the 2G network connection makes buzzing sound in a radio speakers. Except here it makes a mess on the screen.
Now that I know how to reliably replicate the problem, I'll back the phone up and RMA it after christmas.
i have the same problem from the first day, it happens only in 2g signal ...and only if 2g signal is weak... i sent the phone to Samsung , they inform me that they know the problem and it will be fix ..on another update ...it s software problem they told....from this day i have take 3 updates and nothing happened....the phone still have the problem
Same here, took my a52s to a Samsung authorized repair center, after 3 repairs (the third one being the display change) it seems that the problem is solved. To me, it has nothing to do with software.
So, it's a hardware issue, I face the same problem for almost 2 months, and I don't know what to do
Only solution is to contact Samsung and have it fixed
VirtualGamer20 said:
Only solution is to contact Samsung and have it fixed
Click to expand...
Click to collapse
Its not that simple...Some people send phone for repair...twice and still not fixed

Categories

Resources