Kindle PW2 battery issues 5.7.2.1

[NiLuJe]

@Eagle Reader: I'm sorting my Homescreen by most Recent, which is why I see them pop up 'live'. That may not be your case [You appear to be sorting by Title on your screenshots]. And/or you may have a bogus date set on your device, and/or stuff with bogus timestamps on the device.

Anyway, err, I'm afraid I forgot why we were even trying to look at logs in the first place...? .

[knc1]

To find out the state of the indexer system.
There will be messages in the system log file when it changes speed, starts, finishes, etc.

This is a non-jailbroken device, we don't have a lot of information options here.

= = = =

The ;dm script 'cleans' the actual message files - it is 'safe' to attach the system log file to your post.
I.E: You are not getting the 'real thing' your getting redacted copies.

[Eagle Reader]

Originally Posted by NiLuJe

@Eagle Reader: I'm sorting my Homescreen by most Recent, which is why I see them pop up 'live'. That may not be your case [You appear to be sorting by Title on your screenshots]. And/or you may have a bogus date set on your device, and/or stuff with bogus timestamps on the device.

Anyway, err, I'm afraid I forgot why we were even trying to look at logs in the first place...? .

I was having issues with the battery discharging after only a day or so after the 5.7.3 update (which happened on April 5 when I was at a wifi hotspot).

As for my device, to the best of my knowledge, I have no bogus date. In fact, I am embarrassed to say that I don't know how to change the date. I had forgotten to change the time to reflect daylight savings time.

Yes, I did have sort set to titles because I found it easier to go through the docs in list format sorted by title.

[Eagle Reader]

Originally Posted by knc1

To find out the state of the indexer system.
There will be messages in the system log file when it changes speed, starts, finishes, etc.

This is a non-jailbroken device, we don't have a lot of information options here.

= = = =

The ;dm script 'cleans' the actual message files - it is 'safe' to attach the system log file to your post.
I.E: You are not getting the 'real thing' your getting redacted copies.

Ahhh, thanks for telling me that the ;dm script cleans the actual message files. Before I attach the message files, I'll go through the system log file to see if anything jumps out to me, keeping in mind what you have told me to look for. If nothing else, it will be an exercise, perhaps one I won't do well on? But what they hay.

[Eagle Reader]

Originally Posted by knc1

To find out the state of the indexer system.
There will be messages in the system log file when it changes speed, starts, finishes, etc.

This is a non-jailbroken device, we don't have a lot of information options here.

= = = =

The ;dm script 'cleans' the actual message files - it is 'safe' to attach the system log file to your post.
I.E: You are not getting the 'real thing' your getting redacted copies.

Thanks for to all who are helping me with trying to troubleshoot battery draining after 1 or 2 days of low reading use. I am going to leave my PW2 unplugged to see what happens with the battery, will it drain as it did the other day?

Ok, I am attaching the system log that I got this morning. I have deleted them from my kindle and they are on my iMac. I tried to go through the same steps I did this morning to get another set of four log files and have been unsuccessful for some reason. Don't know why I had trouble this time, I was curious to see if there was any evidence of indexing after I got the log files from the ;dm script about 8:44 EST this morning, that is I wanted to try to get logs time stamped about 1:44 PM EDT. Yes, I was looking in documents where my docs are sideloaded. So, the best I have to offer is the system log from this morning. I thought that deleting the log files from my PW2 might help but it did not.

I did a search on the text in the system log for "index" and got 348 hits, the last one being at about 9:30 PM EST hours on April 9th (if I am reading the dates correctly). It was plugged in to power in sleep mode from about 2000 hours overnight through this morning until about 8:40 EST. Am going by the time on my PW2 as I did not correct the time stamp until about an hour ago. So, it would seem that there were no index events after about 9:30 PM EST (or 2130 on the log files).

