Advertisement

Archive for the 'Nokia N810' Category



Nokiahowto.com has useful how-to’s for the new user

With a new device like a Nokia Internet Tablet, a hazy fog of “what do I do?” envelops the break-in period.

How do I connect to the router? How do I get the GPS going? How the heck do I build a playlist in this fershlugginer player?

Of course, dealing with these questions is one of the main purposes of this website.

But even before you have specific questions, the unfamiliar can boggle you. Even with my experiences breaking in the 770 and N800, I’ve been confounded now and then with my new N810.

I think the Nokiahowto.com pages on the N810 should be put on the device itself. They’re more helpful to a new user than the help files and the PDF user manual.

Why is that? They’re nothing exotic, merely short, simple animations. I guess it’s a case of show being more helpful than tell.

egadgetawards.jpg

Engadget is running their annual Engadget awards and the Nokia N810 is nominated in the 2007 Handheld of the Year category. The Nokia N810 is currently trailing the Amazon Kindle by about 300 votes (as of writing).

You have until March 1st to vote for the N810 and your other favorite gadgets.

Vote now.

Nokia has released a new firmware update to OS2008. Maemo.org is reporting that this release (v2.2007.51-3) fixes the following bugs:

  • 2417 No includes for libapt-pkg (aka libapt-pkg-dev)
  • 2917 libgdbm-dev is reported missing with chinook’s apt-get
  • 2766 Missing libxslt1-dev in chinook
  • 2901 Can’t install blues-utils-tools on current n810.

Reports from Internet Tablet Talk members say that the only thing this update fixes is the power-on problem. It looks like however that this update is more for the developers, as indicated at Maemo.org and from the release notes and from the Maemo 4.0 to 4.0.1 comparison table.

Links:
Nokia Internet Tablet Software Update Wizard for the PC
Nokia N810 Firmware image
Nokia N800 Firmware image

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!

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.

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.

Marcus Couch of The Scene Zine just sent me a quick note to tell everyone the he will be doing a Nokia N810 video podcast gig which will be launching soon. Nokia has agreed to somewhat sponsor the show by giving away a 15% off Nokia N810 coupon code if purchased directly from any selected Nokia online stores.

Coupon Code: SceneZine

This brings the Nokia N810 price down by $72/£49.35 which I think beats any online retailer. A 2-day free shipping is included if purchased from the Nokia US online store.

Links: Nokia US Store, Nokia UK Store

amazon.jpg

Amazon.com just released its Holiday Best Sellers list (from Nov. 15 through Dec. 19 Based on Units Ordered) and on the personal computer category, the Nokia Internet Tablet makes it to the Top 3 list:

In PCs, the top sellers included Apple MacBook, Nokia Internet Tablet PC and HP Pavilion Entertainment Notebook PC.

Check out the current prizes of the Nokia Internet Tablets at Amazon.com.

canola2.jpg

The iNdT team must have been actually waiting for the OS2008 update before releasing Canola2 Beta. The Canola official site is now updated with lots of new information about Canola2 Beta, videos, feedback form, and of course the install page. Note however that Maemo.org’s server is being hammered right now and it might take a while for everyone to download and install Canola (9.32 MB).

Eduardo Oliveira (aka handful) has identified some features that are not working and some that needs polishing. It would be great if we can send them what ever bugs we find through the Canola2 Official Feedback page or through the itT Canola2 Beta Discussion Thread new itT Canola forum.

Links:
Install Canola2.
Official Canola Website.



Advertisement


Amazon

Tablet Sites