Firmware 3.17.3 Discussion

[John F]

For all you naysayers... Challenge excepted!

My one request, if it isn't too much work, whoever creates the next discussion thread for the next firmware, could you please post a link to my post in the first post (the link can say: "A Summary of the release can be found here"). I'll try and post fairly early in the thread to reserve a spot; or PM me and I'll start the thread. I'm usually on early most morning, EST. Acceptable?

[Nick_1964]

Originally Posted by John F

For all you naysayers... Challenge excepted!

My one request, if it isn't too much work, whoever creates the next discussion thread for the next firmware, could you please post a link to my post in the first post (the link can say: "A Summary of the release can be found here"). I'll try and post fairly early in the thread to reserve a spot; or PM me and I'll start the thread. I'm usually on early most morning, EST. Acceptable?

Apologies accepted .. I think..I hope others where successfull explaining what I told you.
There is, however,a small chance that admins will delete your post telling you there already is one.
There is a second chance that the person that "discovers" or start the new firmware tread doesn't read your appeal,because it is not always the same person that starts them.
So I think,but thats again my humble opinion,that you can better turn it around, look for the new topic that will be made about the new released firmware and ask the person if he/she would place a link in his article to your post in stead of hoping he will do it,or contact you by him/herself by private message.
You want to make this project,so you are the one who ask seems reasonable to me (and offers the best chance to success).
Maybe when people starts to like it in the future,they will come to you but don't expect them to do it by theirself at the beginning, and there will always be the possibility that the one who starts the topic,doesn't want to put a link to yours.

Just speaking for myself and that has nothing to do with our arguement (hope this is the good word) I would find it a bit confusing when there are 2 topics about the same firmware over and over again,and am afraid that there will be a lot of crossposting between the topics and afraid that information will be missing because people are putting it in an other topic, but time will tell.

[PeterT]

Nick and John; I've been suggesting to the community for a long time that the real solution to this issue is to stop relying on forum posts, but rather to create and maintain MobileRead wiki pages. They have the benefit that anyone can edit pages, not just the original poster.

However no one seems to show any interest

[Nick_1964]

Originally Posted by PeterT

Nick and John; I've been suggesting to the community for a long time that the real solution to this issue is to stop relying on forum posts, but rather to create and maintain MobileRead wiki pages. They have the benefit that anyone can edit pages, not just the original poster.

However no one seems to show any interest

I think it is an interesting idea.. For me I never open a topic about a firmware, due to time difference I mostly discover there is a new one when I am home from work,and English isn't my language, so I often write things to literally and therefore misunderstood like the word "demanding" but really, if there is a new firmware release I take a subscription, wait a couple of days so I can see what new problems are introduced (sigh..) and I do the same for the corresponding patch topic, and I have a subscription to the basic new firmware topic maintained by Murgh, if someone start a new one, then there are 4 topics to follow, because if you don't, people place important information and you missed it, or you ask a question and it will be answered with, that is already explained there, I do understand why John want to start his own project, but if things are scattered across 4 topics for every firmware I am afraid that it will be a mess, but with a wiki there are sometimes people angry because others are changing their original posts, and you get similar discussions at different places.. It worked well the way it does, only it demands that you read all off the topic.. When placing summary in new topics there will always be people who changing discussion to the new one.. Goodwill, isn't always a good motivation.. Again time will tell but I am not gonna follow 4 different topics and or a wiki, for a firmware that changes every 4 weeks, that is simple not manageable...

[jackastor]

Has anyone noticed anything out of the ordinary for battery life for the Kobo touch? Such as rapid battery drain?

regards

Jack

[Nick_1964]

Originally Posted by jackastor

Has anyone noticed anything out of the ordinary for battery life for the Kobo touch? Such as rapid battery drain?

regards

Jack

One person did just before the whole topic change reactions started, he suggested a factory reset, don't know if he did and if it changed his problem. It is at post #198

[SirEvo]

Originally Posted by Nick_1964

No, the system files are in a hidden partition.

Ok, thank you. I will try this today.

Originally Posted by jackastor

Has anyone noticed anything out of the ordinary for battery life for the Kobo touch? Such as rapid battery drain?

regards

Jack

Yes, I have noticed that. (mentioned about that yesterday)

I also want to add this to my problem:
I charged yesterday, it went up from 53% to 100% in 10 minutes or less and I read 80-90 minutes after this charging and it says 73% now. Not even after 24 hours. I wasn't using original cable, maybe that's the reason?

[Nick_1964]

Originally Posted by SirEvo

Ok, thank you. I will try this today.


Yes, I have noticed that. (mentioned about that yesterday)

I also want to add this to my problem:
I charged yesterday, it went up from 53% to 100% in 10 minutes or less and I read 80-90 minutes after this charging and it says 73% now. Not even after 24 hours. I wasn't using original cable, maybe that's the reason?

For myself, I don't think it is the cable, on the usb port there are 4 lines, 2 for power (most outside) and 2 for data.
If a wrong cable is used it is possible that your device can't connect to your computer to send or receive data, but for power that is most unlikely.
The power of the adapter or usb port can be a problem if it is less then 300 milli amps,but even then it will charge.. most usb ports are 500 milli amps and adaptors are even higher, and for myself I have never seen that the power indicator gives wrong values..

[filmo]

State of charge idicator has to learn with a few near full discharge then charge cycles to be accurate. It has to learn this because flat voltage curve until nearly fully discharged. To save battery it should stop battery drain before it can't be charged.

[narual]

Was at 3.15 with minimal complaints. Decided to update to the latest and got this. Now, when coming from a powered off state, my kobo aura HD freezes at the start screen most (all?) of the time, unless it's plugged in, then usually soft resetting it a few times gets it to a working state. Once it's started, it doesn't have any problems until it shuts off again. Trying to decide if I want to mess with rolling back or just turn off the setting that makes it shut down after an hour of sleep.

[Ripplinger]

Personally I never power off my ereader, it only goes to sleep (and I'm lazy about that too, I use a sleep cover). The only time I actually power off a reader are my old ones I never use. Otherwise, there's minimal battery drain just letting it stay in sleep mode, and it starts up near instantly when you're ready to read again and you're right on the page you left off at. So my power off setting is always on "never".

[snazzyapeman]

Originally Posted by Nick_1964

One person did just before the whole topic change reactions started, he suggested a factory reset, don't know if he did and if it changed his problem. It is at post #198

That was me (except I'm on Glo HD), factory reset fixed it. But I'm afraid I was quick to blame the new firmware--I had skipped a couple of updates and was also running KSM + koreader. My current thinking: the power drain probably preceded 3.17.3, but may have been exacerbated by same.

So now back to stock and loving it. May just buy something else for pdf's.

[frostschutz]

Originally Posted by snazzyapeman

So now back to stock and loving it. May just buy something else for pdf's.

If you can pinpoint this issue to a specific modification, you should report it to the author of that modification so they have a chance of fixing / improving.

[Anak]

Originally Posted by Nick_1964

… on the usb port there are 4 lines, 2 for power (most outside) and 2 for data. …

Exactly, and that is why I don't understand why a Kobo reader can't detect if it is connected with a computer (data) or a charger (power only).
Even my very old basic reader and many other usb devices are able to detect this difference.

[JSWolf]

Originally Posted by Anak

Exactly, and that is why I don't understand why a Kobo reader can't detect if it is connected with a computer (data) or a charger (power only).
Even my very old basic reader and many other usb devices are able to detect this difference.

The when I connect my H2O via an iPad charger, the H2O asks to connect or not. That's because Apple did things non-standard.