Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-20 Thread Kostya Vasilyev

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 Vasilyevkmans...@gmail.com  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 TreKingtreking...@gmail.com


On Mon, Jan 17, 2011 at 7:07 AM, Stringsterling.ud...@googlemail.comwrote:

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 :-) )
-
TreKinghttp://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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
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

--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-20 Thread Zsolt Vasvari
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 kmans...@gmail.com 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 Vasilyevkmans...@gmail.com  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 TreKingtreking...@gmail.com

  On Mon, Jan 17, 2011 at 7:07 AM, 
  Stringsterling.ud...@googlemail.comwrote:
  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 :-) )
  ---­--
  TreKinghttp://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 android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs­cr...@googlegroups.com
  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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-20 Thread gjs
Hi,

I still have an (non carrier branded) HTC Hero (gsm version) with
V1.5, it is from a different region than me, it has only been offering
an OTA update to V2.1 just in the last few weeks. Anyway some users
may never be in a position to update from V1.5 even if its available.

Regards

On Jan 21, 11:12 am, Zsolt Vasvari zvasv...@gmail.com wrote:
 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 kmans...@gmail.com 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 Vasilyevkmans...@gmail.com  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 TreKingtreking...@gmail.com

   On Mon, Jan 17, 2011 at 7:07 AM, 
   Stringsterling.ud...@googlemail.comwrote:
   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 :-) )
   ---
­--
   TreKinghttp://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 android-developers@googlegroups.com
   To unsubscribe from this group, send email to
   android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs
­cr...@googlegroups.com
   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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-20 Thread gjs
Hi,

No you are not obligated by the Distribution Agreement regarding
support or updates by my reading.

I just interpret some of it as suggesting that support of your apps is
desirable. And Dianne mentioned stuff that I was not aware. ( Nothing
could be supported for perpetuity ;-)

Version 1.5 vintage phones are likely to die off anyway as the normal
consequence of hardware failure due to age - battery won't charge any
longer etc.

Regards

On Jan 20, 10:48 am, Zsolt Vasvari zvasv...@gmail.com wrote:
 That cannot be right.  That would mean you have to forever support
 every version of Android.  And does the Distirbution Agreement talk
 about having to give the users updates and supports for perpetuity?  I
 doubt you are even required to give even a single update to your app.

 On Jan 19, 2:49 pm, gjs garyjamessi...@gmail.com wrote:







  Hi,

  I'd also suggest rereading the Android Market Distribution Agreement
  if you are withdrawing V1.5 paid apps  your support for them -
  particularly given Dianne's comments about just bumping minSDK  old
  versions still being available.

  I think you may still have to provide refunds under some
  circumstances, when you may have thought your V1.5 version was no
  longer being distributed.

  Regards.

  On Jan 18, 9:48 am, Dianne Hackborn hack...@android.com wrote:

   Huh.  Well it could well be, that was so long ago it is hard to remember. 
   :}

   On Mon, Jan 17, 2011 at 2:42 PM, String 
   sterling.ud...@googlemail.comwrote:

FWIW, I had the same experience, now that you mention it. Using @dimen
references in widget layout XML doesn't work on 1.5.

Bit of a PITA, but I just went ahead and created a few more layouts 
(rather
than resizing them based on dimens) and moved on. It didn't seem like a 
big
enough problem to seriously consider not supporting 1.5 for, and since 
it
was apparently fixed by 1.6, neither did it seem worth raising as an 
issue
anywhere.

I haven't had time to dig into the AOSP links you posted, Dianne, but I 
can
back Kostya up on this - it was broken in Cupcake.

String

--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs
 cr...@googlegroups.com
For more options, visit this group at
   http://groups.google.com/group/android-developers?hl=en

   --
   Dianne Hackborn
   Android framework engineer
   hack...@android.com

   Note: please don't send private questions to me, as I don't have time to
   provide private support, and so won't reply to such e-mails.  All such
   questions should be posted on public forums, where I and others can see 
   and
   answer them.- 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-19 Thread Zsolt Vasvari
That cannot be right.  That would mean you have to forever support
every version of Android.  And does the Distirbution Agreement talk
about having to give the users updates and supports for perpetuity?  I
doubt you are even required to give even a single update to your app.

