Firmware 4.30.18838

[davidfor]

Originally Posted by Haesslich

Are we sure this patch includes the fix for the comic reader? I started having sync issues (won't connect, clock stops working, battery suddenly goes from full this morning to 1% this evening despite not being used most of the day) after opening a CBZ file with this version.

I'm doing a factory reset now after five failed WiFi syncs in a row. Also, it stopped connecting to my WiFi, even after the factory reset.

4.30.18838 definitely fixes an issue with the handling of CBZs and CBRs. But, that issue was causing problems when connecting to a PC via USB. It is unlikely to have changed anything related to syncing. But, if it did, it is more likely to reduce issues. And syncing doesn't sync anything about sideloaded books.

What are the actual symptoms of the sync failing? The sync popup shows the phase of the sync. Where was it getting to?

I did discover a syncing issue related to collection names. I had collections like "toRead" and "toRate". These are maintained via calibre. I changed the case of the values in the library to "ToRead" and "ToRate" to be consistent with the other values. After that, some of my devices would sync a couple of times, then start and never finish. After a bit of investigation, the issue turned out to be the change in case. One of the database updates in the firmware was failing because both "toRead" and "ToRead" existed and this caused a duplicate error in an index. There was also a bit of a loop as all my devices were syncing and different ones were hitting this at different times. Add in that I would connect one to calibre and that did some updates as well. The fix was to manually delete these collections on a device and sync them all. After that, syncing was fix, calibre was able to recreate the collections I wanted and there have been no problems since.

[Haesslich]

Originally Posted by davidfor

What are the actual symptoms of the sync failing? The sync popup shows the phase of the sync. Where was it getting to?

I did discover a syncing issue related to collection names. I had collections like "toRead" and "toRate". These are maintained via calibre. I changed the case of the values in the library to "ToRead" and "ToRate" to be consistent with the other values. After that, some of my devices would sync a couple of times, then start and never finish. After a bit of investigation, the issue turned out to be the change in case. One of the database updates in the firmware was failing because both "toRead" and "ToRead" existed and this caused a duplicate error in an index. There was also a bit of a loop as all my devices were syncing and different ones were hitting this at different times. Add in that I would connect one to calibre and that did some updates as well. The fix was to manually delete these collections on a device and sync them all. After that, syncing was fix, calibre was able to recreate the collections I wanted and there have been no problems since.

Plain old CBZ file without any metadata, synced over WiFi from Dropbox or from an HTTP server on my network. If you don't open the file, sync works fine (connects right away, doesn't hang trying to check for updates), but after reading more than 5-10 pages on, syncs fail to complete as they freeze on the "checking for updates" step.

This has happened with twenty different CBR and CBZ files, and it doesn't matter if there's only one on the device or if there are 50. I've seen it happen on the Libra H20 as well as my current Forma.

Back then, I'd be lucky to complete one sync in 30, waiting 20-40 minutes for a sync to finish. The only surefire fix was to do a factory reset (just repairing would fail, due to the sync issue) and to not open any CBR/CBZ files. Indexing the cover never triggered the issue - you had to get further into the file to do so.

The only collections they belonged to were the one created on the device itself, by the reader software. It's why, when you mentioned the bug with the sync was fixed on the Sage / Libra 2 firmware, that I had hoped I could sideload these again.

This NEVER happened on the older firmware, not up through to the Aura One. Only after that, when they stopped releasing devices with removable storage, did I start having issues. With CBZ and CBR files on the SD card, it never froze like this.

[cycojesus]

Originally Posted by Haesslich

Plain old CBZ file without any metadata, synced over WiFi from Dropbox or from an HTTP server on my network. If you don't open the file, sync works fine (connects right away, doesn't hang trying to check for updates), but after reading more than 5-10 pages on, syncs fail to complete as they freeze on the "checking for updates" step.

This has happened with twenty different CBR and CBZ files, and it doesn't matter if there's only one on the device or if there are 50. I've seen it happen on the Libra H20 as well as my current Forma.

Back then, I'd be lucky to complete one sync in 30, waiting 20-40 minutes for a sync to finish. The only surefire fix was to do a factory reset (just repairing would fail, due to the sync issue) and to not open any CBR/CBZ files. Indexing the cover never triggered the issue - you had to get further into the file to do so.

The only collections they belonged to were the one created on the device itself, by the reader software. It's why, when you mentioned the bug with the sync was fixed on the Sage / Libra 2 firmware, that I had hoped I could sideload these again.

This NEVER happened on the older firmware, not up through to the Aura One. Only after that, when they stopped releasing devices with removable storage, did I start having issues. With CBZ and CBR files on the SD card, it never froze like this.

Elipsa here, I'm having the sync issue for some days now. I noticed the battery would lose >50% overnight. I did a factory reset and it's still the same. Just this morning it's been syncing all night "looking for updates".

I didn't open (or have on device think) any CBZ/CBR.

I'm actually thinking about trying to see if I can get another unit through the warranty...

[anacreon]

Originally Posted by cycojesus

Elipsa here, I'm having the sync issue for some days now. I noticed the battery would lose >50% overnight. I did a factory reset and it's still the same. Just this morning it's been syncing all night "looking for updates".

