MobileRead Forums - View Single Post - Touch Processing Time: How long is too long?

VirgoGirl · 02-09-2012, 04:37 PM

Let me go step by step as to what's happening, maybe I've used the wrong words to describe what's going on. Xennex1170's first reply seems to address my issue, but they second one doesn't.

So this is what happens.
1) Connect my KT to my laptop, click the "connect" option.
2) Either add books to the SD through the KT or just check what's on the card.
3) use the "eject hardware" icon in Win 7.
4) Count to 10 and disconnect the usb cable.

This is where it sits on the black "connected, please eject before disconnecting" screen for what appears to be over 5 minutes now.

After those 5 minutes, it either goes back to the Home screen (if all I've done is browse the SD card) or it goes to the "Processing.." screen. If it goes to the "Processing..." screen, it only takes about less than 2 minutes to process the new stuff.

My concern is the lag between ejecting the KT and it moving to the next screen. If it's the KT scanning th card, then yes it makes sense that it would take a while to see if there are any changes. if it's not, then I'm not sure what it's doing- stopping for a coffee?

I've noticed that if I "delete" a book from my library that's on the SD, it will remove it from my library listing for that session. When I power up the KT again, that book gets "Processed" back into the library. That's fine, I don't want it deleting things from the SD card. So I'm thinking that if I remove the SD card form the KT, add the books directly to the SD card through a card reader, put it back into the KT and power it back on, it'll avoid that 5+ minute lag time between ejecting and processing. Hopefully it should go right into "Processing".

I don't add books directly into the KT memory, I don't trust that I will not lose them again. The firmware, while I found it had a Reading Life bug, is working as it should so I wasn't bothering to update again. Too many weird bugs have popped up for other users, at least mine is working and reading the SD Card.

Thanks again for your help!

02-09-2012, 04:37 PM	#9
VirgoGirl "Why is it doing that?" Posts: 322 Karma: 725344 Join Date: Sep 2011 Device: Black Kobo Touch & Glo, responsible for 2 PaperWhites	Let me go step by step as to what's happening, maybe I've used the wrong words to describe what's going on. Xennex1170's first reply seems to address my issue, but they second one doesn't. So this is what happens. 1) Connect my KT to my laptop, click the "connect" option. 2) Either add books to the SD through the KT or just check what's on the card. 3) use the "eject hardware" icon in Win 7. 4) Count to 10 and disconnect the usb cable. This is where it sits on the black "connected, please eject before disconnecting" screen for what appears to be over 5 minutes now. After those 5 minutes, it either goes back to the Home screen (if all I've done is browse the SD card) or it goes to the "Processing.." screen. If it goes to the "Processing..." screen, it only takes about less than 2 minutes to process the new stuff. My concern is the lag between ejecting the KT and it moving to the next screen. If it's the KT scanning th card, then yes it makes sense that it would take a while to see if there are any changes. if it's not, then I'm not sure what it's doing- stopping for a coffee? I've noticed that if I "delete" a book from my library that's on the SD, it will remove it from my library listing for that session. When I power up the KT again, that book gets "Processed" back into the library. That's fine, I don't want it deleting things from the SD card. So I'm thinking that if I remove the SD card form the KT, add the books directly to the SD card through a card reader, put it back into the KT and power it back on, it'll avoid that 5+ minute lag time between ejecting and processing. Hopefully it should go right into "Processing". I don't add books directly into the KT memory, I don't trust that I will not lose them again. The firmware, while I found it had a Reading Life bug, is working as it should so I wasn't bothering to update again. Too many weird bugs have popped up for other users, at least mine is working and reading the SD Card. Thanks again for your help!