Requires development platform Eclair but this is a release platform.

[Billy Cui]

When I build the Phone app and put in 2.0 emulator, it said so and
keep fc.

"Requires development platform Eclair but this is a release platform."

Any one know what's happening?

Is it the aosp's eclair just development build?

[Jean-Baptiste Queru]

Indeed, the code drop that I made in eclair yesterday is in a
development state and is marked as such. While that's the case,
applications built in that tree get marked such that they can't be
accidentally used in a release build.

JBQ

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



--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Billy Cui]

Thank guy for your prompt reply, any tweak way I can do for fix it to
test the code in emulator? Give me some advise if it's not a extreme
secret of Google :P

On Nov 14, 8:57 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> Indeed, the code drop that I made in eclair yesterday is in a
> development state and is marked as such. While that's the case,
> applications built in that tree get marked such that they can't be
> accidentally used in a release build.
>
> JBQ
>
>
>
>
>
> On Sat, Nov 14, 2009 at 1:16 AM, Billy Cui <billy...@gmail.com> wrote:
> > When I build the Phone app and put in 2.0 emulator, it said so and
> > keep fc.
>
> > "Requires development platform Eclair but this is a release platform."
>
> > Any one know what's happening?
>
> > Is it the aosp's eclair just development build?
>
> > --
>
> > You received this message because you are subscribed to the Google Groups "android-platform" group.
> > To post to this group, send email to android-...@googlegroups.com.
> > To unsubscribe from this group, send email to android-platfo...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/android-platform?hl=.

[Jean-Baptiste Queru]

Well, it should run just fine in the emulator that's part of the
platform build, and that's by far the preferred way to run the
platform code. Trying to mix-and-match platform work and SDK work is
painful, actually, and that's why we've put a version check in place.

If you really want to give it a try, you can try to tweak
build/core/version_defaults.mk but let me be very clear that this is
not advisable: the current state of the droid tree is neither
guaranteed to be fully-compatible with the current SDK nor to be
forward-compatible with future versions. It's just a development tree.

This is one of those situations where "if you need to ask, you shouldn't do it".

JBQ

> For more options, visit this group at http://groups.google.com/group/android-platform?hl=.

[Billy Cui]

Great, it works.

It's really a pity that the source were still part of the final code,
even part of earlier code, I got a lot of error when putting them in
emulator, so I should wait for further code.

Thank you again for your help.

[Joshua Lund]

JBQ has said that this source actually contains new code that
postdates the release of Droid. We're not looking at something is
outdated by any means.

If you are attempting to develop an App why don't you just use the SDK
as JBQ suggested?

Josh

[Billy Cui]

I think u misunderstand JBQ's meant, the current eclair code is just
earlier development code, without the latest code, so there should be
not compatible to SDK2.0, because maybe some code was not exists in
release system like Droid.

What I am doing is tweak the system app themselves, so must need the
latest codes.

[Jean-Baptiste Queru]

Actually, the currently open-sourced Eclair code is newer development
code than Droid (and SDK 2.0 which was around the same time).

In gory detail, Droid was built from the Oct 15 state of Google's
source tree, and what was open-sourced yesterday was the Nov 11 state
of that tree. It is newer enough that it's not quite entirely
compatible with the Droid code.

JBQ

> For more options, visit this group at http://groups.google.com/group/android-platform?hl=.

[Billy Cui]

So I am wrong.

Then why I can not run some compiled app in emulator was because
emulator was old and without some current API.

So the question will be: when we can get the newest emulator, i.e.
sdk2.0r2???

Also, if we compile some app based on aosp, and maybe will fail to run
in current 2.0 released system because they lack of some new API?

[Jean-Baptiste Queru]

That is correct: if you build an app from the eclair source tree, it
could be using some new functionality or depend on some behaviors that
does not exist in Droid and therefore could be incompatlble.

I can't comment about plans for future releases of the SDK (or any
other future formal release for that matter).

JBQ

> For more options, visit this group at http://groups.google.com/group/android-platform?hl=.

[Billy Cui]

Yes, that's what I do, and now I got Phone app compiled and running
very good in emulator.

Thank you for your detailed explain. Keep going!

[Dianne Hackborn]

On Sat, Nov 14, 2009 at 9:35 PM, Billy Cui <bill...@gmail.com> wrote:

So the question will be: when we can get the newest emulator, i.e.
sdk2.0r2???

What is currently available is a development tree, so you need to build the emulator from that tree to run code you compile with it.

 

Also, if we compile some app based on aosp, and maybe will fail to run
in current 2.0 released system because they lack of some new API?

Don't build apps with the current development tree (or ANY development tree).  That is what the official SDKs are for.

To reiterate: the current Eclair branch is a snapshot of development after 2.0, before the next release.  Because of this, the build is marked as a "development" build, which indicates it is something between the current SDK version (5) and the next one (6).

Apps you build with the platform build system can be compatible with 5 or older SDKs, but you'll need to explicitly mark your manifest as targeting the appropriate SDK version, because otherwise the build system will mark it as targeting the development build, so it will not be possible to install it on a release build (since it could be using new APIs that may change or disappear by the final release version).  Even so, you really don't want to do this; if you want to build against an SDK, you should do that in the standard SDK, not out of the platform build tree.  At the very least, you are going to have to test whatever app you build against the standard SDK, because otherwise you have no idea if you are doing something that is in the current development tree that is not compatible with the SDK.

--
Dianne Hackborn
Android framework engineer
hac...@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.

[dinesh...@wipro.com]

Hi,

Hope some one already know the proxy setting to browse for android
envirnment.
Tried the below steps but it is not working for me.

Steps:
In the shell I have given
Sqlite3
data/data/com.google.android.providers.settings/databases/settings.db
"\"INSERT INTO system VALUES(99,'http_proxy','[My proxy]:[My port
number]');\
setprop net.eth0.http-proxy My proxy:My port number

Rgrds,
Dinesh .S

[Marco Pagliari]

Maybe you can find useful informations regarding the status of the proxy in Android here:http://www.android-proxy.com/

I'm trying to build a list of guides for both users and developers, with focus on proxy related tasks.