Related
A number of people have experienced a long-standing Android bug on their Nexus One, that when you spend an extended period of time in an area with no signal, the phone never reconnects until a reboot. Even attempting to shut down cleanly or to go into and out of airplane mode results in Android crashing after a minute or so and rebooting that way.
It's hard to draw conclusions from my experience because the occurrence rate was so random (sometimes a couple of times in a single day, sometimes ten days between occurrences), but I installed Froyo Saturday evening and haven't experienced the "no service" bug since then. That's getting close to the MTBF for me over the last few months. The official ticket is still listed in "new" status (after almost a year!), but it's possible that some change in Froyo fixed it without the developer being aware of that particular ticket.
Has anyone who was experiencing the "no service" bug in 2.1 had it happen again since upgrading to Froyo? Now that I can do hands-free bluetooth dialing, that's the biggest remaining blemish on my Nexus One experience, so I'd be thrilled if the bug were, in fact, gone.
Just a little FYI, that is actually a common "bug" independent of Android. I sell cell phones for a living, and many phones, from BB's to WM, Nokia to Samsung, and everything in between has this "bug". Not all do, but I would say 90% of phones have this bug where if you leave coverage for an extended period, it doesn't re-connect when you move back in, and need to reboot. It is because phones are set up to stop searching for a network after X ammount of time without coverage, to prevent the battery drain of constantly searching. When you do go back into coverage, there are two ways to re-register... either reboot, or most phones have an option to manual search and register with a network. I know with my Nexus One this has only happened to me once, at my Dad's (his house is a deadzone for everyone), and all I did was do the manual search and was back up and running, didn't have to reboot.
The Nexus One version of this bug is unusually annoying, though: a manual search for networks turns up nothing (normally I have good signal strength whenever I step outside my house from both T-Mobile and AT&T, but neither shows up after the bug hits), and having the phone crash and spontaneously reboot if you enable airplane mode when the phone is in this state is pretty severe.
wmm said:
The Nexus One version of this bug is unusually annoying, though: a manual search for networks turns up nothing (normally I have good signal strength whenever I step outside my house from both T-Mobile and AT&T, but neither shows up after the bug hits), and having the phone crash and spontaneously reboot if you enable airplane mode when the phone is in this state is pretty severe.
Click to expand...
Click to collapse
That is pretty severe, in that it reboots... but the "bug" of not getting signal back has nothing to do with strength or the N1 is all I am saying. I have at least 2 people a day come into my store with this issue, on all different handsets. Some can get it back just by manually searching (this is different from switching between airplane and back), others have to reboot.
I spent a few 1/2hr chunks today with my FRF50 Froyo'd N1 in a spot in the office that was guaranteed to cause this bug to show up. And every single time it's reacquired the network when I left. Take that with a grain of salt since the bug has been intermittent for me.
Now if only the headset and AVRCP music controls hadn't broken this would be phone heaven.
Yeah, I think it's improved for me with 2.2 as well. One thing that's handy though is an Airplane Mode widget, as cycling the antenna with that usually worked for me before Froyo.
this "bug" drove me crazy! It would tend to happen to me at least once a day. I am scared to say this, but it hasn't happened one single time since updating to "unofficial froyo"
Well, good news all around! I'm not quite ready to declare the bug dead, because I've been disappointed a number of times after tweaking something and having the bug lurk quietly for a number of days, only to pop up again after I had decided it was gone, but it's certainly looking encouraging. Thanks for all the responses. Keep us updated.
I've had the same bug issues, and usually at home when it happens. This radio seems determined to reacquire no matter what.
As for the AVRCP comment, my N1 a la FroYo is working great with my BT3030 stereo Bluetooth receiver. I use the controls all the time.
hey everyone
so my G2, which I absolutely love, has been having a problem lately. in the first week it happened maybe once and i didn't think much of it, but since Friday it's happened like 8 times now. I'll be sitting there with my G2 and all the sudden I have no service whatsoever. Just an x on the signal strength indicator. 1 or 2 times it has come back after a minute or two, but the other times I had to turn the phone off and back on. the weird part is I'm not moving at all, totally sitting still, but when it comes back on I have FULL bars with HSPA+. so it's not like I walked into an area that didn't get good reception.
any idea what's going on? i looked around but didn't see other people having this issue. any ideas?
thanks
alright well at least i'm not alone. i remember that rumored OTA update was supposed to have some radio bugfixes. maybe when the real OTA update comes it will have something to fix this. i hope so.
I have been trying to diagnose this issue on my phone too.
By any chance, do either of you have your BT on at the time?
Happens to mine as described and I have never turned on bluetooth. However this would also happen to my G1 so I think its a network thing personally.
Yeah, it definitely is. I have 2 areas that it happens in, both are while I am in my car and I have BT on in my car. When I ran it without BT, did not happen.
I have found that when I am in those area's, turning off 3G stops it entirely, even with BT on, so when in my car, I set edge and still use my BT and problem is gone.
I hope this is temporary and an OTA can fix the handoff from 3G to Edge and back better so that I can stop this, but this works well enough.
Mine has done that also, maybe once a week for the past 3 weeks.
Judging by the other problems you can have Id say this one isnt that bad. Especially if it only happens once a week haha. This is the only problem I have with my phone.
no bluetooth...
no no bluetooth on, i never do actually... but also my G1 never did this, which makes me think it's NOT a network thing, but I don't know.
also I'm sure this is just coincidence but it almost always happens when my girlfriend is nearby with her T-Mobile Blackberry Curve. i know it wouldn't make any sense, but she's sitting there on the same network with full service and all the sudden my G2 loses service completely, right next to her... although it's not always while she's there, but like the majority of the times she's been there.
I just started another post to check on something, I have widgets that show me when I am connected to 3G and when I am connected to H. I have noticed that the phone is activity managing that connection. In other word, it is in 3G until data is transfered then it goes to H. I wonder if when we are in areas of "questionable" HSDPA signal if this hand off is causing the problems.
I have seen a lot of op's say that there problems come right after some data activity?
Just a guess a this point
i saw someone mention in another post that it happens after/during a text message alot of times. i haven't noticed that myself, but that's something to think about too.
robinsmy1 said:
I just started another post to check on something, I have widgets that show me when I am connected to 3G and when I am connected to H. I have noticed that the phone is activity managing that connection. In other word, it is in 3G until data is transfered then it goes to H. I wonder if when we are in areas of "questionable" HSDPA signal if this hand off is causing the problems.
I have seen a lot of op's say that there problems come right after some data activity?
Just a guess a this point
Click to expand...
Click to collapse
What I've heard is that the phone will stay in 3G mode until you begin using data in order to save battery life. Makes sense to me.
My Omnia 7 keeps loosing it's 3G connection. To restore it I have to restart the phone. T-Mobile say that this happens from time to time, but it's happening every day now. It's annoying as it stops my push email from being up to date, and of course prevents the use of any internet based services until the phone is restarted.
Has anyone else noticed their phone has switching to GSM?
Had mine for 6 days.Been fine up until today,then I had the same problem.Only the once so far.
Confirm loosing 3G
Confirm loosing 3G connection, and also have phone call failures.
Factory reset did not solve the problem.
Bring it back to shop
Blackstone is back now!
At first this was occasional with my phone, then more frequent, and it's all the time. If I want to use the Internet I have to restart the phone. My house is covered by full HSPA, but the only way to get it is to take the battery out while the phone is switched on. I can sometimes get 3G by a simple restart, which I lasts about 40 minutes.
I like the phone, so I'm going to hold out for a software update. All it needs to do is check available networks and I think that, if this is a wide spread issue, Samsung/Microsoft will fix it. Hope so.
Please post here if you have this issue too.
I have also been having this issue... sometimes it doesnt come back straight away when i restart it but after about 10mins its back.
When I activated it with orange I was told to expect a few txt msg's that would need deleting and the phone restarting... I only got 1 msg, maybe this has something to do with it, maybe the phone hasnt been sent enough updates.
I also have this issue and have done for weeks. Orange couldn't solve it either.
It only happens overnight at home. I either need to reset the phone / rescan available networks or turn flight mode off and on again for the connection to restore.
I was thinking it may be an issue with t-mobile since it only happens at my home where orange signal is poor and i roam over to t-mobile.
If i stay in an area with good Orange signal i don't get the problem.
Good to know i'm not the only one with this problem. It's very annoying!
Hi y'all.
I had the same problem: 3G was lost every time. I was fed up restarting the phone every time, so I looked for another way to get 3G back. I found out that disabling and enabling SIM security (phone > setttings) got me 3G again... for a short while.
But: after disabling SIM security permanently, 3G kept on going (in fact for over a week now).
I think that changing the PIN to some other number, might cause this. I haven't yet tried changing it to the default PIN again, to see if using that for SIM security solves it. For the moment I'm too happy it works again.
I have suffered from poor reception issues ever since I got my Omnia 7.
It seems like the reception comes and goes. I will receive e-mails, which proves that the phone has been connected, but as soon as I try to use data myself, by visiting a web page or refreshing an app like facebook, the reception disappears and the "no reception" symbol drops down from the status bar.
Also, often when I try to send an SMS, it will appear to have been sent, yet 10 minutes later I will receive a "Can't send...try again" message. Once I have received this, the SMS will never successfully send. However, in the meantime I can receive SMS messages, which shows that the phone has been getting a signal.
This is SO frustrating and is ruining my experience with the phone.
I have posted requests on the Microsoft Answers forum and the only suggestions have been to reset the phone or turn WiFi off. Neither of these have had any effect. I have never enabled SIM lock.
I have heard that there is a firmware update due soon which includes a new radio stack. I am desperately hoping that this will improve the situation, as at the moment I cannot rely on my Omnia 7 as my only phone.
Alex.
Hi Loco,
You are right in saying that social answers doesn't really help much .
Luckily there IS a new firmware from a couple of days ago! Check out the Omnia 7 Dev section. There are only a few posts.
And here is also a good link for you. You are right to assume that it comes with a new radio stack which improves on performance.
http://wmpoweruser.com/new-samsung-omnia-7-firmware-and-news-of-a-keyboarded-omnia-8-leaks/
Finally found a thread on this... I have been having a similar problem since I got my phone from Optus here in Australia. I took it back and they replaced it for me but the new phone is exactly the same. I don't lose the 3G icon but anything data related just ceases from loading. Right now I'm trying to refresh the Facebook app and it just comes up with 'Unable to connect', even though I have full 3G reception.
I flashed it to the newer leaked firmware and it hasn't changed anything, problem still persists unfortunately. This is a major problem that isn't getting enough attention! It seems quite widespread and Omnia 7 specific.
Had similar problems, but after I changed my provider ( O2-Germany), 3G is stable.
For the people having this problem, have you tried setting the phone to prefer 3g? Details of how to do this are here http://forum.xda-developers.com/showthread.php?t=915813
johnnymatrix said:
Finally found a thread on this... I have been having a similar problem since I got my phone from Optus here in Australia. I took it back and they replaced it for me but the new phone is exactly the same. I don't lose the 3G icon but anything data related just ceases from loading. Right now I'm trying to refresh the Facebook app and it just comes up with 'Unable to connect', even though I have full 3G reception.
I flashed it to the newer leaked firmware and it hasn't changed anything, problem still persists unfortunately. This is a major problem that isn't getting enough attention! It seems quite widespread and Omnia 7 specific.
Click to expand...
Click to collapse
Same here man. On Optus and my reception sucks with this device. What the hell is samsung doing? FIX IT!
I have been having this problem with my Omnia 7. The frustrating thing is this is a replacement phone I had for an LG which I had replaced THREE TIMES due to random resets. So now I have a phone that I have to turn off and on EVERY MORNING in order for the data connection to start working again. Needless to say I am very frustrated. I am on Orange in the UK. I suspect it could be related to when being an a poor reception area and it tries to switch to tmobile. I am going to try turning roaming off. Please, if anyone finds a solution to this let me know.
Thanks
m4tthall said:
I have been having this problem with my Omnia 7. The frustrating thing is this is a replacement phone I had for an LG which I had replaced THREE TIMES due to random resets. So now I have a phone that I have to turn off and on EVERY MORNING in order for the data connection to start working again. Needless to say I am very frustrated. I am on Orange in the UK. I suspect it could be related to when being an a poor reception area and it tries to switch to tmobile. I am going to try turning roaming off. Please, if anyone finds a solution to this let me know.
Thanks
Click to expand...
Click to collapse
My problem got worse with the Mango update. I'm now on my 2nd handset after having a replacement from Orange warranty. This one still loses it's connection but much less frequently.
TBH i don't think it will ever get fixed. I started an MS Answers thread months ago and lots of people had the same problem but we never got a response from MS.
Conisdering the age of the model now I doubt Samsung care, well they didn't seem to care a year ago so they won't now... For this reason I will not buy another Samsung phone. It's infuriating.
Looks like I am stuck with it until December then when I can upgrade to a Nokia lumia. A long wait :-(
i have this issue, too.. but for me i only have to set airplane mode on and off. sometimes i deactivate data connection, go to a random website, get the 'no connection' error, then activate data connection back and it works.
however, after installing the latest drivers & firmware, i get this issue A LOT less frequent. like once in 2-3 days.
i hope ms or samsung will fix this because it can get really annoying. especially when you need eg. a quick google-search..
Just flicking the flight mode wouldn't be so bad but that doesn't work for me, I have to restart the phone each time. I love WP7 but this and the other problems with the LG is driving me nuts. Almost wondering whether I should have just followed the crowd and gone for an iPhone.
m4tthall said:
Just flicking the flight mode wouldn't be so bad but that doesn't work for me, I have to restart the phone each time. I love WP7 but this and the other problems with the LG is driving me nuts. Almost wondering whether I should have just followed the crowd and gone for an iPhone.
Click to expand...
Click to collapse
Same as me - Flicking flight mode on-off doesn't solve it, needs a soft-reset.
Like I say, there are quite a few with Omnias on Orange with this problem.
I'm in the same boat, I've had this for months now so I guess I'll just deal with it until I can upgrade the start of April and get a Lumia (hopefully the EU 900/910 will be here by then!). There is no way on this earth Samsung are getting any more of my money. Nokia seem fully commited so they can take my cash next time!
I have the same problem with the data stopping working on o2 in the UK. But I also sometimes cant receive calls even though the phone has service, then there are the times where it site there going GPRS/3G/3G+/No Service and you cant do anything with it apart from pull the battery.
This is a topic that hasn't been clearly covered so I'm posting it here.
The new update talks about new 4g scanning functionality. Has anyone had any time with this or any basis of comparison for 4g behavior before or after the update?
4g has to be one of my biggest gripes on this phone pre-update as it was the main reason why I bought it and it's connection strategy ends up using more battery than anything. Just wondering if this new "scanning" feature improves that at all or makes it worse.
Interested in this topic myself.
bump.. yeah I was wondering about this as well.
Initial observations:
When wimax radio is on a couple of scenarios happen.
- Wimax radio on but no 4g service = wimax state is changed to "disconnected" meaning it behaves the way it will when wifi is being used (it doesn't scan so it uses very little power and when in the disconnected state the dc connect errors don't flood logcat; dc connect errors are still present in this update). Before the update if the wimax radio is on it will constantly scan for service even when there is no service available and it will scan every x amount of seconds unless a wifi connection is present then the wimax state is disconnected if the wimax radio is on and a wifi connection is present.
- Wimax radio on, no wifi connection = wimax state will remain "disconnected" until the user taps "scan for service". If no service is found wimax state reverts to "disconnected" meaning the radio is on but not scanning (before the update the radio will constantly scan while it is on) as opposed to off and flooding logcat with dc connect errors in the background.
- Wimax radio on, no wifi connection, no service = notification saying "4g radio is on" (only saw this notification twice mainly because I didn't want to sit and watch my phone tell me the radio is on). Wimax state remains "disconnected" (not off) and will only scan when "tap to scan" is pressed.
What does this mean? Whether you have 4g service or not you're better off leaving the radio on as it will always revert to a disconnected state when no service is found during a scan. Leaving the radio on keeps the dc connect error flood from happening in the background which some people attributed to huge battery drain. As long as the wimax state is "disconnected" and you are not using a wifi connection it does not/will not scan until you tell it to. The constant scan every x amount of seconds when no service is found is what drained the battery for most users.
So what happens with the new update?
Sent from my HTC Evo using XDA App
He just told you in the post before yours.
I guess my new question is this:
Running the previous build, I would just leave 4g on so that I always had it if it was available. My office building has poor 4g signal penetration, so it cuts in and out frequently depending on where I walk. With the new update, if I walk into a portion of the office where my 4g drops, will it not pick back up automatically when I come back into a good service area? Am I going to have to manually tell it to "reconnect" by tapping the scan button every time I hit a dead pocket?
naorion said:
He just told you in the post before yours.
I guess my new question is this:
Running the previous build, I would just leave 4g on so that I always had it if it was available. My office building has poor 4g signal penetration, so it cuts in and out frequently depending on where I walk. With the new update, if I walk into a portion of the office where my 4g drops, will it not pick back up automatically when I come back into a good service area? Am I going to have to manually tell it to "reconnect" by tapping the scan button every time I hit a dead pocket?
Click to expand...
Click to collapse
That's what appears is the new behavior of the wimax radio. It's a two-fold scenario and I believe sprint did this more for customers convenience since people with evos would more than likely keep track of what parts of town has 4g service.
It saves battery somewhat but requires the user to have to scan/rescan for service. I never turned my wimax radio off anyways prior to this update and I only flashed the update last night to check if there were any changes that I was hoping for.
Anything positive you've seen from the update? Are you going to run the new method or revert back to the old? Have you seen any battery improvements as a result of this new method? - it sounds like battery is why they changed it.
This update is actually LESS convenient for me as I now have to manually connect every time I want to use 4g considering how spotty the service is even in my "launch market" of Dallas.
naorion said:
Anything positive you've seen from the update? Are you going to run the new method or revert back to the old? Have you seen any battery improvements as a result of this new method? - it sounds like battery is why they changed it.
This update is actually LESS convenient for me as I now have to manually connect every time I want to use 4g considering how spotty the service is even in my "launch market" of Dallas.
Click to expand...
Click to collapse
For the most part sa is blanketed with 4g service so I am like you in that I have to rescan when I move.
Time will tell for me. I plan on building a rom later tonight with the new update and testing the kernel. I use extended batteries (seidio and sprint) so I don't pay attention to battery life anymore. I'm more concerned with useable performance.
After I build the rom I plan on seeing if I can get the wimax radio to revert back to auto scan. Again time will tell.
Alright well thanks for all the info. I've got a seidio battery on the way, but the log file thing is what piqued my interest. I'm about to flash the rooted version of the stock rom and give it a go.
I just flashed the latest - Is there not a widget or shortcut I can put on my homescreen to initiate the scan?
naorion said:
I just flashed the latest - Is there not a widget or shortcut I can put on my homescreen to initiate the scan?
Click to expand...
Click to collapse
I didn't find a sense specific widget. I used lpp to make a homescreen shorty straight into the 4g settings window.
what is lpp?
Launcher pro plus. Or just the regular free launcher pro will do it for you too. That's just me. I always remove sense entirely whenever I tweak the rom and lpp is my home launcher replacement.
lovethyEVO said:
Initial observations:
When wimax radio is on a couple of scenarios happen.
- Wimax radio on but no 4g service = wimax state is changed to "disconnected" meaning it behaves the way it will when wifi is being used (it doesn't scan so it uses very little power and when in the disconnected state the dc connect errors don't flood logcat; dc connect errors are still present in this update). Before the update if the wimax radio is on it will constantly scan for service even when there is no service available and it will scan every x amount of seconds unless a wifi connection is present then the wimax state is disconnected if the wimax radio is on and a wifi connection is present.
- Wimax radio on, no wifi connection = wimax state will remain "disconnected" until the user taps "scan for service". If no service is found wimax state reverts to "disconnected" meaning the radio is on but not scanning (before the update the radio will constantly scan while it is on) as opposed to off and flooding logcat with dc connect errors in the background.
- Wimax radio on, no wifi connection, no service = notification saying "4g radio is on" (only saw this notification twice mainly because I didn't want to sit and watch my phone tell me the radio is on). Wimax state remains "disconnected" (not off) and will only scan when "tap to scan" is pressed.
What does this mean? Whether you have 4g service or not you're better off leaving the radio on as it will always revert to a disconnected state when no service is found during a scan. Leaving the radio on keeps the dc connect error flood from happening in the background which some people attributed to huge battery drain. As long as the wimax state is "disconnected" and you are not using a wifi connection it does not/will not scan until you tell it to. The constant scan every x amount of seconds when no service is found is what drained the battery for most users.
Click to expand...
Click to collapse
So what if you are in a good 4g area (also not using wifi) turn on the 4g then turn of the 4g does it go into the dc connect error flood? I rarely use my 4g but I avoid turning it on unless i plan to do a reboot to avoid batt drain issues. I am running myns rom so i havent tried to update anything since the latest update. Curious if the new update still forces a reboot after using 4g.
Stroid01 said:
So what if you are in a good 4g area (also not using wifi) turn on the 4g then turn of the 4g does it go into the dc connect error flood? I rarely use my 4g but I avoid turning it on unless i plan to do a reboot to avoid batt drain issues. I am running myns rom so i havent tried to update anything since the latest update. Curious if the new update still forces a reboot after using 4g.
Click to expand...
Click to collapse
I'm gonna sound like a douche but, the answer to your questions are in the text you quoted. Try rereading it as I broke it down about as straight forward as I could for everyone.
lovethyEVO said:
I'm gonna sound like a douche but, the answer to your questions are in the text you quoted. Try rereading it as I broke it down about as straight forward as I could for everyone.
Click to expand...
Click to collapse
Yes you mentioned in the last paragraph about batt drain issues but I dont see how leaving 4g on solves this issue. Leaving 4g on all the time will probably drain more battery scanning for signal (when not available) and use more battery when using the 4g signal then when on 3g. I personally think if you use 4g after you are done with it turn it off reboot then go back to using your phone normally. Yes its a pain to reboot but imo you will get better battery life using this option then the options you are suggesting...thoughts?
Either way i tested it out for myself, i updated to latest radio and still getting the dc connect error flood. From my reading on this issue from other threads it seems this is an HTC code fix not an android fix...but that is speculation.
Source:
http://code.google.com/p/android/issues/detail?id=11008
Lastly I read your response several times..maybe its not as clear as you think it is. Glad you wasted time writing that response then simply answering the question. Dont assume people dont read and search the forum. So congrats on sounding like a douche..be better to discuss this issue then put your great reread comment up.
I walked into a room with no WiMAX signal, 3G kicked in and the notification "Tap to scan" showed up. However, I did not touch anything and after a few minutes, my phone was once again connected through 4G.
So it will actually re-scan and reconnect eventually, even if you don't manually tap to scan.
Stroid01 said:
Yes you mentioned in the last paragraph about batt drain issues but I dont see how leaving 4g on solves this issue. Leaving 4g on all the time will probably drain more battery scanning for signal (when not available) and use more battery when using the 4g signal then when on 3g. I personally think if you use 4g after you are done with it turn it off reboot then go back to using your phone normally. Yes its a pain to reboot but imo you will get better battery life using this option then the options you are suggesting...thoughts?
Either way i tested it out for myself, i updated to latest radio and still getting the dc connect error flood. From my reading on this issue from other threads it seems this is an HTC code fix not an android fix...but that is speculation.
Source:
http://code.google.com/p/android/issues/detail?id=11008
Lastly I read your response several times..maybe its not as clear as you think it is. Glad you wasted time writing that response then simply answering the question. Dont assume people dont read and search the forum. So congrats on sounding like a douche..be better to discuss this issue then put your great reread comment up.
Click to expand...
Click to collapse
You need to read better then. I distinctly said the dc connect errors were still present in the new update.
I distinctly said the wimax state is changed to disconnected when there is no service. I also explained what happens when the wimax state is disconnected.
BUT, since you seem to be adamant that you did in fact read what I posted I will spoon feed the info to you.
When the wimax state is "disconnected" it does not do anything, it does not scan and the radio itself is not off. It is in a "sleep" state.
I said the dc connect errors were still present in this update and I explained that leaving the 4g radio on will revert to a "disconnected" state when there is no service available. Since it doesn't scan in the "disconnected" state it is not using battery. Because of this, the radio is not off and does not flood the background with dc connect errors. In the "disconnected" state the radio does not scan for service and the impact on battery drain is minimal.
Now, if that isn't clear for you then nothing will be. I invite you to search my original unedited text again and show me that I did not SPECIFICALLY state that the dc connect errors are still present in this update. When you find it you will know that it is you who has not read the text properly, not me.
zeuzinn said:
I walked into a room with no WiMAX signal, 3G kicked in and the notification "Tap to scan" showed up. However, I did not touch anything and after a few minutes, my phone was once again connected through 4G.
So it will actually re-scan and reconnect eventually, even if you don't manually tap to scan.
Click to expand...
Click to collapse
I will test this later today if I can. Like I said earlier in this thread sa is blanketed for most part with wimax service so I will have to force this scenario but it's great that it rescans for you.
lovethyEVO said:
You need to read better then. I distinctly said the dc connect errors were still present in the new update.
Click to expand...
Click to collapse
Yeah I know and I said i see you mentioned that in my previous post
lovethyEVO said:
distinctly said the wimax state is changed to disconnected when there is no service. I also explained what happens when the wimax state is disconnected.
BUT, since you seem to be adamant that you did in fact read what I posted I will spoon feed the info to you.
Click to expand...
Click to collapse
I didnt ask you to spoon feed **** i asked for thoughts on my comment
lovethyEVO said:
When the wimax state is "disconnected" it does not do anything, it does not scan and the radio itself is not off. It is in a "sleep" state.
Click to expand...
Click to collapse
this is the part I dont necessarily agree with as ive seen my phone scan when no service is available (otherwise how would it automatically lock back onto 4g) but as the next post said his 4g kicked back in so does mine leading me to think what you are saying isnt correct about it not scanning and draining battery, i could be wrong but i will look into that as well
lovethyEVO said:
I said the dc connect errors were still present in this update and I explained that leaving the 4g radio on will revert to a "disconnected" state when there is no service available. Since it doesn't scan in the "disconnected" state it is not using battery. Because of this, the radio is not off and does not flood the background with dc connect errors. In the "disconnected" state the radio does not scan for service and the impact on battery drain is minimal.
Click to expand...
Click to collapse
Doesnt add up, if the 4g reconnects automatically has to scan to reconnect to 4g not going to magically know that 4g service is available again
lovethyEVO said:
Now, if that isn't clear for you then nothing will be. I invite you to search my original unedited text again and show me that I did not SPECIFICALLY state that the dc connect errors are still present in this update. When you find it you will know that it is you who has not read the text properly, not me.
Click to expand...
Click to collapse
Funny you say search your text again when apparantly you didnt read what i said in my last post saying that you mentioned the batt drain issue (referring to the dc connect errors) never said you didnt speciffically state that, geez dude relax and realize I am trying to troubleshoot the situation as well
Hi everyone. I have a problem with my Legend that's been bugging me for a while, but I never got around to post about it. This is the deal: my Legend often drops the connection to the cell network, meaning I lose BOTH call and data capability. At first I used to reboot the phone, which fixed it, then I found out that turning airplane mode on and off would do the trick. Still, it gets old really fast...
I've searched the forum for similar issues but only found some posts about data connectivity loss / poor reception. In my case I don't have complaints about reception, and the problem isn't restricted to data.
The problem appears both in stock Froyo, which I used since it came out, and Cyanogenmod 9, which I installed last week after finally getting around to rooting the thing.
Any clues as to what the problem is, and better yet, whether there's a fix?
Thanks!