"You can create a Service without an Activity, that's one of the
points
of a
Service, but you still need to be running in a process created by the
activity manager (from an .apk with a manifest etc). "

How can this be done? Any guides/examples of this?

On 16 Maj, 17:15, SGAdrian <[email protected]> wrote:
> Hi,
>
> I have developed a testagent which is started with app_process. This
> testagent can do things like inject keypresses, simulate touch events
> etc. More or less like the Monkey testprogram. The difference is that
> I can communicate with this program over TCP/IP and trigger
> functionality from my pc.
>
> In this process Ineedto call Android API:s thatneedaContext
> instance. So my question how can I get hold of one of these? I guess 
> aneedeither a Service or Activity.
>
> I dont want this program to be visible to the user so that leaves me
> with a Service. So can I start a Service without an Activity? And will
> I be able to inject keypresses between Activities if  I inject from
> this Service?
>
> I run this program as root as it is today so injecting keypresses
> between Activities has never been a problem as it is today.
>
> I will only use this for testing purposes and it will never reach the
> market place or anything. Just a internal testprogram for myself and
> my product.
>
> BR,
> Sven
>
> Like I said, you can't do this.  The appropriate list would probably
> be
> android-porting; I can't move the thread for you.
>
> You can create a Service without an Activity, that's one of the points
> of a
> Service, but you stillneedto be running in a process created by the
> activity manager (from an .apk with a manifest etc).
>
> It might help if you describe what you are actually trying to do, 
> whatcontextthis is coming from (you are building your own platform,
> creating
> something to upload to market, etc).
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to