Jump to content

HTC and Samsung vaguely address Jelly Bean upgrades


pyroscott

Recommended Posts

HTC and Samsung have already addressed questions about their upgrade plans for Jelly Bean on their devices.

 

PocketNow received the statement from Samsung saying:

"Samsung will soon announce which additional devices are eligible for the Jelly Bean update. As the world's largest smartphone manufacturer, Samsung leads the Android community with best-in-class devices like the Galaxy S III, and is creating new device categories with products like the Galaxy Note. Samsung has delivered the most Nexus-branded lead OS devices and we are pleased that Google will be bringing Samsung Galaxy Nexus and Nexus S customers the first experiences of Jelly Bean on a handheld device."

 

 

Android Central was able to get a statement from HTC stating:

"We are excited about Android Jelly Bean and are planning to support it across a variety of our devices. We are reviewing the software to determine our upgrade plans and schedule, so please stay tuned for more updates on specific device upgrade plans."

 

While this doesn't tell us anything really, there is speculation that any device that will see Ice Cream Sandwich, should also see Jelly Bean since it is a small incremental upgrade. After tinkering around with Jelly Bean myself, I would agree that it is not nearly the change we saw from Gingerbread to ICS. To me it seems more like JB was designed optimize the OS to run fast and smooth, as well as add Google now, and some other improvements. Hopefully we will start seeing the dam break open on ICS upgrades for all the Gingerbread phones soon followed closely by Jelly Bean.

Link to comment
Share on other sites

