yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Yes. Yesterday it was happening every 3-5 seconds. After about 15 in a row I turned off the phone and ran whitslack's "start over" method and then loaded the new Fresh ROM. No more error 67. What I did was probably overkill and I've also read this is just a Sprint thing.

Back to our main issue. I tried the call to reconnect several more times today and it worked every time. From watching the notification bar, I see that 3g drops when a call is made (which it should since I think you can only utilize voice and data simultaneously when you have a 4g connection) and in essence creates a "window" for 4g to reconnect. Otherwise, it seems like 3g is overriding 4g, like it has the higher priority. These are my non-technical observations and I hope they can help someone more savvy than I in finding a resolution.

For what it's worth, I also tried sending a text to see if that would reconnect to 4g. It didn't. In fact the text failed - that's a first for me since launch day.
[EVO 4G Q&A, Help & Troubleshooting] initial:
Can you guys post your logcats after turning on the radio? maybe we can gain some insight for there.

Install aLogcat from the market

Reboot phone with 4G radio off

Open logcat and set a filter for "Wimax" (case sensitive)

Turn on 4G radio

Switch to aLogcat, send the report to yourself (menu -> send) and post it here
[EVO 4G Q&A, Help & Troubleshooting] awesomeindeed:
I get this about 3-5 times a day. It never reconnects unless I reboot. Very, very annoying.
[EVO 4G Q&A, Help & Troubleshooting] swatspyder:
Main thread on this topic is here:

http://xdaforums.com/showthread.php?p=7218209

This is a confirmed fix for the long lag time (5+ minutes) to reconnect after losing a 4G signal.

Those of us using a rom with the newest software 1.47.651.1 have been having issues with the 4G connection not reconnecting when losing 4G signal. These instructions fix this problem.

Requirements:

Your MSL code (See Here: http://xdaforums.com/showthread.php?t=697487)

Instructions:

Turn OFF your 4G radio if it is turned on!

1) Click on phone and dial ##DATA# (##3282#)

2) Click on "Edit Mode"

3) Type in your MSL code (see above if you don't have it yet)

4) Click on the menu entry "WiMAX"

5) Scroll down the list and click on "WiMAX_Scan_Retry(s)"

6) Enter the number 15 and click "OK" (This equals 15 seconds instead of 300 seconds)

7) Scroll down the list and click on "WiMAX_Entry_Delay(s)"

8) Enter the number 0 and click "OK" (This equals 0 seconds instead of 300 seconds)

9) Press the "Menu" key and click on "Commit Modifications"

10) Grab a cup of coffee, get a bite to eat, or sit back and wait for your EVO to restart

Testing:

1) Go to your phone's settings and click on "Wireless & networks"

2) Scroll down and click on 4G settings

3) Click on 4G to turn it on and wait for the status to change to "Connected to Sprint"

4) Without touching any of the menu items, cover the top half of your phone with your hands until the status changes to "Scanning..."

5) Uncover the top of the phone and count the seconds until it says "Connecting to Sprint"

6) Realize that you no longer have to cycle the 4G radio to reconnect :D

Result:

After modifying my EVO and my girlfriend's EVO and inputting these changes, the phone will reconnect to the 4G tower in as little as 20 seconds!

Yes, 20 seconds, the most I have seen so far is 30 seconds after dropping the connection. This is a HUGE improvement over the 5+ minutes to reconnect (300+ seconds).
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Okay I did this twice this morning: once with the Wimax filter and once without.