I was on and off my PW2 a few times in the afternoon into the evening (April 9th), including a couple of times where I had it connected to my iMac via usb. After deleting some unneeded files associated with non-Amazon sideloaded files from my kindle, disconnecting from my iMac and restarting, I plugged the kindle back into utility power and put it in sleep mode for the last time at about 9:30 PM EST on April 9th. I unplugged it from utility power about 8:30 AM EST this morning (April 10th.

For those who might be wondering, I corrected the time on my PW2 early this afternoon to reflect daylights saving time.

[knc1]

things like this:

160410:084348 cvm[4683]: I IndexerThread:INDEX_TITLE:path=y13be2fffbf863bb921c1bc14814b5548,phase=INDEX_TITLE_THREADED_START,itemsRemaining=3:

that time stamp is: YYMMDD:<I think seconds - its some invented at lab126 notation>

At least some of the touch and release times are a single unit apart. . . .
And a 1/10 second would be 'flash fingering' and 1 minute would be really, really slow finger movement.

The earlier 'webreader' crash isn't something I would expect to see -
That one looks like it crashed cvm (the hardware assisted, JVM).

[Eagle Reader]

Originally Posted by knc1

things like this:

160410:084348 cvm[4683]: I IndexerThread:INDEX_TITLE:path=y13be2fffbf863bb921c1bc14814b5548,phase=INDEX_TITLE_THREADED_START,itemsRemaining=3:

that time stamp is: YYMMDD:<I think seconds - its some invented at lab126 notation>

At least some of the touch and release times are a single unit apart. . . .
And a 1/10 second would be 'flash fingering' and 1 minute would be really, really slow finger movement.

The earlier 'webreader' crash isn't something I would expect to see -
That one looks like it crashed cvm (the hardware assisted, JVM).

Thanks!

Not quite sure what you mean by flash fingering. But if I am understanding the time stamp in what you copied here, that was around the time that I did the first of two successful ";dm" searches this morning.

I don't know what the exact timestamp is of the webreader crash that you are referring to. But in doing my own search of the log files, I can say that if memory serves I did have my PW2 connected to my iMac during some refrences to webreader. I do recall that I did delete an extraneous and unnecessary file when connected to my iMac. The kindle froze and I rebooted. Don't know if that is the incident that the webreader crash refers to. I was also going and forth between the window where I can see my sideloaded documents and docs in the cloud (no wifi at home.)

There was a second time last night and again this afternoon when I deleted some sideloaded files when I was connected to my iMac. Seems that when I thought I removed some of my sideloaded non-Amazon file that some remenants were still left on the kindle, so I deleted them The kindle did not freeze in either incident.

Just checked the kindle, nothing to report but it has only been a couple of hours.

[knc1]

Fingers that move as fast as those of:
https://en.wikipedia.org/wiki/Flash_%28comics%29

[Eagle Reader]

Originally Posted by knc1

Fingers that move as fast as those of:
https://en.wikipedia.org/wiki/Flash_%28comics%29

Ahh, I get it.

[jhowell]

A translation of the leaked specs for the upcoming new Kindle includes this:

A newly designed Kindle sleep mode can extend battery life to the greatest extent.

I wonder if there are any signs of this in the current firmware or if it is just a feature of the new hardware.

[knc1]

Originally Posted by jhowell

A translation of the leaked specs for the upcoming new Kindle includes this:

I wonder if there are any signs of this in the current firmware or if it is just a feature of the new hardware.

Not longer battery run-time, more batteries
One in the cover, one in the Kindle.

I just happen to have the sources of the kernel for 2.5.4 sitting in front of me - -
It has an option to replace the 'idle loop' with a 'doze mode' (not selected as shipped).

So no, not exactly new, more like 6 years old and (perhaps) now being used in the firmware that ships.

Also, they may be re-enabling the 'conservative' governor - -
something they stopped including at about 5.4.x firmware version.
I.E: Only the K5 and earlier has it available (and it is also un-used).

= = =

Most of that translation just reads as "Marketing Hype" -
a smooth spin on: "We are re-enabling system features that we forgot to include in last year's models."

The weight change, the new position sensor, the physical size change -
those seem to be actual 'added features'.

[Eagle Reader]

Update on April 15th Six days have passed since I first posted on this thread regarding some battery drain issues that I was having after my nonjailbroken PW2 updated to 5.7.3 Thanks to @knc1 and @NiLuJe for your help!

I hope that this isn't too much information. Perhaps someone might find this useful?

I believe (knocking on wood) that the battery drain problems that I was having last week were due to indexing. Perhaps leaving it plugged into utility power in sleep mode did the trick?? I also went in via the usb and cleaned out an unneeded temporary file from an Amazon e-book purchase (the kingle single is there on my PW2). I also figured out that I have to set my PW2 to "all books" in order for the ";dm" command (dumps log files) to work. Have done so two more times and copied same to my iMac before deleting the log files.

I have used the kindle everyday for about 30 minutes for reading in airplane mode (no wifi at home) with whispersync turned off. Yesterday I went to a wifi hotspot, turned on whispersync and then restarted in order to (hopefully) sync my highlights (some are important to me and don't want to lose them). When I was done, I went back to airplane mode and disabled whisperync and restarted. Got home and dumped the log files, pretty decent battery usage, about 90% left.