NickelMenu: An integrated launcher for Kobo eReaders

[DNSB]

Originally Posted by baursak

Unfortunately this folder contains not FB2 only. - Therefore Kobo does successfully reveal files in that folder, unless I will explicitly prevent it to so.

It appears that Kobo's firmware is capable of rendering FB2 ebooks. The last time I tested this was with the original Kobo back in 2011 but just tried an FB2 ebook of Alice in Wonderland on my Sage and Nickel is showing the text and illustrations. There is a default stylesheet(?) in \kobo-update-4.38.21908.zip\KoboRoot.tgz\KoboRoot.tar\.\usr\loc al\Kobo\fb2.xsl.gz

[WormGod]

Originally Posted by Aleron Ives

What does the voltage claim to be if you charge to 100% and then use the Clara for a little while? You'll probably see a nonsensical value like 4.8 V at first, but once it drops, you may be able to estimate what v_max is in order to do the voltage calculations.

I will start tracking my voltage as I use it over the next week or two and see what we get.

[rudy0ne]

Hello guys. I just installed NickelMenu a few days ago and it's working great so far! But I've been wondering if either of these two things are currently possible: adding menu entries to basic notebooks just like in the reader, plus adding a menu entry which toggles bluetooth?

Thanks so much for all your work!

[Aleron Ives]

You could probably add a menu entry that issues a Linux command to turn Bluetooth on and off, but I've not seen any examples of that. You'd have to do some testing over telnet to see which Bluetooth-related commands BusyBox supports.

[kaynsel]

Hello, have you been able to toggle the rainbow effect setting in the KLC using NickelMenu?

[mlavache]

Installed NM on my Clara BW, and I can change the orientation to landscape, but the touchscreen is rotated 180 degrees from the display. In other words, to press a button on the upper-right corner, I have to press the lower-left corner.

This happens in both landscape and inverted landscape.

[WormGod]

Originally Posted by Aleron Ives

What does the voltage claim to be if you charge to 100% and then use the Clara for a little while? You'll probably see a nonsensical value like 4.8 V at first, but once it drops, you may be able to estimate what v_max is in order to do the voltage calculations.

I did track the voltage_now, charge_now, and time_to_empty_now while using the Clara. Here are the raw numbers:

% v_now c_now time_to_empty_now
100 4161100 1380 43980
94 4100100 1354 48720
87 4024400 1218 38820
84 3997500 1179 34800
79 3971900 1119 39480
70 3943800 996 56940
67 3916900 987 28860
63 3876600 892 25680
58 3843700 816 27720
54 3818000 759 25560
47 3787500 698 24660
41 3768000 573 15720
37 3721600 322 10080
100 4161100 1380 51780

voltage_min_design remained constant at 3520
time_to_full_now remained constant at 3932100

1. Is it reasonable to assume that v_max would be 4161100, or do you think a different value is more likely?
2. Is there any value to using the charge_now values?
3. The time_to_empty_now does have some anomalies, but do you have any idea what it (or the time_to_full_now) is supposed to represent?

Thanks!

[Aleron Ives]

Based on 4161100, it would seem v_max is 4200000, or 4.2V. The c_now value should be the current capacity in mAh, so you can divide by c_full to get another % estimate. I would assume that time_to_empty_now is the estimated number of seconds you can use the device before the battery is dead, while time_to_full_now would be the estimated number of seconds to fully charge the battery and is probably meaningless when the battery is discharging.

[Frogm4n]

The c_now and time_to_empty_now numbers are likely to shift if you let the battery drain all the way down, so that the charge controller gets a more accurate reading of the battery capacity.

[WormGod]

Originally Posted by Aleron Ives

Based on 4161100, it would seem v_max is 4200000, or 4.2V. The c_now value should be the current capacity in mAh, so you can divide by c_full to get another % estimate. I would assume that time_to_empty_now is the estimated number of seconds you can use the device before the battery is dead, while time_to_full_now would be the estimated number of seconds to fully charge the battery and is probably meaningless when the battery is discharging.

Thanks! There is no c_full, but there is a capacity - probably the same? I will play around some more and see what I get.

[Aleron Ives]

You could estimate what c_full should be based on c_now after charging and hardcode a reasonable value for c_full, though.

[WormGod]

Originally Posted by Aleron Ives

You could estimate what c_full should be based on c_now after charging and hardcode a reasonable value for c_full, though.

Sounds reasonable. I'll run it through a few charge cycles to see where c_now is after charging multiple times.

Capacity is just the current % displayed by Kobo.

[bohn]

Originally Posted by rudy0ne

plus adding a menu entry which toggles bluetooth?

I would love this. I have been messing around in telnet on the kobo trying to get it to do this with scripts etc.. and not having much luck.

Some of the time if I enable bluetooth manually , I can then disable/re-enable with a script. But not always.

[lumping-sugar66]

If you're comfortable building NickelMenu from source, the latest master branch in the official repository has "bluetooth on/off" instructions implemented.

                  nickel_bluetooth   - one of:
                                         enable   (4.34.20097+)
                                         disable  (4.34.20097+)
                                         toggle   (4.34.20097+)
                                         check    (4.34.20097+)
                                         scan     (4.34.20097+)

Or maybe @geek1011 can make a release of NickelMenu 0.5.5

[silvern0va]

Originally Posted by lumping-sugar66

If you're comfortable building NickelMenu from source, the latest master branch in the official repository has "bluetooth on/off" instructions implemented.

                  nickel_bluetooth   - one of:
                                         enable   (4.34.20097+)
                                         disable  (4.34.20097+)
                                         toggle   (4.34.20097+)
                                         check    (4.34.20097+)
                                         scan     (4.34.20097+)

Or maybe @geek1011 can make a release of NickelMenu 0.5.5

Yeah I would prefer if we could get a new release. I tried compiling it and maybe it's because I'm on Windows but it is NOT working.