respond to
android-developers@googlegroups.com
To
Android Developers android-developers@googlegroups.com
cc
Subject
[android-developers] Re: Unable to start service Intent error in
Client-Server project
Make sure you have added TestService to your build path for the
service monitor :).
I'm
Hi Hans,Thanks for your help Hans, i have created two projects same as your project name and added your files, the TestService project is fine, but for ServiceMonitor project it is giving error at the import statement only.It is not allowing to import the TestService as "The import
You should only need the AIDL file to reside in the TestService's
folder because the IDL compiler will find it there. Again, make sure
you have your build path setup properly for Service Monitor.
Iirc, I tested this on a laptop I'd not used for anything and it built
for me straight away when I
There apparently is an implementation of that class in your local client
.apk. It is very clear from the logs that the client is trying to interact
with -some- component in its package, as you can see right in the component
name.
On Thu, Feb 12, 2009 at 2:37 PM, Hans hkess...@gmail.com wrote:
On Sat, Feb 14, 2009 at 7:38 AM, sunil.mahar...@lntinfotech.com wrote:
import com.android.TestService.*;
Is this code part of the android platform? No? Then please don't use this
namespace. Thanks. :)
--
Dianne Hackborn
Android framework engineer
hack...@android.com
Note: please don't
I'm not trying to be argumentative for the sake of being argumentative
Dianne, but if that was the case, how could the IPC calls to the
remote process be resolved if they are only declared in the manifest
for the service project which is in a different *.apk? This would
mean that android was
On Feb 14, 3:12 pm, Dianne Hackborn hack...@android.com wrote:
On Sat, Feb 14, 2009 at 7:38 AM, sunil.mahar...@lntinfotech.com wrote:
import com.android.TestService.*;
Is this code part of the android platform? No? Then please don't use this
namespace. Thanks. :)
--
Dianne Hackborn
Crud Suni - I accidentally left an error call (from when I was testing
out the weirdness of service creation the 'wrong' way) in the
StartService method in the Service Monitor class...
Right below the comment //Attempt to start the service there's a
call:
startService( new Intent( this,
Fixed and re-uploaded in case anyone else uses it.
--~--~-~--~~~---~--~~
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
To unsubscribe from
On Sat, Feb 14, 2009 at 1:14 PM, Hans hkess...@gmail.com wrote:
I'm not trying to be argumentative for the sake of being argumentative
Dianne, but if that was the case, how could the IPC calls to the
remote process be resolved if they are only declared in the manifest
for the service project
by: android-developers@googlegroups.com
02/13/2009 01:40 AM
Please respond to
android-developers@googlegroups.com
To
Android Developers android-developers@googlegroups.com
cc
Subject
[android-developers] Re: Unable to start service Intent error in
Client-Server project
On Feb 12, 2:47 pm
Hi All,
When my client code calls bindService it was fine and it calls
onServiceConnected, there i am calling the interface method using the
.Stub.asInterface(service) object and there only it gives me bunch
of error as:
02-13 17:14:52.239: WARN/Parcel(1035): enforceInterface()
Sunil, I'll zip up my test projects (a client in its own package and
*.apk and a remote service it its own package, and *.apk, exposing 2
interfaces and using callbacks into the client), I'll post the URL
here when I've done it.
Hope it helps :).
Here's the URL: http://www.plugin-factory.com/storage/workspace.zip
There are two projects in it:
(1)ServiceMonitor - a simple activity that has 3 buttons and a
text view. One buttons starts and binds to the service, the other
stops and unbinds from the service, the third is a query
I tried a similar aidl thing a week ago.
I hope you r binding to the service like bindService(*new*Intent(IRemoteService.
*class*.getName()),Conn, Context.*BIND_AUTO_CREATE*);
Going by the error it looks like you missed the intent filter tag for your
service...
i.e.
intent-filteraction
When I built my client/service code I had two projects, one for the
client (the Activity) and a different project for my Service.
Now, I spent about 3 hours struggling until I realized that for some
reason (probably because I was using an out of process service) I
needed to not only declare my
That really should not fix things. :} I suspect that whatever is happening
now is really not what you want. If the -real- service you are wanting to
bind to does not have an intent-filter, you need to make sure you use
android:exported=true on it so other .apks can find it. Also you can do
adb
I will try that, thanks :)
--~--~-~--~~~---~--~~
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
To unsubscribe from this group, send email
It didn't work. I commented out the service declaration in my
Activity's manifest:
service android:name=com.android.TestService.TestService/
And modified my service's manifest to include 'exported' like this:
?xml version=1.0 encoding=utf-8?
manifest
On Feb 12, 2:47 pm, Dianne Hackborn hack...@android.com wrote:
Um. This is the package your service is in:
manifest xmlns:android=http://schemas.android.com/apk/res/android;
package=*com.android.TestService*
And yet you are trying to start a service in the other package:
Unable to
It turns out that you can avoid using the service reference in your
client manifest if you declare what I presume is a global name in your
service's manifest and simply refer to this name in your client code.
This is what I added to my service's manifest:
action
I replied to this in the other thread, but if you want to explicitly
reference a component from one package that is in another, you need to
explicitly build the ComponentName of both the package and class name of the
target. The shorthand new Intent(this, ...) creates ComponentName objects
whose
On Feb 12, 5:09 pm, Dianne Hackborn hack...@android.com wrote:
I replied to this in the other thread, but if you want to explicitly
reference a component from one package that is in another, you need to
explicitly build the ComponentName of both the package and class name of the
target. The
23 matches
Mail list logo
