top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

Shared key on the Android platform

+1 vote

The platform has several keys that sign apps during build time (platform, shared, media. etc.) one of these keys is the shared key.

For what purpose do apps like Dialer ,Contacts and Launcher need to be signed with the same key? (Launcher and Contacts , for example, don't have a sharedUserId so I don't see why not use different keys for each)

posted May 26, 2014 by Kumar Mitrasen

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

1 Answer

+1 vote

Shared key was used at the time of Android cupcake, only because, at that time there were low-end devices, which required running home (i.e Launcher app) across process with Contacts apps in same process.

But using LOCAL_CERTIFICATE := shared in only really matters if the shared user id is set in Manifest.xml, otherwise launcher will still get its own uid.

Also There's no other reason for using shared key between Launcher, Contacts app,

answer May 29, 2014 by Honey
Similar Questions
+1 vote

I wanted to understand NFC architecture in AOSP code. Primarily a block diagram interaction between NFC hardware with Nfc application in /packages/Nfc over JNI. I can see that the JNI portion of Nfc app is trying to connect via some socket.

Not able to find out the other side of this socket connection. I will really appreciate if someone can point me to any document or blog.

+3 votes

With the major milestone release of Android Studio, I am worried about the suggested IDE for platform development. As we can see on the web [ ], there is a sort of tutorial to set up an Eclipse Environment for AOSP development: while it does not directly involve the ADT plugin, at the same time its presence in the environment it's useful in some situations.

Is there any plan for a substitution of Eclipse as "endorsed" IDE for AOSP?

+1 vote

I am back-porting camera2 legacy implementation to older platforms and want to ship android.util.Size inside the apk. I assume newer systems will simplify ignore these but am not sure such behavior is part of the public API.

+2 votes

I want to build Android 4.2.2 or later without support for telephony to reduce memory footprint. I see PRODUCT_POLICY := android.policy_phone in but it seems that this parameter is ignored.

Is it possible by build files configuration? Any other way?

+2 votes

I want to know whether GCM server API key generated for push notification using google project has expiry date/time?

Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.