Skip to main content

Amazon Kindle support oddness

Amazon sent me an odd email regarding the cover for my Kindle.
Dear Kindle User,

We’re sending this note to remind you about proper attachment and use of your Kindle cover and about Amazon’s Kindle warranty. You can view instructions and illustrations here:
http://www.amazon.com/gp/help/customer/display.html?nodeId=200390460

ATTACHING THE COVER
To install the Kindle, open the cover and lay it on a flat surface. Then insert the bottom attachment hook on the cover into the bottom slot on the left edge of the Kindle. Rotate the Kindle to insert the top attachment hook. Then slide the switch down slightly to lock the cover attachment hooks in place.

Be sure to place the Kindle flat on the cover during installation. Do not tip the Kindle at an angle during installation, as that may cause the cover attachment hooks to bend.

USING THE KINDLE COVER
When using your Kindle with the cover, be careful to open the front cover only. If you open the back cover and pull the cover away from the Kindle, that may cause the attachment hooks to bend and could result in cracking or other damage to the Kindle.

THE AMAZON KINDLE WARRANTY
Your Kindle is covered by a One-Year Limited Warranty you can view here: http://www.amazon.com/kindlewarranty

If the attachment hooks on your cover have become bent, or your Kindle has developed cracking or other damage near the location where the hooks connect to the Kindle, please contact Kindle Support by phone or email regarding warranty replacement.

You can reach us via phone or e-mail through our website by clicking the Contact Us button on our help pages at http://www.amazon.com/kindlesupport or directly by calling one of these numbers:
Inside the United States: 1-866-321-8851, Outside the United States: 1-206-266-0927.

For more information, please see the Warranty Service section of the Kindle Return Policies Help page:
http://www.amazon.com/kindlereturnpolicy


Sincerely,
The Kindle Team

Comments

Popular posts from this blog

Installing Storytlr the lifestreaming platform

" Storytlr  is an open source lifestreaming and micro blogging platform. You can use it for a single user or it can act as a host for many people all from the same installation." I've been looking for something like Storytlr for a few months now or at least trying to do it with Drupal . While I love Drupal and FeedAPI  I did not want to spend all that time building a lifestream website. So I've been playing around with Storytlr instead and found it very easy. Here is how I got it up and running on a Ubuntu EC2 server. You can also check out the official Storytlr install instructions . Assumptions: LAMP stack installed and running. Domain setup for a directory. MySQL database and user ready to go. Lets get started! Get the code : wget http://storytlr.googlecode.com/files/storytlr-0.9.2.tgz tar -xvzf storytlr-0.9.2.tgz You can find out the  latest stable release  on Storytlr's downloads page. Import the database : Within protected/install is database.sq

Sync is currently experiencing problems

Update : I now recommend you install Google Chrome  and  disable  the built in Browser as it supports encrypting all synced data. After picking up a gorgeous  Galaxy Nexus yesterday I was running into an issue where my browser data wasn't syncing to the phone. After a little Googling I found this is commonly caused by having all of my synced Chrome data encrypted instead of the default of only encrypting the passwords. These are the steps I went through to get my dat syncing again without losing any of it. The exact error I was getting was "Sync is currently experiencing problems. It will be back shortly." In Google Chrome open the personal stuff settings page by clicking this link or by opening the wrench menu, and click on "signed in with example@gmail.com".  Hit "disconnect your Google Account" to temporarily disable syncing from your browser. Visit the Google Dashboard and "Stop sync and delete data from Google". I waite

A month of Flutter: a look back

Originally published on bendyworks.com . This is it. 31 blog posts in 31 days. Writing  a month of flutter  has been a ton of work but also lots of fun and a good learning experience. I really appreciate how supportive and and positive everyone as been. Publishing experience For the series I've been posting on  bendyworks.com ,  DEV ,  my personal blog , and  Medium . After publishing to these sites, I would put the Bendyworks link on  Twitter ,  Reddit , and the  Flutter Study Group Slack . Posting to DEV was easy as they use Markdown just like the Bendworks blog. DEV also has built in support for a  series of posts  so it's easy to read the entire series. I did have to manually upload any embedded images. DEV also has a number of  liquid tags  for embedding things like GitHub issues that I didn't make as much use of as I should have. Blogger is rich text so it was easy to copy/paste the rendered posts. This would hotlink all the images though so I had to rem