Skip to content


In retrospect, is Verizon the best carrier to launch the Galaxy Nexus?

Since the Nexus One in early 2010, I’ve been an Adroid advocate, especially when it came to Google’s “flagship” products of a pure Android experience. The simplicity of it was very appealing for those with a minimalist mindset: no carrier bloatware, nothing disabled, good (sometimes great) hardware, and sometimes drastic changes which pushed other manufacturers to keep up. I dropped AT&T (for a change) after being a customer for nearly a decade and switched to T-Mobile to get the Nexus One, and never looked back.

Lessons that I think Google has learned since the Nexus One:

  • Heavy phones weren’t as desirable. The Samsung Nexus S, Nexus S 4G and Galaxy Nexus are all plastic cases and quite light compared to HTC’s Nexus One and its metal case. Granted, the Nexus One “felt” like a substantial phone.
  • Trackballs suck, but notification lights do not. The multi-color trackball on the Nexus One was great for notifications, but in the year I had the phone, I almost never used it. On the Nexus S, I don’t miss the trackball, but miss the notification light. Thankfully the Galaxy Nexus will have a notification light but I haven’t heard anywhere if it’s multi-colored or not.
  • Curved glass is nice. Yeah, maybe it feels better holding it to my face, but honestly, I haven’t seen other manufacturers step up on this one. Obviously not a *necessary* ground-breaking move by Samsung.
  • SD cards are so last year. While I was initially annoyed by the lack of SD card in my Nexus S, I get along fine without it. I have an rsync tool that I use to sync my phone wirelessly with a NAS drive at home. The Galaxy Nexus will take the internal storage one step further by removing all partitioning. The downside is that Linux and Mac users don’t have the “plug and play” capability over USB, but as long as my rsync tool keeps working, I won’t mind.
  • NFC is the future. For now, anyway. The latest Facebook app update includes NFC capabilities, and I read more about NFC uses every day. I’ve used NFC on my Nexus S exactly once: at Google I/O in May 2011.
  • Buying phones online was great for people with agoraphobia (fear of going outside), but it was too risky. The Nexus S was sold in Best Buy stores and later at Sprint stores with the Nexus S 4G revamp. The Galaxy Nexus sounds primed (no pun intended with the rumored device name) to sell at several carrier stores in the near future, as well as Best Buy and Radio Shack.

Knowing all of that, and the latest buzz around the Galaxy Nexus, I need to ask: Was Verizon really the best choice to launch the Galaxy Nexus?

When the Nexus One was released in January 2010, it launched on T-Mobile with 3G capabilities but you could only buy it online, which was risky, and was a solid phone. Rumors of having it on all 4 of the major US carriers flourished, but only AT&T picked it up, and it was quite a while after launch. Verizon and Sprint eventually admitted they weren’t going to carry the device. In December 2010, the Nexus S was released, and again only a T-Mobile version was launched; Sprint picked it up half a year later.

Verizon, aka “Big Red” has had a lot of news coverage about blocking tethering apps, installing permanent bloatware, and then it leaked that they were installing a few apps on the Galaxy Nexus, which is supposed to be entirely free of Carrier applications. I read a lot of “quit whining, it’s only 2 apps” on Engadget, but the truth is that this device wasn’t supposed to have ANY. Over the past few days, it was announced that Verizon and Google were at odds about Google Wallet on the Galaxy Nexus, and today the news broke that Verizon broke some federal rules about the spectrum deal from a few years ago when they blocked Google Wallet from working.

I was quick to criticize Google a few days ago over letting Verizon stipulate the terms of what is supposed to be a “pure” Android device, and that criticism still holds true for me. I don’t believe that Google should have to bow to anyone in that regard, and that the carriers need to just back off and let Google lead the charge. T-Mobile let them. Sprint let them. Yet Verizon is causing so many problems, it’s like they don’t WANT to release the device now.

Frankly, I was ready to pony up $300 of my dollars, plus a $50 ETF to T-Mobile, to switch my service to Verizon, plus pick up several of the accessories, but lately I’m regretting that decision and wondering whether to hold out for another carrier to carry the phone. If Sprint would allow the device on their network, I’d consider it, but not sure I’d want to stay with T-Mobile as they have poor coverage where I live. AT&T isn’t even an option. They’d have to give me the phone for free including cell/data if they ever want me back as a customer.

I know that Google has some sort of “bidding” process where handset manufacturers compete for the rights to build the next Nexus device, but I wonder whether they do the same for carriers, and whether someone’s legal team is going after Verizon over the many delays of this product.

