I think the only major phone in the US still on 1.5 is the CLIQ XT (the one with the keyboard) and there should be an update for that one as well soon.
I put a very large warning on top of my "What's New" pop-up that comes up with every release warning users and to e-mail if they are on 1.5 and it's not the regular CLIQ. But yesterday there was a user who came to me with a problem who was running on the CLIQ XT, but didn't even know what version of Android they are on. I believe a lot of users have absolutely no clue that there are multiple versions of Android out there. On Jan 20, 4:31 pm, Kostya Vasilyev <[email protected]> wrote: > No, I'm not disputing those numbers at all. > > What I meant is - it wasn't a weird phone made by a fringe manufacturer. > > The phone a Motorola Backflip - AFAIK, it still runs 1.5 outside the US, > and the 2.1 update in the US was not an OTA, so perhaps not everyone who > could update actually did. > > -- Kostya > > 20.01.2011 3:47, Indicator Veritatis пишет: > > > > > > > This is interesting: according to the dashboard, less than 5% of > > individual phones connecting to the Google Android Market are still > > running 1.5. Yet you call that 1.5 phone, "a certain quite popular > > phone". > > > How could this be? I am curious to hear how either 1) the dashboard > > sampling could be that far off or 2) how popular this phone really is. > > Can you post the make and model# of the phone without compromising > > confidentiality? > > > On Jan 17, 7:27 am, Kostya Vasilyev<[email protected]> wrote: > >> I recently ran into some 1.5 issues with my widgets that were caused by a > >> certain quite popular phone that still runs 1.5 ignoring @dimen values. > > >> So supporting 1.5, understood as some kind of pure Platonic form, is no > >> problem at all, but dealing with bugs in particular firmware versions is > >> not > >> fun at all. > > >> For now, both my apps continue to support 1.5, but a new project I'm > >> working > >> on will only run on 1.6+ - because that's the first version with > >> multi-resolution support, and one really needs that these days. > > >> -- Kostya > > >> 2011/1/17 TreKing<[email protected]> > > >>> On Mon, Jan 17, 2011 at 7:07 AM, > >>> String<[email protected]>wrote: > >>>> For my own apps, I don't have a problem supporting 1.5, and I figure that > >>>> an extra 5% is nothing to sneeze at. But then, I've yet to run into > >>>> anything > >>>> that was really problematic for me to support on 1.5. Some of the > >>>> resource > >>>> handling is kind of annoying, but not really a big deal. > >>>> If I had some core feature that I just couldn't make backward-compatible, > >>>> then yes, I'd drop 1.5 too. But probably not until then, or until the > >>>> install percentage drops a few more points. > >>> This. (Thanks for writing my post for me :-) ) > >>> ------------------------------------------------------------------------------------------------- > >>> TreKing<http://sites.google.com/site/rezmobileapps/treking> - Chicago > >>> transit tracking app for Android-powered devices > >>> -- > >>> You received this message because you are subscribed to the Google > >>> Groups "Android Developers" group. > >>> To post to this group, send email to [email protected] > >>> To unsubscribe from this group, send email to > >>> [email protected]<android-developers%2Bunsubs[email protected]> > >>> For more options, visit this group at > >>>http://groups.google.com/group/android-developers?hl=en > > -- > Kostya Vasilyev -- WiFi Manager + pretty widget > --http://kmansoft.wordpress.com- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
