Mobileread
Instructions for patching firmware 4.24.15676
#11  jackie_w 09-26-2020, 02:33 PM
Quote Ripplinger
Is there any way or any possibility of removing "Discover" from the bottom of the new home screen?
Do you mean the label "Discover" or do you mean the whole button?

The former might be possible (I haven't looked) but the latter may pi$$ off Kobo (because it's a route to the Kobo store) so is less likely to be created as a patch, even if it was possible.
Reply 

#12  yoman 09-26-2020, 03:19 PM
Ripplinger. Just a thought but, it might be possible to down grade to a previous version.

Quote Ripplinger
Is there any way or any possibility of removing "Discover" from the bottom of the new home screen?
Reply 

#13  Ripplinger 09-26-2020, 06:39 PM
Quote jackie_w
Do you mean the label "Discover" or do you mean the whole button?

The former might be possible (I haven't looked) but the latter may pi$$ off Kobo (because it's a route to the Kobo store) so is less likely to be created as a patch, even if it was possible.
I'd settle for just the label being gone, but that would mean moving the hamburger "More" label over as well. Probably too much of a hassle if very few people would use it. Discover is something I'd never use, I don't remember the last time I bought a book from Kobo actually, most have been from Amazon lately. But I never purchase any book directly through a reader, I prefer to keep them all in one spot on my PC so only purchase through the PC and sideload them to the readers. Which also has the advantage of being able to leave wifi off so never being surprised by new firmware, also uses less battery never syncing.

Quote yoman
Ripplinger. Just a thought but, it might be possible to down grade to a previous version.
I've been staying on 4.20.14622, just before the newest homescreen change, but I wanted to give the newest firmware a good try though with the new dictionaries.

I remember being able to hide all the clutter from the old hamburger menu at the top left of the old homescreen (DropBox, Pocket, Store, Wishlist and Activity) so had the idea it was pretty much in the same category to be rid of things you never use. And since I use the Miniclock add-on, moving the "More" label where "Discover" currently is makes perfect room for where I position the clock.
Reply 

#14  jackie_w 09-26-2020, 07:06 PM
Quote Ripplinger
I remember being able to hide all the clutter from the old hamburger menu at the top left of the old homescreen (DropBox, Pocket, Store, Wishlist and Activity) so had the idea it was pretty much in the same category to be rid of things you never use. And since I use the Miniclock add-on, moving the "More" label where "Discover" currently is makes perfect room for where I position the clock.
I had a similar issue myself with the new Navbutton labels being in the way of MiniClock in the bottom right corner.

It's solved now with @geek1011's latest (experimental, not yet released) version of NickelMenu but, before that was an option, I made a quick and dirty patch for nickel.yaml which caused all 4 Navbutton labels to be displayed white-on-white, i.e. "invisible labels". You would still see the 4 icons. I could post that here if it would be of any use to you?
Reply 

#15  Skydog 09-26-2020, 07:20 PM
Quote Ripplinger
Is there any way or any possibility of removing "Discover" from the bottom of the new home screen?
Another vote here for removal of "Discover"!
Reply 

#16  Ripplinger 09-26-2020, 10:35 PM
Quote jackie_w
I had a similar issue myself with the new Navbutton labels being in the way of MiniClock in the bottom right corner.

It's solved now with @geek1011's latest (experimental, not yet released) version of NickelMenu but, before that was an option, I made a quick and dirty patch for nickel.yaml which caused all 4 Navbutton labels to be displayed white-on-white, i.e. "invisible labels". You would still see the 4 icons. I could post that here if it would be of any use to you?
It doesn't look bad as it is now for me, the clock just covers the text "More", but the full icon shows and can be accessed just hitting the hamburger. While it's not perfectly aligned as it is when within a book, it's only 3 pixels too high so doesn't look bad for as little time as I spend on the homescreen. I'll leave well enough alone with Miniclock versions since it now works perfectly for me (I'm using v20200202).
screen_003.png 
Reply 

#17  Terisa de morgan 09-27-2020, 08:32 AM
I have a "small" problem:
Spoiler Warning below






runtime: out of memory: cannot allocate 638025728-byte block (1090355200 in use)

fatal error: out of memory

