anyway to jail break new oasis (2019)?

[knc1]

Two problems noticed, other people might notice things that I missed:
*) The "blocker directory" is being accessed once every 15 seconds.
Not really a problem, not for this type of computer.

*) There seems to be a really bad problem in the Amazon firmware related to Audio metadata on book, or books.

Setting to "Airplane Mode" ***Should*** cause the firmware to stop trying both things.

Is there any chance you could install a more recent Amazon update?
Something other than 5.12.0 (the recent flurry of 5.12.x.y.z update numbers would indicate they are trying to fix a problem, or problems).

Once again, another set of eyes on those system logs would probably help here.

[shalym]

Originally Posted by knc1

Two problems noticed, other people might notice things that I missed:
*) The "blocker directory" is being accessed once every 15 seconds.
Not really a problem, not for this type of computer.

*) There seems to be a really bad problem in the Amazon firmware related to Audio metadata on book, or books.

Setting to "Airplane Mode" ***Should*** cause the firmware to stop trying both things.

Is there any chance you could install a more recent Amazon update?
Something other than 5.12.0 (the recent flurry of 5.12.x.y.z update numbers would indicate they are trying to fix a problem, or problems).

Once again, another set of eyes on those system logs would probably help here.

I could install a more recent firmware, but I was trying to run an experiment and see if the blocking directory would, indeed block the automatic upgrade to new firmware. Since Amazon is accessing that directory every 15 seconds, maybe that's proof that it *is* blocking the upgrade?

Shari

[knc1]

Originally Posted by shalym

I could install a more recent firmware, but I was trying to run an experiment and see if the blocking directory would, indeed block the automatic upgrade to new firmware. Since Amazon is accessing that directory every 15 seconds, maybe that's proof that it *is* blocking the upgrade?

Shari

The blocking directory is still blocking:

190731:210011 tmd[2704]: W qmgr:fopen_to_write:id=3428,path=---,err=Is a directory(21):
190731:210011 tmd[2704]: I start_transfer:starting:id=3428,dir=down,pri=1800,qpos=0 of 1,net=wifi,on=wifi,was=WAITING,try=1,ceh=0x144840:
190731:210011 tmd[2704]: E qmgr:fopen_to_write:id = 3428, path = ---, err = Is a directory (21):

The reader of such things will notice that two different programmers wrote different parts of the code (and different parts of the error messages). Since the two people can not get the error strings to match, you can guess at what the chances are they can get the parts of the code to "match".
JB has lots of money, he can just keep cycling programmers through the project until two of them "get it right" for their corresponding parts of the programming.

[shalym]

Originally Posted by knc1

The blocking directory is still blocking:

190731:210011 tmd[2704]: W qmgr:fopen_to_write:id=3428,path=---,err=Is a directory(21):
190731:210011 tmd[2704]: I start_transfer:starting:id=3428,dir=down,pri=1800,qpos=0 of 1,net=wifi,on=wifi,was=WAITING,try=1,ceh=0x144840:
190731:210011 tmd[2704]: E qmgr:fopen_to_write:id = 3428, path = ---, err = Is a directory (21):

The reader of such things will notice that two different programmers wrote different parts of the code (and different parts of the error messages). Since the two people can not get the error strings to match, you can guess at what the chances are they can get the parts of the code to "match".
JB has lots of money, he can just keep cycling programmers through the project until two of them "get it right" for their corresponding parts of the programming.

Well, I guess that answers that question! I'll update to the latest firmware then, and see if that helps the battery life.

Shari

[shalym]

Originally Posted by shalym

Well, I guess that answers that question! I'll update to the latest firmware then, and see if that helps the battery life.

Shari

Updating seems to have helped. Only lost about 20% in one day. Still not great, but much better than 75-80%, which is what it was doing before the update. I left the update.bin.tmp.partial directory in place to see if it will continue to block updates.

Shari

[Barty]

How do you decode the production date from digits 9-12 of the serial? (I'm just curious how old my voyage which I bought used is.) Thanks

[ilovejedd]

Originally Posted by Barty

How do you decode the production date from digits 9-12 of the serial? (I'm just curious how old my voyage which I bought used is.) Thanks

9 02 6: 01/11/2019

Year: 9: 2019

Week: 02: 2nd week of the year (01/06-01/12)

Day: 6: 6th day of the week (Friday, 01/11)

[hius07]

Originally Posted by Barty

How do you decode the production date from digits 9-12 of the serial? (I'm just curious how old my voyage which I bought used is.) Thanks

Year Manufactured (9)
Week Manufactured (10-11)
Day of the Week Manufactured (12)

[j.p.s]

Originally Posted by Barty

How do you decode the production date from digits 9-12 of the serial? (I'm just curious how old my voyage which I bought used is.) Thanks

I think digit 9 is year (2010-2019)
digits 10 and 11 week number
and digit 12 day of week
but I can't find the post(s) that document it.

[NiLuJe]

When it rains, it pours .

IIRC, that came to our attention after someone mentioned http://kindle.zzweb.ru/sn/ in a thread. I don't have the ref. to the thread in question, though.

[j.p.s]

Originally Posted by NiLuJe

When it rains, it pours .

IIRC, that came to our attention after someone mentioned http://kindle.zzweb.ru/sn/ in a thread. I don't have the ref. to the thread in question, though.

Must be this one then: https://www.mobileread.com/forums/sh....php?p=3771356

[shalym]

Originally Posted by ilovejedd

9 02 6: 01/11/2019

Year: 9: 2019

Week: 02: 2nd week of the year (01/06-01/12)

Day: 6: 6th day of the week (Friday, 01/11)

Interesting. So my Oasis 3, with 9295 was manufactured on July 19th...just 10 days before I received it?

Shari

[ilovejedd]

Originally Posted by shalym

Interesting. So my Oasis 3, with 9295 was manufactured on July 19th...just 10 days before I received it?

+/- a day. I'm not sure if that week number is Sun-Sat or Mon-Sun.

That would certainly explain why they're so delayed. Amazon's shipping the Oasis 3 as fast as they can manufacture them.

I checked my order history and interestingly enough my PW4 32GB non-SO (delayed ship times) was manufactured 10/27/2018 and I probably received it around 11/10/2018.

[knc1]

Mon-Sat?
No wonder they are having logistical problems (six day week).

[ilovejedd]

Originally Posted by knc1

Mon-Sat?
No wonder they are having logistical problems (six day week).

Whoopsie. Corrected.