NickelMenu: An integrated launcher for Kobo eReaders

[Asyd Rayn]

Love this little app - I have a quick question: In my settings, I have wifi on/off -- it takes a while for the wifi to make a connection with my saved WiFi networks. Is this normal behavior in NickelMenu? It's PDQ when not using NickelMenu and simply turning on the Wifi option.

Also, is there a string to be used to auto-connect when I click the sync button or whenever I use something that needs wifi, similar to auto USB connect without the prompt?

[Aleron Ives]

I made an update for my battery statistics calculation script. It now also calculates the remaining percentage from the battery's voltage, which I've found to be a more reliable capacity indicator than either the mAh-based estimate or Nickel's built-in estimate. I removed some trailing zeroes on the voltage line to make more room for displaying the extra statistic. Here's the new script:

# Battery Statistics Calculator 1.1 (2024-05-25) by Aleron Ives
#
# This script calculates battery statistics for the Kobo Libra 2.
# Check the contents of /sys/class/power_supply/ if you use a different
# model to ensure that the statistics you want to track are available.
#
# You can use NickelMenu to invoke this script like so:
# menu_item :main :Battery :cmd_output :500 :/mnt/onboard/.adds/battcalc.sh

# Gather the necessary statistics

meter=$(cat /sys/class/power_supply/battery/capacity)
v_now=$(cat /sys/class/power_supply/battery/voltage_now)
v_min=$(cat /sys/class/power_supply/battery/voltage_min)
v_max=$(cat /sys/class/power_supply/battery/voltage_max)
c_now=$(cat /sys/class/power_supply/battery/charge_now)
c_full=$(cat /sys/class/power_supply/battery/charge_full)
c_dfull=$(cat /sys/class/power_supply/battery/charge_full_design)

# Format the statistics

let v_pct=$v_max-$v_now; let v_pct/=7000 # Calculate charge percentage from V
let v_pct=100-$v_pct                     # "
let v_now/=1000; let v_min/=10000; let v_max/=10000  # Convert to V
let c_now/=1000; let c_full/=1000; let c_dfull/=1000 # Convert to mAh
let v_nowr=$v_now%1000; let v_now/=1000 # Simulate floating-point arithmetic
let v_minr=$v_min%100; let v_min/=100   # "
let v_maxr=$v_max%100; let v_max/=100   # "
let charge=$c_now*100/$c_full     # Calculate charge percentage from mAh
let c_health=$c_full*100/$c_dfull # Calculate health percentage from mAh

# Display the results

echo Capacity: $c_now mAh / $charge% / $meter%
echo Voltage: $v_min.$v_minr V / $v_now.$v_nowr V / $v_max.$v_maxr V / $v_pct%
echo Health: $c_full mAh / $c_dfull mAh / $c_health%

If you're using the Libra Colour, you'll want to change the v_pct divisor from 7000 to 9000, since the Libra Colour charges its battery to 4.4 V, rather than 4.2 V.

[hatuluang]

Originally Posted by Aleron Ives

I made an update for my battery statistics calculation script. It now also calculates the remaining percentage from the battery's voltage, which I've found to be a more reliable capacity indicator than either the mAh-based estimate or Nickel's built-in estimate. I removed some trailing zeroes on the voltage line to make more room for displaying the extra statistic. Here's the new script:

# Battery Statistics Calculator 1.1 (2024-05-25) by Aleron Ives
#
# This script calculates battery statistics for the Kobo Libra 2.
# Check the contents of /sys/class/power_supply/ if you use a different
# model to ensure that the statistics you want to track are available.
#
#

Hi Aleron, thanks for the battery script.
What number of v_pct divisor for Clara 2E (3.7 V)?
Thanks

[Aleron Ives]

Enable telnet with devmodeon, cd into /sys/class/power_supply/ and use the ls command to see what's there. You can use cat to view the contents of the various statistics.

[hatuluang]

Originally Posted by Aleron Ives

Enable telnet with devmodeon, cd into /sys/class/power_supply/ and use the ls command to see what's there. You can use cat to view the contents of the various statistics.

