How to make an application NOT uninstallable like build-in apps

by Jean-Baptiste Queru » Fri, 06 Mar 2009 05:23:13 GMT

Sponsored Links
 You need to be able to work directly in the system image, i.e. to work
directly with (or to be) a device manufacturer.


On Thu, Mar 5, 2009 at 9:27 AM, Explore Android

Jean-Baptiste M. "JBQ" Queru
Android Engineer, 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


Other Threads

1. Buat yang mesan battery BP6X kloter lalu (4-8 Mei

maaf mods, numpang jalum,
karena kesalahan saya, daftar nama pemesan battery hilang,
dan sampe sekarang masih ada satu orang yang belum mengirimkan ulang data
sehingga battery BP6X+EBC-nya belum dikirim.

bagi yang merasa memesan dan belum menerima batterynya,
silahkan japri, coz barangnya udah sampe dari hari sabtu kemarin. :)

thanks dan maaf jika mengganggu yang lain,, :)

"Indonesian Android Community [id-android]" 

2. Any guidelines for handling the Headset and Bluetooth AVRC buttons in Froyo?

I am trying to figure out what is the correct (new) approach for
handling of Intent.ACTION_MEDIA_BUTTON in Froyo. In pre 2.2 days we
had to register a BroadcastReceiver (either permanently or at run-
time) and the Media Button events would arrive (as long as no other
application intercepts them and aborts the broadcast).

Froyo seems to still somewhat support that model (at least for the
wired headset), but it also introduces the
registerMediaButtonEventReceiver, and
unregisterMediaButtonEventReceiver  methods that seem to control the
"transport focus" between applications.

During my experiments, using registerMediaButtonEventReceiver does
cause  both the bluetooth and the wired headset button presses to be
routed to the application's broadcast receiver (the app gets the
"transport focus"), but it looks like any change in the audio routing
(for example  unplugging the headset) shits the focus back to the
default media player.

What is the correct way to handle that in Froyo? Do we have to detect
the change in the audio routing and try to re-gain the focus?

This is an issue that any 3rd party media player on the Android
platform has to deal with, so I hope that a Google Engineer can
provide some guidelines that we all can follow. Having a standard
approach may make headset button controls a bit more predictable for
the end users.



3. Digest for - 25 Messages in 18 Topics

4. Battery & EBC for Motorola BP6X, Nexus On

5. Error playing multiple sounds

6. Sending touch screen events to the emulator

7. MAAF - [Pre-Order] Battery & EBC for Motorola BP6X, Nexus One