Kindle PW2 battery issues 5.7.2.1

[gmercator]

I went ahead and pasted the contents into the one "extensions" directory, and followed the instructions to generate the "CPU Report"

This is a PW2 2GB on 5.6.5

Hope this works......

[gmercator]

This is from a PW2 4GB on 5.6.5

see attachment (hopefully)

[gmercator]

This is from a PW3 4GB from ebay

I edited out the mfg ID but I can PM to you if needed

[gmercator]

This is from a PW3 4GB from Amazon directly

I have edited out the mfg ID but can PM it to you if needed

[knc1]

Originally Posted by gmercator

This is from a PW2 4GB on 5.6.5

see attachment (hopefully)

Now this one looks a bit flaky - notice the time zone and the 1:12 ratio between high speed and low speed.
But not really 'wrong' - just a little bit different.

Please mention if any of them have the 'short battery run-time' problem.

= = = =

The 'manufacturer's code' should only indicate the production run and engineering change level of the board - I.E: it shouldn't be specific to a certain Kindle.

The 'board id' - now that one **might** be specific to a certain Kindle, which is why I didn't print it.

But to tell all of these devices apart, and specially when people start to report "but this one only lasts two days between charges" for a device -
We have to be able to spot the report that corresponds to the device.

Ah, so an idea that should serve that purpose - -
I'll generate a crypto sum of the 'manufacturer's code' -
That can't be reversed to discover the real 'manufacturer's code' and yet will always tie a report to a reporting device (only the owner can tell if the report was from their device or not).

It's two a.m. here and my mind is dead - -
So let them run for now, see which, if any, runs down in only a day or two.

[gmercator]

Originally Posted by knc1

Now this one looks a bit flaky - notice the time zone and the 1:12 ratio between high speed and low speed.

Please mention if any of them have the 'short battery run-time' problem.

The particular one that you mentioned (PW2 4GB) is still officially unregistered by Amazon, but has had a fake register hack applied so that collections could be set up manually... it also eliminated the "you must register now" nag message on the home screen...


None of these have any known "short battery run-time issue"... these are all still on 5.6.5, and I don't recall complaints about the battery time on 5.6.5

edit: The "crypto sum" of the mfg code is a great idea... no way to reverse to find the device serial number, e.g.


(I have another PW2 2GB on 5.7.2.1 that is being tested for "battery run time". It was registered with Amazon today after running in unregistered sleep mode approx 42 hrs with no apparent "drop" in the battery meter. Now it is running in registered sleep mode to see if there is any change

[knc1]

Remember:
As long as the USB cable is plugged in, the device will never enter suspend (sleep) mode.

The KUAL 'Battery Status' extension will give you a report in numbers, rather than estimating the progress of the battery icon.

but yeah, good base-line information.

I only have one G0-90G1 (PW-3) and no PW-2 devices.
I do have a selection of PW-1 devices (none tested yet) and one K5 on the most recent 5.3.7.3 .

Maybe we should pick one or two or several 'standard' books and see how much battery is used to read one of them over the span of xyz days.

= = = =

The ;st or ;settime search bar shortcut does not set the timezone, only date and time.
I am not sure how you can set the correct(ed) TZ.

[NiLuJe]

I remember that there's a script somewhere to set the TZ "the Amazon Way", but I'm not sure if there's a corresponding search bar command.

[knc1]

Oops.

[gmercator]

I am wondering if there is a sufficient hardware difference between 2GB and 4GB PW2 models that could result in the "battery drain issue", which doesn't seem to affect all PW2's that are beyond 5.6.5?

Went visiting to the PW2 Amazon product page, and started reading more recent negative reviews that mentioned sudden poor battery life. Customers contacting Amazon Kindle support are not being helped in any constructive way, other than to be offered a very small discount on a new replacement unit.... I made a few comments, asked some to verify if they have a 2GB vs 4GB model, and left Amazon links for updating to 5.7.3 Many of these folks have given up on their "battery-dead" PW2's. Very sad.

https://www.amazon.com/review/RPITG4EP627WG

https://www.amazon.com/review/R1ZEX3NDSWHDG7

https://www.amazon.com/review/RGOAOCPSYMIOA

https://www.amazon.com/review/R1XRUVI9YXNQQS

If you guys get any other "battery drain on PW2" reports, try to make a note if it is 2GB vs 4GB.... it's worth a try!

Also, my PW2 2GB on 5.7.2.1 which is now registered and in sleep mode, has not seen any appreciable drop in the battery meter for the last 25 hours... I will let it go another day before turning on the wifi to see if the battery drops quickly and to test out the "magic folder" for blocking an OTA update

Hope this helps

[Yolina]

Is it just PW2 or are some people with PW3 having issues too?

I have a PW3 on 5.7.2.1 and I haven't noticed any difference in battery life between that FW and previous FW. Right now it's going through the battery quicker than what I'm normally used to but that's because I've left wifi on 24/7 the last few days to see if the update.bin.tmp.partial folder trick still works on that FW (so far so good, no auto update)

[knc1]

It is a scattering of reports across the range of models.

Not enough to be conclusive in itself on any one model, except maybe the PW-2. Maybe.

[Yolina]

My PW2 2GB is still on 5.4.5.1. Would it be any use me getting a CPU report from that, then updating it to the latest FW and doing a new report?

[knc1]

It might.

I will not turn down any source of information, on devices with the problem and without.

For instance, I can (now) make a button that will double or triple the battery run-time on a K5 touch running the most recent firmware.
But no one has complained about that one (yet).

[Yolina]

Here's the report for a PW2 2GB on 5.4.5.1 and I'll do a new report once I've got round to updating it, which may be later today or tomorrow.