Jump to content

New update for Evo 4G LTE


Jaggrey

Recommended Posts

i noticed the LTE connection difference as well. i looked into the LTE scan timer and BSR Max timers and noticed they had changed after the maintenence release. i cant remember the values it set when JB was released, but i "think" they were higher with this maintenance release. i set mine back to 1 and 1, and have the same quick connect and long hold time as i did with the original JB release. my wife's takes longer to connect and disconnects easier. i have not changed her settings yet.

 

Have you noticed if changing the settings affects your battery life?

Link to comment
Share on other sites

i actually changed the settings within a day or two of installing the maintenance release. i had already noticed an increase in battery life with the maintenance release. but i have not noticed a decrease with my changes. if there is, its not enough for me to notice. i work inside a building where i have very low signal all day, so my battery is at about 55% by the end of the day(now). prior to the maintenance release, it was at around 30% with the same 1 and 1 settings.

Link to comment
Share on other sites

The values for LTE scan timer and BSR Max timers are 5 and 4 with the JB release. Mine stayed the same with the maintenance release.

 

i guess it is just wishful thinking on my part then. ;)

Link to comment
Share on other sites

I think the signal threshold changed with the maintenance release. It won't connect or hold to a weaker signal like before.

 

after changing mine back to 1 and 1 on the timers, it seems to be connecting just as it did before. but i have always had mine set at that. it became much better with JB, but seems to be the same with the MR. i dont really have a comparison with the stock settings.

Link to comment
Share on other sites

Sorry for the dumb question... but how do you get to the LTE menu to check the values of LTE timer and BSR timer?

 

 

##data# from the dial pad.

 

 

Sent from my iPad4 using TapatalkHD

Link to comment
Share on other sites

Just my observations since the update:

-I cannot test LTE connectivity since NV has yet to begin here in Phx.

-The battery life has significantly improved. Back to how it was before the JellyBean update. I'm back to getting 24 to 30 hrs on each charge. Love it!

-Proximity sensor works great.

-I have had no issues with Google Nav. Yesterday I used it on a drive from North Phx to South Scottsdale, and it worked perfectly.

Link to comment
Share on other sites

I have noticed a drastic lack of connecting to LTE. My partner has the EVO without the update, and mines with the update, his connected automatically to LTE while mines stayed on 3G. I've tested this on multiple occasions already.

 

Has anyone found a fix for this?

 

 

-Luis

Link to comment
Share on other sites

I have noticed a drastic lack of connecting to LTE. My partner has the EVO without the update, and mines with the update, his connected automatically to LTE while mines stayed on 3G. I've tested this on multiple occasions already.

 

Has anyone found a fix for this?

 

 

-Luis

not even HTC has a fix for it, Im calling it a defective LTE antenna
Link to comment
Share on other sites

I have noticed a drastic lack of connecting to LTE. My partner has the EVO without the update, and mines with the update, his connected automatically to LTE while mines stayed on 3G. I've tested this on multiple occasions already.

 

Has anyone found a fix for this?

 

 

-Luis

 

The update seems to have increased the scan time again, so it seems that it now takes longer to connect to LTE. If you want, you can edit the scan time and from what I've heard it takes it back to hire it would connect before the update.

 

Sent from my GS3 using Tapatalk 2

 

 

Link to comment
Share on other sites

I can't tell the difference personally but that may be due to the fact that I am in atlanta and I have lte everywhere, :D .

  • Like 3
Link to comment
Share on other sites

The values for LTE scan timer and BSR Max timers are 5 and 4 with the JB release. Mine stayed the same with the maintenance release.

 

I think what has changed is the threshold of when it will connect to LTE. If your in a marginal area, it seems you can't connect or reconnect like before.

Link to comment
Share on other sites

I contacted Sprint to get my MSL, but they wouldn't give it to me. Their reasoning was that my phone is under contract. Is this typical? I hear of people getting their MSL all of the time, but I also assume that most people are under the 2 year contract.

 

Is there some way I can trick them into giving it to me, or do I just call and talk to someone else?

 

Sent from my EVO using Tapatalk 2

 

 

Link to comment
Share on other sites

I contacted Sprint to get my MSL, but they wouldn't give it to me. Their reasoning was that my phone is under contract. Is this typical? I hear of people getting their MSL all of the time, but I also assume that most people are under the 2 year contract.

 

Is there some way I can trick them into giving it to me, or do I just call and talk to someone else?

 

Sent from my EVO using Tapatalk 2

 

You called them? I called and asked for the MSL, and got the code and was off the phone in about 1 minute. Very easy, didn't really require much effort at all on my part. Maybe it just depends on who answers the phone?

Link to comment
Share on other sites

I contacted Sprint to get my MSL, but they wouldn't give it to me. Their reasoning was that my phone is under contract. Is this typical? I hear of people getting their MSL all of the time, but I also assume that most people are under the 2 year contract.

 

Is there some way I can trick them into giving it to me, or do I just call and talk to someone else?

 

Sent from my EVO using Tapatalk 2

 

I would say that 8 times out of 10 if you simply just call just to ask for your msl they will say no. You might have better luck simply just calling back and asking again. If you were rooted though, you could use msl reader to get it that way which is a lot easier.

Link to comment
Share on other sites

Another easy way to get your MSL code is to activate another phone online. Every time you use the automated online activation, they will email you your MSL code automatically.

 

But note, that it only works when changing between one LTE device and another LTE device. The online activation fails for me when switching out LTE to WiMax and vice versa. I always have to call when a WiMax device is involved. And when you call to activate, you don't get the email.

 

If you have another LTE device just switch them out online and you will get MSL code emails for both. Every time I switch out a device for the first time, I log its MSL code in Evernote for safe keeping. And all is right with the world. ;)

 

Robert via Nexus 7 with Tapatalk HD

  • Like 5
Link to comment
Share on other sites

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

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well. 
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
    • Looks like a great place for for FWA. Many apartment dwellers only have one overpriced choice.
  • Recently Browsing

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