Archive for the ‘Nokia E61’ Category

SymTorrent - Symbian BitTorrent Client

Thursday, October 26th, 2006

Symbian Freak posted about the Symbian based BitTorrent client, and I tried it out on my E61. I only tried a relatively small test, about 80 megabyte download, only one running at a time. Didn’t open up ports in the firewall to allow for outbound connections as well. But my download came through fine and ran pretty quickly over wifi. Great, and it’s open source, fantastic. One thing missing from the article is the project page however. I did a few searches on Google and SourceForge and Freshmeat, nothing. Anyone know where the project is hosted? I would love to take a look at it.

Death by 1000 Needless Clicks

Friday, August 18th, 2006

I’m installing the recently released 3rd edition port of Apache for S60 on my E61 and I’m struck by how cumbersome and useless this signing process is. The actual web server install seems to be a few executables packed into one SIS, 5 or 6 of them, I lost count. Looks like 8 according to the app manager install log. Wow! So for each one I have to not only confirm that I want to install it, what the version is … for some reason, that’s it’s “dangerous” and I know that, and a list of things each app wants to do to my phone. It was something like 4 clicks per part installed, times the 8 things. Insane. Fortunately I was waiting for another download, so I didn’t wander away before I got too bored. It was a close call though. So someone remind me again, how did that just make my phone more secure?

E61 HTTP Proxy

Wednesday, August 16th, 2006

I could have sworn at one point I saw a SOCKS proxy set of settings in either my E61 or on the 6680, but looking all around in the browser and searching online I didn’t find anything. I had pretty much given up on the idea. And then one thing let to another another, and next thing I know I’m reconfiguring Madgat at 2 in the morning instead of sleeping like I should be. And in the process of poking around with various APN settings and trying to figure out how the gateways are passing along requests and how exactly would RADIUS be supported at the gateway and how can I get that info passed to me? I stumble upon the “Advanced Settings” for an APN on the E61.

“What Proxy is this?” I think to myself. Is it a WAP gateway? Maybe it’s another form of APN control point. So I do the obvious thing: login to my public server, fire up netcat, point the proxy to that server and port, and start poking around. Login to IM and nothing shows up on the netcat. So instead I try the browser, and sure enough there comes the proxy request. Fantastic!! Not what I was looking for to begin with, but something I was hoping to find. A few minutes later I have tinyproxy up and running to make sure that everything actually works, both with the KHTML browser and the WAP Services browser. About 20 minutes and one PEAR HTTP_Server package install later and I have the transcoder hooked up to an HTTP processor and I’m transcoding requests to my phone transparently. Now that definitely deserves a w00t!

E61 and Gizmo Project

Thursday, August 10th, 2006

For those familiar with the E61 and SIP, you’ve probably heard about the NAT traversal problem and you’re wondering if you can deal with not having your phone for a while as you get the firmware reflashed once it does. The E61’s SIP implementation is meant to be used with the phone sitting on the same network as the VOIP server, on your corporate network. Unfortunately I don’t have a corporate network. Or, more accurately, my corporate network is actually a rogue access point sitting on someone else’s network. And I’m not running my own SIP server on it.

So imagine my surprize when Russ mailed me a pointer to instructions for getting the E61 working with the Gizmo Project servers. It didn’t work two weeks ago from what we know, but apparently Gizmo had made some changes on the server side that allow the built in SIP support in the E61 to connect. Fantastic!! I just used it to make a call (direct from the contacts app in my phone, w00t!) over my rogue access point to a coworkers mobile using the Gizmo call out. Aww yea. Now if only I could connect to access points without the browser on the E61 crashing…

A Day on the Road with the E61

Monday, July 24th, 2006

I’ve been using the E61 for only a short while. I got it Friday evening, so today is my first work day with the device. A few problems have cropped up, which I’m putting up in the interest of either finding workarounds or emerging for future firmware patches. A lot of them seem to be application level issues, or perhaps drivers. The network handling in particular seems a bit suspect.

