Mobile devices are on my mind at the moment. I have an iPad 2 that recently turned 6 years old. And I have a new Android phone, because my previous phone just bricked.
I didn’t expect the iPad 2 to last this long. I didn’t think that Apple products were meant to last, but to be cast aside for fresher Apple stuff. My iPad 2 hasn’t always had the gentlest of treatment.
But on it goes, insisting that its software–iOS 9.3.5–is up to date. What it really means is that it can’t go beyond that version of iOS. That’s a good thing. I don’t want it to go to iOS 11, under which some of my favorite apps will not run.
As long as it holds up, I will continue to use it for apps such as Polyhedra, Card Thief, Through the Desert,… and many more. I’ll also use it for email. It seems to struggle most with web browsing, although that may be the fault of the Guardian’s site.
My Android phones have been rather less long-lived. My Motorola Droid Maxx turned into a brick a few days ago. It was itself a replacement for a similar phone that suffered from terminal boot-loop.
I now have a Samsung J7 V (for Verizon, I think). So far, so good.
But I’m wondering whether the 6 year old iPad 2 will outlive the new phone…
The big tech/business story of the week is the AT&T/T-Mobile deal: AT&T wants to buy T-Mobile USA from Deutsche Telekom, and Telekom wants to sell, given the $39 billion price tag. One of the things I mean by “big” is “lots of coverage.”
If I had to pick two pieces of required reading, the first would be Om’s account of who loses in this deal. “It’s hard to find winners, apart from AT&T and T-Mobile shareholders.” I can’t see that consumers will win from a deal that reduces the number of mobile phone competitors in the USA to two (or three, if you’re Sprint, or a lawyer for AT&T).
The second piece of required reading was the agreement on my T-Mobile G1 phone, to see when the agreement expires. It expires in August this year. I expect the regulatory scrutiny to last beyond then. I’m not sure what I’ll do for a phone after August…
One recent step takes Google Voice onto the iPhone. As Om reports, it’s browser-based (HTML5). Hence it sidesteps security at the iPhone app store.
A few days ago, Michael Arrington declared himself so besotted with Google Voice that he followed its beckoning extension into Chrome from Safari. Said extension adds click (a phone number on a web page) to call (via Google Voice) to the Chrome browser.
The above two steps have a few things in common: about Google Voice; positive; something of a score for Google over Apple; written by the founder of a blog that grew into a New Media Property (rather than delegated to one of several other writers at said property).
The third and last step I’ll describe in this post offers a contrast with the first two. It’s a step backwards for Google Voice. GV hasn’t worked on my Android G1 pretty much since I moved from Boston to Silver Spring.
I submitted a support ticket at the GV site a few days ago, but have yet to hear anything. Meanwhile, all the calls that I was hoping would be free (or very cheap, in the case of international calls) fail over to a “real” phone number, and T-Mobile bills for real money.
I also posted about this elsewhere. Perhaps that’s why my attempt to give away GV invites didn’t work…
Once again, my review of the Wednesday-to-Wednesday week appears on a Thursday. Here goes: