Jump to content

HTC EVO LTE OTA - System Update 1.22.651.3


Recommended Posts

Posted

The only way to keep your phone from connecting to the airave is to shut off the airave or leave its range.

 

Or use the whitelist.

Posted

 

Or use the whitelist.

 

Yes, but you are opening the door for interference between the airave and macro cell signal.

 

From JBtoro on Forum Runner

Posted

I would like to thank everyone for all the insight on how the airave works.

 

Approx. an hour after my last post on this thread my wifi started to work just fine. I have no idea what changed because I did nothing to the phone or access point.

Shortly there after I left home for work and my phone has been working great. Now that I am back home my phone connects to the wifi access point with no problems, but I am having the same issue again. Pages will not load. I am using the same access point for my laptop and am having no issues at all.

Posted

Lte is still acting weird after the update. I updated the radios and I still will have problems connecting to lte. Have to turn data off to get it to reconnect.

Posted

Lte is still acting weird after the update. I updated the radios and I still will have problems connecting to lte. Have to turn data off to get it to reconnect.

 

Did you apply just the radio or the full firmware package?

Posted

Played around with my evo lte today to see if my signal was worse and speeds lower after the update( I reflashed the firmware +data profile update). I did10 test cycles using rootmetics and dBm average was -104 with average downloads of 127kbps and uploads of 188kbps. I ran an RUU back to stock shipped and ran 10 test cycles again, this time average dBm was -98 with average downloads of 527kbps and uploads of 308 kbps.

All tests were done at the same location. I also activated my S3 on my sisters line (temp) and did tests at the same time, tests were on par with the EVO lte in signal strength and speed before the update.

 

I ended up having a longer lunch today then scheduled, so i drove out to the site just north of town again, when my evo LTE switched towers, it showed i had good signal strength, but no 3G for about 40-45 seconds (this is after the update) lol.

 

I have no idea if these results are coincidence or if i have a defect evo lte. On wednesday, ill have a sprint store take a look at it (also has the light bleed issue)

Posted

I hope someone might be able to help me.

 

Prior to this upade my phone was working great (expect Goggle Wallet) After the update I can not connect to my WiFi via a secure link. If I open it up, it will with no problems.

 

I have done a factory reset and still no go. Sprint also had me do a full reset and it still does not work.

 

I have tried to reset my modem with no luck. I am currently using the WPA/WPA 2

 

When trying to connect it will ask for my password. After inputing the pw it keeps saying incorrect pw entered. I have ensured I typed it in right but still no go. After the second try it will tell me the modom is out of range. When I toggle the WiFi switch it starts over again by asking for the pw.

 

 

 

 

Sprint is willing to replace the phone (refurb ofcourse), I am just trying to avoid that if possible.

 

Dennis

Posted

I hope someone might be able to help me.

 

Prior to this upade my phone was working great (expect Goggle Wallet) After the update I can not connect to my WiFi via a secure link. If I open it up, it will with no problems.

 

I have done a factory reset and still no go. Sprint also had me do a full reset and it still does not work.

 

I have tried to reset my modem with no luck. I am currently using the WPA/WPA 2

 

When trying to connect it will ask for my password. After inputing the pw it keeps saying incorrect pw entered. I have ensured I typed it in right but still no go. After the second try it will tell me the modom is out of range. When I toggle the WiFi switch it starts over again by asking for the pw.

 

 

 

 

Sprint is willing to replace the phone (refurb ofcourse), I am just trying to avoid that if possible.

 

Dennis

 

Just as a troubleshooting step have you tried securing your wifi network with WEP and then see if you are able to connect with the Evo? I know WEP is considered less secure but it might be helpful in diagnosing your problem if the phone will connect with a different setup.

 

Are you also having trouble connecting to other secured wifi, especially networks that you could previously connect to like your work or a friend's house?

 

I can't say I can fix your problem but those were just a couple questions that came to mind.

Posted

To clarify a little for you, the airave broadcasts like a mini tower replacing your connection to the "macrocell". 1900mhz for voice and 3G data. This is why Sprint only wants to send out an airave to people who have little/no coverage in their house. It could potentially cause interference issues with the cell towers for people around it. The only way to keep your phone from connecting to the airave is to shut off the airave or leave its range.

 

It doesn't interfere. Sprint's servers sets up the EV and 1X channel that your box will be on based on your GPS location. 2 reasons: so they are on the right SID, NID, and licensed frequency for your area, and also channels that will not interfere with the tower carriers around you. Now someone could have the servers set wrong but I'm sure there are some safe guards as broadcasting on another cell phone carriers frequency is a big no-no ;)

