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://chaosradio.ccc.de/ . A recent thread on www.tlug.de (thanks Nils Dettenbach and others) made me regard the e90, and nokia even lets me install software, unlike other popular phones.
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.
rfcomm connect 0 <bt-address> 2 # This starts the connection - the pin is now requested on the e90. You can now on the # nokia e90 'authorize' the connection to be established without requesting the pin each time. I guess its just # protected by the bluetooth-address of the device. emacs /etc/bluetooth/rfcomm.conf # an entry for rfcomm0 gets created so accesses trigger the connectionin future
Now run 'minicom' and configure /dev/rfcomm0 as serial line. Talk to the e90 executing 'ATZ' resets, 'AT+CGDCONT=1,,"internet.t-mobile"' and 'ATD*99***1#' should produce no errors and will result in a ppp-connection. If that works stop minicom. An Example-session:
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,"IP",,,0,0 OK AT+CGDCONT=1,"IP","internet.t-mobile" OK ATD*99***1# CONNECT ~ÿ}#À!}!} } }
cat >/etc/ppp/chat_nokia_e90 <<EOT ABORT ERROR '' AT OK ATZ OK AT+CGDCONT=1,"IP","internet.t-mobile" 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->settings->connection->Access points->ISP-internet-entry->Access point name
cat >/etc/ppp/peers/tmobilestart_nokia_e90 <<EOT noauth connect "/usr/sbin/chat -v -f /etc/ppp/chat_nokia_e90" debug /dev/rfcomm0 230400 defaultroute usepeerdns noipdefault crtscts noccp ipcp-accept-remote ipcp-accept-local EOT tail -f /var/log/messages & # lets look at the logfile pon tmobilestart_nokia_e90 # and lets dial in
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/sec. Dunno what the bottleneck is there, i/o to the memory is it not (becaus e usb-transfer is faster), its also not the bluetooth-throughput (because internet-usage from a pc via bluetooth is faster).
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.
$> obexftp -b 00:1A:89:C1:21:A6 -l # this looks for a channel on your device providing obex-services. Example Browsing 00:1A:89:C1:21:A6 ... Channel: 11 Connecting...done Receiving "(null)"... <?xml version="1.0"?> <!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd" [ <!ATTLIST folder mem-type CDATA #IMPLIED> <!ATTLIST folder label CDATA #IMPLIED> ]> <folder-listing version="1.0"> <folder name="C:" user-perm="R" mem-type="DEV" label="Phone memory"/> <folder name="E:" user-perm="RW" mem-type="MMC" label="NO NAME"/> </folder-listing>done Disconnecting...done # Channel 11 was chosen. 'sdptool browse <bt>' did show the servicename 'OBEX File Transfer' for this channel. # So we have directories C: and E: here. We can traverse those step by step $> obexftp -b 00:1A:89:C1:21:A6 -l C:/ [...] <folder name="DATA" modified="20070628T110514Z" user-perm="RW" mem-type="DEV"/> [...] $> obexftp -b 00:1A:89:C1:21:A6 -l C:/DATA/ [...] <folder name="Activenotes" modified="20071211T220908Z" user-perm="RWD" mem-type="DEV"/> <folder name="Documents" modified="20071211T220558Z" user-perm="RW" mem-type="DEV" label="Documents"/> <folder name="Games" modified="20070612T000002Z" user-perm="RW" mem-type="DEV" label="Games"/> [...]