Call me paranoid but I used the second version of the start.sh ...
Originally Posted by arikfunke
@twobob - I realise this is too late now but it is safer to make a copy of the "start.sh" file which you then modify. Leave the original as it was so that the kindle always starts. To then test the framework do the following:
This way, if anything goes wrong it is enough to hit the power switch to hard-reset the device to its non-modified state.
So that's also an option for a less "permanent" or testing solution.
Will dig up some logs. The custom configuration I was using may have done something to make it "not work" last time. It was hardly an OOTB example device...
You can remove the warning mate
Log start timestamp: Wed Oct 24 21:39:59 GMT 2012
Bootstrap OK, PatchingClassLoader instantiated
Packages still handled by original ClassLoader:
JBPatch version 2.4.1: initializing patches
I: Directory synchronization thread started
I: Wed Oct 24 21:40:00 GMT 2012: synchronized
I: (builtin) DeviceInfo registered for
I: Patch policy initialized
was not found in configuration, adding entry and enabling patch
I: updated configuration file
I: File /var/local/jbpatch/com.mobileread.arikfunke.patch.
K3BrowserGoogleMobileSearchPatch-en.txt successfully initialized
registered for com.amazon.ebook.booklet.browser.resources.BrowserResources
search in browser for test
- success report.
extra little detail:
I: com.mobileread.arikfunke.patch.K3BrowserGoogleMobi leSearchPatch applied to com.amazon.ebook.booklet.browser.resources.Browser Resources (6c8c6e226e2f60e134fa7ccec784c4ce -> 96d802f5b0cef88cdf54a2407e263af8)
W: com.mobileread.arikfunke.patch.K3BrowserGoogleMobi leSearchPatch produced MD5 "96d802f5b0cef88cdf54a2407e263af8", but declared "?"
I recall the warning from the 5 but wasn't sure about the ? declaration so I thought I would report it.