Jump to content

One S, One X and possible EvoLTE to get Jellybean this month


Odell

Recommended Posts

What about the Galaxy S3 (SPH-L710)...leaked Jellybean (4.1.1) over at xda with ROMS coming from it now....I think freeza dropped the leaked ROM first, and now it's being customized, but it's an official leaked build (I'm using the DeOdexed leak as my daily driver, so far so good and NO problems at all with anything.)

Link to comment
Share on other sites

I'm more anxious to get LTE than jelly bean. I have it on my Prime, it fixed many of the lag bugs but it's nothing special, IMO.

 

 

-Luis

I agree, looking forward to jb but more interested in the LTE deployment for southeastern Michigan personally.

 

Sent from my UR/evo enabled rocketship on Tapatalk 2

 

 

Link to comment
Share on other sites

I agree, looking forward to jb but more interested in the LTE deployment for southeastern Michigan personally.

 

Sent from my UR/evo enabled rocketship on Tapatalk 2

 

Hopefully the JB update would address the LTE problems too... Maybe I'll get really lucky and get the JB update and never really experience LTE problems :D But maybe that's hoping for too much. One thing at a time :)

 

 

-Luis

  • Like 1
Link to comment
Share on other sites

I'm more anxious to get LTE than jelly bean. I have it on my Prime, it fixed many of the lag bugs but it's nothing special, IMO.

 

 

-Luis

It only took me about 2 days of using CM10 (AOSP Jelly Bean) for me to never, ever want to go back to anything else.

 

For one, I can multitask. Here's hoping HTC fixes that, too.

Link to comment
Share on other sites

If they don't get Jelly Bean out before the SGS3 in the US I'll be purchasing a Samsung phone next time. I love HTC but they have let me down in the past two years. And if they hold onto the Jelly Bean update in order to push some users to the X+ I'll be actively campaigning against them, however I don't think that will happen. My biggest quips are shoddy update schedules, non-removable small batteries, crappy antenna performance and no SD support (exempt on my EVO LTE). They seem to be preferring form over usage factor and not listening to their customers!

Link to comment
Share on other sites

If they don't get Jelly Bean out before the SGS3 in the US I'll be purchasing a Samsung phone next time. I love HTC but they have let me down in the past two years. And if they hold onto the Jelly Bean update in order to push some users to the X+ I'll be actively campaigning against them, however I don't think that will happen. My biggest quips are shoddy update schedules, non-removable small batteries, crappy antenna performance and no SD support (exempt on my EVO LTE). They seem to be preferring form over usage factor and not listening to their customers!

I cant comment on HTC with other providers but I think the update schedules for HTC phones with Sprint has been pretty good. I remember the negative feelings a year and a half ago against Samsung and their very slow update schedule(hello EPIC?). I have to say that so far HTC has not been slow with the EVOLTE. Now if the New year comes around and we dont have JB yet then I may change my mind.
  • Like 1
Link to comment
Share on other sites

I would be willing to bet that every carrier has people complaining that the Android updates don't come fast enough. Once Google announces a new version, that version becomes the Holy Grail Fixer Of All Things Wrong With {insert older version name here}. People then want it yesterday and will complain that so-and-so carrier is the worst with updates.

 

I would say buy a Nexus device if you want fast updates but I have even heard complaints that those updates don't go fast enough.

  • Like 2
Link to comment
Share on other sites

  • 4 weeks later...

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

    • https://www.fiercewireless.com/wireless/t-mobile-gets-little-closer-accessing-its-25-ghz-spectrum-auction-108 Senator Kennedy's bill to grant the FCC temporary auction authority to finish processing the Auction 108 licenses it has sold to their proper licensees. This would greatly benefit T-Mobile.  This delayed process took what would have been a strategic advantage for T-Mobile (1 one year plus head start)  and turned into catch-up, since AT&T and Verizon haven been busy installing their c-band n77 in rural areas.
    • I configured -44/-3 scenarios on an Edge 2022 to be an invalid connection, so yes, it would show no service.. I didn't realize it was a frequent issue though. How certain are you about the other values? Perhaps they are just unchanged from the previous array of signal information that was reported? If that is the case, I can try to have the app discard -44/-3 datapoints and leave the screen unchanged. I worry about the slippery slope of having it display as -140, because that leads users to believe there is a -140 signal present, when in reality we don't know what the actual reading is.   Haha me and you both wish this!!!
    • Following up, I've gone into the office in person today and took my Edge with me. It looks like it now shows "No service" instead of the -44/-3 value.  I saw a lot of "no service" because it apparently does it a lot.  I'll check again on the train ride home later. Assuming I'm correct, is it possible to have some kind of middle ground on this?  I think it was showing other legitimate values, like the TA, even when it was showing -44/-3.  I'd prefer it show the data it has but at -140 dBm in those cases.  I recognize this could be a pain to implement, and if it is, then no worries, mostly curious. EDIT:  But now I'm sitting here thinking "what if the PCI is bad and I don't know it?"  But that can just as easily be the case on other phones that aren't caught.  I do regularly see bad PCI entries on my other devices, so maybe this isn't the best option.  Bleh, I wish this stuff just worked properly! - Trip
    • Forgot to follow up on this. The service was once again abysmal .
  • Recently Browsing

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