Battery issues even sleeping since JB

[Andrewzz]

I Jailbroken my Kindle a long time ago. But since I did that my Kindle is discharging really fast even if I'm not using it.

I've tried updating the JB soft and the Kindle firmware to no avail. For example, I turn off my Kindle with full battery and left it there. I got it again lets say 1 month after and it was almost completely drained, which was not happening before (I was getting a month lifespan with daily usage).

Current Firm: 5.8.9

Could someone please help me? I'm even willing to deinstall the JB as I'm not really using it but don't really know how to do so cleanly.

Thanks!

[Cinisajoy]

Easy way to unjailbreak is click on factory reset.

[coplate]

Originally Posted by Andrewzz

I Jailbroken my Kindle a long time ago. But since I did that my Kindle is discharging really fast even if I'm not using it.

I've tried updating the JB soft and the Kindle firmware to no avail. For example, I turn off my Kindle with full battery and left it there. I got it again lets say 1 month after and it was almost completely drained, which was not happening before (I was getting a month lifespan with daily usage).

Current Firm: 5.8.9

Could someone please help me? I'm even willing to deinstall the JB as I'm not really using it but don't really know how to do so cleanly.

Thanks!

One month on a paperwhite 2 doesn't seem completeley unreasonable.


You can use the ';dm' command to get some logs and see if you see anything.


To be clear - the jailbreak itself only creats 1 text file one text file on the device, it won't affect the battery life.

If you have installed other packages with KUAL, those all could.

Since you are already jailbroken, it is possible for you to do these steps if you really wanted to:

