search

dolt131943 / androidscreencast

Automatically exported from code.google.com/p/androidscreencast
0 stars 0 forks source link

No mouse/keyboard control? #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
When I use the new 0.2 release I no longer get the permission denied, and 
I get the "device" on my screen - but I cannot control it. Mouse and keys 
doesn't work. When I control the device on my Magic it displayes fine on 
the monitor...

What version of the product are you using? On what operating system?
Windows Vista Home Premium - service pack 1
Java 6 version 16
HTC Magic - firmware 1,5 Build 2.16.401.5 (No Root)
Android-sdk-windows-1.6_r1.zip

Original issue reported on code.google.com by kochhansen on 16 Oct 2009 at 7:56

GoogleCodeExporter commented 9 years ago 
I can also confirm that tjcSmith's procedure (Comments 19 and 26) works on Moto 
Droid running FroYo FRF57.

Original comment by jtb...@gmail.com on 15 Jun 2010 at 5:50

GoogleCodeExporter commented 9 years ago 
Moving the .dex file to Dalvik-Cache caused my Milestone to reboot as soon as 
USB was connected. Then, after the reboot, the file was gone, and no more 
reboots after connecting USB... guess it didn't like it all too much... :|

Any ideas?

Original comment by simonbro...@gmail.com on 15 Jun 2010 at 6:29

GoogleCodeExporter commented 9 years ago 
Make sure you have upgrded to the relevant revision of the SDK and then start 
an emulator for THAT version to grab the .dex from... I figured that out when 
the r7/2.1u1 .dex wouldn't work on my Droid running r8/2.2... updated to the r8 
SDK and redid the steps and alls well for me... I don't have a Milestone to 
test this on so your mileage may vary...

Original comment by jtb...@gmail.com on 15 Jun 2010 at 7:11

GoogleCodeExporter commented 9 years ago 
You may be onto something there - I was using an Android 2.2 emulator, and my 
Milestone is running 2.1. I'll give it another try tomorrow :)

Thanks for the tip!

Original comment by simonbro...@gmail.com on 15 Jun 2010 at 7:16

GoogleCodeExporter commented 9 years ago 
Hmmm, for some reason I can't move the file to dalvik-cache.

mv ... failed on '/data/local/...' - Cross-Device link.

Could it be because of my having moved Dalvik-Cache to a different partition? 
Moving the file via Root Explorer doesn't work either (says it's moving the 
file and then doesn't do anything)...

Original comment by simonbro...@gmail.com on 16 Jun 2010 at 10:15

GoogleCodeExporter commented 9 years ago 
Hi there all.
I'm new to this things and i have a problem.
I've a htc magic 1.6.
I'm running windows vista sp2.
I've no root access.
Like many others i can see the htc magic screen but with no mouse and keyboard 
access.
With adb logcat i was able to see an exception when running android screencast.

Can you please help me?

Thanks in advance.

CV

D/AndroidRuntime( 1756):
D/AndroidRuntime( 1756): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1756): CheckJNI is OFF
D/AndroidRuntime( 1756): --- registering native functions ---
I/ActivityManager(   74): Process laik.widget.agenda (pid 441) has died.
E/dalvikvm( 1756): Can't open dex cache '/data/dalvik-cache/data@local@tmp@Injec
tAgent.jar@classes.dex': No such file or directory
I/dalvikvm( 1756): Unable to open or create cache for /data/local/tmp/InjectAgen
t.jar
E/AndroidRuntime( 1756): ERROR: unable to load class 'net.srcz.android.screencas
t.client.Main' from 0x4001ddd0
E/AndroidRuntime( 1756): ERROR: could not find class 'net.srcz.android.screencas
t.client.Main'
D/AndroidRuntime( 1756): Shutting down VM
W/dalvikvm( 1756): threadid=3: thread exiting with uncaught exception (group=0x4
001da68)
E/AndroidRuntime( 1756): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime( 1756): *** EXCEPTION IN SYSTEM PROCESS.  System will crash.
E/AndroidRuntime( 1756): java.lang.ClassNotFoundException: net.srcz.android.scre
encast.client.Main in loader dalvik.system.PathClassLoader@4001ddd0
E/AndroidRuntime( 1756):        at dalvik.system.PathClassLoader.findClass(PathC
lassLoader.java:243)
E/AndroidRuntime( 1756):        at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:573)
E/AndroidRuntime( 1756):        at java.lang.ClassLoader.loadClass(ClassLoader.j
ava:532)
E/AndroidRuntime( 1756):        at com.android.internal.os.RuntimeInit.finishIni
t(Native Method)
E/AndroidRuntime( 1756):        at com.android.internal.os.RuntimeInit.main(Runt
imeInit.java:186)
E/AndroidRuntime( 1756):        at dalvik.system.NativeStart.main(Native Method)