On Jan 19, 2:49 pm, gjs garyjamessi...@gmail.com wrote:
 Hi,

 I'd also suggest rereading the Android Market Distribution Agreement
 if you are withdrawing V1.5 paid apps  your support for them -
 particularly given Dianne's comments about just bumping minSDK  old
 versions still being available.

 I think you may still have to provide refunds under some
 circumstances, when you may have thought your V1.5 version was no
 longer being distributed.

 Regards.

 On Jan 18, 9:48 am, Dianne Hackborn hack...@android.com wrote:



  Huh.  Well it could well be, that was so long ago it is hard to remember. :}

  On Mon, Jan 17, 2011 at 2:42 PM, String 
  sterling.ud...@googlemail.comwrote:

   FWIW, I had the same experience, now that you mention it. Using @dimen
   references in widget layout XML doesn't work on 1.5.

   Bit of a PITA, but I just went ahead and created a few more layouts 
   (rather
   than resizing them based on dimens) and moved on. It didn't seem like a 
   big
   enough problem to seriously consider not supporting 1.5 for, and since it
   was apparently fixed by 1.6, neither did it seem worth raising as an issue
   anywhere.

   I haven't had time to dig into the AOSP links you posted, Dianne, but I 
   can
   back Kostya up on this - it was broken in Cupcake.

   String

   --
   You received this message because you are subscribed to the Google
   Groups Android Developers group.
   To post to this group, send email to android-developers@googlegroups.com
   To unsubscribe from this group, send email to
   android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs
cr...@googlegroups.com
   For more options, visit this group at
  http://groups.google.com/group/android-developers?hl=en

  --
  Dianne Hackborn
  Android framework engineer
  hack...@android.com

  Note: please don't send private questions to me, as I don't have time to
  provide private support, and so won't reply to such e-mails.  All such
  questions should be posted on public forums, where I and others can see and
  answer them.- 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-19 Thread Indicator Veritatis
Why isn't it documented clearly somewhere? Because Google still
believes in that strange myth they got caught up in while designing
their entire development philosophy for Android (and what else?):
throw up early-alpha code and let the community document it for Google
in blogs and mailing lists and even (gasp!) Google groups.

Of course, that IS a myth. The community still does not document it
for Google. This is not just because the community balks at doing
Google's homework for them, it is because the community itself does
not get its hands on such information in a reliable and timely manner.
Too much of what gets written in blogs about open source software is
just rumor with a sprinkling of half-understood facts.

Nor does it help that by the time some generous blogger writes up a
really good series of tutorials on, say, for example, Looper/Handler,
Google announces a new API with much fanfare, describing it as if
writing code using Looper and/or Handler directly is now out of date.
Whether not it is really out of date, it is frustrating, dampening the
enthusiasm of such bloggers for continuing to do Google's homework for
them.

On Jan 17, 10:29 am, TreKing treking...@gmail.com wrote:
 On Mon, Jan 17, 2011 at 12:18 PM, Dianne Hackborn hack...@android.comwrote:

  Oh and I believe on Market that if you put up a new version of your app
  with a higher minSdkVersion, the most recent older version will still be
  visible to older devices.  That is, the .apks you upload are never deleted;
  a new version just supersedes an older one for the devices it is compatible
  with.

 Holy crap - why is awesome information like this not clearly documented
 somewhere!? (Or is it ...?)

 -
 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-19 Thread Indicator Veritatis
Nor is this the only reason we should not put TOO much faith in the
dashboard. There are other reasons that sampling might be skewed.

That said, I am no longer so interested in maintaining 1.5 users
either, since even if the dashboard figure was off by 100%, there just
aren't that many 1.5 users anymore.

But my main point is to remember that the dashboard figure IS only a
sampling, an attempt to measure by a sampling process, measure a
population that is much larger than the actual sample. It takes only a
little experience with the sampling problem in statistics to realize
how subtly misleading such a sample can be.

The vendor of Statistica, StatSoft, has done us all a great public
service by making an excellent Statitics textbook freely available on
the web at http://www.statsoft.com/textbook/. Somewhere in their I
once found a great discussion of the sampling problem.

On Jan 17, 7:37 am, Brill Pappin br...@pappin.ca wrote:
 Thats fine, but doesn't give you any stats on your own app, which is
 very important for maintaining customer loyalty.

 We intend to make the company a truste name (not just the apps) in the
 market with quality product, so we really want to know what *our*
 users are doing.

 - Brill Pappin

 On Jan 17, 10:19 am, Laks laks.pendy...@gmail.com wrote:

  Is this what you are looking for?

 http://developer.android.com/resources/dashboard/platform-versions.html



-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-19 Thread Indicator Veritatis
You say, I believe. But as TrekKing already implied with his
question, this is important enough that it should be documented
somewhere without such a cautionary qualification -- if it is in fact
true. And if it turns out not to be true, then you should post a
follow up to your own comment explaining that you found out it is not
true.