runtime stack:
runtime.throw(0x64a905, 0xd)
/usr/local/go/src/runtime/panic.go:774 +0x64
runtime.largeAlloc(0x26076314, 0x11360101, 0x44b283)
/usr/local/go/src/runtime/malloc.go:1140 +0x108
runtime.mallocgc.func1()
/usr/local/go/src/runtime/malloc.go:1033 +0x39
runtime.systemstack(0xe32f90)
/usr/local/go/src/runtime/asm_386.s:399 +0x53
runtime.mstart()
/usr/local/go/src/runtime/proc.go:1146

goroutine 1 [running]:
runtime.systemstack_switch()
/usr/local/go/src/runtime/asm_386.s:360 fp=0x11437a24 sp=0x11437a20 pc=0
x44e200
runtime.mallocgc(0x26076314, 0x608240, 0x1, 0x0)
/usr/local/go/src/runtime/malloc.go:1032 +0x684 fp=0x11437a78 sp=0x11437
a24 pc=0x40b0c4
runtime.makeslice(0x608240, 0x26076314, 0x26076314, 0x114823dc)
/usr/local/go/src/runtime/slice.go:49 +0x4f fp=0x11437a8c sp=0x11437a78
pc=0x43b1af
bytes.makeSlice(0x26076314, 0x0, 0x0, 0x0)
/usr/local/go/src/bytes/buffer.go:229 +0x69 fp=0x11437ac0 sp=0x11437a8c
pc=0x4c1ed9
bytes.(*Buffer).grow(0x114aed04, 0xf0, 0xf0)
/usr/local/go/src/bytes/buffer.go:142 +0x11c fp=0x11437ae8 sp=0x11437ac0
pc=0x4c199c
bytes.(*Buffer).Write(0x114aed04, 0x118381b4, 0xf0, 0xf8, 0xf0, 0x0, 0x0)
/usr/local/go/src/bytes/buffer.go:172 +0xb5 fp=0x11437afc sp=0x11437ae8
pc=0x4c1b95
compress/flate.(*huffmanBitWriter).write(...)
/usr/local/go/src/compress/flate/huffman_bit_writer.go:136
compress/flate.(*huffmanBitWriter).writeCode(0x118381a0, 0x8002d)
/usr/local/go/src/compress/flate/huffman_bit_writer.go:347 +0x15b fp=0x1
1437b24 sp=0x11437afc pc=0x4df89b
compress/flate.(*huffmanBitWriter).writeTokens(0x118381a0, 0x11582000, 0x4001, 0
x4001, 0x12b6a900, 0x11e, 0x11e, 0x17174300, 0x1e, 0x1e)
/usr/local/go/src/compress/flate/huffman_bit_writer.go:583 +0xa2 fp=0x11
437b4c sp=0x11437b24 pc=0x4e06a2
compress/flate.(*huffmanBitWriter).writeBlock(0x118381a0, 0x11582000, 0x4001, 0x
4001, 0xd100, 0x1154916d, 0x403e, 0x6e93)
/usr/local/go/src/compress/flate/huffman_bit_writer.go:495 +0x312 fp=0x1
1437bb0 sp=0x11437b4c pc=0x4dff62
compress/flate.(*compressor).writeBlock(0x13364000, 0x11582000, 0x4000, 0x4001,
0xd1ab, 0x3, 0x0)
/usr/local/go/src/compress/flate/deflate.go:170 +0xa0 fp=0x11437bd4 sp=0
x11437bb0 pc=0x4dbb60
compress/flate.(*compressor).deflate(0x13364000)
/usr/local/go/src/compress/flate/deflate.go:506 +0x661 fp=0x11437c08 sp=
0x11437bd4 pc=0x4dcc41
compress/flate.(*compressor).write(0x13364000, 0x11cfdc00, 0x60d384, 0x38b984, 0
x60d584, 0xfc8ca35a, 0x1147ad60)
/usr/local/go/src/compress/flate/deflate.go:551 +0x69 fp=0x11437c24 sp=0
x11437c08 pc=0x4dd1c9
compress/flate.(*Writer).Write(...)
/usr/local/go/src/compress/flate/deflate.go:709
compress/gzip.(*Writer).Write(0x1144ef50, 0x11a7c000, 0x60d384, 0x60d584, 0x0, 0
x0, 0x15)
/usr/local/go/src/compress/gzip/gzip.go:196 +0xbd fp=0x11437cac sp=0x114
37c24 pc=0x4eb7bd
archive/tar.(*regFileWriter).Write(0x114040e0, 0x11a7c000, 0x60d384, 0x60d584, 0
x20676e69, 0x656c6966, 0xa)
/usr/local/go/src/archive/tar/writer.go:497 +0xdc fp=0x11437cd0 sp=0x114
37cac pc=0x4d107c
archive/tar.(*Writer).Write(0x114b6840, 0x11a7c000, 0x60d384, 0x60d584, 0x0, 0x1
1468660, 0x30)
/usr/local/go/src/archive/tar/writer.go:435 +0x57 fp=0x11437cfc sp=0x114
37cd0 pc=0x4d0da7
main.(*KoboPatch).ApplyFiles(0x114aed00, 0x0, 0x0)
/drone/src/kobopatch/kobopatch.go:579 +0x398 fp=0x11437e50 sp=0x11437cfc
pc=0x5a8ed8
main.main()
/drone/src/kobopatch/kobopatch.go:171 +0xa0d fp=0x11437fb0 sp=0x11437e50
pc=0x5a2f4d
runtime.main()
/usr/local/go/src/runtime/proc.go:203 +0x1e6 fp=0x11437ff0 sp=0x11437fb0
pc=0x42c0c6
runtime.goexit()
/usr/local/go/src/runtime/asm_386.s:1325 +0x1 fp=0x11437ff4 sp=0x11437ff
0 pc=0x44fb61
Reply 

