You need to work with your device manufacturer.

If you don't have one, you will want to download the Android source code to
build your own emulator and system image, so you can sign your app with the
same cert used to sign your system build.

Please direct further questions to android-porting, as this is outside the
scope of SDK development.

On Sun, Sep 26, 2010 at 11:18 PM, Tejas <[email protected]> wrote:

> Hi Dianne,
>             Thank you very much for quick reply.
>
>             Is there any other way to access surface flinger APIs at
> development phase? Normally i have read your application needs to be
> signed then only you may get access to surface flinger.
>
>             Please guide me , i am on a critical phase of
> development.
>
> Thanks In Advance,
> Tejas.
>
> On Sep 27, 10:14 am, Dianne Hackborn <[email protected]> wrote:
> > This is not available as a third party application; you can only do this
> for
> > applications shipped with a system image, and by having the manufacturer
> > sign the .apk for you.
> >
> >
> >
> > On Sun, Sep 26, 2010 at 10:02 PM, Tejas <[email protected]> wrote:
> > > Hello All Developers,
> > >                I have written video renderer application which is
> > > using surface flinger APIs to get access of it. I am developing and
> > > building application on eclipse. So when i build it , it is already
> > > signed default. But when i run it on emulator, i am getting access
> > > permission failure of surfaceflinger.
> > >                On the some portal i have read that if i want to
> > > access surfaceflinger i need to signed my application with system key.
> > > Is it correct ? If it is correct, can anyone guide me how can i signed
> > > my application with system key to get access surfaceflinger.
> >
> > >                For your information i am developing my application on
> > > froyo.
> >
> > >                If i am wrong please correct me.
> >
> > > Thanks In Advance,
> > > Tejas.
> >
> > > --
> > > You received this message because you are subscribed to the Google
> > > Groups "Android Developers" group.
> > > To post to this group, send email to
> [email protected]
> > > To unsubscribe from this group, send email to
> > > [email protected]<android-developers%[email protected]>
> <android-developers%[email protected]<android-developers%[email protected]>
> >
> > > For more options, visit this group at
> > >http://groups.google.com/group/android-developers?hl=en
> >
> > --
> > Dianne Hackborn
> > Android framework engineer
> > [email protected]
> >
> > 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 [email protected]
> To unsubscribe from this group, send email to
> [email protected]<android-developers%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
>



-- 
Dianne Hackborn
Android framework engineer
[email protected]

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 [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

Reply via email to