Otherwise a lot of people are going to waste a lot of time trying to
figure out whether or not it is really true -- or trying to contain
the damage when their customers get a surprising version of the
software downloaded to the phone.

On Jan 17, 10:18 am, Dianne Hackborn hack...@android.com wrote:
 Oh and I believe on Market that if you put up a new version of your app with
 a higher minSdkVersion, the most recent older version will still be visible
 to older devices.  That is, the .apks you upload are never deleted; a new
 version just supersedes an older one for the devices it is compatible with.

 On Mon, Jan 17, 2011 at 10:14 AM, Dianne Hackborn hack...@android.comwrote:



  By @dimens do you mean the dp unit in layouts?

  If there is something not working on a device, we'd like to know about it
  because it is not compatible with the CDD which is a requirement for having
  Market.

  On Mon, Jan 17, 2011 at 9:40 AM, Kostya Vasilyev kmans...@gmail.comwrote:

  I'm using @dimens quite a bit, not because I have different values for
  different screen sizes / resolutions, but because it lets me tweak my
  layouts more easily during development.

  After seeing them not work on a certain 1.5 device (even though that's
  part of API level 1), I've decided that the extra 5% is not worth the
  trouble.

  -- Kostya

  2011/1/17 String sterling.ud...@googlemail.com

  On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote:

  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.

  What are you doing with multi-resolution that's problematic? I have quite
  a bit of multi-resolution code, and so far the vast majority has degraded
  pretty gracefully on 1.5.

  String
  --
  You received this message because you are subscribed to the Google
  Groups Android Developers group.
  To post to this group, send email to android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

   --
  You received this message because you are subscribed to the Google
  Groups Android Developers group.
  To post to this group, send email to android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

  --
  Dianne Hackborn
  Android framework engineer
  hack...@android.com

  Note: please don't send private questions to me, as I don't have time to
  provide private support, and so won't reply to such e-mails.  All such
  questions should be posted on public forums, where I and others can see and
  answer them.

 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-19 Thread 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 kmans...@gmail.com 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 treking...@gmail.com

  On Mon, Jan 17, 2011 at 7:07 AM, String 
  sterling.ud...@googlemail.comwrote:

  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 android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en



-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-19 Thread String
On Wednesday, January 19, 2011 6:49:12 AM UTC, gjs wrote:

I'd also suggest rereading the Android Market Distribution Agreement 
 if you are withdrawing V1.5 paid apps  your support for them - 
 particularly given Dianne's comments about just bumping minSDK  old 
 versions still being available. 

 I think you may still have to provide refunds under some 
 circumstances, when you may have thought your V1.5 version was no 
 longer being distributed. 


IANAL, but my reading of 
http://www.android.com/us/developer-distribution-agreement.html only turns 
up required refunds in section 7, which applies to app takedowns due to such 
things as TOS violations and IP infringements. Not for just voluntarily 
choosing to stop distributing an app.

String 

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-18 Thread Oded O.
http://developer.android.com/resources/dashboard/platform-versions.html

You can target 1.6 and still enjoy the speed boost of 2.2 if that's the 
version you are running on...

Unless you are using Version-Specific API calls, I would try to target 
the lowest version possible (but not lower than 1.6 :-) )

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-18 Thread Oded O.
How does the analytics API handle offline scenarios? is it possible to store 
all the interaction of the user offline, and post it in a single bulk 
request to the analytics server?
I know they support bulk submission, but the API states that the entire bulk 
will be registered with the same time stamp (not very useful)

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: Will no longer support Android 1.5

2011-01-18 Thread gjs
Hi,

I'd also suggest rereading the Android Market Distribution Agreement
if you are withdrawing V1.5 paid apps  your support for them -
particularly given Dianne's comments about just bumping minSDK  old
versions still being available.

I think you may still have to provide refunds under some
circumstances, when you may have thought your V1.5 version was no
longer being distributed.

Regards.


On Jan 18, 9:48 am, Dianne Hackborn hack...@android.com wrote:
 Huh.  Well it could well be, that was so long ago it is hard to remember. :}

 On Mon, Jan 17, 2011 at 2:42 PM, String sterling.ud...@googlemail.comwrote:









  FWIW, I had the same experience, now that you mention it. Using @dimen
  references in widget layout XML doesn't work on 1.5.

  Bit of a PITA, but I just went ahead and created a few more layouts (rather
  than resizing them based on dimens) and moved on. It didn't seem like a big
  enough problem to seriously consider not supporting 1.5 for, and since it
  was apparently fixed by 1.6, neither did it seem worth raising as an issue
  anywhere.

  I haven't had time to dig into the AOSP links you posted, Dianne, but I can
  back Kostya up on this - it was broken in Cupcake.

  String

  --
  You received this message because you are subscribed to the Google
  Groups Android Developers group.
  To post to this group, send email to android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs 
  cr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-18 Thread gjs