Thanks,
I am using your nm syntax (https://www.mobileread.com/forums/sh...&postcount=993)
to get /sys/class/power_supply/ and compare to your latest battery calculation (image attached)

The difference in current voltage is 4.11 vs 4.10, while the calculated percentage by dividing (current capacity / maximum capacity) is 81%

So it is ok to use battery calculation for Libra to Clara 2E or does it need to be changed?
Thanks

[Aleron Ives]

Oh nice, it seems the Clara 2E has all the statistics, too.

It looks like v_max is the same (4.2 V), but v_min is not (3.6 instead of 3.5 V). You should change the v_pct divisor from 7000 to 6000.

I do wonder if the Libra 2 reports v_min incorrectly. I've noticed that the charge drops off rapidly below 3.6 V, so perhaps 3.52 V is not the real minimum.

[hatuluang]

Originally Posted by Aleron Ives

Oh nice, it seems the Clara 2E has all the statistics, too.

It looks like v_max is the same (4.2 V), but v_min is not (3.6 instead of 3.5 V). You should change the v_pct divisor from 7000 to 6000.

I do wonder if the Libra 2 reports v_min incorrectly. I've noticed that the charge drops off rapidly below 3.6 V, so perhaps 3.52 V is not the real minimum.

Thanks,
Please find the results with v_pct divisor = 6000

[Aleron Ives]

It's good to see that the Clara 2E also reports nonsensical voltage values sometimes. If your battery were really at 4.6 V, your Clara would probably be on fire. The middle value should always be between 3.6 and 4.2, but sysfs doesn't always report real numbers, especially during charging.

[hatuluang]

Originally Posted by Aleron Ives

It's good to see that the Clara 2E also reports nonsensical voltage values sometimes. If your battery were really at 4.6 V, your Clara would probably be on fire. The middle value should always be between 3.6 and 4.2, but sysfs doesn't always report real numbers, especially during charging.

You are right, thanks a lot.

[mullse01]

Hello,

I've been poring over the NM guides, but I haven't been able to find a clear answer: is there a way to display a confirmation dialog in NickelMenu before an action takes place?

For example, with the "power : reboot" command, is there a way to display a dialog that asks you to confirm or cancel the reboot, and then have a chain_success/chain_failure that then takes (or doesn't take) the action?

Something like this:

menu_item : main : Reboot : dbg_msg : Are you sure you want to reboot?

chain_failure : skip -1

chain_success : power : reboot

(I know this is not how dbg_msg works, I'm just using it as a placeholder)

[geek1011]

Originally Posted by mullse01

I've been poring over the NM guides, but I haven't been able to find a clear answer: is there a way to display a confirmation dialog in NickelMenu before an action takes place?

Not in the current form where all actions are synchronous. For now, the recommended way is to use NickelDBus with a shell script and cmd_spawn.

[Rid]

Originally Posted by Asyd Rayn

Also, is there a string to be used to auto-connect when I click the sync button or whenever I use something that needs wifi, similar to auto USB connect without the prompt?

But it would be awesome if you could have a start sync in NickelDBus...

[hatuluang]

Originally Posted by mullse01

Hello,

I've been poring over the NM guides, but I haven't been able to find a clear answer: is there a way to display a confirmation dialog in NickelMenu before an action takes place?

For example, with the "power : reboot" command, is there a way to display a dialog that asks you to confirm or cancel the reboot, and then have a chain_success/chain_failure that then takes (or doesn't take) the action?

Something like this:



(I know this is not how dbg_msg works, I'm just using it as a placeholder)

I know that is a good idea.
However, for this sample, the objective of having a reboot command in Nickelmenu is for the user to be able to reboot their device easily rather than take a manual reboot with the power button.

[hatuluang]

Originally Posted by Asyd Rayn

Love this little app - I have a quick question: In my settings, I have wifi on/off -- it takes a while for the wifi to make a connection with my saved WiFi networks. Is this normal behavior in NickelMenu? It's PDQ when not using NickelMenu and simply turning on the Wifi option.

When you access the discovery page with WiFi turned off, the Kobo preview window will appear asking whether to enable WiFi or not. When confirming yes, the time to connect the WiFi will be the same as when you turn on WiFi via Nickelmenu.

[mullse01]

Originally Posted by geek1011

Not in the current form where all actions are synchronous. For now, the recommended way is to use NickelDBus with a shell script and cmd_spawn.

Hello again,

I'm attempting to create a shell script like you mentioned, but i can't seem to get NickelDBus to actually *do* anything after the dialog box appears. Here's the text of the script as I've got it:

#!/bin/sh

signal=$(qndb -t 10000 -s dlgConfirmResult -m dlgConfirmAcceptReject "Reboot Kobo" "Are you sure you want to reboot?" "Yes" "No")

if ( $signal -eq 1 )
then
qndb -m mwcToast 3000 "Rebooting..."
qndb -m pwrReboot
elif ( $signal -eq 0 )
then
qndb -m mwcToast 3000 "Reboot cancelled."
fi

Am I missing some obvious syntax issue?

(Sorry if this is the wrong thread--the NickelDBus thread hasn't been posted in for like two years, and I didn't want to necropost...)