[Device Plugin] Kobo Touch Extended Driver

[JSWolf]

If Mobi was unchecked as a supported format, would the on-the-fly conversion to KePub happen?

[jackie_w]

Originally Posted by davidfor

If calibre needs to do a conversion, it is done before the send. The result is added to the library and then sent.

Thanks for clarifying.

[mirage]

Am I the only one getting this message from calibre when uploading to a device, a Libra H2O in this case, since the latest firmware update? I just started seeing this message now, but I thought I'd uploaded books before since the update. But maybe I hadn't.

I should probably point out that I've done some patching and the NM/Plato/KOReader one step installation.

Your Kobo is running an updated firmware/database version. As calibre does not know about this updated firmware, database editing is disabled, to prevent corruption. You can still send books to your Kobo with calibre, but deleting books and managing collections is disabled. If you are willing to experiment and know how to reset your Kobo to Factory defaults, you can override this check by right clicking the device icon in calibre and selecting "Configure this device" and then the "Attempt to support newer firmware" option. Doing so may require you to perform a factory reset of your Kobo.
Device database version: 160.
Device firmware version: (4, 22, 15190)

I did check "Attempt to support newer firmware" and am not having any problems as far as I can see.

[davidfor]

Originally Posted by mirage

Am I the only one getting this message from calibre when uploading to a device, a Libra H2O in this case, since the latest firmware update? I just started seeing this message now, but I thought I'd uploaded books before since the update. But maybe I hadn't.

I should probably point out that I've done some patching and the NM/Plato/KOReader one step installation.

Your Kobo is running an updated firmware/database version. As calibre does not know about this updated firmware, database editing is disabled, to prevent corruption. You can still send books to your Kobo with calibre, but deleting books and managing collections is disabled. If you are willing to experiment and know how to reset your Kobo to Factory defaults, you can override this check by right clicking the device icon in calibre and selecting "Configure this device" and then the "Attempt to support newer firmware" option. Doing so may require you to perform a factory reset of your Kobo.
Device database version: 160.
Device firmware version: (4, 22, 15190)

I did check "Attempt to support newer firmware" and am not having any problems as far as I can see.

Read the message again and think about it. Did your device update recently? Is there any discussion about this fact elsewhere that might give you a clue about what is happening?

Yes, there is some sarcasm in that as I'm tired of how little people attention people pay to this. Especially from someone who is active in the forums where this has been discussed many, many times.

[mirage]

Originally Posted by davidfor

Read the message again and think about it. Did your device update recently? Is there any discussion about this fact elsewhere that might give you a clue about what is happening?

Yes, there is some sarcasm in that as I'm tired of how little people attention people pay to this. Especially from someone who is active in the forums where this has been discussed many, many times.

I did a search for one of the lines in the message and it didn't turn up anything. And I did mention that I'd updated recently and suggested that I understood that this may have prompted the message. My purpose was not that I was hoping to get one of the most cliched possible responses on internet forums, rather it was whether others were seeing it, too, and was wondering if there were issues related. I guess I should have searched further than I did.

I've posted a fair amount the last ten days, but am otherwise new here and to Kobo devices. I got a couple within the last week after not having had an ereader for years. You'll forgive me for not having the level of familiarity you have. Or maybe you won't. I suspect that there are other arenas in which the tables might be turned. I hope that in those settings you're on top of things, even if you're new there, as you expect people to be here.

[NiLuJe]

@mirage: I don't think the message can be made any more explicit than that, and it isn't worded in any way that might make you think anything is actually going wrong, so I'm genuinely curious what you were thinking might have been going on given the context?

In the unlikely event there would be a chance for something actually going wrong, you'll find ample warning in the FW release thread, e.g., https://www.mobileread.com/forums/sh...69&postcount=7 (and, quite likely even before that, because betas).

[mirage]

Originally Posted by NiLuJe

@mirage: I don't think the message can be made any more explicit than that, and it isn't worded in any way that might make you think anything is actually going wrong, so I'm genuinely curious what you were thinking might have been going on given the context?

In the unlikely event there would be a chance for something actually going wrong, you'll find ample warning in the FW release thread, e.g., https://www.mobileread.com/forums/sh...69&postcount=7 (and, quite likely even before that, because betas).

I understood the warning message. Maybe I didn't make that clear enough. My questions were, and please remember I'm new, not to calibre, but to Kobo devices and therefore, their plugins, a) are others seeing this message too? Because maybe I'd done something via patches and other addons that set myself up for something others hadn't. And b) has anyone had problems that the warning message advised were possible?

Seems innocent enough to me. People could respond or not. I wasn't looking for a thousand lines. I've done dev work for more than 20 years, so I get what this stuff is about. If there's a warning, maybe there's potential for a bad outcome. I took the risk, what little there was, because the worst case would have been to reset the device and I understood the update to have been relatively minor. Getting back to where I was, even with the hacks, wouldn't have taken much time.

