Hey.
I have a big problem with my desire. The phone is fully working, but when it goes into standby, and I try to turn it on using the "power button" at the top, the keys light up, but nothing comes on the screen It just doesn't turn on again.
Any ideas? Thanks!
In the general section on the desire forum there is a topic related to defective proximity sensor. i,m a new forum-user so i can't make a link yet
Thanks for the help so far, but couldn't find anything that solved my problem :/ Have to restart the phone every time it goes into standby
Like many others, I am also experiencing this standby-of-death (SOD) problem: the lights in the buttons under the screen turn on, but the screen itself stays black. I have found out that it has to do with switching from 3G to 2G networks: the problem occurs after I have been at places where there is no 3G signal, but only 2G. For example, after a car trip or when going into the basement.
A workaround for this problem, is to type the code *#*#4636#*#* in the dialer. You will then end up in a hidden menu. By choosing "Phone information" (first item) and then scrolling down in the next screen, you can change the "Preferred network type". By default, it was set to "WCDMA preferred" on my phone. After I changed this setting to "WCDMA only" (so, 3G only), I have not seen the SOD issue anymore (for 4 weeks now, before it happened almost daily).
A disadvantage of this workaround is that the phone will never use 2G anymore. So, when you are at a place where there is no 3G signal, you will be disconnected (i.e. you cannot receive phone calls). As an alternative, I have now reverted the setting to the original value ("WCDMA preferred") and I have installed an older radio image (version 32.44.00.32U_5.09.05.30_2), which is considered to be more stable by many people. I'll test and see whether the problem reoccurs. If the problem stays away, it is apparently a software (radio image) issue. If not, it must be a hardware issue.
Anyway, if anyone has additional information about the root cause of this standby issue, please let me know!
Stamgastje said:
Like many others, I am also experiencing this standby-of-death (SOD) problem: the lights in the buttons under the screen turn on, but the screen itself stays black. I have found out that it has to do with switching from 3G to 2G networks: the problem occurs after I have been at places where there is no 3G signal, but only 2G. For example, after a car trip or when going into the basement.
A workaround for this problem, is to type the code *#*#4636#*#* in the dialer. You will then end up in a hidden menu. By choosing "Phone information" (first item) and then scrolling down in the next screen, you can change the "Preferred network type". By default, it was set to "WCDMA preferred" on my phone. After I changed this setting to "WCDMA only" (so, 3G only), I have not seen the SOD issue anymore (for 4 weeks now, before it happened almost daily).
A disadvantage of this workaround is that the phone will never use 2G anymore. So, when you are at a place where there is no 3G signal, you will be disconnected (i.e. you cannot receive phone calls). As an alternative, I have now reverted the setting to the original value ("WCDMA preferred") and I have installed an older radio image (version 32.44.00.32U_5.09.05.30_2), which is considered to be more stable by many people. I'll test and see whether the problem reoccurs. If the problem stays away, it is apparently a software (radio image) issue. If not, it must be a hardware issue.
Anyway, if anyone has additional information about the root cause of this standby issue, please let me know!
Click to expand...
Click to collapse
OMG I love you!
Seriously this has been doing my head in for weeks! I have posted a couple of times in this forum. First time, constantly remvoing and replacing the battery left me with a bricked phone. HTC revived it under warranty but after a week I got sick of Sense (and the poor battery life) and tried rooting again (tried Redux and CM7) but the problem came back. Makes sense because it works fine around Bristol (loads of 3G) but constantly SODs in Bournemouth (flicks between 2G and 3G at my desk). Also, just had data off for a few hours and didn't get SOD once.
I am not up on the lingo yet as I am fairly new to rooting but running Baseband version 32.49.00.32H_5.11.05.27. Is this the radio?
Please keep me posted on the older radio version. Shouldn't need a long test period, just need to go from a known 3G area to a known 2G area while locked.
Baseband version 32.49.00.32H_5.11.05.27. Is this the radio?
Click to expand...
Click to collapse
Yes it is the radio.
I have got GingerVillain (Based on CM) and I use the Power Control widget to switch between 2G and 3G. You can customise the widget (just add it to a screen) to get this feature.
I haven't got any 3G around my house so I don't need to activate it all the time .
Yeah Redux has a similar thing so I will use that until a proper solution is found.
Small update: enabling 2G only didn't fix the issue (I think 3G only is okay) so perhaps the issue is with 2G rather than switching between the two.
Instead I am using an app called "3G Data Only!" so that 2G can still be used for calls but not data, working great so far.
I have tied the latest Radio (32.56.00.32U_5.17.05.23) and the problem does not go away.
How come this problem doesn't occur to (many) others? Could it be related to your network provider? Maybe you could change the SIM with another, from another network, and see what happens. Also, you could make use of the phone warranty - if it's still covered by it.
Icysoul said:
How come this problem doesn't occur to (many) others? Could it be related to your network provider? Maybe you could change the SIM with another, from another network, and see what happens. Also, you could make use of the phone warranty - if it's still covered by it.
Click to expand...
Click to collapse
On o2 (in UK) right now, will try out another sim later. As for warranty, never had any issues on non-root Froyo Sense so can't do anything.
Icysoul said:
How come this problem doesn't occur to (many) others? Could it be related to your network provider? Maybe you could change the SIM with another, from another network, and see what happens. Also, you could make use of the phone warranty - if it's still covered by it.
Click to expand...
Click to collapse
I have tried 2 different sim cards, same provider, but the problem persists.
hurin8 said:
I have tried 2 different sim cards, same provider, but the problem persists.
Click to expand...
Click to collapse
Try to change the network, say, from O2 to 3 or Vodafone. If your Desire is branded, there is a free way to unlock it - just look for Desire SIM-Unlock utility in the forum, by sieempi
Been running radio 32.44.00.32U_5.09.05.30_2 for a couple of days now and the issue seems to have gone away.
Stamgastje said:
A disadvantage of this workaround is that the phone will never use 2G anymore. So, when you are at a place where there is no 3G signal, you will be disconnected (i.e. you cannot receive phone calls). As an alternative, I have now reverted the setting to the original value ("WCDMA preferred") and I have installed an older radio image (version 32.44.00.32U_5.09.05.30_2), which is considered to be more stable by many people. I'll test and see whether the problem reoccurs. If the problem stays away, it is apparently a software (radio image) issue. If not, it must be a hardware issue.
Click to expand...
Click to collapse
I also have this SOD issue with the older radio ROM versions, so installing an older version is not a solution.
d10brp said:
I have tied the latest Radio (32.56.00.32U_5.17.05.23) and the problem does not go away.
Click to expand...
Click to collapse
I can confirm that. I have tried most of the radios listed here and here, they all have the SOD issue.
d10brp said:
Been running radio 32.44.00.32U_5.09.05.30_2 for a couple of days now and the issue seems to have gone away.
Click to expand...
Click to collapse
Guess that's just pure luck...
d10brp said:
Instead I am using an app called "3G Data Only!" so that 2G can still be used for calls but not data, working great so far.
Click to expand...
Click to collapse
Great, I'll try this application! Would be very nice if that fixes the problem without disabling 2G phone calls. I never use 2G for data (too slow anyway), but I would like to be able to still make phone calls when out of range of 3G cells.
Icysoul said:
How come this problem doesn't occur to (many) others? Could it be related to your network provider? Maybe you could change the SIM with another, from another network, and see what happens. Also, you could make use of the phone warranty - if it's still covered by it.
Click to expand...
Click to collapse
It might be, I don't know. I'm using a Telfort SIM, connected via the KPN network (Netherlands).
3G data only works a treat for that, you can make calls.
Found with the old radio that it is a lot more stable than the new radio but not 100% perfect. Where I work I only have 2G and it would SOD all the time but now it doesn't. However on a journey I make with intermittent 2G/3G I did get a SOD.
Sent from my HTC Desire using XDA App
3G Data Only doesn't work well enough. The SOD issue does occur less frequently, but the phone still hangs sporadically. So, if have disabled 2G completely again.
You should try Insertcoin. I haven't had this issue since I started using IC v32 a2sd.
Hi there. So i get the same thing on mine. I thought I should report my experience.
Had it over a year old then all of a sudden it started acting like this
heres what i tried
Factory reset, rooted it twice, boot with no sim, no SD card, dismantled it via instructions I found on an android forum to check for loose connections, gave it to a friend who ran some different roms, overclocked it, underclocked it. Its currently on the Oxygen rom, no difference. I tried the secret menu from page one of the comments. I tried living with leaving the screen on for 30 mins..but its so impractical
I should add that if i leave it for say a couple of hours, the damn thing comes on just fine. Its only from being on, to off, then back on..
I think its hardware related, maybe something to do with the power being held back for the screen or something. All i can say is that its really doing my tits in and i'm currently using my old phone which is functional but not as fun.
What can i do next...send to HTC, i'm out of warranty but their repair centre can still have a look, or buy a faulty phone off ebay and harvest some parts...
I dont want to give up on it, because apart from this the phone works fine.
guys i had this problem too, when i force to use 3G only everything works perfect but in area with no 3G signal your phone become useless cuz you are out of network, i also had a self-rebboting problem and i sent my lovely desire to htc repair center, they replace mobo and now i am waiting to receive my phone back and i will test this issue, if everything will works correctly in 3g/gsm etc you guys need to do the same and sent your phone to repair,
Hi Guys,
So, I've been using the GNex for about a month. I moved to this phone from a Moto Atrix and here is what I have noticed and have looked around but didn't see any good answers to these questions I am having. Hopefully I get some answers here.
Device info:
GNex GSM version on ATT.
Running JB 4.1.1 Stock with Trinity Kernel (rooted and bootloader unlocked).
Issue #1: I get really bad reception at work. But, when I leave the building, my phone doesn't automaticaly connect back to the network. Sometimes, if I don't check my phone, it's been like that all night long until the next day when I have tried to make a call and it said "No Network Available" and I have to either reboot or toggle airplane mode to get back on the network. Am I missing something? In my past experience with other devices, they try to automatically connect back to the network when they loose connectivity. Also, if I get in an elevator during a call and the call gets dropped due to network unavailability, it doesn't connect back to the network and I have to toggle airplane mode. Has anyone else had this issue?
Issue#2: This is with the stock mail app. Specifically the search in this mail app. No matter what, it always returns zero results. Has anyone had this issue with the Mail App? If I use the Gmail app, it works fine. That's what I am using now, but am curious as to what I may be missing that make it not return any search results in the stock mail app.
Q3: Speed Dial: How do you set speed dial on the dialer? Is it even supported?
thanks in advance,
vG
verruckterGeck said:
Issue #1: I get really bad reception at work. But, when I leave the building, my phone doesn't automaticaly connect back to the network. Sometimes, if I don't check my phone, it's been like that all night long until the next day when I have tried to make a call and it said "No Network Available" and I have to either reboot or toggle airplane mode to get back on the network. Am I missing something? In my past experience with other devices, they try to automatically connect back to the network when they loose connectivity. Also, if I get in an elevator during a call and the call gets dropped due to network unavailability, it doesn't connect back to the network and I have to toggle airplane mode. Has anyone else had this issue?
it could be to do with your radio, what version is it? baseband version in about phone. im no expert but when i flashed a jellybean rom i had to update my radio afterwards cause my signal was dropping alot. i also had the same problem later on but that was down to my network operator. before i realised it was them i googled my problem and a few forums suggested that my sim card was goosed. so maybe check those three possibilities? i cant help with the other two issues unfortunately but good luck sorting it out!
Click to expand...
Click to collapse
Just wanted to see if anyone else has been experiencing this or maybe knows a way to fix this. I have 2 issues with the phone calling on this phone. I had the 925T since launch and never had an issue with it. ever since i sent it in for repair, I've had a strange issue. Fist one is dialing out. When attemting to make a call, it takes anywhere from 3 seconds to 40 seconds before the call actually gets connected. this is highly annoying as i dial a number and it feels like forever before the call actually connects. my other issue is after the phon ehas been one for a few hours, I dont get any incoming calls. the phone will not show me any incoming calls at all so I don't even know when someone calls me. Ive tried everything i can. tried changing sim cards, updated the bootloader and modem, tried different roms, kernels, stock odin, everything. and its the same story no matter what I do. Anyone Have an idea of what it could be? It only works well after a fresh reboot. calls works without issues. hours later, problem comes back
I've had the same exact problem but I attributed it to using an AT&T Sim card on an unlocked T Mobile phone.
I've now rooted and installed Xtrostolite Rom with latest modem and bootloader. I've yet to have any issues. Good luck.
Anyone else have this issue?
I have this issue. It seems if i leave wifi off i do not ever have this issue. I live in a crappy coverage area so i have to have wifi on at home. I just reboot when i leave. I hate this phone....
btothec said:
I have this issue. It seems if i leave wifi off i do not ever have this issue. I live in a crappy coverage area so i have to have wifi on at home. I just reboot when i leave. I hate this phone....
Click to expand...
Click to collapse
You think the problem is WiFi related?
Yes. If i leave wifi off i never have the issue.
Still is happening. whether I have wifi on or off it always happens. It seem,s to be an issue related to VoLTE. When I turn LTE off, the issue dissapears. Updated baseband and bootloader to latest version and issue is still there. Have a custom rom and the issue is still there. go back to the tmobile rom and the issue is still there. thinkiing of going back to a tmobile firmware and turning off VoLTE in the firware then reflashing back to custom rom and seeing if that helps. if not, im selling the phone and getting the F version of the regular S6 and calling it a day. im done with carrier branded phones.
Interesting enough I haven't had this issue in the last 3 to 4 days. I wonder if it is AT&T related.
I have this issue. All the time. Unlocked from tmo, using straight talk at&t. This phone is the worst.
Anyone not on AT&T network having this issue?
I wonder if flashing the AT&T modem on TMO model will help.
cbutt said:
I have this issue. All the time. Unlocked from tmo, using straight talk at&t. This phone is the worst.
Click to expand...
Click to collapse
Maybe you should get a phone from att.
If att service is better than tmobile then maybe there phone is better than tmobile's phone.
Pp.
PanchoPlanet said:
Maybe you should get a phone from att.
If att service is better than tmobile then maybe there phone is better than tmobile's phone.
Pp.
Click to expand...
Click to collapse
I've been able to switch between carriers on any phone that has the supported bands since the galaxy s2. The issue is with this phone. My mistake in buying it.
Please help!
same thing here its unbearable, using latest unibase and xtrestolite
I have tried a few roms and a few kernels. I have tried differ apns but att Sim in this phone doesn't work like it should. I was going to get a TMOBILE note 5 to use on att but now I know it's not worth the risk.
@stu5797, yea man, I wish I had a solution. I'm happy it's not just me, but pretty bummed that there seems to be no answer other than it just doesn't work properly.
I've noticed the issue only happens during peak hours. Can anyone confirm?
I was having similar problems after the 5.1.1 update so after a few troubleshooting sessions with TMO, they sent me a new phone. 2 weeks now and no more problems. First phone that I have not rooted and flashed..... I was also told by a store rep that a lot of people were having issues since TMO is upgrading towers for 12 band.
osmosizzz said:
Just wanted to see if anyone else has been experiencing this or maybe knows a way to fix this. I have 2 issues with the phone calling on this phone. I had the 925T since launch and never had an issue with it. ever since i sent it in for repair, I've had a strange issue. Fist one is dialing out. When attemting to make a call, it takes anywhere from 3 seconds to 40 seconds before the call actually gets connected. this is highly annoying as i dial a number and it feels like forever before the call actually connects. my other issue is after the phon ehas been one for a few hours, I dont get any incoming calls. the phone will not show me any incoming calls at all so I don't even know when someone calls me. Ive tried everything i can. tried changing sim cards, updated the bootloader and modem, tried different roms, kernels, stock odin, everything. and its the same story no matter what I do. Anyone Have an idea of what it could be? It only works well after a fresh reboot. calls works without issues. hours later, problem comes back
Click to expand...
Click to collapse
Are you still having this issue? I have the same issue and the same phone but mine is unlocked and working on cricket network. So yeah same problem taking forever to connect a call and no receiving calls mos of the time. No ring no notification of missing call. I been doing some research and find a temporary fix. Try going to settings -mobile networks and switch from lte/wcdma/gsm to wcdma/gsm or gsm only. But before do a test. Turn off data and try to make a call see how fast it connects then have someone to call your phone. If it works then this trick will work for you. Of course you gotta sacrifices lte speed . Basically having 4g only but at least will fix your calls. These problems seem to ve related to volte i been trying to disable it but there is no such option under phone app setting. I just dont have it. (I cann show some screen shots) so if someone knows a secret code or app whatever to turn it off i will appreciate it. My phone is a t mobile galaxy s6 edge.
PHP:
---------- Post added at 11:00 PM ---------- Previous post was at 10:45 PM ----------
stu5797 said:
I have tried a few roms and a few kernels. I have tried differ apns but att Sim in this phone doesn't work like it should. I was going to get a TMOBILE note 5 to use on att but now I know it's not worth the risk.
Click to expand...
Click to collapse
Try this..
Are you still having this issue? I have the same issue and the same phone but mine is unlocked and working on cricket network. So yeah same problem taking forever to connect a call and no receiving calls mos of the time. No ring no notification of missing call. I been doing some research and find a temporary fix. Try going to settings -mobile networks and switch from lte/wcdma/gsm to wcdma/gsm or gsm only. But before do a test. Turn off data and try to make a call see how fast it connects then have someone to call your phone. If it works then this trick will work for you. Of course you gotta sacrifices lte speed . Basically having 4g only but at least will fix your calls. These problems seem to ve related to volte i been trying to disable it but there is no such option under phone app setting. I just dont have it. (I cann show some screen shots) so if someone knows a secret code or app whatever to turn it off i will appreciate it. My phone is a t mobile galaxy s6 edge
Didn't work for me. I turn off data and I still have to wait until the call goes through