Today, has been one of those tough lessons about technology. I'm a geek. I expect to get all my tech purchases right, but today I learned that the marketing folks pulled the wool over my eyes, so here's a post to help prevent another poor soul from falling into the same trap.
What is a 3G phone?
For me, the term "3G" evokes images of quick loading web pages, fast downloads and the often advertised "mobile broadband" notion. However, the marketing folks use 3G for that reason and they use it to mean better voice services.
I came to research this because I purchased a Nokia 6263 phone in May, 2008. At that time, I really wanted a Bluetooth phone and I didn't want it to become obsolete when T-Mobile finally got around to rolling out their 3G network - I wanted access to fast data when it came available. However, 3G service rolled out in my neighborhood on October 1 and I haven't noticed any speed increase.
It turns out that while the Nokia 6263 has 3G frequencies for voice - this shows up in specifications as "Dual-band WCDMA 1700, 2100". However, the phone does not have HSDPA which is required for that high speed data downloading I thought I was getting.
It took me all day today to figure this out.
This included two phone calls to T-Mobile support: The first rep told me 3G hadn't been rolled out to my area yet, the second told me it was rolled out to my area, but couldn't explain why I wasn't seeing 3G speeds and didn't offer any ways to measure my speed.
After the two confusing phone calls, I decided to visit my closest T-Mobile store where the two sales people disagreed about whether or not the 6263 was a 3G phone. Then the person who thought it was a 3G phone went on to tell me "you won't get 3G speeds through T-Zones." Still not satisfied, I drove to another T-Mobile store and found out that it just didn't work. While I was at this store, the store employee called T-Mobile support to find out more. The support person on the phone offered to sell me a new data plan that "might" improve my data speed. Instead I decided to do an experiment and used a G1's SIM card in my 6263 - the idea being that the G1 SIM should have the best data plan available and still the 6263 crawled around 90-100kbps on text.dslreports.com/mspeed.
The bottom line is that G3 phones means two things. It definitely means that voice calls and data calls can take place at the same time as specified by WCDMA. High speed data is a subset of G3 and only phones that support HSDPA will have the high speed data.
Now, for normal consumers visiting T-Mobile's web site, this is an even larger problem. On that pages, you can "Shop by Feature" and click on "3G". Doing so will display 6 phones: Nokia 6263, Nokia 3555, Samsung t639, SE TM506, Samsung t819, T-Mobile G1. T-Mobile's web pages offer no specifications. (The links above all go to PhoneScoop.com's specifications)
However, the "Features" section for each of these phones says:
T-Mobile’s high-speed 3G data network delivers the ultimate mobile Web experience in several metropolitan areas
I have a cousin who is legally blind and multi-handicapped. One of the things he loves is listening to his music. He still listens to music on cassette tapes.
I know, I know, it's the 21st century, so why is he still using tape? Well, a long, long time ago he learned how to insert a tape into a tape player. Also, generally tape players have nice big buttons that are easy to push. Since he can't see well and doesn't have great dexterity in his fingers, these factors make it difficult to try something else. He's tried to learn how to use CD players, but generally inserting a CD into a machine is more difficult and usually the controls are just not as friendly.
But it is the 21st century. That means tapes are on their way out. CD's may not be far behind. A digital media player would be the way to go. But, have you ever thought about using an MP3 player with your eyes closed? Although I never thought about it, most of them are designed specifically for sighted people.
I thought that perhaps all was not lost when I read a blog entry at the American Foundation for the Blind(AFB) entitled, "This News is Music to My Ears…" by Darren Burton. In that article, Mr. Burton says, "Apple announced that the new iPod Nano 4th generation will have talking menus, so people with vision loss can independently find and listen to music and other content on their iPods." while Mr. Burton says there will be an upcoming review in AccessWorld, I happened to be at Target today so I picked up a 4th Generation Nano and decided to try it out.
I guess before I go any further, I should say that I am sighted. To try out the Nano, I just tried using things with my eyes closed. My computer is not configured with any sort of screen reader so I cannot comment on the accessibility of iTunes 8.
One of the first things to know is that the talking menus are disabled by default. To turn them on, you have to check the checkbox entitled, "Enable spoken menus for accessibility" on the iTunes display. I don't know easy that will be to do for a non-sighted person.
Unfortunately, the first time I did that, it did not activate any talking menus on the iPod. I had to scratch my head and go out to the web to find out what I did wrong. It seems that I needed to choose a voice in the Speech control panel of Windows XP so that iTunes could generate the talking menus it would download onto the iPod.
I have mixed feelings about the speech synthesis system the iPod uses. On the one hand, it's great that it uses the local computer to generate the names of artists and songs. Still, I sort of wish that I could browse through a number of audio profiles on the iTunes Store to choose a voice I like and download that to the iPod? Heck, that voice could even be done by a voice over specialist rather than a computer generated voice. This voice could be used for the standard menus and messages in the iPod while the generated voice could be used for artists, album names, song names, etc...
The next big complaint I had is that there just don't seem to be enough depth to the use of voice. For example, on my iPod I didn't have any Movies or TV Shows. When I clicked on those menu choices, the screen displayed the message, "No Movies" or "No TV Shows" but did not speak anything to me. While I had my eyes closed, this made it very difficult to know what to do next.
Lastly, I don't think my cousin would be able to use the Nano. Due to his dexterity problems, I don't think he'd be able to handle running his finger around the dial to adjust the volume and I'm not even sure he would be able to learn how to find the different functions (menu, rewind, fast forward, pause/play) that are around the center button.
While I was writing this entry, I came upon the AFB's Now Playing: A Review of the Accessibility of Digital Audio Players, Part 1 which talks more about accessibility of mainstream audio devices.
I've also found the Vi-Player device which looks interesting although it's not even available until November 2008. It looks particularly interesting since it has larger, raised buttons for the functions.
I also encountered the VictorReader Stream which seems to be popular for digital books and MP3's.
Today, Google introduced a new downloadable Java program for accessing your Gmail from your mobile phone. Of course, it doesn't work on my T-Mobile based Treo 600 (even though I have both a Sun and IBM JVM on my phone) or on my wife's Verizon LG-VX8500. After wondering why, I went to the the Gmail Help Center and found this:
Note: The Gmail application doesn't currently work with T-Mobile USA or BREW-based carriers (e.g. Verizon, Alltel, U.S. Cellular).
If your carrier provides TCP/IP access, and your phone provides a JVM, why then does the carrier matter? How does the carrier impact whether or not the Gmail application works?
I'm confused...
I found this in some coverage of Comdex. It's the Tapwave. A 200MHz ARM, Palm OS 5, powered portable game machine (and PDA, too). Looks cool...
I finally have my Tivo upgraded with a 160GB Seagate Barracuda.
I ended up making space in my PC for all the requisite drives by taking out my WinXP boot disk and taking out my CD-RW drive. Booting from the CD, it gave me room to plug in the Tivo drive and backup to a new drive that I bought.
That was the first problem I ran into though. Backups. I still haven't quite figured out what the mfstool thinks a backup is. The regular backup backs up just the "essential" files and is quite small (around 800MB this time). However, it provides an option to backup everything (-a).
So, that's what I thought I would do. I would create a single backup of everything on my hard drive and store on my new 300GB disk. Sounded good in theory. Unfortunately, it turns out that the Linux kernel on the boot cd is version 2.4.4 from Aug-20-2001. Apparently, due to the tools used at the time, it suffers from a 2GB file size limit. (Needless to say, it took forever to figure out that was what was happening. I couldn't find mention of this 2GB file limit in any Linux FAQ.)
Having given up on making a full backup, I used the mfstool to backup and restore to the new drive over a pipe. No problem. It copied everything over. (many hours later.)
My next problem came when I tried to enable backdoors. I thought, "Hey! I'll do the hexedit nonsense while I have the drive in the PC before I put it in the Tivo." Silly me. Turns out the MFS Application Region partitions of the disk are blank after doing an mfstool backup/restore. I needed to boot up the Tivo once to populate the partitions with information that I could then change with hexedit.
Also, when using hexedit it took me a while to realize I was supposed to hit "TAB" before Ctrl-S to do the search for the key string. It was written in the book, I just missed step one and it turns out the editor defaults to searching for hexadecimal strings rather than ASCII strings.
But all is working. Took longer than expected. But which projects around my house don't seem to take longer than expected.
I thought I was all set. Got myself a copy of "Hacking the Tivo" by Willaim von Hagen and I thought I was all set to open my Series 2 box.
I figured I'd dip my toe into the waters of Tivo hacking by doing something simple - upgrade my hard drive. Went to the store and got myself a new Seagate 160GB drive to upgrade the stock 60GB drive in the Tivo. Bought some Torx screwdrivers and thought I was all set.
Then I hit The Wall
The book is great. It provides great directions and it even provides a CD-ROM to boot off of to get into a Linux kernel with all the tools. But I ran into a few hitches.
First, the PC that I have doesn't have any empty drive bays. I've got them filled with:
To do a backup of the existing Tivo drive I need to insert two drives - one to hold the backup and the Tivo drive itself. I hadn't counted on needing two drive bays to do this juggling.
Also, it was pretty funny. I never thought about where I'd backup the existign Tivo drive to. I had just though, "Oh, it's small. I'll be able to back it up." It's a strange world when 60GB of data is starting to look small. Anyhow, I don't have anything big enough to hold that data, so I need to go back and buy another drive tomorrow.
Then, I can take out the XP boot disk (in addition to being too small to do the backup, it's NTFS and that's not supported by the software on the BATBD CD), and the CD-RW and then I'd have enough space to do the backup and upgrade to a new disk.
Oof.