Hi,

I still like targeting V1.5 because it lets you artificially limit the
screen resolution on higher res devices - for a free version of your
app.

And then charge for your V1.6+ version with the supported device
resolutions.

Regards

On Jan 19, 5:49 pm, gjs garyjamessi...@gmail.com wrote:
 Hi,

 I'd also suggest rereading the Android Market Distribution Agreement
 if you are withdrawing V1.5 paid apps  your support for them -
 particularly given Dianne's comments about just bumping minSDK  old
 versions still being available.

 I think you may still have to provide refunds under some
 circumstances, when you may have thought your V1.5 version was no
 longer being distributed.

 Regards.

 On Jan 18, 9:48 am, Dianne Hackborn hack...@android.com wrote:







  Huh.  Well it could well be, that was so long ago it is hard to remember. :}

  On Mon, Jan 17, 2011 at 2:42 PM, String 
  sterling.ud...@googlemail.comwrote:

   FWIW, I had the same experience, now that you mention it. Using @dimen
   references in widget layout XML doesn't work on 1.5.

   Bit of a PITA, but I just went ahead and created a few more layouts 
   (rather
   than resizing them based on dimens) and moved on. It didn't seem like a 
   big
   enough problem to seriously consider not supporting 1.5 for, and since it
   was apparently fixed by 1.6, neither did it seem worth raising as an issue
   anywhere.

   I haven't had time to dig into the AOSP links you posted, Dianne, but I 
   can
   back Kostya up on this - it was broken in Cupcake.

   String

   --
   You received this message because you are subscribed to the Google
   Groups Android Developers group.
   To post to this group, send email to android-developers@googlegroups.com
   To unsubscribe from this group, send email to
   android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs
cr...@googlegroups.com
   For more options, visit this group at
  http://groups.google.com/group/android-developers?hl=en

  --
  Dianne Hackborn
  Android framework engineer
  hack...@android.com

  Note: please don't send private questions to me, as I don't have time to
  provide private support, and so won't reply to such e-mails.  All such
  questions should be posted on public forums, where I and others can see and
  answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread DraganA
I'm not your app user, but I'm curious about this situation. Will 1.5
users be able to download your current app version in the future or
will it just dissappear? I always wondered about what happens when one
decides to stop supporting old Android versions. It would be good if a
version for 1.5 stayed on for 1.5 users.

On Jan 17, 9:47 am, Kostya Vasilyev kmans...@gmail.com wrote:
 I'd say - good riddance!

 2011/1/17 Zsolt Vasvari zvasv...@gmail.com

  I just warned my users that support for Android 1.5 will go away after
  April 1st.  The share of 1.5 is  5% now and dropping.

  Between not supporting multiple resolutions, wonky RelativeLayout and
  old style Contacts provider, it's time to say goodbye to 1.5.

  Would love to hear people's opinion on this decision?

  --
  You received this message because you are subscribed to the Google
  Groups Android Developers group.
  To post to this group, send email to android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Zsolt Vasvari
That's a good point.  Current 1.5 users would still need to be
redownload the app for whatever reason.  I might release a version for
Android 1.5 users only and never update it.

On Jan 17, 6:00 pm, DraganA dand...@gmail.com wrote:
 I'm not your app user, but I'm curious about this situation. Will 1.5
 users be able to download your current app version in the future or
 will it just dissappear? I always wondered about what happens when one
 decides to stop supporting old Android versions. It would be good if a
 version for 1.5 stayed on for 1.5 users.

 On Jan 17, 9:47 am, Kostya Vasilyev kmans...@gmail.com wrote:



  I'd say - good riddance!

  2011/1/17 Zsolt Vasvari zvasv...@gmail.com

   I just warned my users that support for Android 1.5 will go away after
   April 1st.  The share of 1.5 is  5% now and dropping.

   Between not supporting multiple resolutions, wonky RelativeLayout and
   old style Contacts provider, it's time to say goodbye to 1.5.

   Would love to hear people's opinion on this decision?

   --
   You received this message because you are subscribed to the Google
   Groups Android Developers group.
   To post to this group, send email to android-developers@googlegroups.com
   To unsubscribe from this group, send email to
   android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs­cr...@googlegroups.com
   For more options, visit this group at
  http://groups.google.com/group/android-developers?hl=en- 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread String
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.

