Hi, I wonder if you have settled the problem stated here. I have
encountered the same problem as you. I have surfed a lot of posts regarding
to this issue but haven't found a solution. I also have two android
projects, one provides service and the other tries to access the service.
But I
I am still hanging on this issue,
maybe there is someone, who has played around with service and can
provide me some example code, where it works that a service, lying in
one eclipse project is successfully bound to and called maybe by an
activity, which resides lying in another eclipse
The file name doesn't matter, is completely irrelevant, and ignored. The
identity of your app is the package name you declare in the manifest. As I
said, you need to give them different package names for them to actually be
different apps.
On Fri, May 22, 2009 at 1:25 AM, dev_rob
Hey Dianne,
thanks a lot for your answer.
The package names are the same, but not the app-names.
The .apks are called
New_RPC_Client.apk
and
New_RPC_Server.apk
inside both apks the namespace/package name is
de.roberlin.new_rpc
This is the same in both apps, because the package has to be
For the second question, you'll either want to define an abstract action in
an intent-filter for the service and use that as the intent you bind to
(typically the action is the name of the desired interface for binding to
services), or create an explicit ComponentName with the package name + class
I now have the TestInterface.aidl in both eclipse projects and project
2 (the service project) is added to project 1's build path.
I declared the service in the manifest-file with:
service android:name=.TestStringService
android:exported=true
android:process=:remote
Er... you are sure that both .apks have different package names? Anyway it
sounds like whatever problem you have has nothing to do with services
themselves, but just getting both apps installed at the same time?
On Sun, May 17, 2009 at 7:35 AM, dev_rob robwiene...@googlemail.com wrote:
I now
I think it's rather a problem with namespaces. And the package names
in both projects are indeed identical!
But as (one of my original questions) both projects have to contain
the TestInterface.aidl the package names must be the same, because
otherwise there is a different package name in
If you have give the .apks the same name, you can't have them both installed
at the same time, because they are both effectively the same app.
You can have classes in whatever namespace you want inside of the .apk (and
even publish these in the manifest via fully qualified class names).
On Sun,
9 matches
Mail list logo
