Ripping mobility from the clutches of telecom
Archive for June, 2005
Video From 6680 and Treo 650
Jun 17th
Here are two samples of video, one shot with the Nokia 6680 and the other with the Treo 650. Both are just shots of a few seconds of traffic out of the window at the office. The Nokia sample was shot with the back camera (the 1.3 megapixel one) using the built in camera application, which also takes videos:
The second is from the Treo, also using the default camera application, same subject, videos taken pretty much back to back:
If you would rather download the video directly:
Definitely very cool that the both of them record in 3gp format, it would be fantastic to have just one format to deal with for mobile produced content. One of the major improvements with the 6680 is that it will record video in arbitrary lengths now. The 6600 capped video at 10 seconds so that it could be sent via MMS, which made the system pretty much useless for video for me. The 6680 comes with a video editor even, I need to fool around with that. It would be fantastic to be able to video blog directly from a handset.
Picture Sets in Natural Light
Jun 16th
As I promised, here are some images from natural light while wandering over to the office today. First from the Treo:
And then from the VGA camera in the 6680:
And the 1.3 megapixel camera in the 6680:
The 1.3 megapixel camera definitely does rock when you’re outside or if there’s enough light. I’ll certainly swap my sim into it whenever I know I’m gonna be taking a bunch of photos, so I’ll at least have to pick up a couple of applications for use during those outings.
Treo 650 vs. 6680
Jun 16th
I recently did a very geeky post about the Treo650 and all the apps you can put on it. I’m gonna swing back the other way and do an ungeeky post this time. I recently became the proud new owner of a Nokia 6680, and I’ve decided to do a head to head comparison of the two units. But instead of doing a really deep dive into the details, I’m just gonna skim and try to provide tips for those of you thinking something along the lines of “I want a spankin new high tech phone, but I’m not quite sure which one to get”. Russ provided his overview of the 6680 and the apps he runs. I’m just gonna talk about the plain out of the box systems. First, of course, we need a bit of the basic info. Each of the photos below links to a much much larger version if you want to check out some of the details. Much larger, you’ve been warned.
The two devices are about the same size. The 650 is a bit larger in terms of height and width, but definitely thicker. The real clincher is the external antenna on the 650. If you lopped off the antenna on the 650 I would be comfortable saying the devices are about the same size and leave it at that. With the antenna I have to say that the 650 is the larger device. And the 6680 definitely weighs much less than the 650. I’m normally not all that weight sensitive, but the difference was obvious. Of course the screen on the 650 is much larger, so it’s not like that weight is just extra fat.
Lets start out with the basic interface. Major differences are the touchscreen and PC style keyboard on the 650. The Treo derives from the Palm line of PDAs, so it has a stylus. That’s the little fake pen that you use to tap on things on the screen to get things done. Some people love it, some people start foaming at the mouth and spouting obscenities when you talk about pen based interfaces. So depending on which camp you fall into that could be a mark for or against the Treo, I leave that up to you to decide. One additional point I will make is that the Treo really requires a screen protector if you’re going to be keeping it around for a while. This has been an issue with all the PDAs down since the beginning of time, if you don’t want to scratch up the glass of your screen you really need to use one. And the protector detracts from the visual clarity of the screen. The 6680 doesn’t have a touch screen, so they can put nice hard plastic over the screen and you don’t have to worry about it. I’ve been using the screen protector that came in the box with my Treo and it has worked out well, I don’t really mind the bit of blurring caused by the extra layer of plastic. Then there’s the keyboard. I think it’s quite well done on the Treo actually. I expected the keyboard to be very cramped and difficult to use, but it hasn’t been. I suspect if you had fingers too much larger than my own it would start to get difficult. However the shape of the keys and the way that they’re rounded makes for pretty easy typing. There’s also the resolution of the screen itself, the Treo really blows away the 6680 here. I actually use the PIM features in my phones, the calendar in particular. Unfortunately I have way more to do than my tiny little brain can keep track of, so I let my devices do that for me. Although the screen seems somewhat equivalent when navigating the home screens on the different devices, that’s just because the design of the icons and the screen is much better on the Nokia. Taking a look at something like the calendar really shows how much more you can get on the Treo screen:
The Treo can display the whole calendar and even show approximately what time during the days I have appointments when in month view. The 6680 can show me which days have appointments by marking the corner of the day. Also, I apparently can’t sync the 6680 with my Mac. Perhaps not even with addon software. To be fair, I had to get addon software to sync the Treo, so I need to do some looking around to find what I can do with the 6680. Maybe I can weasel the Treo version of the Funambol conduits out of someone, cause the 6680 does work with that. My poor poor data. I’m told it wants to be free, but every device I have seems to be bent on information subjugation.
Next up is the web browser. Wow. I guess I didn’t really appreciate how primitive the Nokia browser seems compared to Blazer until I had both devices in front of me. Part of it derives from the screen resolution I’m sure, there’s a ridiculously small amount of text on the 6680 screen compared to the Treo. But the reformatting of pages in general to fit the screen also seems to work better on the Treo. My standard test is using Bloglines mobile to check on some feeds. The Nokia browser gets all thrown off by elements that it’s not able to render down into the right size. Say you have a forms table that it can’t shrink enough, the entire post wraps to the width of that table, and you end up scrolling side to side in order to view anything. Blazer deals with that no problem, leaving the table larger than it wants to, but wrapping the post at the right length. It’ll even only show the horizontal scrollbar when the oversize table is onscreen. Not too shabby.
There are a zillion things to talk about still, but I have to go to sleep soon so I can head off to the day job tomorrow. So I’m just gonna leave you with some shots from the cameras. I expected the 6680 to really shine here. It has two cameras, one VGA resolution and the other 1.3 megapixels. The 6680 has a flash as well. The Treo has just a VGA resolution camera and no flash. Here are the images as a set:
- 6680 VGA resolution camera
- 6680 1.3 megapixel no flash
- 6680 1.3 megapixel with flash
- Treo 650 VGA camera
These are all indoor pics, so it is biased. But for the indoor set I think the Treo did fantastic. The details of the images come through better, although the color is definitely washed out. And the size is much better on the Treo. The VGA image from the Treo is 88k, while the VGA image from the 6680 is 176k. Ouch. Moving that much data around, no wonder the Nokia folks had to invent another memory card format to conserve battery power ;-) To be really fair though, I’ll have to snap some outdoor pics as well and see how they compare. Hopefully I can get those up soon.
I was expecting this race to be neck and neck. I’m really liking the multithreaded core of Symbian and the button driven interface. But you only get one chance to make a first impression. And I think the first impression is that the Treo is going to spend a lot more time in my pocket. Maybe I’ll get pissed of it crashing on me all the time (it does) and turning off the phone for no particular reason (something else it does) or the terrible battery life it gets (about 20% battery charge remaining after a day of moderate use). That could certainly drive me back to the 6680 and see what I can get working there. But I’m not sure I’m ready to drop all the coin necessary to fully trick out the thing. A lot of the aps on that list top $20. 5 apps and I’ve spent another hundred dollars. Ouch. Maybe a crash every now and again isn’t that bad by comparison.
Vagablog Released as Open Source
Jun 9th
I won the Treo 650 in the raffle at Palm DevCon a few weeks ago. I’ve also been bitching to folks at Palm about how they need to do a better job seeding their developer community. Not serving, seeding. There definitely is a difference. So of course I needed a way to show how a good toy in the hands of the right person could potentially make a difference. There were a bunch of people blogging the event with software that cost $25 per copy. Lightbulb over the head, halo of light, cue the organ music. That seemed like the logical place to start! Especially given that I had blogging software of my own to start out with. For a while (since 2003) I’ve been selling a simple Palm blogging app through online stores for a few dollars a copy. It wasn’t making me any money anyway, and I think a good blogging app for the 650 would really kick some ass. Something people could hack on and extend and come up with novel usages for. I figured I would toss my hat into the ring and release a free version of Vagablog along with the source code. There’s another tool out there called Plogit, maybe we can merge in some of that stuff. I’m assuming I don’t even have to really mention the really obvious stuff, like getting Vagablog to download pasts posts and store them in a local DB or getting it to support image uploads. I’m more interested in the not obvious stuff like audio and video blogging, scheduled uploading, calls to a service like the AJAX spell checker or other server side checker, or extending forms to allow mixing in microformats when posting.
Mobile Monday Meeting in New York
Jun 2nd
I just got this message from Dan Melinger:
Hello all you NYC-area lurkers out there.
This coming Monday at d.b.a. (wifi and a garden, what more could you want?) we will be holding what I believe is the first NYC Mobile Monday. It will be a casual affair with the lofty objective of planning the future of MoMo NYC. No speakers are lined up. Just come if you’re interested in meeting others from our community and in planning for the future of our new group.
6 June
d.b.a. – http://www.drinkgoodstuff.com/ny/
41 1st Ave (b/t 2nd and 3rd)
7pmPlease forward this message to anyone who might be interested…
And please join the mailing list -
http://groups-beta.google.com/group/MoMo-NYCBest,
Dan|| Dan Melinger
|| kamida :: creators of socialight|| email dan at socialightdotnet
|| cell +1 917 494 5856
|| web socialight.net
There have been meetings by a group called Mobile Media Monday meeting out in New York, but that group is unrelated to Mobile Monday as a whole. Kinda odd choice of naming on their part, but M^3 is a nice abbreviation to be able to use. And when Russ and I started using the name we were squatting cause we thought the name was abandoned, I can’t fault anyone else for picking it up as well. Unfortunately they’re not following through on the same vision, and I just hope that isn’t too confusing. On the other hand, Dan is related to the Mobile Monday events in Finland and here in the Silicon Valley, and is looking to create an open community meeting for the mobile industry. Good luck to Dan and the rest of the NY folks!


