Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 09-11-2025, 08:15 PM   #136
workbee
Junior Member
workbee began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Sep 2025
Device: PW2
Quote:
Originally Posted by FalconFour View Post
Excellent win here... by the power of Claude Code ripping through the codebase and applying ideas and transformations, I managed to create a near-entirely-new version of this extension that takes a totally different approach. Instead of relying on complex internal timers and recovery techniques, we just ask the OS framework to do our bidding. Everything is now entirely based on events - device wakes? Update the image. Device is about to enter deep sleep? Set a future RTC wake time based on the scheduler. That's it.

By dramatically simplifying the code paths, I'm now on target for a full week of battery life on a charge, updating every 8 minutes during the day and 30 minutes at night. It hasn't missed a single update.

Check it out: https://github.com/FalconFour/onlinescreensaverPW2

I'll keep the Github repo updated with whatever new fixes I find it needs.
Thanks a lot for this, I've got it almost working and I hope you can help. So my Kindle (PW2 - 6th gen, DP75SDI) seems to be updating images from my server but it does distort them. When I update manually, or just put Kindle to sleep it looks good but just for a few seconds and then it distorts the image. When it updates itself from server it's distorted straight away and again when I put it to sleep it looks good just for a few seconds. I've attached photos of my test grid working and distorted (only horizontally).

I suspect it'll be something with resolution of my images? I've tried 758x1024 and 768x1024 px both with the same results. I did nothing special to images, just exported them out from Figma.

I'm nearly there, maybe I'm missing something?
Thanks!
Attached Thumbnails
Click image for larger version

Name:	kindleok.jpeg
Views:	87
Size:	204.7 KB
ID:	218039   Click image for larger version

Name:	kindlenotok.jpeg
Views:	85
Size:	129.4 KB
ID:	218040  

Last edited by workbee; 09-11-2025 at 08:20 PM.
workbee is offline   Reply With Quote
Old 09-12-2025, 02:32 AM   #137
FalconFour
Member
FalconFour began at the beginning.
 
Posts: 12
Karma: 10
Join Date: Mar 2018
Device: Kindle 7th Gen
Oh, that's... interesting. The script just uses "eips" to update the image - info here: https://wiki.mobileread.com/wiki/Eips - syntax is "eips -f -g {imagefile}".

A fair bit has been said about the PNG format sent to the Kindle. The HA Kindle screensaver add-on (separate from my extension) has this to say:
https://github.com/sibbl/hass-lovela.../main/index.js - near the bottom, lines 302-326

It indicates the PNG output to be greyscale, bit depth 8 (that is actually somewhat unusual these days - creating a greyscale PNG specifically using 8-bit coding), with dithering and various other transformations that apply to the image, not the file format. With that, the missing piece may simply be to make it an 8-bit PNG, whereas most PNG output today is 24-bit color or higher.

Not sure if that's the whole problem, though. Rendering it twice is oddly suspicious, but one render could be coming from "linkss" rendering (which may be smarter), with a duplicate coming shortly behind it by the "eips" renderer called by the script.

If rendering it as an 8-bit PNG doesn't improve things, maybe upload an example file?

Also, unrelated - but I only noticed late in the game (while charging my Kindle for the week), that my newly improved extension will never update the screen while it's charging... it's entirely event-driven and focused on battery life above all else. It's better to cycle a battery than to keep it charging all the time anyway! (nervous laugh)... yeah, maybe I'll find a way to work "plugged-in" updates back into it in the future! It'd need to bring some self-timers back into the game, a bit ugly... but it might work.
FalconFour is offline   Reply With Quote
Old 10-16-2025, 06:04 AM   #138
rich21044
Junior Member
rich21044 began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Oct 2025
Device: Kindle Paperwhite 7th Gen.
Thumbs up Kindle PaperWhite 7th Gen

