With Pushover being recently added to ifttt as a recipe option, I’ve been sending notifications to my phone for all those time-sensitive throwaway messages that I’d otherwise have used email for. If tomorrow’s forecast is particularly warm, it’s going to rain, or if Team GB win an medal at the Olympics.
Posts Tagged ‘mobile’
Two months ago, I had no use for Twitter. Now it seems it’s everywhere, on everything and no device can survive without that talkative little bird. So I thought I’d gather together all the different applications I’ve managed to dig out and install so far.
- TwitterFeed – Update Twitter automatically from this blog – both the posts and currently reading RSS feeds.
- Twit4Live (MSN Live Messenger Plus!) – Update your status from within any messenger chat window with /twitter <tweet>.
- rss2psm Nutz (MSN Live Messenger Plus!) – A slightly modified version of this script updates my MSN Personal Message whenever I post to Twitter.
- Twitula (Windows Mobile enabled iPAQ 4150)
- Shozu (Symbian Nokia N95)
- Twitux (GNOME Linux / Ebuntu Eee PC 701)
- TwitterFox (Firefox) – Update and view status from within the browser.
- RSS2IMAP – My RSS feed reader of choice, read the Twitter RSS and convert into emails, for viewing in Thunderbird.
- Facebook Twitter – Updates my Facebook status whenever I post to twitter (from anywhere).
- BeTwittered (iGoogle)
And because of all of this, I never need to visit twitter.com any more. That’s progress 🙂
Setting up the Internet on the Eee PC over bluetooth to my Nokia N95 with T-Mobile GPRS/EDGE/3G connection can be tricky. Yet it sounds like one of those setups that could be so easy, right? Well it seems stable for the moment, so here’s what you’ll need. Or rather, what I have…
- Eee PC 701
- Nokia N95
- Bluetooth dongle
- Ubuntu Eee installed on the 701 (not Xandros – although check out these scripts if you don’t want to change)
- T-Mobile UK contract with included data plan (preferably). And Internet already working on the phone.
You’re going to be setting up your connection though pppd, and all of these instructions are based on instructions that I’m going to steal, slightly change and probably skip parts to suit my purposes (and hopefully yours) perfectly.
If your set-up doesn’t match exactly, perhaps you can make use of both pages and work out where things should change. Or lovingly rip these instructions off, as I did – to make your own.
Setup your bluetooth dongle
First off, you’re going to need an apt repository that has the bluez-utils packages in. So open up a terminal
sudo nano /etc/apt/sources.list
and add the line
deb http://ftp.de.debian.org/debian etch main
Then you can install the package.
apt-get install bluez-utils
lsusb | grep -i bluetooth
(should show the bluetooth device)
(also lists bluetooth devices)
You can grab my gprs-settings which should be put into /etc/ppp/peers directory, and untarred.
tar -xvf gprs-settings.tar
Pair the phone
First, get the bluetooth ID of the N95
Then pair your Eee with your phone, you have to do this from the N95.
Bluetooth -> right arrow (Paired devices) - Options
New paired devices (search)
Choose your eee and then type the pairing keys (anything of your choosing
Bind bluetooth to an rfcomm device
We use “rfcomm” to bind the bluetooth connection to a device. So first, find out the channel the phones bluetooth dial up networking system is on. You can do this with sdptool (Service Discovery Protocol tool):
sdptool search dun
Service Name: Dial-Up Networking
Service RecHandle: 0x1001e
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
Language Base Attr List:
Profile Descriptor List:
"Dialup Networking" (0x1103)
Note the “Channel: 2” which show which channel to bind.
Then to bind the channel (in this case #2) to one of the rfcomm devices (for example, rfcomm0):
rfcomm bind 0 11:22:BE:EF:44:33 2
You can see the binding with:
rfcomm0: 11:22:BE:EF:44:33 channel 2 clean
You might find you need to reset the bind and restart it every now and then (especially failed connection attempts)
rfcomm release 0
rfcomm bind 0 11:22:BE:EF:44:33 2
You can edit the settings in “/etc/bluetooth/rfcomm.conf,” set bind to “yes” and give the device and channel for rfcomm0. Then you can put these commands into /etc/init.d/bluetooth and it will automatically bind and release the rfcomm device:
# At the end of the "start)" section
rfcomm bind all
# At the beginning of the "stop)" section
rfcomm release all
Start pppd to connect.
Start up pppd. Command line first, but because we’ve called it ppp0, you will later be able to do this via the normal ubuntu eee networking menu in the menu bar.
% pppd call ppp0
You should now have a ppp0 interface in your ‘ifconfig’ output that is up and running. The output should look something like this:
# pppd call ppp0
Press CTRL-C to close the connection at any stage!
defining PDP context...
waiting for connect...
If the following ppp negotiations fail,
try restarting the phone.
Serial connection established.
using channel 1
Using interface ppp0
Connect: ppp0 <--> /dev/rfcomm0
You can hit control-c on the pppd process and it will shut down the connection, then you can release the rfcomm binding.
So… as I was saying… It’s not the easiest thing in the world to get going, but once you’ve got the hang of it, and set it up once you’ll have a connection everywhere you go.
I recently bought myself an Asus Eee 701 4G Surf from Expansys for the bargain price of 169.33 including delivery. If you don’t know about these tiny laptops, they’re low-spec, cheap machines often times running a Debian-based Linux installation called Xandros, rather than Windows (although XP versions are also available in the higher spec versions). Its key specs are a 7-inch screen, 512MB of RAM (upgradeable to 2GB), built-in WiFi and hard wired ethernet ports, 4GB solid-state drive, weighing only 922g, and really really small.
For those of you that just about nodded off to sleep – it’s really light, really small (for a feature-packed laptop, I mean), and lets you use word processing, spreadsheets, browse the Internet, read emails, blogging, instant messenger, Skype and, well – just about everything you’d normally do on your laptop really. Except… did I mention it’s really portable?
I’m not totally sure where it fits into my technology arsenal yet. It’s certainly not a desktop replacement, and it might even be best described as a second-laptop (the first of which, I hasten to add, spends way more time charging than it ever does getting used). But the Eee PC is certainly a lot easier to carry around, and more likely to be dropped into my rucksuck as an afterthought since it takes up so little space.
It’s also been described as “something to play with” and the Eee fits into this category just as well as it would as a solid dependable netbook (if you’d rather leave the endless tinkering alone). Perhaps it’s because the device is so cheap, or easy to reinstall the base system with all your essential apps in tact (take that Microsoft) – but even if you’re just looking for an alternative to Windows, the Eee might just be a good place to start.
So, expect more posts about the Eee shortly – the usual technical-guides are going to help me rebuild the system if I do manage to break it – as well as give me an excuse for something to write about 😉
There is no end to this phones capabilities, it seems – so this evening I’ve had my trusty Nokia N95 working as a wireless bluetooth webcam and sending real-time videos across MSN.
* You have invited Alison to start viewing webcam. Please wait for a response or Cancel (Alt+Q) the pending invitation.
Alison says (22:21):
you doing something kinky?
I’m not sure where I got this undeserved reputation from, personally. But anyway, if you’d like to try this yourself, it’s compatible with all kinds of Symbian S60 phones, so head over to motvik’s web site and download wwigo. It’s free, and it’s cool – what else could you ask for?