Update for Nook Simple Touch 1.1.0

[RHWright]

Since this has wandered all over the place, I'll throw in my comments on what I can.

1) Haven't noticed any real impact from update, good or bad.

2) Battery life is the same.

3) Don't have a wireless router at home. But I do know it would be impractical to test with all possible brands/configurations. Though, anecdotally, there seems to be a major gap in whatever testing they were able to do.

4) As to the whole browser vs/ it's just an ereader topic: though I have no real need for another web-enabled device (especially an eInk one after the laughable N1E browser), I can see how others might have different needs. I like the simple, relatively inexpensive, "it's just an ereader" model. Maybe there is room for an intermediate model between the N2E and NC/Tablet? An eInk model with a robust browser, small app store for games, etc. Possibly 3G (for downloads only)? Those would address multiple issues I've heard raised since the N2E came out.

Overall, the N2E is a great fit for my needs. The great thing is, there are so many choices out there that it is possible to find a fit that works for you. If not B&N, then Amazon, or Sony, or Apple, etc., etc.

[dhalbert]

I took a new Simple Touch out of the box Monday night, and set it up. I did NOT enter a credit card, but otherwise registered it. It came with 1.0.1. I expected it to update itself within a short time, but as of Thursday morning, it hasn't, and it's been in wi-fi range the whole time.

I know I can manually update it, but I'm in no hurry, and wonder why it hasn't happened yet. Three possibilities I can think of:

1. It may take several days for the servers to get around to it.

2. The update is being held back while they prepare another one.

3. Not giving a credit card means it will not update until I do give one.

Any insight? Thanks.

[gstone]

---

dhalbert wrote:

I took a new Simple Touch out of the box Monday night, and set it up. I did NOT enter a credit card, but otherwise registered it. It came with 1.0.1. I expected it to update itself within a short time, but as of Thursday morning, it hasn't, and it's been in wi-fi range the whole time.

I know I can manually update it, but I'm in no hurry, and wonder why it hasn't happened yet. Three possibilities I can think of:

1. It may take several days for the servers to get around to it.

2. The update is being held back while they prepare another one.

3. Not giving a credit card means it will not update until I do give one.

Any insight? Thanks.

---

There is no update for you. Firmware 1.1 is the latest firmware.

Niether of our NSTs are on accounts with credit cards. I have a seperate account to make ebook purchases and sideload those ebooks. Not entering a credit card should only prevent you from making purchases from the device.

[dhalbert]

"There is no update for you. Firmware 1.1 is the latest firmware."

Thanks for the credit card info; that is helpful to know. As for the firmware, my NST came with 1.0.1, so I am expecting it to update to 1.1.0.

[gstone]

---

dhalbert wrote:

"There is no update for you. Firmware 1.1 is the latest firmware."

Thanks for the credit card info; that is helpful to know. As for the firmware, my NST came with 1.0.1, so I am expecting it to update to 1.1.0.

---

My bad I read that as 1.1 the first time.

[RHWright]

My experience with the N1E was that it downloaded the current update immediately when I registered it.

I would assume it was the same with the N2E. (Though there I had to wait for my existing unit to be updated.)

My guess is that, yes, not having a credit card on file means that your NOOK has not completed registration, so it doesn't know to push an update to you.

Q: if you go online to My NOOK, does it show the N2E under Manage My NOOK?

[gstone]

---

RHWright wrote:

Q: if you go online to My NOOK, does it show the N2E under Manage My NOOK?

---

Yes

Edit:

I just checked my mom's N2E and it updated via wifi without having a credit card on the account. It may be they are not pushing out the 1.1 update now and are preparing a new update that addresses the v1.1 problem with wifi and certain routers.

[scotta316]

I waited for my N2E to update over wifi when the update came out. It updated on the fifth day after it was released. Maybe they enter some kind of queue to be updated. I believe it's normal.

[wisdombunny]

Me too..  

[boomerrang]

After the new software update the activity reader does not work most of the time. I will go to a book and all I get is a blank white page. This new update is terriable. If they cannot fix this I may just have to go to the kindle.

[JoeAtWork7]

Since I see there're a lot of people out there who want the web browser with version 1.1.0...here's how you access it:

1. Hit the "n" button, and go to "Settings"

2. Click on "Social"

3. Click on "Link to Facebook, Twitter, and Google"

4. Click on "Link Your Account" under GOOGLE <-- remember...under google!

5. Click "Can't access your account?" at the bottom of the page

6. Click "Google Home" at the bottom of the page

This brings up the google homepage from where you can search web addresses or whatever...

Don't know why you'd want to do it...I chose the nook so I could read for 15 days without charging :-P

Credit for this information should be given to Avram Piltch:  http://blog.laptopmag.com/nook-simple-touch-ereader-dramatically-improve-page-turns-with-a-firmware-...

[Sun_Cat]

---

JoeAtWork7 wrote:

Since I see there're a lot of people out there who want the web browser with version 1.1.0...here's how you access it:

...

Credit for this information should be given to Avram Piltch:  http://blog.laptopmag.com/nook-simple-touch-ereader-dramatically-improve-page-turns-with-a-firmware-...

---

Thanks, but this was already posted and discussed here back in December. It was without the link you gave, but I don't see any reference there to the browser workaround, so I'm not sure why you gave it as the source.

[JoeAtWork7]

Oh well, 0 for 2...copy/pasted the wrong link and totally didn't see someone had already mentioned this...

I guess for the record though, I might add that I updated to 1.1 last night with (so far) no signs of trouble...