Related
My wifi connection is dropping within seconds of connection. The phone switches to 3g, wifi turns back on and connects again for a few seconds, drops then kicks back onto 3g.
Ive had this issue on multiple roms, so I am relating it to something similar to RezRom and CleanRom or to the leak itself.
Anybody have ANY ideas?
Update: seems that after the firmware update, my router and phone did not like each other. I was able to tweak my router quite a bit and it appears that the dropping connection issue is resolved.
ih8mydroid said:
My wifi connection is dropping within seconds of connection. The phone switches to 3g, wifi turns back on and connects again for a few seconds, drops then kicks back onto 3g.
Ive had this issue on multiple roms, so I am relating it to something similar to RezRom and CleanRom or to the leak itself.
Anybody have ANY ideas?
Update: seems that after the firmware update, my router and phone did not like each other. I was able to tweak my router quite a bit and it appears that the dropping connection issue is resolved.
Click to expand...
Click to collapse
It is a wireless N router? I do believe I read that our phones are having issues when on the 5Ghz band.
mjones73 said:
It is a wireless N router? I do believe I read that our phones are having issues when on the 5Ghz band.
Click to expand...
Click to collapse
The phone does not have 5GHz abilities, but regular 2.4Ghz N is supported.
Via Rezound using XDA Premium
EDIT: Take that back, however it doesn't see any of my 5Ghz access points here at all.
I have a wireless N router at home with no problems. It is on the 2.4ghz band though. I think.
ih8mydroid said:
Update: seems that after the firmware update, my router and phone did not like each other. I was able to tweak my router quite a bit and it appears that the dropping connection issue is resolved.
Click to expand...
Click to collapse
What settings did you wind up changing? I have a similar issue with my phone and one of my routers.
destro158 said:
What settings did you wind up changing? I have a similar issue with my phone and one of my routers.
Click to expand...
Click to collapse
Ditto. My wi-fi is dropping intermittently. If I toggle it off and back on, it starts working again.
What router tweaks did you do or phone tweaks?
My rezound picks up N 5ghz just fine.
Sent from my ADR6425LVW using xda premium
I'm having the same problem. However, mine doesn't drop out within seconds, it'll probably be good for a couple hours then I'll notice it's trying to sync with my Exchange server for a while, and will eventually time out and then I lose all internet connectivity until I turn wifi off and back on again. This happens on multiple wifi networks, including wireless-N and non wireless-N.
I do also see that the 3g icon will come and go every few seconds when connected to wifi. Anyone know if this is just a bug with the new ICS leak or is there some kind of fix floating around?
dynofrk666 said:
I'm having the same problem. However, mine doesn't drop out within seconds, it'll probably be good for a couple hours then I'll notice it's trying to sync with my Exchange server for a while, and will eventually time out and then I lose all internet connectivity until I turn wifi off and back on again. This happens on multiple wifi networks, including wireless-N and non wireless-N.
I do also see that the 3g icon will come and go every few seconds when connected to wifi. Anyone know if this is just a bug with the new ICS leak or is there some kind of fix floating around?
Click to expand...
Click to collapse
I am unlocked and rooted but I am running the stock ROM and mine does exactly what yours is doing. I don't actually know if this happens outside of my house since I'm generally using 3/4G then.
I have a thread on this in the question section but no answers yet.
killahrey said:
My rezound picks up N 5ghz just fine.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
This is true. The rezound does seem to have 5ghz capability. However my POS netgear doesnt get the same distance on 5ghz as 2.4ghz.
As far as what I did was actually reset my router and update firmware. This seems to have fixed the issue for now. I only started having this issue with the updated leak and it was happening on all roms and even stock. Reinstalling a ROM would fix it for about 2 to 3 minutes then it was back to switching between both data and wifi.
My phone burned up the battery in a matter of an hour and half as it was constantly going from wifi to 3g.
My phone does the same thing!! I think it happpened when I flashed the new leak zip without re locking vootkoader. In hoping that official ics will fix it
Sent from my ADR6425LVW using Tapatalk
Just curious if anyone found a solid solution to the Wifi problem that we seem to be experiencing with the new leak? I tried the suggestion of disabling auto wifi in the dock mode but that didn't seem to fix it for me. I guess I'm just trying to see if this is widespread, or if it's only affecting certain people in different scenarios. It doesn't seem to be getting as much attention as the overheating/battery life issues that others are reporting.
So far I've tried connecting to multiple networks with different security types (open, wpa, wpa2, wep) all seem to the have the same result of showing that wifi is connected, works for a couple of hours, then will lose wifi connectivity, even though the wifi indicator is showing that it's connected. I've done everything i can think of other than re-flashing the ICS leak. I've also never unlocked my phone, just installed the update per the original instructions on Android Police.
I am unable to connect my eVOLTe to my Airave access point. All the other phones in the house (two Pixis, a Pre, an OG EVO, and a Hero) are able to connect flawlessly and go from one bar to full in the process. However, my new eVOLTe flickers on one bar, occasionally dropping to VZW roaming. This is the case even if none of the other phones are present in the house, and I have never enabled any of the restricted phone settings on the Airave.
I was wondering if anyone had experienced similar issues, and if so, if they had found a solution.
Techrocket9 said:
I am unable to connect my eVOLTe to my Airave access point. All the other phones in the house (two Pixis, a Pre, an OG EVO, and a Hero) are able to connect flawlessly and go from one bar to full in the process. However, my new eVOLTe flickers on one bar, occasionally dropping to VZW roaming. This is the case even if none of the other phones are present in the house, and I have never enabled any of the restricted phone settings on the Airave.
I was wondering if anyone had experienced similar issues, and if so, if they had found a solution.
Click to expand...
Click to collapse
Don't know if this will work because I'm away from home and can't confirm. In the mobile network settings is a setting to turn lte off, cdma only mode. My guess is the cdma/lte mode is what's causing the issue.
Sent via LTEVO!
Techrocket9 said:
I am unable to connect my eVOLTe to my Airave access point. All the other phones in the house (two Pixis, a Pre, an OG EVO, and a Hero) are able to connect flawlessly and go from one bar to full in the process. However, my new eVOLTe flickers on one bar, occasionally dropping to VZW roaming. This is the case even if none of the other phones are present in the house, and I have never enabled any of the restricted phone settings on the Airave.
I was wondering if anyone had experienced similar issues, and if so, if they had found a solution.
Click to expand...
Click to collapse
Airave allows 5 devices at one time. Try connecting to it without one of the other devices using it.
Already tried that
Dredz said:
Airave allows 5 devices at one time. Try connecting to it without one of the other devices using it.
Click to expand...
Click to collapse
--
Techrocket9 said:
This is the case even if none of the other phones are present in the house
Click to expand...
Click to collapse
Now that I'm home I see it's working just fine, I have 3 devices accessing it.
Sent via LTEVO!
jeffsanace said:
Don't know if this will work because I'm away from home and can't confirm. In the mobile network settings is a setting to turn lte off, cdma only mode. My guess is the cdma/lte mode is what's causing the issue.
Sent via LTEVO!
Click to expand...
Click to collapse
jeffsanace said:
Now that I'm home I see it's working just fine, I have 3 devices accessing it.
Sent via LTEVO!
Click to expand...
Click to collapse
I've been having issues as well, my issues are with sms. I keep getting the same messages over and over from people and I'm unable to send any. I just unplugged it before I saw your suggestion to change the phone to CDMA only. I switched it and I'm waiting for the Airave to connect. We'll see if it helps.
Edit: Airave is back up and everything seems to be working fine. Thanks for the tip.
Alas...
ausch30 said:
I just unplugged it before I saw your suggestion to change the phone to CDMA only. I switched it and I'm waiting for the Airave to connect. We'll see if it helps.
Edit: Airave is back up and everything seems to be working fine. Thanks for the tip.
Click to expand...
Click to collapse
Alas, CDMA mode did nothing to connect me to the Airave.
ausch30 said:
I've been having issues as well, my issues are with sms. I keep getting the same messages over and over from people and I'm unable to send any. I just unplugged it before I saw your suggestion to change the phone to CDMA only. I switched it and I'm waiting for the Airave to connect. We'll see if it helps.
Edit: Airave is back up and everything seems to be working fine. Thanks for the tip.
Click to expand...
Click to collapse
I had the same problem... Was in phone with customer service for almost 2 hours... Then I asked about my airrave and they said reset it... And it fixed it right away.. then they gave me a 25 dollar credit for spending almost 2 hours on the phone.
Sent from my EVO using Tapatalk 2
Techrocket9 said:
Alas, CDMA mode did nothing to connect me to the Airave.
Click to expand...
Click to collapse
I had an issue like this when I first got my EVO LTE a few days ago. At first I couldn't connect and then it would let me make phone calls but all text messages would appear as if they failed and even if I retried sending 20 times they would fail. I personally think it was my old phone (OG EVO 4G) causing a problem as it was still on and my EVO LTE would never connect to my Airave! I played with it for over an hour trying to get it to work but then I thought of turning my old phone off and then resetting/unplugging the Airave and when it came back online my new EVO LTE connected without issue and I haven't had a problem since! See if that works for you?
5th
It works now
Ep3n3wp said:
Then I asked about my airrave and they said reset it...
Click to expand...
Click to collapse
It's working now. Thank you for the tip. I wonder if it installed a firmware update that was pushed to it during the reset...
If your phone is not yet activated, DO NOT activate it with an airrave present. For some reason, the OTA activation doesn't work right unless you're connected to a real tower.
FWIW, also try changing your Roaming to "Sprint Only", and also, update your PRL.
Mine finally connected when I did that as well as changing from LTE/CDMA to CDMA only.
turned off inactive phone and it texts again
Fifth313ment said:
I had an issue like this when I first got my EVO LTE a few days ago. At first I couldn't connect and then it would let me make phone calls but all text messages would appear as if they failed and even if I retried sending 20 times they would fail. I personally think it was my old phone (OG EVO 4G) causing a problem as it was still on and my EVO LTE would never connect to my Airave! I played with it for over an hour trying to get it to work but then I thought of turning my old phone off and then resetting/unplugging the Airave and when it came back online my new EVO LTE connected without issue and I haven't had a problem since! See if that works for you?
5th
Click to expand...
Click to collapse
Wow! worked perfectly... after getting a headache with sprint support...
I tried rebooting moden router, airrave... lucky for me I saw your post about the non active phone being on, I turned it off, rebooted the airrave, and I can now send text messages again....
good tip!! thanks so much for the help
Hey guys not sure if this is the right area for this question. So I just got my new HTC DNA phone and it won't connect via my wireless N network, it will talk on G though. I originally had my WiFi set only to transmit on N, but now I have to leave it set for mixed mode. I have told it to forget my network and set it up several times. Nothing will get it to talk on N. I even tried old B and it would talk there.
My router is a Linksys by Cisco WRT310N v1 with Firmware Version: v1.0.10 (newest). I have even tried to power it off and back on again, no change. I even tried to reboot my phone several times in the process too.
For a bit yesterday when messing with this I showed connected to WiFi and to 4G at the same time.
Thoughts?
Updates:
- SSD is broadcast, otherwise my none of my phone's see the network.
- Tried a factory reset, no change.
- Router only broadcasts on 2.4GHz freq.
I can connect to my 'N' at home no issues. I am broadcasting the SSID, not sure if it works with it hidden. I had some issues with that on a prior device / custom ROM.
charlatan01 said:
I can connect to my 'N' at home no issues. I am broadcasting the SSID, not sure if it works with it hidden. I had some issues with that on a prior device / custom ROM.
Click to expand...
Click to collapse
Good to hear that yours works! I am also broadcasting the SSID, as I also had issues with my Incredible and Incredible 2 not connecting. Also when I am transmitting just N, my phone does see it but just won't connect.
I can connect to my N at home too. Can connect on both the 2.4 and 5GHz as well.
Sent from my Droid DNA using xda premium
cortesjues said:
I can connect to my N at home too. Can connect on both the 2.4 and 5GHz as well.
Sent from my Droid DNA using xda premium
Click to expand...
Click to collapse
Thanks for the info. It seems my router only broadcasts on the 2.4GHz freq, don't see anyway to set it to 5GHz.
I also just did a factory reset to see if that makes any difference, which it does not. I'm going to swing by a Verizon store today and see what they can do about swapping my phone out with another new one. If they can't or won't I'll just stick with the phone, as I don't want to play the refurbished game again.
chayos00 said:
Thanks for the info. It seems my router only broadcasts on the 2.4GHz freq, don't see anyway to set it to 5GHz.
I also just did a factory reset to see if that makes any difference, which it does not. I'm going to swing by a Verizon store today and see what they can do about swapping my phone out with another new one. If they can't or won't I'll just stick with the phone, as I don't want to play the refurbished game again.
Click to expand...
Click to collapse
Did you check if your dba could connect to another router ? It could just be some type of incopatibility issue with the DNA and your specific router. Also double check the routers firmware is up to date
Sent from my Droid DNA using xda premium
cortesjues said:
Did you check if your dba could connect to another router ? It could just be some type of incompatibility issue with the DNA and your specific router. Also double check the routers firmware is up to date
Sent from my Droid DNA using xda premium
Click to expand...
Click to collapse
So far I haven't had the chance to get to another router. I'm going over to my in-laws later today, so I'll give it a shot there. So if it works, then I know it's my router, which is only about 2-3 years old, but hey ya never know...
I checked the router firmware yesterday, it's the newest one out there for it.
Not sure if the Verizon store has the capabilities to reflash phone firmware, but I'm going to ask them when I stop by later today.
So when I tested my phone at my in-laws with their WiFi it connected to their Wireless N network. So turns out my phone doesn't like my router's Wireless N setup. I'll try a factory reset on my router to see if that makes any difference.
I have searched all over and I don't find an answer, if I'm missing a thread please just point me in the right direction.
My home wifi has been working with my Note just fine since I got the phone (cue ominous music) up until yesterday. Last night, it started asking me for a password (which was weird, because it hadn't since I first got the phone and set the connection up), and I put the password in, but it kept saying "authorization error." I am really frustrated, I rebooted the phone, the router, removed the home wifi connection (the "forget" button) and reinput it -- I even booted into "safe" mode to make sure it wasn't some app -- no joy. It's a very simple linksys router, WPA/WPA2 security, all the other tablets/computers/phones in the house work just fine (tablets/other phone Android, laptops Windows.) And my Note was working just fine until last night -- no recent software install or update, it was seemingly just random. It's a stock Verizon Note, I haven't even bothered to root since it does everything I want.
Here's the kicker: I connect to OTHER public networks just fine. I connected to my work and McDonald's wifi this morning, no problems.
What could be wrong? I really need to be able to use my wifi at home, I don't see anything in Google or on the boards about this. I am hoping my search-fu is weak and someone knows what is up with this.
restore defaults on your router, then setup a new password.
Hope this Helps....
MaureenMun said:
I have searched all over and I don't find an answer, if I'm missing a thread please just point me in the right direction.
My home wifi has been working with my Note just fine since I got the phone (cue ominous music) up until yesterday. Last night, it started asking me for a password (which was weird, because it hadn't since I first got the phone and set the connection up), and I put the password in, but it kept saying "authorization error." I am really frustrated, I rebooted the phone, the router, removed the home wifi connection (the "forget" button) and reinput it -- I even booted into "safe" mode to make sure it wasn't some app -- no joy. It's a very simple linksys router, WPA/WPA2 security, all the other tablets/computers/phones in the house work just fine (tablets/other phone Android, laptops Windows.) And my Note was working just fine until last night -- no recent software install or update, it was seemingly just random. It's a stock Verizon Note, I haven't even bothered to root since it does everything I want.
Here's the kicker: I connect to OTHER public networks just fine. I connected to my work and McDonald's wifi this morning, no problems.
What could be wrong? I really need to be able to use my wifi at home, I don't see anything in Google or on the boards about this. I am hoping my search-fu is weak and someone knows what is up with this.
Click to expand...
Click to collapse
I have been experiencing this problem for the past 4 days. I have owned my Note II since December 25, 2012 and it has been working on any WIFI AP ive tried. 4 days ago in the middle of the day, my phone started giving out "authorization error" and would not let me log in to my home WIFI. I have 4 computers, 3 smartphones and other devices all working perfectly in my home WIFI. My problem even occurred when connecting to open, unsecured WIFI AP also. Nothing seemed to work. I called Verizon and did all the steps leading up to factory reset. With no luck on any tricks or tips from them I called Samsung. They walked me through the same processes and everything, so I decided to do a factory reset. This did not fix anything. I still get "authorization error" and "wrong password" on any WIFI i try to connect to.
I found out yesterday if I stand within 5 feet of my WIFI router I can connect and browse the internet for a few minutes until it kicks me off and does the same old "authorization error". If I sign in to my WIFI within the 5 feet and walk away, it disconnects and again, gives me the error messages.
I called Verizon back and they are sending me a replacement phone.
TL;DR:
Try accessing your WIFI when you are right next to it.
If problems still persist, call your carrier.
I hope your phone isnt as busted as mine.
Argh, that's bad. At least my phone connected to open networks so I knew the hardware was ok -- I wiped the router and set it up again (per the suggestion in this thread) and I'm good for now. (Embarrassed I didn't think of that myself) Hope you have better luck with your replacement phone!
soaptylerdurden said:
I have been experiencing this problem for the past 4 days. I have owned my Note II since December 25, 2012 and it has been working on any WIFI AP ive tried. 4 days ago in the middle of the day, my phone started giving out "authorization error" and would not let me log in to my home WIFI. I have 4 computers, 3 smartphones and other devices all working perfectly in my home WIFI. My problem even occurred when connecting to open, unsecured WIFI AP also. Nothing seemed to work. I called Verizon and did all the steps leading up to factory reset. With no luck on any tricks or tips from them I called Samsung. They walked me through the same processes and everything, so I decided to do a factory reset. This did not fix anything. I still get "authorization error" and "wrong password" on any WIFI i try to connect to.
I found out yesterday if I stand within 5 feet of my WIFI router I can connect and browse the internet for a few minutes until it kicks me off and does the same old "authorization error". If I sign in to my WIFI within the 5 feet and walk away, it disconnects and again, gives me the error messages.
I called Verizon back and they are sending me a replacement phone.
TL;DR:
Try accessing your WIFI when you are right next to it.
If problems still persist, call your carrier.
I hope your phone isnt as busted as mine.
Click to expand...
Click to collapse
Ok............ wow you have me 100% nervous now. I've been experiencing this issue ever since I unlocked, rooted and ROM'd my Note 2 back in the middle of December, and I experience the problem with only my Wireless-N SSID on my router. I can connect to the Wireless-G band just fine but the N one gives me this error no matter whether it's open or not. I seriously hope this isn't an issue of broken hardware..............
I figured this was worth mentioning. I have 3 Note 2's in my household, 2 of them are running Beans Build 5 and Perseus kernel overclocked and the other phone is totally stock.
All 3 phones have the exact same issue of connecting to the 802.11 N band on my router. They connect to the G band just fine. I think this rules out any worries about it being a lemon issue. Most definitely is a Samsung software issue that's been happening to multiple models going back a few years. Here's a google search of this issue using non-phone specific parameters. Notice how ALL phone specific forums point to a Samsung device.
I have a bad feeling that this is not something that will be getting resolved any time soon.
Edit:
The plot thickens. I have performed some tests on my router to see if I could get my phone to connect. Well here's my results:
5Ghz band = Wireless-N Only = Authentication error occurred
5Ghz band = Wireless-A/N Mixed = Connects instantly
2.4Ghz band = Wireless-N Only = Authentication error occurred
2.4Ghz band = Wireless-G Only = Connects instantly
The problem is clear. It's Wireless-N. I can connect just fine at Wireless-A speeds (54mbps max signal) and everything up to Wireless-G, independent of frequency, but as soon as I try to force Wireless-N onto my phone, it craps out and fails to authenticate. This happens regardless of whether I have the network encrypted or not.
And based upon my google search I have linked to in this post, I doubt this is something we can expect to be fixed anytime soon. Oh yeah and for the record, when I have my router set to Wireless-N only mode, I was able to connect instantly without error on my crappy old HTC Thunderbolt running a hacked together AOSP 4.0.3 ROM.
Yep............... GG Samsung
wireless n has been a unreliable joke since it was released...my favorite routers are the linksys wrt-54gl running linux dd-wrt firmware. one of the most affordable rock solid routers built. its only g band but most people do not need anything faster for home use. heck most of us cant afford the t1 type connection speed to utilize n band anyway.
Exact same problem as well...I'll have to try the Wireless N-only vs. Auto to see if that fixes it...
EDIT: Both wireless mode settings of 'N-only' and 'Auto' caused the problem. I had to set it to 'Legacy' in order to get the connection to stick without authentification errors. Have an ASUS RT-N66U router...
EDIT 2: Did the same thing on my Cisco E3000 and it worked as well.
Really looks like a Sansung wifi bug on the Note 2....
vortmax said:
Really looks like a Sansung wifi bug on the Note 2....
Click to expand...
Click to collapse
It's not Samsung. There have been issues with myriad devices and wireless N pretty much the whole time it's been around. Android OS or the the N standard-- I personally know people with other manufacturers hardware and the exact same issues. If it's an OS problem, you would think it would be fixed by now, but who knows, like was mentioned above, very few people need the bandwidth that wireless n can theoreticly provide.
Good Luck,
Jason
jacampb2 said:
It's not Samsung. There have been issues with myriad devices and wireless N pretty much the whole time it's been around. Android OS or the the N standard-- I personally know people with other manufacturers hardware and the exact same issues. If it's an OS problem, you would think it would be fixed by now, but who knows, like was mentioned above, very few people need the bandwidth that wireless n can theoreticly provide.
Good Luck,
Jason
Click to expand...
Click to collapse
It's definitely something specific with Samsung and the N2 since my cousin's G3 connects to the same router on 5GHz WirelessN/Auto with no issues at all. I think they have a bug to fix...
Can someone else perform a check with their Note 2 on a Wireless N only setting? It seems this is a bug that really need to be fixed.
vortmax said:
Can someone else perform a check with their Note 2 on a Wireless N only setting? It seems this is a bug that really need to be fixed.
Click to expand...
Click to collapse
Mines been working on N only since I got it. Rooted and running about 6 different ROMs.
Sent from my SCH-I605 using xda premium
I just had this issue come up when moving to an AOSP ROM this morning. I even nandroided to a previous ROM that had working WiFi and still not working. I restore defaults on my router and reset all my security settings. Still getting the same authentication error.
Sent from my SCH-I605 using xda app-developers app
For the people experiencing this issue, are you on 4.1.1 or 4.1.2?
vortmax said:
For the people experiencing this issue, are you on 4.1.1 or 4.1.2?
Click to expand...
Click to collapse
I have tried roms that were 4.1.1 and 4.1.2 with no luck.
Sent from my SCH-I605 using xda app-developers app
I am pretty much to the point of using Odin to go back to stock and see if that fixes it. I went back to stock rooted rom that was my first backup and the problem still carries over.
Sent from my SCH-I605 using xda app-developers app
Hi folks,
I have a weird situation with my phone.
Under stock, the only way I could get a data connection is if I ran it in CDMA mode. If I turned on LTE/CDMA mode it would automatically show as "disconnected."
If I used signal check pro, it would say I am receiving eHRPD signal, but unregistered.
I can connect fine via EV-DO. Have a stable connection.
Under Cyanogemod, LTE is turned on, but automatically falls back to EV-DO.
I did talk with Ting and everything seems to be normal.
Any ideas?
Im curious about this too
I'm curious about this too, because I have the opposite problem where I only connect over CDMA/LTE
(stock 4.3 rooted, S-off)
essextrain said:
I'm curious about this too, because I have the opposite problem where I only connect over CDMA/LTE
(stock 4.3 rooted, S-off)
Click to expand...
Click to collapse
Same here. Can't use CDMA only mode as it immediately disconnects. Also having issues with LTE dropping out constantly and I can only get it back with airplane toggle. Weird thing is that it never drops if the phone is plugged in. I've tested this extensively too.
Sent from my EVO using xda premium
dsEVOlve said:
Same here. Can't use CDMA only mode as it immediately disconnects. Also having issues with LTE dropping out constantly and I can only get it back with airplane toggle. Weird thing is that it never drops if the phone is plugged in. I've tested this extensively too.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
That's really odd...
My wife has the same phone and everything appears to be working fine for her.
Well, I tried going to LTE/CDMA mode last night and it looks like everything works as expected now...
Really weird.
I know Sprint has been aggressively upgrading towers in the area.
Maybe just a glitch in the matrix?
I am running stock and have been having this problem for awhile now. Phone works fine in CDMA only mode (EV-DO) or if LTE connects. But the phone absolutely will not function over eHRPD, giving the error "Unable to establish a wireless data connection. LTE:ESM-65535". I had this problem three months ago for about a week, then it went away. Came back two weeks ago for about a week. And now it just started happening again. I always contacted the various support channels, although I never really heard back from anyone, so I don't know if someone got my message and fixed it or if it just went away on its own.
When it is fixed, my phone doesn't attempt to connect to eHRPD, so that when LTE drops out or is unavailable, my One Max drops to EV-DO and works great. But, after the over-the-air update from HTC two days ago and a forced profile update, my phone once again tries to connect via eHRPD, which clearly does not function.
Okay, I have finally fixed it myself. I used SignalCheck Pro to enter the Data/EPST menu in edit mode, typed in my MSL, went to Advanced, selected eHRPD and set it to Disabled. Now the phone seems to work just fine again. Still no idea what is going on here, or why I didn't think to fix it this way before, but here we are.