Advertisement

Archive for January, 2008

trolltech.jpg

Yesterday’s big news was Nokia’s $153M acquisition of Trolltech, makers of the Qtopia framework and the Qt platform. Some of you might have heard of the Qtopia Mobile Phone, or the Sony Mylo, or Skype, or Google Earth, or Adobe Photoshop Album, or the Nokia PC Suite — one thing common about them is that they are ‘Trolltech Inside.’

A lot of discussion brewed from this move from Nokia. A hefty discussion brewed at itT and posting the same question at the Maemo Developers List received some interesting responses worthy of a ‘free software opera’ as Quim Gil, Nokia Development Platform Product Manager puts it.

Quim, as most of us know from Maemo.org, has just posted a new entry on his blog to hopefully put some perspective on Trolltech and Maemo. Here are some snippets:

…I made some research to confirm the guess. When it comes to maemo, there are no Trolltech/Qt related plans at the moment.

On the mid term… well, nobody knows. What follows are my thoughts today.

Trolltech develops Qt, a cross-platform application development framework that powers KDE and is also licensed to many commercial software projects. Nokia pushes the Symbian OS with several own platforms on top like S60, plus S40 running on top of Nokia OS, plus several non-mobile applications like Nokia PC Suite (developed with Qt, by the way). Trolltech’s toolkit and its C++ native language (which is native in Symbian as well) fit very well in Nokia’s short term strategy to improve cross-compatibility between the Symbian platforms. If making a good use of the Qt library helps having in maemo some of the cool stuff available in S60, all the better then.

Thanks for taking time explaining things Quim!

Read the full article.

Ah, bliss. That’s what you feel when you hold a new Nokia N810 Internet Tablet in your hands.

And after the long build-up of anticipation, the waiting for stock in the U.S. and for the go-ahead from Nokia (not to mention enduring an unrealized warning about a potential additional 3-week delay before shipping), yesterday afternoon I was able to check online and see that Fedex had delivered my own N810 yesterday afternoon.

At 2:24 p.m. according to the uselessly precise information recorded in the shipping log. By 7:30 I would be home from Manhattan and experiencing that bliss myself.

But, as it happens, I’m not holding a new N810 in my hands now. Why? Because, despite the statement in the shipping log, a Fedex truck did not pull up in front of our house yesterday with the long-awaited package.

Somewhere in my home town of Montclair, NJ, someone’s front door did receive an unanticipated Fedex delivery yesterday afternoon.

Just not my front door.

Fedex shipping log proving the delivery of the N810 (not)

Bliss I was expecting, not the nightmare and torment of now-you-see-it-now-you-don’t.

I’m just shaking my head at the moment (literally and figuratively), waiting for what comes next. Yes, I see: I get to play an extra round in the waiting game.


Added Wednesday, Jan 30

We have the first clue in the case.

Fedex never got back to me (why did I instinctively type ‘of course’?), so I called again today. Vanessa, who took the call, said the trace they had done involved querying the driver, who affirmed that he had delivered the package.

Duh. But where had he delivered it?

“To your house, 27 [Ourstreet], Montclair. A white house next to a blue house.”

Aha! We don’t live next to a blue house!

After promising to send a note to the Fairfield center and let the driver know that we live in a white house between another white house and a yellow one, Vanessa advised me that I’d hear back from them this morning (I’m writing this at 2:30 p.m. and haven’t heard anything, but that just about goes without saying).

As it happens, number 23 is a blue house, and so I visited number 21 (no one home and no package lying about the premises) and left a message about the N810.

Perhaps the driver misread the 7 as a 1?

I hope to learn from our neighbors this evening if they took in a package they hadn’t realized was misdelivered. With two really young children, they might not have bothered to open an unexpected delivery yet.

Well, at least I can hope.


Added Thursday, Jan 31

The saga continues:

Fedex delivery was definitely not made to number 21. The other high-likelihood candidates nearby are all the immediate here’s-your-misdirected-package sort. Thus the odds of a nearby misdelivery (the package does have our name and address on it, after all) are rapdily declining.

The street we live on is only one block long, so number confusion is less common than street confusion. We get mail every couple weeks that is meant for 27 Some-Other-Street (of course, that’s USPS, not Fedex). If the N810 is going to show up in the next day or so, that’s now the most likely explanation.

But I’m already bracing myself for the “OK, who’s going to accept responsibility for replacing this device” discussion with the shipper and deliverer.


Added Friday, Feb 1

After my third phone call with Fedex, I asked “Are you done? What do I do?” And I got the answer that the shipper should put in for reimbursement.

So yesterday morning, I called LetsTalk.com, explained the situation to their rep, who said she would check with Fedex and then have a supervisor call me back that morning. (Um, never called, of course. As if I were expecting it.)

