Closed GoogleCodeExporter closed 8 years ago
what version of BTstack do you have installed? we had that problem before and I
thought it got fixed.
Please attach /tmp/hci_dump.pklg to this issued after it crashed.
Original comment by matthias.ringwald@gmail.com
on 19 May 2010 at 7:59
btstack keyboard (1.0-24939)
btstach mouse (1.0-24869)
I have another "microsoft wireless motebook presenter mouse 8000". I tried to
pair
with this one. It works well. The one which will crash the program is the old
one
bought in 3 years ago and the new one I got several months ago. I guess the
reason
why 2 mouses of the same model but get different results is that they use
different
bt chips. Anyway, the connection problem is solved and it is really great to use
mouse and keyboard on ipad. The only issue is that in my "jump desktop" app
about 1/4
of the right side of the lcd has no response to the mouse click. Is there
anyway to
solve this problem? Thanks!
Original comment by khs...@gmail.com
on 20 May 2010 at 1:53
please try to have a single ticket for a single issue.
as I wrote in the other ticket already, yes, mouse does not click in the area
next to
the HOME button, but nobody know why it's not working. That part is open-source
if
anybody is interested:
http://code.google.com/p/iphone-tweaks/source/browse/trunk/MouseSupport/Tweak.xm
Original comment by matthias.ringwald@gmail.com
on 20 May 2010 at 8:08
btw. mouse can click everywhere. make sure you have latest version of
MouseSupport
installed
Original comment by matthias.ringwald@gmail.com
on 28 May 2010 at 7:06
Original comment by matthias.ringwald@gmail.com
on 28 May 2010 at 7:16
thanks to another user, I've got a hci_dump.pklg and was able to figure out
what's
going on: It crashes because the remote name is not encoded in UTF-8 but in
Latin-1
although that's what the Bluetooth Specification mandates.
I've fixed it today in the sources, but it's not yet in the apps. The fix will
be in
the next update of BTstack GPS/Mouse/Keyboard.
Original comment by matthias.ringwald@gmail.com
on 28 May 2010 at 10:01
Original issue reported on code.google.com by
khs...@gmail.com
on 19 May 2010 at 7:54