I have noticed in the past few weeks that my signal reception has gotten worse. Places where I usually get 3G and HSPDA, now I only get Edge. It's seldom I get 3G anymore anywhere.
I am currently using K's ROM v1.30b. I tried a bunch of different radios as well, but no affect.
I am wondering is there something that can cause the signal to drop like that? Is it ROM dependent?
BTW, I'm on at&t in the midwest.
No one knows what can cause this?
Unless you have handled your device badly then it sounds like a transmitter issue. What radio version are you using? Also go into: start>system>phone>band
tell us what settings are selected.
The reception and etc....is attributed to the radio stack version, nothing else.
mrvanx said:
Unless you have handled your device badly then it sounds like a transmitter issue. What radio version are you using? Also go into: start>system>phone>band
tell us what settings are selected.
The reception and etc....is attributed to the radio stack version, nothing else.
Click to expand...
Click to collapse
Thank you for your reply. I've used the following radios:
1.47, 1.48, 1.50, 1.54 all with approximately the same results. Meaning mostly Edge network everywhere and very very rarely 3G. Whereas it was 3G mostly before.
My settings are :
Select your network type: GSM (Should this be Auto?)
Select your GSM/UTMS band: Auto
Dont forget that sometimes the problem can be on AT&T's end...
The tower by my work has occasionally gone screwey for a day and all I can get is EDGE, or sometimes 3G with only 1 or 2 bars before switching to another tower on EDGE (normally full bars).
It's happened 4 times in the last year, each lasting only one day.
Go to a friends house or somewhere else and see if 3G comes back. If so then it might just be your local tower, esp. since you have tried so many radios without a difference.
EDIT: just read the above post..
Network type MUST be Auto or WCMDA for 3G to function!!
anubus12 said:
Thank you for your reply. I've used the following radios:
1.47, 1.48, 1.50, 1.54 all with approximately the same results. Meaning mostly Edge network everywhere and very very rarely 3G. Whereas it was 3G mostly before.
My settings are :
Select your network type: GSM (Should this be Auto?)
Select your GSM/UTMS band: Auto
Click to expand...
Click to collapse
Your troubles as shown in the post above this one....your mode is set to GSM....hence why your device will not work on UMTS/3G unless the mode is set to WCDMA or auto.
I'm having trouble with my EVO staying in 3G coverage. My phone is fully rooted and running Froyo (The problems were the same with the Eclair build however), have the 2.05+ radio installed (however the problems were the same with the 1.39 radio as well) and I'm living in Michigan.
At any given time my phone will slip into 1X coverage and will seem to lock in there. When I first received the phone I felt like the phone quality was subpar compared to the Hero I had prior. I'm not sure if its been a firmware issue or network issue or simply a phone issue (starting to think the later), but hoping its a simple fix with something else.
About a week ago I was on a trip across Michigan which should have had 3g coverage the entire way (I was a passenger and trying to use wireless tethering to do some work along the trip). I would constantly go into 1X and would have to restart my phone to get back in 3G. Even at home I'll go into 1X and will have to reboot my phone to get it back to 3G.
I've tried Real Signal as well during these times and it also shows no 3G signal.
Anyways, anyone else experience this? Is it likely a bad radio or something else. I hate to have to return the phone and go through that process plus root again but I might have to at this point.
Thanks for any help that can be provided!!
Hmmm, whereabouts in MI? I am all over the south east and have never seen my phone drop out of 3G yet.
Have you tried wiping everything and trying stock rom w/OTA 1.47 just to make sure it isn't the ROM?
I am having the exact same problem. Using 2.0xxx radio and Fresh 0.5.3. I recently exchanged my phone and got a new one. The first phone did not do this
Try this:
When it shows you no 3G coverage, instead of restarting, go to-- SETTINGS> WIRELESS & NETWORKS> scroll down and look at "Mobile Network". When i get the 3g problem it says "Connection Failed". I think uncheck that box and re-check it and it connects back to 3g again (for a time, but then I have to do it again).
My MOBILE NETWORK settings are: Data Roaming = OFF, Always-on mobile data = ON, and CDM Roaming mode is set to: SPRINT only. Call guard = ON but i dunno what that means.
I dunno wtf is going on with this. Im in Houston and this issue is really pissing me off because i actually got a Novatek screen this time and don't want to risk taking the phone back and getting the Epson...
Anyone else experiencing this retarded issue?
Elegant: I'm in SE Michigan as well. I've tried several roms and have had issues with them all. I'm currently using a Froyo rom with similar issues as I've had with stock and other eclair roms.
As for checking/unchecking the box as you stated in Froyo I don't have that option available... I'm sure there's another way to get to it but I can't through settings. I think there was a #* code to get to where you are talking about but I'd have to look again.
It is a very annoying issue and like yourself I don't want to have to return my phone if there's a simple fix.
On a side note: How do I find out what panel I have? I've been considering the kernel that would get rid of the 30 fps cap but haven't yet pulled the trigger in part because I don't know which panel I have - and because I need to learn a little more about it before I go ahead with it.
http://forum.xda-developers.com/showthread.php?t=719763
Post 3 tells how to determine screen
Thanks for your help - got the kernel and now get around 40 FPS. Now if I can just figure out why the phone goes in and out of 3g on occasion. Its really not as big a deal when I'm at home but when I travel it is a pain.
well i returned my phone and got one with an Epson screen. im using Fresh 1.0.1 and it is even worse. i cant even use 3g data for more than 5 seconds before it disconnects. i've read some stuff about APN but dont know how to refresh/update them. i've updated PRL and Profile and nothing helps. how am i having this problem with 2 phones running 2 different ROMs? last rom was fresh 0.5.3 and now it is fresh 1.0.1...
anyone help with this APN issue? (i dont even know what APN stands for)
i actually am using the kernel for 55 FPS for Epson screens. would that be a factor either?
I'm and having the same issue with 3g.
Every thing worked fine with the first stock root of 1.32.651.1, PRI 1.40_003, PRL 60666.
With the second root of 1.47.651.1, PRI 1.34.651.1 now my 3g is unstable.
I don't know what FPS has to do with any of this, but I put radio radio-1.39.00.04.26 and it seems to improve a tiny bit, but I don't know how to update back to PRI 1.40_003.
Not happy
Also having problems in SE Michigan. Just started today after installation of Fresh 1.0.1 and the new radios. I also have a co-worker with and unrooted EVO and the latest OTA/Radio with the same problem.
I have a rooted EVO (DC 3.2.3). My wife has a stock EVO (fully updated).
Last night our phones started bouncing between roaming/sprint 3G, while we were sitting at home.
We started getting this error if we turned off Data Roam:
"Data Call Failure
Error Code 67: Registration failure. Your PCS Vision username and/or password may be incorrect. Please try again."
The error pops every time it tries to connect to Sprint's mobile network and fails.
We also live in Michigan. Perhaps they are doing provisioning?
Rebooting + update Profile/PRL seems to help, sometimes, but not permanently.
I am having the same issue with my 3g coverage.
When I go into my settings and turn mobile network on, it connects but then immediately says connection failed.
Does anyone have any suggestions as this is getting really annoying and frustrating.
Went to a Sprint store last night; apparently Michigan was having some significant network issues (the store reps said their phones kept getting disconnected as well), and that it was expected to be resolved by sometime today. After a reboot last night, I haven't had any more issues myself.
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 all,
I got my Desire from the British carrier "Three" last April when it came out. It was stocked with Android 2.1 but the phone was unbranded and not locked so making life much easier.
I rooted the phone weeks later and flashed a number of various roms and radios (usually newest ones recommended by rom developers) and just played around with them. No problems ever occured and everything went smooth.
However a while ago (about 4 weeks I would say) strange thing happened: when the carrier 3 does not gave 3G coverage it usually switches to other network's 2G roaming service. It is also possible to switch to 2G permanently by forcing it via phone settings. It stopped working in Central London for me while still worked elsewhere (very strange) so I had to rely only on 3G service. I thought it was a network issue at first but now I'm not sure.
Later (or at least so I noticed) the connectivity started fooling around: even when standstill (i.e. NOT in a train, bus etc.) and staying at home the network connectivity just disappears all of a sudden. Sometimes it comes back by itself and sometimes I just do it manually via netowking settings. This is much more common when on the move (i.e. on the train etc. even though it never used to happen before). Moreover, sometimes while manually searching for network it says "your sim would not allow to connect to this network" even though I try to connect to the correct one. Instead I switch "WCDMA only" and "WCDMA/GSM auto" options and connection comes back by itself. Then it disappears again after a while. Even more strangely, connection does not disappear if I am talking on the phone with someone but in other situations (such as browsing internet) it just disappears and I see no bars in network reception indicator and cannot connect to internet or make phone calls.
I know 3 has a reputation (deserved or not) of having "bad" network but I don't think this has anything to do with that. My Desire used to work fine before and never had such problems (except in specific spots which have bad coverage). Moreover, I have another old phone and it works fine without any problems with networking while the Desire messes around. I am sure it has either to do with firmware or, worse, hardware.
I have tried a number of roms, radios and settings and it's the same thing all over.
If nothing works is there a way I can still bring it to warranty service after flashing "unrooted" stock rom if there is one available? I'm so frustrated because I have no idea why this is happening.
Its because three have switched off 2g roaming I have the same problem. Search Google
Sent from my HTC Desire using XDA App