I didn't open (or have on device think) any CBZ/CBR.

I'm actually thinking about trying to see if I can get another unit through the warranty...

I've noticed my Sage doing the same thing since this F/W only. I think it is a bug of the software, and changing the unit won't solve it.

[cycojesus]

Originally Posted by anacreon

I've noticed my Sage doing the same thing since this F/W only. I think it is a bug of the software, and changing the unit won't solve it.

Reading these last posts I think you're right, it looks like a software issue.

Since the release of the Sage and Libra 2 I'm having regrets getting the Elipsa but that's not how I'll be able to get rid of it.

I'll try downgrading to 4.28.17925

EDIT: downgrading to 4.28.17925 didn't fix the sync issue :|

[cycojesus]

Went "nuclear"!

Upgraded back to 4.30.18838 since downgrading to 4.28.17925 didn't solve the sync issue.
While the Elipsa was mounted I got into sqlite and nuked all shelves expect a few specific ones I actually use (prefixed by _)

DELETE FROM Shelf WHERE Name NOT LIKE "\_%" ESCAPE '\';
DELETE FROM ShelfContent WHERE ShelfName NOT LIKE "\_%" ESCAPE '\';

Also told calibre to not create shelves for series (since the kobo already manages that anyway. I think it was a leftover from a long time ago)

Now the Elipsa sync'd successfully.

I suspect it didn't like one or more shelf name, maybe with an 'É' in its name, or a '?'

Strangely the shelves are still visible on the device...

[compurandom]

Originally Posted by davidfor

I did discover a syncing issue related to collection names. I had collections like "toRead" and "toRate". These are maintained via calibre. I changed the case of the values in the library to "ToRead" and "ToRate" to be consistent with the other values. After that, some of my devices would sync a couple of times, then start and never finish.

I've had that problem for more than a year. I probably renamed a whole bunch of collections at once. Any suggestions how to fix it without manually deleting a couple hundred collections from the device?

It just gets stuck in "Checking for updates".

[Deobulakenyo]

Indicator light turns off even if turned ON in the setting during charging.

I hope this can be fixed by a patch.

[davidfor]

Originally Posted by compurandom

I've had that problem for more than a year. I probably renamed a whole bunch of collections at once. Any suggestions how to fix it without manually deleting a couple hundred collections from the device?

It just gets stuck in "Checking for updates".

Not really. I believe the issue I had was because some things are case sensitive and some are not. The way calibre manages the collections should match the way it is done through the UI, but, the case sensitivity, or using extended character sets might not match perfectly. I haven't played enough with that side of things for a while. Calibre has been doing a good job of this and it was only when I posted a list of my collections and someone asked why they looked like that, that I decided it was time to make them more consistent.

You can try what @cycojesus did. But, that doesn't completely remove the collections. They will disappear from the device, but, they will probably be synced back to the device later. But, the complete cleanup might fix it as the "bad" collections won't be there.

I would not delete the records, but would mark them for deletion. This would be:

UPDATE Shelf SET _IsDeleted = 'true', LastModified = CURRENT_TIMESTAMP;
UPDATE ShelfContent SET _IsDeleted = 'true', DateModified = CURRENT_TIMESTAMP;

After that, when you sync, it should delete the collections from the server. And if you have other devices, a sync will remove the collections from them as well. Then you can start fresh.

If you are using calibre for collection management, turn that off until you have done the above. You can connect for other reasons and make sure you get a couple of syncs to the Kobo server to make sure it is working. And if it doesn't work, we'll have to look at what else it could be. This solved the big problem I was having, but, I feel like there may be something else. But, I don't have a pattern yet.

[compurandom]

Ok, that got it to the point where it sync'ed a couple of overdrive books. But now it's stuck on "Loading content"... I still haven't been able to complete a sync.

When it gets stuck like this, turning off wifi and canceling the sync still leaves the sync indicator spinning. I think that in itself is a bug of some sort.

It seems like if I let it time out and then retry, sometimes it gets further.

[John F]

Has the charging behavior changed?

When I plugged in my reader to charge on older firmwares, the battery/charging level would update on the sleep screen. With this firmware, I need to unplug/plugin to see an updated level.

This is on a Forma.

[Sirtel]

Originally Posted by John F

Has the charging behavior changed?

When I plugged in my reader to charge on older firmwares, the battery/charging level would update on the sleep screen. With this firmware, I need to unplug/plugin to see an updated level.

This is on a Forma.

Yeah, same with the Sage.

[cycojesus]

Originally Posted by John F

Has the charging behavior changed?

When I plugged in my reader to charge on older firmwares, the battery/charging level would update on the sleep screen. With this firmware, I need to unplug/plugin to see an updated level.

This is on a Forma.

I thought so too but I saw the level being updated from time to time.

[John F]

Originally Posted by cycojesus

I thought so too but I saw the level being updated from time to time.

I'm curious what "time to time" is. I started it charging at 20%, waited quite a while, unplugged it and plugged it in, and it went to 80%.

[anacreon]

Originally Posted by John F

Has the charging behavior changed?

When I plugged in my reader to charge on older firmwares, the battery/charging level would update on the sleep screen. With this firmware, I need to unplug/plugin to see an updated level.

This is on a Forma.

Same here with Sage.