MobileRead Forums - View Single Post - Can "Active Content" damage the system partition?

NiLuJe · 11-08-2014, 04:13 PM

It's actually still there, but it simply doesn't support the new devices. (If the full Kindlet framework were gone, you wouldn't even be able to sideload azw2 files and have them show up on the Homescreen [and/or registered to the relevant backend]).

It's similar to what happened when the 4GB PW2 came out on FW 5.4.3.2: the FW didn't know about the new devices, couldn't figure out which device the Active Content was running on, and since that device check is mandatory, the launch is aborted...

Given the response from Kindle's CS, it would appear to have been done on purpose this time, although the method they chose to employ is quite a bit puzzling...

[And, again, hitting and failing that device check is completely harmless for the system].

11-08-2014, 04:13 PM	#12
NiLuJe 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	It's actually still there, but it simply doesn't support the new devices. (If the full Kindlet framework were gone, you wouldn't even be able to sideload azw2 files and have them show up on the Homescreen [and/or registered to the relevant backend]). It's similar to what happened when the 4GB PW2 came out on FW 5.4.3.2: the FW didn't know about the new devices, couldn't figure out which device the Active Content was running on, and since that device check is mandatory, the launch is aborted... Given the response from Kindle's CS, it would appear to have been done on purpose this time, although the method they chose to employ is quite a bit puzzling... [And, again, hitting and failing that device check is completely harmless for the system]. Last edited by NiLuJe; 11-08-2014 at 04:17 PM.