actually, i found out that the ussp-push i got is already patched. and its working.
and now im trying
http://www.holtmann.org/linux/bluetooth/rfcomm.html
well, downloaded the script for generating ttyU , loaded the modules,
now when im running root@gentoo bluetooth # rfcomm 0 00:60:57:76

D:5E 10
i'd get
RFCOMM configuration utility ver 2.3
Usage:
rfcomm [options] <command> <dev>
and the rest of the help menu.
if i do this ...
root@gentoo bluetooth # rfcomm connect 00:60:57:76

D:5E 10
Can't connect RFCOMM socket: Host is down
and the output of hcitool browse is.
sdptool browse 00:60:57:76

D:5E
Browsing 00:60:57:76

D:5E ...
Service Name: Fax
Service RecHandle: 0x10000
Service Class ID List:
"Fax" (0x1111)
"Generic Telephony" (0x1204)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Fax" (0x1111)
Version: 0x0100
Service Name: Dial-up Networking
Service RecHandle: 0x10001
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: OBEX File Transfer
Service RecHandle: 0x10002
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 10
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100
Service Name: Bluetooth Serial Port
Service RecHandle: 0x10003
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Service Name: Handsfree Audio Gateway
Service RecHandle: 0x10004
Service Class ID List:
"" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x111e)
Version: 0x0100
Service Name: OBEX Object Push
Service RecHandle: 0x10005
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 9
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
which means its working, specially when i do
root@gentoo bluetooth # hcitool scan
Scanning ...
00:60:57:76

D:5E MeanGuy
---------
incase u're wondering. the ussp-push error is
root@gentoo bluetooth # ./ussp-push /dev/ttyU0 ussp-push ussp-push
pushing file ussp-push
name=ussp-push, size=16447
Registered transport
set user data
created new objext
Can' t open tty: No such device
Link broken!
started a new request
Error while doing OBEX_HandleInput()
Connection return code: -1, id: 0
Can' t open tty: No such device
Link broken!
Error while doing OBEX_HandleInput()unable to connect to the server
--- i can also ping the phone
root@gentoo bluetooth # l2ping 00:60:57:76

D:5E
Ping: 00:60:57:76

D:5E from 00:10

C:E9:5E:3D (data size 20) ...
0 bytes from 00:60:57:76

D:5E id 200 time 34.70ms
0 bytes from 00:60:57:76

D:5E id 201 time 30.79ms
2 sent, 2 received, 0% loss
-----------
it seems like a permission problem.
if anyone can help i'd appreciate it. i think i'll post something in gentoo forum, incase i get lucky ;/
im still looking though.