Hello again,
just to let you know that the problem was that we've put the
taskAffinity="android.task.mms" for the application to be the same as
for the original mms application, and then they were considered to be
same tasks and the activities were randomly called by the launcher.
Makes sense, an
Hi again,
this is an extract of the Manifest:
http://schemas.android.com/apk/res/android";
package="Mmsfro.app">
-
...
-
-
The package name is unique accross the system, but the application
name and the activity name are the same as names of a different (stock
mms) appli
Also make sure you read and understand:
http://android-developers.blogspot.co.uk/2011/06/things-that-cannot-change.html
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
I have seen this, historically, on older phones using HTC's sense ui. The
application launcher would cache the invokable target using properties of
the AndroidManifest. It seemed to eventually go away, specifically if the
device was restarted. I noticed this specifically when we changed the name
On Tue, Oct 9, 2012 at 9:30 AM, katarina wrote:
> Actually the apk file has a different name, but within the Manifest we
> have application and activity names the same as the original mms
> application - do you think this can produce the cofusion too?
>
> Can it be because of the applicaiton name
Hi All,
thanks very much for your answers, we didn't know about domains, will
have to change that.
Actually the apk file has a different name, but within the Manifest we
have application and activity names the same as the original mms
application - do you think this can produce the cofusion too?
latimerius wrote:
> katarinawrote:
> > Can it be because we have another application on the phone with the
> > same name
>
> Hm, I don't think this is even possible - how do you achieve this?
> IIRC if you try to "adb install" an .apk with a package name that's
> installed already it will ret
On Mon, Oct 8, 2012 at 4:19 PM, katarina wrote:
> Can it be because we have another application on the phone with the
> same name
Hm, I don't think this is even possible - how do you achieve this?
IIRC if you try to "adb install" an .apk with a package name that's
installed already it will return
Can it be because we have another application on the phone with the
> same name - com.android.mms.MmsApp and another activity (in a
>
The Package name MUST be unique
> different application) with the same name
> com.android.mms.ui.ConversationList?
>
> What has to be unique on the system -
Hi Justin,
sorry for not coming back immediatelly I hope you will read this
message...
This is a part of the manifest file:
-
-
-
-
Can it be because we have another application on the phone with the
same name - com.android.mms.MmsApp and another acti
10 matches
Mail list logo