It's a discussion forum. Why not ask what others think about something that was a new sighting for me? If we all were out for dinner (if only we could be) and one of you asked what we thought of our dishes, would that be cause for me to snap at everyone and proclaim that millions of people had already given opinions on their food over the years and I should have consulted that instead?

Anyway, sorry to go on for so long. Thanks for clarifying what you might find objectionable without being rude about it. I'll go back to my book now.

[davidfor]

Originally Posted by mirage

I understood the warning message. Maybe I didn't make that clear enough. My questions were, and please remember I'm new, not to calibre, but to Kobo devices and therefore, their plugins, a) are others seeing this message too? Because maybe I'd done something via patches and other addons that set myself up for something others hadn't. And b) has anyone had problems that the warning message advised were possible?

Seems innocent enough to me. People could respond or not. I wasn't looking for a thousand lines. I've done dev work for more than 20 years, so I get what this stuff is about. If there's a warning, maybe there's potential for a bad outcome. I took the risk, what little there was, because the worst case would have been to reset the device and I understood the update to have been relatively minor. Getting back to where I was, even with the hacks, wouldn't have taken much time.

It's a discussion forum. Why not ask what others think about something that was a new sighting for me? If we all were out for dinner (if only we could be) and one of you asked what we thought of our dishes, would that be cause for me to snap at everyone and proclaim that millions of people had already given opinions on their food over the years and I should have consulted that instead?

Anyway, sorry to go on for so long. Thanks for clarifying what you might find objectionable without being rude about it. I'll go back to my book now.

I have to ask. Did you patch the firmware without reading the thread about the firmware release? If so, do you really think that is a good idea?

[JSWolf]

If there is an issue with new firmware and the current version of Calibre, it will be mentioned in the firmware thread.

[mirage]

Originally Posted by davidfor

I have to ask. Did you patch the firmware without reading the thread about the firmware release? If so, do you really think that is a good idea?

Yes, I did read the thread. Sorry to disappoint you. The changes struck me as fairly minor. I saw there that there were updated patches and read that thread. I used the patches I wanted. Later, when I got the warning message, I checked again to see if anyone had mentioned database changes. I didn't see anything. So I figured I'd be OK and that worst case, I'd reset the device. Again, it was something I hadn't seen before, so I figured I'd ask in a discussion forum what others thought about it.

Originally Posted by JSWolf

If there is an issue with new firmware and the current version of Calibre, it will be mentioned in the firmware thread.

Thanks. Much appreciated.

[davidfor]

Originally Posted by mirage

Yes, I did read the thread. Sorry to disappoint you. The changes struck me as fairly minor. I saw there that there were updated patches and read that thread. I used the patches I wanted. Later, when I got the warning message, I checked again to see if anyone had mentioned database changes. I didn't see anything. So I figured I'd be OK and that worst case, I'd reset the device. Again, it was something I hadn't seen before, so I figured I'd ask in a discussion forum what others thought about it.

But, did you really read it? The fact that you felt the need to ask the question that started this conversation, suggests that you didn't read it.

And so that there is no argument, post 7 in that thread.

[mirage]

Originally Posted by davidfor

But, did you really read it? The fact that you felt the need to ask the question that started this conversation, suggests that you didn't read it.

And so that there is no argument, post 7 in that thread.

Think what you want to think.

You might keep in mind that I don't develop for the device or calibre, that I've only had the devices for a little over a week, and that I haven't posted here 20,000 times. So my level of familiarity with the details and the implications of them is going to be different than yours.

My apologies to those who read this thread for being a part of these recent posts. I'll let this go as of this post.

[JSWolf]

Kindle Previewer 3.40.0 does not like max-width and max-height in CSS. Having either of both of these lines in CSS does not stop the conversion from happening.

[JSWolf]

I've decided that for anything semi-complex, KFX is a botch job. In the ePub I converted, it has an HTML file that display 5 maps and 2 family trees all full screen (One image to a page/screen). With KFX, this gets all botched.

Screen 1 = Map full screen (as full as you can get with the wide margins)
Screen 2 = 2 maps
Screen 3 = 1/2 screen map
Screen 4 = 1 map and 1 family tree
Screen 5 = 1 family tree full screen (as full as you can get with the wide margins)

The ePub and KF8 (conversion) display these images correctly.

[Beaupedia]

Originally Posted by mirage

Yes, I did read the thread. Sorry to disappoint you. The changes struck me as fairly minor. I saw there that there were updated patches and read that thread. I used the patches I wanted. Later, when I got the warning message, I checked again to see if anyone had mentioned database changes. I didn't see anything. So I figured I'd be OK and that worst case, I'd reset the device. Again, it was something I hadn't seen before, so I figured I'd ask in a discussion forum what others thought about it.



Thanks. Much appreciated.

Brand new Kobo owner and came here with the same question. These guys, especially davidfor, are being absolute jerks to you. There is really no reason for it. They could have chosen not to respond. It's disappointing and a major turnoff to have this be my first interaction here after getting my Kobo. Sorry you dealt with it. I can only hope others here are more patient, less condescending, and more kind.