After about 2 weeks of faffing about with Haas-Lovelace-Kindle-Screensaver and the online screensaver extension on my Kindle Paperwhite 7th Gen.
I finally found the avhm version (Page 9, Post#125 of this thread) and it works just fine.

Just need to get the Home Assistant dashboard right now
rich21044 is offline   Reply With Quote
Old 10-27-2025, 07:59 AM   #139
tgechev
Junior Member
tgechev began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Oct 2025
Device: Kindle Paperwhite 7th Gen
Thank you

Quote:
Originally Posted by FalconFour View Post
Oh, that's... interesting. The script just uses "eips" to update the image - info here: https://wiki.mobileread.com/wiki/Eips - syntax is "eips -f -g {imagefile}".

A fair bit has been said about the PNG format sent to the Kindle. The HA Kindle screensaver add-on (separate from my extension) has this to say:
https://github.com/sibbl/hass-lovela.../main/index.js - near the bottom, lines 302-326

It indicates the PNG output to be greyscale, bit depth 8 (that is actually somewhat unusual these days - creating a greyscale PNG specifically using 8-bit coding), with dithering and various other transformations that apply to the image, not the file format. With that, the missing piece may simply be to make it an 8-bit PNG, whereas most PNG output today is 24-bit color or higher.

Not sure if that's the whole problem, though. Rendering it twice is oddly suspicious, but one render could be coming from "linkss" rendering (which may be smarter), with a duplicate coming shortly behind it by the "eips" renderer called by the script.

If rendering it as an 8-bit PNG doesn't improve things, maybe upload an example file?

Also, unrelated - but I only noticed late in the game (while charging my Kindle for the week), that my newly improved extension will never update the screen while it's charging... it's entirely event-driven and focused on battery life above all else. It's better to cycle a battery than to keep it charging all the time anyway! (nervous laugh)... yeah, maybe I'll find a way to work "plugged-in" updates back into it in the future! It'd need to bring some self-timers back into the game, a bit ugly... but it might work.
Registered just to say thank you for your efforts. I am using your version of the extension and it has been great. I have set up an update schedule once per hour and battery life is not an issue at all. I can confirm that there are no updates while the Kindle is charging, I will be waiting for the fix!

Best regards,
Ted
tgechev is offline   Reply With Quote
Old Yesterday, 09:20 PM   #140
Ro4cHii
Junior Member
Ro4cHii began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Nov 2025
Device: Kindle Paperwhite 2024 (12th Gen; "PW6")
Kindle Paperwhite PW6 not waking up?!

Good evening,

I wonder if anybody has managed to get this working on a Paperwhite 2024 (PW6/12th generation)?

Basically, I am using this version: https://github.com/64bits/Little-Lan...nescreensaver/

I made some slight adaptations here and there but nothing wild:
  1. Submitting battery level and charging state to Home Assistant when fetching the screenshot of the dashboard
  2. Resetting my default screensaver when disabling the auto-update feature via KUAL

For testing purposes, I set the update interval to every 10 minutes.
Also, I disabled the Kindle's power saving mode in order to prevent any WiFi/connectivity issues.

Taking a look at the log file, that doesn't seem to work though and it seems that the Kindle fails to wake up properly.

This is my observation for now:
  • 01:22 – Kindle is in active state → I send it to sleep by pressing the power button
  • 01:23 – Screensaver state is active, so the script starts to fetch the dashboard screenshot, updates the screensaver file and executes the `eips` command. After that, the Kindle goes to sleep for 10 minutes
  • 01:43 – I wake up the Kindle manually because the script has failed to wake it up within the specified 10 minutes
  • 01:43 – Kindle is in active state again, no update because of active state
  • 01:47 – I send it to sleep manually once more → update gets triggered
  • 01:57 – WiFi status is 1 but WiFi connection state is NA. Is the Kindle struggling to re-connect to the WiFi here? Whatever it is, updating is not working here.
  • 02:04 – I execute the "update now" script via KUAL → Screensaver gets updated properly

Quote:
Sat Nov 29 01:23:17 CEST 2025: Device status: Powerd state: Screen Saver Remaining time in this state: 39.633875 defer_suspend:1 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 85% Charging: No Battery logging: On
Sat Nov 29 01:23:17 CEST 2025: Device in screensaver mode - performing scheduled update
Sat Nov 29 01:23:17 CEST 2025: Starting update cycle
Sat Nov 29 01:23:17 CEST 2025: Initial WiFi status: 1
Sat Nov 29 01:23:17 CEST 2025: WiFi was already enabled
Sat Nov 29 01:23:17 CEST 2025: WiFi connection state: CONNECTED
Sat Nov 29 01:23:17 CEST 2025: Starting network connectivity test with 58 second timeout
Sat Nov 29 01:23:17 CEST 2025: Successfully connected to internet after 1 ping attempts (58 - 58 seconds elapsed)
Sat Nov 29 01:23:17 CEST 2025: Network connection established, proceeding with image download
Sat Nov 29 01:23:18 CEST 2025: Screen saver image updated successfully from https://***.de/
Sat Nov 29 01:23:18 CEST 2025: Updating image on screen
Sat Nov 29 01:23:22 CEST 2025: Update completed successfully in 5 seconds
Sat Nov 29 01:23:22 CEST 2025: Update took 5 seconds
Sat Nov 29 01:23:22 CEST 2025: Schedule 00:00-06:00=10 active, interval is 10 minutes
Sat Nov 29 01:23:22 CEST 2025: Next update in 10 minutes
Sat Nov 29 01:23:22 CEST 2025: Next update in 10 minutes, sleeping until then
Sat Nov 29 01:23:22 CEST 2025: Starting battery-efficient wait for 600 seconds
Sat Nov 29 01:23:22 CEST 2025: Setting RTC wakeup in 600 seconds (absolute time: 1764376402)
Sat Nov 29 01:23:22 CEST 2025: RTC wakeup successfully set for 1764376402
Sat Nov 29 01:23:22 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:23:40 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:23:41 CEST 2025: Device status: Powerd state: Screen Saver Remaining time in this state: 16.034625 defer_suspend:1 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:23:41 CEST 2025: Device in screensaver mode - performing scheduled update
Sat Nov 29 01:23:41 CEST 2025: Starting update cycle
Sat Nov 29 01:23:41 CEST 2025: Initial WiFi status: 1
Sat Nov 29 01:23:41 CEST 2025: WiFi was already enabled
Sat Nov 29 01:23:41 CEST 2025: WiFi connection state: CONNECTED
Sat Nov 29 01:23:41 CEST 2025: Starting network connectivity test with 58 second timeout
Sat Nov 29 01:23:41 CEST 2025: Successfully connected to internet after 1 ping attempts (58 - 58 seconds elapsed)
Sat Nov 29 01:23:41 CEST 2025: Network connection established, proceeding with image download
Sat Nov 29 01:23:41 CEST 2025: Screen saver image updated successfully from https://***.de/
Sat Nov 29 01:23:42 CEST 2025: Updating image on screen
Sat Nov 29 01:23:46 CEST 2025: Update completed successfully in 5 seconds
Sat Nov 29 01:23:46 CEST 2025: Update took 5 seconds
Sat Nov 29 01:23:46 CEST 2025: Schedule 00:00-06:00=10 active, interval is 10 minutes
Sat Nov 29 01:23:46 CEST 2025: Next update in 10 minutes
Sat Nov 29 01:23:46 CEST 2025: Next update in 10 minutes, sleeping until then
Sat Nov 29 01:23:46 CEST 2025: Starting battery-efficient wait for 600 seconds
Sat Nov 29 01:23:46 CEST 2025: Setting RTC wakeup in 600 seconds (absolute time: 1764376426)
Sat Nov 29 01:23:46 CEST 2025: RTC wakeup successfully set for 1764376426
Sat Nov 29 01:23:46 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:24:16 CEST 2025: Performing cleanup before exit
Sat Nov 29 01:24:16 CEST 2025: Clearing RTC wakeup alarm
Sat Nov 29 01:43:32 CEST 2025: Performing cleanup before exit
Sat Nov 29 01:43:32 CEST 2025: Clearing RTC wakeup alarm
Sat Nov 29 01:43:32 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:43:32 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:43:34 CEST 2025: Device status: Powerd state: Active Remaining time in this state: 598.785461 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:43:34 CEST 2025: Device status: Powerd state: Active Remaining time in this state: 598.789600 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:43:34 CEST 2025: Device in other state, waiting 60 seconds before recheck
Sat Nov 29 01:43:34 CEST 2025: Device in other state, waiting 60 seconds before recheck
Sat Nov 29 01:43:34 CEST 2025: Starting battery-efficient wait for 60 seconds
Sat Nov 29 01:43:34 CEST 2025: Starting battery-efficient wait for 60 seconds
Sat Nov 29 01:43:34 CEST 2025: Setting RTC wakeup in 60 seconds (absolute time: 1764377074)
Sat Nov 29 01:43:34 CEST 2025: Setting RTC wakeup in 60 seconds (absolute time: 1764377074)
Sat Nov 29 01:43:34 CEST 2025: RTC wakeup successfully set for 1764377074
Sat Nov 29 01:43:34 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:43:34 CEST 2025: RTC wakeup successfully set for 1764377074
Sat Nov 29 01:43:34 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:44:35 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:44:35 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:44:36 CEST 2025: Device status: Powerd state: Active Remaining time in this state: 539.385751 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:44:36 CEST 2025: Device in other state, waiting 60 seconds before recheck
Sat Nov 29 01:44:36 CEST 2025: Starting battery-efficient wait for 60 seconds
Sat Nov 29 01:44:36 CEST 2025: Setting RTC wakeup in 60 seconds (absolute time: 1764377136)
Sat Nov 29 01:44:36 CEST 2025: RTC wakeup successfully set for 1764377136
Sat Nov 29 01:44:36 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:44:36 CEST 2025: Device status: Powerd state: Active Remaining time in this state: 539.191348 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:44:36 CEST 2025: Device in other state, waiting 60 seconds before recheck
Sat Nov 29 01:44:36 CEST 2025: Starting battery-efficient wait for 60 seconds
Sat Nov 29 01:44:36 CEST 2025: Setting RTC wakeup in 60 seconds (absolute time: 1764377136)
Sat Nov 29 01:44:36 CEST 2025: RTC wakeup successfully set for 1764377136
Sat Nov 29 01:44:36 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:45:37 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:45:37 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:45:38 CEST 2025: Device status: Powerd state: Active Remaining time in this state: 477.217156 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:45:38 CEST 2025: Device in other state, waiting 60 seconds before recheck
Sat Nov 29 01:45:38 CEST 2025: Starting battery-efficient wait for 60 seconds
Sat Nov 29 01:45:38 CEST 2025: Setting RTC wakeup in 60 seconds (absolute time: 1764377198)
Sat Nov 29 01:45:38 CEST 2025: RTC wakeup successfully set for 1764377198
Sat Nov 29 01:45:38 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:45:38 CEST 2025: Device status: Powerd state: Active Remaining time in this state: 477.026432 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:45:38 CEST 2025: Device in other state, waiting 60 seconds before recheck
Sat Nov 29 01:45:38 CEST 2025: Starting battery-efficient wait for 60 seconds
Sat Nov 29 01:45:38 CEST 2025: Setting RTC wakeup in 60 seconds (absolute time: 1764377198)
Sat Nov 29 01:45:38 CEST 2025: RTC wakeup successfully set for 1764377198
Sat Nov 29 01:45:38 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:46:39 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:46:39 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:46:40 CEST 2025: Device status: Powerd state: Active Remaining time in this state: 553.712211 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:46:40 CEST 2025: Device in other state, waiting 60 seconds before recheck
Sat Nov 29 01:46:40 CEST 2025: Starting battery-efficient wait for 60 seconds
Sat Nov 29 01:46:40 CEST 2025: Setting RTC wakeup in 60 seconds (absolute time: 1764377260)
Sat Nov 29 01:46:40 CEST 2025: RTC wakeup successfully set for 1764377260
Sat Nov 29 01:46:40 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:46:40 CEST 2025: Device status: Powerd state: Active Remaining time in this state: 552.894246 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:46:40 CEST 2025: Device in other state, waiting 60 seconds before recheck
Sat Nov 29 01:46:40 CEST 2025: Starting battery-efficient wait for 60 seconds
Sat Nov 29 01:46:40 CEST 2025: Setting RTC wakeup in 60 seconds (absolute time: 1764377260)
Sat Nov 29 01:46:40 CEST 2025: RTC wakeup successfully set for 1764377260
Sat Nov 29 01:46:40 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:47:41 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:47:41 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:47:42 CEST 2025: Device status: Powerd state: Screen Saver Remaining time in this state: 11.876713 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:47:42 CEST 2025: Device in screensaver mode - performing scheduled update
Sat Nov 29 01:47:42 CEST 2025: Starting update cycle
Sat Nov 29 01:47:42 CEST 2025: Initial WiFi status: 1
Sat Nov 29 01:47:42 CEST 2025: WiFi was already enabled
Sat Nov 29 01:47:42 CEST 2025: WiFi connection state: CONNECTED
Sat Nov 29 01:47:42 CEST 2025: Starting network connectivity test with 58 second timeout
Sat Nov 29 01:47:42 CEST 2025: Device status: Powerd state: Screen Saver Remaining time in this state: 11.720314 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:47:42 CEST 2025: Device in screensaver mode - performing scheduled update
Sat Nov 29 01:47:42 CEST 2025: Starting update cycle
Sat Nov 29 01:47:42 CEST 2025: Successfully connected to internet after 1 ping attempts (58 - 58 seconds elapsed)
Sat Nov 29 01:47:42 CEST 2025: Network connection established, proceeding with image download
Sat Nov 29 01:47:42 CEST 2025: Initial WiFi status: 1
Sat Nov 29 01:47:42 CEST 2025: WiFi was already enabled
Sat Nov 29 01:47:42 CEST 2025: WiFi connection state: CONNECTED
Sat Nov 29 01:47:42 CEST 2025: Starting network connectivity test with 58 second timeout
Sat Nov 29 01:47:42 CEST 2025: Successfully connected to internet after 1 ping attempts (58 - 58 seconds elapsed)
Sat Nov 29 01:47:42 CEST 2025: Network connection established, proceeding with image download
Sat Nov 29 01:47:42 CEST 2025: Screen saver image updated successfully from https://***.de/
Sat Nov 29 01:47:43 CEST 2025: Updating image on screen
Sat Nov 29 01:47:43 CEST 2025: Screen saver image updated successfully from https://***.de/
Sat Nov 29 01:47:43 CEST 2025: Updating image on screen
Sat Nov 29 01:47:47 CEST 2025: Update completed successfully in 5 seconds
Sat Nov 29 01:47:47 CEST 2025: Update took 5 seconds
Sat Nov 29 01:47:47 CEST 2025: Schedule 00:00-06:00=10 active, interval is 10 minutes
Sat Nov 29 01:47:47 CEST 2025: Next update in 10 minutes
Sat Nov 29 01:47:47 CEST 2025: Next update in 10 minutes, sleeping until then
Sat Nov 29 01:47:47 CEST 2025: Starting battery-efficient wait for 600 seconds
Sat Nov 29 01:47:47 CEST 2025: Update completed successfully in 5 seconds
Sat Nov 29 01:47:47 CEST 2025: Setting RTC wakeup in 600 seconds (absolute time: 1764377867)
Sat Nov 29 01:47:47 CEST 2025: Update took 5 seconds
Sat Nov 29 01:47:47 CEST 2025: RTC wakeup successfully set for 1764377867
Sat Nov 29 01:47:47 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:47:47 CEST 2025: Schedule 00:00-06:00=10 active, interval is 10 minutes
Sat Nov 29 01:47:47 CEST 2025: Next update in 10 minutes
Sat Nov 29 01:47:47 CEST 2025: Next update in 10 minutes, sleeping until then
Sat Nov 29 01:47:47 CEST 2025: Starting battery-efficient wait for 600 seconds
Sat Nov 29 01:47:47 CEST 2025: Setting RTC wakeup in 600 seconds (absolute time: 1764377867)
Sat Nov 29 01:47:47 CEST 2025: RTC wakeup successfully set for 1764377867
Sat Nov 29 01:47:47 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:57:49 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:57:49 CEST 2025: Wait completed, device should be awake
Sat Nov 29 01:57:50 CEST 2025: Device status: Powerd state: Screen Saver Remaining time in this state: 56.824259 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:57:50 CEST 2025: Device in screensaver mode - performing scheduled update
Sat Nov 29 01:57:50 CEST 2025: Starting update cycle
Sat Nov 29 01:57:50 CEST 2025: Device status: Powerd state: Screen Saver Remaining time in this state: 56.772211 defer_suspend:0 suspend_grace:0 prevent_screen_saver:0 drive_mode_state:1 PRIMARY BATTERY Battery Level: 84% Last batt event at: 84% Charging: No Battery logging: On
Sat Nov 29 01:57:50 CEST 2025: Device in screensaver mode - performing scheduled update
Sat Nov 29 01:57:50 CEST 2025: Starting update cycle
Sat Nov 29 01:57:50 CEST 2025: Initial WiFi status: 1
Sat Nov 29 01:57:50 CEST 2025: WiFi was already enabled
Sat Nov 29 01:57:50 CEST 2025: Initial WiFi status: 1
Sat Nov 29 01:57:50 CEST 2025: WiFi was already enabled
Sat Nov 29 01:57:50 CEST 2025: WiFi connection state: NA
Sat Nov 29 01:57:50 CEST 2025: Starting network connectivity test with 58 second timeout
Sat Nov 29 01:57:50 CEST 2025: WiFi connection state: NA
Sat Nov 29 01:57:50 CEST 2025: Starting network connectivity test with 58 second timeout
Sat Nov 29 01:57:59 CEST 2025: Ping attempt 10 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:57:59 CEST 2025: Ping attempt 10 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:57:59 CEST 2025: Ping attempt 10 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:57:59 CEST 2025: Ping attempt 10 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:57:59 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:57:59 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:09 CEST 2025: Ping attempt 20 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:09 CEST 2025: Ping attempt 20 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:09 CEST 2025: Ping attempt 20 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:09 CEST 2025: Ping attempt 20 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:09 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:09 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:20 CEST 2025: Ping attempt 30 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:20 CEST 2025: Ping attempt 30 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:20 CEST 2025: Ping attempt 30 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:20 CEST 2025: Ping attempt 30 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:20 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:20 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:30 CEST 2025: Ping attempt 40 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:30 CEST 2025: Ping attempt 40 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:30 CEST 2025: Ping attempt 40 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:30 CEST 2025: Ping attempt 40 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:30 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:30 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:40 CEST 2025: Ping attempt 50 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:40 CEST 2025: Ping attempt 50 to www.google.com failed. Last error: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:40 CEST 2025: Ping attempt 50 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:40 CEST 2025: Ping attempt 50 failed: ping: www.google.com: Temporary failure in name resolution
Sat Nov 29 01:58:40 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:40 CEST 2025: Current WiFi state during ping failure: NA
Sat Nov 29 01:58:48 CEST 2025: No internet connection after 58 seconds and 58 ping attempts, aborting.
Sat Nov 29 01:58:48 CEST 2025: No internet connection after 58 seconds and 58 ping attempts, aborting.
Sat Nov 29 01:58:48 CEST 2025: Network timeout after 58 seconds, 58 ping attempts to www.google.com
Sat Nov 29 01:58:48 CEST 2025: Network timeout after 58 seconds, 58 ping attempts to www.google.com
Sat Nov 29 01:58:48 CEST 2025: Final WiFi status: enabled=1, state=NA
Sat Nov 29 01:58:48 CEST 2025: Failed to establish network connection, skipping image download
Sat Nov 29 01:58:48 CEST 2025: Final WiFi status: enabled=1, state=NA
Sat Nov 29 01:58:48 CEST 2025: Script aborted due to network connectivity failure
Sat Nov 29 01:58:48 CEST 2025: Failed to establish network connection, skipping image download
Sat Nov 29 01:58:48 CEST 2025: Script aborted due to network connectivity failure
Sat Nov 29 01:58:50 CEST 2025: Update completed successfully in 60 seconds
Sat Nov 29 01:58:50 CEST 2025: Update took 60 seconds
Sat Nov 29 01:58:50 CEST 2025: Schedule 00:00-06:00=10 active, interval is 10 minutes
Sat Nov 29 01:58:50 CEST 2025: Update completed successfully in 60 seconds
Sat Nov 29 01:58:50 CEST 2025: Update took 60 seconds
Sat Nov 29 01:58:50 CEST 2025: Schedule 00:00-06:00=10 active, interval is 10 minutes
Sat Nov 29 01:58:50 CEST 2025: Next update in 10 minutes
Sat Nov 29 01:58:50 CEST 2025: Next update in 10 minutes, sleeping until then
Sat Nov 29 01:58:50 CEST 2025: Starting battery-efficient wait for 600 seconds
Sat Nov 29 01:58:50 CEST 2025: Setting RTC wakeup in 600 seconds (absolute time: 1764378530)
Sat Nov 29 01:58:50 CEST 2025: RTC wakeup successfully set for 1764378530
Sat Nov 29 01:58:50 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 01:58:50 CEST 2025: Next update in 10 minutes
Sat Nov 29 01:58:50 CEST 2025: Next update in 10 minutes, sleeping until then
Sat Nov 29 01:58:50 CEST 2025: Starting battery-efficient wait for 600 seconds
Sat Nov 29 01:58:50 CEST 2025: Setting RTC wakeup in 600 seconds (absolute time: 1764378530)
Sat Nov 29 01:58:50 CEST 2025: RTC wakeup successfully set for 1764378530
Sat Nov 29 01:58:50 CEST 2025: RTC alarm set, allowing device to suspend
Sat Nov 29 02:04:31 CEST 2025: Initial WiFi status: 1
Sat Nov 29 02:04:31 CEST 2025: WiFi was already enabled
Sat Nov 29 02:04:31 CEST 2025: WiFi connection state: CONNECTED
Sat Nov 29 02:04:31 CEST 2025: Starting network connectivity test with 58 second timeout
Sat Nov 29 02:04:31 CEST 2025: Successfully connected to internet after 1 ping attempts (58 - 58 seconds elapsed)
Sat Nov 29 02:04:31 CEST 2025: Network connection established, proceeding with image download
Sat Nov 29 02:04:31 CEST 2025: Screen saver image updated successfully from https://***.de/
I will be glad to share my solution once this last issue has been resolved (I don't think that it's worth sharing before because the adaptations I made so far are really minor).

Ro4cHii is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
AZW3 Extension fcm52 Amazon Kindle 6 09-29-2013 07:47 PM
SSModeSwitcher: An extension to change Screensaver mode thomass Kindle Developer's Corner 13 11-04-2012 10:31 PM
Troubleshooting file extension gerry7 Amazon Kindle 1 05-25-2011 07:55 AM
Will there be another US copyright extension? pdurrant General Discussions 30 04-08-2011 11:12 AM
NO extension, no sugar.... Greg Anos Lounge 7 01-16-2010 11:23 AM


All times are GMT -4. The time now is 08:12 AM.


MobileRead.com is a privately owned, operated and funded community.