Aura ONE Kobo Aura One owners thread

[ratinox]

Originally Posted by Iñigo

I've read exactly 0 people having USB issues with Linux, Apple or any Windows computer before Windows 10 Anniversary Edition, but the problem is caused by the Kobo device... of course!

Windows 7: no problems with any released firmware version.
Windows 10 AE: no problems with 4.2.8110 or 4.2.8283.
Macintosh: no problems with 4.2.8110.
Linux: no problems 4.2.8110.

One important point: Kobo device enumeration changes with firmware changes. That's a fancy way of saying that each firmware version looks like a different device. The way the Windows driver architecture works it will create a new device entry on the first plug for each new firmware version it sees. If Windows crashes when this happens? And you haven't reproduced it on other computers? The Kobo is not the root cause.

[Iñigo]

Originally Posted by Katsunami

The Kobo device is the only device to have problems after the Anniversary Update.

Win 10 AE is the only OS and version having issues, thus...

[Iñigo]

Originally Posted by ratinox

Windows 7: no problems with any released firmware version.
Windows 10 AE: no problems with 4.2.8110 or 4.2.8283.
Macintosh: no problems with 4.2.8110.
Linux: no problems 4.2.8110.

This.

I've connected my KA1 with my linux desktop, linux laptop, work Win10 laptop (pre AE and post AE), my wife's laptop (Win 8.1 and then Win10 pre AE and post AE)... none of them showed any problem either.
And I've tested every single firmware Kobo has released since the original version 3.19.5761.

[jiminrussell]

Originally Posted by Katsunami

What lunacy is this remark?

I can count my computer crashes in the last 20 years on the fingers of one hand, and all of them were caused by buggy display drivers.

Read the thread. The KA1 has USB connectivity problems on Windows 10 since the Anniversary Update last year, where *no other device* has been affected.

The number of USB-sticks, external hard drives, phones, and a plethora of other devices I use with this computer is staggering, and none of them ever failed to connect; not before, and not after the Anniversary update.

Maybe none of your other devices were affected but there were multiple reports of Kindle devices causing windows to Bluescreen after the Windows 10 anniversary update. Another update released by Microsoft on Sept. 13 apparently fixed that problem.

https://answers.microsoft.com/en-us/...6353f95?auth=1

I haven't had any connectivity problems with my KA1 and my two Windows 10 machines for several months. I know that doesn't help you but I don't think the issue you had is a common one.

[DNSB]

Originally Posted by Iñigo

So you say the problem first appeared with Windows 10 Anniversary Edition... not before... not other Windows, not even previous Windows 10 editions...

I've read exactly 0 people having USB issues with Linux, Apple or any Windows computer before Windows 10 Anniversary Edition, but the problem is caused by the Kobo device... of course!

Actually, the thread was for issues with all Kobo devices not just the KA1. And if we go back into pre-history, check for issues with Windows XP and needing an updated AMD USB filter driver.

And the problem appeared with the Insider Preview releases of Windows 10 long before the Anniversary update was released.

Since this is a Kobo forum, I won't go into the Kindle devices bluescreening your computer with Windows 10, again noted in the Insider Preview releases prior to the Anniversary release.

[DNSB]

Originally Posted by Katsunami

The Kobo device is the only device to have problems after the Anniversary Update.

Microsoft changed/fixed something. No devices have problems with that, only the KA1. It means the KA1 is doing something it shouldn't be doing.

That, together with all the battery problems, syncing issues, and even the official sleep cover not always shutting down the reader, makes the KA1 a highly unreliable device. I'm seriously thinking (again) to pick up my old Kindle again.

Umm... you mean those reports of Kindles bluescreening the computer were incorrect? Do a quick search on "kindle bluescreen windows 10" for more information.

And if you want to do more digging, you will find reports about quite a few devices having issues. Such items as webcams, Apple iDevices, etc.

OTOH, I had the issue with my Kobos (not just the KA1) prior to the Anniversary update but I was and am running the Insider Preview releases so got to enjoy life on the bleeding edge. I was not the only person who posted in this forum warning about the issues with Kobo's ereaders due to changes being made in Windows 10.

I will admit that while I had a couple of Kindles bluescreen my Windows 10 machine, I have never had a Kobo ereader do anything other than refuse to mount the exposed partition. AFAIR, there were enough posted workarounds for that prior to the Windows 10 AE release so for me, it was no biggie.

[robko]

Originally Posted by Katsunami

I can count my computer crashes in the last 20 years on the fingers of one hand, and all of them were caused by buggy display drivers.

