14 July 2006
I've been using bluetooth for its mobile data networking since about the time of its death, and I really was concerned for a bit -- there weren't many bluetooth phones from which to choose, and the ones that did exist were considerably more expensive. Today, it's much more common, since everyone wants the wireless hands-free kit. My next car will probably have bluetooth as well.
I'm very pleased that the personal-area-network has finally become useful for the normal people. Now I just hope that the manufacturers don't let the data side of the devices slip in favor of only supporting voice services, like some errant carriers try to do.
08 May 2006
Opera Mini 2.0 is out, and it works pretty nicely on my S710a. It looked good on Doug's T616 as well. It's contending with Google Local for Mobile as my favorite application on my phone.
The user interface has improved a bit -- the scrolling page history thing is just interesting, but the ability to fire off the platform web browser to download and save files is very welcome.
13 January 2006
I've been programming a MIDlet for my phone, and I wanted to make sure I'm following some sort of design standard beyond just cobbling it together from the API docs, so I wandered out to my local Borders Book Store last night. I found no Java ME (J2ME) books anywhere. In fact, their computer section has been shrinking for a while.
I find this hard to believe when I've seen a few of these books coming up on publishers' new release lists. I also take Google's own Google Local Mobile MIDlet to be a sign that Java ME really is about to come of age.
Since I was mostly searching for an impulse buy, I'm not going to bother ordering anything online or running out to Ollie's Outlet to buy old bargain-bin books about MIDP 1.0 just yet. It looks like Sun and others have a pretty good set of Java ME articles which should get me to the next level nicely. The wireless blueprint program looks like it may be exactly what I need at this point.
20 September 2005
After almost no time spent obsessing over the SonyEricsson S710a, I've found occassion to buy the thing -- Claire broke her phone, so we had to head off to the local Cingular store for a couple new phones and contracts.
I justified the paying the $200 (after rebate) by telling myself it's my only device -- I carry this in place of a camera, PDA, gameboy, media player, whatever.
It's been pretty slick so far, and the feature lists available on all the other websites represent all the good things about the device. Since there are so many positive things about the phone, I may just focus more on some of the negative surprises here.
The camera is pretty decent, and it has lots of configurations. It sets EXIF data on the images, so I can more easily tell when I took the picture and it even the figures out the orientation (horizontal or vertical) of the photo, so it can be automatically rotated on the PC.
When viewing photos, there's a More->Use->Rotate option which seems to only rotate the display of the image locally. If you send this picture off, it'll still be in its original (sideways) orientation. For images 320x240 or smaller, there's an Edit option which has its own Rotate tool to permanently rotate an image. Larger images can not be rotated permanently on the phone. That's sort of disappointing, since I'll need to always take upright pictures to send off to the moblog or take them smaller. I had hoped to write a little plugin or something to get Blojsom to thumbnail and link the large images for me. Maybe I'll need to figure out how to rotate the image as well according to the EXIF orientation data.
From within the camera function, there is a Send button as soon as you snap a picture. This option initially presented me with options to Send via MMS or Send to Kodak Mobile -- there's no Send via Email. Playing with the Message->Settings->Web Storage options, I managed to add and select my own Web Storage with my moblog email address. This made my custom option available in the camera's Send option. Trying it, I found that the message got sent in such a way that Blojsom didn't quite handle it correctly (dropped the JPG extension and formed a broken link), and it came from email@example.com -- it went out as an MMS, not normal email. I ended up having to just drop back and send it explicitly attached to an email from the built-in email client, not from the camera.
This brings me to the messaging options. AT&T Wireless gave me a little mMode account with email which I conveniently dedicated to my phone. Cingular doesn't do this, so I needed to create a mobile email address for myself -- I don't like having this thing hooked up to my primary email account all the time. In all the default accounts, the Outgoing Mail server is set to
cwmx.net, so I kept that for mine. Since the email client insists on authenticating against an incoming server somewhere (even though it's unrelated to the outgoing server), I needed to set up my incoming account before I could email any pictures.
I've found that I can send:
That's a whole lot of messaging options. Additionally, there are IM networks which I don't intend to actually use. Maybe I'll load a Jabber Java midlet someday.
The default internet configuration for the phone's browser used HTTP through a proxy instead of WAP through a gateway. It may have been the HTTP proxy or something, but the browser seemed very slow and unreliable. I'd often get failures trying to load some MediaNet pages, and my bank's mobile access just rendered blankly. Switching to the WAP settings (found in Cingular's knowledge-base) work much more reliably, and communicate properly with my bank. Rendering seems to be the same for most my normal websites with either configuration.
Once I got tethering setup (which took a bit more configuration than it did with AT&T), I found I was getting the same old high ping-times (800ms), but my downloads could run at a blazing 26kBps (yeah, BYTES). EDGE is kind of cool like that.
I've managed to push my little toy MIDP 1.0 application to my phone and it runs nicely -- quicker than on the T616, which I'd expect. The couple little 3D games they had loaded on the phone were very limited demos, so I just deleted them. I'll probably code to the MIDP 1.0 spec for a while just to keep wider compatibility, but I look forward to exploring MIDP 2.0 once MIDP 1.0 gets too awkward. I have a bunch of applications to test, like Jabber and SSH midlets.
I did try a little motion detecting camera app. I was amused to see the application successfully enable and access the camera. I couldn't find an "Ask only once" option, though so the application stops and asks me permission every 1 second when it tries to snap a picture. That obviously won't work. The phone doesn't seem to want to allow me to change some of the application-specific Java permissions. Hopefully, I'll stumble upon a solution to this one.
I had to hack Bluemote 2.0 a bit to get it to even be able to connect to the phone. It just seems to be a minor issue of the read buffers. Once I figure it out cleanly, I'll submit a patch.
The directory hierarchy on the card and camera memory is amazingly deep. I pull my photos from camera memory using "Phone Memory/Pictures/camera_semc/100MSDCF" as the source path in
obexftp. Alternatively, the phone actually came with a little 3-in-1 USB card reader from Sony. It works beautifully with Linux as standard USB storage.
I'm looking forward to trying to use the MP3 player to carry a short podcast or 2 with me and play them in the car without having to boot up my notebook. There doesn't seem to be a commercially available stereo adapter available, though. There are supposedly schematics available to build one. The normal old hands-free adapter for Sony Ericssons seems to only hook up the right side. I'm sure I can figure out something.
The camera also stores 3gp files, which I got mplayer to play with a bit of convincing, but sound doesn't seem to work. I've seen some notes about patching mplayer with the AMR sound format reference source, but haven't tried it yet.
Update (20 September 2005): The little cover over the bottom port (for charging and hands-free) pops off often. I never remember to close it after charging, so I knock it off putting it in the case. I also rip the thing off when I open the phone with something plugged into it. It's a poor design, and I'll eventually just lose the thing.