And so I called again today, went through exactly the same process, even down to the “I have to get a supervisor to handle this” when I interjected “You know, I’ve only called you because Fedex said they were done with the trace and I should put in for reimbursement.”

That seemed to be just the right thing to say. The LetsTalk rep called Fedex right then and there — conferencing me in — and the apologetic Fedex rep who answered said they would be sending the driver back to leave a note at the house where the delivery was made but that LetsTalk should definitely ship another unit and put in for reimbursement. (Unspoken was the alternate scenario: “And if we find the package, we’ll ship it back and settle up again.”)

Right outcome. So now I’ve got a Monday or possibly Tuesday delivery.

I’ll wait to celebrate ’til I get the package.
Ah, bliss. That’s what you feel when you hold a new Nokia N810 Internet Tablet in your hands.

And after the long build-up of anticipation, the waiting for stock in the U.S. and for the go-ahead from Nokia (not to mention enduring an unrealized warning about a potential additional 3-week delay before shipping), yesterday afternoon I was able to check online and see that Fedex had delivered my own N810 yesterday afternoon.

At 2:24 p.m. according to the uselessly precise information recorded in the shipping log. By 7:30 I would be home from Manhattan and experiencing that bliss myself.

But, as it happens, I’m not holding a new N810 in my hands now. Why? Because, despite the statement in the shipping log, a Fedex truck did not pull up in front of our house yesterday with the long-awaited package.

Somewhere in my home town of Montclair, NJ, someone’s front door did receive an unanticipated Fedex delivery yesterday afternoon.

Just not my front door.

Fedex shipping log proving the delivery of the N810 (not)

Bliss I was expecting, not the nightmare and torment of now-you-see-it-now-you-don’t.

I’m just shaking my head at the moment (literally and figuratively), waiting for what comes next. Yes, I see: I get to play an extra round in the waiting game.


Added Wednesday, Jan 30

We have the first clue in the case.

Fedex never got back to me (why did I instinctively type ‘of course’?), so I called again today. Vanessa, who took the call, said the trace they had done involved querying the driver, who affirmed that he had delivered the package.

Duh. But where had he delivered it?

“To your house, 27 [Ourstreet], Montclair. A white house next to a blue house.”

Aha! We don’t live next to a blue house!

After promising to send a note to the Fairfield center and let the driver know that we live in a white house between another white house and a yellow one, Vanessa advised me that I’d hear back from them this morning (I’m writing this at 2:30 p.m. and haven’t heard anything, but that just about goes without saying).

As it happens, number 23 is a blue house, and so I visited number 21 (no one home and no package lying about the premises) and left a message about the N810.

Perhaps the driver misread the 7 as a 1?

I hope to learn from our neighbors this evening if they took in a package they hadn’t realized was misdelivered. With two really young children, they might not have bothered to open an unexpected delivery yet.

Well, at least I can hope.


Added Thursday, Jan 31

The saga continues:

Fedex delivery was definitely not made to number 21. The other high-likelihood candidates nearby are all the immediate here’s-your-misdirected-package sort. Thus the odds of a nearby misdelivery (the package does have our name and address on it, after all) are rapdily declining.

The street we live on is only one block long, so number confusion is less common than street confusion. We get mail every couple weeks that is meant for 27 Some-Other-Street (of course, that’s USPS, not Fedex). If the N810 is going to show up in the next day or so, that’s now the most likely explanation.

But I’m already bracing myself for the “OK, who’s going to accept responsibility for replacing this device” discussion with the shipper and deliverer.


Added Tuesday, Feb 5, 3 p.m.

Delivered five minutes ago. Hoorah!

vc00.jpg

Previously released on OS2007 as beta, Nokia just announced Video Center’s official release for OS2008. Video Center lets you subscribe, download, stream, and manage video from feeds and gives you the option to store them on your Internet Tablet for later viewing.

Video Center is currently configured to support video feeds from PodShow and Rocketboom with other official feeds to be added in the future. You can add your own video feeds however, as long as they are in RSS 2.0, XMLTV, or SPF format.

Links: Video Center Garage, Install Video Center OS2008

Official screenshots after the jump.

Continue reading ‘Video Center for OS2008′

Hm-m. Who is the most worthy non-Nokia N810-owning member of the Internet Tablet community?

Tim Samoff wants to know, and he’s got an appropriate gift for said worthy: a free, new Nokia N810 Internet Tablet.

Yes, Tim has two N810’s (plus an N800) and he’s giving a share of his bounty to someone — whoever that may be — where it will do the most good.

See this forum post and his blog for all the details.

* * *

Added later: What’s this about thoughtfix being an N810-havenot? Didn’t he get to exchange his pre-production device for a keeper?

Despite the iPhone’s tremendous hype, we all know that it’s a small, small segment of the total mobile-phone market. According to IDC, a market research firm, iPhones comprise just 2 percent of smartphones — compared to the 63 percent powered by Symbian*.

