removing Phone.apk from the device

by RajaniKanth » Wed, 29 Apr 2009 18:09:39 GMT


Sponsored Links
 Hi All,
          To remove PhoneApp form the device, i followed the below
setps:

1) Execute 'adb remount' to mount /system folder in rw mode.
2) telnet 192.168.16.2 to logint to phone.
3) Execute 'rm /system/app/Phone.apk' to remove apk.
4) Execute 'rm /data/dalvik-cache/sys...@app@phone....@classes.dex'
to remove the running instance of the Phone app
5) Execute ' cd /data/data' and 'rm -R rm -R com.android.phone' to
remove the personal data of Phone App.

Even after doing all these setps, PhoneApp is still running on the
device.

Is it due to the android:persistent="true"attribute in
AndroidManifest.xml file.

Could you please help me in removing Phone App from the device.

Cheers
RajaniKanth
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. Bluetooth : RFCOMM connection fails while connecting to a headset which is in discoverable mode.

Hi,
  Iam novice to android and i have seen a issue in G1. can some one
help me to proceed further ?
Steps to reproduce:
1.Pair and connect to a BT mono / Stereo headset.
2. Disconnect the headset from the G1 phone.
3. Switch off the headset.(Plantronics 320 / Motorola HT820)
4. Put the headset back in discoverable mode.
5. Now initiate a connection from G1.
6. Problem in connecting to Headset message pops up.
Note: when a stereo headset is connected in the same way (step 5) ,
only a2dp connection succeeds and HFP connection always fails. when a
mono headset is connected (step 5) , failure happens as it supports
only hfp.
of the RFCOMM connection failure. I see the below message in the log:

rfcomm async connect() error: CONNECTION REFUSED (111).40 attempts of
calls to waitForAsyncConnectNative has failed and the result was
returned as < 0..
Reference: waitForAsyncConnectNative() function in
android_server_headsetbase.cpp.

Any help would be really useful.

Thanks in advance,
Bhargavi


--~--~---------~--~----~------------~-------~--~----~

2. Static Variables after Application life cycle

Hello all,
  I have noticed in my application(s) that after a call to
Activity.finish() that the static variables that I declared in my
classes still hold the values that they were changed to during the
activity's life cycle. Upon the re-launch of the activity, the program
does not re-instantiate the variables as declared or set them to the
default java behavior. Is there something that I can do to cause this
to happen, other than re-setting every static variable in my
application?

--~--~---------~--~----~------------~-------~--~----~

3. How to get the current webpage title and url

4. setup email account programatically

5. Static Variable after Application life cycle.

6. Use native C/C++ libraries

7. shared ID and permissions sharin