Ice Cream Sandwich is the code name for Android 4.0. Jelly Bean is Android 4.1 and Gingerbread is Android 2.3. You can read more about the Android versions at http://en.wikipedia.org/wiki/Android_version_history
On 23/08/12 12:10, jeremy wrote: > Lol, ice cream sandwich, ics, is one of the later versions of the > android operating system. I believe the numbering for it goes up to > 4.04, but I may be a bit off on that one. > Take care. > > > On 8/23/2012 10:47 AM, reggie.alvar...@gmail.com wrote: >> Curious! What is ice cream sandwich? If I am correct, I have it and >> perhaps happy about >> >> Reggieit? Smiles. and Brooks >> >> >> On Aug 22, 2012, at 5:26 PM, Keith Watson <lnx...@gmail.com> wrote: >> >> This has probably been answered, but I thought I would throw my 2 >> cents in here anyway. >> >> There is such ambiguity between phone manufactures, carriers and >> google that programmers are forced to alter their code for each >> version of the operating system they plan on supporting. Not only each >> version of the OS but each tree within that version. For instance, >> look at Ice cream sandwich. HTC, Motorola, Samsung and god knows who >> else all alter the base code for their particular hardware. This means >> that no version of Ice cream sandwich is the same as what Google >> released. App developers don't like to work within these types of >> boundaries. It's much easier to write apps for IOS as no matter what >> version of the phone you own the base operating system is the same. >> >> Just saying'. >> >> >> On Aug 22, 2012, at 2:53 PM, Christopher Chaltain <chalt...@gmail.com> >> wrote: >> >>> I'm curious. What do you mean by "seamless integration of software to >>> hardware that Apple is able to supply." What is Android not providing >>> with respect to seamless integration that Apple is providing? I'm not >>> arguing with the statement; I'm just not sure what's meant by it. >>> >>> On 22/08/12 13:38, Chuck Dean wrote: >>>> I prefer the seamless integration of software to hardware that Apple is >>>> able to supply. >>>> >>>> I am not impressed with any of the current models of smartphones on any >>>> other platform. >>>> >>>> I would not switch for such a minor convenience. >>>> Chuck >>>> >>>> On Wednesday, August 22, 2012 10:31:46 AM UTC-7, Syntellia Inc wrote: >>>> >>>> Hi from the Fleksy team. We are writing to ask a question to those >>>> in the list. >>>> >>>> As you know, we are committed to develop Fleksy and make it >>>> available for more and more users. >>>> >>>> One of the restrictions we've had so far, is that on iOS, Fleksy >>>> cannot replace your system keyboard across the device. We provide as >>>> much integration as possible, letting you email, SMS, tweet, and >>>> (soon) post to Facebook from within Fleksy. And you can copy and >>>> paste to any other app. >>>> >>>> We are trying to go beyond this: we could provide Fleksy as a >>>> keyboard across the device, so you can use it in every single app >>>> without the need to have a separate app, or to copy and paste. We've >>>> also noticed that Android is becoming more and more accessible for >>>> visually impaired users with each update. >>>> >>>> So, here's a question for the list: >>>> >>>> If there was a phone that was accessible, and that had Fleksy built >>>> in from the start. By built in, we mean that Fleksy could be used as >>>> a system keyboard on every app, and that Fleksy would come with the >>>> phone, i.e. without having to purchase the app separately. >>>> >>>> How likely would this be to make you consider buying such a device? >>>> >>>> Obviously we are talking about a hypothetical scenario, so for now >>>> let's assume all other features will be the same as your current >>>> device. >>>> >>>> Would the availability of Fleksy as a system typing mode to use in >>>> every app make you consider an accessible Android phone in your next >>>> upgrade? >>>> >>>> Looking forward to your thoughts on this. >>>> >>>> Ioannis >>>> Fleksy team >>>> >>>> -- >>>> You received this message because you are subscribed to the "VIPhone" >>>> Google Group. >>>> To search the VIPhone public archive, visit >>>> http://www.mail-archive.com/viphone@googlegroups.com/. >>>> To post to this group, send email to viphone@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> viphone+unsubscr...@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/viphone?hl=en. >>>> >>>> >>> -- >>> Christopher (CJ) >>> chaltain at Gmail >>> >>> >>> -- >>> You received this message because you are subscribed to the "VIPhone" >>> Google Group. >>> To search the VIPhone public archive, visit >>> http://www.mail-archive.com/viphone@googlegroups.com/. >>> To post to this group, send email to viphone@googlegroups.com. >>> To unsubscribe from this group, send email to >>> viphone+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/viphone?hl=en. >>> >>> > -- Christopher (CJ) chaltain at Gmail -- You received this message because you are subscribed to the "VIPhone" Google Group. To search the VIPhone public archive, visit http://www.mail-archive.com/viphone@googlegroups.com/. To post to this group, send email to viphone@googlegroups.com. To unsubscribe from this group, send email to viphone+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/viphone?hl=en.
