User talk:Plaicy

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(spp)
 
Line 32: Line 32:
  
 
> Just to add to this info: I have not followed the unlock sequence offered through http://www.freedominput.com/unlock.html. I don't know if this really matters, but since I don't own compatible hardware (i have just the moko) i cannot get an unlock code :/
 
> Just to add to this info: I have not followed the unlock sequence offered through http://www.freedominput.com/unlock.html. I don't know if this really matters, but since I don't own compatible hardware (i have just the moko) i cannot get an unlock code :/
 +
 +
: Sorry for late reply, but I do not watch my personal page.  You should ether reply exactly where I wrote or use my discussion page.  Using "SPP" you do not need any "hci*" commands. "rfcomm connect 0".  If you send me an email I can sent you the python code.  But I can not test it at the moment because I have no working distribution on my phone.--[[User:Plaicy|plaicy]] 21:12, 23 August 2009 (UTC)

Latest revision as of 22:12, 23 August 2009

[edit] Universal Keyboard Hacking

Using the om2008.12 release + a fresh freedom keyboard (i do not possess any of the working smartphones as of date). It is a no-go at the moment. I saw your recent comment on http://wiki.openmoko.org/wiki/Talk:Manually_using_Bluetooth#Bluetooth_keyboards_which_doesn.27t_support_HID:_tested_a_keyboard

On that page you are hinting about getting this keyboard to work. Is it possible to post more details on what you do to get to the situation you describe? So far I have done the following (reading from http://wiki.openmoko.org/wiki/Manually_using_Bluetooth):

i switch on my keyboard with SPP, as you posted it would work with.

then on the moko

root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset
root@om-gta02:~# hciconfig
hci0:	Type: USB
	BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:0 acl:0 sco:0 commands:0 errors:0
root@om-gta02:~# hciconfig hci0 up
root@om-gta02:~# hcitool scan
Scanning ...
	00:0B:0D:FF:FF:FF	FREEDOM KEYBOARD

root@om-gta02:~# modprobe uinput
root@om-gta02:~# hidd --connect 00:0B:0D:FF:FF:FF
Can't create HID control channel: Connection reset by peer

Can you shed some light on this sequence? And possibly reveal the details of the script you are the only to use?

Bye,--Ivo 22:19, 5 January 2009 (UTC) Ivo

> Just to add to this info: I have not followed the unlock sequence offered through http://www.freedominput.com/unlock.html. I don't know if this really matters, but since I don't own compatible hardware (i have just the moko) i cannot get an unlock code :/

Sorry for late reply, but I do not watch my personal page. You should ether reply exactly where I wrote or use my discussion page. Using "SPP" you do not need any "hci*" commands. "rfcomm connect 0". If you send me an email I can sent you the python code. But I can not test it at the moment because I have no working distribution on my phone.--plaicy 21:12, 23 August 2009 (UTC)
Personal tools

Universal Keyboard Hacking

Using the om2008.12 release + a fresh freedom keyboard (i do not possess any of the working smartphones as of date). It is a no-go at the moment. I saw your recent comment on http://wiki.openmoko.org/wiki/Talk:Manually_using_Bluetooth#Bluetooth_keyboards_which_doesn.27t_support_HID:_tested_a_keyboard

On that page you are hinting about getting this keyboard to work. Is it possible to post more details on what you do to get to the situation you describe? So far I have done the following (reading from http://wiki.openmoko.org/wiki/Manually_using_Bluetooth):

i switch on my keyboard with SPP, as you posted it would work with.

then on the moko

root@om-gta02:~# echo 1 > /sys/bus/platform/devices/neo1973-pm-bt.0/power_on
root@om-gta02:~# echo 0 > /sys/bus/platform/devices/neo1973-pm-bt.0/reset
root@om-gta02:~# hciconfig
hci0:	Type: USB
	BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:0 acl:0 sco:0 commands:0 errors:0
root@om-gta02:~# hciconfig hci0 up
root@om-gta02:~# hcitool scan
Scanning ...
	00:0B:0D:FF:FF:FF	FREEDOM KEYBOARD

root@om-gta02:~# modprobe uinput
root@om-gta02:~# hidd --connect 00:0B:0D:FF:FF:FF
Can't create HID control channel: Connection reset by peer

Can you shed some light on this sequence? And possibly reveal the details of the script you are the only to use?

Bye,--Ivo 22:19, 5 January 2009 (UTC) Ivo

> Just to add to this info: I have not followed the unlock sequence offered through http://www.freedominput.com/unlock.html. I don't know if this really matters, but since I don't own compatible hardware (i have just the moko) i cannot get an unlock code :/