Jump to content

OTA coming for EVO next few days...


Crimson01

Recommended Posts

The loop in nebraska (norfolk) is 1x

 

I wonder if the ever finished Mississippi. I know they did Baton Rouge in summer 2010 at least they let us use Alltel 850 evdo natively for several years before this which was smoking fast and worked great. It was a sad day when it was removed from us. And lake Charles was early 2011.. Even Cricket had EVDO before Sprint did there. I am glad to see their NV plan is more aggressive than their EVDO one was.

 

Sent from my C64 w/Epyx FastLoad cartridge

  • Like 1
Link to comment
Share on other sites

If this guy is to be believed, the update will be available 8/22. (Wednesday)

 

http://forums.androi...ing-8-22-a.html

 

Evo 4G LTE software update coming next week

 

Customer Initiated: 8/22/12, Available via Network Push: 8/28/12

 

Enhancements/Fixes:

 

-Browser randomly closes from bookmarks

 

-Minor Bluetooth fix

 

-Latest version of Google Wallet

 

-LTE scanning improvement

  • Like 2
Link to comment
Share on other sites

Why do people think updates come out as soon as they wake up. 2 it is a search for update in which you have to tell your phone to look for it starting today, and 1 week later it will be pushed out to all.

 

Sent from my EVO using Tapatalk 2

Link to comment
Share on other sites

Why do people think updates come out as soon as they wake up. 2 it is a search for update in which you have to tell your phone to look for it starting today, and 1 week later it will be pushed out to all.

 

Sent from my EVO using Tapatalk 2

 

I'm assuming this was directed at my comment... Clearly I know to check for the update manually. Thanks for your concern though.

  • Like 1
Link to comment
Share on other sites

With the GS3 LG8 update, I was not able to manually or automatically able to get the update for almost 2 weeks. I could have downloaded it from a third party and applied it, but I was curious to see how long it would take.

 

Robert via CM9 Kindle Fire using Forum Runner

  • Like 2
Link to comment
Share on other sites

There is still more day left!!! If as usual, it will be at 11:59:59, just like when a software company says it will be release in Q1, it is the last day of Q1.

Link to comment
Share on other sites

Well on a side note htc released the source code for 1.13 right after the 1.22 ota was released. It looks like htc finally released the source code for the current 1.22 software so hopefully thats a sign that the next ota is right around the corner.

 

http://htcdev.com/devcenter/downloads

  • Like 2
Link to comment
Share on other sites

There is still more day left!!! If as usual, it will be at 11:59:59, just like when a software company says it will be release in Q1, it is the last day of Q1.

 

Q1??? of what?

Link to comment
Share on other sites

Well on a side note htc released the source code for 1.13 right after the 1.22 ota was released. It looks like htc finally released the source code for the current 1.22 software so hopefully thats a sign that the next ota is right around the corner.

 

http://htcdev.com/devcenter/downloads

 

Good catch!

Link to comment
Share on other sites

Did sprint ever officially say it was coming that day?

 

Sent from my C64 w/Epyx FastLoad cartridge

 

Not that I know of but that has never stopped Rampant Speculation. He is usually followed by his cousin Profound Disappointment.

  • Like 2
Link to comment
Share on other sites

FYI to you EVO 4G LTE users, I noticed this comment today on the sprint.com forum from a Sprint tech.

 

I think this might be the most public acknowledgement from Sprint that there is a "known issue" with the device connecting to LTE and that there will be an OTA fix.

 

They just put an LTE repeater in our building last week for testing and in order to get it to connect to any of our phones, we had to reset the network settings through a specific ## code. I'm not saying it should have to be the same for live sites, but in the small % of users who are unable to connect to 4G LTE in an LTE market, it may be required in order to resolve the issue. CHIPnKC - I'd be happy to send you the instructions specific to your phone if you'd like to private message me with your Sprint number.

 

Also - If you are using the HTC Evo 4G LTE, there is currently a known issue with some devices not being able to discover the LTE signal. Both Sprint and HTC are working on refining the signal discover and acquisition process on the phone and will be addressed through a maintenance release.

 

BTW, I don't know what dialer code he is talking about to get certain devices to connect. I know that at least on the GS3 the ##DATA# menu tree with MSL code can force the phone to LTE-only, but this workaround borks it for voice and texting via 1x. (Note that this part of the tech's comment was not directed specifically at any device.)

Link to comment
Share on other sites

As always take the comments from the tech as a rumor.

 

Sent from my C64 w/Epyx FastLoad cartridge

 

