| 
			
			 | 
		#1846 | 
| 
			
			
			
			 Enthusiast 
			
			![]() Posts: 32 
				Karma: 10 
				Join Date: Jan 2016 
				
				
				
				Device: PW3 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			I tried last image, cover and cycle mode and they all work.  
		
	
		
		
		
		
		
		
		
		
		
		
	
	   But random mode doesn't work,  it just stays in cycle mode. Should it work on fw 5.7.2? Thanks!
		 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1847 | 
| 
			
			
			
			 Going Viral 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 17,212 
				Karma: 18210809 
				Join Date: Feb 2012 
				Location: Central Texas 
				
				
				Device: No K1, PW2, KV, KOA 
				
				
				 | 
	
	|
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1848 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			@Mike_73: You're possibly reading KFX titles, in which case, use the snapshot version of the hack. 
		
	
		
		
		
		
		
		
		
		
		
		
	
	@kalyy: As @knc1 mentioned, the shuffling process is done when the hack starts up (which normally is at boot, or during a framework restart triggered from KUAL).  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1849 | 
| 
			
			
			
			 Enthusiast 
			
			![]() Posts: 32 
				Karma: 10 
				Join Date: Jan 2016 
				
				
				
				Device: PW3 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Yes I did a framework restart and also a device restart. 
		
	
		
		
		
		
		
		
		
		
		
		
	
	I just try it again kual->Screen savers->Restart framework now And configurations->Restart Whith the device restart I see the "S randomizing screensavers..." message and when I did the framework restart it showed a message in white letters for less than a second.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1850 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			@kalyy: The you misunderstood the behavior of the hack. it simply reshuffles the order in which the images will be shown, but it's still a cycle from 0 to 100, it's just that 'n' might not point to the same picture between two different boots.
		 
		
	
		
		
		
		
		
		
		
		
		
		
	
	 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1851 | 
| 
			
			
			
			 Enthusiast 
			
			![]() Posts: 27 
				Karma: 10 
				Join Date: Oct 2015 
				
				
				
				Device: Kindle pw2, NST 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			;dm gonna try that. 
		
	
		
		
		
		
		
		
		
		
		
		
	
	Wonder if you could add "custom picture" that has picture # and reason it failed? and cache THAT so screensaver cycle stays working? I will check into usbnetwork too, thanks.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1852 | 
| 
			
			
			
			 BLAM! 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506 
				Karma: 26047202 
				Join Date: Jun 2010 
				Location: Paris, France 
				
				
				Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			@XXCoder: Not feasible. Can't (easily) predict how the framework will handle some files  
		
	
		
		
		
		
		
		
		
		
		
		
	
	 .At best you could play with parsing identify's output to look for common issues, but, again, the best place to do that is outside the Kindle  .
		 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1853 | 
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,179 
				Karma: 11573197 
				Join Date: Feb 2011 
				Location: London, UK 
				
				
				Device: Voyage 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Is there a size limit after which the PW3 isn't happy? I resized my previously-used-on-PW2 images to the larger PW3 resolution and for some reason the PW3 doesn't like one of them - at the new res, it's 1.93MB whilst all the others (working fine) are between 300KB and 1.6MB
		 
		
	
		
		
		
		
		
		
		
		
		
		
	
	 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1854 | 
| 
			
			
			
			 Going Viral 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 17,212 
				Karma: 18210809 
				Join Date: Feb 2012 
				Location: Central Texas 
				
				
				Device: No K1, PW2, KV, KOA 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Any chance the conversion made other changes? 
		
	
		
		
		
		
		
		
		
		
		
		
	
	Such as from PNG8 to indexed grayscale - or any other such 'invisible' internal changes.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1855 | 
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,179 
				Karma: 11573197 
				Join Date: Feb 2011 
				Location: London, UK 
				
				
				Device: Voyage 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			I don't think so - I did exactly the same for all the images, and it's just this one the PW3 isn't happy with. I'll try the resize again later today just in case and see what happens.
		 
		
	
		
		
		
		
		
		
		
		
		
		
	
	 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1856 | 
| 
			
			
			
			 Going Viral 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 17,212 
				Karma: 18210809 
				Join Date: Feb 2012 
				Location: Central Texas 
				
				
				Device: No K1, PW2, KV, KOA 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			Are the PW-2 and PW-3 both running the same firmware version? 
		
	
		
		
		
		
		
		
		
		
		
		
	
	Why? During the lifetime of the PW-2 there was a png library version change, which may or may not be the problem here. The PW-3 has only used the new(er) png library. Otherwise - You may have just discovered a limitation of the ss display.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1857 | 
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,179 
				Karma: 11573197 
				Join Date: Feb 2011 
				Location: London, UK 
				
				
				Device: Voyage 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			The PW2 is still on 5.4.5.1; PW3 on 5.7.2. 
		
	
		
		
		
		
		
		
		
		
		
		
	
	All the other images I was using on the PW2 work fine on the PW3 at the new res  
		 | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1858 | |
| 
			
			
			
			 Going Viral 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 17,212 
				Karma: 18210809 
				Join Date: Feb 2012 
				Location: Central Texas 
				
				
				Device: No K1, PW2, KV, KOA 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
 Your PW-2 uses the old libpng, your PW-3 is using the new libpng. That is one certain difference. But if it is the cause of this inablity to handle the large file, I can't say.  | 
|
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1859 | 
| 
			
			
			
			 Wizard 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,179 
				Karma: 11573197 
				Join Date: Feb 2011 
				Location: London, UK 
				
				
				Device: Voyage 
				
				
				 | 
	
	
	
		
		
		
		
		 
			
			I've resized again from the original, and same problem. 
		
	
		
		
		
		
		
		
		
		
		
		
		
			That image was obviously smaller on the PW2, around 1MB. Ah well, one of those things I guess. Last edited by Yolina; 02-11-2016 at 02:09 PM.  | 
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
| 
			
			 | 
		#1860 | |
| 
			
			
			
			 Going Viral 
			
			![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 17,212 
				Karma: 18210809 
				Join Date: Feb 2012 
				Location: Central Texas 
				
				
				Device: No K1, PW2, KV, KOA 
				
				
				 | 
	
	
	
		
		
		
		
		 Quote: 
	
 If it works, then it is indeed the file size that is the problem on the PW-3.  | 
|
| 
		 | 
	
	
	
		
		
		
		
			 
		
		
		
		
		
		
		
			
		
		
		
	 | 
![]()  | 
            
        
            
| Tags | 
| kindle touch hacks, paperwhite, python, screensavers, touch | 
            
  | 
    
			 
			Similar Threads
		 | 
	||||
| Thread | Thread Starter | Forum | Replies | Last Post | 
| Problem installing Kindle ScreenSavers Hack | ratchetclank | Kindle Developer's Corner | 3 | 12-30-2015 10:59 PM | 
| Is it impossible to hack screensavers in K4 4.1? | nonfactor | Kindle Developer's Corner | 1 | 07-04-2012 08:17 PM | 
| Help! Used screensaver hack- now all collections gone and no screensavers!!! | kuklachica | Amazon Kindle | 1 | 01-16-2011 09:17 PM | 
| Is a hack necessary to add screensavers? | mldavis2 | Amazon Kindle | 4 | 10-29-2010 06:34 PM | 
| Hack for screensavers on Kindle 2 | KookyKathy | Introduce Yourself | 5 | 01-10-2010 12:16 AM |