Hi Dianne Hackborn,
Am also facing the same problem, can tell me wheather you got the
solution for the problem or not?
On Nov 22 2008, 5:23 am, "Dianne Hackborn"
wrote:
> Correct, one application can not inject key events into another
> application. There should be no way around this.
>
> For
There is no plan at this point, though I imagine some time in the future
some of these things may be allowed maybe under the guise of telling the
user that the application can do anything they can or such.
On Sat, Nov 22, 2008 at 8:33 AM, Dorn Hetzel <[EMAIL PROTECTED]> wrote:
>
> Is that a perma
That kinda seems like the wrong way to do things, simulating key
events.
But anyways, if you want to pass data between Activities, you add it
into the Intent. See putExtra() and getExtra().
- michael
--~--~-~--~~~---~--~~
You received this message because you ar
Quick question:
I am trying to use instrumentation to launch a second screen upon
pressing a button on the first screen (which is automatically launched
by the instrumentation code). I successfully do so. But, what I now
need to do is click something on the second screen (which is part of
the sam
Hi,
I've been just wondering about these security issues, injecting
events, access to some low level APIs, screen lock, telephony, etc.
I've been developing on other mobile operating systems for years and
all them allow this kind of technique, it's valuable for some kind of
applications, mainly i
I'm just wondering about these security issues, injecting events, access to
some low level APIs, screen lock, telephony, etc. I've been developing on
other mobile operating systems for years and all them allow this kind of
technique, it's valuable for some kind of applications, mainly in corporate
Is that a permanent, security related, state if the droid, or is it
thought that someday, with the right permissions, or between
consenting applications, this would be allowed? :)
On Fri, Nov 21, 2008 at 7:23 PM, Dianne Hackborn <[EMAIL PROTECTED]> wrote:
> Correct, one application can not inject
Correct, one application can not inject key events into another
application. There should be no way around this.
For instrumentation test cases that cross application boundaries, I strongly
recommend you set up an ActivityMonitor to block the launching of that other
application's activity, return
Hi Hackbod -
I tried this using Instrumentation -
The goal of this little program is to make an outgoing call and then
generate a keypress on the ENDCALL button.
1. It appears that I am incapable of unlocking the keyguard:
11-21 14:40:58.445: INFO/InstTest(209): after
inKeyguardRestrictedInput
On Nov 13, 4:42 pm, dreamerBoy <[EMAIL PROTECTED]> wrote:
> What gave me hope is that there was an injectKeyEvent method on
> WindowManager in the last API release.
> See:http://www.anddev.org/throwing-simulating_keystrokes_programatically-...
That was never in the SDK; that is a private API th
Hi Hackbod - sorry if I wasn't clear. This application is to be run
in a COMPLETELY AUTOMATED mode - no humans clicking on anything. No
humans at all - launch the app and review the results - that's it.
(It's more of a test application than a consumer application.)
What gave me hope is that the
Fwiw, there has never been a public API to inject a key event, except
for the official API is on the Instrumentation class (which still
exists). As far as I know we don't right now have an API to get an
Instrumentation object when not running an instrumentation test,
though.
I am a little confus
Note that the key event injection is inside the SAME application. I
am NOT trying to contact a foreign application to simulate e.g., user
behavior.
Hackbod was going on about InstrumentationTestCase to handle that
situation but I don't think that this case is from the same mold
(application cont
13 matches
Mail list logo