This was easy for me as I get 4g outside of my office but never inside so it was just a matter of walking in and out of the building. I turned on 4g outside, let it connect, walked into the building to disconnect, went back outside and waited a bit for reconnect (which doesn't happen) and then I made a phone call for a few seconds to enable 4g to reconnect.

Here is the filtered version (I cut off most of the E/Wimax* and I/Wimax* lines off the top as it's just the same thing over and over again with a different proVersion #s ---- I also substituted question marks (?) wherever I thought there may be sensitive info):

And here is the unfiltered portion (at least I think I grabbed the right part) of the disconnect and make a phone call to reconnect in case it helps:
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Interesting. What does covering the phone with your do? Not sure if this is appropriate for me since I never reconnect.
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Holy ****! It works! THANK YOU!

Question: I had previously changed my idle sleep time to 300 from 10. Does that need to change?

Now I just need to figure out why my Wimax processes are constantly running when 4g is off (see my first logcat above) and thus killing my battery.
[EVO 4G Q&A, Help & Troubleshooting] sw99:
Do you think this quick reconnect, when out of 4G coverage is also a battery drainer?
[EVO 4G Q&A, Help & Troubleshooting] kamiller42:
Good work. Very interesting. I will have to try this next time I go into a 4g area.

I suspect these values are maximum values, i.e. wait 300 seconds before looking for the 4g network again and wait up to 300 seconds before raising a timeout error when attempting to enter the 4g network. The timeout error would then throw the process back into scanning of course.

Setting entry delay to 0 could mean wait forever to enter the network or enter with no delay. Why have any delay? I assume the phone would want to delay some to ensure it's locked onto a good 4g signal before beginning the network sign in process. Setting to 0 means "The second you find a 4g signal, sign me on." Setting a value higher than 0 means "Sign me into the network when the 4g has met quality level X for up to Y seconds."

I might play with the scan retry first because the problem I am seeing is it can't find a signal in the first place when I re-enter 4g. So, not sure the entry delay will fix that.

In any case, 300 seconds for both does seem high, but that maybe for battery saving reasons. Powering the 4g hardware is still going to eat more of the power than what the software executing does.

All the above is my guess and speak with no authority on these settings.
[EVO 4G Q&A, Help & Troubleshooting] jefftse:
When I dialed ##data#, nothing happened.................. not sure why
[EVO 4G Q&A, Help & Troubleshooting] sw99:
The aLogCat app was a great idea...See what happens when I receive a call after being in 4G range without connectivity (I highlighted the intersting parts):

07-16 11:40:21.321 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:24.331 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:27.341 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:30.351 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:33.351 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:36.361 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:39.371 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:41.641 D/WimaxService( 84): onReceive ACTION_PHONE_STATE_CHANGED state=RINGING

07-16 11:40:41.651 D/WimaxStateTracker( 84): handlePhoneRinging DDTM is not implemented

07-16 11:40:42.381 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:45.201 D/WimaxService( 84): onReceive ConnectivityService CONNECTIVITY_ACTION type=MOBILE[CDMA - 1xRTT], state=SUSPENDED

07-16 11:40:45.201 D/WimaxStateTracker( 84): wimaxRescan

07-16 11:40:45.201 D/WimaxStateTracker( 84): wimaxRescan: set force scan flag

07-16 11:40:45.201 D/WimaxStateTracker( 84): wimaxRescan : CBES::forceScanning reset-state=0

07-16 11:40:45.381 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:45.811 D/WimaxService( 84): onReceive ACTION_PHONE_STATE_CHANGED state=OFFHOOK

07-16 11:40:45.811 D/WimaxStateTracker( 84): handlePhoneOffHook DDTM is not implemented

07-16 11:40:47.311 I/Wimax ( 84): Ndss: ScanRoundCompleted

07-16 11:40:47.311 I/WimaxStateTracker( 84): NdsRoundCompleteNotification +-

07-16 11:40:47.311 D/WimaxStateTracker( 84): NdsRoundCompleteNotification: BsFound: 0

07-16 11:40:48.390 D/WimaxStateTracker( 84): GetAvailableMs

07-16 11:40:48.561 I/Wimax ( 84): Ndss: Scan Bs Found (Ext Band)

07-16 11:40:48.561 I/WimaxStateTracker( 84): NdsBsFoundExtBandNotification: bandIdx:5 freqIdx:2 pbIdx:46 napId:2 rssi:-7281 cinr:2447 cinrR1:1927 cinrR3:2321

07-16 11:40:48.561 D/WimaxStateTracker( 84): NdsBsFoundNotification: no data connection or only have 1xRTT or force scan, connect to WIMAX ASAP

Looks like losing 3G does in fact trigger the Wimax Channel scan. If this is the case, there should be a way to programatically manage this connection, and not have to mess with delays that could have adverse effects.
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Sw99- yes regarding battery.

Unfortunately this new method seemed to work for brief periods of being out of 4g range but it didn't work after a period of 3 hours.
[EVO 4G Q&A, Help & Troubleshooting] sw99:
Using the above Wimax logic in the logs, I performed another test. I disabled "Mobile Networks" in the Wireless/Network settings.

In this scenario, 4G will reconnect fairly quickly (~20 seconds).

So what this tells me is:

1. If I am in marginal 4G coverage, I'm going to want to disable mobile networks.

2. Should not matter whether you are rooted or not, as this appears to be in the wimax code.

3. There should be a way to overcome this limitation.

I suspect that Sprint did this deliberately to conserve battery. I just wish they would have either consulted the users or at least added an override so that we can still use it the old way.
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
You think this is a 1.47.651.1 thing?
[EVO 4G Q&A, Help & Troubleshooting] sw99:
That's when most folks started noticing the problem.
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
That is my experience as well. Prior to that I was suffering from continuous 3g/4g alternating. I updated to 1.47* for the first time through whitslack's method and that is when the current problem started. If I had to pick I'd take this over the constant alternating but it sure would be nice to have my cake and eat it too!
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Who else is getting this every few seconds when 4g is OFF?

This has to be what's killing my battery!
[EVO 4G Q&A, Help & Troubleshooting] sw99:
I've seen that, also seen the following when 4G is off (which sound like a battery drainer):

07-16 14:16:59.188 I/Wimax ( 84): <DC> Try to establish a connection to DC server.

07-16 14:16:59.198 E/Wimax ( 84): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'

07-16 14:17:01.198 I/Wimax ( 84): <DC> Try to establish a connection to DC server.

07-16 14:17:01.198 E/Wimax ( 84): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'

07-16 14:17:03.198 I/Wimax ( 84): <DC> Try to establish a connection to DC server.

07-16 14:17:03.198 E/Wimax ( 84): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'

07-16 14:17:05.198 I/Wimax ( 84): <DC> Try to establish a connection to DC server.

and this when 4G is on but refusing to attempt to reconnect:

07-16 12:00:10.906 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:13.916 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:16.926 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:19.936 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:22.946 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:25.956 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:28.966 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:32.296 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:35.306 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:38.306 D/WimaxStateTracker( 84): GetAvailableMs

07-16 12:00:41.326 D/WimaxStateTracker( 84): GetAvailableMs
[EVO 4G Q&A, Help & Troubleshooting] jacc1234:
I get the same thing when 4G is off. I assume its querying the daemon to see if its enabled. No idea how much that taxes the phone or even if thats what its doing.
[EVO 4G Q&A, Help & Troubleshooting] kamiller42:
I have a new problem appearing today . I am sitting in the airport. I can connect 4g and get an IP. Everything looks good. However, when I go to the browser, it cannot resolve any addresses. Ahh!! Will the wimax problems never cease? 3g works fine.
[EVO 4G Q&A, Help & Troubleshooting] kamiller42:
This exactly what I am seeing when connected but unable to browse. GetAvailableMs over and over. Could this be a bad tower? Kind of doubt because 3g is working fine. I am getting full 4g signal here.
[EVO 4G Q&A, Help & Troubleshooting] kamiller42:
I hate making this thread my journal, but I had to mention that I am typing this on a 4g connection. What did I do? Update PRL and rebooted. Didn't even update profile. I updated PRL and profile earlier this morning and rebooted when things didn't work with no change. Go figure.

I hate to wish frustration on other users, but I hope non-rooted users with all updates are experiencing these same problems. I would hate to think Sprint/HTC figured out a way to "get" the root users.
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
I'm making it a point to ask whenever I see someone walking around with an EVO.
[EVO 4G Q&A, Help & Troubleshooting] jacc1234:
The "GetAvailableMs" entries mean that the 4G is searching for a connection. It means that your Evo is not currently connected to 4G and is constantly "Scanning" which is the same issue I am having.
[EVO 4G Q&A, Help & Troubleshooting] kamiller42:
Disregard my last journal entry. Apparently I am on the edge of 4g coverage in this terminal. I went back to other terminal and 4g seems to stay connected.
[EVO 4G Q&A, Help & Troubleshooting] sw99:
Just an update: I disabled "Mobile Networks", enabled 4G and took a 1 hour drive while downloading a huge file. The phone had no problem connecting and reconnecting to 4G as needed throughout the trip. (Was usually only out of 4G coverage for short amounts of time).

What was really interesting is that the download never failed. It hung on while waiting for 4G to reconnect. This is likely because of that timeout that I changed from 10 to 300 seconds.

In any case, when 3G is disabled, 4G works the way you would expect it to.
[EVO 4G Q&A, Help & Troubleshooting] mikev43:
which setting from 10 to 300??
[EVO 4G Q&A, Help & Troubleshooting] sw99:
These were the only 2 changes I made:

wimax_idle_sleep(s) changed from 10 to 300 seconds

wimax_scan_attempt_timeout(s) changed from 1 to 20 seconds
[EVO 4G Q&A, Help & Troubleshooting] mikev43:
ok and did you do How to start over: Fully rooted stock 1.47.651.1 in one shot (no adb!)? have you tried other radio/wimax versions and get better/worse results?
[EVO 4G Q&A, Help & Troubleshooting] sw99:
yes, but no other radios.
[EVO 4G Q&A, Help & Troubleshooting] mikev43:
it seemed like the old radio and wimax did a better job connecting and possibly better speeds but it's really hard to know especially for 4g because I'm not sure my location has good reception and or it seems to just bounce a lot from none to 2 bars... I'm really irritated with this whole 4g.. why am I paying $10 more for inferior service? 3g I have gotten 2Mbits! I have seen upstairs in my house nearly 6Mbit down but this new radio seems like it's struggling to find a network and keep a connection.. I really am not sure what to do..

Can I flash the old radios with what I have now which is PC36IMG-1.47.651.1_eng-hboot_RA-1.7.0.1

to

EVO_Radio_1.36.00.04.02 & EVO_WiMAX_24722 and keep the existing rom listed above?
[EVO 4G Q&A, Help & Troubleshooting] sw99:
I'd like to respectfully disagree. With the old radio, I could not get a signal in my office, which I now can (in certain areas). I think the radio is better (at least in my experiences). The problem we are having is with the software logic. It seems that in order to save battery, Sprint has chosen longer timeouts for reconnections. So if in the past you had a marginal signal, you may now be dropping the connection and having to wait longer to reconnect (way longer). I would not attempt to mix s/w versions with different radios, that probably asking for problems.

Due to the reconnection problems, I now only use 4G when I am going to be in a stationary location for some amount of time, and 3G the rest of the time.
[EVO 4G Q&A, Help & Troubleshooting] mikev43:
Yeah I tried this and at one point the 4g would turn on and off on it's OWN!! Ghost in the machine!!

I also tried the pc36 1.32.651.1_eng-hboot_RA-1.7.0.1.zip with no success.. I'm really starting to think there is some interference from the tower to my house as I have had an insane amount of random connects/disconnects and wildly varying speeds.. At one point upstairs I got nearly 6Mbit.. then it would drop connection and the next test .5Mbit..

this is soooooooo frustrating.. I think I'm going to disable 4g all together unless I know absolutely for sure it will work.. really a WASTE of my $10
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Unless you are 100% stock your complaints are unfounded.
[EVO 4G Q&A, Help & Troubleshooting] mikev43:
you mean stock from the store?? or??? there has been known issues now with sprint 4g OTA and we all know how the radio/wimax rooted updates went.. there is a lot more going on than meets the eye.
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Stock. Were you having the same 4g issues prior to rooting/modding your phone? If so, I guess you have a point but then again I would have just returned it for another functional one prior to rooting, etc.

If your 4g issues started after rooting/modding you really can't complain about your $10 and Sprint...
[EVO 4G Q&A, Help & Troubleshooting] xeroxsmm:
Non-rooted, stock user here with this problem. If I'm in a strong 4G area and enter a building to where I lose signal, the 4G will not reconnect after going back outside. The radio needs to be reset. Annoying!
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
xeroxsmm- May I ask what city? Has your EVO always behaved this way? I assume you are going to take it back? If so, see if they can tell you what is going on!
[EVO 4G Q&A, Help & Troubleshooting] mikev43:
that's pretty well documented at this point.. it's these commands that will force the 4g to re scan VERY quickly.. within 30 seconds or less..

you need your msl code to do this

wimax_idle_sleep(s) changed from 10 to 300 seconds

wimax_scan_attempt_timeout(s) changed from 1 to 20 seconds

Originally Posted by swatspyder

I need someone to confirm, but I believe I found a FIX!!!

Requirements:

Your MSL code (See Here: http://xdaforums.com/showthread.php?t=697487)

Instructions:

Turn OFF your 4G radio if it is turned on!

1) Click on phone and dial ##DATA# (##3282#)

2) Click on "Edit Mode"

3) Type in your MSL code (see above if you don't have it yet)

4) Click on the menu entry "WiMAX"

