12-11-2013, 09:35 AM | #721 |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Nah, not sold out. But obviously the logistics company prefers to let it lay around for 10+ days in some of its dispatch centers instead of shipping it.
Still unsure about whether/when it will eventually arrive - but Amazon has now arranged a replacement shipping. So I assume that I'll eventually get two of them, of which I'll have to send one back Last edited by ixtab; 12-11-2013 at 09:39 AM. |
12-11-2013, 04:07 PM | #722 | |
Connoisseur
Posts: 95
Karma: 5854
Join Date: Aug 2011
Device: none
|
I think I need help here pls.
I tried to follow the instructions in the first post. Before that I used jailbreak for my PW2 (5.4). Before I waste mine and your time - I assume at the moment none of these instructions are of any use since the CM won't work with PW2 vs. 5.4x, right? But if it would or if it will soon, my problem is this: 1. Jailbreak - done 2. CM Followed links to [Kindle] Unified Application Launcher. KUAL (V 2.2) UPDATE v 2.2: followed link again, got the tar, installed the update_kindlet-dev-20130710-k5-ALL_install.bin went back to the CM thread, and am stuck with Quote:
update_k5_ALL_PW_ALL_kindlet_jailbreak_install.bin in the prerequisites-all-supported-devices.zip All I have is update_kindlet-jailbreak-20121029_install.bin Shall I install this? I am confused and lost, jumping forward and backward .. But maybe it wouldn't work anyway and everything starts again when there are updates for vs 5.4 available. |
|
Advert | |
|
12-11-2013, 05:56 PM | #723 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
I have now modified the initial post to be more up to date. It's not really difficult - CM really just needs a jailbroken device with the dev certificates and the Kindlet Jailbreak installed. But as Amazon is constantly trying to screw us, all of these three are somewhat moving targets. The current first post is probably as good as it can be right now (BTW, NiLuJe, you deserve a MASSIVE thank you for keeping up with the constant changes! Really, everybody who reads this, give NiLuJe some Karma for his continued effort!) That said, yes, the best that you will get in CM right now is something along the lines of "Your Kindle is running Firmware 5.4.x, which is not currently supported by Collections Manager". If you get to that message, it means that CM as such can -- in principle -- run, but doesn't know how to handle your particular Firmware. Thanks to Amazon's "fuck independent developers, let's screw them over again and again" policy, CM has to needlessly be adapted to every firmware. And all of that said: yes, I will be looking into the FW 5.4.x changes. But as mentioned before, I can't promise anything, and I can only do that when I have a PW2 in my hands. |
|
12-11-2013, 06:11 PM | #724 |
but forgot what it's like
Posts: 741
Karma: 2345678
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
|
@ixtab, did you look at Lua scripts in /usr/lib/ccat? In the end, stock Java code works with catalog database through these scripts anyway (and so is Collections Manager). Scripts are more readable than Java bytecode and even if they are slightly changed with firmware updates, changes are easlily tracked with simple diff'ing.
/usr/lib/ccat/worker.lua is executed for answering to HTTP requests to http://127.0.0.1:9101/. It recognizes POST requests to predefined endpoints with JSON-encoded POST data. This JSON request is transfromed by Lua script into SQL query to execute. Useful endpoints inculde http://127.0.0.1:9101/query endpoint for selecting from catalog database and http://127.0.0.1:9101/change endpoint for updating catalog database. Example of HTTP request: Code:
curl http://127.0.0.1:9101/query -d '{"type": "QueryRequest", "maxResults": 2}' Code:
local function logged (handler_name, post_data_handler) return function (post_data) llog.info("ccat_worker", handler_name, post_data, "") return post_data_handler(post_data) end end Code:
sed -ie 's/^\(_G.\+=\s*\)\([^.]\+\)\(\..\+\)$/\1logged("\2", \2\3)/g' /usr/lib/ccat/worker.lua Format of log entries is 'ccat_worker:<endpoint>:<JSON-encoded data>:' Here are sample log entries recorded right after invoking of Collections Manager from Home screen: Spoiler:
This is not my discovery, there was Kindle_Touch_Hacking#Collections and some old threads mentioned this way too. |
12-11-2013, 06:14 PM | #725 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@ixtab: You're not doing so bad yourself .
@eureka: Ooh, shiny! |
Advert | |
|
12-12-2013, 08:37 AM | #726 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
My own answer to the problem: "Find a manufacturer willing to cooperate with owner's after-market development - then pick the hobby device." The progress to date (and why readers are seeing less of twobob and myself here for awhile): The good news: A manufacturer has been found, and is convinced this type of relationship with the owners of their products is an advantage to themselves. (Yeah! Big win!) Work is underway to make this idea a reality, with the active support of the company. The bad (?) news: This manufacturer does not make e-ink display devices. (What can I say? I tried, but none of the e-ink device manufacturers I contacted want to be first.) When will the world know more about this? Probably sometime next spring, it's a big project. Just what is it all about: To keep the open source software Open (even after modification for the device) ; To keep company proprietary software Private ; And the big, catch-22 sounding goal: Keeping the device and firmware security system in-place that protects against malicious code at the same time as meeting the GPLv3 requirement that the owner can install code of their own choosing (including updates to the GPLv3 items). Leaving firms that are stuck with aging GPLv2 code due to their corporate policies in the dust of history. One possible side-effect - - The death of the Amazon Kindle Fire product line. But hey - it was Amazon's own policies that brought this all about. (Talk about shooting one's self in the foot. ) |
|
12-12-2013, 09:06 AM | #727 |
Member
Posts: 15
Karma: 10
Join Date: Nov 2013
Location: Germany
Device: Kindle Paperwhite (2nd gen)
|
But... isn't that part of the fun for many devs here, finding out a way to give back an even bigger fuck you to Amazon by cracking their "protection" from anything non-Amazon?
(well I guess mostly for the JB and system-"intrusive" hack developers, not for the rest...) But in any case, that sounds pretty awesome, knc1. A company that is interested in giving their customers full access to their product's potential? Shall they be praised! Last edited by chipf0rk; 12-12-2013 at 09:08 AM. |
12-12-2013, 04:49 PM | #728 | ||
Connoisseur
Posts: 95
Karma: 5854
Join Date: Aug 2011
Device: none
|
Quote:
Question: would it be of use (and possible) to downgrade the firmware then? The thought alone makes me sweat but I really really miss the easy working with Calibre and Kindle Collections. Quote:
If Amazon would listen to users and improve the Kindle users would be happy, Amazon would be happy (because sales might increase) and only developers will be bored. |
||
12-13-2013, 08:34 AM | #729 | |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
Different hardware inside, different CPU, different GPU. About the only thing the same between the PW2 and the earlier devices is the "Kindle" name. |
|
12-13-2013, 09:37 PM | #730 |
Fat Guy
Posts: 408
Karma: 24165
Join Date: Jun 2010
Device: Kindle Voyage
|
Did you get your pw2 yet ixtab?
|
12-14-2013, 05:17 AM | #731 |
Connoisseur
Posts: 52
Karma: 58450
Join Date: Jan 2013
Device: kindle NT, PW1, PW2, Kobo H2O
|
|
12-14-2013, 10:18 AM | #732 |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
|
12-14-2013, 11:40 AM | #733 |
Evangelist
Posts: 408
Karma: 1050547
Join Date: Mar 2011
Device: Kindle Oasis 2
|
Shit... I hope you get it earlier, that really sucks. What about the one that got stuck somewhere? Did it just magically disappear? Because if I recall correctly, you said that you had already contacted Amazon and they were planning on shipping another.
I also hope someone still has a 5.4.0 version, by the time you have your device and get around to developing the rescue pack... |
12-14-2013, 12:04 PM | #734 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
In the mean time, the first one's status is now "Exported and in transit to country of destination" - and has been so for *another* almost two weeks. I don't know if they transport the Kindles by bicycle, or fly them 10 times around the earth, or what. |
|
12-14-2013, 12:40 PM | #735 |
Member
Posts: 15
Karma: 10
Join Date: Nov 2013
Location: Germany
Device: Kindle Paperwhite (2nd gen)
|
It's a conspiracy, they don't want you to make a new Collections Manager version.
|
Tags |
collections, collections manager, kindle touch hacks |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Troubleshooting Books from collections are visible apart from the collections | splitloop | Amazon Kindle | 3 | 07-08-2012 01:03 PM |
ES File Explorer, Astro File Manager or File Manager HD? | DreamWriter | Android Devices | 15 | 04-05-2012 03:00 PM |
Importing Collections - Only original collections?? | kuklachica | Amazon Kindle | 6 | 01-20-2012 03:39 PM |
File manager and collections creator for PRS-505 | igorsk | Sony Reader | 19 | 02-12-2009 05:02 PM |