Wake up from sleep

[Bluescreen]

Yes, I used exactly this version with a few additional outputs to console for diagnostics.
I will add some logging to a file and try again.

[knc1]

Originally Posted by Bluescreen

Yes, I used exactly this version with a few additional outputs to console for diagnostics.
I will add some logging to a file and try again.

What model of Kindle is device: "None Yet"?

Please update your info box to indicate what Kindle model you are writing about for the times when you forget to mention it in the text of your posts.

There is one of me and over a 1/4 million members registered here.
You gotta give me a break, I can't remember what model Kindle everyone has.

[Bluescreen]

Originally Posted by knc1

What model of Kindle is device: "None Yet"?

Ok, I will update my profile. :-)
But I had written in my first post, it is a PW2 with firmware 5.8.9.2 jailbreaked via serial.

Originally Posted by knc1

There is one of me and over a 1/4 million members registered here.
You gotta give me a break, I can't remember what model Kindle everyone has.

I thought you have a brain the size of a planet

I added some debug output to a file now. So here is my test script:

RTC=0
LOGGING=1
LOGFILE=/tmp/rtctest.log

currentTime () {
  date +%s
}

##############################################################################
# Logs a message to a log file (or to console if argument is /dev/stdout)
logger () {
  MSG=$1

  # do nothing if logging is not enabled
  if [ "x1" != "x$LOGGING" ]; then
    return
  fi

  #if no logfile is specified, set a default
  if [ -z $LOGFILE ]; then
    $LOGFILE=stdout
  fi

  echo `date`: $MSG >> $LOGFILE
}

##############################################################################
# Wait some time using RTC for wakeup

wait_for () {
  # calculate the time we should return
  ENDWAIT=$(( $(currentTime) + $1 ))

  # disable/reset current alarm
  echo 0 > /sys/class/rtc/rtc$RTC/wakealarm

  # set new alarm
  logger "Current time is $(currentTime)"
  logger "Setting Waketime to $ENDWAIT"
  echo $ENDWAIT > /sys/class/rtc/rtc$RTC/wakealarm

  # check whether we could set the alarm successfully
  if [ $ENDWAIT -eq `cat /sys/class/rtc/rtc$RTC/wakealarm` ]; then
    logger "Waketime set correctly"
    # wait for timeout to expire
    while [ $(currentTime) -lt $ENDWAIT ]; do
      REMAININGWAITTIME=$(( $ENDWAIT - $(currentTime) ))
      if [ 0 -lt $REMAININGWAITTIME ]; then
        logger "Waiting remaining $REMAININGWAITTIME seconds"
        # wait for device to resume from sleep, or for time out
        lipc-wait-event -s $REMAININGWAITTIME com.lab126.powerd resuming || true
      fi
    done
  else
    logger "Failure setting alarm on rtc$RTC, wanted $ENDWAIT, got `cat /sys/class/rtc/rtc$RTC/wakealarm`"
  fi

  # not sure whether this is required
  # the following throws an error, so I commented it
  #  lipc-set-prop com.lab126.powerd -i deferSuspend 1
}

# wait 2 hours and then wake up
echo "RTCTEST started"
logger "RTCTEST started"
while [ 1 -eq 1 ]; do
  wait_for 900
  echo "Good morning"
  logger "Good morning"
done

And here is the resulting logfile

Fri Jun 30 08:19:53 UTC 2017: RTCTEST started
Fri Jun 30 08:19:53 UTC 2017: Current time is 1498810793
Fri Jun 30 08:19:53 UTC 2017: Setting Waketime to 1498811693
Fri Jun 30 08:19:53 UTC 2017: Waketime set correctly
Fri Jun 30 08:19:53 UTC 2017: Waiting remaining 900 seconds
Fri Jun 30 13:42:56 UTC 2017: Good morning
Fri Jun 30 13:42:57 UTC 2017: Current time is 1498830176
Fri Jun 30 13:42:57 UTC 2017: Setting Waketime to 1498831076
Fri Jun 30 13:42:57 UTC 2017: Waketime set correctly
Fri Jun 30 13:42:57 UTC 2017: Waiting remaining 899 seconds

You see the device does not wake up. Only after I switch on the kindle at 13:42 it continues the script.

[knc1]

This wake up from sleep thing might also depend on the firmware version running.
Different firmware versions, often different kernel versions, etc. ...