5) Scroll down the list and click on "WiMAX_Scan_Retry(s)"

6) Enter the number 15 and click "OK" (This equals 15 seconds instead of 300 seconds)

7) Scroll down the list and click on "WiMAX_Entry_Delay(s)"

8) Enter the number 0 and click "OK" (This equals 0 seconds instead of 300 seconds)

9) Press the "Menu" key and click on "Commit Modifications"

10) Grab a cup of coffee, get a bite to eat, or sit back and wait for your EVO to

restart

Testing:

1) Go to your phone's settings and click on "Wireless & networks"

2) Scroll down and click on 4G settings

3) Click on 4G to turn it on and wait for the status to change to "Connected to Sprint"

4) Without touching any of the menu items, cover the top half of your phone with your

hands until the status changes to "Scanning..."

5) Uncover the top of the phone and count the seconds until it says "Connecting to

Sprint"

6) Realize that you no longer have to cycle the 4G radio to reconnect

Result:

After modifying my EVO and my girlfriend's EVO and inputting these changes, the phone

will reconnect to the 4G tower in as little as 20 seconds!

Yes, 20 seconds, the most I have seen so far is 30 seconds after dropping the

connection. This is a HUGE improvement over the 5+ minutes to reconnect (300+ seconds).
[EVO 4G Q&A, Help & Troubleshooting] sdc177:
Wow, this thread has grown large.
[EVO 4G Q&A, Help & Troubleshooting] pflatlyne:
Im not rooted and I have the problem. The thing is,your going to see far far more rooted users complaining than not. Users who root their phone are typically more technically saavy than those who dont. Therefore they will notice there is a problem with connecting to 4g while others may not. For what its worth,I find that for some reason I seem to connect 4g much more reliably when wifi is on. In fact,there are times when its sitting there searching and then turn on wifi and it immediatly connects to sprints 4g network.
[EVO 4G Q&A, Help & Troubleshooting] xeroxsmm:
I'm in Portland, OR and my 4G coverage has been rather disappointing since launch day. Troubling, since we were one of the first markets for Clear, I would have assumed more consistent coverage. However I have felt that my connection issues have been more frequent since applying the latest OTA update. Me thinks the radio in this thing is just weak.