String

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread TreKing
On Mon, Jan 17, 2011 at 7:07 AM, String sterling.ud...@googlemail.comwrote:

 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Stephen Jungels
I've been tempted to drop 1.5, partly because it tends to be installed
on low-end devices where people will not have a very good experience
of my app, but recently my percentage of 1.5 users has gone up instead
of down on some apps.

There's a big difference between dropping (loyal) 1.5 users and never
having them in the first place, so for new apps my default assumption
is I will target 1.6+ or even 2.1+.

SJ

On Mon, Jan 17, 2011 at 8:52 AM, TreKing treking...@gmail.com wrote:
 On Mon, Jan 17, 2011 at 7:07 AM, String sterling.ud...@googlemail.com
 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 - 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 android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Kevin Duffey
Is there a site that shows the number of users for each version?

I'd rather target 2.2+ now.. just because its the version that brought in a
big speed boost, making a lot more apps much smoother. I still have the
Droid 1 and I thought that was one of the lower end devices out there? Being
that I'll be able to upgrade this year, I would suspect by end of this year
most of the owners would be on 2.2 or later.

On Mon, Jan 17, 2011 at 6:50 AM, Stephen Jungels sjung...@gmail.com wrote:

 I've been tempted to drop 1.5, partly because it tends to be installed
 on low-end devices where people will not have a very good experience
 of my app, but recently my percentage of 1.5 users has gone up instead
 of down on some apps.

 There's a big difference between dropping (loyal) 1.5 users and never
 having them in the first place, so for new apps my default assumption
 is I will target 1.6+ or even 2.1+.

 SJ

 On Mon, Jan 17, 2011 at 8:52 AM, TreKing treking...@gmail.com wrote:
  On Mon, Jan 17, 2011 at 7:07 AM, String sterling.ud...@googlemail.com
  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 - 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 android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
  For more options, visit this group at
  http://groups.google.com/group/android-developers?hl=en

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Laks
Is this what you are looking for?

http://developer.android.com/resources/dashboard/platform-versions.html

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Kostya Vasilyev
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 treking...@gmail.com

 On Mon, Jan 17, 2011 at 7:07 AM, String sterling.ud...@googlemail.comwrote:

 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 android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Kostya Vasilyev
Not absolute numbers, but rather percentages, can be seen here:

http://developer.android.com/resources/dashboard/platform-versions.html

-- Kostya

2011/1/17 Kevin Duffey andjar...@gmail.com

 Is there a site that shows the number of users for each version?

 I'd rather target 2.2+ now.. just because its the version that brought in a
 big speed boost, making a lot more apps much smoother. I still have the
 Droid 1 and I thought that was one of the lower end devices out there? Being
 that I'll be able to upgrade this year, I would suspect by end of this year
 most of the owners would be on 2.2 or later.


 On Mon, Jan 17, 2011 at 6:50 AM, Stephen Jungels sjung...@gmail.comwrote:

 I've been tempted to drop 1.5, partly because it tends to be installed
 on low-end devices where people will not have a very good experience
 of my app, but recently my percentage of 1.5 users has gone up instead
 of down on some apps.

 There's a big difference between dropping (loyal) 1.5 users and never
 having them in the first place, so for new apps my default assumption
 is I will target 1.6+ or even 2.1+.

 SJ

 On Mon, Jan 17, 2011 at 8:52 AM, TreKing treking...@gmail.com wrote:
  On Mon, Jan 17, 2011 at 7:07 AM, String sterling.ud...@googlemail.com
  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 - 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
 android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
  For more options, visit this group at
  http://groups.google.com/group/android-developers?hl=en

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Kevin Duffey
Indeed. Good info to have. So looks like 2.1+ is the target.

On Mon, Jan 17, 2011 at 7:19 AM, Laks laks.pendy...@gmail.com wrote:

 Is this what you are looking for?

 http://developer.android.com/resources/dashboard/platform-versions.html

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Brill Pappin
I started development during 2.1 so i never went there.
I'm moving all new code up to minimum 2.2 because thats were 60% of my
customer base is.
That said, I'll support the one app I have thats 2.1 for as long as I
have greater than 10% users.

On that note. It's bogus that the Market doesn't give me any stats on
who my users are. I had to go to ApBrain for that.
How are you tracking what percentage of your users are on what
platform?
There is a GOogle Analytics library for Aneroid, but I haven't tried
implementing it yet.

