Aura ONE Kobo Aura One owners thread

[Poppaea]

Sorry, but I think you wanted to answer someone else.

The information is very interesting, so thank you for that.

[Alan_S]

Originally Posted by Zekathon

Does KOReader consume battery faster?

Actually, it does when you read. When not, it doesn't, or it does, depending if device entered false sleep, or not. Very instructive reading about this subject is here: https://github.com/koreader/koreader/issues/2239

Also, you need to know that you need few full charging to reach full battery capacity (it looks like you didn't do full charging from your description, so try to fully charge battery, at least now in the beginning).

[Zekathon]

Originally Posted by ratinox

Yup. Kobo do not ship wall warts with Aura ONE.

The User's Guide states that a 5V, 500mA micro USB adapter can be used for charging. Chances are, any recent charger made for fast charging phones and tablets is rated much higher, from 1000mA up to around 2500mA. In principle this should not be a problem since it's not what the adapter can provide, it's what the device will draw. If it wants 500mA then it will pull 500mA regardless of how much the adapter is capable of providing.

In practice, cheap, no-name wall warts are junk. The power they deliver generally is not well regulated (choppy, spikey) and they are more likely to short out and cause permanent damage than reputable brands like Amazon and Anker. If you have a genuine Samsung charger then it should be good (I have two and they've exhibited no problems with any of my devices).

Also, it's been demonstrated that USB wall warts can be used to inject malware into devices being charged. I'm not saying that this is the cause of the unexpected data connection pop-ups (my ONE sometimes does the same with my Surface Pro's charger for no apparent reason since it's definitely power only) but it's certainly a possibility.

As for battery life, if you've installed firmware 4.1.x then you should have reasonable battery life. IME, maybe 5% drain while idle over a 24 hour span (that's an off the cuff figure; I haven't measured it). I found that I needed to perform a factory reset before installing 4.1.x. If you're using a sleep cover then you need firmware 4.2.8110.

I am using a certified LG charger now, although it delivers 1 amp, but as you said, it is not like the charger pushes the charge, but that the device pulls it when it needs it.

The idea of hacking a device via power grid is interesting, i know there are Ethernet replicators distributing LAN across the home using wall plugs as outputs, so technically it should be possible

I got mine KA1 a day before the 4.2.8110 has been released (seller told me, he has updated it, so it came with whatever version was previous) and i immediately updated it via Kobo app to the latest.The battery drain shouldn't be caused by firmware. I charged it the day before yesterday (at 10 PM it was charged), i have been reading till 2 AM, yesterday i have been reading almost whole day - like from 10 AM, till 12 PM -, with max. 2 hours pause and today i plugged it in again with 10% left... so i think the battery just needed a calibration as it lasted more then a day with frontlight on most of the time.

Originally Posted by moonshot

I've not been here for a while but I bought and set up my new Kobo Aura One
yeaterday having waited weeks to find a store that had one.

There was a dark shadow around the margin area of the screen. Phoned Kobo and they advised a factory reset. This lightened the shadow but it is still there. Phoned Kobo again and was advised that I would be contacted by a higher level...... but I'm still waiting.

Has anyone had or have this problem, I can return the Kobo to the store for a refund but they don't have any more in store.

My KA1 has just a little lighter stripe on the bottom of the screen caused by frontlight + the colour of day light isn't completely equal across the screen, but the difference is minimal, unnoticeable when you don't directly search for it. You should probably return it.

Originally Posted by Alan_S

Actually, it does when you read. When not, it doesn't, or it does, depending if device entered false sleep, or not. Very instructive reading about this subject is here: https://github.com/koreader/koreader/issues/2239

Also, you need to know that you need few full charging to reach full battery capacity (it looks like you didn't do full charging from your description, so try to fully charge battery, at least now in the beginning).

The bug report is interesting, mainly the fact, that the KSM is running in the background all the time, so probably it checks for inputs and drains the battery a bit.. as i don't see any advantage in the KSM, because i use it only as a hub between Nickel and KOReader, i will probably get rid of it.

I will try to calibrate the battery by full charge/discharge/charge cycle thx

(sorry for the long post xD, although this a forum about reading, so you should be ok with it )

[Alan_S]

Originally Posted by Zekathon

The bug report is interesting, mainly the fact, that the KSM is running in the background all the time, so probably it checks for inputs and drains the battery a bit.. as i don't see any advantage in the KSM, because i use it only as a hub between Nickel and KOReader, i will probably get rid of it.

It looks like you misread something.

KSM isn't cause of battery drain. It happens also when you start koreader without KSM.

[Katsunami]

Originally Posted by Poppaea

Mine neither and it is not in the description.

Confirmed. The KA1 doesn't come with a charger.

I'm just using the charger from my Nexus 4 phone. It's an LG 2A charger, and it just works fine for everything that has a micro of mini-USB port. (The charger has a removable cord.)

[amo]

Question re. searching for library books: is there a way to limit the search of the Kobo site to "available from library" only?

[DNSB]

Originally Posted by amo

Question re. searching for library books: is there a way to limit the search of the Kobo site to "available from library" only?

Umm... already answered in your message in another thread.

[moorekom]

I'm a recent owner of Kobo Aura One and a newbie to Kobo. Love the size, font customization and the natural light option. But when I received the device, I noticed that there was the same two tone issue in A1 just as the voyage. Having returned several kindle voyage because of this issue, I was disappointed and contacted kobo. I showed them some pictures and they agreed to send a replacement (it also had a green blotch at natural light setting). The replacement has arrived after several days of follow-ups (and just being a nuisance) and I'm disappointed again. It looks very yellow and it has the two tone problem too (only much worse). No green light anymore so I guess that is an improvement.

My questions are: how common are these issues? Has anyone here gone through replacements because of these through Kobo? Did you find a reasonably even screen? How many tries has Kobo allowed?

Note: I am attaching a link for anyone who wishes to see a comparison. I have contacted Kobo through FB and they promised to send another replacement and told me that $25 store credits will be provided because of this issue. Kudos to them. Although I was frustrated with their CS, contacting them through FB is the way to go. I declined the credits and asked them if they can expedite the delivery instead as the last one took about 3 weeks (Canada to US. I know it's Holiday season.. but still). They said it will ship in another 5-7 days and sent a waybill to return both the defective devices. But at this point, I am worried that I might get a dud again. I know this process is basically lottery but I want to weigh some options and get some insight on this from fellow owners. Thanks in advance.
https://imgur.com/a/CDAG8
http://archive.is/nayGI

[Poppaea]

Originally Posted by Katsunami

Confirmed. The KA1 doesn't come with a charger.

I'm just using the charger from my Nexus 4 phone. It's an LG 2A charger, and it just works fine for everything that has a micro of mini-USB port. (The charger has a removable cord.)

I still have a charger from my Sony PRS-650 that has all the right specs and one from my Kobo Arc 10 HD whose specs are just slightly different but it works just fine. Ditto the one that came with my little tablet.

Both the Sony and the Kobo charger are separate from the cord which is a very nifty thing considering the lifespan of those simple cords Kobo hands out.

[Zekathon]

Originally Posted by Alan_S

It looks like you misread something.

KSM isn't cause of battery drain. It happens also when you start koreader without KSM.

Yes, i understood it. koreader has a bug, which under certain condition causes a drain of the battery, because of incorrectly set sleep flag somewhere in the code. Furthermore, it generally consumes more, then Nickel interface, which is understandable given the simplicity of Nickel.

What i was referring to, was one of the responses saying that the KSM is running in the background. Of course the main consumer is the KOR, but the KSM has to be draining it too, as the process never stops and awaits an event. I am not saying, that it the main cause, but surely it has its own part in the process.

PS.:
HAPPY NEW YEAR TO ALL OF YOU GUYS!

[Barty]

Originally Posted by moorekom

I'm a recent owner of Kobo Aura One and a newbie to Kobo. Love the size, font customization and the natural light option. But when I received the device, I noticed that there was the same two tone issue in A1 just as the voyage. Having returned several kindle voyage because of this issue, I was disappointed and contacted kobo. ..

My questions are: how common are these issues? Has anyone here gone through replacements because of these through Kobo? Did you find a reasonably even screen? How many tries has Kobo allowed?

How many voyages did you go through before getting one you found acceptable?

I think the problem is inherent with these front lit, flushed screen, e-ink readers. You may get one that is better than another, but it's a lottery.

[amo]

Originally Posted by DNSB

Umm... already answered in your message in another thread.

So you did - thank you!
In case anyone else has the same question, David's answer is here: https://www.mobileread.com/forums/sho...d.php?t=282228

[Alan_S]

Originally Posted by Zekathon

Yes, i understood it. koreader has a bug, which under certain condition causes a drain of the battery, because of incorrectly set sleep flag somewhere in the code. Furthermore, it generally consumes more, then Nickel interface, which is understandable given the simplicity of Nickel.

What i was referring to, was one of the responses saying that the KSM is running in the background. Of course the main consumer is the KOR, but the KSM has to be draining it too, as the process never stops and awaits an event. I am not saying, that it the main cause, but surely it has its own part in the process.

First, KSM doesn't work like that. It starts whatever reader you want (and have installed on your device) and stop using processor. Including nickel. If it started nickel and continue to drain battery, then you would see higher battery drain with nickel also (nickel is also started with KSM, if you didn't know that). Which is not the case. So, I hope you see now, obviously tells us all that KSM isn't culprit.

Second, if you read issue, culprit for false sleep is a bit more (a lot more) complicated. Maybe now when suspend script is written in lua would be solved. It remains to be seen.

Third, nickel uses less battery when reading not because it is simpler software, but because it is written in such fashion that after user turns page he goes in sleep and only leaves IR active waiting for next user input.

Koreader doesn't enter sleep mode when it is on. Maybe some day it will, it is theoretically possible to program it to behave like that.

This a bit higher battery drain when reading isn't that big that it makes that big difference. Especially with KA1 which usually also uses battery for light (which obviously couldn't be stopped in periods when device waits for user input).

[Zekathon]

Originally Posted by Alan_S

First, KSM doesn't work like that. It starts whatever reader you want (and have installed on your device) and stop using processor. Including nickel. If it started nickel and continue to drain battery, then you would see higher battery drain with nickel also (nickel is also started with KSM, if you didn't know that). Which is not the case. So, I hope you see now, obviously tells us all that KSM isn't culprit.

Second, if you read issue, culprit for false sleep is a bit more (a lot more) complicated. Maybe now when suspend script is written in lua would be solved. It remains to be seen.

Third, nickel uses less battery when reading not because it is simpler software, but because it is written in such fashion that after user turns page he goes in sleep and only leaves IR active waiting for next user input.

Koreader doesn't enter sleep mode when it is on. Maybe some day it will, it is theoretically possible to program it to behave like that.

This a bit higher battery drain when reading isn't that big that it makes that big difference. Especially with KA1 which usually also uses battery for light (which obviously couldn't be stopped in periods when device waits for user input).

Thanks for clarification, i am having an ereader just a few days. It is an undiscovered land to me.

Btw. is there any way to display a custom screensaver on KA1, except for replacing all covers? I have discovered a hack for it, but it was for GloHD only (or it appeared to be). I tried searching the forum, it found a few mentions, but none of them was very helpful. It would be nice, to be welcomed by an artwork every time I open the sleep cover

in case, this hack works, where should i put the image (images?)?

EDIT: I found out, that there is an option in the KOReader to display images from a folder, that's great i would love to have this even for Nickel, but better then nothing

[moorekom]

Originally Posted by Barty

How many voyages did you go through before getting one you found acceptable?

I think the problem is inherent with these front lit, flushed screen, e-ink readers. You may get one that is better than another, but it's a lottery.

I see your point. As I mentioned, I know this process is a lottery and I'm not interested in going through replacement after replacement only to find variable degrees of gradients. I wanted to check how prevalent this is and if it is very much so, then I guess it is what it is.