#18  Terisa de morgan 09-27-2020, 08:33 AM
The problem is when I add different dictionaries, but as I can copy them manually, no problem at all.
Reply 

#19  geek1011 09-27-2020, 09:10 AM
Quote Terisa de morgan
I have a "small" problem:
Spoiler Warning below






runtime: out of memory: cannot allocate 638025728-byte block (1090355200 in use)

fatal error: out of memory

runtime stack:
runtime.throw(0x64a905, 0xd)
/usr/local/go/src/runtime/panic.go:774 +0x64
runtime.largeAlloc(0x26076314, 0x11360101, 0x44b283)
/usr/local/go/src/runtime/malloc.go:1140 +0x108
runtime.mallocgc.func1()
/usr/local/go/src/runtime/malloc.go:1033 +0x39
runtime.systemstack(0xe32f90)
/usr/local/go/src/runtime/asm_386.s:399 +0x53
runtime.mstart()
/usr/local/go/src/runtime/proc.go:1146

goroutine 1 [running]:
runtime.systemstack_switch()
/usr/local/go/src/runtime/asm_386.s:360 fp=0x11437a24 sp=0x11437a20 pc=0
x44e200
runtime.mallocgc(0x26076314, 0x608240, 0x1, 0x0)
/usr/local/go/src/runtime/malloc.go:1032 +0x684 fp=0x11437a78 sp=0x11437
a24 pc=0x40b0c4
runtime.makeslice(0x608240, 0x26076314, 0x26076314, 0x114823dc)
/usr/local/go/src/runtime/slice.go:49 +0x4f fp=0x11437a8c sp=0x11437a78
pc=0x43b1af
bytes.makeSlice(0x26076314, 0x0, 0x0, 0x0)
/usr/local/go/src/bytes/buffer.go:229 +0x69 fp=0x11437ac0 sp=0x11437a8c
pc=0x4c1ed9
bytes.(*Buffer).grow(0x114aed04, 0xf0, 0xf0)
/usr/local/go/src/bytes/buffer.go:142 +0x11c fp=0x11437ae8 sp=0x11437ac0
pc=0x4c199c
bytes.(*Buffer).Write(0x114aed04, 0x118381b4, 0xf0, 0xf8, 0xf0, 0x0, 0x0)
/usr/local/go/src/bytes/buffer.go:172 +0xb5 fp=0x11437afc sp=0x11437ae8
pc=0x4c1b95
compress/flate.(*huffmanBitWriter).write(...)
/usr/local/go/src/compress/flate/huffman_bit_writer.go:136
compress/flate.(*huffmanBitWriter).writeCode(0x118381a0, 0x8002d)
/usr/local/go/src/compress/flate/huffman_bit_writer.go:347 +0x15b fp=0x1
1437b24 sp=0x11437afc pc=0x4df89b
compress/flate.(*huffmanBitWriter).writeTokens(0x118381a0, 0x11582000, 0x4001, 0
x4001, 0x12b6a900, 0x11e, 0x11e, 0x17174300, 0x1e, 0x1e)
/usr/local/go/src/compress/flate/huffman_bit_writer.go:583 +0xa2 fp=0x11
437b4c sp=0x11437b24 pc=0x4e06a2
compress/flate.(*huffmanBitWriter).writeBlock(0x118381a0, 0x11582000, 0x4001, 0x
4001, 0xd100, 0x1154916d, 0x403e, 0x6e93)
/usr/local/go/src/compress/flate/huffman_bit_writer.go:495 +0x312 fp=0x1
1437bb0 sp=0x11437b4c pc=0x4dff62
compress/flate.(*compressor).writeBlock(0x13364000, 0x11582000, 0x4000, 0x4001,
0xd1ab, 0x3, 0x0)
/usr/local/go/src/compress/flate/deflate.go:170 +0xa0 fp=0x11437bd4 sp=0
x11437bb0 pc=0x4dbb60
compress/flate.(*compressor).deflate(0x13364000)
/usr/local/go/src/compress/flate/deflate.go:506 +0x661 fp=0x11437c08 sp=
0x11437bd4 pc=0x4dcc41
compress/flate.(*compressor).write(0x13364000, 0x11cfdc00, 0x60d384, 0x38b984, 0
x60d584, 0xfc8ca35a, 0x1147ad60)
/usr/local/go/src/compress/flate/deflate.go:551 +0x69 fp=0x11437c24 sp=0
x11437c08 pc=0x4dd1c9
compress/flate.(*Writer).Write(...)
/usr/local/go/src/compress/flate/deflate.go:709
compress/gzip.(*Writer).Write(0x1144ef50, 0x11a7c000, 0x60d384, 0x60d584, 0x0, 0
x0, 0x15)
/usr/local/go/src/compress/gzip/gzip.go:196 +0xbd fp=0x11437cac sp=0x114
37c24 pc=0x4eb7bd
archive/tar.(*regFileWriter).Write(0x114040e0, 0x11a7c000, 0x60d384, 0x60d584, 0
x20676e69, 0x656c6966, 0xa)
/usr/local/go/src/archive/tar/writer.go:497 +0xdc fp=0x11437cd0 sp=0x114
37cac pc=0x4d107c
archive/tar.(*Writer).Write(0x114b6840, 0x11a7c000, 0x60d384, 0x60d584, 0x0, 0x1
1468660, 0x30)
/usr/local/go/src/archive/tar/writer.go:435 +0x57 fp=0x11437cfc sp=0x114
37cd0 pc=0x4d0da7
main.(*KoboPatch).ApplyFiles(0x114aed00, 0x0, 0x0)
/drone/src/kobopatch/kobopatch.go:579 +0x398 fp=0x11437e50 sp=0x11437cfc
pc=0x5a8ed8
main.main()
/drone/src/kobopatch/kobopatch.go:171 +0xa0d fp=0x11437fb0 sp=0x11437e50
pc=0x5a2f4d
runtime.main()
/usr/local/go/src/runtime/proc.go:203 +0x1e6 fp=0x11437ff0 sp=0x11437fb0
pc=0x42c0c6
runtime.goexit()
/usr/local/go/src/runtime/asm_386.s:1325 +0x1 fp=0x11437ff4 sp=0x11437ff
0 pc=0x44fb61
That's because I currently read the entire file into memory.

I'll fix and release that next week (if you want to do it, it's just using os.Open to open the file, the file .Stat to get the size for the tar header, then io.Copy for writing to the tar).

That dictionary is quite large (638 MB). Does it have images?
Reply 

#20  Mrs_Often 09-27-2020, 12:08 PM
Quote geek1011
On Linux, you may have to press Ctrl+H to show the .kobo folder.
And on Mac, you may have to press Shift+Command+.
Reply 

 « First  « Prev Next »  Last »  (2/9)
Today's Posts | Search this Thread | Login | Register