- Brill Pappin

On Jan 17, 3:32 am, Zsolt Vasvari zvasv...@gmail.com wrote:
 I just warned my users that support for Android 1.5 will go away after
 April 1st.  The share of 1.5 is  5% now and dropping.

 Between not supporting multiple resolutions, wonky RelativeLayout and
 old style Contacts provider, it's time to say goodbye to 1.5.

 Would love to hear people's opinion on this decision?

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Brill Pappin
Its shameful, but the Market doesn't give us any useful data on that
(which makes giving quality product a problem).
I got my data through AppBrain, but its certainly not ideal.

There is a lib for Google Analytic, but I looks a bit chunky, so I
haven't tried to use it yet.

- Brill Pappin

On Jan 17, 10:14 am, Kevin Duffey andjar...@gmail.com wrote:
 Is there a site that shows the number of users for each version?

 I'd rather target 2.2+ now.. just because its the version that brought in a
 big speed boost, making a lot more apps much smoother. I still have the
 Droid 1 and I thought that was one of the lower end devices out there? Being
 that I'll be able to upgrade this year, I would suspect by end of this year
 most of the owners would be on 2.2 or later.







 On Mon, Jan 17, 2011 at 6:50 AM, Stephen Jungels sjung...@gmail.com wrote:
  I've been tempted to drop 1.5, partly because it tends to be installed
  on low-end devices where people will not have a very good experience
  of my app, but recently my percentage of 1.5 users has gone up instead
  of down on some apps.

  There's a big difference between dropping (loyal) 1.5 users and never
  having them in the first place, so for new apps my default assumption
  is I will target 1.6+ or even 2.1+.

  SJ

  On Mon, Jan 17, 2011 at 8:52 AM, TreKing treking...@gmail.com wrote:
   On Mon, Jan 17, 2011 at 7:07 AM, String sterling.ud...@googlemail.com
   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 - 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 android-developers@googlegroups.com
   To unsubscribe from this group, send email to
   android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs
cr...@googlegroups.com
   For more options, visit this group at
  http://groups.google.com/group/android-developers?hl=en

  --
  You received this message because you are subscribed to the Google
  Groups Android Developers group.
  To post to this group, send email to android-developers@googlegroups.com
  To unsubscribe from this group, send email to
  android-developers+unsubscr...@googlegroups.comandroid-developers%2Bunsubs 
  cr...@googlegroups.com
  For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Brill Pappin
Thats fine, but doesn't give you any stats on your own app, which is
very important for maintaining customer loyalty.

We intend to make the company a truste name (not just the apps) in the
market with quality product, so we really want to know what *our*
users are doing.

- Brill Pappin

On Jan 17, 10:19 am, Laks laks.pendy...@gmail.com wrote:
 Is this what you are looking for?

 http://developer.android.com/resources/dashboard/platform-versions.html

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Stephen Jungels
My stats are from Google Analytics. If you use it and explain what you
are doing in your terms of service or license agreement, you are
likely to get at least a few comments from users who think you are
spying on them, but in some cases it is worth it because you have a
better picture of how your app is being used.

SJ

On Mon, Jan 17, 2011 at 10:37 AM, Brill Pappin br...@pappin.ca wrote:
 Thats fine, but doesn't give you any stats on your own app, which is
 very important for maintaining customer loyalty.

 We intend to make the company a truste name (not just the apps) in the
 market with quality product, so we really want to know what *our*
 users are doing.

 - Brill Pappin

 On Jan 17, 10:19 am, Laks laks.pendy...@gmail.com wrote:
 Is this what you are looking for?

 http://developer.android.com/resources/dashboard/platform-versions.html

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread String
On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote:

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.


What are you doing with multi-resolution that's problematic? I have quite a 
bit of multi-resolution code, and so far the vast majority has degraded 
pretty gracefully on 1.5.

String

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Kostya Vasilyev
I'm using @dimens quite a bit, not because I have different values for
different screen sizes / resolutions, but because it lets me tweak my
layouts more easily during development.

After seeing them not work on a certain 1.5 device (even though that's part
of API level 1), I've decided that the extra 5% is not worth the trouble.

-- Kostya

2011/1/17 String sterling.ud...@googlemail.com

 On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote:

 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.


 What are you doing with multi-resolution that's problematic? I have quite a
 bit of multi-resolution code, and so far the vast majority has degraded
 pretty gracefully on 1.5.

 String
 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Dianne Hackborn
