K5 JBPatch

[April_7th]

Originally Posted by ixtab

It all depends on how you ask.

and what was wrong with my question exactly?

[ixtab]

Originally Posted by April_7th

and what was wrong with my question exactly?

That you obviously didn't bother to read the 3.1.1 announcement. That you don't bother to use correct capitalization in your sentences. That your entire question sounded more like "Where is my progress bar patch?!".

Off-topic discussion concerning this topic ends here, at least for me.

[April_7th]

Originally Posted by ixtab

That you obviously didn't bother to read the 3.1.1 announcement. That you don't bother to use correct capitalization in your sentences. That your entire question sounded more like "Where is my progress bar patch?!".

Off-topic discussion concerning this topic ends here, at least for me.

yeah, you should really work with your perception..
though you're right about capitalizations.

thank you for jbpatch..

[corpcd]

Installed JBpatch on my KT 5.3.2, perfect!

In a poll for new features to add to JBPatch I'd vote for adding covers to collections. I dont know it that is possible using a hack.

[GoSharks]

Originally Posted by ixtab

Paperwhite 5.3.3 users:
Please don't spam this thread asking when there will be a version for Firmware 5.3.3. I'm not a patch-porting machine, and it will be released when it's ready. If Amazon weren't re-obfuscating their classes with every new firmware release, almost all of the patches would simply work on all firmware versions, and the time and energy could actually go into the development of new useful patches. But Amazon are really doing a great job in transforming patch development from an interesting and challenging hobby into a boring and tedious maintenance nightmare. WTF is wrong with you, lab126?!

Just wanted to let you know how much I appreciate the effort you put into this "interesting and challenging hobby". Now that you have me hooked on hyphenations, I don't want to go without! Thanks! (5.3.1 airplane moded and waiting patiently )

[twobob]

For my part I see this as just one more reason to step away from stuff relating to the obfuscated underbelly.

replace not amend.

[ixtab]

Originally Posted by twobob

For my part I see this as just one more reason to step away from stuff relating to the obfuscated underbelly.

replace not amend.

100% agreed - except that this is totally impossible in the case of JBPatch, because the underbelly is exactly what it was created for.

If the first versions of the firmware had been obfuscated as badly as the current ones are, JBPatch would never have been written in the first place. At the time, it was interesting and fun - but now, it's absolutely not anymore.

[twobob]

The Man is Cruel.

[TheSacredSoul]

Ah, I was under the delusion JBPatch was working fine since I had installed it on PW newly upgraded to 5.3.3. But alas, just realized hyphenation isnt working. Shall wait patiently!

[Dylan Tomorrow]

@Lab126 & Amazon: WTF! Way to be short-sighted idiots and hurt your own ecosystem long-term ... Loyalty is built by being awesome, not by being dicks to your community! How about you treat the devs here like you treat all the self-publishing writers, as valuable partners you can profit from? Urgh!

@Ixtab: Thank you for all the hard work on JBPatch sofar! It's a damn shame lab126 basically killed it for new firmware with their obfuscation bullshit. No-one can demand you to do thankless funless tedious code rewrites that add no functionality at all over and over again ...

I am just going to stay with the older firmware on my Touch then. My kindle would be way less fun to use without the custom font sizes and Fertigo as my reading font and the progress bar, so thanks for developing all that! Also, the framework is so damn buggy especially with sideloaded ebook files with less than perfectly valid HTML in them that I am rather glad I have a in-GUI option to "killall cvm" in JBPatch and Font Hack.

Plus thanks to all you other devs for developing the jailbreak. Thanks for the screensaver hack! And thanks for the USBNet hack! Being able to connect to my KT via SSH and look at the syslog in real time helped me understand more and more how it works and how I can sidestep some of its bugginess in using it. It made it less this frustrating closed-off mystery blackbox device and more like a linux tablet I can understand a bit and play around with and fix via console when it has issues just like my linux PC .

[n0b0]

Thank you so much for this patch! I was a bit worried with this, since a really like my kindle (and it is bought in the US, but i live in Denmark).
I purchased the Kindle to read books (obviously), but also to read academic texts, but these are always posted in PDF and Kindle's default reader has HUGE margins. With this patch I'm easily able to read these text on the Kindle.
THANK YOU!

Also:
Will the margin-patch (which is the only patch I use) work if I install 5.3.3 or should I keep it in flight mode for now?

[DuckieTigger]

Originally Posted by n0b0

Will the margin-patch (which is the only patch I use) work if I install 5.3.3 or should I keep it in flight mode for now?

No, the margins won't work yet in 5.3.3.

[n0b0]

I'll just keep it in flight mode then, thanks

[Fianor]

I am having trouble updating/uninstalling JBpatch 2.2.1. I am getting some error, I think it has a 006, but I'm not sure because the error code writes on top of the previous line. I have tried both install and uninstall and both give the error code.

I am trying to upgrade my KT to 5.3.2 and it won't update from USB, I was seeing some indication that I would need to uninstall JBPatch for the update to work.

Any help would be appreciated.

edit:
the error is unsupported init.xargs and then another error overwrites teh init.xargs line with something mentioning 006, the KT keeps scrolling on by while I'm trying to see exactly what they say.

edit2:
Nevermind, ignore the idiot here, I was trying the 5.3 version, because apparently I'm stupid.

[Reagal]

No news of JBpatch update for 5.3.3 PW users yet?

Sure Ixtab is working hard for us, i think.

See soon.