I for one am looking forward to the JB update. Having more control in the Notifications area would be nice.Plus smoothness...one less thing for iPhone users to gloat about to me (though, don't get me wrong, my phone is plenty fast).

 

As for the GB->ICS update, my thought there was that some devices might not get it due to not having enough RAM or similar. However the HTC One V has 512MB of RAM yet is running ICS from day one, so I guess that most Android devices could upgrade just fine (seeing as how the lowly Optimus One series of phones, currently stuck on Froyo, have 512MB of RAM).

Link to comment
Share on other sites

HTC and Samsung have already addressed questions about their upgrade plans for Jelly Bean on their devices.

 

PocketNow received the statement from Samsung saying:

 

 

 

Android Central was able to get a statement from HTC stating:

 

 

While this doesn't tell us anything really, there is speculation that any device that will see Ice Cream Sandwich, should also see Jelly Bean since it is a small incremental upgrade. After tinkering around with Jelly Bean myself, I would agree that it is not nearly the change we saw from Gingerbread to ICS. To me it seems more like JB was designed optimize the OS to run fast and smooth, as well as add Google now, and some other improvements. Hopefully we will start seeing the dam break open on ICS upgrades for all the Gingerbread phones soon followed closely by Jelly Bean.

 

I wouldn't hold my breath. Especially when it comes to Samsung. At best, you should probably expect an update in about 6 months. I remember the Epic launching with Eclair and being promised an update to Froyo "soon". Soon turned out be months. If Samsung has their act together and gets it before out before then, then maybe we'll have hit a turning point for Android. I doubt it though.

Link to comment
Share on other sites

However the HTC One V has 512MB of RAM yet is running ICS from day one, so I guess that most Android devices could upgrade just fine (seeing as how the lowly Optimus One series of phones, currently stuck on Froyo, have 512MB of RAM).

 

I think there is a combination of factors that makes OEMs say a device is not compatible and refuse to push out an upgrade for the OS. It costs them a fair amount to write the software and beta test it. They have to weigh the advantages and disadvantages before committing to an upgrade. It is not just a matter of plugging the new version of android into the code. It makes a lot of difference what the phone was designed to run on. A manufacturer doesn't really know for sure how the phone's hardware will mesh with the OS. If they can't work the bugs out, it would be disasterous to promise an upgrade and not deliver. One of the things that makes Android great is the wide range of hardware combinations that can be offered, but this also creates a nightmare for upgrading the OS and retaining functionality.

 

Apple can continue to upgrade their old devices because they only have 4 phone models to deal with. The updates for the 3G and 3GS are not much more than changing the number of the software version in the "about phone" menu and maintaining functionality with itunes.

 

Windows Phone has strict guidelines for the hardware used and doesn't allow OEMs to skin their operating system, making it easier for them to push out updates, much like the Nexus line for Android.

 

It all comes down to open source, really. I was reading a Kindle Fire message board the other day and someone asked if Amazon would update the KF to ICS. I busted out laughing and the wife thought I was losing my mind. The kindle fire is perfectly capable of running ICS (I am running it on my KF now) but Amazon has literally nothing to gain by spending money to upgrade the OS. You can barely even classify the KF as running Android, but in the code, it is Android.

 

I am more or less rambling at this point, but I wouldn't expect any phone over a year old to be upgraded unless it is an iconic device. The manufacturers will claim that it is a hardware limitation, when it is really only a cost/reward limitation. They don't want to have to go in and tailor the OS to fit the device. It only gets more time consuming and expensive as the device ages to rewrite Android OS to work on their older devices. Even Google refused to update the Nexus One to ICS. I heard that it was because of the RAM, but XDA has HTC Nexus One ICS ROMs. I'm sure that will be seeing JB ROMs too. Manufacturers just don't want to spend the money to update software forever and have to pull the plug sooner or later. They usually leave the device with a functional OS with the bugs worked out. (No, not the Epic with GB upgrade)

  • Like 1
Link to comment
Share on other sites

I wouldn't hold my breath. Especially when it comes to Samsung. At best, you should probably expect an update in about 6 months. I remember the Epic launching with Eclair and being promised an update to Froyo "soon". Soon turned out be months. If Samsung has their act together and gets it before out before then, then maybe we'll have hit a turning point for Android. I doubt it though.

 

That is because the manufacturers can't release a buggy update to the general public. ROMs pop up right away and are full of bugs. Just like CyanogenMOD goes through months of "nightly" status, which is essentially alpha and beta releases, then however many release candidates before it is considered a stable "public release." Samsung would definately benefit by increasing their software upgrade personnel, but I applaud them for not pushing some buggy beta release out to the general public.

Link to comment
Share on other sites

That is because the manufacturers can't release a buggy update to the general public. ROMs pop up right away and are full of bugs. Just like CyanogenMOD goes through months of "nightly" status, which is essentially alpha and beta releases, then however many release candidates before it is considered a stable "public release." Samsung would definately benefit by increasing their software upgrade personnel, but I applaud them for not pushing some buggy beta release out to the general public.

 

I've always thought that was a copout. If they wanted to keep their phones up to date they would. I just think it's the manufacturer's mentality. Why spend resources on updating existing hardware when we can get them to buy new hardware? That's why I'm really considering making the jump to a nexus device now. As long as you don't get a cdma version, you'll always be current on android.

Link to comment
Share on other sites

I've always thought that was a copout. If they wanted to keep their phones up to date they would. I just think it's the manufacturer's mentality. Why spend resources on updating existing hardware when we can get them to buy new hardware? That's why I'm really considering making the jump to a nexus device now. As long as you don't get a cdma version, you'll always be current on android.

 

GSM Nexus One is still on Gingerbread...

 

It is a copout in a sense, but the manufacturer knows the development community is large enough that if someone wants a buggy pre-release, they can load it on their phone themself. Manufacturers don't get paid one cent from the consumer for software upgrades. Any upgrades they push out are just to try to keep customer loyalty and keep their phones selling. Maybe they should start charging customers for software upgrades, but that would probably not go well.

Link to comment
Share on other sites

GSM Nexus One is still on Gingerbread...

 

It is a copout in a sense, but the manufacturer knows the development community is large enough that if someone wants a buggy pre-release, they can load it on their phone themself. Manufacturers don't get paid one cent from the consumer for software upgrades. Any upgrades they push out are just to try to keep customer loyalty and keep their phones selling. Maybe they should start charging customers for software upgrades, but that would probably not go well.

 

Only because a manufacturer would probably charge an exorbitant amount. If there was a $5 or $10 charge to upgrade from say ICS to jellybean, I think a lot of people would happily pay it.

 

As far as the nexus one goes, there's always a cutoff. Hardware gets too slow to run new software eventually.

Link to comment
Share on other sites

Only because a manufacturer would probably charge an exorbitant amount. If there was a $5 or $10 charge to upgrade from say ICS to jellybean, I think a lot of people would happily pay it.

 

As far as the nexus one goes, there's always a cutoff. Hardware gets too slow to run new software eventually.

 

It would be tough to do, I usually donate $10+ to the developer of a ROM that I use heavily, and I would pay for a MFG upgrade, but it would just be another point that people would compare Android with iOS WP etc. I can hear it now "I don't have to pay for my software upgrades, sucker!" Probably not something Google wants. They have been all about open source and the open community. Someone trying to make money off a software upgrade wouldn't fit with that philosophy...

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

i am looking forward to the jb update for the ltevo when it eventually gets here. however, at the moment i would be happy if they would just add google now to the play store for us to download and take advantage of, or update the current google search to operate as google now. that is one of the biggest features/upgrades i am looking forward too personally

Link to comment
Share on other sites

Just wondering out loud...does anyone have a guess as to when the LTEVO will get the upgrade to Jellybean.

 

I ask because I am planning on upgrading to the LTEVO either in September or December, and I was wondering if it would have Jellybean by the time I get it.

 

KCT - "No Matter Where You Go, There You Are!"

Link to comment
Share on other sites

Just wondering out loud...does anyone have a guess as to when the LTEVO will get the upgrade to Jellybean.

 

I ask because I am planning on upgrading to the LTEVO either in September or December' date=' and I was wondering if it would have Jellybean by the time I get it.

 

KCT - "No Matter Where You Go, There You Are!"[/quote']

 

Well it took HTC and the rest of the Android OEM's 8 months to upgrade to ICS. I doubt jelly bean will take that long... so December is a good possibility. I think September is a little aggressive.

 

Sent from JBToro on Forum Runner

Link to comment
Share on other sites

 

Well it took HTC and the rest of the Android OEM's 8 months to upgrade to ICS. I doubt jelly bean will take that long... so December is a good possibility. I think September is a little aggressive.

 

Sent from JBToro on Forum Runner

 

Thanks.

 

KCT - "No Matter Where You Go, There You Are!"

Link to comment
Share on other sites

 

 

Well it took HTC and the rest of the Android OEM's 8 months to upgrade to ICS. I doubt jelly bean will take that long... so December is a good possibility. I think September is a little aggressive.

 

Sent from JBToro on Forum Runner

correction, it took SPRINT an extra 3 months atleast to bloat it
Link to comment
Share on other sites

Depends on the devices I suppose. The LTEVO doesn't really have the bloat as the previous devices. If they add the bloat and it goes to all devices the same, I would think a lot of LTEVO owners are going to be, to put it politely, extremely upset. That's my opinion, and one of the delay factors I see coming. It would mean multiple versions to support multiple devices, or the exclusion of older devices. The only bloat I've seen on my LTEVO is for the hot spot and sprint zone. Sprint zone can be useful at times and I don't use the hot spot.

 

Sent from my EVO using Tapatalk 2

Edited by Acidsurfr
Link to comment
Share on other sites

  • 2 weeks later...

 

 

It would be tough to do, I usually donate $10+ to the developer of a ROM that I use heavily, and I would pay for a MFG upgrade, but it would just be another point that people would compare Android with iOS WP etc. I can hear it now "I don't have to pay for my software upgrades, sucker!" Probably not something Google wants. They have been all about open source and the open community. Someone trying to make money off a software upgrade wouldn't fit with that philosophy...

 

I think they could give you a stock version for a device and charge for it. I would pay $10-$20 to have a stock android ROM experience from HTC for my EVO LTE. I think 2 flavors would be nice and the stock ROM should not require any additional work as I imagine they have to get it to this point before adding sense features.

 

I am probably showing ignorance on this post.

  • Like 1
Link to comment
Share on other sites

  • 8 months later...

Ok...so this may be the wrong place to post this, but I don't want to start a new thread, so here goes...

 

I know the HTC One comes 'Stock' with Android 4.1, but so have heard that it might get Android 4.2.

 

What do you all think?

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

    • If they use n41 + n41 2CA, people that are somewhat distant from the cell site will have an OK download but the upload will be a disaster.  Upload capability on b-41 was always a disaster on the old Sprint Network.   Now, with n25 + n41 combination, even the more distant users have a more decent upload.  I see n41 + n41 + n25 now with my S22 and I understand that we will see 4xCA with newer phones in the future.     I also see n41 + n41 + n71 sometimes too. Also some other combinations of 25, 41, 71.  I would think that eventually we will see AWS paired with n41 too.  What I am not sure of is ----  when I see 3xCA on my S22, I can see the 3 channels involved in the download but I am never sure just what I have on the upload. I do not think I have 3xCA on the upload.
    • I don't know enough about the nuts and bolts of NR to know the answer, but is there a reason they're not doing two overlapping 100 MHz n41 carriers and using selective resource shutoff to make each one 97 MHz?  Thus making use of the full 194 MHz instead of leaving 4 MHz unused as implied by the current standard 100+90 configuration? - Trip
    • Looks like another T-Mobile 5G bump happened over the past week and a half, maybe less: n41 carriers are now 90+100 MHz, up from 80+100 (which in turn is up from 40+100 back in early March). This is on top of the new n25 carrier recently. As part of this, it looks like T-Mobile is starting to prefer n25+n41 2CA even when pushing data, rather than having higher levels of CA that would hit higher peak speeds; at least indoors I need to force n41-only if I want to see the full 190 MHz there. To be fair the speeds are plenty quick with that amount of spectrum, and I'm sure they're load balancing, and my guess is this is a little better for battery life? With this expansion, they're now at 10x10+10x10 n25, 15x15 n71, 100+90 n41, for a total of 260 MHz (including FD uplink) of deployed NR here, up from 250 MHz a week ago, 230 MHz two weeks ago, and 190 MHz six months ago. VZW is at 140 MHz minus mmW, 170 if you count n2 DSS. AT&T is at 150 MHz (80+40 n77, 15x15 n5), 210 MHz I think if you count n2 and n66 DSS (guessing they're still running those). With this level of spectrum they should be able to continue offering home internet wherever. Guessing this is the last upgrade they can make before they need to throw new equipment on sites for C-Band. At this rate I figure that'll happen next year on a few dozen high-traffic sites.
    • https://www.lightreading.com/wireless/tds-telecom-to-launch-mobile-service-via-nctc-s-mvno Surprising given merger.
    • My wife has a Pixel 8 Pro and has no complaints. I have an S22U and I get slightly better signal than her but 99.9% of the time, its not noticeable. 
  • Recently Browsing

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