By @dimens do you mean the dp unit in layouts?

If there is something not working on a device, we'd like to know about it
because it is not compatible with the CDD which is a requirement for having
Market.

On Mon, Jan 17, 2011 at 9:40 AM, Kostya Vasilyev kmans...@gmail.com wrote:

 I'm using @dimens quite a bit, not because I have different values for
 different screen sizes / resolutions, but because it lets me tweak my
 layouts more easily during development.

 After seeing them not work on a certain 1.5 device (even though that's part
 of API level 1), I've decided that the extra 5% is not worth the trouble.

 -- Kostya

 2011/1/17 String sterling.ud...@googlemail.com

 On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote:

 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.


 What are you doing with multi-resolution that's problematic? I have quite
 a bit of multi-resolution code, and so far the vast majority has degraded
 pretty gracefully on 1.5.

 String
 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Dianne Hackborn
Oh and I believe on Market that if you put up a new version of your app with
a higher minSdkVersion, the most recent older version will still be visible
to older devices.  That is, the .apks you upload are never deleted; a new
version just supersedes an older one for the devices it is compatible with.

On Mon, Jan 17, 2011 at 10:14 AM, Dianne Hackborn hack...@android.comwrote:

 By @dimens do you mean the dp unit in layouts?

 If there is something not working on a device, we'd like to know about it
 because it is not compatible with the CDD which is a requirement for having
 Market.


 On Mon, Jan 17, 2011 at 9:40 AM, Kostya Vasilyev kmans...@gmail.comwrote:

 I'm using @dimens quite a bit, not because I have different values for
 different screen sizes / resolutions, but because it lets me tweak my
 layouts more easily during development.

 After seeing them not work on a certain 1.5 device (even though that's
 part of API level 1), I've decided that the extra 5% is not worth the
 trouble.

 -- Kostya

 2011/1/17 String sterling.ud...@googlemail.com

 On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote:

 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.


 What are you doing with multi-resolution that's problematic? I have quite
 a bit of multi-resolution code, and so far the vast majority has degraded
 pretty gracefully on 1.5.

 String
 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Kostya Vasilyev
No, I mean defining a value like this:

dimen name=some_value140dp/dimen

and then using it like this:

RealtiveLayout . android:layout_width=@dimen/some_value

I used this for widget sizing, and had a default fallback dimens.xml in
res/values (without alternate qualifiers).

Based on my user's feedback, this produced zero-sized (invisible) widget
layouts.

Was this supposed to work for 1.5?

-- Kostya

2011/1/17 Dianne Hackborn hack...@android.com

 By @dimens do you mean the dp unit in layouts?

 If there is something not working on a device, we'd like to know about it
 because it is not compatible with the CDD which is a requirement for having
 Market.


 On Mon, Jan 17, 2011 at 9:40 AM, Kostya Vasilyev kmans...@gmail.comwrote:

 I'm using @dimens quite a bit, not because I have different values for
 different screen sizes / resolutions, but because it lets me tweak my
 layouts more easily during development.

 After seeing them not work on a certain 1.5 device (even though that's
 part of API level 1), I've decided that the extra 5% is not worth the
 trouble.

 -- Kostya

 2011/1/17 String sterling.ud...@googlemail.com

 On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote:

 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.


 What are you doing with multi-resolution that's problematic? I have quite
 a bit of multi-resolution code, and so far the vast majority has degraded
 pretty gracefully on 1.5.

 String
 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread TreKing
On Mon, Jan 17, 2011 at 12:18 PM, Dianne Hackborn hack...@android.comwrote:

 Oh and I believe on Market that if you put up a new version of your app
 with a higher minSdkVersion, the most recent older version will still be
 visible to older devices.  That is, the .apks you upload are never deleted;
 a new version just supersedes an older one for the devices it is compatible
 with.


Holy crap - why is awesome information like this not clearly documented
somewhere!? (Or is it ...?)

-
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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Ken H
 Holy crap - why is awesome information like this not clearly documented
 somewhere!? (Or is it ...?)


You crystalized my thoughts...although I usually find I just didn't
read the documnetation deeply :)

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Dianne Hackborn
That's strange, I don't see why that wouldn't work.  This is the code in
1.5:

http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/java/android/view/ViewGroup.java;h=e686d1c20bd21eaa050ff3bf9187b549ee7b1355;hb=refs/heads/cupcake-release#l3319

Which boils down to:

http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/java/android/content/res/TypedArray.java;h=3a32c0312202532c32bb79c0801121c4fc09b70c;hb=refs/heads/cupcake-release#l426