Interesting then that in December, Google reported, it had more internet traffic from iPhones than any other mobile device.

Think this says something about how useful people find the walkaround web? Or why AT&T is giving free access to 10,000 WiFi hotspots to its broadband subscribers?

And why the Internet Tablet has an 800-pixel-wide screen but still fits in your pocket and weighs only 8 ounces?

Ari Jaaksi pointed out more than two years ago that with the arrival of the Internet Tablet the web wasn’t stationary any more. People with laptops aren’t walking around checking the web. And surfing the internet on a cellphone screen is just painful. Those were never harbingers of a web paradigm shift.

But we users of the Nokia 770, N800 and N810 know the truth of Ari’s statement. And iPhone users are learning it too. We need the web, wherever we are — not every second of the day, but at any moment of our day.

And a large screen, light weight and small size are absolute requirements.

I think we’re going to see a much wider commercial acceptance of this “useless” niche this year.

__________
* Nokia owns 47.9 percent of Symbian.


My good pal, Matt Miller, The Moble Gadgeteer blogger over at ZDNet, gives a good demo and detailed instructions on how to tether the Nokia N95’s integrated GPS and modem with the Nokia N800 Internet Tablet, all via Bluetooth.

Basically, you need the Symarctic ExtGPS (beta) app installed on the N95 which will allow other devices (mac, pc, linux included) to use its GPS, a data plan to have the N95 connect to the internet, and Maemo Mapper. What is interesting is that both the GPS and modem are working together via one (or maybe two) Bluetooth connection(s) to the N800.

Thanks Matt!

Read Matt’s full writeup.

From the AP wire:

Nokia Corp., the world’s No. 1 mobile phone maker, on Thursday said that fourth-quarter net profit surged 44 percent to $2.6 billion and that it had reached its long-term goal of 40 percent market share in handset sales. The company’s stock soared.

Finland-based Nokia said that net sales in October through December grew 34 percent to 15.7 billion euros ($22.9 billion), and that it sold more than 133 million handsets — up 27 percent from the same period in 2006.

Hm-m. Guess they know what they’re doing, eh?

Oh, and Motorola? “Net profit fell 84 percent in the fourth quarter and mobile phone sales were down 38 percent.”

Nokia has experienced some delays in making devices available to the 500 developers and bloggers (and other contributors? did anyone receive a discount for contributing documentation?) who qualified for the maemo device program discounts. (See this thread in the ITT forums, for instance.)

This morning, the next-to-last on the list — contributors buying from the U.S. stocks — were notified that they could now apply their discount code to purchase a Nokia N810 Internet Tablet.

Alas, the usual glitches are still preventing this — developers report Friday morning that inserting a discount code results in either an “invalid code” or “zero balance” response and operators at Let’sTalk.com who hanclle phone orders decline any knowledge of the discount.

I’m posting this info now in hopes that someone at Nokia might see this and straighten things out.

* * *


Added Jan 22: New email, new results: orders accepted and delivery due in two days.

Added Jan 24: People who placed orders as recently as Jan 22 in the evening have been notified that the N810 is back-ordered and they shouldn’t expect their devices for three weeks.

The first set of Canola2 Beta bug fixes are coming out early next week. Expect the following fixes and enhancements:

  1. Compilation or SoundTrack albums being replicated N times
  2. Cover Art support
  3. Cover Art selection
  4. Podcast downloading / playblack and remembering state
  5. MP4 not playing when mplayer installed
  6. Some Pictures not appearing at all in the application
  7. Support for WMA and WMV files

A major update is scheduled to be released on February, finally adding more video, music, and podcast support.

As always, feedback on the update as well as suggestions for additional features can be made through itT’s Canola forum.

Read the full details of the upcoming update.

Here’s more proof of the upcoming WiMAX enabled Internet Tablet. It seems like Nokia is currently working with Alvartion Ltd., Cisco, and Mocano Telecom on establishing a Center of Excellence on WiMAX aiming to provide consumers VoIP, streaming video, and an always on-line experience. Alvarion is bringing in their 4Motion Open WiMAX solution, Cisco is providing seamless WiMAX mobile integration via their Broadband Wireless Gateway, Nokia is bringing in a WiMAX 2.5GHz compatible Internet Tablet, and Monaco Telecom is experimenting on the solution at Tunisia.

According to Ari Virtanen, Vice President, Convergence Products at Nokia:

Working with Alvarion, Cisco and Monaco Telecom is a great step towards making Mobile WiMAX available for consumers and fits perfectly with our strategy of offering a broad and innovative portfolio of devices.

In the US, WiMAX will be via Sprint’s XOHM.

Expect the new internet tablet sometime April - May.

Read the full article.



Advertisement


Amazon

Tablet Sites