Yes, but in this case, the venue is much different than some one-on-one contact between a tech and a single customer. The comment came under the imprimatur of the tech's Sprint logo avatar, and it came in a stickied thread on sprint.com that was started by a Sprint admin expressly as a reaction to the firestorm over the early LTE rollout. Such a forum format, for example, is how they announce official OTA releases. So this was more like an on-the-record public announcement.

  • Like 1
Link to comment
Share on other sites

I am just jaded I guess.. I have had Sprint folks on there also tell you some crazy things almost as bad as the ones on the phone. So I take everything from them as rumors unless it is an official document.

 

Hell, I will take AJs and Roberts word over a Sprint rep any day :)

 

Sent from my C64 w/Epyx FastLoad cartridge

  • Like 1
Link to comment
Share on other sites

In my experience dealing with carriers -- about whom I am just as cynically jaded as anyone is -- the act of admitting in writing in their own public space that some problem is a "known issue" is significant. The use of that term of art can trigger more business concessions, especially if the customer has any leverage at all. (Two years ago, for example, there was a "known issue" with 3G upload speeds on the new Epic 4G, and Sprint extended my 14-day trial until two weeks after whatever time they released a fix so I could confirm that it worked. The fix was released shortly.)

 

Up until the point of saying "there is a known issue," no matter how unquestionably and widely established any problem really is on all the user forums, the reps' script always call for them to say, "This is the first report I have ever heard of that issue, sir." Because in their alternate vocabulary, an issue is not a "known issue" until management officially decides it is "known." And management doesn't do that until there is a solution in the works.

 

BTW, I note that one thing Sprint's thread did not say was when this OTA fix will be released.

  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Excuse my rookie comments here, but after enabling *#73#, it seems that the rainbow sim V2? requires n70 (I turned it off along with n71 - was hoping to track n66) to be available else it switches to T-Mobile.  So this confirms my suspicion that you need to be close to a site to get on Dish.  Have no idea why they don't just use plmn. To test, I put it into a s21 ultra, rebooted twice, came up on T-Mobile (no n70 on s21).  Tried to manually register on 313340, but it did not connect (tried twice). I am on factory unlocked firmware but used a s22 hack to get *#73# working.  Tried what you were suggesting with a T-Mobile sim partially installed, but that was very unstable with Dish ( I think they had figured that one out).  [edit: and now I see Boost sent me a successful device swap notice which says I can now begin to use my new device.  Sigh.  Will try again later and wait for this message - too impatient.]
    • Hopefully this indicates T-Mobile hasn't completely abandoned mmwave and/or small cells? But then again this is the loop, so take that as you will. Hopefully now that most macro activity is done (besides rural colo/builds), they will start working on small cells.   
    • This has been approved.. https://www.cnet.com/tech/mobile/fcc-approves-t-mobiles-deal-to-purchase-mint-mobile/  
    • In the conference call they had two question on additional spectrum. One was the 800 spectrum. They are not certain what will happen, thus have not really put it into their plans either way (sale or no sale). They do have a reserve level. Nationwide 800Mhz is seen as great for new technologies which I presume is IOT or 5g slices.  T-Mobile did not bite on use of their c-band or DOD.  mmWave rapidly approaching deadlines not mentioned at all. FWA brushes on this as it deals with underutilized spectrum on a sector by sector basis.  They are willing to take more money to allow FWA to be mobile (think RV or camping). Unsure if this represents a higher priority, for example, FWA Mobile in RVs in Walmart parking lots working where mobile phones need all the capacity. In terms of FWA capacity, their offload strategy is fiber through joint ventures where T-Mobile does the marketing, sales, and customer support while the fiber company does the network planning and installation.  50%-50% financial split not being consolidated into their books. I think discussion of other spectrum would have diluted the fiber joint venture discussion. They do have a fund which one use is to purchase new spectrum. Sale of the 800Mhz would go into this. It should be noted that they continue to buy 2.5Ghz spectrum from schools etc to replace leases. They will have a conference this fall  to update their overall strategies. Other notes from the call are 75% of the phones on the network are 5g. About 85% of their sites have n41, n25, and n71, 90% 5g.  93% of traffic is on midband.  SA is also adding to their performance advantage, which they figure is still ahead of other carriers by two years. It took two weeks to put the auction 108 spectrum to use at their existing sites. Mention was also made that their site spacing was designed for midrange thus no gaps in n41 coverage, while competitors was designed for lowband thus toggles back and forth for n77 also with its shorter range.  
    • The manual network selection sounds like it isn't always scanning NR, hence Dish not showing up. Your easiest way to force Dish is going to be forcing the phone into NR-only mode (*#*#4636#*#* menu?), since rainbow sims don't support SA on T-Mobile.
  • Recently Browsing

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