Can you make sure you patch the version string as well? If you don't change the version string, people who install the screensaver hack by tempering with the system configuration files are really going to confuse customer support moving forward. At least if you change the version string to something like "Version 2.0 + ScreenSaver Hack", then customer supports will include that as detail when they file bug report from customer. Devs really hate it when the details are skipped out when they investigate bug report.

stevenmoy from what I understand now, the patch only fixes the screensaver. It doesn't change anything else related to the version you have now, be it 2.0 or 2.0.1.

That's the problem. When customer contacts customer support, the support department needs to file report. If they forward that report to devs to investigate, devs really want to reproduce the problem, so they can fix it. Now with this bit of modification on the screensaver location, new scenarios are introduced. If devs aren't in the loop of that's happening, devs will be running circles and may not able to reproduce the problem. Pain for devs...

It's *extremely* unlikely that this particular patch would have an effect on any other component of the Kindle, but possible. Anyone who uses this patch and has a problem should be smart enough to revert back to their earlier version and reproduce the problem before reporting it to Amazon.

After using OS X for years, I've seen so many cases for pixi hacks on the systems. And every time Apple pushes out a software update, so many griefs are created on both sides... Both the users of the hacks and the devs who are assigned to investigate on root cause. Root cause analysis is time consuming and seriously frustrates the devs if they are hunting for ghosts due to an unintended system modification.

That's why if the update file is going to modify the configuration directory, I want to appeal to the author of the file to include a change on the version string. Such that those bug report will indicate a change on the system file.

I didn't want to do that because it doubles the complexity of the mod (quite literally, now we have to edit two files ).

However, you raise valid points, and God (Ken Thompson) created regular expressions for a reason. So I've gone ahead and done this. The big concern was that every change that's made has to be able to be revoked or else official updates will fail when they can't get the correct checksums on the files. So I had to do some testing to make sure everything was kosher.

That's the problem. When customer contacts customer support, the support department needs to file report. If they forward that report to devs to investigate, devs really want to reproduce the problem, so they can fix it. Now with this bit of modification on the screensaver location, new scenarios are introduced. If devs aren't in the loop of that's happening, devs will be running circles and may not able to reproduce the problem. Pain for devs...

Maybe that will lead to that the functionality will be introduced in the standard firmware since the cost to handle all these problems will be high.

After using OS X for years, I've seen so many cases for pixi hacks on the systems. And every time Apple pushes out a software update, so many griefs are created on both sides... Both the users of the hacks and the devs who are assigned to investigate on root cause.

As a developer I have been on both sides of the. When people change you software or use it as no intended and have problems, they expect you to fix it.

This is always why as a user I resist installing hacks that are out side of the standard expected configuration methods.

This is also why as a developer I strive to ensure that there are planned extension points that won't cause as much pain during updates. Document them so the users know what you expect. It is not always easy to do.

This is why I am very surprised that the kindle doesn't allow for "screen saver" images to be changed by the users. It is obvious if you looked around that people were doing in on the K1... and to expect that they would want do it on the K2.

THe only motivation I can think of that they don't want you doing this is because they are going to rotate those images when you are connected to whispernet with ads. TiVo puts ads on its menu to increase there revenue. I would not be at all surprised if Amazon started doing this once they have a captive audience of Kindle users.

It's painful and really not constructive via this venue. kindle2-feedback [at] amazon.com is the way to suggest and argue for enhancement. If you have looked at things that users ask for from Kindle 1, many improvements have been made on the Kindle 2 front. Amazon has been a customer focus company for a long time, the brand is built around that. Customer feedbacks does matter in Amazon world.

To pilotbob:

The screensaver feature in Kindle 1 isn't on the official list to start with... It's likely that the devs who put it in got in enough trouble already... That's why I have been encouraging users to go through official channel to suggest to Amazon that custom screensaver is a feature they would really want and enhance users' experience. That way, users get what they want and customers can get the proper official support when its needed. Devs are rarely at odds with the users because they want to delight the users as well.

I'm seeing the same blank images. At first, I thought I had done something wrong - the blank image appeared first!!! When I saw wilsondm2's post, I tried sleep/wake/sleep and finally saw my image, so my heart started again. Repeated use of the power key is showing that it's consistently every odd image (1-3-5) that's coming up blank.

Thanks so much for figuring this out - I'd much rather see my puppies than dead authors.