That seems basically like the code we have today, so should work the same
way.

The only way I can imagine someone breaking this is if they change the
implementation of those two functions...  and if someone does that, I hate
them. :|

For what it's worth, the whole @dimen thing is very intrinsic to the
resource system; it is not really a special @dimen, but the @ syntax
that generally says to get the value from the resource indicated.  The only
thing that knows anything about dimen at all just aapt to help you build
resources in a standard way.

So the simple act of retrieving a TypedArray will already take care of
resolving resource references to their final value, and does this
independently of what specific types there are.  You can't break things at
this level without breaking all kinds of stuff.

Which is all to say, I have no idea why that would break. :/

On Mon, Jan 17, 2011 at 10:26 AM, Kostya Vasilyev kmans...@gmail.comwrote:

 No, I mean defining a value like this:

 dimen name=some_value140dp/dimen

 and then using it like this:

 RealtiveLayout . android:layout_width=@dimen/some_value

 I used this for widget sizing, and had a default fallback dimens.xml in
 res/values (without alternate qualifiers).

 Based on my user's feedback, this produced zero-sized (invisible) widget
 layouts.

 Was this supposed to work for 1.5?

 -- Kostya

 2011/1/17 Dianne Hackborn hack...@android.com

 By @dimens do you mean the dp unit in layouts?

 If there is something not working on a device, we'd like to know about it
 because it is not compatible with the CDD which is a requirement for having
 Market.


 On Mon, Jan 17, 2011 at 9:40 AM, Kostya Vasilyev kmans...@gmail.comwrote:

 I'm using @dimens quite a bit, not because I have different values for
 different screen sizes / resolutions, but because it lets me tweak my
 layouts more easily during development.

 After seeing them not work on a certain 1.5 device (even though that's
 part of API level 1), I've decided that the extra 5% is not worth the
 trouble.

 -- Kostya

 2011/1/17 String sterling.ud...@googlemail.com

 On Monday, January 17, 2011 3:27:02 PM UTC, Kostya Vasilyev wrote:

 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.


 What are you doing with multi-resolution that's problematic? I have
 quite a bit of multi-resolution code, and so far the vast majority has
 degraded pretty gracefully on 1.5.

 String
 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to
 android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




 --
 Dianne Hackborn
 Android framework engineer
 hack...@android.com

 Note: please don't send private questions to me, as I don't have time to
 provide private support, and so won't reply to such e-mails.  All such
 questions should be posted on public forums, where I and others can see and
 answer them.

  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en


  --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this 

[android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Doug
On Jan 17, 11:33 am, Ken H hunt1...@gmail.com wrote:
  Holy crap - why is awesome information like this not clearly documented
  somewhere!? (Or is it ...?)

 You crystalized my thoughts...although I usually find I just didn't
 read the documnetation deeply :)

This was news to me too, and I swear I've read everything at least
once.  Not that the Android Market itself has documentation for
developers to read.

Doug

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread String
FWIW, I had the same experience, now that you mention it. Using @dimen 
references in widget layout XML doesn't work on 1.5.

Bit of a PITA, but I just went ahead and created a few more layouts (rather 
than resizing them based on dimens) and moved on. It didn't seem like a big 
enough problem to seriously consider not supporting 1.5 for, and since it 
was apparently fixed by 1.6, neither did it seem worth raising as an issue 
anywhere.

I haven't had time to dig into the AOSP links you posted, Dianne, but I can 
back Kostya up on this - it was broken in Cupcake.

String

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Will no longer support Android 1.5

2011-01-17 Thread Dianne Hackborn
Huh.  Well it could well be, that was so long ago it is hard to remember. :}

On Mon, Jan 17, 2011 at 2:42 PM, String sterling.ud...@googlemail.comwrote:

 FWIW, I had the same experience, now that you mention it. Using @dimen
 references in widget layout XML doesn't work on 1.5.

 Bit of a PITA, but I just went ahead and created a few more layouts (rather
 than resizing them based on dimens) and moved on. It didn't seem like a big
 enough problem to seriously consider not supporting 1.5 for, and since it
 was apparently fixed by 1.6, neither did it seem worth raising as an issue
 anywhere.

 I haven't had time to dig into the AOSP links you posted, Dianne, but I can
 back Kostya up on this - it was broken in Cupcake.

 String

 --
 You received this message because you are subscribed to the Google
 Groups Android Developers group.
 To post to this group, send email to android-developers@googlegroups.com
 To unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.comandroid-developers%2bunsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en




-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en