Kindle Freetime Daily Goals on jailbroken device broken?

[belektro]

Hi,

I have a K5 (PW/Touch) that I jailbroke following the hints in this forum.

As my son is going to school now and he learns reading I set him up a daily goal in Freetime and deployed two books for him.
While he today read at least for 10 minutes in one of the books, the Freetime app accounted only 4 minutes.

I didn't find any official information about how the reading time is being calculated nor did I find anyone who noticed a similar problem.

Is it possible that this phaenomenon is being caused by the jailbreak?

Cheers,
b.

[knc1]

Originally Posted by belektro

Hi,

I have a K5 (PW/Touch) that I jailbroke following the hints in this forum.

As my son is going to school now and he learns reading I set him up a daily goal in Freetime and deployed two books for him.
While he today read at least for 10 minutes in one of the books, the Freetime app accounted only 4 minutes.

I didn't find any official information about how the reading time is being calculated nor did I find anyone who noticed a similar problem.

Is it possible that this phaenomenon is being caused by the jailbreak?

Cheers,
b.

Short answer: No
Long answer: Nnnnooooo

[belektro]

Ok. I first thought the kernel may had been replaced by installing the jailbreak and the replacement kernel might lack some reliable clock source/event timer or the HZ value might have been fiddled with. But that's obviously nonsense.

[NiLuJe]

@belektro: This is not Android Lollipop . The jailbreak is fairly inert in and of itself.

[knc1]

Originally Posted by belektro

Ok. I first thought the kernel may had been replaced by installing the jailbreak and the replacement kernel might lack some reliable clock source/event timer or the HZ value might have been fiddled with. But that's obviously nonsense.

You could have read what the JB does in the "what does it do" section of the first JB thread post.
OR
in the README file in the Jailbreak archive.

[Ruskie_it]

Originally Posted by knc1

You could have read what the JB does in the "what does it do" section of the first JB thread post.

That section only says "JB opens the doors to pretty much everything". It says what it does, not how it does, for a non techie it could have been a legit question.
How course it should also be pretty clear from the ops you do to jailbreak that this is not a kernel replacement

[knc1]

Originally Posted by Ruskie_it

That section only says "JB opens the doors to pretty much everything". It says what it does, not how it does, for a non techie it could have been a legit question.
How course it should also be pretty clear from the ops you do to jailbreak that this is not a kernel replacement

Nice to be corrected when necessary.
(Even when I did not suggest it was not a legitimate question.)

Many places here **do** mention that the only (primary) thing done is add a single file, our (Mobileread's) signature certificate to the certificate store.

[Akirainblack]

NiJuLe, just in case you're interested it would appear that a modified kernel is no longer necessary to root Lollipop.
Chainfire manged to find a way.

[Ruskie_it]

Originally Posted by knc1

Many places here **do** mention that the only (primary) thing done is add a single file, our (Mobileread's) signature certificate to the certificate store.

Maybe not the right place to ask, and maybe it isn't even easy/possible for you to answer, but how/why the new firmware makes this jailbreak no longer viable?
If it is too off topic then never mind.

[knc1]

Originally Posted by Ruskie_it

Maybe not the right place to ask, and maybe it isn't even easy/possible for you to answer, but how/why the new firmware makes this jailbreak no longer viable?
If it is too off topic then never mind.

Not hard to answer, in fact, you can see for yourself how the (prior-to recent firmwares) JB does its thing by looking at the filenames of the files you copied to JB the Kindle.

See that one with the very strange name?
The one whose filename looks like a shell command?
Guess what, it is.
What in the *nix world is called a: "poison filename".

The most recent versions of the series 5.x firmware goes through a filename check and rename process that avoids letting the shell actually execute the filename.

Which is actually more convoluted than the system built-in method of avoiding poison filenames - but we have stopped giving Lab126 Linux lessons.

[NiLuJe]

(with an early exit in case of failed rename, in case someone had any bright ideas ).

[Ruskie_it]

[QUOTE=knc1;2991227]
See that one with the very strange name?
The one whose filename looks like a shell command?
Guess what, it is.
What in the *nix world is called a: "poison filename".

The most recent versions of the series 5.x firmware goes through a filename check and rename process that avoids letting the shell actually execute the filename.[quote]
A poison filename, cool.
I have always read about hacking tecniques - though not specific to kindle - and always wondered how one could discover them... poison filenames, stack overflows
Just playing around ramdomly? In this case, creating filenames at random?

Which is actually more convoluted than the system built-in method of avoiding poison filenames - but we have stopped giving Lab126 Linux lessons.

You mean there's some modification in the linux kernel the Kindle uses that checks for filenames not being... don't know, longer than a set length, before executing them?

[Akirainblack]

Originally Posted by NiLuJe

(with an early exit in case of failed rename, in case someone had any bright ideas ).

Bah, the second I read the statement about rename I immediately jumped to the simple write protect the file. :'(

[knc1]

Originally Posted by Ruskie_it

A poison filename, cool.
I have always read about hacking tecniques - though not specific to kindle - and always wondered how one could discover them... poison filenames, stack overflows
Just playing around ramdomly? In this case, creating filenames at random?
- - - - - -

In this case its just *nix history.

You've heard of "K & R" ?
Designed/wrote the "C" programing language and then used that to write (well, actually re-write) their Unix operating system.

Ken Thompson also wrote the first command shell.
That was already a standard feature of the first release of Unix in 1971.

The Thompson shell was not actually intended for scripting.

J. R. Mashey wrote an "enhanced" Thompson shell that was intended for scripting. The Mashey shell introduced shell variables.

System control by scripting was clearly becoming a useful technique and A.T.&T. wanted to replace the Thompson shell in support of that trend.

Steve Bourne wrote the Bourne shell as the system replacement command shell in the mid to late '70s.
The Bourne shell shipped with, and replaced the existing shell programs in both Unix Version 7 and in 2BSD.
Both of those operating systems where released in 1979.

"Poison filenames" was a feature of the Bourne shell, I am fairly certain (I.E: as best as I can recall).
They where actually used as a "shortcut" to writing a full script.

I don't recall if they existed in the Thompson shell (or in the contemporary C-shell or Korn-shell).
(My memory's failure, I **should** know! K&R where both still in school when I got my start in C.S.)

- - - - -

I can't claim any part of their use in jailbreaking the Kindle.
Someone else had to remember the technique.
I only recognized it for what it was when the JB that used it was published here.

[pghaworth]

Originally Posted by Akirainblack

NiJuLe, just in case you're interested it would appear that a modified kernel is no longer necessary to root Lollipop.
Chainfire manged to find a way.

Sorry to go OT, but seriously? I haven't been taking updates because of lack of further JB on my Android. Good to know. Chainfire's my go-to.