And I don't need either hand (or any of my toes for that matter ) to count the number of times a Kobo device has crashed my computer since I had them (and I've used most of them going back to the original no light, no touch Kobo). The number is zero. It sucks that your Kobo and the USB on your computer don't like each other, but it's not a widespread issue (outside the specific issue with Windows AE update), so the likelihood is that something about your particular configuration (not saying there is anything wrong with it, just that some combination of things with it is slightly different to most) doesn't get along with Kobo.

And as others have pointed out, Kobo certainly was not the only device (let alone the only e-reader) that had issues with the Anniversary update and USB.

[Gone]

Originally Posted by Katsunami

Another stupid remark. The KA1 is the only USB device I have that has problems constantly, so it's the only device at fault. If the problem was with windows, other devices would have had problems.

As other pointed out, Windows is the problem. Sorry if you think it is stupid to say.

[petercreasey]

Claude, your continuing to blame Windows seems specious.

[Katsunami]

Originally Posted by jiminrussell

Maybe none of your other devices were affected but there were multiple reports of Kindle devices causing windows to Bluescreen after the Windows 10 anniversary update. Another update released by Microsoft on Sept. 13 apparently fixed that problem. (And others who said similar things and mentioned other devices such as webcams....)

If so, I've said nothing. Then it could indeed be Windows 10's fault.

I've been using the following USB devices with this computer for a year now:
- 4 external hard drives
- 4 USB sticks
- 2 card readers
- Logitech wireless mouse receiver
- A computer chess board
- Kindle KPW1
- Nexus 4 phone
- And the KA1.

And some external hard drives, USB-sticks, phones, and a Kindle that aren't mine. No problems, not before the AU, and not after.

The only device that has been having problems since the day I got it, is the KA1, mostly not wanting to connect. ("USB Device Not Recognized.") USBDeview could fix this problem by removing the unknown allocation and trying again; most of the time, it would work.

Today, after yesterday's update, I connected the KA1 to put some books on it, and the computer just BSOD (it's very first BSOD actually), so I naturally assumed the KA1 was to blame.

I still think it has more USB issues than I've ever had with any other device on any computer (except HP printers, maybe).

[Sweetpea]

Originally Posted by Katsunami

If so, I've said nothing. Then it could indeed be Windows 10's fault.

I've been using the following USB devices with this computer for a year now:
- 4 external hard drives
- 4 USB sticks
- 2 card readers
- Logitech wireless mouse receiver
- A computer chess board
- Kindle KPW1
- Nexus 4 phone
- And the KA1.

And some external hard drives, USB-sticks, phones, and a Kindle that aren't mine. No problems, not before the AU, and not after.

The only device that has been having problems since the day I got it, is the KA1, mostly not wanting to connect. ("USB Device Not Recognized.") USBDeview could fix this problem by removing the unknown allocation and trying again; most of the time, it would work.

Today, after yesterday's update, I connected the KA1 to put some books on it, and the computer just BSOD (it's very first BSOD actually), so I naturally assumed the KA1 was to blame.

I still think it has more USB issues than I've ever had with any other device on any computer (except HP printers, maybe).

I've only once gotten the "usb device not recognized" on a windows 10 machine and that was when I connected my Garming GPS to my SP2. But then, I've never connected my One to my Surface and my main PC is still Windows 7

[ratinox]

Originally Posted by Katsunami

- And the KA1.

It's not one Aura ONE. It's one Aura ONE for each firmware version. It's when those are detected and the USB driver is initialized for each new detection that your system is crashing.

That's Windows without a doubt. Bad driver, bad registry, bad something else I don't know what but it's definitely Windows, definitely not the Kobo.

[Katsunami]

The one thing I'm now suspecting is, possibly, a bad USB-cable. I've ditched the cable for a different one, and at this time, I haven't had any problems (yet).

I don't suspect Windows at this point. If the OS had a problem with USB-devices in general, it would have surfaced with other devices as well. USBDeview shows all the correct connections and drivers (including the KA1).

[Terisa de morgan]

Originally Posted by Katsunami

The one thing I'm now suspecting is, possibly, a bad USB-cable. I've ditched the cable for a different one, and at this time, I haven't had any problems (yet).

I don't suspect Windows at this point. If the OS had a problem with USB-devices in general, it would have surfaced with other devices as well. USBDeview shows all the correct connections and drivers (including the KA1).

Not blue screen but I've had problems with KA1 and a specific cable, so perhaps it is the reason.

[kiwik]

All bluescreen and chkdsk/filesystem issues can be solved by using USB 2.0 ports.

If you don't have a USB 2 port (like me), then buy yourself a USB 2.0 hub. Problem solved!

See this thread for more details:

https://www.mobileread.com/forums/sh...d.php?t=282881