bluevolume wrote:
JerryF wrote:
PS, I recently saw one bit of very bad news for all of us folks that own a Samsung Charge phone. The news is that Samsung has NOT included the Charge phone in the future update plans for the next OS version called Ice Cream Sandwich. Gingerbread 2.3.6 may be our first and final update for the life of this phone and that is to bad.
I wouldn't call it "very bad news", honestly its an "oh well" at best. The Charge, and all other devices in its class, we designed to run Android v. 2.0. The hardware is definitely going to be an issue when jumping to a new operating system, and this is to be expected. When an OS is revved a full version, it should incorporate the latest advancements in hardware, even shooting towards what is coming down the pipe. Multi-core processors, 1GB+ of RAM with faster timings, extended GPU instruction sets, etc.
What ends up happening in this situation, is that for compatibity sake there will be software-based modules that it will fall back on when the hardware isn't up to snuff. Now, not only is your device already overburdened by the demands of the new OS, it has to process a bunch of code that would normally be offloaded to a hardware component. Long story short, "Why is my device SO SLOW on this new OS?"
If Verizon gets us to a good, stable release of Gingerbread that will be the best thing until we get our next phones.
I have been researching Ice Cream Sandwich, and while I don't know if Samsung will release it for the Charge, I remember reading information from Google that said that any device that was capable of running Gingerbread would be capable of running Ice Cream Sandwich. Does that mean it will come to the Droid Charge? I don't know, that is Samsung's decision. But Google claims that it is capable. Honestly, I would love to see it on my Charge, but right now, I will be content with Gingerbread - when I finally receive my OTA (I've been checking my screen every 10 minutes like a kid at Christmas, waiting for my notification that it's my turn)
Maybe it's good news because we will not be upset and worrying about getting a new update.
We probably will just buy a new phone.
Gee, I wonder if that's what Samsung and Verizon want us to do???
JerryF
shuddle13 wrote:
bluevolume wrote:
JerryF wrote:
PS, I recently saw one bit of very bad news for all of us folks that own a Samsung Charge phone. The news is that Samsung has NOT included the Charge phone in the future update plans for the next OS version called Ice Cream Sandwich. Gingerbread 2.3.6 may be our first and final update for the life of this phone and that is to bad.
I wouldn't call it "very bad news", honestly its an "oh well" at best. The Charge, and all other devices in its class, we designed to run Android v. 2.0. The hardware is definitely going to be an issue when jumping to a new operating system, and this is to be expected. When an OS is revved a full version, it should incorporate the latest advancements in hardware, even shooting towards what is coming down the pipe. Multi-core processors, 1GB+ of RAM with faster timings, extended GPU instruction sets, etc.
What ends up happening in this situation, is that for compatibity sake there will be software-based modules that it will fall back on when the hardware isn't up to snuff. Now, not only is your device already overburdened by the demands of the new OS, it has to process a bunch of code that would normally be offloaded to a hardware component. Long story short, "Why is my device SO SLOW on this new OS?"
If Verizon gets us to a good, stable release of Gingerbread that will be the best thing until we get our next phones.
I have been researching Ice Cream Sandwich, and while I don't know if Samsung will release it for the Charge, I remember reading information from Google that said that any device that was capable of running Gingerbread would be capable of running Ice Cream Sandwich. Does that mean it will come to the Droid Charge? I don't know, that is Samsung's decision. But Google claims that it is capable. Honestly, I would love to see it on my Charge, but right now, I will be content with Gingerbread - when I finally receive my OTA (I've been checking my screen every 10 minutes like a kid at Christmas, waiting for my notification that it's my turn)
That is correct, they are "capable." But refer to my 2nd paragraph above.
Okay...im not sure what to believe but the verzion red i just called said its not available on any of android devices on verizon...soo im not sure
http://wirelessandmobilenews.com/2011/11/samsung-droid-charge-update-android-2.3-gingerbread-ota.htm... this might help a lot of users
CAn the droid charge run Icecream sanswhich? (Android 4.X).
Sure can.
Will they officially release it?
Who knows.
Google designed Icecream sanswhich to be very scalable on almost all Android phones and tablets. How much of the fancy interface can be done depends on hardware. But the core kernal can run efficient on all devices. They want at least all devices in the past 18 months to have it. Merging Phone and tablets onto one base OS kernal and using the cloud system, and tablet/phone synch.
However things can effect that. Such as number of phone owners and users. Continued consumer support. They won't put team effort into it if their is not enough support of the device.
Gingerbread general core uses more then 4.0. They actually simplified the interfaces in 4.0 with less graphical demand. Then ramped up other features. Hummingbird is no weak processor even if it is based on the Cortex A8. It has more threads then the Snapdragon counter part. However available main system memory can be an issue. Icecream sanswhich can fix that. It offsets loaded apps quickly, effiecently, and doesn't leave garbage not being used running.
Yes The Droid charge could run, and could get Android 4.0. Yet Samsung will evaluate user base, and active phone users on the Charge (verizon) and other carrier i510 counterparts. Even if Google wants most of the devices on it.
Thanks Hustonheart for the info. I also read somewhere that at one time Samsung/Verizon might skip gingerbread and go right to icecream sandwitch for the droid charge...
know ever knows about update thill they happen!!
I love my phone and i have none of the problems others are having. I hope GB is the same way when I get the OTA
Charles c.
OK UPDATE:
I, personally still have not gotten this, but i just got off the phone with a Tech and got some really interesting news.
1) the *#*#2432546#*#* is a semi-urban legend... The tech told me it spells out checkin and will give the notification but has never heardf of it actually forcing an update. (kinda like those buttons for the walk signs at crosswalks. they are there but never work.
2) The update IS getting pushed by Samsung and Google (example used, Samsung and Google are a car, and Verizon is just the road travelled)
3) The ZIP.file is NOT considered rooting the phone, However was advised that it is a buyer-beware issue. I was told that it is not rooting the phone, but that unless you know the source it could do harm, and only try it if you a knowledgable enough to undo it if need be.
4) Verizon in no way can force the update. Was told turthfully it's best to let nature take it's course. We know the update went live and that people are starting to get it, it's just a matter of patience of when it fianally hits your given device.
I have been a Verizon customer for 16 years. I have had the Charge since May. I live in the 253 area code. Still no Gingerbread.
Start a new topic or ask questions in the open forum.
