Jump to content

Jelly Bean for One X

Crimson01

By Crimson01
in HTC

 Share

Recommended Posts

puch96 Member Level: 1x Advanced

puch96

Posted
Posted

HTC stated that all 2012 released phones will have priority. It is rumored that the One X and Vs ATT and T-Mobiile will be seing updates stateside within 2 to 3 weeks. Then, the HTC EVO 4G LTE will most likely see the udpate maybe weeks from then.

My quess (quess only) is that we could see an update by end of the year.

http://www.gottabemobile.com/2012/11/12/android-4-1-jelly-bean-release-date-predictions/

 

The thing is is that HTC / Sprint knows about the LTE connectivity issues with the EVO, so they might be conducting extensive testing to make sure they correct the issue (or at least significantly improve it) before they launch the next round of updates....

Link to comment
Share on other sites
Mondays In Flames Member Level: eHRPD

Mondays In Flames

Posted
Posted

HTC stated that all 2012 released phones will have priority. It is rumored that the One X and Vs ATT and T-Mobiile will be seing updates stateside within 2 to 3 weeks. Then, the HTC EVO 4G LTE will most likely see the udpate maybe weeks from then.

My quess (quess only) is that we could see an update by end of the year.

http://www.gottabemo...te-predictions/

 

The thing is is that HTC / Sprint knows about the LTE connectivity issues with the EVO, so they might be conducting extensive testing to make sure they correct the issue (or at least significantly improve it) before they launch the next round of updates....

 

I hope you're right about the extensive testing they might be doing. I'll be more than happy to wait a couple of extra weeks to know that my phone will receive an update that fixes the LTE issue. I have experiences LTE down here in Miami, but the phone has only connected once on it's own. I think that is pretty shitty, tbh. When I had my sensation, granted HSPA+ isn't really anything special, I would always be connected to "4G" no matter what. I never really had problems with the signal, but HTC seems to have dropped the ball with this phone, which will hopefully, sometime soon, get it's problems fixed.

 

 

-Luis

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.

×
 Share
Go to topic listing

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • T-MoblieUser207
      Network Vision/LTE - New York City Market

      By T-MoblieUser207 · Posted

      The DAS at LGA Terminal B actually has n41 at 100+20, but if you are deprioritized, good luck on the busy days, as all the bands are congested, even B41 and n41, with data being worse than 128kbps international roaming. It has SA active for n41 as well. The L train tunnel is actually 80+20 for n41, with SA n41 active. Speeds aren't anything compared to Philadelphia's DAS system that has n41 though. The gig+ upgrades are expanding, as eNBs 894588 (Sprint convert site) and 55987 can both pass 1 Gbps now. Clocked nearly 1.3Gbps on eNB 55987 today.
    • Rickie546
      Official Tmobile-Sprint merger discussion thread

      By Rickie546 · Posted

      Hopefully this goes thru!  https://www.reddit.com/r/tmobile/comments/1211mh7/tmobile_files_another_sta_application_to/
    • Paynefanbro
      Network Vision/LTE - New York City Market

      By Paynefanbro · Posted

      Yup 80MHz C-band + 40MHz DoD for a total of 120MHz. They should be pretty well setup post-clearance. — — — — — Famous Verizon site on Atlantic referenced in this reddit post got moved to the top of the building next door. — — — — — Also looks like I mapped a T-Mobile oDAS node eNB 347812 in Brooklyn Heights. Streetview shows it as one of the CC nodes with no antenna on top as of May 2022 but this specific eNB was first mapped this month. I didn't notice that I mapped it until I got home but the range on it is significantly greater than the normal "antenna-less" nodes T-Mobile deploys. I'm wondering if it got upgraded to the new 5G oDAS design but I won't be able to check it out until next weekend.  
    • transitwatch889
      Network Vision/LTE - New York City Market

      By transitwatch889 · Posted

      I didn't know they had access to 80 MHz of c-band that does change some things then once that's online
    • Trip
      SignalCheck Beta Crew Forum

      By Trip · Posted

      While I've been loath to update my Samsung devices past the May 2022 update to keep the Band Selection tool, I note that it looks like Android 14 is going to add Timing Advance for NR to the API.  (Was looking today as I have another Verizon A42 5G now that I'm going to unlock for T-Mobile, and wanted to figure out if I should let it update or not.)  Since I can technically make band changes from *#73#, on the A42 5Gs, I can probably live without the Band Selection tool if a later Android version adds something useful like TA values. I assume SCP will be updated to support that once it becomes publicly available.  The real question is whether or not the phones will support it.  My S21FE and A42 5G devices do on LTE, but I know the S22 and the A32 5G do not support it even on LTE, providing just zero in that field. - Trip

  • Recently Browsing

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