I will try the steps posted above, I assumed they were for rooted users at first.
[EVO 4G Q&A, Help & Troubleshooting] elusivebyte:
I'm having 4G issues. Specifically, my persist.wimax.0.USER-IDENTITY is blank.

Some background:

I bought my phone yesterday. I rooted my phone using Simple Root OTA when Toast's method wouldn't work. Then 4G didn't work. Simple Root might have given me NAND access, but I didn't think so, so I followed other instructions to get it. Those instructions included flashing the radio, I believe (evo.1.39.00.05.31.zip). If it wasn't that, then some other instructions included it. I can go back and find the details if it's important.

At any rate, while reading instructions to debug 4G issues, I found this quote:

(This is from a different thread.)

I went into Settings > System Update > and hit Update Profile (and Update PRL as instructed elsewhere.) Then I rebooted. Supposedly this would fix the persist.wimax.0.USER-IDENTITY being blank, but it's still blank. How do I fix this?

Edits:

This is the wimax version I apparently have: "Firmware Version (4.6.2.2_v24722): You may have toasts old wimax or another older release"

For what it's worth, I don't have any xml files in data/misc/wimax

UPDATE: I'm good! It turns out I missed an important step early on. When I did Toast's Part 2, it flashed Amon RA Recovery over my clockwork recovery I got from Simple Root. I didn't do the evo-recovery step in Toast's part 2 because I thought I was good with Clockwork. So I did my backup in CW. And I was supposed to restore my backup when all was said and done, but I never did, because now I had the wrong recovery. So I had a stock 1.17 version (or something like that) instead of 1.47. And wimax just didn't work. So I followed the "start over" instructions and now it works!
[EVO 4G Q&A, Help & Troubleshooting] sw99:
can you run the aLogCat when this happens. I'd be curious to know if there is a trigger for this, as there was for scenario where a phone call is made/received and when "Mobile Networks" is disabled.

It would make more sense NOT to scan for 4G when you have wifi, unless your wifi is on and not connected.
[EVO 4G Q&A, Help & Troubleshooting] deddy777:
My 2 cents

Just my 2 cents, I haven't rooted yet and I am having the scanning problem as well. I did find something interesting though. When at my desk in the Seattle area, while looking at signal strength moving back and forth between fair and poor, I kept loosing my connection. I moved my EVO about 7 feet away in the window and now I have good bouncing to fair. Ran speed test and got low numbers then it pegs to the red and I get a major jump, so I try picking somewhere else. I pick Kansas to New York below are the results. Any ideas why it would peg like that?