09-17-2013, 07:31 AM | #16 |
Developer's Corner Mascot
Posts: 486
Karma: 1277790
Join Date: Sep 2013
Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4
|
Ok, I've found this in a chinese forum (translated with google):
From a practical point of view experience, more than 5M e-book is easy indexing fails (due to insufficient memory), repeated attempts lead to sustained power. My ultimate solution is to jailbreak, modify the internal java cvm virtual machine startup parameters, the memory limit from-Xmx20m raised to 30m. However, this process is too technical, the simple solution is not to put more than 5M books. It seems to be the java virtual machine memory limit... right? Could it help also in running smoothly KUAL apps? |
09-17-2013, 08:01 AM | #17 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
most kual apps run independent of that structure once launched.
but nice thought |
Advert | |
|
09-17-2013, 08:46 AM | #18 |
Addict
Posts: 250
Karma: 136662
Join Date: Apr 2011
Device: N/A
|
Please excuse my lack of knowledge here: what do you mean by no more than 5M e-books? Five million books?
|
09-17-2013, 08:48 AM | #19 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Five books whose title begins with M ?
- - - - - Those (and other) system limits are stored in a CRAMFS image file. The general process to change something would be: * Copy the CRAMFS image somewhere (perhaps off-kindle) * Mount the image * As 'root', do an exact copy of the files to a writable file system * Use the KDB utility to read/write/re-set the limit desired. * Re-create a CRAMFS image from the writable file system * **USE A TEMPORARY** means to make the system use your customized limits database image (such as a manual umount/mount sequence). Something you can recover from with a full re-boot. * Close (i.e: Stop) anything that was using the old limits (such as kdb and cvm - both catch the settings). You **MUST** get the old files 'closed' somehow (because of how inode file systems work). * Restart whatever you stopped, in the proper order * test until you are blue in the face. then test some more. (If you are normally blue skinned, test until you are red in the face.) Only then consider replacing the Amazon CRAMFS image file with your customized image file. Last edited by knc1; 09-17-2013 at 09:01 AM. |
09-17-2013, 09:14 AM | #20 |
Developer's Corner Mascot
Posts: 486
Karma: 1277790
Join Date: Sep 2013
Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4
|
|
Advert | |
|
09-17-2013, 10:07 AM | #21 |
Addict
Posts: 250
Karma: 136662
Join Date: Apr 2011
Device: N/A
|
|
09-18-2013, 02:55 AM | #22 |
Connoisseur
Posts: 67
Karma: 70690
Join Date: May 2013
Device: Kindle Paperwhite 1 & Kindle 4 Black
|
Nice to see you again.
Maybe there is something wrong with my method, If everyone can help to feedback the problem, I will be work better! Thank you for everyone! |
09-19-2013, 06:12 PM | #23 | |
Member
Posts: 11
Karma: 10
Join Date: Aug 2013
Device: Kindle PW
|
Quote:
the debug commands dont even work on the PW |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Disable indexing (search) = longer battery life! | statethatiamin | Kindle Developer's Corner | 58 | 05-02-2012 07:58 AM |
Question about disable indexing permanently by disabling access to "Search Indexes" | WS64 | Kindle Developer's Corner | 1 | 12-17-2011 05:51 PM |
Hacks DXG disable indexing without jailbreak? | Bricorn | Amazon Kindle | 10 | 10-08-2011 07:20 AM |