wider225 / android-bluez-ime

Automatically exported from code.google.com/p/android-bluez-ime
0 stars 0 forks source link

Error: read failed, socket might closed or timeout, read ret: -1 #260

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What version of BluezIME are you using?
Latest from Play store as of 12/24/2013 (1.18 I think)

What Android device do you have? What Android version?
Samsung Galaxy S, Android 4.2.2 - CyanogenMod 10.1.3

What gamepad are you using?
Zeemote JS1 V3

What steps will reproduce the problem?
1. Pair remote to phone using Zeemote's software (test apps work fine)
2. Launch Bluez IME and select JS1
3. App shows message: Connecting to xx:xx:xx:xx:xx
4. App shows message: Error: read failed, socket might closed or timeout, read 
ret: -1

What is the expected output? What do you see instead?
App connecting to remote and showing message: Connection successful to 
xx:xx:xx:xx:xx

Please provide any additional information below.
I'm not sure if this is a 4.2.2 issue. I was using Bluez IME fine with stock 
android 2.3

Original issue reported on code.google.com by Zakaria....@gmail.com on 24 Dec 2013 at 6:38

GoogleCodeExporter commented 9 years ago
I Have a Samsung I9505 international, android 4.4.2 stock, with root access

used gamepads:
Zeemote JS1 
MSI CHainpus BGP100
Phonejoy
iControlPad

repro
1. Pair remote to phone using Zeemote's software (test apps work fine)
2. Launch Bluez IME and select JS1
3. App shows message: Connecting to xx:xx:xx:xx:xx
4. App shows message: Error: read failed, socket might closed or timeout, read 
ret: -1

What is the expected output? What do you see instead?
App connecting to remote and showing message: Connection successful to 
xx:xx:xx:xx:xx

Original comment by oqp...@gmail.com on 16 Jun 2014 at 9:06

GoogleCodeExporter commented 9 years ago
I have the same problem :\

Original comment by sithninj...@gmail.com on 13 Aug 2014 at 8:04

GoogleCodeExporter commented 9 years ago
Same problem on Nexus 9 Lollipop 5.0 with ps4 controller.
Controller actually kinda works but this message keeps repeating and alternates 
with a "connecting to [ps4Controller'sID]..."

Original comment by car...@districtware.com on 19 Nov 2014 at 5:16

GoogleCodeExporter commented 9 years ago
Same problem using dual shock 4 on my nexus 4, lollipop 5.0

Original comment by rush...@gmail.com on 5 Mar 2015 at 4:10