Connection Kobo to new Macbook Pro

[johnnyb]

Originally Posted by PeterT

How is the database architecture sensetive?

Sent from my Nexus 7 using Tapatalk

Because it's one big database in one file... If parts of the file get corrupted, everything tends to fall apart much quicker...

[DNSB]

Originally Posted by johnnyb

Because it's one big database in one file... If parts of the file get corrupted, everything tends to fall apart much quicker...

Are you suggesting that if they used separate database files, it would somehow be better? Gee, we only lost part of the information so it's all useless anyways.

Have you looked at the design of SQLite? Check this link for more information: How To Corrupt An SQLite Database File paying special attention to the first paragraph. Then read the rest to help give some basis to paranoia about database corruption.

[johnnyb]

Originally Posted by DNSB

Are you suggesting that if they used separate database files, it would somehow be better? Gee, we only lost part of the information so it's all useless anyways.

Have you looked at the design of SQLite? Check this link for more information: How To Corrupt An SQLite Database File paying special attention to the first paragraph. Then read the rest to help give some basis to paranoia about database corruption.

Somehow unconvincing when the Kobos I owned over the past years all suffered from corrupt databases at some point...

[PeterT]

For a long time some of the mods for Kobo caused database corruption because they installed on the same partition as the database and books, kept files open on that partition which prevented the dismount of that partition when the device was connected via USB.

Another source of corruption is file system corruption caused by not correctly ejecting the device after a USB connection.

Sent from my Nexus 7 using Tapatalk

[johnnyb]

Originally Posted by PeterT

Another source of corruption is file system corruption caused by not correctly ejecting the device after a USB connection.

Yup, exactly my point. And this thread is about Kobo not connecting properly and losing connection randomly. It's just puzzling how they couldn't figure out stable USB connections in 2018.

[davidfor]

Originally Posted by johnnyb

Yup, exactly my point. And this thread is about Kobo not connecting properly and losing connection randomly.

Yes it is. So why did you bring up the database issues and then not expect others to discuss it?

[davidfor]

Originally Posted by DNSB

Have you looked at the design of SQLite? Check this link for more information: How To Corrupt An SQLite Database File paying special attention to the first paragraph. Then read the rest to help give some basis to paranoia about database corruption.

Interesting. I feel like there have been less issues since Kobo change to write-ahead logging. I was also forced to change the SQLite library used to support this, so that might have helped as well. For Windows calibre users at least.

I'll have to think about some of the other things mentioned on that page. And workout exactly what SQLite versions are involved.

[johnnyb]

Originally Posted by davidfor

Yes it is. So why did you bring up the database issues and then not expect others to discuss it?

Because the random connection losses caused by the USB drivers that Kobo just cannot seem to get right can cause database corruption (among other problems less severe but equally annoying).
I am being honest: I got an h2o ed2 on the cheap and I was totally looking forward to using it. The first thing I noticed: I have to stand on my head and whistle a tune to get it to connect to my computer which I will have to do quite often because Kobo does not allow my books into the cloud. My experience tells my that after half a year of random disconnects something will snap and I will have to factory reset, thereby losing all my notes and stats irretrievably.
Everytime I get a Kobo I hope that something will be different. Unfortunately it never really is. Kobo is a really crappy product. It‘s crap dressed up with nice font and page controls, but that does not make it not crap.

[davidfor]

Originally Posted by johnnyb

Because the random connection losses caused by the USB drivers that Kobo just cannot seem to get right can cause database corruption (among other problems less severe but equally annoying).

Not in my experience. As I have commented in another thread here today, I do have some disconnect issues relating to the exact cable and port choice. At no time have I had a corrupt database when this has happened. But, I have had corrupt databases when I accidentally knocked the cable out of my laptop.

And I don't see how corrupt database could be a result of the problem that the OP reported. The problem is the their Mac won't see the device. That's a big problem. But, can you tell me how that could possibly be causing a corrupt database?

[Terisa de morgan]

Uninteresting post.

[Terisa de morgan]

Originally Posted by moortjekras

Hi everyone,

I just bought a new MacBook Pro which doesn't have any USB ports anymore, so you would have to use a connecting piece. However, I can't seem to be able to connect my Kobo to my laptop anymore. It doesn't show on the desktop, nor via the Kobo app, I have tried all ports on the connecting piece and different cables, but none of it seems to work.
Do you have any other ideas?

Many thanks!

I haven't read this. I'm afraid that the problem could be the adaptor USB-C - USB (that I guess is what you're using as Apple, in its infinite wisdom, has decided to ditch USB ports to put USB-C ports).

[johnnyb]

Originally Posted by Terisa de morgan

I haven't read this. I'm afraid that the problem could be the adaptor USB-C - USB (that I guess is what you're using as Apple, in its infinite wisdom, has decided to ditch USB ports to put USB-C ports).

I honestly think that it may be the adaptors, cables and ports. However, in my case, they all work well with all other devices, just not the H2O2 (and the older H2O I used to own).
I think Kobo is to blame for this, for their flawed implementation of the USB standard.

[MGlitch]

I haven't had these issues with my H2O, KA1, or Forma on my Mac Mini or iMac 5k 2017.

I've use both the cable Kobo provides and an old cable from one of my Nooks.

I've run into the issue of Calibre not being able to process the database, but I suspect that was due to corrupt database since the Kobo mounted. And I hardly blame Kobo for that since I have run various mods and patches on all my Kobos, some of which had a history of possibly causing database corruption.

[Terisa de morgan]

Originally Posted by johnnyb

I honestly think that it may be the adaptors, cables and ports. However, in my case, they all work well with all other devices, just not the H2O2 (and the older H2O I used to own).
I think Kobo is to blame for this, for their flawed implementation of the USB standard.

That's your opinion. I disagree as I haven't had any problem with my Lobos (Mini, Touch, Glo, Aura, HD, Aura Ed2, Aura One, Clara, Forma only one connection till now). They are finicky with the wires, but not more than my PRS 350 was with the charger.

[NiLuJe]

@davidfor: Yeah, the switch to WAL was generally a Great Thing(TM), for a whole lotta reasons .

That leaves onboard's FS as a weak link, but switching away from FAT32 is kind of unrealistic (at least for the masses), unfortunately .

Amazon's approach was to hide the db away in a separate ext* partition, which is great for reliability and performance, but absolutely terrible for customization, since we lost direct access to the db during USBMS.

----

To get back to the issue at hand, while I did encounter some weird USB being terrible issues at one point or another, I don't think I've *ever* had any issue since switching motherboard a while ago.
I've been using USB 2.0 ports in both cases, FWIW, and my issues were pretty much tied to the mxc platform in general, so, Kobo, Kindle, whatever, didn't make much difference .