This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
hardwarerelated:nokia_e90 [2018/06/10 02:17] chris |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Nokia e90 communicator for an admin ===== | ||
- | Provides ssh and vnc. Nice features like gps, wlan, sip. My hints here are focused on getting the e90 to fill my admin-needs. I want to listen to the podcasts from http:// | ||
- | === applications === | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | |||
- | === applications:: | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | * http:// | ||
- | |||
- | ===== internet-access from linux-pc via bluetooth ===== | ||
- | I want to access the internet using the nokia e90 via bluetooth from a thinkpad running linux Debian unstable. Kernel with the bluetooth-parts at least as modules is required. The part for pin-authentication uses dbus now as backend, this was sdp-daemon bevore. | ||
- | |||
- | |||
- | ===== first time setup ===== | ||
- | === first steps === | ||
- | - apt-get install bluez-utils pkg-config libdbus-1-dev minicom | ||
- | - now activate bluetooth if needed, pressing < | ||
- | - hciconfig hci0 up | ||
- | - killall hcid # stops the running hcid | ||
- | - hcid -nds # execute | ||
- | - hciconfig -a # should show informations on your computers bluetooth-adapter now | ||
- | - hcitool scan # now searches for bt-devices. If the nokia e90 is appropriately configured it can be seen here | ||
- | - l2ping < | ||
- | - sdptool browse | ||
- | - sdptool search DUN # this searches for the DialUpNetworking service, should be ' | ||
- | - Now we need an agent for the pin-handling, | ||
- | * cd / | ||
- | * %%zcat passkey-agent.c.gz > | ||
- | * make # build the passkey-agent | ||
- | * mv passkey-agent / | ||
- | * %%/ | ||
- | |||
- | === serial connection over bluetooth === | ||
- | < | ||
- | rfcomm connect 0 < | ||
- | # nokia e90 ' | ||
- | # protected by the bluetooth-address of the device. | ||
- | |||
- | emacs / | ||
- | </ | ||
- | |||
- | === minicom session === | ||
- | Now run ' | ||
- | < | ||
- | Press CTRL-A Z for help on special keys | ||
- | |||
- | AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0 | ||
- | OK | ||
- | ATZ | ||
- | OK | ||
- | AT+CGDCONT? | ||
- | +CGDCONT: 1," | ||
- | |||
- | OK | ||
- | AT+CGDCONT=1," | ||
- | OK | ||
- | ATD*99***1# | ||
- | CONNECT | ||
- | ~ÿ}#À!}!} } } | ||
- | </ | ||
- | * http:// | ||
- | |||
- | === the chatfile === | ||
- | < | ||
- | cat >/ | ||
- | ABORT ERROR | ||
- | '' | ||
- | OK ATZ | ||
- | OK AT+CGDCONT=1," | ||
- | OK ATD*99***1# | ||
- | CONNECT '' | ||
- | EOT | ||
- | # for other ISP than t-mobile you have to replace internet.t-mobile with the value from the e90 menu | ||
- | # tools-> | ||
- | </ | ||
- | |||
- | === the ppp-configfile === | ||
- | < | ||
- | cat >/ | ||
- | noauth | ||
- | connect "/ | ||
- | debug | ||
- | / | ||
- | 230400 | ||
- | defaultroute | ||
- | usepeerdns | ||
- | noipdefault | ||
- | crtscts | ||
- | noccp | ||
- | ipcp-accept-remote | ||
- | ipcp-accept-local | ||
- | EOT | ||
- | |||
- | tail -f / | ||
- | pon tmobilestart_nokia_e90 | ||
- | </ | ||
- | |||
- | ===== daily usage ===== | ||
- | * Enable bluetooth on the e90, ' | ||
- | * Any access to / | ||
- | |||
- | ====== obexfs ===== | ||
- | === What is it? Alternatives? | ||
- | This provides access to the nokia e90 memory using the obex protocoll. The memory is mounted like a usual filesystem. Bandwith when accessing via bluetooth is 23kbyte/ | ||
- | |||
- | Accessing the e90 via wlan with opexftp (-n option) didnt succeed here, apparently the obex-service is only provided via bluetooth and maybe irda. Using the usb-cable and mounting the e90 as usb-storage-device is the fastest way. | ||
- | |||
- | === installing and finding the obex-channel === | ||
- | - compile a kernel with CONFIG_FUSE_FS as module or build in | ||
- | - modprobe fuse | ||
- | - apt-get install obexfs obexftp # or get, compile and install it from http:// | ||
- | - activate bluetooth on the e90 | ||
- | - hcitool inq # scan for the e90, get the bluetooth-address | ||
- | - sdptool browse 00: | ||
- | |||
- | === testing with obexftp === | ||
- | < | ||
- | $> obexftp -b 00: | ||
- | Browsing 00: | ||
- | Channel: 11 | ||
- | Connecting...done | ||
- | Receiving " | ||
- | < | ||
- | [ < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | Disconnecting...done | ||
- | |||
- | # Channel 11 was chosen. ' | ||
- | |||
- | # So we have directories C: and E: here. We can traverse those step by step | ||
- | $> obexftp -b 00: | ||
- | [...] | ||
- | < | ||
- | [...] | ||
- | $> obexftp -b 00: | ||
- | [...] | ||
- | < | ||
- | < | ||
- | < | ||
- | [...] | ||
- | </ | ||
- | |||
- | === mounting the obex-filesystem === | ||
- | - mkdir /mnt/e90 # create mountpoint | ||
- | - obexfs -b 00: | ||
- | - obexfs -b 00: | ||
- | - fusermount -u /mnt/e90 # use this for umounting | ||
- | - extension for automounter is possible ofcourse | ||
- | |||
- | === links === | ||
- | * http:// | ||
- | * http:// |