2010-06-09, 23:27
Thanks again for the replay Kitlaan. I think we are getting close to the root of the problem.
So I did what you said and 1) unpaired my remote. 2) stopped the bluetooth service. 3) I started "sudo bluetoothd -nd" and in another terminal ran the pairing script. When I went back to the bluetoothd terminal screen I saw nothing when I was mashing buttons. then after about 30 sec to a min later of still mashing I saw a bunch of Got Key commands flying up the screen. so far so good (kind of, see below). I tried the "hold PS button" to disconnect and after about 20 seconds i got the following message:
I wasnt sure what this meant but after pressing a button it looked like my remote reconnected because I saw this:
so disregarding the error I continued on. At this point I got the remote commands coming in through bluetooth and looks good. So next I terminated the bluetoothd and restarted it. Now when I go to press buttons, nothing. I kept pressing for like 5 mins and still nothing.
So it seems i am closer but my main problem is when I stop/start the bluetooth service my remote stops working completely. This is probably explains why when I reboot my system the remote doesnt work ( I verified uniput and the bluetooth service starts up on reboot).
My second problem (well question) is what might be the cause of the delay in my initial connection? I mean after I re-pair the remote I would think it would already be connected and sending commands immediately but it takes like I said about 30 sec to a full min before I see the remote commands coming out.
Third, that funky error message when my remote disconnected. I also flipped my off switch and saw the error (see my comment in this thread here on how to add a switch to the BD remote ). but again both times when I turned my remote back on and pressed a button, I saw the Got Key commands again.
So I did what you said and 1) unpaired my remote. 2) stopped the bluetooth service. 3) I started "sudo bluetoothd -nd" and in another terminal ran the pairing script. When I went back to the bluetoothd terminal screen I saw nothing when I was mashing buttons. then after about 30 sec to a min later of still mashing I saw a bunch of Got Key commands flying up the screen. so far so good (kind of, see below). I tried the "hold PS button" to disconnect and after about 20 seconds i got the following message:
Code:
bluetoothd[xxxx]: Got Key: 108 [0]
bluetoothd[xxxx]: Hangup or error on ps3remote server socket
(bluetoothd:xxxx) Glib-CRITICAL **: g_source_remove: assertion 'tag > 0' failed
I wasnt sure what this meant but after pressing a button it looked like my remote reconnected because I saw this:
Code:
bluetoothd[xxxx]: adapter_get_device(00:26:43:BA:B6:57)
bluetoothd[xxxx]: Incoming connection on PSM 17
bluetoothd[xxxx]: Incoming connection on PSM 19
bluetoothd[xxxx]: Processing PS3 device: 00:26:43:BA:B6:57
bluetoothd[xxxx]: Got Key: 108 [1]
bluetoothd[xxxx]: Got Key: 108 [0]
so disregarding the error I continued on. At this point I got the remote commands coming in through bluetooth and looks good. So next I terminated the bluetoothd and restarted it. Now when I go to press buttons, nothing. I kept pressing for like 5 mins and still nothing.
So it seems i am closer but my main problem is when I stop/start the bluetooth service my remote stops working completely. This is probably explains why when I reboot my system the remote doesnt work ( I verified uniput and the bluetooth service starts up on reboot).
My second problem (well question) is what might be the cause of the delay in my initial connection? I mean after I re-pair the remote I would think it would already be connected and sending commands immediately but it takes like I said about 30 sec to a full min before I see the remote commands coming out.
Third, that funky error message when my remote disconnected. I also flipped my off switch and saw the error (see my comment in this thread here on how to add a switch to the BD remote ). but again both times when I turned my remote back on and pressed a button, I saw the Got Key commands again.