E/AndroidRuntime( 1756): Crash logging failed: java.lang.NullPointerException
I/Process ( 1756): Sending signal. PID: 1756 SIG: 9

Original comment by carlos.j...@gmail.com on 17 Jun 2010 at 2:20

GoogleCodeExporter commented 9 years ago 
what is "rooted"?

Original comment by mmservic...@gmail.com on 14 Jul 2010 at 9:47

GoogleCodeExporter commented 9 years ago 
Comment 26 solved all problems with my rooted moto droid running Froyo. The 
only hold up was in step 2. Do not copy/paste from this page, it doesn't space 
things right. When manually typed out I did not have problems.

Original comment by ruxtr...@gmail.com on 16 Jul 2010 at 9:43

GoogleCodeExporter commented 9 years ago 
Isn't working on my rooted Samsung Galaxy i7500 (galax0 1.6.3.3).

I can see the screen, but no control with keyboard or mouse.

I followed the instructions I saw in some comments but isn't work.

Any one with the same devide had success?

Original comment by TheRpL...@gmail.com on 9 Aug 2010 at 6:48

GoogleCodeExporter commented 9 years ago 
Works 100% with TJs fix, now the lil problem of the speed lol!

Original comment by Stephen....@gmail.com on 30 Aug 2010 at 5:20

GoogleCodeExporter commented 9 years ago 
I have rooted Xt720. but don't work mouse and key. Finally I solved this 
problem.
I used RootExplorer for this issue. just change dalvik-cache directory 
Permission. Checked Other Read/Write Permission. Keyboard/mouse all work fine.

Original comment by kyrha7...@gmail.com on 14 Sep 2010 at 5:19