The access point groups just don’t work out very well because switching networks doesn’t work well. Take the messenger app for example, which seems to have some real drastic issues when used for email. I had configured it to use an access point point group that included my home wifi and the access point for my cellular provider. When I walked out of my apartment this morning and my phone beeped to tell me it lost the connection to the wifi that was fine, I had it configured to notify me of status changes. But when I got to the office half an hour later and it was just continually popping up “messenger error” when I tried to open my Inbox I knew something was up that shouldn’t be. I had to hold down the red hangup key till it specifically closed down the gprs connection completely, and then manually select the access point within messenger, and reconnect. And that was just the start.

I have spotty coverage at work, my packet connection will bounce while walking from one side of the office I work in to the other. The email portion of messenger doesn’t seem to handle this AT ALL. I set up messenger to use just the cellular connection, thinking it was the switching of access types that tripped it up. But for a few hours during the day it did the same thing it did before. Pulled a message or two down for email, and then my inbox was completely inaccessible (SMS inbox as well, messenger would not run at all). Eventually I disabled the email connection and put it in manual update mode, since which it’s been working fine. But given that this device seems to be aimed at the corporate crowd, for whom email is their lifeblood, I just can’t dismiss this poor implementation of basic email functionality. If you’re thinking “Hmm.. I was going to get a blackberry, but this E61 has wifi and should do the same thing” cut that thought off right there. The E61 is not up to snuff yet as far as email goes, full stop.

That said, for me fortunately email is not a deal breaker. I would like to have my emails pinging me and letting me know what’s up, but I have hackerish workarounds that I can use to replicate that kind of function without having the device do it. However, the dodgy WPA support within the wifi stack seems to be a bit more fundamental. It works, I can use the device at home with my WPA configured access point. However I’ve seen a bunch of crashes and odd odd hangs especially when working with a low signal level. Russ says he’s seen nothing of the sort, but is on WEP instead. I tried out using my neighbors unsecured network for a while, and wouldn’t you know, it certainly did behave a lot better. Now, I could switch my network to WEP. But as we all learned with the well documented revelation of encrypted packet replay using ARP packets WEP shouldn’t even provide the illusion of safety any more. This is really more of an issue for me, and is more of a black mark for me than the email issue even. And once again, if being positioned as a device for the corporate warrior this device needs to handle WPA without the slightest hiccup.

I’ve also had a few spurrious reboots when searching for networks. I was curious how using the device on a public network, say an access point at the ubiquitous Starbucks or other local coffee house would be. For the most part things work out fine. Say you’re at Starbucks and are looking for the tmobile hotspot, and you see it there with a signal strength of 95%.. no problem. If however you don’t know exactly what you’re connecting to, the process is frequently experimental. I admit this might be a bit “high tech environment”-centric, but the device does offer an automatic scan and status display for network availability, so I have to assume they’ve considered the use of random network hopping. It’s one of the reasons I wanted a wifi device that was handheld, so I could just hop on any random network if there happens to be one available and try it out.

The problem is, the E61 doesn’t seem to handle non-responses very well. Sometimes it takes trying a few seemingly open networks to find one that works. Maybe they’re doing MAC filtering even though security is off, maybe you picked up a few randomly reflected beacon packets from some AP you can’t really talk to. The 770 handles this great. Scan network and try it, scan again and try, no problem. The E61 however does not seem to like this usage, and I’ve had it spurriously reboot on me a few times when trying to connect to access points. It seems like there’s a low level watchdog timer sitting down in the OS that’s just too tight for the response time of the wifi drivers. It doesn’t feel like something drastically wrong, the OS just seems to get pulled over and the system cycles. When it does come back within time it’s not a problem, but that random reboot, total joykill. Especially if you’re randomly scanning access points cause some crisis just occured and you need to get online to check it out. Waiting through the seemingly infinite boot time is enough to get you to drop the device and pull out a laptop, and right there you’ve pretty much killed the value proposition of the device.

I’m hoping a lot of this stuff can be taken care of in firmware. The messenger problem, definitely, that’s gotta be some software mixup. And any time the operating system falls over and applications fail I always assume that’s a bug and not some fundamental design flaw. Even if it is a design flaw, patch over it so that at least the device doesn’t reboot. Fail, sure. But fail a bit more gracefully. Nothing like a busy work day to bring the honeymoon with your new device to an abrupt halt.