> But things have been getting better and JBQ is very active within this
> group and always has been as helpful as permitted.

> I am sure JBQ has seen this thread, and I would expect that as soon as
> there is news - we will all know.

> On Tue, Nov 3, 2009 at 10:13, Bronson <bronson.si...@gmail.com> wrote:
>> I purchased an ADP1 phone about a week or two ago.  I am surprised
>> there is no information regarding 2.0 on the *only* dev device.

>> I am not worried about buying a new device, just left confused about
>> communication.  My only guess is the Droid launch.  Lack of
>> information tends to fuel rumors.

>> -Bronson

>> On Nov 2, 2:32 pm, Troy - Purple Oranges <t...@purpleoranges.com>
>> wrote:
>>> I am not advocating development only within the SDK, I would suggest
>>> however for the most part of an applications life - that is where most
>>> development will take place.

>>> Yes, it will be frustrating if the ADP1 can not be upgraded to Android
>>> 2.0 - I would love access to the features that it offers.

>>> What I am trying to remind people of - is that the ADP1 was never sold
>>> as a device that can be upgraded to 2.0. There have been several posts
>>> almost asserting that HTC / Google have been deceptive in their
>>> practices by selling the ADP1, and as far as I can see this is simply
>>> not the case.

>>> You wouldn't buy a phone from Nokia today, then expect them to replace
>>> it in a week if they released a new model. I worked for Nokia in Japan
>>> for quite a while, and I know that they are models ahead in their
>>> development - but I couldn't accuse them of being deceptive having a
>>> phone on the market knowing that it can't be upgraded to their latest
>>> software platform.

>>> Troy

>>> On Tue, Nov 3, 2009 at 08:01, Dario Laverde <dario.nycj...@gmail.com> wrote:
>>> > @Troy:

>>> > "testing shouldn't be done on the hardware device. We use the ADP1's mainly
>>> > to demo..."

>>> > Well maybe you don't use the sensors, OpenGL, etc... or run into any
>>> > emulator only issues - or more importantly issues that only manifest
>>> > themselves on a device.

>>> > It's very important to test on a device before submitting to the market.
>>> > Unbelievably there are some who submit to the market by testing only on the
>>> > emulator which only adds to the "force close" issue (yes, that's a whole
>>> > other story..).

>>> > Unlike commercially available devices, a dev device that comes with a
>>> > dev-friendly version of the firmware (or at least the ability to install
>>> > your own builds) makes it easier to debug the OS as well.

>>> > Maybe Google is planning to heavily subsidize the next developer phone for
>>> > those who bought ADP1 in the last 6 months by giving them a significant
>>> > discount on the next one.  How about a Droid for ADP2?  ;-)

>>> > -Dario

>>> > On Fri, Oct 30, 2009 at 6:37 PM, Troy - Purple Oranges
>>> > <t...@purpleoranges.com> wrote:

>>> >> Michael,

>>> >> Most of your dev should be done within the emulator in the SDK.  With
>>> >> the new screen sizes, resolutions etc - testing shouldn't be done on
>>> >> the hardware device.

>>> >> We use the ADP1's mainly to demo to clients etc.

>>> >> If you need some help setting up emulators in the SDK let us know,
>>> >> there are a few helpful places online with good info.

>>> >> Cheers, Troy

>>> >> On Sat, Oct 31, 2009 at 03:58, Michael Marino
>>> >> <michael.marino...@gmail.com> wrote:
>>> >> > Understandable, I just wanted a little clearer of a picture before I
>>> >> > went out and bought the ADP1. I want to do my part as a developer to
>>> >> > make sure that there was not some obvious known "end of life" date
>>> >> > that I was unaware of. I just want to make sure that my $400
>>> >> > investment is not to be outdated in a mere 3 months. If so, my taste
>>> >> > for the platform in general would be very damaged to the point I
>>> >> > wouldn't develop anymore(unless they sold the new phones for a 80% -
>>> >> > 90% discount for previous owners :P ). Thanks though.

>>> >> > Michael

>>> > --

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

>>> Purple Oranges Pty Ltd (ACN 107 409 263)
>>> SYD +61-2-8231-5785 BNE +61-7-3018-2829 MEL +61-3-8682-0401
>>> New York +1-212-359-1678http://purpleoranges.com/

>>> Disclaimer - This email and any files transmitted with it should be considered without prejudice and are confidential
>>> and contain privileged or copyright information. You must not present
>>> this message to another party without gaining permission from the
>>> sender. If you are not the intended recipient you must not copy,
>>> distribute or use this email or the information contained in it for any
>>> purpose other than to notify us.

>>> Any views expressed in this message are those of the individual sender,
>>> except where the sender specifically states them to be the views of
>>> Purple Oranges Pty Ltd.

>> --

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

> Purple Oranges Pty Ltd (ACN 107 409 263)
> SYD +61-2-8231-5785 BNE +61-7-3018-2829 MEL +61-3-8682-0401
> New York +1-212-359-1678
> http://purpleoranges.com/

> Disclaimer - This email and any files transmitted with it should be considered without prejudice and are confidential
> and contain privileged or copyright information. You must not present
> this message to another party without gaining permission from the
> sender. If you are not the intended recipient you must not copy,
> distribute or use this email or the information contained in it for any
> purpose other than to notify us.

> Any views expressed in this message are those of the individual sender,
> except where the sender specifically states them to be the views of
> Purple Oranges Pty Ltd.

> --

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