Posted

Just as a troubleshooting step have you tried securing your wifi network with WEP and then see if you are able to connect with the Evo? I know WEP is considered less secure but it might be helpful in diagnosing your problem if the phone will connect with a different setup.

 

Are you also having trouble connecting to other secured wifi, especially networks that you could previously connect to like your work or a friend's house?

 

I can't say I can fix your problem but those were just a couple questions that came to mind.

 

I tried that after I wrote the orignal post. I was able to get a secure connection using WEP. I have not tried any other WiFi's yet but will over the next couple of days. I am content as of now. Hope there is a more major update soon. This update did not change my color saturation on the camera, but that is a minor thing for me.

Thanks for the input.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Well you officially fried my brain. Many of these topics are well beyond my very rudimentary amateur knowledge.. this has my head spinning even more than usual. When someone figures it out, just let me know what I need to do with the app! 😂
    • Confusingly, there are two different types of Cell IDs, the NR Cell ID (NCI) and the Local Cell ID, which I will call the LCID from here on out. From my understanding, @Trip is trying to get the LCID from the NCI but the same gNB is showing up for multiple sites in the app. Some background for those that don’t know about NCIs (NR Cell ID) and how they relate to gNBs and LCIDs. Just like the E/GCI which is comprised of the eNB + LCID with the eNB denoting the site, the NCI is comprised of the gNB + LCID with the gNB denoting the site. A major difference is that the eNB is a fixed number of bits in the E/GCI but the gNB can vary between 22-32 bits (out of 36) in the NCI and there is nothing transmitted which tells you what the length is. The reason for the mentioning LTE sites is that Verizon’s gNB numbering scheme in most of the USA is based upon the sites eNB (using the rules I mentioned) and a 22-bit gNB. Additionally, their LCIDs start at 25 and increment by compinations of 16 and 1. Basically, it is common to see LCID sets of 25/26/27, 41/42/43, and 57/58/59. Looking at Trip’s data and some other data from the area, they are not following the format used in the rest of the USA.  From what I can tell, they are using a 29-bit or 30-bit gNB (that gives LCIDs that follow Verizon’s standard patterning). 29-bit shares the same gNB across the two locations, while 30-bit splits the two sets: 18504107674 - gNB 144563341 + CLID 26 (29-bit) or 289126682 + CLID 26 (30-bit) 18504107690 - gNB 144563341 + CLID 42 (29-bit) or 289126682 + CLID 42 (30-bit)  18504107691 - gNB 144563341 + CLID 43 (29-bit) or 289126682 + CLID 43 (30-bit)  18504107706 - gNB 144563341 + CLID 58 (29-bit) or 289126682 + CLID 58 (30-bit)  18504107707 - gNB 144563341 + CLID 59 (29-bit) or 289126682 + CLID 59 (30-bit) 18504107738 - gNB 144563341 + CLID 90 (29-bit) or 289126683 + CLID 26 (30-bit)  18504107739 - gNB 144563341 + CLID 91 (29-bit) or 289126683 + CLID 27 (30-bit)  If true, this is a problem for SignalCheck and other mapping apps because this means they are using at least two different gNB lengths depending on the location in the USA.
    • Yeah I can confirm that the status bar is updating correctly and as often as the main app!  Great to have that back after so long. Waiting on the app to pick up the 5G data.  I'm on AT&T and I find that it only reports the 5G signal data a fraction of the time.  Once I can get it to pop back up I'll send a report with the LTE RSRP showing up in the status bar instead of the NR RSRP. I am not sure if it is new behavior with the Beta because I had it set to just show the Band since I couldn't display the band and signal at the same time. Edit:  Sent a diagnostic and here's a screenshot:
    • Yes, for various reasons the beta mapping project was limited to S4GRU sponsors at launch. It's still a work in progress but I have added a few users as it has evolved. I am inclined to leave it as-is for now -- it's not completely off-limits to discuss here (especially if there's an outage), but with so many posts I just try to keep discussions organized. RAvirani handles the map server and he monitors the other thread closer.   I might be confused, but are we talking apples and oranges here? My interpretation was Trip is talking about NR cells on different sites sharing cell IDs as far as the app is concerned, while the other comments are about LTE to NR cell ID calculations?
    • I hope this is true!! The Android development team did claim this bug was fixed several months ago, and it is typical for it to take several releases before changes are included. I was on the Android beta until I got my Pixel 9, now I am back on the public releases. With each monthly update, I have optimistically checked this icon and been disappointed. This would be fantastic to get back!   Could you send some diagnostic reports when you see this please? It is new behavior with QPR Beta 3?
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...