This thread originated at a time when firmware (and kernel used) was considerably different (I did just scan the first page or so of the thread and I don't see where anyone documented the firmware version being run).

It might be helpful to the debugging to hook into the going to screensaver and wake from screensaver events.
Note: If the USB cable is plugged in, then 'going to screensaver' does not imply 'going to sleep'.
We have a worked example of that here:
https://www.mobileread.com/forums/sh...d.php?t=198484

[Bluescreen]

While I will look an the mentioned thread, her another log. I have set the wait time to 300 seconds. You see it wake three times, the Kindle goes asleep and nothing happens anymore.

Yes I disconnected USB for forcing the Kindle to fall asleep.

Fri Jun 30 14:00:30 UTC 2017: RTCTEST started
Fri Jun 30 14:00:30 UTC 2017: Current time is 1498831230
Fri Jun 30 14:00:30 UTC 2017: Setting Waketime to 1498831530
Fri Jun 30 14:00:30 UTC 2017: Waketime set correctly
Fri Jun 30 14:00:30 UTC 2017: Waiting remaining 300 seconds
Fri Jun 30 14:05:30 UTC 2017: Good morning
Fri Jun 30 14:05:30 UTC 2017: Current time is 1498831530
Fri Jun 30 14:05:30 UTC 2017: Setting Waketime to 1498831830
Fri Jun 30 14:05:30 UTC 2017: Waketime set correctly
Fri Jun 30 14:05:30 UTC 2017: Waiting remaining 300 seconds
Good morning
Fri Jun 30 14:10:30 UTC 2017: Good morning
Fri Jun 30 14:10:30 UTC 2017: Current time is 1498831830
Fri Jun 30 14:10:30 UTC 2017: Setting Waketime to 1498832130
Fri Jun 30 14:10:30 UTC 2017: Waketime set correctly
Fri Jun 30 14:10:30 UTC 2017: Waiting remaining 300 seconds
Good morning
Fri Jun 30 14:15:30 UTC 2017: Good morning
Fri Jun 30 14:15:30 UTC 2017: Current time is 1498832130
Fri Jun 30 14:15:30 UTC 2017: Setting Waketime to 1498832430
Fri Jun 30 14:15:30 UTC 2017: Waketime set correctly
Fri Jun 30 14:15:30 UTC 2017: Waiting remaining 300 seconds

[knc1]

Please post the firmware version your device is running.
You can find that in the 'Device Info' panel of the 'settings' section.

[Bluescreen]

As I said, firmware is 5.8.9.2, sadly. I don't know how to downgrade, the usual way via "update my kindle" does not work anymore with that version.

I now created a little test script to see the powerd events which are happening.
The script puts the current time plus 15 minutes into the wakeupalarm and then waits for all events from powerd.

#!/bin/sh

ENDWAIT=$(( `date +%s` + 900 ))

echo Wakeup time : `date -d @$ENDWAIT`
echo Current time: `date`

echo 0 > /sys/class/rtc/rtc0/wakealarm
echo $ENDWAIT > /sys/class/rtc/rtc0/wakealarm

lipc-wait-event -mt com.lab126.powerd '*'

Starting point was Kindles normal operation mode.
As you can see in the following log, all the expected events came but the wakeup event.

Wakeup time : Fri Jun 30 19:14:38 EEST 2017
Current time: Fri Jun 30 18:59:38 EEST 2017
[19:04:29.706631] goingToScreenSaver 3
[19:05:29.811153] readyToSuspend 10
[19:05:34.813016] readyToSuspend 8
[19:05:39.818784] readyToSuspend 7
[19:05:59.939158] readyToSuspend 7
[19:06:04.910156] readyToSuspend 6
[19:06:09.949382] readyToSuspend 2
[19:06:14.926352] readyToSuspend 1
[19:06:23.667195] suspending "mem"

I sampled the output at 19:25. After pressing the power button to wake up Kindle manually, this output happens:

[19:25:45.384165] wakeupFromSuspend 1160
[19:25:45.392901] resuming
[19:25:45.411959] t1TimerReset
[19:25:45.470198] outOfScreenSaver 1

So I think all the event stuff is working as intended, only the wakeup timer does not work.

[Bluescreen]

I found the rtc driver "file" /proc/driver/rtc
Immediately after running my event script I see..

[root@kindle bin]# cat /proc/driver/rtc
rtc_time        : 17:47:42
rtc_date        : 2017-06-30
alrm_time       : 18:02:14
alrm_date       : 2017-06-30
alarm_IRQ       : yes
alrm_pending    : no
update IRQ enabled      : no
periodic IRQ enabled    : no
periodic IRQ frequency  : 1
max user IRQ frequency  : 64
24hr            : yes

It's exactly the alarm time I set minus 2h (my timezone) and also the current time fits. Why it is not waking the Kindle. Maybe that alarm pending thing?

[knc1]

Originally Posted by Bluescreen

As I said, firmware is 5.8.9.2, sadly. I don't know how to downgrade, the usual way via "update my kindle" does not work anymore with that version.
- - - -

As you said?
I could not find it in your posts, which is why I asked for that information.

I do not recall asking you to downgrade your firmware, you must have me confused with someone else your working this problem with.

From what you are doing/posting, you must have the device jailbroken.

Install rescue pack, and optionally, its add-on coward's rescue pack.
Boot into diags.
ssh into diags and manually install a lower version of the firmware if that is what you want to do.
There are several threads around here with the full details of how to install the 'main' system while running the 'diags' system.

Firmware 5.8.9.2 -
I have no interest in running that version on any of my Kindles, so I will not be able to attempt to duplicate your problem and help you troubleshoot it, if it can be duplicated.

[Bluescreen]

Hm, it seems somehow we don't understand each other.

Originally Posted by knc1

As you said?
I could not find it in your posts, which is why I asked for that information.

I wrote it in my first post in this thread. You asked it several times and I answered.

I do not recall asking you to downgrade your firmware, you must have me confused with someone else your working this problem with.

No, you don't asked that. I told it because I wanted to show how I hate that Amazon upgraded my device without asking. So I had to open it up and add a serial port to jailbreak it. And I have the problem that I cannot do with it what I wanted because the wakeup timer does not work.

From what you are doing/posting, you must have the device jailbroken.

I said that also several times in this thread.

Install rescue pack, and optionally, its add-on coward's rescue pack.
Boot into diags.
ssh into diags and manually install a lower version of the firmware if that is what you want to do.
There are several threads around here with the full details of how to install the 'main' system while running the 'diags' system.

I only found that downgrade via "upgrade your Kindle" thing. Maybe I look for one of "several threads" you mentioned.

Or I rip this nice eInk display from the Kindle and attach it to an ESP microncontroller board. Maybe that's easier than friggling around with that fullblown Linux of the kindle for my simple task.

Firmware 5.8.9.2 -
I have no interest in running that version on any of my Kindles, so I will not be able to attempt to duplicate your problem and help you troubleshoot it, if it can be duplicated.

I can understand that, I also have no interest in that, but Amazon forces me. I will never again buy a Kindle.

Sorry, to bother you.

Maybe there are others who trapped in this firmware trap and are interested in finding why it is not working either.

Bye
Thorsten

[knc1]

You do not need the serial port to downgrade a jailbroken kindle.
You only need to install RP (Rescue Pack) and use it.

Start with the sticky thread with "Where do I start?" in its title.
You will find out how to manually install a different main OS.

The fact that you couldn't find it does not prove that it isn't there, you can't prove a negative.
All you proved is that you could not find it.

If you refuse to use RP, then you can use the serial port.
Only the specifics of the switching from 'main' to 'diags' and back again is slightly different.
The rest of the procedure is the same as documented.

Your claim that the hardware wakeup does not work is also false.
You can't prove a negative.
All you have shown is you can not find how to make it work.

Please provide a link where the manufacturer (Amazon) claims that your Kindle can be used for the 'simple' use you intend to use it for.
I am certain you will not be able to find that one either.

When you try to use the device for anything that the manufacturer does not describe as its intended function, your on your own (with whatever help you can find other than the manufacturer).
Your failure so far to do that is not the fault of the Kindle or of Amazon.

Try your own alternate solution.
It will not be as easy as you imagine and it is unlikely to work.
There are too many hardware details unknown to you for you to even suggest it.
And we have all been able to read how little you like reading (and even following) directions that deviate from your own preconceived notions of what should be required.
"Should" according to your own definitions.

Lots of luck on your next attempt to use Kindle parts.

[Bluescreen]

Danger! This post is a dircet answer to knc1. It is off topic and long. But I cannot accept the attacks knc1 addresses at me. So if you don't want to be involved, pleas skip this article.

Originally Posted by knc1

You do not need the serial port to downgrade a jailbroken kindle.
You only need to install RP (Rescue Pack) and use it.
Start with the sticky thread with "Where do I start?" in its title.
You will find out how to manually install a different main OS.

Ok, I will try to find and use it. I read that thread but maybe overread some thing. There are several thousands of articles in this forum. Sorry that I cannot read all of them yet.
And about searching: it is sometimes difficult to find the right search words, esp. if english isn't your mother language.
I never understood why people in forums often are so repellent if someone askes a question which is somewhere answered already. If they are so embaressed about the question, they should simply not answer, but blocking a thread for others that are not so embaressed.

The fact that you couldn't find it does not prove that it isn't there, you can't prove a negative
All you proved is that you could not find it.

That is quibbling (hope that is the right word). I never said it isn't there. I only say I didn't find it yet and that is the truth.

If you refuse to use RP, then you can use the serial port.
Only the specifics of the switching from 'main' to 'diags' and back again is slightly different.

I don't refuse it, I only didn't read all the stuff. And I thought it may be interesting to find out WHY it isn't working with that new FW version. But I see, that is to complicated for me. So I simply asked if anyone knows how to proceed in finding out.

Your claim that the hardware wakeup does not work is also false.
You can't prove a negative.
All you have shown is you can not find how to make it work.

That is quibbling, too. I think you know exactly what I mean. Ok: the known methods of activating a wakeup call using the RTC does not work with the new FW. And I didn't find it yet. Is that better.

Please provide a link where the manufacturer (Amazon) claims that your Kindle can be used for the 'simple' use you intend to use it for.
I am certain you will not be able to find that one either.

Why should I. I understand that Amazon is not interested in letting people "missuse" their device. That's ok for me. But that they force me to update MY device is NOT ok for me. It's all and everywhere the same today. The producer of some goods forces the owner of the good to do this and that and even destroys the good if the want.
E.g. I bought a computer game some months ago. It works flawlessly on my old PC. Until some day stupid Steam forcefully updated it. Now it crashes and I cannot use it anymore. 30 bucks for trash. Nice.
If I knew before buying a product it will be altered afterwards without my approval I would not buy it. But nowaday then I could buy nothing, because all the software producers seem to be the same.

Your failure so far to do that is not the fault of the Kindle or of Amazon.

I does not blame Amazon for blocking other uses, but I blame the for altering MY device without asking me, as stated above.

Try your own alternate solution.
It will not be as easy as you imagine and it is unlikely to work.

Yes that will not be easy. But I see more chances for me. I have a solid know how in hardware things and know how to use a logic analyzer and how to program display controllers and microcontrollers.

But Linux is a mystery for me.

There are too many hardware details unknown to you for you to even suggest it.

Maybe. But maybe it is possible to find out the controller chip of the display or even trace the signals with a logic analyzer. We will see. It would be easier to simply buy am eInk display with known datasheet. But it seems that nowaday the producers of such parts are not willing to sell them in small quantities, so we hobbyists have to reverse engeneer things if we want to use them.

And we have all been able to read how little you like reading (and even following) directions that deviate from your own preconceived notions of what should be required.

Sorry, I don't understand the second part of the sentence. Seems my english is not good enough. And about my "little liking to read" I already said at the top of this post that it is a simple matter of time. I cannot read all the thousands of articles at the same time. And what you mean with "directions that deviate my own preconceived notions" is a to complicated sentence which I simply don't understand.

I think this thread is dead now because of our misunderstandings and blaming each other. I am very sorry for that. Maybe it's the language differences, maybe I missunderstand some of the meanings of this conversations. Maybe I should only post in forums that are in my motherlanguage german.

I will not waste more time in asking something and try to find out by myself. As knc1 said: it's all here (hopefully). I only have to find the "needle in a haystack". It should be a joyfull weekend project. But now I am too annoyed to preceed. May be later.

[knc1]

We often do make allowances for people whose native language is not English.
You do not have the part of the world which is your location included in your info box.
You have not mentioned that English is not your native language until very recently in the post order.

Since English is not your native language:
The main index of this forum:
https://www.mobileread.com/forums/fo...play.php?f=150
is divided into two main sections, separated by a gray bar.

The threads indexed above the gray bar also have a green tag prefix: "Sticky".
That means those threads will always be found in that top section of the index.

One of those threads includes in its title:
(a.k.a: Where do I start?)
That is an abbreviation for "Also Known As":
It is also known as the "Master Index".

Click to the first post of that link.
Browse the sections in that first post.
Pay specific attention to the ones on the subject of "De-Bricking" the Kindles.

At this site, "Bricked" translates to "no apparent operation" sometimes the same thing as "hung".
In general, it isn't behaving as intended (by Amazon).

Un-Bricking a device almost always include manually installing a 'known good' main operating system.
(The touchscreen Kindles are all dual boot systems.)

If you include the Kindle running an undesired by owner firmware version as bricked, then those manual directions for installing a 'known good' main operating system includes installing an operating system other than the current.

Since around the version 5.2.x firmware version, all Amazon updates include a complete system image.
The spoiler of step #7 of the current jailbreak:
https://www.mobileread.com/forums/sh...d.php?t=275877
contains a list of links to "older than current" firmware images.

The thread: "NiLuJe's snapshots" -
https://www.mobileread.com/forums/sh...d.php?t=225030
contains the most recent builds of those things which he maintains.
That includes the application: "KindleTool"

KindleTool is the application that can convert an Amazon image file into a compressed archive where common tools can access the contents.
Which you want to do, if you are looking for where to get an older than current firmware kernel and system image.

Near the top of the forum index page you will find a line of buttons and boxes -
The 'Prefix Filter' setting tool.

Set the first drop down box to "tools" and click the last box "Show threads".
That gives you a relatively short (few pages) index list of threads.
That list will always include "NiLuJe's snapshots" thread.

It may include other tools that your will find of interest to your needs.
You should also review the list of things prefixed: "Tutorial" and things prefixed by your device's nickname (PW2).

There is no expectation that a person should read all of the thousands of threads here.

Like finding a specific tree in a forest, nobody needs to examine each and every tree.
That would be foolish.
All they have to do is understand how to follow the established paths and comprehend the established path markers.

[Bluescreen]

Hi

I finally was able to downgrade the Kindle to FW 5.4.5, after trying several howtos until I found one that was working.
Then I started my small test script:

#!/bin/sh

ENDWAIT=$(( `date +%s` + 900 ))

echo Wakeup time : `date -d @$ENDWAIT` $ENDWAIT
echo Current time: `date`

echo 0 > /sys/class/rtc/rtc0/wakealarm
echo $ENDWAIT > /sys/class/rtc/rtc0/wakealarm
echo Readback time: `cat /sys/class/rtc/rtc0/wakealarm`

lipc-wait-event -mt com.lab126.powerd '*'

It worked !!!

I then installed the screensaver hack and worked on the server side script.
Then, the next day, I tried again and it didn't wake up any more. Aaaargh!
Here's the protocol of my testscript:

Wakeup time : Tue Jul 4 19:15:42 EEST 2017
Current time: Tue Jul 4 19:10:42 EEST 2017

Now I pressed the power button to switch off

[19:10:46.936943] goingToScreenSaver 2
[19:11:46.974498] readyToSuspend 10
[19:11:51.954220] readyToSuspend 7
[19:12:12.019680] readyToSuspend 7
[19:12:17.021449] readyToSuspend 6
[19:12:22.028260] readyToSuspend 2
[19:12:27.037310] readyToSuspend 1
[19:12:35.584246] suspending

It does not wake up. So I pressed the power button

[19:18:26.800988] resuming
[19:18:26.819733] t1TimerReset
[19:18:26.909454] outOfScreenSaver 1

I tried again without using the power button to switch off. It's the same. It goes to sleep after about 10 minutes and nothing more (I increased the wakeuptime to 15 minutes, so it can go to suspend before waking up).

Now I see two alternatives: it happens to wakeup once because of who knows what (current star constellations, subspace anomalies, whatever) or because of the only change which I did to the system: the screensaver hack. So I uninstalled it.

It doesn't work. So what? Subspace Anomalies?
If anyone has any idea, I will try. If not, I think I have to give up. Running out of ideas.

[Bluescreen]

I think, I found the problem. If Wifi is on when device is suspending it does not wake up. I added a Wifi-Off Command before setting the wakeup time and it seems to wake up. Hope it is stable.