1. Create a special file that allows jailbroken paperwhite to downgrade (I'll explain later if you wanted )
2. Downgrade to factory
3. Upgrade to a version like 5.8.1 that you could decide to jailbreak if you wanted to later.
4. Do a settings->reset to wipe the jailbreak and have a clean 5.8.1

I am not sure if the factory image at #2 resets the jailbreak or not.

[knc1]

Since you are already jailbroken, it is possible for you to do these steps if you really wanted to:

1. Create a special file that allows jailbroken paperwhite to downgrade (I'll explain later if you wanted )
2. Downgrade to factory
3. Upgrade to a version like 5.8.1 that you could decide to jailbreak if you wanted to later.
4. Do a settings->reset to wipe the jailbreak and have a clean 5.8.1

I am not sure if the factory image at #2 resets the jailbreak or not.

The installation of any image file will overwrite "the jail break" - that single text file.
BUT ....
The auto-install code will still auto-install it next time you boot it up.
SO, do...
0) "Reset (to factory defaults)"
As described in the spoiler of Step #2, that will erase the auto-install code
Then continue as quoted.

Hmm...
Not that simple in this case, I think it would be better if coplate runs the hotfix un-install code in the special self-destruct script he creates that will allow your Kindle to install the factory initial firmware.
The "reset" that you do after his script runs will also remove the special file his script has to create.

= = = =

PS: It is all a waste of time.
Nothing posted on this site affects the run-time of the Kindle's system.
The few times someone has proposed or even posted such code, they have been shown the error of their ways and re-designed their code.
(One of the reasons we only encourage open source software here, so that everything can be peer reviewed.)

What you are seeing is the effect of normal aging of the battery.
And the messages you will see after the ;dm will tell you that.
The actual, current, storage capacity is reported.
Usually each time the device wakes up (but might very with firmware versions that I haven't seen myself).

[Andrewzz]

I do have KUAL and screensaver hacks.

Could the Kindle discharge fully in a month even if it is not being used at all? I though that when the Kindle was sleeping it wouldn't discharge, or at least would last a lot longer.

I attached the ;dm logs.

[knc1]

Originally Posted by Andrewzz

I do have KUAL and screensaver hacks.

Could the Kindle discharge fully in a month even if it is not being used at all? I though that when the Kindle was sleeping it wouldn't discharge, or at least would last a lot longer.

I attached the ;dm logs.

170430:151621 [  645.850420] KERNEL: I pmic:fg suspend battinfo:current=-23mA, volt=3841mV, capav=044%, mAh=781mAh:

Start planing to buy a new battery, that one is nearly worn out.
It has less than half of its, original, labeled storage capacity.

These types of batteries do "age" - which is what yours has done.
You are not as young now as when you first got this Kindle and neither is the Kindle.
The cause of the changes you have noticed: Tempus Fugit

And it might help if you would set the time and date correctly if it is not correct now.
Its wake up time calculations are about a year off, so that it is not taking as long a nap as it could be taking.

[coplate]

Looks like the battery went from 753 mAh to 67 mAh while it was suspended in 10 days

170501:061613 syslog-ng[898]: new configuration initialized
170511:201553 [ 1590.117663] max77696-rtc max77696-rtc.0: read time:
170511:201553 [ 1590.118168] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 01 DOW 02 HOUR 09 MIN 10 SEC 0C
170511:201553 [ 1590.118220] max77696-rtc max77696-rtc.0: --> 2017-05-01 Mon 09:16:12
170511:201553 [ 1590.124073] PM: Syncing filesystems ... done.
170511:201553 [ 1590.138176] PM: Preparing system for mem sleep
170511:201553 [ 1590.138244] Freezing user space processes ... (elapsed 0.01 seconds) done.
170511:201553 [ 1590.154961] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
170511:201553 [ 1590.174942] PM: Entering mem sleep
170511:201553 [ 1590.174949] Suspending console(s) (use no_console_suspend to debug)
170511:201553 [ 1590.195573] max77696-rtc max77696-rtc.0: read time:
170511:201553 [ 1590.195587] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 01 DOW 02 HOUR 09 MIN 10 SEC 0C
170511:201553 [ 1590.195599] max77696-rtc max77696-rtc.0: --> 2017-05-01 Mon 09:16:12
170511:201553 [ 1590.202562] KERNEL: I pmic:fg suspend battinfo:current=-13mA, volt=3828mV, capav=043%, mAh=753mAh:
170511:201553 [ 1590.225564] max77696-rtc max77696-rtc.0: read time:
170511:201553 [ 1590.225578] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 01 DOW 02 HOUR 09 MIN 10 SEC 0C
170511:201553 [ 1590.225589] max77696-rtc max77696-rtc.0: --> 2017-05-01 Mon 09:16:12
170511:201553 [ 1590.225622] add wake up source irq 105
170511:201553 [ 1590.226880] add wake up source irq 51
170511:201553 [ 1590.226938] PM: suspend of devices complete after 51.536 msecs
170511:201553 [ 1590.227336] PM: late suspend of devices complete after 0.383 msecs
170511:201553 [ 1590.227643] triggered: wake_irq_isr[0-3]: 0x0, 0x0, 0x200, 0x0
170511:201553 [ 1590.227653] gpio4 triggered 0x100000 (0xfad58f71/0x100088)
170511:201553 [ 1590.228099] PM: early resume of devices complete after 0.195 msecs
170511:201553 [ 1590.228211] imx2_wdt_reinit re-initializing wdog
170511:201553 [ 1590.228362] remove wake up source irq 51
170511:201553 [ 1590.340393] remove wake up source irq 105
170511:201553 [ 1590.355955] max77696-rtc max77696-rtc.0: read time:
170511:201553 [ 1590.355968] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 0B DOW 10 HOUR 4B MIN 0F SEC 33
170511:201553 [ 1590.355980] max77696-rtc max77696-rtc.0: --> 2017-05-11 Thu 23:15:51
170511:201553 powerd[2589]: I def:sm:Time consumed before going to suspend  = (95):
170511:201553 powerd[2589]: W def:lipc:method=LipcOpenEx service=com.lab126.powerd.perf:Method has been deprecated.
170511:201553 syslog-ng[898]: STATS: dropped 0
170511:201553 [ 1590.356470] max77696-rtc max77696-rtc.0: read alarm0:
170511:201553 [ 1590.356481] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 01 HOUR 09 MIN 0E SEC 25
170511:201553 [ 1590.356491] max77696-rtc max77696-rtc.0: --> 2017-05-01 09:14:37
170511:201553 [ 1590.356500] max77696-rtc max77696-rtc.0: max77696_rtc_resume: alarm_time:1493630077 resume_time1494544551
170511:201553 [ 1590.360907] KERNEL: I pmic:fg resume battinfo:current=-1mA, volt=3801mV, capav=036%, mAh=37mAh:
170511:201553 [ 1590.380605] KERNEL: I pmic:onkey::wario button online event
170511:201553 [ 1590.405941] max77696-rtc max77696-rtc.0: read time:
170511:201553 [ 1590.405955] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 0B DOW 10 HOUR 4B MIN 0F SEC 33
170511:201553 [ 1590.405967] max77696-rtc max77696-rtc.0: --> 2017-05-11 Thu 23:15:51
170511:201553 [ 1590.425316] PM: resume of devices complete after 197.099 msecs
170511:201553 [ 1590.425567] PM: Finishing wakeup.

And the same thing again.

170511:201750 [ 1707.518370] PM: Syncing filesystems ... done.
170520:113139 [ 1707.563076] PM: Preparing system for mem sleep
170520:113139 [ 1707.565585] Freezing user space processes ... (elapsed 0.01 seconds) done.
170520:113139 [ 1707.585336] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
170520:113139 [ 1707.605346] PM: Entering mem sleep
170520:113139 [ 1707.605353] Suspending console(s) (use no_console_suspend to debug)
170520:113139 [ 1707.626123] max77696-rtc max77696-rtc.0: read time:
170520:113139 [ 1707.626137] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 0B DOW 10 HOUR 4B MIN 11 SEC 31
170520:113139 [ 1707.626149] max77696-rtc max77696-rtc.0: --> 2017-05-11 Thu 23:17:49
170520:113139 [ 1707.641873] KERNEL: I pmic:fg suspend battinfo:current=-16mA, volt=3798mV, capav=035%, mAh=628mAh:
170520:113139 [ 1707.666109] max77696-rtc max77696-rtc.0: read time:
170520:113139 [ 1707.666121] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 0B DOW 10 HOUR 4B MIN 11 SEC 31
170520:113139 [ 1707.666133] max77696-rtc max77696-rtc.0: --> 2017-05-11 Thu 23:17:49
170520:113139 [ 1707.666164] add wake up source irq 105
170520:113139 [ 1707.668934] add wake up source irq 51
170520:113139 [ 1707.668991] PM: suspend of devices complete after 63.190 msecs
170520:113139 [ 1707.669390] PM: late suspend of devices complete after 0.383 msecs
170520:113139 [ 1707.669697] triggered: wake_irq_isr[0-3]: 0x0, 0x0, 0x200, 0x0
170520:113139 [ 1707.669707] gpio4 triggered 0x100000 (0xfad58f71/0x100088)
170520:113139 [ 1707.670346] PM: early resume of devices complete after 0.190 msecs
170520:113139 [ 1707.670462] imx2_wdt_reinit re-initializing wdog
170520:113139 [ 1707.670612] remove wake up source irq 51
170520:113139 [ 1707.844395] remove wake up source irq 105
170520:113139 [ 1707.845401] KERNEL: I pmic:onkey::wario button online event
170520:113139 [ 1707.866676] max77696-rtc max77696-rtc.0: read time:
170520:113139 [ 1707.866687] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 14 DOW 40 HOUR 42 MIN 1F SEC 26
170520:113139 [ 1707.866699] max77696-rtc max77696-rtc.0: --> 2017-05-20 Sat 14:31:38
170520:113139 [ 1707.867272] max77696-rtc max77696-rtc.0: read alarm0:
170520:113139 [ 1707.867281] max77696-rtc max77696-rtc.0: YEAR 11 MONTH 05 DOM 01 HOUR 09 MIN 0E SEC 25
170520:113139 [ 1707.867292] max77696-rtc max77696-rtc.0: --> 2017-05-01 09:14:37
170520:113139 [ 1707.867301] max77696-rtc max77696-rtc.0: max77696_rtc_resume: alarm_time:1493630077 resume_time1495290698
170520:113139 [ 1707.873330] KERNEL: I pmic:fg resume battinfo:current=-1mA, volt=3771mV, capav=029%, mAh=31mAh:

In each of those, the first log entry is it finishing up the log of when it suspended, and the second log entry is after waking up.

[knc1]

Casual readers :
That 'ten days' is from the first column, you read it as:
YYMMDD::HHMMSS

= = = =

I was just browsing through the same report on my PW3 -
the report format is a bit different.
In addition to the calculated average capacity that PW2 report shows, the one on the PW3 also shows the actual 'aged' battery capacity.

IIRC - one is a three terminal battery and the other is a four terminal battery.
(But then I might be wrong - there are about 76 models of Kindles, I do get confused.)

= = = =

I just happen to have a short stack of KTs here, let me browse those, see what some 'really old' devices have to say for themselves.

- - - -

KT - Wifi only - No ads - logs go back to 2012 (so this one must not have been used much).
Battery still holds 98% of label rating at full charge.

KT - Wifi+3G - ads - logs go back to 2016 (this one I was testing with leaving 3G on to check its ad retrieval during 'sleep') (it does).
This one is at about the same battery capacity as the PW-2 in question here.

KT - Wifi only, No ads
This one is at about 87% of label rating at full charge.

KT - Wifi+3G - No ads - this one had to go on the charger - all I have is the 'plug me in' picture right now.
Logs go back to 2013 - battery report shows it still has 98% of original capacity.

- - - -

Does the PW-2 have 3G?
Was it ever a 'Demo' unit?

[Andrewzz]

Thanks for your help guys. I'm charging my Kindle right now. I'll try again to dump the logs again after it is fully charged to see if there is any discrepancy.
Also the time/date is correctly configured.

[knc1]

Originally Posted by Andrewzz

Thanks for your help guys. I'm charging my Kindle right now. I'll try again to dump the logs again after it is fully charged to see if there is any discrepancy.
Also the time/date is correctly configured.

It looked that way from the first column.
Those timer messages must just be wrong, they can't be correct.

Was this device a 'Demo' model (it will say: "not for resale" on the case).

[Andrewzz]

It is not a demo unit. The time/date is correct (It is July 27 @ 23:40 where I live)

I'm attaching the new dumps.

170727:233137 powerd[2589]: I def:battinfo:batt_type = PRIMARY, capav=90%, mAh=1337mAh, volt=4197mV, current=322mA, temp=78F, lmd=1408mAh, cycl=22, reason_for_log=Battery log due to regular timer:
170727:233137 powerd[2589]: I def:battinfo-misc:batt_type = PRIMARY caprep=89%, capmix=95%, mAhav=1337mAh, mAhmix=1344mAh, reason_for_log=Battery log due to regular timer:

[knc1]

At the time of the messages you quoted:

Is Wifi enabled?
Is a USB cable attached? To what? PC, wall charger.

[Andrewzz]

Yes, wifi enabled and connected to PC to an USB 3.0 port.

[HarryT]

If this was one of the first PW2s sold, it's now almost four years old. Lithium batteries have a typical lifespan of around 3-5 years, so the sort of decline in battery capacity that you're seeing is entirely normal.

[Andrewzz]

I bought the Kindle two years ago on 4/23/15. I thought the device wouldn't discharge at such a fast rate when it was turned off cause the screen wasn't using energy at all.
Keep in mind the discharge happened while the device was off/suspended.
===
The Kindle is specifically this model:
Kindle PaperWhite 2 (2013) WiFi (4GB) (U.S., Intl.)