GoogleCodeExporter commented 9 years ago 
Thanks, RootExplorer change dalvik-cache directory permission solved problem 
with keyboard/mouse on my Samsung Galaxy 3. In Call menu keyboard/mouse not 
working :(

Original comment by omachac...@gmail.com on 17 Sep 2010 at 9:30

GoogleCodeExporter commented 9 years ago 
I don't have data@local@tmp@InjectAgent.jar@classes.dex anywhere in my android 
filsystem. How do I do then? Copy from somewhere else? 

I'm running Galaxy 5 GT-I5500B with android 2.1. 

My computer OS is Arch Linux. Thank you!

Original comment by alinefr...@gmail.com on 19 Sep 2010 at 7:26

GoogleCodeExporter commented 9 years ago 
I just used root explorer and changed permission of directory dalvik-cache to 
777 and it works fine with mouse and keyboard.  Is this a security risk?

None of the other ways worked because it kept saying TEMPclasses.dex did not 
exist so I could not pull what is not there.

Rooted Moto Droid 2.2

thanks for help!

Original comment by phaze3131 on 24 Sep 2010 at 3:19

GoogleCodeExporter commented 9 years ago 
Hi! I'm from Argentina, I've found this project searching in XDA and I think 
it's really interesting.

I'm running it on Moto Milestone 2.1 rooted, and I can see my home, but I can't 
control it, only view it.

Is there a solution to this without giving full control to dalvik cache 
(security reasons)?

Thanks!

Original comment by ngiagn...@gmail.com on 30 Sep 2010 at 3:22

GoogleCodeExporter commented 9 years ago 
Having the same on a Rooted Nexus one with FRG83 2.2.1
OSX.

Java app updates the screen, right click works, in app buttons, home, menu, 
back, url do not work. mouse does not control device. 

More then happy to provide more info.

Original comment by avulsion...@gmail.com on 3 Oct 2010 at 9:53

GoogleCodeExporter commented 9 years ago 
i'm on a rooted evo running the 10/6 nightly of CM6.  no love with button 
control.  tried pushing the dex file and it didn't matter one bit.  i can 
right-click and rotate, i can explore.  i cannot, however, manage to get the 
phone to do squat using keyboard/mouse controls.  

adb remounted prior to running java program, still no luck

Original comment by timothyd...@gmail.com on 6 Oct 2010 at 8:08

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Thank you TJ for the workaround, here is a super simplified version of the walk 
through... if you can't follow this i don't know if you should be doing this.

{NOTE: CMD LINES ASSUME YOU INSTALLED ANDROIDSDK DIRECTLY TO C:\ and changed 
its name... i.e. C:\AndroidSDK}

                             ~Phone should not be connected yet~

1.Download AndroidSDK to C:\ and change its name to AndroidSDK

2.Run it and update everything (this will take a bit of time)

3.Make an AVD (Android Virtual Device) of your phone. Virtual Devices>New…
      Give it a name (whatever is clever)
      Target (your android version)
      SD Card (size of SD)
      Create AVD

4.Start AVD, let it load completely to android home screen

5.Start Screencast

6.Open command line (start>search>cmd)

7.In cmd type… (every line signifies the push of enter)
      cd\
      cd AndroidSDK\tools
      adb pull /data/dalvik-cache/data@local@tmp@InjectAgent.jar@classes.dex mine.dex

8.Turn off emulator, Android SDK, and screencast

9.Connect ROOTED droid (MUST BE IN USB DEBUG MODE)

10.in cmd type…
      adb push mine.dex /data/local/data@local@tmp@InjectAgent.jar@classes.dex
      adb shell
      su (wait a second b/c your phone will ask you to allow/deny access to Super User, allow)
      mv /data/local/data@local@tmp@InjectAgent.jar@classes.dex /data/dalvik-cache/data@local@tmp@InjectAgent.jar@classes.dex

That’s it. Nothing of importance will post on cmd to let you know it worked. 
Close out cmd and turn on screencast again. It should work fine no bugs or 
crashes at all, right click works too. Admittedly it is a bit slow on screen 
but input is instantaneous if looking at your phone. Also, your phone has to 
stay in Debug mode for it to work.

Original comment by oneill....@gmail.com on 11 Oct 2010 at 12:24

GoogleCodeExporter commented 9 years ago 
was able to make it work on my Droid 1 with no hassle----------Just got my 
Droid 2 and it only displays. cannot control from the mouse or keyboard. Did 
the steps in post 71 and still nothing.  any ideas guys? Im rooted.  One thing 
I did notice what that if I click on explore at the top of screencast that the 
data folder says "denied" if im root shouldnt this be wide open? hwo can I fix 
that issue?

Original comment by davidjmo...@gmail.com on 15 Oct 2010 at 6:44

GoogleCodeExporter commented 9 years ago 
Ok New symptom.....if im on the home screen nothing is working.....not keyboard 
or mouse. BUT if i go into a message both work. I can email and also use the 
buttons on the app.  anyone know why it works in the apps but noot outside any 
apps?

Original comment by davidjmo...@gmail.com on 15 Oct 2010 at 8:39

GoogleCodeExporter commented 9 years ago 
I've just upgraded to 2.2 on my Milestone. None of the above methods are 
working. The Chmod 777 worked for 10 seconds then stopped.

Its as if the system changes the security on the folder just when it needs it.

Original comment by mat.john...@gmail.com on 20 Oct 2010 at 1:10

GoogleCodeExporter commented 9 years ago 
I just tried pulling/pushing the .dex file and still no dice.

Moto Droid, 2.2 rooted. I can see it fine, but no input.

Original comment by Dwebt...@gmail.com on 9 Nov 2010 at 2:33

GoogleCodeExporter commented 9 years ago 
Hi guys!! i have trouble with my hero.. :(

I can see the screen on my Mac but... i can not control it..
I have superuser control.. 

Where Am I wrong?

Original comment by tufano.d...@gmail.com on 16 Nov 2010 at 4:23

GoogleCodeExporter commented 9 years ago 
HTC Vision (T-Mobile G-2) rooted, OS 2.2, tried before and after the pull/push 
and chmod instructs above.  Can view, but no mouse or keyboard.  I do get this 
in a popup while Screencast is loading:

java.lang.NullPointerException
    at net.srcz.android.screencast.api.injector.Injector.connectToAgent(Injector.java:195)
    at net.srcz.android.screencast.api.injector.Injector.init(Injector.java:175)
    at net.srcz.android.screencast.api.injector.Injector.access$0(Injector.java:155)
    at net.srcz.android.screencast.api.injector.Injector$1.run(Injector.java:26)

Original comment by pator...@gmail.com on 23 Nov 2010 at 6:42

GoogleCodeExporter commented 9 years ago 
had the same problem (no left mouse or keyboard) on rooted Epic.

I just changed the permissions on dalvik-cache directory as following:

adb shell
su
cd data
chmod 777 dalvik-cache

Restarted the desktop app and have full control now.

Is changing the permissions on that directory too risky? Is there a particular 
file I can change permissions on instead of the entire directory? Thanks.

Original comment by pryosl...@gmail.com on 4 Dec 2010 at 6:16

GoogleCodeExporter commented 9 years ago 
Rooted DX i have some control mouse works in texts e-mails but it doesnt work 
on any of the home screens the key board works but the directional keys only go 
up down and to the right no left and i have the Droid explorer program on my 
computer. Is there a really easy way to fix it so i have total and full 
control? im not very computer savy sorry :(

Original comment by Oblivion...@gmail.com on 28 Dec 2010 at 7:05

GoogleCodeExporter commented 9 years ago 
Just an update I can get this to work every time on my droid x (had a period 
last month where I needed a replacement and went thru a few handsets before 
asurion decided just to give me a new phone)

{NOTE: CMD LINES ASSUME YOU INSTALLED ANDROIDSDK DIRECTLY TO C:\ and changed 
its name... i.e. C:\AndroidSDK}

                             ~Phone should not be connected yet~

1.Download AndroidSDK to C:\ and change its name to AndroidSDK

2.Run it and update everything (this will take a bit of time)

3.Make an AVD (Android Virtual Device) of your phone. Virtual Devices>New…
      Give it a name (whatever is clever)
      Target (your android version)
      SD Card (size of SD)
      Create AVD

4.Start AVD, let it load completely to android home screen

5.Start Screencast (see note if screencast does not work)

6.Open command line (start>search>cmd)

7.In cmd type… (every line signifies the push of enter)
      cd\
      cd AndroidSDK\platform-tools
      adb pull /data/dalvik-cache/data@local@tmp@InjectAgent.jar@classes.dex mine.dex

8.Turn off emulator, Android SDK, and screencast

9.Connect ROOTED droid (MUST BE IN USB DEBUG MODE)

10.in cmd type…
      adb push mine.dex /data/local/data@local@tmp@InjectAgent.jar@classes.dex
      adb shell
      su (wait a second b/c your phone will ask you to allow/deny access to Super User, allow)
      mv /data/local/data@local@tmp@InjectAgent.jar@classes.dex /data/dalvik-cache/data@local@tmp@InjectAgent.jar@classes.dex

That’s it. Nothing of importance will post on cmd to let you know it worked. 
Close out cmd and turn on screencast again. It should work fine no bugs or 
crashes at all, right click works too. Admittedly it is a bit slow on screen 
but input is instantaneous if looking at your phone. Also, your phone has to 
stay in Debug mode for it to work.

*******NOTE: the only bug I have found is that sometimes I need to scan with 
adb devices to get screencast to work. to do this open cmd and:

          cd\
          cd AndroidSDK\platform-tools
          adb devices

Also, I just did it to my droid while updating this post and noticed that 
Screencast has been updated to scan for devices as well, BUT, I had no control 
with keyboard or mouse. However, after doing the above steps I did.

good luck

Original comment by oneill....@gmail.com on 27 Feb 2011 at 8:31

GoogleCodeExporter commented 9 years ago 
Comment 38 worked for me on HTC Hero with android2.3

Thanks Guys!

Original comment by s.raje...@gmail.com on 5 Mar 2011 at 9:28

GoogleCodeExporter commented 9 years ago 
Comment number 42:
I faced the same problem and fixed it
It has happened because you have not agreed to super user access.

When you enter su check you phone display

Original comment by mahekm...@gmail.com on 22 Mar 2011 at 10:04

GoogleCodeExporter commented 9 years ago 
I did the above steps several times on a rooted Android-3 ASUS Transformer 
TF101. All the commands work and the files are in the right place but cannot 
get mouse access. Right click rotates screen and the keyboard seems to work 
fine.  Just mouse issues.

with the log "adb logcat" I did see these messages if they make sense to anyone.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.
W/WindowManager(  142): Input event injection failed.
I/InputDispatcher(  142): Dropped event because input dispatch is disabled.

Original comment by AD.Barco...@gmail.com on 29 Jun 2011 at 5:30

GoogleCodeExporter commented 9 years ago 
question will it ever be able to work on the camera and video everything works 
just fine like if i pulled up camera all the buttons work but you cant actually 
see what the camera sees?

Original comment by NickDixo...@gmail.com on 30 Jun 2011 at 8:24

GoogleCodeExporter commented 9 years ago 
I can verify that comment 33 (thanks) works on Motorola Droid.  I was able to 
get android screencast to display but had difficulty getting the mouse and 
keyboard to work. I found the easiest way to resolve the problem was:

  1)Download "Better Terminal Emulator Pro" from the market (there is a fee of $3.99 but worked well...other free terminal emulators and a basic version of $0.99 are available but not tested)

  2)Open the application and proceed to the Shell section. Look for the words "Start as root" and make sure it is checked (this will start the terminal as root (device must be rooted)

  3)Type in the following commands...

chmod 777 /data/dalvik-cache
cd /data/dalvik-cache
chmod 777 ./*

Start android screencast. Mouse and keyboard will work.  There is some delay of 
the typed words and mouse clicks, but only on the pc (screencast). No delay on 
the actual android device. Hope this helps others who are having difficulty. 
Best of luck and leave a reply if helpful.

Original comment by bphech...@gmail.com on 24 Oct 2011 at 1:45

GoogleCodeExporter commented 9 years ago 
same here...rooted G1. not able to mouse, keyboard. only right clicks works.
DEVICE: G1
STATUS: rooted
Java 1.6 v 17
SDK 2.0
vista ultimate

Original comment by pudem...@gmail.com on 5 Mar 2012 at 1:15

GoogleCodeExporter commented 9 years ago 
galaxy s2 on ICS

followed the procedure, but only the keyboard works :/

Original comment by tiitaf...@gmail.com on 8 May 2012 at 9:40

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
No Mouse support for ICS with the newest SDK.

Original comment by Childoft...@gmail.com on 9 Jul 2012 at 5:16

GoogleCodeExporter commented 9 years ago 
droidx - have done the steps to pull to tmp, push, move, verified 777, yada 
yada yada. still nothing other than right click rotates. 

rooted of course
sdk 2
android 4.1 api 16

any suggestions?

Original comment by joshthue on 28 Aug 2012 at 8:44

GoogleCodeExporter commented 9 years ago 
JellyBean ROM exceptions (no mouse&keyboard):

12-17 20:18:15.172: E/AndroidRuntime(1448): java.lang.NoSuchMethodError: 
android.view.IWindowManager.injectPointerEvent

12-17 20:29:45.919: I/dalvikvm(2716): Could not find method 
android.view.IWindowManager.injectPointerEvent, referenced from method 
net.srcz.android.screencast.client.Main.handleCommand

12-17 20:29:45.919: I/dalvikvm(2716): Could not find method 
android.view.IWindowManager.injectKeyEvent, referenced from method 
net.srcz.android.screencast.client.Main.handleCommand

...

Original comment by gajo...@gmail.com on 17 Dec 2012 at 8:29

GoogleCodeExporter commented 9 years ago 
Galaxy S2 Skyrocket on JellyBean

As soon as I click the mouse, i get this:

02-04 14:23:30.760 W/dalvikvm(17175): threadid=11: thread exiting with uncaught 
exception (group=0x414e1360)
02-04 14:23:30.760 E/android.os.Debug(17175): !@Dumpstate > dumpstate -k -t -z 
-d -o /data/log/dumpstate_sys_error
02-04 14:23:30.760 E/AndroidRuntime(17175): *** FATAL EXCEPTION IN SYSTEM 
PROCESS: Thread-13
02-04 14:23:30.760 E/AndroidRuntime(17175): java.lang.NoSuchMethodError: 
android.view.IWindowManager.injectPointerEvent
02-04 14:23:30.760 E/AndroidRuntime(17175):     at 
net.srcz.android.screencast.client.Main.handleCommand(Main.java:110)
02-04 14:23:30.760 E/AndroidRuntime(17175):     at 
net.srcz.android.screencast.client.Main.handleClient(Main.java:95)
02-04 14:23:30.760 E/AndroidRuntime(17175):     at 
net.srcz.android.screencast.client.Main.access$0(Main.java:82)
02-04 14:23:30.760 E/AndroidRuntime(17175):     at 
net.srcz.android.screencast.client.Main$1.run(Main.java:41)
02-04 14:23:30.790 I/dumpstate(17220): begin

Original comment by Rushi.1...@gmail.com on 4 Feb 2013 at 7:38

GoogleCodeExporter commented 9 years ago 
I'm confused as to how to open the emulator on the computer.  I'm assuming that 
what you're doing anyway considering screencast wouldn't make sense for someone 
who's screen worked on their phone.  My captivate's screen is shattered but it 
still works.  Trying to reset my phone to sell it.  I can see the phone on 
screencast but can't control it.  I downloaded better terminal emulator (Free 
version) onto the phone.  But how do I open it if my phone doens't work?  Or 
how do I open it on my computer to control my phone?  Sorry for these noob 
questions.

Original comment by Jay.Kay...@gmail.com on 9 Feb 2013 at 6:42

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
till now i didn't found an answer for those who did everything above and the 
mouse and the keyboard still now working, its seems that screencast and the 
honeycomb will not work with any android version above 2.2,
if am a good java developer ill modify the screencast in away to make it work 
with the new android version, but sadly am not
anyway is there any other way or other app to do the same job as the screencast

Original comment by kimhars...@gmail.com on 13 Feb 2013 at 9:45

GoogleCodeExporter commented 9 years ago 
Hi
I've a different problem... In my case my keyboard is working fine but NO mouse 
control. I can use right click which rotate the screen view but cant open any 
app or select anything with mouse!!!

Any help will be highly appreciate 

my Phone: HTC incredible S
PC: XP service pack 3
Droid version: 0.8.8.8 (x86)

Original comment by snc...@gmail.com on 23 May 2013 at 4:24

GoogleCodeExporter commented 9 years ago 
I can't get the mouse to work on a rooted Galaxy S3 (android 4.0.4).

I'm getting this in the log:

I/InputDispatcher( 2089): Dropped event because input dispatch is disabled.
W/WindowManager( 2089): Input event injection failed.
I/InputDispatcher( 2089): Dropped event because input dispatch is disabled.
W/WindowManager( 2089): Input event injection failed.
I/InputDispatcher( 2089): Dropped event because input dispatch is disabled.
W/WindowManager( 2089): Input event injection failed.
I/InputDispatcher( 2089): Dropped event because input dispatch is disabled.
W/WindowManager( 2089): Input event injection failed.
I/InputDispatcher( 2089): Dropped event because input dispatch is disabled.
W/WindowManager( 2089): Input event injection failed.

Original comment by rustam...@gmail.com on 19 Jun 2013 at 7:18

GoogleCodeExporter commented 9 years ago 
Sorry, the actual log for my previous message is in fact this one:

I/InputDispatcher( 2086): Dropped event because it is stale.
W/WindowManager( 2086): Input event injection failed.
I/InputDispatcher( 2086): Dropped event because it is stale.
W/WindowManager( 2086): Input event injection failed.
I/InputDispatcher( 2086): Dropped event because it is stale.
W/WindowManager( 2086): Input event injection failed.
I/InputDispatcher( 2086): Dropped event because it is stale.
W/WindowManager( 2086): Input event injection failed.
I/InputDispatcher( 2086): Dropped event because it is stale.
W/WindowManager( 2086): Input event injection failed.

Original comment by rustam...@gmail.com on 19 Jun 2013 at 7:47