Given the pentaband radio support in the Galaxy Nexus, would it make more sense to just sell an unlocked device where you got to choose your carrier based on the SIM you insert? Should I pick up a Canadian model over the holidays and see which GSM carrier to use?

Posted in mobile.


Search and Replace in Bash script

Had a colleague ask me how to do in-line regular expression matching for a Bash shell script. Since Bash v3 only offers a regex matching check and not the full s/foo/bar/ syntax, I offered to look into other alternatives.

My natural instinct was to look for a Perl cmdline regex parser, which works great if you're manipulating a file and not shell variables.

In the end, since he only needed a simple search and replace, and not an actual regular express, this suffices:

#!/bin/bash
VAR1="foobar"
VAR2=`echo $VAR1 | awk -v srch="foo" -v repl="bar" \
   '{ sub(srch,repl,$0); print $0 }'`
echo $VAR1
echo $VAR2

Posted in devops, howto.

Tagged with .


Fixing NO_PUBKEY errors from Apt

I've been ignoring a problem updating Diodon (a great clipboard manager) whenever Ubuntu's daily Update Manager tries to alert me of new software updates. I finally opened a shell prompt, ran "apt-get update" and got this error:

W: GPG error: http://ppa.launchpad.net natty Release: The following
signatures couldn't be verified because the public key is not
available: NO_PUBKEY 751A20CF523884B2

Here's how to fix any NO_PUBKEY error in two simple steps:

$ gpg --recv-keys 751A20CF523884B2
gpg: requesting key 523884B2 from hkp server keys.gnupg.net
gpg: /home/id/.gnupg/trustdb.gpg: trustdb created
gpg: key 523884B2: public key "Launchpad PPA for Diodon Team"
imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)

$ gpg --armor --export 751A20CF523884B2 | sudo apt-key add -
OK
Ta-da… 
$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  diodon
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 55.4 kB of archives.
After this operation, 115 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Just have to replace “751A20CF523884B2″ with whatever public key value that Apt is complaining about. You can also specify which GPG server to connect to when using the –recv-keys flag, but if you leave it off, I beleive it will just connect to their main pool of GPG databases.

 

Posted in devops, howto.

Tagged with , , , .


Elastic Path Software: out of the colo and into the cloud, with Google App Engine

Eddie Chan at Elastic Path Software got a guest blog spot on Google Code's blog as part of their "Who's at IO" and wrote about what Elastic Path is up to with regards to moving your apps out of colocation facility and writing them as Google App Engine applications. This is one sandbox sessions I'm looking forward to checking out while I'm at IO.

While I'm always interested in running apps "in the cloud" (and we seriously need a new term for that), I'm not sure if I want to get into Java programming just yet. I remember attending an introductory "This is Java, this is how it'll change the world" evening session with some coworkers from QNX back in late 1996, but I guess I've always enjoyed the rapid development cycle of scripted languages because I can make fast changes to code for testing without having to stop and compile anything.

I'm currently in the process of moving a client from a built-by-me e-commerce buying portal to OScommerce because I have too much on my plate already to rebuild his inventory/sales system from scratch. I was hoping to have had the time/energy to rewrite the catalog system in Python and move him to G.A.E., but his needs outpaced my available freelance development time.

Posted in devops, webdev.

Tagged with , , , , , .


Where is the Linux-native Amazon Kindle reader?

So I've been digging into Python more and more, and upon Jorge's recommendation, I picked up a Kindle edition of O'Reilly's "Learning Python" by Mark Lutz, as well as the "Pocket Reference" edition.

What boggles my mind, however, is that Amazon has an Android-compatible Kindle app, yet no native Linux app. Since I'm much more comfortable doing development in Linux, I needed a way to read my Kindle book via Linux so I didn't have to squint at the 4" screen of my Nexus S in order to read. Perhaps Google IO next week will surprise me with a free tablet, but I'm not holding my breath.

Wine 1.3.x to the rescue. While it's not the 'stable' release for Ubuntu (at work) or Gentoo (on the laptop), it will allow you to run Amazon's PC application which is a free download. And it works very well. Everything sync's up just fine, but I'm still disappointed that Amazon, who seems to love Linux for their EC2 platform and other AWS services, would forego a native Kindle app.

 

Posted in devops, misc.

Tagged with , , , , , .



Get Adobe Flash playerPlugin by wpburn.com wordpress themes

This website uses a Hackadelic PlugIn, Hackadelic SEO Table Of Contents 1.7.3.