Kob Firmware 2.3.2

[bartveld]

Originally Posted by Mrs_Often

Good luck! Waves of moral support flying your way

Well, that went well! Gone are the small letters in a new chapter and overall the device seems a bit snappier. I can't for the life of me imagine why this update hasn't been pushed out yet.

[GeoffR]

Originally Posted by bartveld

Are there any more of you who have installed 2.3.2? I'm still on the fence, but this fontsize-turns-minuscule-at-new-chapter thing is driving me nuts. Reading through this thread experiences are diverse, so I would like to hear more before I take the plunge.

The only change I noticed with 2.3.2 was that the new chapter-fontsize-bug had gone, no new bugs.

[Mrs_Often]

Originally Posted by bartveld

Well, that went well! Gone are the small letters in a new chapter and overall the device seems a bit snappier. I can't for the life of me imagine why this update hasn't been pushed out yet.

Glad you're rid of the font nonsense! Happy reading!

[z1984z]

Originally Posted by xor_

Sure. The attached KoboRoot.tgz sets the Kobo to run a custom script /mnt/onboard/run.sh at startup, and sets the root password to "banana". (You have to unzip it first, for some reason the board software complained when I tried to attach it directly.)

The attached dropbear.zip should be unpacked in /mnt/onboard

Then I put the line

/mnt/onboard/dropbear/dropbear -r /mnt/onboard/dropbear/kobokey

into my /mnt/onboard/run.sh script. This starts dropbear at startup. I guess you could also start it from the plugin instead.

Once you have it up and running, you could/should probably change the keyfile
/mnt/onboard/dropbear/kobokey

and change the root password.

Hope that helps.

Xor_, thank you very much!!!

I will try in a couple of weeks becouse I out of my home without a pc (only kobo and a tablet...). When I can back I'll do....

Again thank you!!!

[z1984z]

Originally Posted by xor_

Sure. The attached KoboRoot.tgz sets the Kobo to run a custom script /mnt/onboard/run.sh at startup, and sets the root password to "banana". (You have to unzip it first, for some reason the board software complained when I tried to attach it directly.)

The attached dropbear.zip should be unpacked in /mnt/onboard

Then I put the line

/mnt/onboard/dropbear/dropbear -r /mnt/onboard/dropbear/kobokey

into my /mnt/onboard/run.sh script. This starts dropbear at startup. I guess you could also start it from the plugin instead.

Once you have it up and running, you could/should probably change the keyfile
/mnt/onboard/dropbear/kobokey

and change the root password.

Hope that helps.

hi Xor_,

I try this yesterday and work´s like a charm!!!

Thank you very much and see you!!!!

[EldRick]

I can't for the life of me imagine why this update hasn't been pushed out yet.

Perhaps they are testing it, for a change.

[Dr. Drib]

I have firmware version 2.3.1 (r45611, 12/7/12)

I haven't done anything with my Kobo Glo since I got it.

Are there any 'compelling' reasons why I should get the newer firmware?




Don

[robko]

Originally Posted by Dr. Drib

I have firware version 2.3.1 (r45611, 12/7/12)

I haven't done anything with my Kobo Glo since I got it.

Are there any 'compelling' reasons why I should get the newer firmware?

Don

Unless you are running into one of the bugs and it's driving you nuts, then no there is no reason to jump to 2.3.2.

[jlynton]

On my GLO, fw 2.3.1 I had the new chatpter tiny font bug, so I went to 2.3.2, the font bug was cured, but I realised shortly that new books added to the device (micro sdcard) did not show their series info, despite having done the modifications in calibre referred to in this thread: http://www.mobileread.com/forums/sho...d.php?t=193184

So reluctantly, and I hope, temporarily, I have gone back to 2.3.1 :-(

[GeoffR]

Originally Posted by jlynton

On my GLO, fw 2.3.1 I had the new chatpter tiny font bug, so I went to 2.3.2, the font bug was cured, but I realised shortly that new books added to the device (micro sdcard) did not show their series info, despite having done the modifications in calibre referred to in this thread: http://www.mobileread.com/forums/sho...d.php?t=193184

So reluctantly, and I hope, temporarily, I have gone back to 2.3.1 :-(

Series info shows fine with 2.3.2 on my Glo.

[jlynton]

Originally Posted by GeoffR

Series info shows fine with 2.3.2 on my Glo.

Maybe I didn't make it clear, the books loaded before upgrading to 2.3.2 showed the series info properly on 2.3.2, but the books loaded after the upgrade did not show the info.

[Mrs_Often]

Originally Posted by jlynton

Maybe I didn't make it clear, the books loaded before upgrading to 2.3.2 showed the series info properly on 2.3.2, but the books loaded after the upgrade did not show the info.

Very weird. Are you sure you have the series information in the right place for the books you loaded after you upgraded to 2.3.2?

[davidfor]

Originally Posted by jlynton

Maybe I didn't make it clear, the books loaded before upgrading to 2.3.2 showed the series info properly on 2.3.2, but the books loaded after the upgrade did not show the info.

There is no difference in how 2.3.1 and 2.3.2 handle the series information. Or how calibre handles these firmware versions. But, calibre can't set the series information as it puts the books on the device, you have to reconnected to calibre after the device processes the books. Did you do this?

[volpo]

I have a Touch (v2.1.5) and a few series in my calibre library with the right series info entered in the proper metadata fields. The books are already loaded on the touch. What do I need to do to get series info into the touch?

Thanks,

V

[davidfor]

Originally Posted by volpo

I have a Touch (v2.1.5) and a few series in my calibre library with the right series info entered in the proper metadata fields. The books are already loaded on the touch. What do I need to do to get series info into the touch?

You have to upgrade your Touch to at least firmware 2.2.0. Otherwise, you use a metadata plugboard to put the series info into the title and put the books on the device again.