Onyx Boox Kon-Tiki 2 (Nova3 platform) - apps

[mergen3107]

I did factory reset and setup everything from scratch yesterday.
I stayed with Magisk 23.0, everything seems to work great now, including new gestures and MagsikSSH.

[mergen3107]

Alarm clocks are not working if the device is asleep. However, they trigger as soon as the device is unlock via cover or button.
Is there a way to make them work?

[Renate]

Originally Posted by mergen3107

Alarm clocks are not working if the device is asleep. However, they trigger as soon as the device is unlock via cover or button.
Is there a way to make them work?

Mmm, I don't think so. There's a big difference between an Eink device that's gone to sleep and your cell phone with the screen off. We're looking at the difference between a device that stays charged for a few days and one that stays charged for a month.

I can get you some actual numbers in a bit.

[mergen3107]

OK! I suppose it is intended to be this way then. I just fell into the trap of having a working speaker on the Onyx had my phone discharged with no charging brick around and had only Kon-Tiki 2 with me, to wake me up next morning. So I hoped at least

[Renate]

I just checked an old Nook Glow4 (the old 7.8"). When it's normal sleeping it's drawing less than 3/4 of a milliampere. When it's idling away, about 35 mA. Those are pretty small numbers. Some devices wakeup at infrequent intervals. I'm not sure how long. If you set the alarm for tomorrow morning it might wake you in a week!

[mergen3107]

Handy!
Thank you

[mergen3107]

Does anyone else experience the same?
Sometime when I unlock the device, the touch input are not working. Lock and unlock helps, but this issues happens from time to time.

[mergen3107]

@Renate
Do you know the best way to recover a text file (actually, .lua file), accidentally deleted from the device?

[Renate]

Hmm. I don't know if your data partition is encrypted.
Also, any usage of your device might overwrite the "deleted" file.
The best would be to make a backup now of your data partition on your desktop.
You could do that with EDL. Or UMS.
Then you can scan the whole thing for your file. It's easier if you remember some content.
Is the .lua file your own work? Or is there another source?

[mergen3107]

Originally Posted by Renate

Hmm. I don't know if your data partition is encrypted.
Also, any usage of your device might overwrite the "deleted" file.
The best would be to make a backup now of your data partition on your desktop.
You could do that with EDL. Or UMS.
Then you can scan the whole thing for your file. It's easier if you remember some content.
Is the .lua file your own work? Or is there another source?

Thank you!

This .lua file is generated by KOReader app, it is metadata and settings of opened books. I just had recently a crash opening a book, which was solved by removed these metadata lua files. Alas, I didn't keep the broken one and deleted it, might be very useful for debugging.

Some of the content might be easily found from new healthy files, like structures and common words. What tool should I then use? Recuva, for example? This is a PC specific file recovery tool. Or should I look for something Android-oriented?

I am not sure whether it is encrypted or not. I didn't set up the encryption manually. Does the enabled PIN code requirement make it encrypted?

[Renate]

It could be encrypted without you even doing anything.
There's lots of things that I've never done a deep dive into, that's one.

I have done similar things with corrupted hard disks.
In the best of all possible worlds (thank you, Dr. Pangloss) the blocks are contiguous.
You can scan the raw blocks looking for file headers and try to assemble continugous blocks.

I've usually just made ad-hoc tools to search. The usual tools I use are designed for sane sized files. Searching 32 GB with less than 40 GB memory is not currently possible. I should make it possible though. Of course you could break your big file into smaller chunks.

E:\>findtext m.img dm-verity /x30 /y50
E:\m.img
01DA501B                     drivers/md/dm-verity-target.c
01DDB144                     drivers/md/dm-verity-fec.c
01E11A5A                                dm-verity enforcing
01EC577A                                dm-verity device corrupted

In any case, if you want to recover your stuff, you should either archive userdata or else scan it now, before you write more files that will overwrite the old ones.

[mergen3107]

@Renate
Could you please point me in the right direction?

USB OTG keyboard’s mapping has some of the digit keys mapped wrong. In Button Mapper however these keys are recognized correctly, like NUMPAD_1 for “1”, etc.

Numbers 6-9 work, numbers from 1-5 don’t.

[Renate]

I know less than nothing about Button Mapper. So going on the rash presumption that it's not the problem... Just make sure under Android Settings > System > Languages > Physical Keyboard > that it says "Default".

When you connect any type of keyboard there should appear something in logcat saying what the device is and what keylayout it decided to load. Check that first for VID/PID and whatever.kl

$ logcat | grep attached
$ logcat | grep keylayout

Use my UsbMode.apk and see the "Linux Code" and the "Android Code" for what you are talking about.
http://www.temblast.com/usbmode.htm

[mergen3107]

Thank you! I’ll have a thorough look

[mergen3107]

Thank you very much for your USB mode app!

I found that these four strange Numpad buttons are not recognized as usual NUMPAD_# keys. They don’t have Linux code, only Android one. Symbol says BUTTON_1 instead of NUMPAD_1.

The device is recognized as SONiX USB device. It was default and I also can choose languages.

With the second logcat you provided I can see that the keyboard was registered 9 times in a row. Path leads to /system/usr/keylayout/Generic.kl .

So I guess my custom keyboard has weird names for those numpad guys, but only on Android. In Windows/Linux/MacOS they work fine though