None of those things are true in fact. The prerelease sdk they offered
didn't run on any device (yeah well..) and retail units can run "unsigned"
code (as the other poster said, its self-signed.)
You'll be at a pretty big disadvantage for using features from 1.5
('cupcake') or running on those devices, since the emulator (which is up to
date) is only sort of like the actual device. (1.0/1.1 sdk apps developed
with the emulator almost all had crashes/bugs/problems on phones. Plus some
things are missing - compass, sensors, bluetooth, etc. 1.5 is likely to be
the same way.)
On Fri, May 1, 2009 at 12:09 PM, roschler <[email protected]> wrote:
>
> Hello everyone,
>
> I found out about the developer's handset after I already bought a G1
> with a 2 year contract with T-Mobile (which I got about a week ago).
> Do I have to shell out another $399 for the developer's unlocked
> device which accepts unsigned code? Or can I get by with a locked G1
> which only accepts signed apps?
>
> I know I'll have to wait for the formal release of any SDK if I don't
> have a dev handset, and be unable to get the preview versions
> available to developers, but right now I'd like to avoid the expense
> if I could. So can I go ahead and develop full blown apps and
> possibly even distribute them through the app store with my locked G1?
>
> Thanks,
> Robert
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
